Critical: 10.04 -> 10.10 blank screen on reboot - checking non-existent battery

Bug #658183 reported by Libor Spacek
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-openchrome (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: ubuntu-docs

After upgrading from 10.04 to 10.10 on AMD64, when rebooting and thereafter the system is frozen with a blank screen.
Playing with failsafe bootup, it appears to be stopped when 'checking battery state' but this is a desktop machine!
Following various hints from the forum, such as updating and reinstalling ubuntu-desktop etc did not help.

As my computer is dead now, I cannot supply any more diagnostics.
---
Architecture: amd64
CheckboxSubmission: 340ff73e8201023b4f6f65dd95101636
CheckboxSystem: fc73f07fcd9845bb95fa3ca6b8be7ef2
CurrentDmesg:
 [ 105.242484] svc: failed to register lockdv1 RPC service (errno 97).
 [ 105.243748] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
 [ 105.249864] NFSD: starting 90-second grace period
 [ 120.320021] tap0: no IPv6 routers present
DistroRelease: Ubuntu 10.10
Lsusb:
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: xorg 1:7.5+6ubuntu3
PackageArchitecture: amd64
ProcCmdLine: root=UUID=090e805a-05a1-40d8-a3e1-68f670587fba ro quiet splash
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/tcsh
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Tags: maverick maverick
Uname: Linux 2.6.35-22-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video
dmi.bios.date: 10/14/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.80
dmi.board.asset.tag: 00000000
dmi.board.name: K8Upgrade-VM800
dmi.board.version: 1.00
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/14/2005:svn:pnK8Upgrade-VM800:pvr1.00:rvn:rnK8Upgrade-VM800:rvr1.00:
dmi.product.name: K8Upgrade-VM800
dmi.product.version: 1.00
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-22-generic

Libor Spacek (libors)
tags: added: boot
Revision history for this message
Libor Spacek (libors) wrote :

I meant safemode, not safemore above

Libor Spacek (libors)
Changed in ubuntu-docs (Ubuntu):
status: New → Confirmed
Revision history for this message
Book 'em Dano (heymrdjd) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better.

First, bugs have to be confirmed by someone other than the person who is reporting the bug.

Second, could you please add the log files from '/var/log/dist-upgrade/' to this bug report as separate attachments? Boot up using a Live CD and search for your hard drive that you installed Ubuntu to, then look for the files in /var/log/dist-upgrade/ & the /var/log/Xorg.0.log. Thanks in advance.

affects: ubuntu-docs (Ubuntu) → xorg (Ubuntu)
Changed in xorg (Ubuntu):
status: Confirmed → Incomplete
tags: added: lucid2maverick
Revision history for this message
Robert Manresa (robert-manresa) wrote : Re: [Bug 658183] Re: Critical: 10.04 -> 10.10 blank screen on reboot - checking non-existent battery

Hi,

Now I am using nv driver but when I try to use the nvidia one xorg does
not start and only console is avalable. I think it's related to this:

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/626974

and this:

http://www.nvnews.net/vbulletin/showthread.php?t=154895&highlight=xorg+1.9

I have a GeForce 4 TI4200

Errors are the same.

On 12/10/10 21:09, Book 'em Dano wrote:
> Thanks for taking the time to report this bug and helping to make Ubuntu
> better.
>
> First, bugs have to be confirmed by someone other than the person who is
> reporting the bug.
>
> Second, could you please add the log files from '/var/log/dist-upgrade/'
> to this bug report as separate attachments? Boot up using a Live CD and
> search for your hard drive that you installed Ubuntu to, then look for
> the files in /var/log/dist-upgrade/& the /var/log/Xorg.0.log. Thanks
> in advance.
>
> ** Package changed: ubuntu-docs (Ubuntu) => xorg (Ubuntu)
>
> ** Changed in: xorg (Ubuntu)
> Status: Confirmed => Incomplete
>
> ** Tags added: lucid2maverick
>

Revision history for this message
Libor Spacek (libors) wrote :
Revision history for this message
Libor Spacek (libors) wrote :
Revision history for this message
Libor Spacek (libors) wrote :
Book 'em Dano (heymrdjd)
tags: added: black-screen
Revision history for this message
Libor Spacek (libors) wrote :

I am able to boot up in failsafe mode and run failsafex in low resolution mode, getting the popup message: 'could not apply stored monitor settings'. None of the other items on the failsafe menu, such as 'reconfigure graphics' work. That is when I select them, it just returns to the failsafe screen options.

Is the information now complete? Please do let me know if you need any more.

Revision history for this message
Libor Spacek (libors) wrote :

I have created xorg.conf with "vesa" video driver entry (copied from xorg.failsafe).
This enables me to boot up for the first time but, of course, still only in
low graphics with horribly wrong aspect ratio.

Very poor show, 10.10. I think 0.10 would have been a better number,
as in 0 marks out of 10.

As much as I hate the idea, I guess it is time to go back to Windows?!?

Changed in xorg (Ubuntu):
status: Incomplete → In Progress
description: updated
Revision history for this message
Book 'em Dano (heymrdjd) wrote :

Libor, are you sure that you have attached all the logs that are located in /var/log/dist-upgrade/? Are there any more logs in /var/log that have Xorg in the file name, for instance, Xorg.0.log.old? If there are any more files, could please attach them to this report. And in a terminal (Applications > Accessories > Terminal) please type in the following command:

apport-collect 658183

Information pertaining to your computer will be gathered and forwarded to this report that will help determine the manner to resolve your issue.

Also, I'm changing the status from "In Progress" to "New" as the "In Progress" status is only used when the bug has been specifically assigned to someone.

Changed in xorg (Ubuntu):
status: In Progress → New
Revision history for this message
Libor Spacek (libors) wrote :

I previously included only the *.log files.
I am attaching now the complete contents of /var/log/dist-upgrade/

tags: added: apport-collected
description: updated
Revision history for this message
Libor Spacek (libors) wrote : BootDmesg.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : Dependencies.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : Lspci.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : PciDisplay.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : ProcModules.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : RelatedPackageVersions.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : UdevDb.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : UdevLog.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : XorgConf.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : XorgLog.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : XorgLogOld.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : Xrandr.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : glxinfo.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : monitors.xml.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : peripherals.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : setxkbmap.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : xdpyinfo.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote : xkbcomp.txt

apport information

Revision history for this message
Libor Spacek (libors) wrote :

I have VIA integrated graphics.
I now attach all the /var/log/Xorg.* files

Bryce Harrington (bryce)
tags: added: lucid maverick
Revision history for this message
Libor Spacek (libors) wrote :

I think this bug is happening because the latest maverick Xorg driver does not support VIA integrated graphics. I don't understand it, as the previous one, shipped with Ubuntu 10.04 worked better.

Revision history for this message
Libor Spacek (libors) wrote :

That is to say, at least its "vesa" driver kind of worked but now even that is broken.

affects: xorg (Ubuntu) → xserver-xorg-video-openchrome (Ubuntu)
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.