[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

Post by admin » 28 Feb 2007, 12:42

I am really out of idea for the moment... I will post a message if I have a new idea about what to test.

I fixed the typo in the splash screen, thanks

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

Post by markmarques » 28 Feb 2007, 13:04

An idea:
I have seen that the startup text appears always correct.

Why do not write a full config line example on it ?

Something like "example: boot: vmlinuz1 root=/dev/ram0 initrd=vmlinuz1.igz" ?
For instance the line corresponding to the "nofb" option or even to the text only mode...
So if by some reason something fails the boot process could be continued.

The strangest thing is that Knoppix LiveCD (5.1.1) also reports only one and the same error but allows to continue...
Meaning that the same error is present but in a different place in the config file.

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

Post by admin » 28 Feb 2007, 13:18

I think it would be easier and faster if I give you the way to edit isolinux.cfg:

You will need to run these commands from a working linux system with cdrtools installed:

1) Mount sysresccd-0.3.3-rc2 to /mnt/cdrom
2) Create a temp directory:
mkdir /root/TESTS
3) Copy all files:
cp -a /mnt/cdrom /root/TESTS
4) edit /root/TESTS/cdrom/isolinux/isolinux.cfg
5) cd /root/TESTS/
6) mkisofs -J -R -l -V testiso -o /root/TESTS/testiso.iso -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table /root/TESTS/cdrom

And you have the final iso in /root/TESTS/testiso.iso

Thanks

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

Post by admin » 28 Feb 2007, 19:52

I am looking at the syslinux mailing list. Maybe we can find the same kind of problem:
http://www.gossamer-threads.com/lists/syslinux/users/

burdicda
Posts: 3
Joined: 01 Mar 2007, 18:12
Location: Melbourne, Fl
Contact:

Good thing I kept my 0.3.1 whew !!!

Post by burdicda » 01 Mar 2007, 18:19

Not bootable
Not useable in anyway
like others in here I get the same config file problem on boot attempt

something about fb800

and when I typed in the exact line someone else said worked for them
it goes into an infinite loop repeating the same error message over
and over again forever .....

i am running an HP P4 with 512ram 40g hd
model zt1195

runs all other distros ive tried and boots gparted 3.3.7 perfectly
as well as knoppix 5.1

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

Post by admin » 01 Mar 2007, 19:47

Hi burdicda,

Since I have no way to reproduce the bug, I will need you to make several tests for me, sorry.

I had new ideas about what to change. I decided to completely rewrite the isolinux.cfg. I took a working gentoo livecd-2006.1 and only changed several lines in the isolinux.cfg.

Could you test this ISO, and tell me the exact error message if you have one.
The only working is fb800 (or just press enter). I removed all other possible choices (to keep isolinux.cfg close to the gentoo version):
http://cdbeta.dupoux.org/testiso-20070301-18h20.iso

Of course, the system will not be able to boot, since I removed sysrcd.dat in order to make this ISO file as small as possible, to make test easier. I just want to know if you have an isolinux error ("no image found" for example) or if the kernel is starting well, as on this screenshot:
http://cdbeta.dupoux.org/loading-kernel.png

If the first ISO is working, could you try this one: (I added fb640, fb1024, ...)
http://cdbeta.dupoux.org/testiso-20070301-18h43.iso

Thanks

burdicda
Posts: 3
Joined: 01 Mar 2007, 18:12
Location: Melbourne, Fl
Contact:

OK

Post by burdicda » 02 Mar 2007, 03:05

Didn't bring my laptop home with me tonight but just downloaded both
your test iso's and will give er a whirl first thing tommorrow morning.

and let you know

we can work this thing out ....

tnx

Burdicda

burdicda
Posts: 3
Joined: 01 Mar 2007, 18:12
Location: Melbourne, Fl
Contact:

Feedback1

Post by burdicda » 02 Mar 2007, 11:54

Could you test this ISO, and tell me the exact error message if you have one.
The only working is fb800 (or just press enter). I removed all other possible choices (to keep isolinux.cfg close to the gentoo version):
http://cdbeta.dupoux.org/testiso-20070301-18h20.iso

"Unknown keyword in config file."
then I entered "fb800" and hit enter
and it replied back "Could not find kernel image: fb800"


On the 2nd iso -18h43

Same exact responses as the first iso ....

Burdicda

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

Post by markmarques » 02 Mar 2007, 12:08

I tried both latest test images and confirm the results ...
still : "unknown keyword in config file"...:(

It seems the problem is related to Notebooks / laptops only ...
Although I didnt execute the latest instructions due to time constraints... :(
I will try to make them during the weekend...
and help a bit more :)

thanks

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

Post by admin » 02 Mar 2007, 14:16

Thanks for your tests. I have a new idea. In the working gentoo config file, "gentoo" is both the default boot name, and the name of the kernel file (usually vmlinuz, and vmlinuz1 in sysresccd).

I made a new image, with the following properties:
I renamed vmlinuz1 to rescuecd
The default choice is rescuecd
I hope we are close to the solution.

You can download this image from this url:
http://cdbeta.dupoux.org/testiso-20070302-12h54.iso

And if the first ISO works, could you test this one with the full config file:
http://cdbeta.dupoux.org/testiso-20070302-13h11.iso

You can try to boot both ISO different ways:
- just press enter
- type rescuecd + enter
- type fb800 + enter

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

Post by markmarques » 03 Mar 2007, 09:13

I tried the latest isos "testiso-20070302-12h54.iso" and "testiso-20070302-13h11.iso" both still with the same problem.
Although both images did continue booting with the single "Enter", they ended up with an loop regarding "atkbd.c: Spurious ACK in isa0060/Serio0.Some program might be trying to access hardware directly." and keep looping with no exit.

After some reading I am seeing something "strange" in the config file, the number of errors in the startup "unknown keyword in config file" are the same number of the "blank space lines" between kernel config labels...

Idea: could you please take off the "blank space lines" between labels ?

I havent tried this myself due to personal "data size" constraints in my Linux distro ... :(

Thanks for all th feedback ...

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

Post by admin » 03 Mar 2007, 09:33

Thanks for your test. You said it works if you just press enter. Then it is the first time it is possible to boot something, isn't it ?

Don't worry about the kernel warnings we will have a look at these problems after fixing problems with isolinux.

I removed blank lines as you suggested, and the new ISO is there:
http://cdbeta.dupoux.org/testiso-20070303-08h10.iso

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

Post by markmarques » 03 Mar 2007, 10:08

I tested the new iso ...
But this time I got only "5" messages of keyword error.
After reading the isolinux.cfg file I did not find any apparent detail except for the spaces (tabs ?) at the start of each line after the label.

Does isolinux allows any tab or space in the cfg file before any command ?
Could please test if by removing the starting spaces or tabs in the lines after the labels does it works ?

Also noticed that the "default rescuecd" option does not read correctly the command line specified.
If I press enter it calls directly "rescuecd" as single command ( and I noticed that it works become the "rescuecd" file exists...
It crashes because it does not read the label... :(
so when I press enter it simply calls the rescuecd "program" with no param whatosever... No root options, no nothing ...

So if the "unknown keyword error" is solved and the labels got correctly read there are no problem afterwards.... :)

We are close to solve this...

Thanks ...

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

Post by admin » 03 Mar 2007, 10:17

I replaced tabs with two spaces a long time ago, because I found two spaces in the gentoo config file, and the gentoo livecd is working. But this time I removed this spaces anyway.

I let the gentoo.cfg and knoppix.cfg in the isolinux directory. You can have a look at these config files to compare with isolinux.cfg.

Now, I removed the spaces at the beginning of the lines.
You can download this ISO:
http://cdbeta.dupoux.org/testiso-20070303-08h56.iso

It should work with the default "default rescuecd" now since I did as I saw in the knoppix config this time: I wrote the "append" line that works with default just after the default line.

If the first ISO works, try this one (it has all config options):
http://cdbeta.dupoux.org/testiso-20070303-09h19.iso

Thanks

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

Post by markmarques » 03 Mar 2007, 10:47

Sorry to say it did not work... :(
Still the 5 errors still appear ...
But this time after pressing enter it started diferently ...
It called rescuecd and afterwards rescuecd.igz ...
After letting it boot , it reached the keymap selection, I keep the default one by pressing enter and suddenly it stopped with : "Determining root device..."
"!the root bblock device is unspecified or undetected" ...
and keeped asking with boot():: ...

I tried /dev/ram0 but with no sucess...

So I am getting out of ideas.... :(

Returning to the isolinux config file there are somewhere an invalid char or "keyword" in the label part... :(

Idea: could it be any tab in any of the command lines? or an non printable char ? Is there any line copied from another place ?

As it seems it still ignores the labels in the config file....
So the nofb or any other option are still not working ...


thanks ...

Post Reply