[Bug 965855] Re: Failure when attempting to boot from stock configuration

[Luis Araujo]

I have a similar issue trying to build a stock image using Raring.

The binary/isolinux/txt.cfg file contains the boot menu options with the
names initrd.lz and vmlinuz like this:

default live
label live
  menu label ^Try Ubuntu without installing
  kernel /casper/vmlinuz
  append  file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --

Nevertheless the names of the files inside the casper/ directory are:
initrd.img-3.8.0-25-generic  and vmlinuz-3.8.0-25-generic respectively.

So the bootloader can't find the files during boot time and shows the
dialog message '/casper/vmlinuz' file not found, after pressing OK, it
just stays in the splash menu.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to live-build in Ubuntu.
https://bugs.launchpad.net/bugs/965855

Title:
  Failure when attempting to boot from stock configuration

Status in “live-build” package in Ubuntu:
  New

Bug description:
  I'm trying to use live-build 3.0~a24-1ubuntu17 on an updated install
  of Oneiric/i386.

  The first example in the official documentation - <http://live-
  manual.debian.net/manual-3.x/manual/html/live-manual/examples.en.html>
  - has a simple stock image to start with:

      mkdir tutorial1 ; cd tutorial1 ; lb config
      lb build

  When I do this, I end up with what appears to be a working binary-
  hybrid.iso. When I boot it, it shows the Debian Live splash screen,
  and prompts me to enter "live" or "memtest" to run the livecd or
  memtest86+ respectively. Running "memtest" works, but if I type
  "live", it seems to do absolutely nothing. The splash screen does stay
  visible and I can still type in memtest or interact with isolinux, but
  it doesn't (visibly) try to load the kernel or initrd or boot at all.

  I note that, in the tutorial1 directory, the file
  binary/isolinux/live.cfg looks like this:

      default live
      label live
              menu label ^Live
              menu default
              kernel /live/vmlinuz
              append initrd=/live/initrd.img boot=live config 

  However, the binary/live/ directory doesn't contain a "vmlinuz" or
  "initrd.img". It does contain:

      initrd.img-3.2.0-2-486 
      initrd.img-3.2.0-2-686-pae
      vmlinuz-3.2.0-2-486
      vmlinuz-3.2.0-2-686-pae 

  
  Now, that's me matching the official *Debian* documentation with the *Ubuntu* package, so maybe there's another step that needs to be done since I'm running inside Ubuntu? If I missed that, please let me know. 

  
  I also wondered if the problem was that it generated two initrd images and two kernels. I tried to test for this: I modified the the auto/config file which 'lh' created so that it contained these lines: 

      --architectures i386 \
      --linux-flavours 486 \

  When I re-ran "lb build", it only created one initrd and one vmlinuz:
  "initrd.img-3.2.0-2-486" and "vmlinuz-3.2.0-2-486". However, the
  "live.cfg" file still was referencing a "vmlinuz" and "initrd.img".

  
  Any help is greatly appreciated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/965855/+subscriptions