Created attachment 124199 [details]
Distro: Arch Linux
IBM Laptop: ThinkPad A21p
Also the system becomes completely unusable, it affects even the ttys, I can barely see the text. After reboot the screen stays black and white until I completely turn it off.
I can avoid the segfaults with configs, but that don't make me see the window manager.
Uh oh. I assume 6.9.2 was ok? What are the configs that prevent the segfault? Also, does the segfault go away if you keep the old configs but only use the internal panel?
Created attachment 130358 [details]
Xorg log file of the r128 driver crash on ThinkPad A20P
Created attachment 130361 [details]
Xorg configuration used
I ran into the same issue
Distro: Slackware 14.2
IBM Laptop: ThinkPad A20p
GPU: Rage Mobility 128 AGP 2X/Mobility M3 (rev 02)
I attached my Xorg config and Xorg log for details.
After the driver crashed the image on the screen became monochrome, and unreadable. After powering the unit off everything reverts back to normal.
The line jumping out at me from the log is the DRI failure because it needs 17325kB of memory. Was this line always there even in working instances from before? If not, it may be that the new driver is defaulting to a larger screen size and you need to change it.
I fixed the static buffer overflow by forcing the resolution down to 800×600 despite having a 1400×1050 monitor. I also disabled acceleration to be safe and have DRI causing no potential problems.
Xorg now starts succesfully but the screen is still black and showing all symptons as stated above.
> Was this line always there even in working instances from before?
The driver never worked, before I always used the VESA driver which is extremely slow.
(In reply to roderik from comment #12)
> > Was this line always there even in working instances from before?
> The driver never worked, before I always used the VESA driver which is
> extremely slow.
If all the times you tried were after 2014, you might want to compile commit 4efc87f41d770c753ddf7f54fe334b6dbd7daf79 to see if randr was the problem. And when you say you disabled acceleration, I assume you mean the 2D and 3D part (setting "NoAccel" to "true") so that we can rule out EXA as the problem.
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-r128/issues/10.