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 have 13.37 installed and am thinking of changing to it but I have had two system freezes with it. This never happens on 13.0. Once was when I was selecting reboot from kde and another time I was closing another program - I forget which.
I have this in kdm log and xorg.log
Quote:
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
Not enough details, but could be related to a common KDM bug that happens at log out.
Edit /etc/kde/kdm/kdmrc and un-comment TerminateServer=true.
This makes KDM actually restart the X server, rather than respawn/reset. Works around various bugs in Xorg, and some display drivers. Happens to me personally with Intel graphics.
It froze on me once while using google maps. All that worked was the cursor. I couldn't ctrl-alt-esc or ctrl-c or anything.
I hit the reset button before I remembered to try ctrl-alt-F2 or whatever closes X or changes the runlevel or whatever. I'll probably installing the nvidia driver anyway. I have no idea what caused the crash though. I've never seen that happen before.
I'm using a custom compiled 2.6.37.6, so I don't know about the generic kernel but I've been experiencing random freezes since 2.6.36 (this is an eeePC 1005HA). In my case I'm almost sure it's not about external software because all is fine if I boot with the 2.6.35 kernel. Still, I've had just one freeze with 2.6.37.6 which makes it the best so far. I tried to find clues in the logs about what goes wrong but I was unable to find any.
same issue multiple times over the weekend, locked where mouse can move, but nothing responds. Unable to kill X or tab out. This happened before and after I enabled the nouveau driver. Just havent had time to debug it yet.
I unwittingly was using nouveau for a while. It locked up my box twice. Once I got the binary NVIDIA driver running it's been rock solid as always. The version of nouveau with this kernel is not ready for prime time.
I had the same problems with nouveau. I used the nvidia driver from slackbuilds.org. The nvidia installer blacklisted the nouveau module for me automatically:
Quote:
matt@amd:~$cat /etc/modprobe.d/nvidia-installer-disable-nouveau.conf
# generated by nvidia-installer
blacklist nouveau
options nouveau modeset=0
The Nvidia drivers are always going to perform better. And if at some point they don't, nvidia should just stop making their drivers.
Nouveau is going to be good enough if you don't want anything fancy and are ok with 2D hardware accelerated graphics. I was fine with nouveau until I tried gnome 3 and the interface didn't display properly.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.