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'm running it now and it seems more responsive for everyday desktop use. However when under heavy load it seems poorer and more jittery, I think its because of the switch to the anticipatory io scheduler.
So I think better for desktops, not so much for number crunching.
this nvidia patch you speak of...... linkie please??
other than the nvidia driver it works great nothing seems to be wrong except for a few warnings regarding my soundcard during compilation, but that works just great, in spite of the warnings...
I'm running without pre-emt and wanted to do some benchmarking of quake3 but.. that wouldn't be entirely fair considering that the nvidia driver isn't working.
my only problem being that I just compiled 2.8.1 yesterday.
There are two patches listed here. http://kerneltrap.org/node/view/4022 . I don't know how well they work, I have a crappy SiS315Pro. The "Pro" stands for "no hardware acceleration".
thanks muchly!! google wasn't much of a help in this particular area..
sure hope nvidia gets their act together and I don't have to go through this complete crap
and on a side note the nv driver just crapped out on me. I'm rather impressed with this series of events
after the patch to 2.6.9 from 2.6.8.1, uname identified it as still a 2.6.8.1 and couldn't ssh out(got a "ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory" error) or use cat.
I compiled from full source, and took care of the identification problem but the other two were still there. installed 2.6.6 and all is fine. I used the same .config from the 2.6.8.1 except minus a few net drivers. I tried looking through the config but didn't see anything that looked relevant to ssh.
Don't know if it is the kernel module or something else, but the emu10k1 driver for SBLive caused problems with artsd (1.3.1/KDE 3.3.1). In threaded mode the system completely hangs. But alsa works fine with this card as far as I can see now. Not a real problem as OSS is deprecated any way.
k3b 0.11.17 still does not work as normal user, but maybe I use some old version cdrecord or something...
I used the Driver-patch from http://ngc891.blogdns.net/index.php?...nvidia-drivers and it works perfectly.
Other than that I can find no differences to 2.6.8 in everyday desktop-use.
Did anyone request more WiFi support for the newest kernel? I'm sick and tired of trying to use ndiswrapper and madwifi. 802.11b and 802.11a have been out for a long time now. Inherent Linux support should be the norm by now. And yes I do know about vendors being tight-wa** and not wanting to release Linux drivers.
compiling from source of 2.6.8.1 worked fine but with 2.6.9 stops:
root@blue:/usr/src/linux-2.6.9# make menuconfig
HOSTCC scripts/basic/fixdep
In file included from scripts/basic/fixdep.c:105:
/usr/include/sys/types.h:27:22: features.h: No such file or directory
In file included from /usr/include/sys/types.h:31,
from scripts/basic/fixdep.c:105:
/usr/include/bits/types.h:27:22: features.h: No such file or directory
In file included from /usr/include/bits/types.h:31,
from /usr/include/sys/types.h:31,
from scripts/basic/fixdep.c:105:
/usr/lib/gcc-lib/i486-slackware-linux/3.3.4/include/stddef.h:213: error: syntax error before "typedef"
In file included from scripts/basic/fixdep.c:105:
/usr/include/sys/types.h:133:18: time.h: No such file or directory
/usr/include/sys/types.h:158:20: missing binary operator before token "("
In file included from scripts/basic/fixdep.c:106:
/usr/include/sys/stat.h:26:22: features.h: No such file or directory
In file included from scripts/basic/fixdep.c:106:
/usr/include/sys/stat.h:103: error: parse error before "__BEGIN_DECLS"
In file included from /usr/include/sys/stat.h:105,
from scripts/basic/fixdep.c:106:
/usr/include/bits/stat.h:36: error: syntax error before "struct"
In file included from scripts/basic/fixdep.c:106:
/usr/include/sys/stat.h:208: error: parse error before "__THROW"
/usr/include/sys/stat.h:212: error: parse error before "__THROW"
/usr/include/sys/stat.h:255: error: parse error before "__THROW"
/usr/include/sys/stat.h:272: error: parse error before "__THROW"
/usr/include/sys/stat.h:281: error: parse error before "__THROW"
/usr/include/sys/stat.h:293: error: parse error before "__THROW"
/usr/include/sys/stat.h:319: error: parse error before "__THROW"
/usr/include/sys/stat.h:321: error: parse error before "__THROW"
/usr/include/sys/stat.h:323: error: parse error before "__THROW"
/usr/include/sys/stat.h:351: error: parse error before "__THROW"
/usr/include/sys/stat.h:357: error: parse error before "__THROW"
/usr/include/sys/stat.h:358: error: syntax error before '{' token
/usr/include/sys/stat.h:370: error: parse error before "__THROW"
/usr/include/sys/stat.h:371: error: syntax error before '{' token
In file included from scripts/basic/fixdep.c:107:
/usr/include/sys/mman.h:23:22: features.h: No such file or directory
In file included from scripts/basic/fixdep.c:107:
/usr/include/sys/mman.h:58: error: syntax error before "extern"
/usr/include/sys/mman.h:59: error: parse error before "__THROW"
/usr/include/sys/mman.h:77: error: parse error before "__THROW"
/usr/include/sys/mman.h:82: error: parse error before "__THROW"
/usr/include/sys/mman.h:87: error: parse error before "__THROW"
/usr/include/sys/mman.h:101: error: parse error before "__THROW"
/usr/include/sys/mman.h:104: error: parse error before "__THROW"
/usr/include/sys/mman.h:109: error: parse error before "__THROW"
/usr/include/sys/mman.h:113: error: parse error before "__THROW"
In file included from scripts/basic/fixdep.c:108:
/usr/include/unistd.h:26:22: features.h: No such file or directory
In file included from scripts/basic/fixdep.c:108:
/usr/include/unistd.h:28: error: parse error before "__BEGIN_DECLS"
In file included from scripts/basic/fixdep.c:108:
/usr/include/unistd.h:260: error: syntax error before "extern"
/usr/include/unistd.h:260: error: parse error before "__THROW"
/usr/include/unistd.h:290: error: parse error before "__THROW"
/usr/include/unistd.h:306: error: parse error before "__THROW"
/usr/include/unistd.h:310: error: parse error before "__THROW"
/usr/include/unistd.h:313: error: parse error before "__THROW"
/usr/include/unistd.h:353: error: parse error before "__THROW"
/usr/include/unistd.h:362: error: parse error before "__THROW"
/usr/include/unistd.h:371: error: parse error before "__THROW"
/usr/include/unistd.h:389: error: parse error before "__THROW"
/usr/include/unistd.h:394: error: parse error before "__THROW"
/usr/include/unistd.h:409: error: parse error before "__THROW"
/usr/include/unistd.h:423: error: parse error before "__THROW"
/usr/include/unistd.h:441: error: parse error before "__THROW"
/usr/include/unistd.h:444: error: parse error before "__THROW"
/usr/include/unistd.h:456: error: parse error before "__THROW"
/usr/include/unistd.h:467: error: parse error before "__THROW"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.