|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
On Sun, 2002-11-17 at 18:40, Time wrote:
> On Sun, Nov 17, 2002 at 05:52:10PM -0500, Stephen Gran wrote:
> > If you are sure that's the right module (you can check what the kernel
> > thinks of your card with lspci
>
> r2d2:~# lspci
> 00:00.0 Host bridge: Silicon Integrated Systems [SiS]: Unknown device 0648 (rev 02)
> 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP
> 00:02.0 ISA bridge: Silicon Integrated Systems [SiS]: Unknown device 0963 (rev 04)
> 00:02.3 FireWire (IEEE 1394): Silicon Integrated Systems [SiS] OHCI Compliant FireWire Controller
> 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
> 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 PCI Audio Accelerator (rev a0)
> 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 91)
> 00:09.0 Ethernet controller: 3Com Corporation 3c595 100BaseTX [Vortex]
> 01:00.0 VGA compatible controller: nVidia Corporation NV20 (GeForce3) (rev a3)
>
> and from dmesg:
>
> Nov 17 18:10:59 r2d2 kernel: sis900.c: v1.08.02 11/30/2001
> Nov 17 18:10:59 r2d2 kernel: eth0: Error EERPOM read ffff
>
>
> > and cross-reference with /usr/src/linux/Documentation,
>
> doing that now.
>
> > although you probably know that (^: )
>
> yes, but I do appreciate your reminding me 8)
>
> > try modprobe instead of insmod - it's much smarter about loading, and will
> > load other modules if needed.
>
> I'm trying to find out if there is a way to tell modproe where the
> device is located since it seems to be looking (and failing) at ffff
> which, according to bc is address 00 on the pci bus, which is returning
> in lspci as an unknow device.
Having done a certain amount of PCI BIOS work in a previous life, that
error, to me, looked like a complaint that FFFF had been read in the
address space that PCI devices use to identify and describe
themselves....and FFFF is a value that simply makes no sence.
Check the source of the sis900_get_mac_addr() func in
/usr/src/linux/drivers/net/sis900.c Chances are pretty high that this
is where modprobe is going arry (how many places in the code is EEPROM
misspelled as EERPOM?)
The EEPROM on the card is returning a bad value. Maybe try reseating
it? (yeah yeah, works in that other OS, I don't know what to tell ya)
_________________________________________________________________________
Philadelphia Linux Users Group -- http://www.phillylinux.org
Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce
General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
|
|