Elive

  • Status Closed
  • Percent Complete
    100%
  • Task Type Bug Report
  • Category Live Mode
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version 1.0 Gem (Stable)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Elive
Opened by daikatana - 2009-06-28
Last edited by thanatermesis - 2009-07-10

FS#412 - elive_1.9.31_unstable ISO file - Grub Menu is wrong!

Subj: elive_1.9.31_unstable ISO file - Grub Menu is wrong!

If you check the contents of the menu.lst file in the boot/grub folder and compare the kernel and initrd filenames in the menu to the actual filenames, you will see that they do not match (spelling issue with “_” and “-” characters), thus it is not possible to boot the system.
Since I was using FAT32 partition (with grub4dos and the original menu.lst file from the iso) to which I extracted the contents of the ISO file, I was able to boot the installer after editing the grub menu.lst file. I have yet to get the installer working correctly, since the system boots but doesn’t continue with the installer...

Closed by  thanatermesis
10.07.2009 12:22
Reason for closing:  Not a bug
Admin

You are talking about the menu.lst of the live mode or of the installed system ?

Do you are using unetbootin ? or using a normal CD mode ?

Sorry, I thought it was clear what I meant. I am talking about menu.lst file in the elive_1.9.31_unstable.iso CDROM file, so I believe that will be the live-mode. But as mentioned, I extracted the contents from the iso to a HD partition so that I can use an installation method similar to the “USB-HD install” method (except ins place of the USB-HD, I used a partition on my HD for extracting the contents).
Today I have tried the earlier versions elive_1.9.30_unstable.iso file, and extracted the contents for installation and Grub menu.lst in that ISO file is correct and the system boots.
Hope this clarifies...???

Admin

yes, mmmh, can you show us these two menu.lst ? (only the wrong line)

Admin

The one of the 1.9.31 looks like this, that looks like to be correct:

title  Elive Normal Mode
kernel /boot/vmlinuz-2.6.26.8-elive-686 boot=eli quiet vga=788 resolution
initrd /boot/initrd.img-2.6.26.8-elive-686

yes, as per your last message, the grub menu looks correct, but what that doesn’t account for is the actual Kernel and Initrd filenames in the BOOT folder!
So let me expound on that...

1.9.31.iso mounted with daemon tools (under windows), and here we have the following:

Kernel and initrd files -

   <cd-rom>:\BOOT\VMLINUZ_2.6.26.8_ELIVE_686
   <cd-rom>:\BOOT\INITRD.IMG_2.6.26.8_ELIVE_686

Grub - MENU.LST file first entry (and the other entries have the same kernel and initrd filenames referenced!) as shown below:

 title  Elive Normal Mode
 kernel /boot/vmlinuz-2.6.26.8-elive-686 boot=eli quiet vga=788 resolution
 initrd /boot/initrd.img-2.6.26.8-elive-686

If you compare the filesnames to the menu entries, you will see that they do not match (”_” in the filenames vs, “-” in the menu entries when referencing the kernel and initrd). Either the Menu.lst has to be edited to reflect the correct Kernel and Initrd filenames, or the files should be renamed!

I have checked the previous version ISO file (1.9.30), and files in the boot folder and the references to them in the grub Menu.lst file are correct, and they both use “-”, so I think the standard convention is that the Kernel and Initrd files must have “-”, and not “_” in the 1.9.31.iso file!
They should be:

   \BOOT\VMLINUZ-2.6.26.8-ELIVE-686
   \BOOT\INITRD.IMG-2.6.26.8-ELIVE-686

Has anyone manage to boot the 1.9.31.ISO file succesfully? I didn’t, and all I got was “file not found” fault message from grub loader!

P.S.: Question- if anyone interested is in detailed instructions on how to boot from 1.9.30/31.iso using a small fat32 HD partition, I can deliver it. This uses Grub4DOS and I think Windows users might find that easier to follow. I am not sure where I should post such info, so please advise if there’s interest in such instruction.

Admin

I think that your ISO was modified in a sort of way, is windows again doing things that we dont want ? :)

I have downloaded the 1.9.31 FROM the mirrors and everything is correct:

[root /tmp/foo]# mount -o loop elive_1.9.31_unstable.iso mont/
[root /tmp/foo]# ls mont/boot/
grub                               memtest86+.bin
initrd.img-2.6.26.8-elive-686      memtest86+_v1.70.bin
initrd.img-2.6.26.8-elive-686.sig  vmlinuz-2.6.26.8-elive-686
[root /tmp/foo]# grep kernel mont/boot/grub/menu.lst | head -1
kernel /boot/vmlinuz-2.6.26.8-elive-686 boot=eli quiet vga=788 resolution
[root /tmp/foo]# 

Btw, made a look to: http://www.elivecd.org/Help/Howto/boot-elive-from-usb

Admin

In the Elive Forum is a good place to post it :) http://forum.elivecd.org

Although this item is closed, I am not sure if it IS or IS NOT a bug, but I can finally confirm that there's an issue. Ifinally had time to download and retest some things including your comment about Windows doing what it is NOT supposed to do. What I found is the following:

According to ISOBuster (a windows ISO file analyzer program), there seems to be 2 different CD file system layouts, one is linux type (Shown as RR file system) and the other is the ISO9660 standard file system. Both of them refer to the same physical files on the CD, however, the ISO9660 Table of contents list tthe files with "_" instead of "-" and that is what is causing the problem when I extract the ISO contents under Windows, and I had to either rename the files using "-" or edit the Menu file wherein the file references are modified using "_" character.

I think that when creating the ISO file, especially with the ISO9660 standard, the ISO program should be used such that the filenames in the CD Table of Contents are created correctly to enable uniformity. AFAIK, and from my own tests, ISO9660 do not accept "-" character in a filename, only Joliet (or Joliet+ISO9660) accept the "-" character in a filename or as a cd label. Therefore, perhaps, for windows users, the CD format should include Joliet option instead of pure ISO9660 standards, if the filenames should have "-" character.

Date User Effort (H:M) Comment
watch my effort tracking timers

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing