Summary: | RadeonHD not working with Mobility Radeon 3650 HD | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Glen Nelson <glen.nelson.1> | ||||||
Component: | Driver/radeonhd | Assignee: | Luc Verhaegen <lverhaegen> | ||||||
Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> | ||||||
Severity: | normal | ||||||||
Priority: | medium | CC: | c.overweel | ||||||
Version: | unspecified | ||||||||
Hardware: | x86-64 (AMD64) | ||||||||
OS: | Linux (All) | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Glen Nelson
2009-06-11 13:33:27 UTC
Created attachment 26695 [details]
Xorg.0.log as an attachment
Remove the Option "DRI" for the moment - there is no usable 3D support yet anyway. Otherwise it looks like the MC is going berserk... Removed Option "DRI" as well as the DRI section. Still no change in behavior. This is caused by the same MTRR issue that is causing Bug 20645. This bug is also posted on lauchpad: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-radeonhd/+bug/352050 That post seems to indicate that there is a workaround based on MTRR (See: http://lists.opensuse.org/radeonhd/2009-05/msg00070.html and http://lists.opensuse.org/radeonhd/2009-04/msg00253.html ), But I'm no where near good enough with Linux to try and do that myself. Anyone have any useful links or tutorials that could help me attempt it? Heres some additional information that might be helpful. From cat /proc/mtrr " reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back reg01: base=0x080000000 ( 2048MB), size= 1024MB, count=1: write-back reg02: base=0x100000000 ( 4096MB), size= 1024MB, count=1: write-back reg03: base=0x0ffe00000 ( 4094MB), size= 512KB, count=1: write-protect reg04: base=0x0bfe00000 ( 3070MB), size= 2MB, count=1: uncachable " from dmesg: "[ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f400 (usable) [ 0.000000] BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved) [ 0.000000] BIOS-e820: 00000000000d2000 - 00000000000d4000 (reserved) [ 0.000000] BIOS-e820: 00000000000d8000 - 0000000000100000 (reserved) [ 0.000000] BIOS-e820: 0000000000100000 - 00000000bf8b1000 (usable) [ 0.000000] BIOS-e820: 00000000bf8b1000 - 00000000bf8b7000 (reserved) [ 0.000000] BIOS-e820: 00000000bf8b7000 - 00000000bf9bc000 (usable) [ 0.000000] BIOS-e820: 00000000bf9bc000 - 00000000bfa0f000 (reserved) [ 0.000000] BIOS-e820: 00000000bfa0f000 - 00000000bfb08000 (usable) [ 0.000000] BIOS-e820: 00000000bfb08000 - 00000000bfd0f000 (reserved) [ 0.000000] BIOS-e820: 00000000bfd0f000 - 00000000bfd18000 (usable) [ 0.000000] BIOS-e820: 00000000bfd18000 - 00000000bfd1f000 (reserved) [ 0.000000] BIOS-e820: 00000000bfd1f000 - 00000000bfd64000 (usable) [ 0.000000] BIOS-e820: 00000000bfd64000 - 00000000bfd9f000 (ACPI NVS) [ 0.000000] BIOS-e820: 00000000bfd9f000 - 00000000bfde4000 (usable) [ 0.000000] BIOS-e820: 00000000bfde4000 - 00000000bfdfd000 (ACPI data) [ 0.000000] BIOS-e820: 00000000bfdfd000 - 00000000bfe00000 (usable) [ 0.000000] BIOS-e820: 0000000100000000 - 0000000140000000 (usable)" So Usable: 0 - 652288 1048576 - 3213561856 3213586432 - 3214655488 3214995456 - 3216015360 3218141184 - 3218178048 3218206720 - 3218489344 3218731008 - 3219013632 3219116032 - 3219128320 4294967296 - 5368709120 Both of these have been added as an attachment Created attachment 29537 [details]
MTRR and DMESG results
Does this issue occur with the preferred ati driver (xf86-vide-ati)? If so, please move this to the Driver/Radeon component. Development of radeonhd has pretty much halted and development focus is on the ati driver. Please see http://www.x.org/wiki/radeonhd If the issue does not exist in the ati driver (or if there is no response to this message), this bug will be closed as WONTFIX unless someone contributes a patch. Unfortunately I no longer have the laptop for which this was relevant, so the ticket should be closed. I will leave it to be marked as the proper status by someone else. |
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.