PDA

View Full Version : Booting Knoppix4.0.2 from DOS



hobz
01-01-2006, 04:34 PM
Hi all
I am trying to boot Knoppix 4.0.2 from Dos
I did the following
create Folder in E: called Knoppix
put knoppix .iso inside with initrd.tgz minirt.gz and a file called linux with loadlin
I go to e:/knoppix I type loadlin linux + some other options I get
invalid compressed format (err2)

Any Idea

ruymbeke
01-01-2006, 05:15 PM
Hi all
I am trying to boot Knoppix 4.0.2 from Dos
I did the following
create Folder in E: called Knoppix
put knoppix .iso inside with initrd.tgz minirt.gz and a file called linux with loadlin
I go to e:/knoppix I type loadlin linux + some other options I get
invalid compressed format (err2)
Any Idea
I did it from a DOS bootable USB dongle using both lilo and grub, check in here:
http://s94002264.onlinehome.us/grub/usb_dgle4.zip
The key piece is the new minirt ramdisk boot file: minirt_usb2.gz
which is required to boot from an iso cd image file (double loop back):
http://s94002264.onlinehome.us/grub/minirt_usb2.gz
For more info and updates please have a look at this thread:
http://www.knoppix.net/forum/viewtopic.php?p=93758#93758
Cheers,
Gilles

hobz
01-01-2006, 05:38 PM
I will go ahead and read it but I don't think it will help
as I am having and old bios that does not support booting from USB

ruymbeke
01-01-2006, 06:32 PM
I will go ahead and read it but I don't think it will help
as I am having and old bios that does not support booting from USB
I am not sure you have understood how I was trying to help you.
I used DOS to boot from my USB dongle and from DOS I boot Knoppix from the ISO.
In your case, since you already have your computer booting DOS,
you only need to get the second part which is to get Knoppix to boot from the iso file using DOS.
So to get that done, you can use the second part of my setup:
You will need to use at least my minirt_usb2.gz for the iso boot
and modify your configuration files, menu.lst for grub, or the bat file you use to launch lilo.
To achieve this, please get inspired by the configuration files I used in my USB boot setup.
Good luck,
Gilles

hobz
01-01-2006, 07:05 PM
Thanks
I realized this after an indepth reading
I will try to execute the steps and feed you back

hobz
01-01-2006, 08:03 PM
I see in GRUB only supports USB and NTFS what about fat what subdir I an use for this sorry if my question seems silly

ruymbeke
01-02-2006, 02:38 AM
I see in GRUB only supports USB and NTFS what about fat what subdir I an use for this sorry if my question seems silly
Both this version of grub & my minirt_usb2.gz actually supports most file systems, including fat/12/16/32, ntfs, ext2/3 and reiser.
Follow what I have done on my USB setup as for the config files and where to store them.
Gilles

hobz
01-02-2006, 08:33 AM
wow
It started booting
But it hangs in th middle at
acpi setting ELCR to 0200 from (0420)
what cheat code shuld i add to the start command line ?

ruymbeke
01-02-2006, 09:27 AM
wow
It started booting
But it hangs in th middle at
acpi setting ELCR to 0200 from (0420)
what cheat code shuld i add to the start command line ?
From the knoppix-cheatcodes.txt file, you can read:
In case of a failing hardware autodetection, try booting with any of
the "no-" options as shown in the table above, like in
knoppix noagp noaudio noapm noapic acpi=off nodma nopcmcia noscsi nousb
to skip some critical parts of the autodetection system.
In your case, I would try acpi=off first, then noapic and nolapic ...
Good Luck,
Gilles

hobz
01-02-2006, 09:36 AM
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)

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
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
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.


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.


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
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
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
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

mikekgr
01-03-2006, 02:47 PM
Dear ruymbeke,
I follow your steps and now I can boot my 1G usb2 ext. usb stick.

Thanks a lot

Best Regards,
Mike Kranidis.

P.S. what is the filesystem of the loop file minirt_usb2 ??? I tried to mount (after decompretion) using mount -o loop ./minirt_usb2 /mnt/test but it was unsuccessfully can you guess why??

hobz
01-03-2006, 06:53 PM
Thanks
great it works
Iwill try it to see if we are having problems with discs to be read write and wireless lan card which is not dicovered

ruymbeke
01-03-2006, 09:18 PM
P.S. what is the filesystem of the loop file minirt_usb2 ??? I tried to mount (after decompretion) using mount -o loop ./minirt_usb2 /mnt/test but it was unsuccessfully can you guess why??
I mount it this way. It should work...
Are you super user when running the mount ?
It should not matter, but I copy first the minirt_usb2.gz file in the knoppix directory and also mount it in the knoppix directory using:
mount -o loop minirt_usb2 toto
Gilles

hobz
01-03-2006, 09:40 PM
Ok
C: & E: are mounted on /mnt/hda1 /mnt/hda5 Read and write I see the 3 partitions on desktop
but on clicking D: or /dev/hda5 it is read only
when I click it konqueror opens but i don see /dev/hda5 I see /cdrom2.loop
in my cheat code I am putting root=/dev/hda1 !!! could this be a problem
wirless lan works now
Thanks a million

ruymbeke
01-03-2006, 10:04 PM
Ok
C: & E: are mounted on /mnt/hda1 /mnt/hda5 Read and write I see the 3 partitions on desktop
but on clicking D: or /dev/hda5 it is read only
when I click it konqueror opens but i don see /dev/hda5 I see /cdrom2.loop
in my cheat code I am putting root=/dev/hda1 !!! could this be a problem
wirless lan works now
Thanks a million
I am a little bit confused, what is D: since hda5 is already E ?
Anyway, if you enter the wrong device in the bootfrom= kernel command line, my linuxrc boot scipt (within the minirt_usb2.gz)
will automatically search for an other device where the iso file is located using the same directory path.
If you look carefully at the text written on the screen, you should notice that the iso file is not found where expected
but in an other device and the text should suggest you to correct the kernel command bootfrom= cheatcode
with the correct device which has been used to complete the boot.
Now, since the partition containing the iso file is mounted at a very early stage by the linuxrc boot script
in order to mount the Knoppix root file system and complete the Knoppix boot, this boot partition is mounted by default
as read only and as /cdrom2.loop. You can remount this partition as writable (but I would not do that on a ntfs partition though)
by using the following command line: mount -f -o remount,rw /cdrom2.loop
But it probably unnecessary to tell you not to delete or move the Knoppix iso cd image file...
Cheers,
Gilles

hobz
01-03-2006, 10:39 PM
this command works for root only
what should I add for all users & what is -f

Thanks for supporting me the last 2 days

ruymbeke
01-03-2006, 10:52 PM
this command works for root only. what should I add for all users & what is -f
Thanks for supporting me the last 2 days
Is sudo acceptable for you ? (to be run as a user) ==> sudo mount -f -o remount,rw /cdrom2.loop
-f means force (try: man mount to read more bout it).
You need that because the /cdrom2.loop device is already in use (but in read only mode) at the time you run the (re)mount.
My pleasure,
Gilles

hobz
01-05-2006, 03:20 PM
My next challenge
My PC at work it is an NTFS with a sata hard drive
I got ntfsdos
it mounts the partitions
in grub.bat
I have the command:
grub.exe --config-file(sd0,4)/knoppix/menu.lst
I there somthing wrong with this (sd0 ?????
it can't find menu .list

ruymbeke
01-05-2006, 06:30 PM
My next challenge
My PC at work it is an NTFS with a sata hard drive
I got ntfsdos
it mounts the partitions
in grub.bat
I have the command:
grub.exe --config-file(sd0,4)/knoppix/menu.lst
I there somthing wrong with this (sd0 ?????
it can't find menu .list
Grub do not use the linux syntax. You have to use (hdx,y).
The best way to check what should be used, is to start grub
and from the command line prompt (c key) use the grub autocompletion (by using the tab key):
type something as "root (hd[tab key]" and grub will list all the disk available.
then if you select the first disk drive: "root (hd0,[tab key]", grub wil list
all the partitions and the partition types availbale on the first disk drive.
This should help you to figure out the path for the menu.lst.
If you type the [tan key] at the prompt you will have a list of the commands.
The grub command line shell is really a nice feature for debugging your setup.
Cheers,
Gilles

PS: did sudo worked for you ? I would apreciate some feedback before moving to the next topic ...

hobz
01-05-2006, 07:48 PM
I get this message when trying to save any file as a normal user

The document could not be saved, as it was not possible to write to file:///cdrom2.loop/bios.txt.
Check that you have write access to this file or that enough disk space is available.

even when I try putting rw switch
chmod 777cdrom2.loop does not work even as root

ruymbeke
01-05-2006, 08:25 PM
I get this message when trying to save any file as a normal user
The document could not be saved, as it was not possible to write to file:///cdrom2.loop/bios.txt.
Check that you have write access to this file or that enough disk space is available.
even when I try putting rw switch
chmod 777cdrom2.loop does not work even as root
I am not sure to understand what this relates to...
A little bit of context and feedback on my previous answers will be apreciated.

If the cdrom2.loop partition device is not NTFS and you got write access granted
to the partition using the mount -f -o remount,rw ... it shoudl work....
Gilles

hobz
01-05-2006, 09:47 PM
Yes it works
but only if i am editin files as root user
I need to ty su before kwrite for instance

cvevans
08-28-2006, 06:26 AM
I don't know if anyone else still cares about this thread, but as I just found it,
I'll add my 2c.

1. only root can write:
Knop4 always does this (only root can write) to the partition with the .iso on it.
you will find that booting from a CD you can write to it.
If you have more than one partition, the others will write fine.

2. .iso filenames:
I found that my Knop4 knx.iso would never be found unless I did
bootfrom=/hda1/KNX.iso
perhaps 4.iso would be less troublesome

ruymbeke
08-28-2006, 07:30 AM
...perhaps 4.iso would be less troublesome
This is the reason for the "bootfrom=.../*.iso" in my menu.lst
My 2 cts,
Gilles

cvevans
09-01-2006, 02:26 AM
I also have 5.iso for Knoppix 5 on the same partition;
Is there any way to multiboot Knop4 & 5 with no CD?

ruymbeke
09-01-2006, 07:38 AM
I also have 5.iso for Knoppix 5 on the same partition;
Is there any way to multiboot Knop4 & 5 with no CD?
Yes of course, I have 5 iso boots on my laptop... Knoppix 4 & 5, Kanotix, accelerated knoppix, ...
Just use different path and/or filenames for the various versions of set of files (kernel, ramdisk and iso)
BTW, the iso file do not need to be called iso, you could rename it with only a letter to avoid
the upper/lower case problem then just use "bootfrom=.../5" in your menu.lst
My 2 cts,
Gilles