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 installed slackware 9.0 onto my sony fxa32 laptop.. everything is good, except when i start up kde, then i get a few assertion failed's in my syslog, and then it sometimes crashes. here are the assertions:
i checked the driver file, but i don't understand what these mean. any help, or any pointers on where to go for help, would be greatly appreciated.
i also get a lot of insmod errors when the system boots up, KMOD apparently tries and fails repeatedly to get my ethernet driver going, but i suspect its unrelated.
I dont know man, I tried forever to get the kernel sound driver to work with my via onboard sound...all i could get was CD sound. I just use alsa now, works fine.
About the insmod problem, I think, this is a think, its because on the default kernel it loads up alot of things just because it has to. Peoples systems vary so it loads stuff up for every system possible just about. On the stock kernel I was getting alot of errors like 'something something couldnt be found'. Just recompile the kernel and include stuff only for your pc.
Slack 9.0 introduce a new system for called hotplugging, if it was enabled during the install. The modules that are creating the errors can be added to the end of the /etc/hotplug/blacklist file to prevent them from being loaded. One common module has been with 8139cp and 8139too modules. In this case just add 8139cp to the end of the blacklist file.
Don't know about the VIA sound problem with the kernel drivers. Unless it is two programs competing for the same resource. For instance, KDE uses arts for system sounds etc. But if xmms is run with OSS or eSound configuration, xmms will lock up. Once arts daemon is killed then xmms will start working again. So I set KDE to not start arts when loaded. I still have the problem once in awhile, but I know what to look for. I have some apps that want to use arts only so I do not want to disable completely. If playing mp3 files then the program "noatun" will work with arts OK.
I'm using the drivers from www.viaarena.com in RH9 and everything seems to be fine except that in quake3 audio is very choppy (video is very good though). I was wondering if anyone had any ideas, xmms is fine, when using eSound, it sounds pretty bad when using OSS.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.