live cd - graphics safe mode, standard mode fails

Bug #289598 reported by Matt.V
4
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
Invalid
Undecided
Tormod Volden

Bug Description

Hello:

This bug is from using the 2008.10 beta live CD on two workstations.

When I try to boot using the live cd, the user interface stops working near the end of the boot sequence.
  - I see the initial boot screens with the ubuntu graphical progress slider
  - right at the end of the boot where the xdesktop would start the screen goes blank and I see no further activity

I tried this with the default options and with safe mode, no difference in booting.

The first machine:
    - an x86 pc, with a nvidia 6100 graphics card installed and active
 The second machine
   - an x86 pc, with integrated Intel 82865G graphics -- currently Centos is running on this machine using a graphical desktop with no issues

The machine with the nvidia card I saw green and pink bars, the Intel graphics just displayed a blank screen. I'm sure this is related to the xserver setup.

Is there a way to force to command mode to run the x configuration before launching the xserver? I tried the CTRL-SHIFT-backspace and CTRL-ALT-backspace, but it didn't do the trick.

I have a laptop with integrated Intel 965 express graphics where I've tried the same 2008.10 beta live cd and it works flawlessly.

Sincerely,
Matt

-----
I tried this on the release version, same issues.
When I took off the 'splash' and 'quiet' boot flags, and had safe mode, I saw the last mesage that was visible is "Launching Ubiquity"

When I searched for other options, I tried using some vesa modes (771,775, ...) which worked fine until either gnome display manager was launched or the ubiquity was launched.

With the non-safe mode with no splash option there was some garbage displayed on launch of gnome... not usable.

How can I configure the Ubuntu boot so that so it will install with a LCD giving me reasonable output when gnome or ubiquity is launched? Where can I find this information?

Matt

------

I received a response to a similar bug in an earlier build, suggesting I run some diagnostics.

>Hi mvording,
>
>Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this >issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

How do I go about doing this from the boot sequence, as I haven't yet installed Ubuntu onto my system? Any links to examples on how to capture the diagnostic information required would be appreciated.

Matt.V (mvording)
description: updated
Matt.V (mvording)
description: updated
Revision history for this message
Tormod Volden (tormodvolden) wrote :

These are bugs in the graphics drivers. I have moved this bug report to intel, please open a new bug for your nvidia pc (package is xserver-xorg-video-nv).

You can get the lspci output from running any linux version, this information does not change.

To get at least a minimal X log, boot with the "text" boot/kernel parameter (normal session, "try out Ubuntu").
Then log in and run "sudo Xorg -probeonly". Then copy /var/log/Xorg.0.log to a USB stick or your hard drive, which you can mount with "sudo mount /dev/sda1 /mnt" - change sda1 to the correct partition name. Your drive is now under /mnt.

Changed in ubiquity:
assignee: nobody → tormodvolden
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in xserver-xorg-video-intel:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.