lspci lists in one of it's lines:
00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139 C+ (rev 10)
Found this (as experimental) in the same place as the National Semincondutor driver, and thus enabled it with *. Recompiled and installed new kernel. WOW: eth0 up and running!
Got these warnings though:
8139cp: pci dev 0000:00:10.0 (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
8139cp: Try the "8139too" driver instead.
How can I build and install this module, since it seems that it's not part of kernel config? Any hints on documents describing such a process on crux?
Helge
Yes, a * means it's compiled into the kernel. While an M means it can be loaded into the kernel as a module.
It shouldn't matter if it's built in the kernel or as a module. I think modules just allow more flexibility for configuring your system and switching hardware.
You should have a * on EISA, VLB, PCI and on board controllers
and a * on National Semiconductor DP8381x series PCI Ethernet support
check dmesg and lspci -> is your hardware physically installed correctly in the computer? Check all your connections.
-Toshi
Date: Wed, 3 Jan 2007 21:34:13 +0100
From: helgeingvart@gmail.com
To: jgilmour@bigpond.net.au
Subject: Re: Fwd: Netgear FA-311
CC: crux@lists.crux.nuThen it's not compiled in either. The natsemi code is located in:
Device drivers -> Network device support -> Ethernet (10 or 100Mbit) ->
EISA, VLB, PCI and on board controllers (i think this is a 2.6.19.x
thing) -> National Semiconductor DP8381x series ...
I've done all this already before. However I have a * on National Semiconductor
DP8381x series, does that mean that its somehow compiled into the kernel,
and not loaded as a module, and thus not visible in /sys/modules? Also, I'm
running a 2.6.15.6 kernel, dunno if that means anything? That was the latest
2.2 image though. I will try to mark it with m instead and load it using modprobe in
my net script to see if that makes a difference.If you've enabled kernel modules above then you can select m or * and if
you haven't then you'll only be able to select *. Either way should be
fine.
I already have a m marked on the EISA, VLB, PCI and on board controllers.Now once you've done recomiled your kernel and run lilo and rebooted
then check that eth0 will be available with ifconfig -a.
The reason a lot of this stuff isn't in the handbook or on the CD is
that it is assumed that someone interested in CRUX will have a firm
grasp of setting up hardware and software and recompiling kernels. If
you're willing to working through these challenges though it is a very
rewarding distribution.
Please bear with me, I'm not very often using Linux, but I will more
in the future. Anyway, thanks for your support. And yes: I am learning...
Regard,
Helge F.
Get free, personalized online radio with MSN Radio powered by Pandora. Try it!