screen remains blank after boot / wrong resolution

[Mario Hock]

Binary package hint: xorg

I just tried the ubuntu 10.10 release candidate. While booting I can see the ubuntu-boot-logo, after that the screen gets black.

I found out that the screen was set to an wrong resolution. "13??x7??" but my monitor only supports resolutions up to 1280x800. So I typed <Alt>-F2, xterm, sudo xrandr -s 1280x800.

After that all is working fine.

I'm using a Samsung R50 with ATI Mobilitiy Radeon X700
---
Architecture: i386
DRM.card0.DVI.D.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x800 1280x720 1152x768 1024x768 800x600 848x480 720x480 640x480
 edid-base64:
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DistroRelease: Ubuntu 10.10
GdmLog1: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.1'] failed with exit code 1: cat: /var/log/gdm/:0.log.1: No such file or directory
GdmLog2: Error: command ['gksu', '-D', 'Apport', '--', 'cat', '/var/log/gdm/:0.log.2'] failed with exit code 1: cat: /var/log/gdm/:0.log.2: No such file or directory
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
MachineType: SAMSUNG ELECTRONICS CO.,LTD R50/R51
Package: xserver-xorg-video-ati 1:6.13.1-1ubuntu5
PackageArchitecture: i386
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/casper/vmlinuz noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=de console-setup/layoutcode?=de
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Tags: maverick maverick
Uname: Linux 2.6.35-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 11/02/2005
dmi.bios.vendor: SAMSUNG ELECTRONICS CO.,LTD
dmi.bios.version: D5CA.20051102.1854.LMK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnSAMSUNGELECTRONICSCO.,LTD:bvrD5CA.20051102.1854.LMK:bd11/02/2005:svnSAMSUNGELECTRONICSCO.,LTD:pnR50/R51:pvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD:ct1:cvrN/A:
dmi.product.name: R50/R51
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO.,LTD
glxinfo: Error: [Errno 2] No such file or directory
system:
 distro: Ubuntu
 codename: maverick
 architecture: i686
 kernel: 2.6.35-22-generic

[Dave Gilbert (ubuntu-treblig)]

Hi,
  Can you include the output of:

lspci -v
a copy of your /var/log/Xorg.0.log and the output of dmesg and finally the output of xrandr.

If you can try and run apport-collect 654170 which should collect a load of stuff and attach it to this report.

Dave

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

apport information

[Mario Hock (mariohock)]

Hi, I just added the files you asked for. Hope this helps solving the bug.

Unfortunately I discovered some kind of partial blanking of the screen while scrolling or moving windows. I suppose this it another bug, but I wanted to mention it.

Thank you.

[Dave Gilbert (ubuntu-treblig)]

It seems odd, the specs of your machine on the web show it as 1280x800. so I'm not sure why it's claiming to be able to do 1360x768.

Now you've put that information there I'll leave it to the Xorg guys to try and debug what's going on.

Dave

[Mario Hock (mariohock)]

I wonder about that, too.

I just checked that on ubuntu 10.04. Surprisingly it also claims to be able of 1360x768. But on 10.04 1280x800 is chosen by default. I suppose the only difference is another heuristic in 10.10 which chooses 1360x768..

Thanks for your assistance.

[bugbot (bugbot)]

Hey Mario,

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.