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.
Running just fine, but I don't have stock Slackware. I'm currently using Slackware-Current i486, with updated kernel (stock 2.6.30.3) and latest NVidia drivers (beta 190.18).
KDE4 with Compiz Fusion - no artifacts, smooth work, no strange errors, no freezes, cores or similar troubles
Running just fine, but I don't have stock Slackware. I'm currently using Slackware-Current i486, with updated kernel (stock 2.6.30.3) and latest NVidia drivers (beta 190.18).
In that case the information is useless. This needs to be tested (as stated a few times before in this thread) against -current (both x86 and x86_64 if possible) with huge-smp-2.6.29.6-smp or generic-smp-2.6.29.6-smp, as those are the supported kernel version.
Besides, the proprietary nVidia drivers overwrite Mesa's libGL.so, does not use libdrm, and has it's own kernel-side driver anyway, so if it works for one user (see above) it does in all probability work for all the others too.
I am using 32bit -current with an ati x1400 and the radeonhd driver in my laptop. I was having a few problems with the setup in -current such as the machine would lock-up when I exited x, even with ctrl-alt-backspace. With these testing packages the problems I was having have disappeared, so everything seems good now with my setup.
I can't startx without a xorg.conf like others have reported, but that doesn't bother me.
I've tested the packages on my laptop with the intel graphic 945GME. I use slackware-current with the stock kernel (2.6.29.6-smp), first I've upgraded all packages except the intel driver, but the graphic was as slow as before.
Then I've tried the intel driver 2.8.0, now everything is fine (with 2.7.1 i had only 50 FPS, with 2.8.0 I've got more than 300FPS).
Now I can play torcs race with my laptop :-)
Thanks to everyone involved in the testing and feedback; without that, we'd not have known whether it was a good idea to take the risk of putting this new stuff in -current.
Thanks to everyone involved in the testing and feedback; without that, we'd not have known whether it was a good idea to take the risk of putting this new stuff in -current.
It will be great if Eric post something like"[TESTING REQUEST] KDE4.3 in -current(yes, it is)" ;D
I finally got around to installing current on my T400 Thinkpad (Intel G45 chipset). Can't complain.
Without an xorg.conf, startx gave me my native resolution of 1280x800. There was no screen tearing when I set xine to use the xv driver and watched several of my AMVs. World of Goo's performance was good (certainly not the stuttering I would get with software rendering). My mouse wheel worked with as both a wheel and a button. The computer did not crash when I switched from X to a virtual console. The computer did not crash when I exited X. Xfce's performance was as fast as expected.
Running glxgears for two iterations produced the following:
Code:
2422 frames in 5.000 seconds = 484.400 FPS
1711 frames in 5.000 seconds = 342.200 FPS
The file produced by "X -configure" didn't work (blank screen). xorgsetup did produce an xorg.conf file that worked just as well as not having one .
This was with the stock Slackware kernel (2.6.96.6-smp) and the 2.8.0 intel driver, of course.
Odd that the "X -configure" produced xorg.conf doesn't work -- as I understand it, that's basically the "virtual" xorg.conf used if one doesn't exist :/
Perhaps try with the 2.7.1 intel driver -- the 2.8.0 is (according to upstream) better for 2.6.30+ (and really 2.6.31rc) kernels.
I can't duplicate the problem with the non-working xorg.conf (it seems to have started working now). However, the 2.7.1 driver gives me really bad performance in both glxgears and World of Goo:
Code:
298 frames in 5.011 seconds = 59.469 FPS
300 frames in 5.002 seconds = 59.976 FPS
300 frames in 5.002 seconds = 59.976 FPS
I can't duplicate the problem with the non-working xorg.conf (it seems to have started working now).
Of course - isn't that how it goes? :-)
Quote:
However, the 2.7.1 driver gives me really bad performance in both glxgears and World of Goo:
Code:
298 frames in 5.011 seconds = 59.469 FPS
300 frames in 5.002 seconds = 59.976 FPS
300 frames in 5.002 seconds = 59.976 FPS
That's not entirely unexpected re glxgears - the changes they made to it result in a "performance" matching the monitor's refresh rate quite often, so I trust the World of Goo game more than glxgears. Try creating an xorg.conf and specify UXA acceleration in it to see if that makes a difference.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
