Re: 3COM 3c509 eeprom failed to come ready
On Sun, 25 Aug 2002, Nate Lawson wrote: Beat me to it. Every problem I've had in the past with a pre-PnP ISA card was due to other device probes confusing the proper device. So I typically disable all probes of any non-PnP ISA cards unless I have them. Yea, the probe for the 3c507 (ie driver) isn't very smart. I've rewritten all the ISA front ends for the 'ie' driver but haven't yet gotten the rest of the driver into shape. If someone is interested in picking this up from me do speak up. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3COM 3c509 eeprom failed to come ready
On Sat, Aug 24, 2002 at 10:30:15PM -0400, Craig Rodrigues wrote: On Sat, Aug 24, 2002 at 06:16:48PM -0800, Beech Rintoul wrote: On Saturday 24 August 2002 05:33 pm, Craig Rodrigues wrote: On Sat, Aug 24, 2002 at 05:00:25PM -0800, Beech Rintoul wrote: ep0: eeprom failed to come ready ep0: eeprom failed to come ready ep0: eeprom failed to come ready ep0: eeprom failed to come ready ep0: Ethernet address 00:00:00:00:00:00 Well, your mileage may vary, but I had exactly the same error message with one of those cards about 3 months ago. Re-running the setup utils fixed it. If my memory serves me correctly, I also disabled PNP-OS in the bios. I already have PNP-OS disabled in the BIOS, (I needed to do this 4 years ago when running Linux.) Hi, I think I solved the problem. I did not need to recompile the kernel, and I did not have to reconfigure my NIC with the 3Com DOS utilities. I read the following post from 1999 by Poul-Henning Kamp: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=632436+0+archive/1999/freebsd-current/19991128.freebsd-current Poul states that the probing of the ie and ex drivers affects the 3Com magic config registers. So, what I did was, I edited /boot/device.hints and commented out a bunch of lines and disabled a few drivers: #hint.ie.0.at=isa #hint.ie.0.port=0x300 #hint.ie.0.irq=10 #hint.ie.0.maddr=0xd hint.ie.0.disabled=1 #hint.fe.0.at=isa #hint.fe.0.port=0x300 #hint.le.0.at=isa #hint.le.0.port=0x300 #hint.le.0.irq=5 #hint.le.0.maddr=0xd hint.le.0.disabled=1 When I rebooted with the GENERIC kernel, my 3Com 509 card came up just fine. -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3COM 3c509 eeprom failed to come ready
On Sun, 25 Aug 2002, Craig Rodrigues wrote: I think I solved the problem. I did not need to recompile the kernel, and I did not have to reconfigure my NIC with the 3Com DOS utilities. I read the following post from 1999 by Poul-Henning Kamp: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=632436+0+archive/1999/freebsd-current/19991128.freebsd-current Poul states that the probing of the ie and ex drivers affects the 3Com magic config registers. So, what I did was, I edited /boot/device.hints and commented out a bunch of lines and disabled a few drivers: #hint.ie.0.at=isa #hint.ie.0.port=0x300 #hint.ie.0.irq=10 #hint.ie.0.maddr=0xd hint.ie.0.disabled=1 #hint.fe.0.at=isa #hint.fe.0.port=0x300 #hint.le.0.at=isa #hint.le.0.port=0x300 #hint.le.0.irq=5 #hint.le.0.maddr=0xd hint.le.0.disabled=1 When I rebooted with the GENERIC kernel, my 3Com 509 card came up just fine. Beat me to it. Every problem I've had in the past with a pre-PnP ISA card was due to other device probes confusing the proper device. So I typically disable all probes of any non-PnP ISA cards unless I have them. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3COM 3c509 eeprom failed to come ready
On Sun, 25 Aug 2002, Craig Rodrigues wrote: ep0: 3Com 3C509-TPO EtherLink III at port 0x300-0x30f irq 11 on isa0 ep0: Ethernet address 00:60:08:05:3d:bd There don't appear to be any substantial differences in the 'ep' driver between -CURRENT and -STABLE. It could be that some other device driver is stomping on the card... Boot verbose and see if there is any additional information. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: 3COM 3c509 eeprom failed to come ready
On Sat, Aug 24, 2002 at 07:12:02PM -0800, Beech Rintoul wrote: I'm not sure about an earlier -current, but I can tell you I'm running one of those cards with yesterday's -current with no problems. You didn't say which kernel you're running, but if it's GENERIC it has device ep uncommented. The only way I could get rid of that eeprom error was to re-run the setup util. Mine however wasn't hanging the boot it would go on and define the card as ep1. One thing you might try is putting the card in another slot and see if it will boot. Anyone else have this problem with -current? Hi, I am indeed having this problem with the GENERIC kernel that is included with the 20020818 -current snapshot. Here is some more information: - instead of booting the GENERIC kernel that gets installed with 20020818, if I boot with the kernel from the floppy disk that comes with 20020818, and then from the command-prompt specify the root filesystem as ufs:ad0s2a (which is where I installed -current), then the system boots up fine, and I have no problem with ep0, and in fact I can use ep0 successfully. So, there is something different between the GENERIC kernel and the kernel on the bootdisk in 20020818. Any idea what it could be? Thanks. -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
