Radeon Mobility 7500 does not detect video projector

[Dominik Holler]

Binary package hint: xserver-xorg-video-ati

I plug my thinkpad t41 incl. ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] to a video projector, then boot the notebook (the only way X and linux detect an external monitor). X does not regonize the resolution of the beamer (feisty and tribe4 tested) (e.g. NEC NP100, but others are effected, too) (hint: X of feisty does not detect the available resolutions of the notebookdisplay, but gutsy tribe4 does).
Result: the virtual X desktop is bigger than the used physical resolution, not useable to watch movies and not usable for presentations

[Dominik Holler (dominik-holler)]

my workaround: book connected to an usual externel screen, while X is running plug out the screen, and plug in the projector

[Dominik Holler (dominik-holler)]

my workaround: booT connected to an usual externel screen, while X is running plug out the screen, and plug in the projector

[Bryce Harrington (bryce)]

Can you please test using the .debs here? http://people.ubuntu.com/~bryce/Testing/ati/

The version of -ati currently in Gutsy and Feisty do not have randr 1.2 support for allowing projector hotplugging. The 6.7.192 -ati does have xrandr 1.2 for things like projector hotplugging, and we're evaluating inclusion of it into Gutsy. So your testing feedback of this would be quite valuable.

[Dominik Holler (dominik-holler)]

Hi,
thx for rapid replying.
I'll test the following:
1. boot gutsy with projector connected, to see if the problem occurs with that projector
2. install your xserver-xorg-video-ati_6.7.192-1ubuntu1_i386.deb on gutsy
3. reboot gutsy with projector connected, to see if the problem is still there
4. reboot gutsy without projector connected, log in, connect beamer, see what happens, play with the new gtk-xconfig-tool

would this be good ?

I am not sure if I have got access to an beamer next time, but I will have a look for.

[Dominik Holler (dominik-holler)]

today I tested unsing a projector and an external screen,
first I booted connected to projector on feisty - works in correct resolution
then I booted gutsy (updates of yesterday) - still works, but the gtk-x-config tool does not ,,see" the projector, I tried to set up Xinemara using the tool, but does not work (but written the xorg.conf)
then I installed bryce's xserver-xorg-video-ati_6.7.192-1ubuntu1_i386.deb, restarted X, an X does not start again, a reboot does not help. (xorg.conf + Xorg.0.log attached)

I unplugged the projector, remove the xorg.conf and X start again. After a sudo dpkg-reconfigure xserver-xorg X was still working. I pluged in an external screen, and played around with the gtk-x-config-tool, but the external screen stayed black, an my Notebookdisplay gets wrong resolutions.
After rebooting and new a new xorg.conf things get not better: the external screen was used in colone-mode (Screenshot-3.png), and try to get cinemara unsing the config-tool behave like first time.

[Brian Murray (brian-murray)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. In the development cycle for Intrepid there have been some vast improvements in the open source ati video driver and we could use your help testing them. Could you please download the latest Alpha CD image of Intrepid and test this particular bug just using the Live CD? You can find the latest image at http://www.ubuntu.com/testing . Your testing can help make Ubuntu and the open source ati driver even better! Thanks in advance.

[Bryce Harrington (bryce)]

Hi dominik, it's been some time since we last heard from you - are you still interested in this bug? If so, it'd be great if you could re-test it against intrepid, and provide the info mentioned above. Otherwise, we'll close this as expired.

[Dominik Holler (dominik-holler)]

The projectors are no longer available, but I will get the notebook again, and test with an other projector using interpid as soons as a life cd is available.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.