Bug 17666 - rhdBIOSScratchUpdateBIOSScratchForOutput: Assertion 'Device != atomNone' failed.
Summary: rhdBIOSScratchUpdateBIOSScratchForOutput: Assertion 'Device != atomNone' failed.
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/radeonhd (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Egbert Eich
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-19 09:50 UTC by pl4nkton
Modified: 2008-09-20 08:45 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg log (4.68 KB, application/x-lzma)
2008-09-19 09:50 UTC, pl4nkton
no flags Details
This patch should fix the problem. (20.84 KB, patch)
2008-09-20 01:24 UTC, Egbert Eich
no flags Details | Splinter Review
xrandr output - incorrect res (1.18 KB, application/x-lzma)
2008-09-20 06:15 UTC, pl4nkton
no flags Details

Description pl4nkton 2008-09-19 09:50:32 UTC
Created attachment 19020 [details]
Xorg log

MacBook Pro 2.2 with X1600
ubuntu intrepid 2.6.27-rc6 git custom kernel
git radeonhd driver
xserver: 1.5

xorg server crashes at startup if externel screen is connected. (vga at dvi-d connector)
Comment 1 Egbert Eich 2008-09-20 01:24:50 UTC
Created attachment 19029 [details] [review]
This patch should fix the problem.

Please get a recent version of the driver from GIT and test this patch. 
(Check http://wiki.x.org/wiki/radeonhd for informations on how to do this).
I cannot test it here.
Thanks!
Comment 2 pl4nkton 2008-09-20 06:13:34 UTC
Ok DVI-A and D works, but the detected resolutions are still incorrect for both.
Comment 3 pl4nkton 2008-09-20 06:15:24 UTC
Created attachment 19035 [details]
xrandr output - incorrect res
Comment 4 Egbert Eich 2008-09-20 07:12:04 UTC
OK, I will push the patch then. Thanks for testing!
As for the wrong resolution:
It's possible that DDC isn't working.  We have seen this on MacBooks before. 
When I had access to a MacBook the problem didn't appear. It's hard to fix this without being able to reproduce it.
Some people claimed it went away after a suspend/resume cycle.
Please provide a verbose log file for the Xserver.
Do:
X -logverbose 7
on the command line in the console, kill the server with ctrl-alt-backspace.

Please, don't compress any files before you attach them.

Comment 5 Egbert Eich 2008-09-20 08:45:41 UTC
OK, I've committed the fix.
Commit ID:
4d14b581abdc2acfd60f4eeabf103451199df9eb

Thus I'm closing the bug, please post your log here regardless.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.