Bug 66241 - radeon fails to initialise the monitor
Summary: radeon fails to initialise the monitor
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-30 22:53 UTC by Chris Rankin
Modified: 2016-03-23 18:58 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.12.2,3.12.3
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
dmesg log for 3.12.2 (67.93 KB, text/plain)
2013-11-30 22:53 UTC, Chris Rankin
Details
Successful boot with 3.11.10 (67.97 KB, text/plain)
2013-11-30 22:57 UTC, Chris Rankin
Details
dmesg output when radeon.hw_i2c=0 (69.22 KB, text/plain)
2013-12-03 21:02 UTC, Chris Rankin
Details
possible fix (2.02 KB, patch)
2013-12-03 22:28 UTC, Alex Deucher
Details | Diff
dmesg output with 2nd patch applied (68.19 KB, text/plain)
2013-12-04 00:10 UTC, Chris Rankin
Details
possible fix (2.04 KB, patch)
2013-12-04 17:29 UTC, Alex Deucher
Details | Diff
dmesg output from 3.12.3 + 3rd patch (51.51 KB, text/plain)
2013-12-04 22:19 UTC, Chris Rankin
Details
dmesg output from 3.12.3 + 3rd patch; original system (68.04 KB, text/plain)
2013-12-04 22:44 UTC, Chris Rankin
Details

Description Chris Rankin 2013-11-30 22:53:14 UTC
Created attachment 116951 [details]
dmesg log for 3.12.2

I upgraded from Linux 3.11.10 to 3.12.2, but the monitor went blank when the radeon driver loaded. According to the dmesg log:

[    1.993793] radeon 0000:02:00.0: No connectors reported connected with modes
[    1.993795] [drm] Cannot find any crtc or sizes - going 1024x768

The full log is attached. The system behaves properly when reverting to 3.11.10.

I have a HD4890 / RV790 PCIE graphics card.

Booting with radeon.aspm=0 or radeon.dpm=0 does not help.
Comment 1 Chris Rankin 2013-11-30 22:57:15 UTC
Created attachment 116961 [details]
Successful boot with 3.11.10

For reference, here is the dmesg log for a successful boot with 3.11.10.
Comment 2 Alex Deucher 2013-12-03 16:07:02 UTC
Do you have radeon.hw_i2c=1 set somewhere?  If so, it should be fixed by this commit:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=fae009d15a44e5f1d938340facf4b8bc7dc69a09
Comment 3 Chris Rankin 2013-12-03 21:02:47 UTC
Created attachment 117291 [details]
dmesg output when radeon.hw_i2c=0

I do have hw_i2c=1 in my /etc/modprobe.d/local.conf file, but the patch does not help. However, I am able to boot when I add radeon.hw_i2c=0 to the grub command line.

dmesg output is attached.
Comment 4 Alex Deucher 2013-12-03 22:28:26 UTC
Created attachment 117321 [details]
possible fix

Does the attached patch help?
Comment 5 Chris Rankin 2013-12-04 00:10:36 UTC
Created attachment 117331 [details]
dmesg output with 2nd patch applied

No, the additional patch did not help.
Comment 6 Alex Deucher 2013-12-04 17:29:49 UTC
Created attachment 117461 [details]
possible fix

Does this patch work any better?
Comment 7 Chris Rankin 2013-12-04 22:19:49 UTC
Created attachment 117501 [details]
dmesg output from 3.12.3 + 3rd patch

I have just updated a second system from 3.11.10 to 3.12.3. This new system also experienced this bug, and the 3rd patch fixes it :-).

I will test the 3rd patch on the other system next.
Comment 8 Chris Rankin 2013-12-04 22:44:51 UTC
Created attachment 117511 [details]
dmesg output from 3.12.3 + 3rd patch; original system

The 3rd patch allows my original system to boot 3.12.3 as well.

dmesg output is attached.

Note You need to log in before you can comment on or make changes to this bug.