Guide to installing Knoppix 3.4ct with 2.6 kernel
I sucessfully installed to HD the 3.4 ct version with the 2.6 kernel thanks largely to a thread in the "News" section and the wisdom and kindness of Stephen and champagnemojo who posted tips on how to get it to install. As somewhat of a novice myself, I felt it would be nice to put together an installation guide for how to get a HD install of Knoppix 3.4ct up and running with the 2.6 kernel, so here goes:
- boot the Knoppix Live CD (as the keyboard layout is German by default you'll need to use shift and 0 to get the = sign).
- once in KDE on the live CD open konsole and issue the following commands:
this will install the needed missing files, as well it will start the knoppix installation to your HD
- (I used /dev/hda3 so that's the reference point for example i'll use from here on out, please subsititute /dev/hda3 for whatever slice or HD you used). After Knoppix has been sucessfully installed to your HD you'll need to mount the drive you installed. and to save yourself a lot of headache later it's a good idea to download module-init-tools at this point too.
the sudo wget command with the URL following it is all on the same line, not two seperate lines, fyi.
- now that you've got that downloaded, just leave it there, you'll come back to install it later. As for now lilo on your installation drive needs to be updated.
Code:
sudo chroot /mnt/hda3/ /sbin/lilo -v
once this has updated you're ready to reboot and take the CD, go ahead and do this.
- At lilo's boot menu select LinuxOLD (if you boot into linux you get kernel panic errors). Don't be surprised like I was when LinuxOLD boots up and your mouse/network card, etc might not be functioning. We're just botting into linuxOLD to do some text based maintence work. When KDE starts loading go ahead and kill it and drop to console:
Code:
Cntrl-Alt-F1
(log on)
su
Password:
cd /boot
mkinitrd -o linux-2.6.1.gz
this will make an initrd image that WON'T cause a kernel panic when you try to boot into it normally.
- now it's time to add this entry to /etc/lilo.conf. Update /etc/lilo.conf as follows (I used vi but feel free to use the editor of your choice)
you'll come to a section looking something like this:
Code:
image=/boot/vmlinuz-2.6.1
label=Linux
initrd=/boot/initrd.gz
replace the last line (initrd=/boot/initrd.gz) with the one you created earlier:
Code:
initrd=/boot/linux-2.6.1.gz
- you'll need to update lilo again for it to recognize the change you just made, so issue the following command:
- Some last minute prep work we have to do now. remember the module-init-tools package you downloaded earlier? Well now it's time to install it so that your mouse, network card, sound card, etc. will be recognized when you reboot:
Code:
dpkg -i module-init-tools_3.0-pre9-1_i386.deb
- one last thing that needs to be done is to add an entry into /etc/fstab that the 2.6 kernel requires:
add the following lines to the file
Code:
## Needed for kernel 2.6
none /sys sysfs defaults 0 0
save the file, and then you're all set!
- you should now just have to reboot your computer, and choose Linux from lilo's boot menu, and voila you're up and running with the 2.6 kernel
Steps still required on 3.4 disto dated 2004-05-04 ?
Are the steps mentioned in the posts here still required for the recent Knoppix 3.4 iso files ?
I still get the kernel panics, but wasn't sure the workarounds listed here should still be required to get going in 2.6 kernel.
Tx, cheers de Mark @ 7tronics
changing kernel boot default in lilo.conf?
This is probably a simple fix, but I want to have linux 2.6.5 be the default booting kernel in lilo at startup. If I don't arrow down to linux 2.6.5 in my boot loader, it will default to 2.4. after 5 seconds.
Here's the part of my lilo.conf which I think changes the boot order:
__________________________________________________
...
...
# append=""
# Boot up Linux by default.
#
default="Linux"
image=/boot/vmlinuz
label="Linux"
initrd=/boot/initrd.img
append="ramdisk_size=100000 init=/etc/init lang=us apm=power-off nomce noscsi screen=1280x1024"
read-only
image=/boot/vmlinuz-2.4.26
label="Linux(2.4)-1"
initrd=/boot/initrd.img-2.4.26
append="ramdisk_size=100000 init=/etc/init lang=us apm=power-off nomce noscsi screen=1280x1024"
read-only
image=/boot/vmlinuz-2.6.5
label="Linux(2.6)-2"
initrd=/boot/initrd.img-2.6.5
append="ramdisk_size=100000 init=/etc/init lang=us apm=power-off nomce noscsi screen=1280x1024"
read-only
______________________________________________
I tried changing the line default="Linux"
to default="Linux(2.6)-2"
but that didn't help during boot. I would think that I need to change this line to the 'label' of the image I want, but it didn't work. Do I need to do additional changes in initrd?
Also, once I've succesfully changed the boot order, I'd like to change the timeout to 2 seconds.
Thanks for any help
Re: Guide to installing Knoppix 3.4ct with 2.6 kernel
Quote:
Originally Posted by Hayabusa
I sucessfully installed to HD the 3.4 ct version with the 2.6 kernel thanks largely to a thread in the "News" section and the wisdom and kindness of Stephen and champagnemojo who posted tips on how to get it to install.
Let me know if the following is covered somewhere else, but...
The 3.4 May 10th release does not recognize my Linksys WUSB V2.8 wireless device. Since it is hooked up to a desktop, and the system is upstairs, I'd like to avoid having to carry everything up and down to get Knoppix going.
I installed to the HD using the recommended option, and got a nice Debian system. However, the source for the kernel is mislinked (everything points to the 2.4 stuff even though booting into 2.6), and so I am unable to compile the Atmel drivers from Berlios to enable the network card.
Reading your step by step here, it would appear that if I DL'd a few tgz and deb files on a different machine and burn them to a CD that I might be able to get a kernel setup that would allow me to compile the Atmel drivers. Can I just DL the files that you are wget'ing in your article? Any particular place they need to be copied to? Anything else I need that you didn't since your connection was live?
Thanks,
Ewan Grantham