Booting Knoppix4.0.2 from DOS

**hobz** · 01-02-2006, 10:01 AM

Ok Now
I have overcomed the last fault by specifying root=/dev/hda1

My command no is loadlin linux init=/etc/init acpi=off noscsi root=/dev/hda1

I get a new error
kernel panic no syncing no init defined try passing init= option to kernel
(6)input: at translated set 2 keyboard on isa0060/serio0
logips2pp:detected unknown logitech mouse model 0
input IMPS/2logitech Wheel mouse on isa0060/serio4
input AT translated set 2 keyboard on isa0060/serio0

and it hangs.

**ruymbeke** · 01-02-2006, 11:07 AM

Originally Posted by hobz

I have added acpi=off to the command then I got
kernel panic: no syncing:vfs unable to mount root from unknown block (1-3)

Are you using grub or lilo ? (lilo has a very ennoying command line length limitation)
Where is the knoppix iso file ? did you rename it ? did you update the bootfrom= path cheatcode to point to it ?
Gilles

**hobz** · 01-02-2006, 12:17 PM

knoppix iso file in d:/knoppix/boot/knoppix-204 or /dev/hda5/knoppix/boot/knoppix-204 it goes there and starts booting sequence
I think this way I am not using grub or lilo
I am just typing loadlin linux .blablabla
grub.exe is in the same directory as knoppix.iso and loadlin
but when I tried it , it searches menu.lst and itcan't find it even it is there

**ruymbeke** · 01-02-2006, 01:10 PM

Originally Posted by hobz

knoppix iso file in d:/knoppix/boot/knoppix-204 or /dev/hda5/knoppix/boot/knoppix-204 it goes there and starts booting sequence

In my setup I have all the 3 knoppix boot files in the /boot/knoppix.402 directory:
the "linux" kernel, the "minirt_usb2.gz" boot ramdisk, and the KNOPPIX_V4.0.2CD-2005-09-23-EN.iso cd iso image file,
the location of these files has to match the kernel boot cheatcode: bootfrom=/dev/hda1/boot/knoppix.402/*.iso
Please note the *.iso (iso lowercase) and the KNOPPIX_V4.0.2CD-2005-09-23-EN.iso (iso lowercase)
With linux and a boot ramdisk you can already get the boot sequence to start,
but only a correct setup and the proper boot ramdisk will allow you to get Knoppix to finich the boot properly.

Originally Posted by hobz

I think this way I am not using grub or lilo I am just typing loadlin linux .blablabla

loadlin.exe is a DOS port of the lilo boot loader and has a command line lenght limitation.
I would recommend to use grub.exe instead (which require to not have emm386 loaded)
Grub has an interactive mode (c) and an edit mode (e) for fine setup which i find very useful.

Originally Posted by hobz

grub.exe is in the same directory as knoppix.iso and loadlin but when I tried it,
it searches menu.lst and itcan't find it even it is there

You have to tell grub where to find the menu.lst file using a command line as follow:
grub.exe --config-file=(hd0,0)/boot/grub/menu.lst
assuming that the menu.lst file is in the /boot/grub directory of the first partition of the first disk drive.
You should modify my menu.lst to match your needs, or something as follow:
title Knoppix 4.02 from ISO
kernel (hd0,0)/boot/knoppix.402/linux ramdisk_size=100000 init=/etc/init bootfrom=/dev/hda1/boot/knoppix.402/*.iso vga=791 noprompt apm=power-off nomce quiet lang=us dma
initrd (hd0,0)/boot/knoppix.402/minirt_usb2.gz
boot
Please note that: (hd0,0) --> hda1, (hd0,1) --> hda2, (hd1,0) --> hdb1, (hd3,4) --> hdd5, ...

**hobz** · 01-02-2006, 03:26 PM

Ok fine
finally able to start booting through grub
I see the linux pinguin at the top left
at the start i see a new error
can't find knoppix file system sorry dropping you to a very limited shell

the command is
kernel (hd0,0)/knoppix/boot/knoppix.402/linux ramdisk_size=100000 init=/etc/init bootfrom=/dev/hda5/knoppix/boot/knoppix-402/knoppix.iso vga=791 noprompt apm=power-off nomce quiet lang=us nodma
initrd (hd0,0)/knoppix/boot/knoppix.402/minirt_usb2.gz
boot

**ruymbeke** · 01-02-2006, 07:04 PM

Originally Posted by hobz

Ok fine
finally able to start booting through grub
I see the linux pinguin at the top left
at the start i see a new error
can't find knoppix file system sorry dropping you to a very limited shell

Knoppix did not find the iso cd image file, because the bootfrom kernel cheatcode
do not match the path where the iso cd image file is stored.
Please follow what I wrote in my previous post.
Gilles

**hobz** · 01-02-2006, 10:11 PM

In my setup I have all the 3 knoppix boot files in the /knoppix/boot/knoppix-402 directory: inside partition d: or /dev/hda5 or (HD0,4)
the linux kernel, the minirt.gz boot ramdisk, and the knoppix.iso cd iso image file,
kernel boot cheatcode: bootfrom=/dev/hda5/knoppix/boot/knoppix-402/knoppix.iso

this is my setup

**ruymbeke** · 01-02-2006, 11:16 PM

Originally Posted by hobz

In my setup I have all the 3 knoppix boot files in the /knoppix/boot/knoppix-402 directory: inside partition d: or /dev/hda5 or (HD0,4)
the linux kernel, the minirt.gz boot ramdisk, and the knoppix.iso cd iso image file,
kernel boot cheatcode: bootfrom=/dev/hda5/knoppix/boot/knoppix-402/knoppix.iso
this is my setup

Did you use my minirt_usb2.gz boot ramdisk ? Or the minirt.gz file off the cd ?
The minirt.gz boot ramdisk off ce CD cannot boot from an ISO file, which is one of the reasons for my minirt_usb2.gz update.
Gilles

**hobz** · 01-03-2006, 06:34 AM

In fact I was using the one in the cd
when I saw the minirt_usb.gz , I thought it is related to booting from usb & not hard drive
so u are suggesting that it must be used
I will do and feed you back

**ruymbeke** · 01-03-2006, 09:39 AM

Originally Posted by hobz

In fact I was using the one in the cd
when I saw the minirt_usb.gz , I thought it is related to booting from usb & not hard drive
so u are suggesting that it must be used
I will do and feed you back

Correct.
The minirt_usb2.gz boot ramdisk includes quite a few features not available from the minirt.gz off the cd.
Firts, it will allow you to boot Knoppix from an ISO file located on fat12/16/32, ext2/3 or reiser partition (ntfs and reiser added).
In case of a wrong devive name, the boot script will automatically search for an other working device with the same directory path,
boot from it, and suggest you to update your kernel boot command line with the working device. (bootfrom=)
Then, it will allow you to change the hostname of the machine with a fixed or dynamic name (network_hw_address or time)
and has a bug fix for using the USB2.0 kernel module on USB2.0 hardware (instead of always using the slow USB1 kernel module).
I changed the name of the boot ramdisks with the new features added over time which may be a little confusing,
but all the previous added features are still included in the new update.
As an exaple, the minirt_usb2.gz adds usb2 support to the previous iso boot, ntfs, reiser, auto search, and hostname features.
Gilles