Public bug reported:

The LiveCD boots normally to the initial splash screen with menu
options.  After selecting any option, the screen goes black with no
backlight and remains that way.  X never appears to start.

The hardware specific to this bug report is a Dell Inspiron 1420.  Detailed 
report for Gutsy can be found here:
    https://wiki.ubuntu.com/LaptopTestingTeam/DellInspiron1420

Under the hood are:
    intel core 2 duo t7500
    nVidia GeForce 8400M GS

The normal kernel bug reports will be attached following the report,
along with a comparison of LiveCD results for Feisty, Gutsy, and Hardy
Alpha 1.

This bug may be similar to #147623 and #67079.

The bug has occurred in every daily version of Hardy as well as the
Alpha 1 release.  The last one tested was 12152007.  Gutsy at least
failed over to displayconfiggtk.

Their are only two resolutions found so far:

1.  Remove 'splash' from the LiveCD kernel boot parameters.

2.  Insert break=top, then when the busybox shell pops up, enter:
modprobe vga16fb

The second method does not result in a splash screen, but the LiveCD
will boot into X without user intervention.

I was unable to reproduce this in any other distribution, as I don't
personally know any other that uses usplash.  I tested a debian
installation, but they are using directfb during initial installation
for a gui.

i386 can also be installed on the specific laptop, but also results in
the same problem, at least with the Alpha 1 release.  This was not
tested with additional daily versions.

I wasn't sure whether this was a casper, usplash, or linux problem, but
allowed the wiki.ubuntu.com/Bugs/FindRightPackage to lead the way.

If there are any further questions after this initial report, I will
promptly answer them.

Best regards,

Harvey

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 casper hardy linux livecd usplash

-- 
[Hardy Desktop amd64 Alpha 1 - 20071215] screen remains black when booting 
livecd
https://bugs.launchpad.net/bugs/177255
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to