Re: radeon r300
Kevin Bowling <[email protected]> Sat, 17 Jan 2026 19:41:35 -0700
| Newsgroups | gmane.os.netbsd.devel.x11 |
|---|---|
| Message-ID | <CAK7dMtA12bMsFy+22cMSwCeX3f748qdFHa_bTUk1N-jqyhz_SA@mail.gmail.com> |
On Sat, Jan 17, 2026 at 4:28=E2=80=AFAM Robert Swindells <[email protected]> w= rote: > > > Kevin Bowling <[email protected]> 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. If I boot with userconf to disable radeondrm, X seems to only come up in VESA so not sure if another config is needed for user mode setting or if that has been deprecated. Regards, Kevin