DE-530 doesn't see eeprom
Harald Koenig
koenig@tat.physik.uni-tuebingen.de
Tue May 25 17:12:43 1999
using a `D-Link DE-530 CT+ Rev-B5' 10Mbit card, Linux usually doesn't `see' the eeprom.
when being in this state, tulip driver doesn't work at all, and de4x5 driver
words only with hw address 0:0:0:0:0:0:
using 2.2.9:
tulip.c:v0.90 10/20/98 becker@cesdis.gsfc.nasa.gov
eth0: Digital DC21041 Tulip at 0xe000, 21041 mode, EEPROM not present, 00 4c 69 6e 75 79, IRQ 0.
eth0: Old style EEPROM -- no media selection information.
note the strange `IRQ 0' too!
eth0: DC21041 at 0xe000 (PCI bus 0, device 9), h/w address 00:00:00:00:00:00, and requires IRQ12 (provided by PCI BIOS).
de4x5.c:V0.543 1998/12/30 davies@maniac.ultranet.com
eth0: media is BNC.
but in rare cases (maybe if Win95is first started after cold boot -- but Win95 network
never was configured and isn't used at all) the card works fine, eeprom and hw addresss
are found and tulip driver works too:
eth0: DC21041 at 0xe000 (PCI bus 0, device 9), h/w address 00:80:c8:e5:92:79,
and requires IRQ12 (provided by PCI BIOS).
de4x5.c:V0.544 1999/5/8 davies@maniac.ultranet.com
eth0: media is BNC.
and
tulip.c:v0.90 10/20/98 becker@cesdis.gsfc.nasa.gov
eth0: Digital DC21041 Tulip at 0xe000, 21041 mode, 00 80 c8 e5 92 79, IRQ 12.
eth0:21041 Media information at 30, default media 0800 (Autosense).
eth0: 21041 media #0, 10baseT.
if the card doesn't work well in Linux, it's _not_ enough to boot Win95 and
immediately reboot to Linux again. then the card still doesn't work correctly:(
any idea what'a wrong here ?
how can this be fixed ?
which additonal information do you need ?
thanks for any hint,
Harald
--
All SCSI disks will from now on ___ _____
be required to send an email notice 0--,| /OOOOOOO\
24 hours prior to complete hardware failure! <_/ / /OOOOOOOOOOO\
\ \/OOOOOOOOOOOOOOO\
\ OOOOOOOOOOOOOOOOO|//
Harald Koenig, \/\/\/\/\/\/\/\/\/
Inst.f.Theoret.Astrophysik // / \\ \
koenig@tat.physik.uni-tuebingen.de ^^^^^ ^^^^^