← Back to team overview

kernel-packages team mailing list archive

[Bug 1072965] Re: 12.10 live USB crashes on boot


Will Kemp, could you please confirm this issue exists with the latest
development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
could you please run the following command in Precise from a Terminal
(Applications->Accessories->Terminal), as it will automatically gather
and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

** Tags added: needs-kernel-logs needs-upstream-testing regression-

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  12.10 live USB crashes on boot

Status in “linux” package in Ubuntu:

Bug description:
  Ubuntu 12.10 live image written to a USB stick using the utility in
  Ubuntu 12.04.

  ISO file matches MD5 hash.

  On booting from USB stick, first screen with accessibility icons
  appears and dialog is functional but after that, i get a flasshing
  underline cursor in the top LHS position on the screen for a few
  seconds and then it crashes. If i enter the accessibility menu, i get
  the boot selection dialog after choosing the keyboard. Then, after
  selecting the try without installing option, it goes to the cursor and
  then crashes. If i don't do anything at the accessibility icon screen,
  after the timeout it goes immediately to the cursor and then crashes.

  When i say "crashes", what actually happens is there's no further
  output to the screen. The monitor reports "no signal". There is a
  small amount of hdd activity after that, but then no sign of life.
  After a few minutes, i do a hard shutdown.

  The system is a Shuttle XS35V3
  CPU: Atom D2700
  Chipset: N10/ICH7
  VGA: Atom Processor D2xxx/N2xxx Integrated Graphics Controller

  Ubuntu 12.04 runs on this system without problems (i'm using it to
  lodge this bug report).

To manage notifications about this bug go to: