Summary: | ati/radeon 6.7.193 drivers doesn't work with macmini (RV280) | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Alex Muntada <alexm> | ||||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||
Severity: | major | ||||||||
Priority: | medium | CC: | alexm, broonie, magnade | ||||||
Version: | 7.2 (2007.02) | ||||||||
Hardware: | PowerPC | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Alex Muntada
2007-09-22 09:29:27 UTC
Created attachment 11684 [details]
Xorg.0.log using latest git code
Just compiled and tried xf86-video-ati from git master (commit 5a6f74103f0ec0d451d0e2573442efe5922848af) and it doesn't work either. I'm attaching the Xorg.0.log.
For the record, I previously reported this bug in Ubuntu Gutsy: https://bugs.launchpad.net/bugs/141372 The mac mini needs a custom connector table like most other macs. What connectors does it have? based on apple's web site, it looks like it has just a DVI port that can drive DVI or VGA or tv-out (via DVI adapters). I'm guessing it uses internal TMDS and the TV DAC. The question is what ddc line it uses. Does adding the following option in the device section of your config help? Option "ConnectorTable" "X,1,0,3,0,1,2,6" replace X with 1 or 2 or 3 or 4 or 5 until you get DDC working. Once we sort this out, I'll add a MacModel option for the mini. Mine has just a DVI port with a DVI-to-VGA adapter. I tried the ConnectorTable option with 1..5 values without success. All values seemed to have the same result: ... (EE) RADEON(0): No valid modes. (II) UnloadModule: "ati" (II) UnloadModule: "radeon" (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found However, for X=4 X didn't end with an error though the screen went to sleep mode (I guess that's because it was receiveing bad values). I kept all 5 Xorg.0.log files; let me know which one would help or whether I should try different values in ConnectorTable. Thanks a lot! Having a similar problem with a Mac Mini I found that Option "ConnectorTable" "4,1,0,3,0,1,2,6" caused DDC to kick into life, though I am still experiencing problems with this as discused in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443570 (which appear to match the problem that Alex is seeing). The machine is: machine : PowerMac10,2 motherboard : PowerMac10,2 MacRISC3 Power Macintosh detected as : 287 (Unknown Intrepid-based) (I should probably add that the information read via DDC does look accurate for my monitor.) (In reply to comment #5) > Having a similar problem with a Mac Mini I found that > > Option "ConnectorTable" "4,1,0,3,0,1,2,6" > > caused DDC to kick into life, though I am still experiencing problems with this > as discused in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443570 (which > appear to match the problem that Alex is seeing). perhaps it's using external TMDS, try: Option "ConnectorTable" "4,1,1,3,0,1,2,6" This one worked wonders, though the cursor issue from bug #11796 is shown. (In reply to comment #8) > This one worked wonders, though the cursor issue from bug #11796 is shown. > So to confirm, Option "ConnectorTable" "4,1,1,3,0,1,2,6" (external TMDS) fixes the display for you? (In reply to comment #8) > This one worked wonders, though the cursor issue from bug #11796 is shown. > Also is this with DVI or VGA connection? Created attachment 11686 [details]
working Xorg.0.log
The attached Xorg.0.log confirms that Option "ConnectorTable" "4,1,1,3,0,1,2,6" (external TMDS) fixes the DVI-to-DVI display on my MacMini.
Excellent. Fixed upstream: 81114af1cdddc0b10d076f2e38c7a00c1223cc48 With ati git master Option "MacModel" "mini" should do the right thing automatically. Just recompiled latest git master to confirm that Option "MacModel" "mini" works fine with my DVI-to-DVI display. Thanks a lot! |
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.