![](https://secure.gravatar.com/avatar/2426734ec25e928cced5a64a9e3657e6.jpg?s=120&d=mm&r=g)
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.