On Thursday, Mar 31, 2005, at 11:01 US/Central, Rex Nelson wrote:
The first factor is the kernel and how it was compiled. If it was compiled with a lot of modules such as the network modules then you cannot escape it.
The second factor is the Ram Disk and what it was set up to load. If it was set up to load the network, you are also SOL.
The last factor is/are the modules that get loaded at the end. This can be changed.
I discovered I can boot Koppix with the 2.6 kernel using this:
knoppix26 init=/bin/bash
All this does is load the kernel and start a bash shell. No startup scripts are run. In addition, I can load the module for the card with 'modprobe de4x5', which is the module the 2.4 kernel uses. lsmod shows that the module loaded and 'ifconfig -a' shows I have an interface eth0. However, the system freezes when I do a 'pump -i eth0'. It also freezes when I type 'ifconfig eth0 192.168.10.10 netmask 255.255.255.0'
Could be that Knoppix is loading the wrong module. When I boot Debian/Sarge, it uses the de2104x module.
In short, VPC can boot Knoppix with the 2.6 kernel, but seems to load the wrong network module. This is why it would be nice to boot Knoppix in a minimalist mode, load the correct module manually, and then continue into a full Knoppix graphical session. Or is there a way to specify the correct NIC module at the boot prompt?
Regards, - Robert http://www.cwelug.org/downloads Help others get OpenSource software. Distribute FLOSS for Windows, Linux, *BSD, and MacOS X with BitTorrent
_______________________________________________
CWE-LUG mailing list
http://www.cwelug.org/ [email protected]
http://lists.firepipe.net/listinfo/cwe-lug
