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 controllersand a * on National Semiconductor DP8381x series PCI Ethernet supportcheck dmesg and lspci -> is your hardware physically installed correctly in the computer? Check all your connections.-ToshiDate: Wed, 3 Jan 2007 21:34:13 +0100From: helgeingvart@gmail.comTo: jgilmour@bigpond.net.auSubject: Re: Fwd: Netgear FA-311CC: 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.xthing) -> 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 inmy net script to see if that makes a difference. If you've enabled kernel modules above then you can select m or * and ifyou haven't then you'll only be able to select *. Either way should befine.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 rebootedthen 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 isthat it is assumed that someone interested in CRUX will have a firmgrasp of setting up hardware and software and recompiling kernels. If you're willing to working through these challenges though it is a veryrewarding distribution.Please bear with me, I'm not very often using Linux, but I will morein the future. Anyway, thanks for your support. And yes: I am learning... Regard,Helge F. _________________________________________________________________ Type your favorite song. Get a customized station. Try MSN Radio powered by Pandora. http://radio.msn.com
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 On 1/3/07, Hitoshi Satow <satowh@hotmail.com> wrote:
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.nu
Then 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! <http://radio.msn.com>
Helge Fredriksen wrote:
lspci lists in one of it's lines:
00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139 C+ (rev 10)
This probably means that the error from the beginning was believing that it's a national semiconductor nic while it was a very common realtek chip card...
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!
:) good! the [*] means that it's static in your kernel, so you don't need to modprobe it.
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.
you probably have both 8139cp and 8139too static in the kernel, so you get the first warning, but you also have support for the 8139too cards, so it's working anyway...
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?
Building the kernel is not a crux-specific issue, so it's not part of the crux documentation, but the subject of many generic how-tos and of part of the kernel documentation... it requires a good knowledge of the hardware you own or the need to make a very generic kernel. If you want to build "drivers" as modules you should have kernel modules enabled in Loadable module support --> Enable loadable module support Then go in Device Drivers->Network device support->Ethernet (10 or 100Mbit)->Ethernet (10 or 100Mbit) and make sure that you press M on RealTek RTL-8129/8130/8139 PCI Fast Ethernet Adapter support (NEW); this will show <M> beside it. Make sure an <M> shows on everything you want as module all along the menus of the menuconfig, and that [*] is selected for every piece of hardware that is needed for boot. The help will often hint you whether you need it or not... I think the kernel config on the boot-cd might be a good "inspiration", you could start from there and then gradually tune it for your system/needs.
Helge
bye, happy kernel-config-hacking ;) giorgio -- NullPointer || GnuPG/PGP Key-Id: 0x343B22E6
participants (3)
-
Giorgio Agrelli -
Helge Fredriksen -
Hitoshi Satow