• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

MSI MS6378LX w/LAN + Linux = trouble! Please help!

J

Joffer

Member
I've just got a new mainboard with vga, sound and nic integrated, ideal for a small server, more specific a MSI MS-6378XL - MSI Homepage: MS-6378 Product Info. The webpage says it has a RealTek 8100 chip, while I've located an AMDtek AN983B
chip on the mainboard, and so says the manual too. Looking at the info on the CD that came with the mainboard, and also doing a quick search on the net, told me it was a some kind of a tulip chip/nic, but modprobe tulip did not work, giving me this error:

with 2.2.20 kernel (trustix iso as of 20020301):

using /lib/modules/2.2.20-1tr/net/tulip.o
/lib/modules/2.2.20-1tr/net/tulip.o: init_module: device or resource busy
Hint: insmod errors can be caused by incorrect modules parameters, including
invalid IO or IRQ parameters


I also tried with a 2.4.18 kernel, but here i get this:

/lib/modules/2.4.18/kernel/drivers/net/tulip/tulip.o: init_module: No such
device
Hint: insmod errors can be caused by incorrect modules parameters, including
invalid IO or IRQ parameters
modprobe: insmod /lib/modules/2.4.18/kernel/drivers/net/tulip/tulip.o failed
modprobe: insmod tulip failed

lspci gives me:
00:0f.0 Ethernet controller: Bridgecom, Inc: Unknown device 9511 (rev 11)

any suggestions?
 
There is no Realtek 8100 listed on the redhat hardware compatibility list. Try the 8139 module (8139too according to the RH HCL).
 
yeah, but as i was saying, the homepage said realtek, but the manual, the chip on the mainboard, and the info on a textfile said ADMtek AN983B. I've just been informed that the kernel tulip driver isn't compatible with the ADMtek AN983B chip, so I will Donald Beckers drivers one more time. looks like i have to force an install or something.... well.. I'll keep this thread posted.

ohh.. I should have mentioned this being a very new mainboard, and I don't think MSI have updated the webpage, cuz it is a V3.0, not 1.7/8 or 2.0. It might be an OEM board perhaps, I got the mainboard like it was OEM/Bulk..

anyway.. will try (again) with Donald Beckers latest src.rpm drivers. will keep this thread posted.
 
Well.. I sent an email to Donald Becker, the man behind the tuliup.c driver among other things, and I got an answer. And it looks like I've been a bit blind, I did not see the link to his updates (http://www.scyld.com/network/updates.html)

The quick and dirty solution was:
# Transfer the Scyld PCI Netdriver package
# Perhaps use ncftpget ftp://ftp.scyld.com/pub/network/netdrivers-3.1-1.src.rpm
rpm -i ftp://ftp.scyld.com/pub/network/netdrivers-3.1-1.src.rpm
# Build the binary version for your kernel
cd /usr/src/RPM
rpm -bb SPECS/netdriver*.spec
# Now install it your newly built package.
rpm -i --force RPMS/i386/netdrivers-3.1-1.i386.rpm
(or rpm -i --force RPMS/i386/netdrivers-3.1-1.i686.rpm in my case)

well, isn't it typical. I actually did go out and by myself a cheap unex 10/100 NIC for 12 bucks, and now, about 6 hours later, I solved the mystery.. very well.. can't do any harm having a (cheap,) spare NIC lying around.

well.. I'm off to do a new install on this box.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top