radeon mobility x1600 broken since 3.4.0-rc6 (bisected)

Hausensteiner Keg skitching at apache.org
Mon Aug 27 12:04:02 PDT 2012


On 27/08/12 20:29, Jerome Glisse wrote:
> On Sun, Aug 26, 2012 at 8:34 PM, Hausensteiner Keg <skitching at apache.org> wrote:
>> After some more experimenting with different versions, I'm getting odd
>> results. So feel free to ignore this report..
>>
>> FYI, what I see is:
>> * as noted, commits before bb6355 work fine (ie up to 3.4-rc6).
>> * including commit bb6355, graphics freeze on the first transition after
>> grub (Plymouth?)
>> * the very next commit makes the (plymouth?) splash screen work, but the
>> greeter screen display is corrupted; ctrl-alt-f2 works - if pressed
>> immediately
>> * this situation continues up until release v3.5^. But building v3.5 itself
>> works perfectly! Presumably I've done something wrong here..
>> * v3.6-rc3 displays the splash (plymouth?) screen fine, but instead of a
>> greeter screen, screen goes blank.
>>
>> I'll try to make some more sense of this in the next few days - but
>> suggestions are welcome.
>>
>> Sorry if I'm posting this in the wrong place - let me know if I should
>> create a bugzilla entry or whatever.
>>
>> Regards,
>> Simon
>>
> Does patch
>
> http://people.freedesktop.org/~glisse/0001-drm-radeon-extra-type-safe-for-fence-emission.patch
>
> Helps ?

Thanks Jerome. Will try patch tonight or tomorrow morning.

How do I check whether the radeon is on an AGP bus?
The lspci output does not mention AGP; line for video controller is:
   01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee 
ATI M56P [Radeon Mobility X1600]
The "lshw" output also shows no signs of AGP.

The dmesg output contains "[0.909546] Linux agpgart interface v0.103" 
but otherwise no mention of "agp" or "AGP".

By the way: tested the 3.5.3 release made today : still corrupt 
graphics. And the v3.5 release (which was oddly working) also showed the 
same corrupt graphics as soon as I forced a rebuild of the initrd - 
maybe an older radeon module somehow ended up in the initrd built by 
"make-kpkg --initrd".

Regards,
Simon


More information about the dri-devel mailing list