Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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 am relatively new to this comile-my-own-kernel stuff ... but mostly works good for me.
I was always just trying some little things, like an openMosix-patch or so... and when I compiled always some little things were not pefect but it was ok, as long as it was a test and the tested thing was ok. ...
But now I have a big problem.
I compiled a 2.4.26 kernel, which is the same as the working one, with the /boot/config-ide-2.4.26 as config. Well, it started but I have no sound (erorr comes later) ... well ok... I had exactly this errormessage beofre...
So I rebooted my old kernel (which I did not touch nor change somethin in it's section in lilo.conf) and... DAMN! The same error message!!!
Like I said, this error wasn't new to me, but until now it did not effect the system when I booted my old working kernel...
Since I never had to deal with Linux's sound system I know NOTHING about it. It always worked after the install
So, now here's the Error-Dialog coming up when KDE's login is over:
------------- Informativ - aRts-Meldung ------------------------------------------------
Sound server information message:
Error while initializing the sound driver:
device: default can'T be opened for playback (No such device)
The sound server will continue, using the null output device.
------------------------------------------------------------------------------------------
Don't know what the heck I can do against that
Is it possible, that "make mrproper" killed something off?
As additional information: Slackware 10.0 on Fujitsu Siemens Amilo A
Any help is welcome!
Greetings, Sascha
Last edited by theonebeyond; 09-21-2004 at 07:22 AM.
Hmm...
Ok, for I am not sure how to do all this... here is what I#ve done so far:
lsmod shows me a loaded module 'via-rhine' don't know if thats something usefull/needed but it's the only thing in that direction...
Then, in /etc/rc.d/rc.modules is an out-commentet line which would load the module 'via82cxxx_audio' (along others) and I think I remember to have seen somthing with via...
Now I tried to modprboe exactly that module but.... not found...
modprobe: can't locate module via82cxxx_audio
Ok... and I looked into /lib/modules/2.4.26/kernel/drivers/sound ... there are a lot of entries ( .o ) but nothing with via...
I tired to locate somthing with via on my system... but I can only find it in /usr/src/linux/drivers/sound/ ....
In my /usr/src/linux/.config I have turned on "Sound card support" ... and "VIA 82C686 Audio Codec" but not "VIA82c686 Midi" ...
I don't know if this will help you, but via82cxxx_audio is the OSS driver, and via82xx is the ALSA driver. AFAIK, you should use via82xx, and check in /etc/modules.conf that it is spelled correctly.
It seems to me, that this damn module simply isn't there ... god knows why...
I did a 'find / -name *via82* ' and a lot of via82cxx were found. the only via82xx.* that were found are from the kernel 2.6.8.1 sources ... but thats by far not the one I am dealing with ...
2.4.26 does only have a lot of via82cxxx.* file...
but I have no clue how I could solve this problem...
Maybe I have to patch it into the kernel????
So frustrating :-)
Sascha
Last edited by theonebeyond; 09-22-2004 at 06:58 AM.
At the top of your linux kernel tree (usually /usr/src/linux), there is the file .config; open this file and locate the comment stating that this module is not built, and change it so that it is built as a module.
Well alsamixer won't come up... and the channels are Muted... I know ... but that isn't the point ... I am still getting this damn error on kde-login ( look into my first post) and the damn module just can't be loaded...
modprobe snd-via82xx tells me:
/lib/modules/2.4.26/kernel/sound/acore/snd.o: unresolved symbol unregister_sound_special
/lib/modules/2.4.26/kernel/sound/acore/snd.o: unresolved symbol register_sound_special
/lib/modules/2.4.26/kernel/sound/acore/snd.o: insmod /lib/modules/2.4.26/kernel/sound/acore/snd.o failed
/lib/modules/2.4.26/kernel/sound/acore/snd.o: insmod snd_via82xx failed
Hell, I don't know why the install routine from alsa doesn't put the module where it belongs or whatever the problem is ...
Thanks for all your time! I'll have to go for now... but I#ll be back tomorrow ... thanks for your help 10000000 times so far! :-)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.