Date: Wed, 11 Aug 2004 14:12:41 -0700 (PDT) From: Rostislav Krasny <rosti_bsd@yahoo.com> To: John Baldwin <jhb@FreeBSD.org>, freebsd-arch@FreeBSD.org Cc: Rostislav Krasny <rosti_bsd@yahoo.com> Subject: Re: adv(4) bandaid [Was Re: again question about "IRQ 2 problem"] Message-ID: <20040811211241.17442.qmail@web14828.mail.yahoo.com> In-Reply-To: <200408111111.35564.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--- John Baldwin <jhb@FreeBSD.org> wrote: > On Tuesday 10 August 2004 08:27 pm, Rostislav Krasny wrote: > > --- John Baldwin <jhb@FreeBSD.org> wrote: > > > On Saturday 07 August 2004 11:35 am, Rostislav Krasny wrote: > > > > --- John Baldwin <jhb@FreeBSD.org> wrote: > > > > > This should be fixed in rev 1.35 of sys/kern/subr_rman.c > Please > > > > > let me know if it is not, thanks! > > > > > > > > Thank you very much! The "IRQ 2 problem" is fixed now and that > > > > device (ed1) is working. > > > > > > > > The only strange thing is what I see in 'dmesg -a' output after > > > > booting in verbose mode (the first "adv1:..." line): > > > > > > Try this patch to the adv(4) driver to see if your messages go > away: > > > > > > Index: dev/advansys/adv_isa.c > > > > =================================================================== > > > RCS file: /usr/cvs/src/sys/dev/advansys/adv_isa.c,v > > > retrieving revision 1.26 > > > diff -u -r1.26 adv_isa.c > > > --- dev/advansys/adv_isa.c 30 May 2004 20:08:24 -0000 1.26 > > > +++ dev/advansys/adv_isa.c 9 Aug 2004 19:17:11 -0000 > > > @@ -117,6 +117,12 @@ > > > struct resource *iores, *irqres; > > > > > > /* > > > + * We don't know of any PnP ID's for these cards. > > > + */ > > > + if (isa_get_logicalid(dev) != 0) > > > + return (ENXIO); > > > + > > > + /* > > > * Default to scanning all possible device locations. > > > */ > > > port_index = 0; > > > > After patching the "adv_isa.c" file and rebuilding the GENERIC > kernel > > those messages went away. Previously posted chunk of the 'dmesg -a' > > output looks so now: > > > > isa_probe_children: probing PnP devices > > ed1: <ISA PLUG & PLAY Ethernet Card> at port 0x200-0x21f irq 5 on > isa0 > > ed1: [GIANT-LOCKED] > > ed1: bpf attached > > ed1: Ethernet address: 00:00:21:82:25:03 > > type NE2000 (16 bit) > > unknown: <PNP0303> can't assign resources (port) > > unknown: <PNP0303> at port 0x60 on isa0 > > unknown: <PNP0800> failed to probe at port 0x61 on isa0 > > unknown: <PNP0a03> can't assign resources (port) > > unknown: <PNP0a03> at port 0x4d0-0x4d1 on isa0 > > unknown: <PNP0c02> can't assign resources (port) > > unknown: <PNP0c02> at port 0x208-0x20f on isa0 > > unknown: <PNP0501> can't assign resources (port) > > unknown: <PNP0501> at port 0x3f8-0x3ff on isa0 > > unknown: <PNP0700> can't assign resources (port) > > unknown: <PNP0700> at port 0x3f2-0x3f5 on isa0 > > unknown: <PNP0401> can't assign resources (port) > > unknown: <PNP0401> at port 0x378-0x37f on isa0 > > unknown: <PNP0501> can't assign resources (port) > > unknown: <PNP0501> at port 0x2f8-0x2ff on isa0 > > Device configuration finished. > > procfs registered > > > > > > P.S. What are these "unknown: <PNPXXXX>..." messages? I don't have > so > > many PnP devices. And my speaker (port 0x61) is working properly. I > > even can run 'kldload -v /boot/kernel/speaker.ko' and then 'morse > -p -e > > -w 23 I am a 5.2-CURRENT, test me.' :-) > > They are PnPBIOS entries for things like the ISA timers, AT 8259A > PICs, and the speaker. FreeBSD doesn't currently use the PnPBIOS > device entries to attach to these devices. If FreeBSD doesn't currently use the PnPBIOS device entries, why FreeBSD tries assign or probe resources for those device entries anyway? Please, correct me if I misunderstood something here. Thank you __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040811211241.17442.qmail>