[Solved] Not Bootable nor usable

Post in this forum for problems at boot time, if there was no problem for burning the disc. For example can't find the CD, or strange errors when you press enter at the very first prompt.
admin
Site Admin
Posts: 2715
Joined: 17 Jul 2003, 09:44

Not Bootable nor usable (isolinux boot problems)

Post by admin » 03 Mar 2007, 10:56

Thanks for your test. That's good news:

1) With the default image and "Determining root device..."
This is an expected error since I removed the big file in the ISO (sysrcd.dat) in order to make the ISO very small. We are only testing isolinux, not the whole startup system. For me, it means isolinux is working well with the default "rescuecd" image. When we are sur isolinux is working well, I will prepare a real ISO with all files, and we will make the real test.

2) nofb can't work since I removed most images in the first iso (testiso-20070303-08h56.iso). But in this iso, you can test fb800. You can test the second iso instead, since it has all the boot images (including nofb):
http://cdbeta.dupoux.org/testiso-20070303-09h19.iso

About invalid chars: I removed all the tabs in the text file. I had a look with an hexadecimal editor. This text file is formatted with unix end of lines, like in gentoo / knoppix configs. I really tested everything about invalid chars and I really don't think there can be remaining invalid chars.
Last edited by admin on 03 Mar 2007, 22:47, edited 1 time in total.

markmarques
Posts: 85
Joined: 26 Feb 2007, 12:30
Contact:

Post by markmarques » 03 Mar 2007, 11:20

well...
I do not why but this latest iso
did increased the number of "keyword" errors at startup...

So as I indicated earlier the labeled images did not work...:(

As expected it starts correctly until the root block device part after selecting the keymap...

So the error does invalidate the label selection.... :(

as an idea the "default rescuecd" should start something as plain as possible like nofb ...

I gave a look in the cfg file but I did not find anything that could explain this problem... :(

As the number of errors has increased , the new lines inserted have something (char, keyword) that contains the problem...
Is there any new line inserted that contains something diferent ?

I am using a CDRW so I do not have ther previous version.... :(

admin
Site Admin
Posts: 2715
Joined: 17 Jul 2003, 09:44

Post by admin » 03 Mar 2007, 11:25

What we can say:
- the default choice (enter or "rescuecd" + enter) is working well
- there is one error per choice after the default choice

I cannot see the invalid keyword, we will have to make other tests again to find it. I will try to find ideas about what to change, and I will post new ISO, if you have time.

Thanks

markmarques
Posts: 85
Joined: 26 Feb 2007, 12:30
Contact:

Post by markmarques » 03 Mar 2007, 11:48

After some more reading at the cfg file...
Perhaps we were looking at the wrong place....
Is it possible to check out for invalid chars at the F1.msg
or other files "*.msg" ?

For instance the error does invalidates both labels and the F keys ...

Just an idea... :)

Thanks

admin
Site Admin
Posts: 2715
Joined: 17 Jul 2003, 09:44

Post by admin » 03 Mar 2007, 12:31

Maybe you are right about the MSG files, could you test it:
http://cdbeta.dupoux.org/testiso-20070303-11h10.iso
(of course, all the messages printed on the screen are related to gentoo, please ignore it, and try with "rescuecd", "fb800", ...)

But in the the other hand, there are as many keywords errors as there are boot images. (there were 5 errors when there were 5 other boot choices, and many errors when there were more choices).

admin
Site Admin
Posts: 2715
Joined: 17 Jul 2003, 09:44

Post by admin » 03 Mar 2007, 22:27

I found several very interesting message about the "Unknown keyword in config file" problem there:

1) http://syslinux.zytor.com/archives/2006 ... 06784.html
I'm maintainer of a Live-CD and several users reported the problem:
| Unknown keyword in config file
| Could not find kernel image: grml
to me. The problem wasn't present with older isolinux versions (IIRC until 3.08), but with newer versions (including 3.11) it's present on several boxes. :-(
2) http://syslinux.zytor.com/archives/2006 ... 06586.html
This user had problems to boot Fedora Core 5 Test 3, based on isolinux-3.10. It worked for him with version 3.08:
I'm trying to boot Fedora Core 5 Test 3 from either CD or DVD, (which uses ISOLINUX), and I get the error messages:
Unknown keyword in config file
Could not find kernel image: linux
boot:
There are at least two other people in the world with the same problem. Unfortunately, all of the rest of the Fedora test community doesn't seem to have a problem with it, so its not a high profile issue with the Fedora development team.
...
3/ The media uses "ISOLINUX 3.10 2005-08-24"
4/ An older version of Fedora Core that uses "ISOLINUX 3.08 2005-05-19" works fine on the same hardware.
...
3) http://syslinux.zytor.com/archives/2006 ... 06609.html
So far I've got reports of this on:
eMachines T5026
Delphin Clevo 2700t (bios from SystemSoft according to DMI)
fujistu-siemens amilo L1300 (notebook)
Acer Aspire 2023WLMi
Since gentoo-2006.1 works for you, and it is based on isolinux-3.09, I suppose the problem appeared between versions 3.09 and 3.11. I decided to make a new ISO with isolinux downgraded from 3.36 to 3.09:
http://cdbeta.dupoux.org/testiso-20070303-21h01.iso

Could you test it ? (and you can also try the ISO with differents MSG files as you suggested, have a look at the previous post in this topic).

(We already tested with and old isolinux.bin but there was an old isolinux.cfg with kernel not yet renamed from vmlinuz1 to rescuecd.)

markmarques
Posts: 85
Joined: 26 Feb 2007, 12:30
Contact:

Post by markmarques » 05 Mar 2007, 09:30

I have tested the latest images with strange results...

The first (with only the gentoo msgs) worked flawlessly ... :)
Called the F keys and other images with any problem...

The secod one (downgraded 3.0X version) reported the usual "unknown keyword" 7 errors and no F1 nor acceptance of any other image .
So downgrading does not help...
The problem still exists at some point in the MSG files (probably) ...
Why does it only appears in certain machines (usually laptops ?) still no idea...

admin
Site Admin
Posts: 2715
Joined: 17 Jul 2003, 09:44

Post by admin » 05 Mar 2007, 09:45

Thanks for your test. We are close to fix it now, since we know it comes from the MSG files...

I will make new test ISO, in order to know that MSG has a problem. We need to do 4 tests, since there are 4 MSG files.

About laptops: only several computers have the problem because it depends on the BIOS, according to the posts I quoted in my previous post.

I will prepare the next test ISOs now.

admin
Site Admin
Posts: 2715
Joined: 17 Jul 2003, 09:44

Post by admin » 05 Mar 2007, 10:25

There a 4 message files (responsible for F1, F2, F3, F4), and each MSG use an image (LSS file).

The gentoo MSG files are working, and the original MSG files are not.
I prepared 4 ISO, in order to find which MSG file has a problem:

1) In the first: original-F1 and gentoo-F2-F3-F4
http://cdbeta.dupoux.org/testiso-200703 ... rig-F1.iso

2) In the first: original-F2 and gentoo-F1-F3-F4
http://cdbeta.dupoux.org/testiso-200703 ... rig-F2.iso

3) In the first: original-F3 and gentoo-F1-F2-F4
http://cdbeta.dupoux.org/testiso-200703 ... rig-F3.iso

4) In the first: original-F4 and gentoo-F1-F2-F3
http://cdbeta.dupoux.org/testiso-200703 ... rig-F4.iso

I hope we won't have to test LSS files (the picture files used by MSG)

Thanks.

markmarques
Posts: 85
Joined: 26 Feb 2007, 12:30
Contact:

Post by markmarques » 05 Mar 2007, 10:33

Tested the first Iso ( the one with F1) with about 11 errors "unknown Keyword in config file".
Noone F Keys available... :(
Could it be the lss image file ? ?
I suppose we could try that one out...
Without the boot image... just in case ...

admin
Site Admin
Posts: 2715
Joined: 17 Jul 2003, 09:44

Post by admin » 05 Mar 2007, 10:41

Interesting test...

I just prepared a new ISO without the LSS picture:
http://cdbeta.dupoux.org/testiso-200703 ... -nolss.iso

Thanks
Last edited by admin on 05 Mar 2007, 10:59, edited 2 times in total.

markmarques
Posts: 85
Joined: 26 Feb 2007, 12:30
Contact:

Post by markmarques » 05 Mar 2007, 10:54

Sucess ... :)
No Errors...

So we narrowed down all to the Lss file.... :)

Dumb question: How is created the lss file ?

My idea is that the lss file has an invalid char in HEX that crashes Isolinux...

Although I forgot to mention (did I already in the first post ?) that the image was garbled with erronous lines.

So if we discard the image part all is workable..

I can continue to debug the lss problem if needed ....

admin
Site Admin
Posts: 2715
Joined: 17 Jul 2003, 09:44

Post by admin » 05 Mar 2007, 10:58

Sorry, I made an error with this test. Could you test this image instead:
http://cdbeta.dupoux.org/testiso-200703 ... ix-lss.iso

In the previous test (testiso-20070305-09h22-orig-F1-nolss.iso), the success may be due to:
- the way I call LSS image from F1boot.MSG
- the LSS file itself

In this test (testiso-20070305-09h33-orig-with-knoppix-lss.iso), I kept all the original files, and I only replaced f1boot.lss with the picture from the knoppix cdrom that works on your computer.

If this test succeed, it mean I will have to create a new picture.

The LSS file is created with a script (lss16toppm) that converts a PPM picture. This perl script is provided with isolinux.zip

Thanks

markmarques
Posts: 85
Joined: 26 Feb 2007, 12:30
Contact:

Post by markmarques » 05 Mar 2007, 11:17

Tested with the knoppix image and
Strange thing....

The image is completly garbled ....
And got only 1 error ...
Although noone of the F Keys worked ...
I have here with me the knoppix CD and tested and realised that it only works with the default option ... :oops:
So no F keys nor boot image options..... :oops:
My fault .... :oops:

So in the first post I should have said that Knoppix did not worked perfectly...
Ok...
So lets continue....

It is settled that the problem is with the Lss file....
or a least with the Perl script that created it....

I still think that the lss file has 1 or more invalid chars inside, as interpreted by the isolinux exe....

admin
Site Admin
Posts: 2715
Joined: 17 Jul 2003, 09:44

Post by admin » 05 Mar 2007, 11:26

No problem, thanks for these details.

You said the gparted livecd works well. I just prepared a new ISO: I kept all original files, except I repalced the LSS with gparted.lss that is supposed to be working:
http://cdbeta.dupoux.org/testiso-200703 ... ed-lss.iso

Just to be sure this is really the LSS file itself, and not the way we use if from b1boot.msg

Thanks

Post Reply