Created attachment 16594 [details] xf86MapVidMem error hello, radonhd 1.2.1 driver has worked nicely with the 2.6.25 kernel but no more with the last 2.6.26-rc2 kernel. However, i didn't recompile all xorg tools. The new PAT option has been activated in the new 2.6.26 kernel. CONFIG_MTRR=y CONFIG_X86_PAT=y Please, see attachement.
Egbert, any ideas here?
(In reply to comment #1) > Egbert, any ideas here? > Not really. The size of the mapped range is 256MB which is the size of the BAR aperture and should be OK. One could try and replace VIDMEM_FRAMEBUFFER by VIDMEM_MMIO in rhd_driver.c:rhdMapFB() for testing. This would essentially disable the mtrr setup.
Doesn't seem to be a bug of our driver: http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-05/msg04111.html http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-05/msg04413.html
Seems to be fixed in the kernel with http://linux.derkeiler.com/Mailing-Lists/Kernel/2008-05/msg03361.html So, not our bug :)
Thank you for your fast reply. I'm glade to see it is not a bug of yours but more like a kernel issue and i will see after the links you kindly suggest :) Although both computers have PAT activated. The issue has probably something to do with how many of ram is installed in the computer. 4Go seems to lead to some troubles :( For instance, cat /proc/mtrr reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1 reg01: base=0x80000000 (2048MB), size=1024MB: write-back, count=1 reg02: base=0xc0000000 (3072MB), size= 256MB: write-back, count=1 reg03: base=0xcff00000 (3327MB), size= 1MB: uncachable, count=1 reg04: base=0x100000000 (4096MB), size= 512MB: write-back, count=1 reg05: base=0x120000000 (4608MB), size= 256MB: write-back, count=1 reg06: base=0xd0000000 (3328MB), size= 256MB: write-combining, count=1 and PAT activated, xorg doesn't work cat /proc/mtrr reg00: base=0x00000000 ( 0MB), size=2048MB: write-back, count=1 reg01: base=0xc0000000 (3072MB), size= 256MB: write-combining, count=3 and PAT activated, xorg works. (although it isn't the same computer) I hope the patch will soon be integrated in the new kernel release. Thanks
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.