Bug 93417 - xf86-video-ati [mobility radeon x2300] driver does not identify LVDS "no monitor specified"
Summary: xf86-video-ati [mobility radeon x2300] driver does not identify LVDS "no moni...
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.6 (2010.12)
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-16 22:11 UTC by Kokodu
Modified: 2019-11-19 07:54 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Yorg.0.log, no screen section available (39.47 KB, text/plain)
2015-12-16 22:11 UTC, Kokodu
no flags Details
dmesg (59.62 KB, text/plain)
2015-12-17 18:31 UTC, Kokodu
no flags Details
journalctl (94.04 KB, text/plain)
2015-12-17 18:32 UTC, Kokodu
no flags Details
Xorg.0.log of debian live system, older kernel (49.75 KB, text/plain)
2015-12-17 19:47 UTC, Kokodu
no flags Details
Xorg.0.log with radeon.backlight=0 (39.85 KB, text/plain)
2015-12-17 21:11 UTC, Kokodu
no flags Details
dmesg.radeon.backlight=0 (57.83 KB, text/plain)
2015-12-17 21:19 UTC, Kokodu
no flags Details

Description Kokodu 2015-12-16 22:11:43 UTC
Created attachment 120554 [details]
Yorg.0.log, no screen section available

The driver does not load correctly and therefore the LVDS is not being recognized. I do get a dark [not black] screen after boot. With help of a second monitor I managed to get a screen I can work with. I used the setting "radeon.modeset=0" to get it. No xorg.conf has been created.
The machine is a Sony Vaio VGN-CR11Z/R (x64). Running: Archlinux 4.2.3-1 x86_64 
The mobility Radeon X2300 seems to belong to r600 according to Xorg.0.log, though radeonwiki says r500. lspci says RV516/M64. That is a bit unhelpful.
Xorg.0.log says: compiled for (Server) 1.18.0, module version = (Version) 7.6.1
Comment 1 Alex Deucher 2015-12-16 22:43:45 UTC
Please attach your dmesg output with the radeon kernel driver loaded.
Comment 2 Kokodu 2015-12-17 18:31:00 UTC
Created attachment 120568 [details]
dmesg

minor information removed
Comment 3 Kokodu 2015-12-17 18:32:02 UTC
Created attachment 120569 [details]
journalctl

minor information removed
Comment 4 Alex Deucher 2015-12-17 19:13:50 UTC
The LVDS is detected as an 1280x800 panel.  Does it seem like a backlight issue?  Is this a regression?  If so when did it used to work?  Can you try setting radeon.backlight=0 on the kernel command line in grub to disable driver backlight control.  You might be seeing a regression as a result of this patch:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4281f46ef839050d2ef60348f661eb463c21cc2e
which was fixed in:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=4cee6a9057d5e13911f0cb6e143d11dc1a3245dd
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ae93580ee59c02395c1711d3e6b90546b8137b86
Comment 5 Kokodu 2015-12-17 19:47:40 UTC
Created attachment 120572 [details]
Xorg.0.log of debian live system, older kernel
Comment 6 Kokodu 2015-12-17 19:48:45 UTC
(In reply to Alex Deucher from comment #4)
> The LVDS is detected as an 1280x800 panel.  Does it seem like a backlight
> issue?  Is this a regression? I think so. 

> If so when did it used to work? It worked with older kernel versions. To give an example, I attached the Xorg.0.log of a debianoid live system with older kernel, driver and Xorg server.

> Can you try
> setting radeon.backlight=0 on the kernel command line in grub to disable
> driver backlight control.  You might be seeing a regression as a result of
> this patch:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
> ?id=4281f46ef839050d2ef60348f661eb463c21cc2e
> which was fixed in:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
> ?id=4cee6a9057d5e13911f0cb6e143d11dc1a3245dd
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
> ?id=ae93580ee59c02395c1711d3e6b90546b8137b86

Will try and set in jiffy.
Comment 7 Kokodu 2015-12-17 21:11:39 UTC
Created attachment 120574 [details]
Xorg.0.log with radeon.backlight=0
Comment 8 Kokodu 2015-12-17 21:14:01 UTC
(In reply to Alex Deucher from comment #4)
It worked with older kernel versions. To give an example, I attached the Xorg.0.log of a debianoid live system with older kernel, driver and Xorg server

> Can you try
> setting radeon.backlight=0 on the kernel command line in grub to disable
> driver backlight control.  You might be seeing a regression as a result of

This did not work. Output attached.
Comment 9 Kokodu 2015-12-17 21:19:56 UTC
Created attachment 120575 [details]
dmesg.radeon.backlight=0
Comment 10 Alex Deucher 2015-12-17 21:25:16 UTC
(In reply to Alex Deucher from comment #4)
> You might be seeing a regression as a result of
> this patch:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
> ?id=4281f46ef839050d2ef60348f661eb463c21cc2e
> which was fixed in:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
> ?id=4cee6a9057d5e13911f0cb6e143d11dc1a3245dd
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/
> ?id=ae93580ee59c02395c1711d3e6b90546b8137b86

Does reverting these help?  If not, can you bisect?
Comment 11 Kokodu 2015-12-17 22:17:43 UTC
I would like to try this, but unfortunately this is beyond my capacity atm. I need to learn what to do first. Can you give me a link/resource, so I can try reverting these? I would need basic explanation of what I'm doing. I might be able to try with a friend, perhaps. =P
Comment 12 Martin Peres 2019-11-19 07:54:13 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/issues/147.


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.