SiS630E Chipset based ethernet controller problems
 

This was mistakenly posted first in the network forum but I think it is better here.

After struggling for a little while I'm giving in. This post is similar to many others, but the so-far suggested remedies don't work. I tried them.....

It seems that something is a bit weird with this motherboard, the ASUS TUSI-M and SuSE Linux 7.3. The installation went like a dream, all devices recognised and correctly identified during the installation (CDR, DVD, onboard VGA, onboard sound, onboard LAN) but eth0 will not work.

The fix 'alias eth0 sis900' is already applied in SuSE7.3, so this isn't the problem. The hardware monitor shows the device using irq 10 (shared with another device), io memory at d400 which all sounds reasonable enough.

An extract from boot.msg:

insmod: /lib/modules/2.4.10-4GB/kernel/drivers/net/sis900.o: invalid parameter parm_io
insmod: /lib/modules/2.4.10-4GB/kernel/drivers/net/sis900.o: insmod eth0 failed
Setting up network device eth0
insmod: /lib/modules/2.4.10-4GB/kernel/drivers/net/sis900.o: invalid parameter parm_io
insmod: /lib/modules/2.4.10-4GB/kernel/drivers/net/sis900.o: insmod eth0 failed
SIOCSIFADDR: No such device
insmod: /lib/modules/2.4.10-4GB/kernel/drivers/net/sis900.o: invalid parameter parm_io
insmod: /lib/modules/2.4.10-4GB/kernel/drivers/net/sis900.o: insmod eth0 failed
eth0: unknown interface: No such device
insmod: /lib/modules/2.4.10-4GB/kernel/drivers/net/sis900.o: invalid parameter parm_io
insmod: /lib/modules/2.4.10-4GB/kernel/drivers/net/sis900.o: insmod eth0 failed
SIOCSIFBRDADDR: No such device
insmod: /lib/modules/2.4.10-4GB/kernel/drivers/net/sis900.o: invalid parameter parm_io
insmod: /lib/modules/2.4.10-4GB/kernel/drivers/net/sis900.o: insmod eth0 failed
eth0: unknown interface: No such device
insmod: /lib/modules/2.4.10-4GB/kernel/drivers/net/sis900.o: invalid parameter parm_io
insmod: /lib/modules/2.4.10-4GB/kernel/drivers/net/sis900.o: insmod eth0 failed
SIOCSIFNETMASK: No such device

insmod always fails, with or without parameters - what should the parameters be? The modinfo output still leaves me clueless.

As far as I can remember the only change I made to the standard installation is to add 'ether=d400,10,eth0' to the append line of the kernel command line:
<4>Kernel command line: auto BOOT_IMAGE=linux ro root=307 BOOT_FILE=/boot/vmlinuz enableapic vga=0x0317 hdd=ide-scsi ether=d400,10,eth0

So far, very familiar problems, but additionally I sometimes see a message like
eth0: No MII transceivers found
in the system log. I have no idea what this means.

Curiously the setup tool YaST1 shows eth0 as active, while YaST2 always shows it as inactive.

Now I don't know where insmod is getting parm_io from, if it is my ether= line going wrong, but to me this sounds like Linux knows what the hardware is, but doesn't know what to do with it. Could be me that upset something too....

That's enough complaining from me, can someone please help? Got to be worth a Mass of beer if you are ever in Munich.
:confused:

http://www.linuxquestions.org/questi...threadid=14851
double post

Hi,

first I want to tell you : "be happy it could be worse"
I can't answer because on my laptop it is absolutly the opposite.
SIS630/SIS900 eth0 works fine, Screen works slow, bad sound with lots of crashes, onboard Modem works not, CD/DVD yes CDRW no, etc.

Best regards
Ramon

The irony of this situation is, ultimately this computer will be a server, no display, no sound, no keyboard - the only thing I REALLY NEED to work is the #%&&* network!

Steep learning curve....

:smash: :study: