[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Xorg fails on ATI after update (mmio aperture)



Please re-read what I wrote. I never claimed it's a KMS driver.

> On Mar 6, 2017, at 4:05 AM, Michel Dänzer <michel@daenzer.net> wrote:
> 
>> On 04/03/17 04:49 AM, John Paul Adrian Glaubitz wrote:
>>> On 03/02/2017 07:44 PM, Riccardo Mottola wrote:
>>> [    4.174055] atyfb 0000:00:10.0: enabling device (0086 -> 0087)
>>> [    4.174138] atyfb: using auxiliary register aperture
>>> [    4.174809] atyfb: 3D RAGE Mobility L (Mach64 LN, AGP 2x) [0x4c4e rev 0x64]
>>> [    4.174896] atyfb: 4M SDRAM (2:1) (32-bit), 14.31818 MHz XTAL, 230 MHz PLL, 70 Mhz MCLK, 53 MHz XCLK
>>> [    4.180172] aty: Backlight initialized (atybl0)
>>> [    4.180787] atyfb: monitor sense=0, mode 20
>> 
>> Your machine is loading the framebuffer kernel driver which will only work
>> when you configure X.Org to use the "fbdev" driver. You can either set your
>> display driver to "fbdev" (see further below) or disable the framebuffer driver
>> on the kernel command line with:
>> 
>>    video=atyfb:off
>> 
>> Then it should be possible to use the "mach64" driver *if* the kernel has
>> support for the hardware. However, looking at the information available in
>> the X.Org wiki [1], it seems the mach64 DRM module is currently not part of
>> the Linux kernel, so the fbdev driver might be your only option.
> 
> John, what you're writing would apply if mach64 was a KMS kernel driver,
> but it's not; it predated KMS by a long shot.
> 
> xf86-video-mach64 works without the mach64 kernel driver. It may or may
> not work with the atyfb kernel driver — there's no particular reason why
> it couldn't.
> 
> Somebody should probably try isolating the kernel change which broke
> Riccardo's setup.
> 
> 
> -- 
> Earthling Michel Dänzer               |               http://www.amd.com
> Libre software enthusiast             |             Mesa and X developer


Reply to: