Date: Mon, 28 Aug 2000 18:03:56 -0400 From: Antoine =?iso-8859-1?Q?Beaupr=E9?= <abeaupre@chemcomp.com> To: Siegbert Baude <siegbert.baude@gmx.de> Cc: beaupran@IRO.UMontreal.CA Subject: Re: ed0 device timeout without conflict Message-ID: <39AAE1CC.6E357CD0@chemcomp.com> References: <39AA7993.EA7023DB@chemcomp.com> <39AADCCC.43CD1A66@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Siegbert Baude wrote: > > Hello Antoine, Hi, > > ed0 at port 0x300-0x31f iomem 0xd8000 irq 12 on isa0 > > ed0: address 00:00:1b:4d:57:30, type NE2000 (16 bit) > > > > But when I try to configure it (ifconfig ed0 inet 192.168.1.1) I get a > > kernel message: > > > > ed0: device timeout > > > > The man page says it might be: > > > > "Usually caused by an interrupt conflict with another card on the ISA > > bus." > > > > Unfortunatly, no other card is using interrupt 12. None is using the > > same port parameter (or iomem, for what it means?), either. > > I had this for myself and read from still another guy. I didnīt need the > NIC for the moment and so disabled this. On Linux boot however I see > some more verbose kernel messages: > > eth1: Tx timed out, cable problem? TSR=0x0, ISR=0x0, t=508. > > And thatīs true, because for the moment there is no cable or terminator > on it (second box is in a different location for now). Thatīs the same > statement of this other guy, who stated that this error will occur only > with no cable connected. This might be it. However, I think it is unlikely because the "link" light is on at the end of the cable. Humm... This is strange, because I'm trying to connect only 2 machines using a cross-link cable. I did that once without any problems (not with the exact same hardware, though). I will try to connect the machine to a hub and see what I have... > > There are strange things going on over ISA however: > > > > isab0: <Intel 82371AB PCI to ISA bridge> at device 7.0 on pci0 > > isa0: <ISA bus> on isab0 > > [...] > > isa0: too many dependant configs (8) > > isa0: too many dependant configs (8) > > isa0: unexpected small tag 14 > > > > Bet you have a Soundblaster AWE PnP? Good guess. :) > This card gives too many (more than > 8) PnP proposalsm, therefore this message. The "unexpected small tag 14" > error I donīt know, but was also reported here a few weeks ago. Look in > the archives on www.freebsd.org or maybe www.deja.com/usenet . Thanks, I'll take a look. As long as it's not related to the NIC, I don't care. > > I also have a few other problems with dmesg messages. For example, the > > kernel recognizes a USB bus/port, even if my motherboard is pre-USB and > > does not have any kind of USB support on. Even worse, the Kernel itself > > doesn't (by the config file, at least) USB support compiled in. Could > > this be because I haven't made a "make clean" after removing USB support > > from the kernel? > > A motherboard with Intel PIIX4 without USB support? I don't know what a Intel PIIX4 is, but the board is quite old. I really don't think there's support for USB on the board. I think USB wasn't even generally used at the time I bought my computer (3-4 years ago?). > Just not having the cable connected to your motherboard doesnīt mean this chip isnīt able > to do it. This I know. But the specs of the board are really against that. And what's worst is that I removed USB support from the kernel! There shouldn't be anything there! > > One third thing, before I leave, why isn't my modem (sio2) recognized > > (unknown: ...)? Is it because of PNP non-config? This is a small problem > > and I don't expect to have a hard time to solve... > > If it is a Winmodem, you do Iīm afraid ;-) It's not, and I've been running it happily on FBSD 3.X stable for a while. Thanks for the advice A. -- Antoine Beaupre System Administrator Chemical Computing Group, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39AAE1CC.6E357CD0>