SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I finally discovered the cause of a bug that forced me to reboot daily: My ATI patches!
I'm using Slackware 9.1
Fujitsu P 2110 notebook
ATI Rage Mobility
There is a beautiful patch http://www.retinalburn.net/linux/ that I had used in 9.0 to get XV and GL support. It still works in 9.1, but after a while of use causes a terrible (daily) crash, something involving "Xlib" and "BadLength". I neet do reboot to get X working again.
So!
Has anyone else had this problem? Does anyone know of a fix / different patch?
Tricky_linux, I have XV and and GL support now. I just don't know what is causing the bug. I am not using Mandrake Linux. I'm using Slackware Linux 9.1. You sound very confused.
Anyway, here is my logic: If X worked great in 9.0, but X dies a horrible death in 9.1, then I will use the X packages from 9.0. I'll report back soon!
I've been using Slackware since 8.0. I did a full install of Slackware 9.1 onto a clean harddisk on my Fujitsu P2110 laptop.
The problem is, after a random number of days, X would DIE, saying:
wmaker warning: internal X error: BadLength (poly request too large or internal Xlib length error)
Request code: 18 X_ChangeProperty
Request minor code: 0
Resource ID: 0x48
Error serial: 5873
X was unable to be started again until I rebooted. (...reboot? ...in Linux??) >:O This would happen every few days.
My solution: X worked in 9.0. X dies in 9.1. So, since both Slackwares are using X 4.3.0, I simply installed the 9.0 X packages over my 9.1 X package installation.
The only big difference I found between the X in 9.0 and 9.1 is the 9.1 uses the new freetype2 and fontconfig, but if you just install the 9.0 X over the 9.1 X then it's no problem.
Sorry, it's kind of a yucky solution, but it works. Here's hoping for Slackware 10!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.