Update Device Module (Driver) on Live CD
 

I currently use Linux for several jobs, one of them is imaging windows PC's. I normally use either RIPLinuX or Knoppix to boot up and then use ntfsclone. Problem is I just bought a bunch of Optiplex 755's and the old e1000.ko module doesn't work with the onboard nic. I did some searching and found the following thread:

http://www.linuxquestions.org/questi...tiplex+755+nic

This I'm sure would solve my problem, but I don't know how to install a module on a live CD. I never had to do this before. Can I simply boot up and use insmod/modprobe to install the updated module? Or do I have to create my own live CD with the module installed to do this?

Thanks in advance for any help you can provide.

1) I have not remaster knoppix but it has dox on howto but I have remastered rip and here is online doc...its also on the cd

http://ftp.cvut.cz/rip/docs/RIPLinux-1.8.readme

2) so follow those instructions or the latest off the cd...you can leave that new folder
/rip2 on your system or copy to usb etc

3) if this is the first time you attempt any remaster I suggest you use a cdrw or run the new iso in a emulator thingee....I strongly recommend virtualbox.

4) I have no read the module build instruction but when you create the new folder what you need to do is chroot into that folder and therefore you are using tools relative to rip and once you have built your module...relative to rip if the instruction does not already say so...run depmod -a ....then complete the repacking or remaster iso instructions

5) I am aware that when you test under vbox...you are using an emulated bios with emulated hardware so its not going to detect your net card....but it will at least prove the iso works so if you have no cdrw...you do not run the risk of creating a coaster.

good luck

I followed your instructions and the ones in the README file, however I haven't gotten very far. Every time I try and compile the source I get an error saying that the kernel source isn't found and I need to install the kernel development package. I tried running the make install both in chroot and non chroot.

I do have the kernel source downloaded (via apt-get install kernel-source) but it's the debian version since I'm running debian.

Do I need to download the latest from slack or kernel.org? Do I need to make any changes in the e1000 Makefile so it's pointing to the right directory for kernel files? Am I looking in the completely wrong direction? Keep in mind this is the first time I've ever had to remaster a live CD distro.

Thanks again for any help.

I am not sure which distro you are referring to so I split

a) if you mean rip...I have not recompiled that b4 ....just checked it in vbox and yep has no /usr/src/...so no kernel headers or source
b) have never attempted knoppix remaster...I have a cd edition 5.1.1
at /usr/src/knoppix-kernel.readme it says there is a config file on the dvd edition but to use the vanilla kernel

so no matter which distro you are talking about....
import into the rip or knoppix unpack....a full vanilla kernel

2) but this introduces a problem with the config file....please save that file elsewhere...the one from rip or knoppix....and study the filesystem format....live cds use things like cramfs unionfs

3) the bonus is by running a vanilla...I do on Mdv...there is already a e1000 available as per /linux-2.6.24.2/Documentation/networking/e1000.txt

4) but knoppix is already full....so me thinks you may be better off to copy your vanilla into rip first ....vanilla unpacked is about 350 Megs and my rip4 is 72 megs so you should be able to just leave the full vanilla on the the iso you are playing with.

from the rip link I posted
The replacement kernel must have this support builtin.

CONFIG_SHMEM=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_INITRD=y
CONFIG_ISO9660_FS=y
CONFIG_EXT2_FS=y
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y "MSDOS and/or VFAT for USB Flash drive access!"
CONFIG_VFAT_FS=y
CONFIG_PROC_FS=y
CONFIG_TMPFS=y

that link mentions slackware so maybe that is what you were referring to?

but by using a vanilla you can break any old blood bonds you have felt obliged to uphold.

ok here is the non-vanilla kernel config that rip uses
http://www.tux.org/pub/people/kent-r...ocs/kernel.txt

accordingly its already got
CONFIG_E1000=y

so you can use the same config if you need to compile a vanilla....but a vanilla will need more packages installed....so to be sure....I have rip version 4.3


what version with old e1000 of rip are you using?

leaping ahead...edition rip 4.3

after I chrooted into /rip2/

looking for kernel dependencies...not all but the main ones

bash-3.2# gcc --version
bash: gcc: command not found
bash-3.2# make --version
bash: make: command not found
bash-3.2# ld -v
bash: ld: command not found
bash-3.2# fdformat --version
bash: fdformat: command not found
bash-3.2# depmod -V
module-init-tools 3.4
bash-3.2# tune2fs
tune2fs 1.40.2 (12-Jul-2007)
bash-3.2# showmount --version
showmount for 1.1.1

and as per previous reference Kent uses slackware 12.0 packages.

pls use a mirror close to you...but here is a list of where packages are
http://mirror.internode.on.net/pub/s...ware/FILE_LIST

assuming you are going to run make menucofig...packages a d l seem a good place to start.

2) you may also need a good slackware based kernel compile guide. I no longer use slack so I will let you search for a specific one but I use
http://www.digitalhermit.com/linux/K...ild-HOWTO.html

I'm trying to compile a vanilla kernel because I figured it would be easier, but I'm having issues. Since I couldn't find and tgz files to install gcc and the rest of the tools needed I ran through the list of dependencies as you did on my debian system, I thought I could compile the kernel on it. Here is what I have installed:

I figured I would go ahead and try and run make menuconfig, and here is the errors I'm getting:

The Kernel I downloaded is linux-2.6.24.tar.gz & patch-2.6.24.4.gz. I followed the README file included with the kernel to install the patch.

Thanks again for your help aus9.

--Update--

OK, I think I figured out part of my problem. I did a quick google search and found the following:
http://forum.kernelnewbies.org/read.php?10,18,18

It looked like the same issues I was having so I installed the debian build-essential package and then tried make menuconfig. Here is what happened:

It seems to let me get a little farther. Am I missing other packages? Thanks!


----Another Update----


OK, I think I got the dependencies figured out. I found another thread:
http://forums.debian.net/viewtopic.p...625080b6b1f2ac
And the post at the bottom simply says:
I installed this and now it works! I can get into make menuconfig no problem. However, I am getting some errors fly across the screen before the menuconfig opens:

It's obviously trying to use the config for my debian kernel. Is there a way for me to change this or do I even have to worry about it?

1) I ran through the list of dependencies......yes but we are trying to build it in a chroot environment on an unpacked rip live cd.

unless you are trying to tell me you have never done a vanilla b4...in which case you would be wise to try building one to test on your real hardware.

But its still going to be a different build than rip due to its structure and I still think it would be wise to test the iso image in an emulator such as virtual box


EDIT found a nice slack howto
http://www.slackbook.org/html/system...KERNEL-COMPILE


2) I need to repeat my earlier question...what edition of rip are you using pls?

now I am thinking ahead.

assuming your answer is 4.3 live cd....I will attempt a vanilla install as well. But if you would like me to do that....I need your assistance....I am not going to make an iso image and get into trouble with GPL police because I can not at my online storage host his source. Instead if I succeed...I will only link to a kernel and initrd for your consideration.

If you wish to parallel build please do so.

To signify you want help pls upload the results of your lspci > /home/name/pci.txt to an online storage....if you have none pls consider using www.ripway.com

2) further to your consent....can you provide a link to all hardware that is troublesome for rip so I can check it.

3) this might sound legalese...disclaimer that altho my final vanilla kernel...if posted....works in a vbox....that does not guarantee it will work with your hw.

and please be patient.

4) even if you do not agree....I will at least try to give you the names of the slack packages...and yes I should have mentioned ncurses-devel if you use make menuconfig

I realise this post will be rude to some....but I prefer to be bluntly honest so I am as transparent as possible.

I do not want to do it just for you.....so it will be to try and help others in a similar situation.

let me know if you understood any of this pls

well some success and some failure

1) use the unpack live cd ..../doc/contents.txt to see what you have.

2) the old link to kernel rebuild named pcmcia-cs but its now called pcmciautils
EDIT
command to check is
pccardctl -V

3) have not found libncurses-devel....the contents shows ncurses is installed but we need the dev package to use make menuconfig.

4) I tried a number of times here with no luck
http://packages.slackware.it/

I tried libncurses-devel libncurses ncurses-devel ncurses ....I got some hits but not for the dev package

4) Generally speaking I downloaded other packages which are tgz....moved them to the unpack folder but I created a new folder
/rip2/boot/1/slack then I chrooted into /rip2/boot/1/ then cd to slack

then run commands
installpkg (package name)

5) I am aware you can do them all at once but I was also running a verification command as per kernel rebuild link from post 8

I have hit a wall (ok it was human but they are not groaning much now)

its got me beat...this libncurses-devel.

so time to abandon ship?

would you consider d/loading a recent live cd that has k 2.6.24.4?
http://distrowatch.com/table.php?distribution=slax

yes I know its not based on Debian but they are not yet released AFAIK thru a search of distrowatch for the most recent kernel.

slax dox suggests it all modular so you can whip in and whip out whatever you like...but I am hoping to go for a simple solution as my slackware braincells have faded in time.

thanks for any patience you have left in me

I'm using RIPLinuX 4.3. I tried to compile in the chroot environment but didn't have much luck trying to find all the packages in the .tgz format. So thats when I decided to try and compile the kernel on my debian box. I'm hoping I can simply build the kernel, replace the existing kernel and it will boot. We'll see.


---- Update ----

OK, I downloaded RIPLinuX 4.4 and tried it, no dice. I've also tried building my own kernel twice, each time I get an error that says kernel is corrupt or missing (RIP 4.3 iso). I made sure to follow the directions givin by the readme file. I'm sure I'm just missing something stupid. Is there anything I can post from my build that would help? Is there a way to pull up the kernel config that Rip 4.4 uses and put it in the 2.6.24.4 kernel I'm trying to build?

I'm going to go ahead with your suggestion and try slax, I'll let you know if it works. In the mean time if any one else can provide input aus9 and I would appreciate it!

Thanks again aus9 for your help. This so far has been quite a challenge for both of us.