drm/radeon issues with ATi X300

Nathan Lay nslay at comcast.net
Mon Dec 24 13:57:48 PST 2007


I updated 7.0 (world and kernel) today and applied the provided patch.  
Enabling AIGLX no longer crashes the system, but instead the screen 
corruption persists.  Any ideas?

Best Regards,
Nathan Lay

Adam K Kirchhoff wrote:
> The AIGLX crash is a known issue.  There's a patch here: 
> https://bugs.freedesktop.org/show_bug.cgi?id=11870
>
> As for the graphics corruption.  This is a PCIe card, correct?  I had nearly 
> the exact same problem with 6.2 (though with my problem, restart X never 
> fixed it), and it was fixed (for me) in -CURRENT sometime in the last year.  
> I've had a similar problem with an AGP card when my AGP gart size was set 
> higher in my xorg.conf file than it was in my BIOS.
>
> Adam
>
> On Monday 24 December 2007 01:52:18 Nathan Lay wrote:
>   
>> Hi list,
>> I'm having a couple issues with drm/radeon with ATi X300 (RV370, M22)
>> card on an IBM Thinkpad T43 on both FreeBSD 6.2 and 7.0-BETA4 with Xorg
>> 7.3.  The first issue is initially (immediately after a boot) the
>> graphics are corrupt, though upon restarting X the corruption vanishes.
>> Here is a screenshot of the corruption
>> http://img171.imageshack.us/img171/1073/desktopfo9.png
>>
>> Secondly, enabling AIGLX crashes the system.  Upon a startx, the screen
>> goes black for about 5-10 seconds, then the system reboots.  I have
>> attached xorg.conf and Xorg.0.log generated by Xorg on FreeBSD
>> 6.2...again, the same behavior is seen on FreeBSD 7.0-BETA4.
>>
>> Here is pciconf's output
>> drm0 at pci1:0:0:  class=0x030000 card=0x056e1014 chip=0x54601002 rev=0x00
>> hdr=0x00
>>     vendor   = 'ATI Technologies Inc'
>>     device   = 'Mobility Radeon X300'
>>     class    = display
>>     subclass = VGA
>>
>> drm/radeon attaches and prints
>> drm0: <ATI Radeon Mobility X300 M22> port 0x3000-0x30ff mem
>> 0xc0000000-0xc7ffffff,0xa8100000-0xa810ffff irq 16 at device 0.0 on pci1
>> info: [drm] Initialized radeon 1.24.0 20060225
>>
>> I have additionally attached my dmesg.
>>
>> I searched Google and lists and didn't find much.  Has anybody else had
>> these problems?  Is there anymore information I can provide to help
>> pinpoint the problem?
>>
>> Best Regards,
>> Nathan Lay
>>     
>
>
>
>   



More information about the freebsd-x11 mailing list