Helge Fredriksen wrote:
case $1 in start) /sbin/modprobe 3c59x
Unless you have a 3Com card with this chipset don't modprobe 3c59x. Again you shouldn't need to manually modprobe anything.
ifconfig has only listing of the loopback device.
Then the network card isn't being seen yet. ifconfig only shows active nics unless you add the -a switch then it will show everything available.
If you compiled the natsemi module as a module did it load? What's the output of lsmod?
Didn't compile natsemi as a module, did a reconfigure of the kernel as adviced since I couldn't find any support on my CD for making this as a module.
Support for using modules is a kernel thing. I'm using 2.6.19.1 and in menuconifg it's the 3rd option down in the main menu.
You can tell if the kernel you're running has the natsemi code available by looking at the subdirectories of /sys/module.
Hmm, nope, couldn't see any natsemi stuff there.
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 ... 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. 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. HTH, Joe