BUGS > 2012.1

(partly solved) all releases not booting ...

(1/5) > >>

michaa7:
I downloded the i386 xfce and i386 lxde. update-grub creates strange not working entries for both, there is an additional ";1" which prevents both isos from booting:


--- Quote ---menuentry "siduction-12.1-desperado-lxde-i386-201205212227 (vmlinuz0.686;1)" {
        insmod iso9660
        insmod part_msdos
        insmod ext2
        set root='(hd1,msdos9)'
        search --no-floppy --fs-uuid --set=root 1cadc53c-13b1-4b5a-81eb-a01fc22ce007
        loopback loop /sidon/siduction-12.1-desperado-lxde-i386-201205212227.iso
        linux (loop)/boot/vmlinuz0.686;1 fromhd=UUID=1cadc53c-13b1-4b5a-81eb-a01fc22ce007 fromiso=/sidon/sidu$
        initrd (loop)/boot/initrd0.686;1
}
menuentry "siduction-12.1-desperado-xfce-i386-201205212237 (vmlinuz0.686;1)" {
        insmod iso9660
        insmod part_msdos
        insmod ext2
        set root='(hd1,msdos9)'
        search --no-floppy --fs-uuid --set=root 1cadc53c-13b1-4b5a-81eb-a01fc22ce007
        loopback loop /sidon/siduction-12.1-desperado-xfce-i386-201205212237.iso
        linux (loop)/boot/vmlinuz0.686;1 fromhd=UUID=1cadc53c-13b1-4b5a-81eb-a01fc22ce007 fromiso=/sidon/sidu$
        initrd (loop)/boot/initrd0.686;1
}
menuentry "siduction-pontos (2.6.27-10.slh.1-sidux-686)" {
        insmod iso9660
        insmod part_msdos
        insmod ext2
        set root='(hd1,msdos9)'
        search --no-floppy --fs-uuid --set=root 1cadc53c-13b1-4b5a-81eb-a01fc22ce007
        loopback loop /sidon/siduction-pontos.iso
        linux (loop)/boot/vmlinuz-2.6.27-10.slh.1-sidux-686 fromhd=UUID=1cadc53c-13b1-4b5a-81eb-a01fc22ce007 $
        initrd (loop)/boot/initrd.img-2.6.27-10.slh.1-sidux-686
}
### END /etc/grub.d/60_fll-fromiso ###

--- End quote ---


Worked fine for all RCs (finaly). As you can see, the entry for an old pontos image does not have this additional  ";1" and boots fine.

After manually removing ";1" in grub.cfg, the xfce iso boots,  the lxde does not, it stopps at:

...
starting init process...
Target file system doesn't have requested /sbin/init
No init found
...

Both md5 sums are ok!

midrow:
I confirm the described behavior for the i386 KDE iso:

a) Only the desperado iso gets the additional ";1" by fll-fromiso.

b) The booting process stops with the following messages:

--- Code: ---Mounting aufs union filesystem...
Preparing live filesystem on /root...

Starting init process...

_
--- End code ---

michaa7:
same goes for 12.1.5.rqt.

Is there really noone else (exept midrow) having this problem?

I moved the isos to /srv, still the same.
So this seems not related to strange path/Label/UUID combinations. What is / seems so special in my environment that makes  /etc/default/grub2-fll-fromiso behaving so strange?

No hint, no interest in solving this problem?

devil:
I have not used fromiso in years, so no clue really, sorry.
It's too muh work for my taste.
But we are looking into it.

greetz
devil

michaa7:

--- Quote from: "devil" ---I have not used fromiso in years, so no clue really, sorry.
--- End quote ---

So you using isos from usb-stick only?

--- Quote ---It's too muh work for my taste.
--- End quote ---

I do not understand. With Grub2 you configure it once and your done for ever (if it works as expected). So it's less work than dd it on an stick.

--- Quote ---But we are looking into it.
--- End quote ---

Thxx.

One observation of which I don't know wether it is related or not:
It's the naming of the kernel. IIRC in RC you used a real name and version  for the kernel (in .../iso/boot/<kernel> ; was booting and ffl-fromiso didn't create this additional ";1"), with the release you changed to ".../iso/boot/vmlinuz0.686" (not booting and ffl-fromiso does create this additional ";1").
This does not happen with an old pontos.iso from this other distro. This indicates, AFAICS that it's the iso, not the hw or its config.

I do not really need a working iso although I prefere it over booting a CD if I need a second system for maintance. So I mainly tested the ISOs out of curiosity ( I am fine with my siduction-fluxbox installation ). But as long as you ship ffl-fromiso it should work, I think.
Still wondering how few people seem to use it (given that only one other person reports this problem).

Navigation

[0] Message Index

[#] Next page

Go to full version