drm: [radeon] no display; out-of-range resolution at Live CD boot

Bug #529497 reported by TJ
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Starting x86 Ubuntu Live CD Alpha 3 on a PC equipped with an ATI Radeon R200 the kernel mode-setting chooses a resolution the CRT monitor cannot support, thus rendering the Live CD session unusable.

In order to capture the boot logging the PC was booted using PXE, TFTP and NFS from a Lucid Alpha 3 image and the boot log captured via serial port (by adding "console=tty0 console=ttyS0,115200n8" to the PXE kernel boot options. netconsole only captures fragments of the boot log - another problem there I suspect).

[ 5.036760] [drm] Radeon Display Connectors
[ 5.041206] [drm] Connector 0:
[ 5.044459] [drm] VGA
[ 5.047077] [drm] DDC: 0x60 0x60 0x60 0x60 0x60 0x60 0x60 0x60
[ 5.053432] [drm] Encoders:
[ 5.056615] [drm] CRT1: INTERNAL_DAC1
...
[ 5.250844] [drm] Initialized radeon 2.0.0 20080528 for 0000:01:05.0 on minor 0
[ 5.261997] vga16fb: mapped to 0xc00a0000
[ 5.266425] fb1: VGA16 VGA frame buffer device
[ 5.330282] [drm] DAC-9: set mode 1280x1024 23
[ 5.350943] Console: switching to colour frame buffer device 160x64

There are other issues with the drm failing in the attached log but this one is the first that needs tackling.

Revision history for this message
TJ (tj) wrote :
TJ (tj)
description: updated
Revision history for this message
TJ (tj) wrote :

Starting with the kernel option "radeon.modeset=0" avoids the loss of the console and results in an Xorg display of 1024x768.

[ 4.635430] [drm] Initialized radeon 1.31.0 20080528 for 0000:01:05.0 on minor 0
[ 4.647097] vga16fb: mapped to 0xc00a0000
[ 4.651568] fb0: VGA16 VGA frame buffer device
[ 4.760578] Console: switching to colour frame buffer device 80x30

Running "System > Preferences > Display" reports a Messeltronik Dresden GmbH 16" that can support 1280x1024. Selecting this option, the CRT is able to display correctly at 1280x1024@60Hz.

Revision history for this message
TJ (tj) wrote :

Install "read-edid" package, then:

sudo get-edid | parse-edid >edid.log

 # EDID version 1 revision 2
Section "Monitor"
 # Block type: 2:0 3:ff
 # Block type: 2:0 3:fd
 # Block type: 2:0 3:fc
 Identifier "MD 1772JA"
 VendorName "MED"
 ModelName "MD 1772JA"
 # Block type: 2:0 3:ff
 # Block type: 2:0 3:fd
 HorizSync 30-72
 VertRefresh 50-120
 # Max dot clock (video bandwidth) 110 MHz
 # Block type: 2:0 3:fc
 # Block type: 2:0 3:fc
 # DPMS capabilities: Active off:yes Suspend:yes Standby:yes

 # Block type: 2:0 3:ff
 # Block type: 2:0 3:fd
 # Block type: 2:0 3:fc
 # Block type: 2:0 3:fc
EndSection

tags: added: kernel-series-unknown
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi TJ,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 529497

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
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.