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 compiled 2.6.11.3 and have it running without any problem on Slackware-current, just took me an hour to have it setup and running with NVidia drivers, lm_sensors and ALSA.
Try updating udev to the latest version since there were some bugs on the previous ones.
Oh I just remembered a thing that called my attention, when I booted it told me DMA wasn't enabled and I didn't want to make hdparam on every boot since it didn't seem correct so I made a deep search and there's a option inside the kernel configuration to activate DMA automatically if it's available. Besides there wasn't anything wrong.
Popescu Mihai: The forum rules do not permit advertising. Please visit http://www.linuxquestions.org/advertising/ for more information on advertising. Feel free to contact the forum admin if you have any questions about this policy.
well...with the 2.6.11-kernel all devices in the dir. /dev/sound are made again at boot.
with 2.6.10 that didn't happen.
and just installed the .3.........
no crashes using tv, mozilla, jack+synth and some consoles at the same time, so : ok to me.
but i was just bored, 2.6.9 was ( and is ) ok.
and i can't say i read, or even understand the changelog......
Running 2.6.11-rc4 on Slack 10 with no problems. Installed Nvidia's latest and greatest with no problems or patching this time!
This is, however, the first time that udev played nice. Must of been my compiling skills on the other attempts. I have the udev upgrade, but i haven't installed it yet.
2.6.11 does not work with the ATi drivers without patches. So those using ATi drivers currently would do better to wait until either ATi or the kernel developers fix this problem.
I am glad the nvidia and kernel people have got their act together (for now). It was becoming a bit annoying to have to hunt for patches over the web each time I updated the kernel.
im having the worst time trying to make sound work... because my devices are gone when i reboot :S, i guess is user problem, not software
i think it's the combination of kernel and udev.
i'm still using the "old" udev-050-i486-1. ( that didn' work with 2.6.10 but ok with 2.6.9 and 2.6.11 )
and carboncopy,
are you sure you need pppoe ?
what kind of modem do you have and how is it connected to your pc ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.