Hi, I have a quick question about alsasound and kernel modules. I was previously using the on-board sound of my Abit KT600 motherboard, which uses the via82xx sound chip. I wanted to try a different soundcard to see if it fixed some problems I am having, so disabled sound in the BIOS, and installed a Creative card (ensoniq 1371). Yast autodetected the card, but did not configure it properly, since the module for the via82xx hardware is still being loaded automatically by alsasound at boot time. I have checked, and Yast does not see the old hardware (via82xx), and there is no mention of it in either /etc/modprobe.conf or /etc/modprobe.d/sound. Yast does see the new card (en1371), and if I try to configure it with alsaconf it finds it aswell, but when it runs the alsasound startup script is loads 2 instances of en1371 and one of via82xx!!!!??? Why is the system still installing this driver? How can I "tell" the kernel not to bother looking for this bit of hardware? Is this indicative of something wrong with my system? Hope someone can work out what's going wrong. Cheers, Jon. -- Jonathan Brooks (Ph.D.) Research Assistant. PaIN Group, Department of Human Anatomy & Genetics, University of Oxford, South Parks Road, Oxford, OX1 3QX tel: +44(0)1865-282654 fax: +44(0)1865-282656 web: http://www.fmrib.ox.ac.uk/~jon
On Monday 04 April 2005 18:38, Jonathan Brooks wrote:
Why is the system still installing this driver? How can I "tell" the kernel not to bother looking for this bit of hardware? Is this indicative of something wrong with my system?
You neglected to mention which version of suse you are running, but I'm going to assume it's one with a 2.6 kernel, in which case you can force the kernel to ignore the module by inserting the line install via82xx /bin/true in /etc/modprobe.conf.local and running depmod I know that linguistically it looks backwards, but this will disable the loading. Aside from that, you can have a look in /etc/sysconfig/hardware, there should be a file there that loads the module. If you delete that file, it should also disable it, but the above will guarantee it
Hi Anders, Thanks for your suggestion - not sure if it worked though? You guessed right :) SuSE 9.1, kernel 2.6.5-7.151-default I edited modprobe.conf.local as you suggested, and typed depmod. To test this I then ran /etc/init.d/alsasound stop/start, here's the output: anat0005:/etc/init.d # ./alsasound start Starting sound driver: ens1371 Message from syslogd@anat0005 at Tue Apr 5 10:51:04 2005 ... anat0005 kernel: Disabling IRQ #12 ens1371 via82xx done Restoring the previous sound setting done I'm not sure if this the behaviour you expect to see? P.s. One of the things I have found necessary to get sound working on an identical machine is to add pci=noacpi to the boot command. Is this screwing things up?? Cheers, Jon. Anders Johansson wrote:
On Monday 04 April 2005 18:38, Jonathan Brooks wrote:
Why is the system still installing this driver? How can I "tell" the kernel not to bother looking for this bit of hardware? Is this indicative of something wrong with my system?
You neglected to mention which version of suse you are running, but I'm going to assume it's one with a 2.6 kernel, in which case you can force the kernel to ignore the module by inserting the line
install via82xx /bin/true
in /etc/modprobe.conf.local and running depmod
I know that linguistically it looks backwards, but this will disable the loading.
Aside from that, you can have a look in /etc/sysconfig/hardware, there should be a file there that loads the module. If you delete that file, it should also disable it, but the above will guarantee it
-- Jonathan Brooks (Ph.D.) Research Assistant. PaIN Group, Department of Human Anatomy & Genetics, University of Oxford, South Parks Road, Oxford, OX1 3QX tel: +44(0)1865-282654 fax: +44(0)1865-282656 web: http://www.fmrib.ox.ac.uk/~jon
On Tuesday 05 April 2005 11:57, Jonathan Brooks wrote:
Hi Anders,
Thanks for your suggestion - not sure if it worked though? You guessed right :) SuSE 9.1, kernel 2.6.5-7.151-default
I edited modprobe.conf.local as you suggested, and typed depmod. To test this I then ran /etc/init.d/alsasound stop/start, here's the output:
anat0005:/etc/init.d # ./alsasound start Starting sound driver: ens1371 Message from syslogd@anat0005 at Tue Apr 5 10:51:04 2005 ... anat0005 kernel: Disabling IRQ #12 ens1371 via82xx done Restoring the previous sound setting done
I'm not sure if this the behaviour you expect to see?
Actually it is. The question is do you see the via82xx driver module if you run 'lsmod' The above just says that the sound subsystem tries to load the driver. Your edit of modprobe.conf.local should sneak in behind that, so to speak, and disable the module forceably If you find the right file in /etc/sysconfig/hardware and delete it, you should get rid of even the text 'via82xx' when you restart alsasound You might want to check a mixer (volume setting) program to see if it can see your ensoniq, maybe it's just a volume setting that makes it silent?!
P.s. One of the things I have found necessary to get sound working on an identical machine is to add pci=noacpi to the boot command. Is this screwing things up??
It shouldn't. If your motherboard can't handle acpi for your old sound card, then it won't be able to handle it for your new sound card either
Hi, Nah - it's still there :( lsmod gives: snd_via82xx 25636 0 snd_mpu401_uart 8064 1 snd_via82xx snd_pcm 97160 3 snd_pcm_oss,snd_via82xx,snd_ens1371 snd 61572 13 snd_pcm_oss,snd_mixer_oss,snd_seq_midi,snd_seq_midi_event,snd_seq,snd_via82xx,snd_mpu401_uart,snd_ens1371,snd_rawmidi,snd_seq_device,snd_pcm,snd_timer,snd_ac97_codec **Stop press** Okay figured it out: the line I needed was install snd_via82xx /bin/true I.e. you need the snd_ prefix Cheers, Jon Anders Johansson wrote:
On Tuesday 05 April 2005 11:57, Jonathan Brooks wrote:
Hi Anders,
Thanks for your suggestion - not sure if it worked though? You guessed right :) SuSE 9.1, kernel 2.6.5-7.151-default
I edited modprobe.conf.local as you suggested, and typed depmod. To test this I then ran /etc/init.d/alsasound stop/start, here's the output:
anat0005:/etc/init.d # ./alsasound start Starting sound driver: ens1371 Message from syslogd@anat0005 at Tue Apr 5 10:51:04 2005 ... anat0005 kernel: Disabling IRQ #12 ens1371 via82xx done Restoring the previous sound setting done
I'm not sure if this the behaviour you expect to see?
Actually it is. The question is do you see the via82xx driver module if you run 'lsmod'
The above just says that the sound subsystem tries to load the driver. Your edit of modprobe.conf.local should sneak in behind that, so to speak, and disable the module forceably
If you find the right file in /etc/sysconfig/hardware and delete it, you should get rid of even the text 'via82xx' when you restart alsasound
You might want to check a mixer (volume setting) program to see if it can see your ensoniq, maybe it's just a volume setting that makes it silent?!
P.s. One of the things I have found necessary to get sound working on an identical machine is to add pci=noacpi to the boot command. Is this screwing things up??
It shouldn't. If your motherboard can't handle acpi for your old sound card, then it won't be able to handle it for your new sound card either
-- Jonathan Brooks (Ph.D.) Research Assistant. PaIN Group, Department of Human Anatomy & Genetics, University of Oxford, South Parks Road, Oxford, OX1 3QX tel: +44(0)1865-282654 fax: +44(0)1865-282656 web: http://www.fmrib.ox.ac.uk/~jon
participants (2)
-
Anders Johansson
-
Jonathan Brooks