Hey, got problems after doing the change in config + $ make menuconfig $ make all $ make modules_install $ cp arch/i386/boot/bzImage /vmlinuz $ cp System.map / Lilo loading CRUXEBDA is big; kernel setup stack overlaps LILO second stage........ Helge F. On 1/2/07, Clare Johnstone <claregj@gmail.com> wrote:
Hi Helge
Device Drivers ---> Network device support ---> Ethernet (10 or 100Mbit) ---> < > National Semiconductor DP8381x series PCI Ethernet support And if you press "?" key it says: More specific information and updates are available from <http://www.scyld.com/network/natsemi.html>.
Hope this helps clare
On 1/2/07, Helge Fredriksen < helgeingvart@gmail.com> wrote:
Could you give me some clues as to which section in the kernel setup I should look in? I tried to have a look, but couldn't seem to locate it
in a intuitive manner...
Regards, Helge F.
On 12/31/06, Joe Gilmour <jgilmour@bigpond.net.au> wrote:
Helge Fredriksen wrote:
Hello,
I've just installed Crux 2.2 on a PC with a brand new Netgear FA-311 network card. I'm trying to launch the driver adding the statement
/sbin/modprobe natsemi
to the /etc/rc.d/net script. However, I found that this module probably isn't installed. How do I proceed to upgrade my system?
Best regards, Helge Fredriksen Welcome to CRUX.
You need to either compile a new kernel with the natsemi code built in (then you wont need to modprobe it) or build the module in whiuch case
you can just build and install the modules.
Normally a system will automatically load the modules so you shouldn't need to modprobe at all.
HTH,
Joe
Helge Fredriksen wrote:
Hey, got problems after doing the change in config +
$ make menuconfig $ make all $ make modules_install $ cp arch/i386/boot/bzImage /vmlinuz $ cp System.map /
Lilo loading CRUXEBDA is big; kernel setup stack overlaps LILO second stage........
OK, 2 questions. Does your lilo.conf point to your new kernel? Did you actually run lilo after you copied your kernel? Joe
Nope, didn't know I had to do that... No vmlinuz backup either I'm afraid. I guess I can fix this using my crux install CD? Helge On 1/2/07, Joe Gilmour <jgilmour@bigpond.net.au> wrote:
Helge Fredriksen wrote:
Hey, got problems after doing the change in config +
$ make menuconfig $ make all $ make modules_install $ cp arch/i386/boot/bzImage /vmlinuz $ cp System.map /
Lilo loading CRUXEBDA is big; kernel setup stack overlaps LILO second stage........
OK, 2 questions. Does your lilo.conf point to your new kernel? Did you actually run lilo after you copied your kernel?
Joe
Please consider reading this article. http://www.xs4all.nl/~hanb/documents/quotingguide.html Helge Fredriksen wrote:
Nope, didn't know I had to do that...
No vmlinuz backup either I'm afraid. I guess I can fix this using my crux install CD?
Helge
On 1/2/07, Joe Gilmour <jgilmour@bigpond.net.au> wrote:
Helge Fredriksen wrote:
Hey, got problems after doing the change in config +
$ make menuconfig $ make all $ make modules_install $ cp arch/i386/boot/bzImage /vmlinuz $ cp System.map /
Lilo loading CRUXEBDA is big; kernel setup stack overlaps LILO second stage........
OK, 2 questions. Does your lilo.conf point to your new kernel? Did you actually run lilo after you copied your kernel?
Joe
Oops, This message was supposed to go off-list. # Han -- http://www.xs4all.nl/~hanb/software/crux/
Ok, fixed that problem. But still having problem with the network interface. Upon launching ./net start in /etc/rc.d I get these errors on standard out: SIOCSIFADDR: No such device eth0: unknown interface: No such device SIOCSIFNETMASK: No such device SIOCADDR: Network is unreachable Helge F.
OK, 2 questions. Does your lilo.conf point to your new kernel? Did you actually run lilo after you copied your kernel?
Joe
Helge Fredriksen wrote:
Ok, fixed that problem. But still having problem with the network interface.
Upon launching ./net start in /etc/rc.d I get these errors on standard out:
SIOCSIFADDR: No such device eth0: unknown interface: No such device SIOCSIFNETMASK: No such device SIOCADDR: Network is unreachable
Helge F. This message normally means that eth0 doesn't exist. When asking a question it would really help if you posted the relevant config/scrips/output e.g what does your rc.d/net look like? What is the output of ifconfig? If you compiled the natsemi module as a module did it load? What's the output of lsmod?
You can tell if the kernel you're running has the natsemi code available by looking at the subdirectories of /sys/module. HTH, Joe
Upon launching ./net start in /etc/rc.d I get these errors on standard
out:
SIOCSIFADDR: No such device eth0: unknown interface: No such device SIOCSIFNETMASK: No such device SIOCADDR: Network is unreachable
Helge F.
This message normally means that eth0 doesn't exist. When asking a
question it would really help if you posted the relevant config/scrips/output e.g what does your rc.d/net look like?
# more net #!/bin/sh # # /etc/rc.d/net: start/stop network # case $1 in start) /sbin/modprobe 3c59x /sbin/ifconfig lo 127.0.0.1 /sbin/ifconfig eth0 10.0.0.10 netmask 255.255.255.0 /sbin/route add default gw 10.0.0.138 # /sbin/dhcpcd eth0 ;; stop) # killall -q /sbin/dhcpcd /sbin/ifconfig eth0 down /sbin/ifconfig lo down ;; restart) $0 stop $0 start ;; *) echo "usage: $0 [start|stop|restart]" ;; esac # End of file # What is the output of ifconfig? ifconfig has only listing of the loopback device. 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. 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. Thanks, Helge F.
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
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.
participants (3)
-
Han Boetes -
Helge Fredriksen -
Joe Gilmour