tech-x11 archive

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

Re: radeon r300



Kevin Bowling <kevin.bowling%kev009.com@localhost> wrote:
> On Sat, Jan 17, 2026 at 4:28 AM Robert Swindells <rjs%fdy2.co.uk@localhost> wrote:
> > Kevin Bowling <kevin.bowling%kev009.com@localhost> wrote:
> > > I get the following with 10.1 or NetBSD 11.0_BETA (GENERIC) #0: Thu
> > > Jan  8 10:53:08 UTC 2026
> > > when starting X:
> > >
> > > [   104.512784] radeon0: autoconfiguration error: error: ring 0
> > > stalled for more than 10000msec
> > > [   104.512784] radeon0: warn: GPU lockup (current fence id
> > > 0x0000000000000003 last fence id 0x0000000000000006 on ring 0)
> > >
> > I'm able to get a working session with this file added to
> > /etc/X11/xorg.conf.d/20-radeon.conf:
> > Section "Device"
> >        Identifier "Radeon"
> >        Driver "modesetting"
> >        Option "AccelMethod" "none"
> > EndSection
> >
> > With the modesetting default of AccelMethod "glamor", X will not start with:
> > glamor requires at least 128 instructions (64 reported)
> >
> > So it seems the older EXA radeon might be preferable, but something is
> > going wrong in the kernel.  Has anyone looked into this drm stuff
> > recently?
>
> What happens if you set AccelMethod to EXA in your 20-radeon.conf file?

> As far as I can tell only glamor is supported for modesetting.  If
> setting EXA here, X does start but llvmpipe is still somewhat used and
> things like glxinfo segfault.

Have you tried using the old radeon driver with EXA?

We build two versions of this, they get built as radeon_drv.* and
radeon_drv_old.* and live in the /usr/X11R7/lib/modules/drivers
directory.

To use the old one, rename radeon_drv.* to radeon_drv_new.* and
radeon_drv_old.* to radeon_drv.*.


Home | Main Index | Thread Index | Old Index