[SOLVED] Xorg problem after upgrade in CURRENT x86_64
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.
Just to remark that one should not run CURRENT if he can't deal with things like this. Someday one thing or another will break up.
It's not Pat or anyone's fault. If you want things stable you should run STABLE.
By definition CURRENT is a test/development branch, where we the users test the whole thing up for future inclusion in the next RELEASE.
In my opinion, Slackware CURRENT has had fewer breaks after upgrades than any other "rolling release" like Arch, etc.
Keep the great work. We are gratefull.
This week, I've had several hard lockups (and one unexpected system reset) which I suspect are graphics driver related while using a local build of the 4.1.6 kernel running on top of Slackware64-14.1 (nouveau not intel though). Not seeing them with the 3.14.y kernel branch, so I'm somewhat uneasy about the 4.1.y kernels at present.
I don't know if I should open a new thread but after updating today my Xorg fails with an error saying
"libEGL.so.1 not found" I'm using openbox.
Perhaps it has something to do with another error I'm getting.
When I ran find to see if libEGL.so.1 existed I got this:
find: WARNING hard link count is wrong for /proc/fs
I don't know if I should open a new thread but after updating today my Xorg fails with an error saying
"libEGL.so.1 not found" I'm using openbox.
Perhaps it has something to do with another error I'm getting.
When I ran find to see if libEGL.so.1 existed I got this:
find: WARNING hard link count is wrong for /proc/fs
so, if any of you have intel hardware and got problems, please try this updated driver (I add also the mesa package for convenience) and report if it fixes for you...
Thanks a lot, ponce. X windows works well again on my 64 bit box running Intel graphics hardware using your updated software.
This week, I've had several hard lockups (and one unexpected system reset) which I suspect are graphics driver related while using a local build of the 4.1.6 kernel running on top of Slackware64-14.1 (nouveau not intel though). Not seeing them with the 3.14.y kernel branch, so I'm somewhat uneasy about the 4.1.y kernels at present.
Just ten minutes ago I had a hard lockup with 3.18.11 - Slackware64-current as of 9th August, clean install, nouveau driver.
Had intended to update to the latest -current plus Nvidia driver today but held back when I learned of the mesa problem.
I had been running -current before today's clean install for some months without an issue, although that was with Nvidia 's driver.
so, if any of you have intel hardware and got problems, please try this updated driver (I add also the mesa package for convenience) and report if it fixes for you...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.