Xorg won't start

[Serge Hallyn]

Binary package hint: xorg

I updated my maverick laptop this afternoon. Now after
boot is mostly completed, I get a blank screen. I can't
get to any terminals either (without booting an older kernel, where I get dropped straight into a console instead of getting X). All I can do is hit alt-sysrq-b.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: xorg 1:7.5+6ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
Architecture: amd64
Date: Tue Oct 5 20:42:47 2010
DkmsStatus:
 virtualbox-ose, 3.2.8, 2.6.35-20-generic, x86_64: installed
 virtualbox-ose, 3.2.8, 2.6.35-22-generic, x86_64: installed
 nvidia-current, 260.19.06, 2.6.35-22-generic, x86_64: installed
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100820)
MachineType: Sony Corporation VPCF11KFX
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-20-generic root=UUID=39014c73-b7b6-48d9-9ae6-62eec39544eb ro
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
dmi.bios.date: 12/07/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0250Y6
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0250Y6:bd12/07/2009:svnSonyCorporation:pnVPCF11KFX:pvrR5840006:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCF11KFX
dmi.product.version: R5840006
dmi.sys.vendor: Sony Corporation
system:
 distro: Ubuntu
 codename: maverick
 architecture: x86_64
 kernel: 2.6.35-20-generic

[Serge Hallyn (serge-hallyn)]

RAOF on #ubuntu-desktop pointed me to http://www.nvnews.net/vbulletin/showthread.php?t=155218 .
Falling back to the 256.53-0ubuntu3 nvidia-common package fixes the issue. So the 260 nvidia driver
appears broken for my vaio F11 laptop.

[bugbot (bugbot)]

Hey Serge,

Thanks for testing maverick during its development period. Unfortunately it looks like this bug report didn't get attention during the maverick development period. But I see there's not been more comments on the bug since the release, which makes me wonder if this is still an issue for you?

If you've not seen this issue since maverick's release yourself, it may have been solved by kernel or X or other updates that occurred late in the release; if so, would you mind please closing the bug for us? Go to the URL mentioned in this bug report, click the yellow icon(s) in the status column and set to 'Fix Released'.

If you no longer have the hardware needed to reproduce the problem, or otherwise feel the bug no longer needs tracked in Launchpad, you can set the status to 'Invalid'.

If you are the original reporter and still have this issue, just reply to this email saying so. (Or set the bug status to Confirmed.) If you are able to re-test this against 11.04 Natty Narwhal (our current development focus) and find the issue still affects Natty, please also run 'apport-collect <bug-number>' while running natty, which will add fresh logs and debug data, and flag it for the Ubuntu-X development team to look at.

[Serge Hallyn (serge-hallyn)]

The last time I tried, which I think was after natty alpha-1, I still had this problem. Unfortunately that laptop is currently serving wireless for the whole house and family, so it may take a few days before I can find a good time to test. I'll leave the bug state 'incomplete' until I can confirm whether it's still a problem.

(FWIW since nvidia always tries to upgrade itself (I never found a good pinning recipe), and nouveau inexplicably hangs the system two or three times per day (there's an open bug for that), I'm currently using VESA on that laptop.)

[Serge Hallyn (serge-hallyn)]

Yay, latest nvidia driver in natty is working for me on my Sony vaio F11.