| Summary: | radeon driver doesn't switch video out in xorg 7.x | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Alexey Parshin <alexeyp> | ||||||
| Component: | Driver/Radeon | Assignee: | Xorg Project Team <xorg-team> | ||||||
| Status: | RESOLVED DUPLICATE | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | high | CC: | alexdeucher, erik.andren, marius.andreiana, mjs | ||||||
| Version: | 7.0 (2005.12) | ||||||||
| Hardware: | x86 (IA32) | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
Alexey Parshin
2006-04-23 15:06:01 UTC
Please post your xorg.conf and your xorg.log Created attachment 5428 [details]
xorg.conf
Created attachment 5429 [details]
log file
Try Option "BIOSHotkeys". (In reply to comment #4) > Try Option "BIOSHotkeys". I already have Option "BIOSHotkeys" "on" (see my xorg.conf). Am I using it in the wrong place? It's correctly placed. I suppose turning it off doesn't make a difference? (In reply to comment #6) > It's correctly placed. I suppose turning it off doesn't make a difference? That's correct :( Does switching work on the console? Make sure the thinkpad apci module is configured correctly (you might also test without it loaded). It can be configured to generate acpi events for things like the video toggle button rather than letting the bios handle it. (In reply to comment #8) > Does switching work on the console? Make sure the thinkpad apci module is > configured correctly (you might also test without it loaded). It can be > configured to generate acpi events for things like the video toggle button > rather than letting the bios handle it. I have checked the ACPI log. When I press switch monitor button - it doesn't generate any events. Sleep, lid, power buttons work fine - events are generated and processed. I've also tried to use "ati" driver instead of "radeon" (in xorg.conf). I'm seeing an issue like this, but I'm not sure if it's the same one. Plugging a projector in video-out results in no image on the external projector. "radeontool dac on" has no effect. Restarting the X server (logging out or <ctrl><alt><bksp>) results in a display, but the resolution is borked (low-res and stretched vertically). In that mode xrandr reports: # xrandr SZ: Pixels Physical Refresh *0 848 x 480 ( 287mm x 163mm ) *-25880 Current rotation - normal Current reflection - none Rotations possible - normal Reflections possible - none xrandr cannot change resolutions in that mode. Am I seeing the same bug, or should I open a different one? BTW, This is a Thinkpad T41. I use the radeonfb driver in the kernel. I need it to make suspend power down the graphics card. I don't have BIOShotkeys enabled. It used to work for me too. (In reply to comment #10) > I'm seeing an issue like this, but I'm not sure if it's the same one. > > Plugging a projector in video-out results in no image on the external projector. > "radeontool dac on" has no effect. > > Restarting the X server (logging out or <ctrl><alt><bksp>) results in a display, > but the resolution is borked (low-res and stretched vertically). > > In that mode xrandr reports: > > # xrandr > SZ: Pixels Physical Refresh > *0 848 x 480 ( 287mm x 163mm ) *-25880 > Current rotation - normal > Current reflection - none > Rotations possible - normal > Reflections possible - none > > xrandr cannot change resolutions in that mode. > > Am I seeing the same bug, or should I open a different one? > > BTW, This is a Thinkpad T41. I use the radeonfb driver in the kernel. I need > it to make suspend power down the graphics card. I don't have BIOShotkeys > enabled. It used to work for me too. You problem looks like bug 7243. (In reply to comment #11) > You problem looks like bug 7243. Thanks. On further investigation, I think it looks like 7203. Looks like bug #2000 too. Reporter, please mark this one as dupe. *** This bug has been marked as a duplicate of bug 2000 *** |
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.