Bad Sound in Slackware
A message that is not in the archive (sent off-list or not yet received): 20040206071508.4A4921C946@heisspf
Quoted 3 lines · you
Thanks Richard!
see my reply to the list for most of your questions.
I have cc'ed this back to the list.
Quoted 5 lines
Quoted 1 line · [email protected] said:
In other words stop using ALSA and use OSS
How is that done? When I disabled alsactl in
/etc/rd.cI had now more sound.
Using the default installed 2.4.22 kernel from slack-9.1. Remove ALL ALSA modules (if they are loaded) Then all that should be nessasary is;
modprobe via82cxxx_audio
The dependancies should not be a problem as in /lib/modules/2.4.22/modules.dep the following is defined.
/lib/modules/2.4.22/kernel/drivers/sound/via82cxxx_audio.o.gz:
/lib/modules/2.4.22/kernel/drivers/sound/ac97_codec.o.gz \
/lib/modules/2.4.22/kernel/drivers/sound/soundcore.o.gzQuoted 8 lines
Quoted 1 line · [email protected] said:
HuuH,! No such file or directory
@/ peter]$ ls
/etc/modules.conf/etc/modules.confOK I mad missed the 's' or if there es no such file in Slackware I must have copied it there from RH in the hope to get the sound going.
Slackware differs none its is "modules.conf"
Quoted 2 lines
Regards
Signature · 15 lines
If the Linux community is a bunch of theives because they try to imitate windows programs, then the Windows community is built on organized crime. Regards Richard [email protected] http://people.zeelandnet.nl/pa3gcu/ - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
At 04:19 PM 2/7/2004 +0100, pa3gcu wrote:
[...]
Quoted 10 lines
Using the default installed 2.4.22 kernel from slack-9.1. Remove ALL ALSA modules (if they are loaded) Then all that should be nessasary is;
modprobevia82cxxx_audio
The dependancies should not be a problem as in/lib/modules/2.4.22/modules.depthe following is defined.
/lib/modules/2.4.22/kernel/drivers/sound/via82cxxx_audio.o.gz:/lib/modules/2.4.22/kernel/drivers/sound/ac97_codec.o.gz \ /lib/modules/2.4.22/kernel/drivers/sound/soundcore.o.gz
Richard -- In a separate message, Peter reported having trouble with modprobe. It got me wondering if Slackware doesn't automatically run depmod when doing "make modules_install" ... or maybe during boot/init. Slackware's init setup is so different from other major distros, this seems at least possible to me ... and it would explain Peter's success with insmod but failure with modprobe. I wondered if you knew.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 14 lines · Ray Olszewski
At 04:19 PM 2/7/2004 +0100, pa3gcu wrote:
[...]Quoted 10 lines
Using the default installed 2.4.22 kernel from slack-9.1. Remove ALL ALSA modules (if they are loaded) Then all that should be nessasary is;
modprobevia82cxxx_audio
The dependancies should not be a problem as in/lib/modules/2.4.22/modules.depthe following is defined.
/lib/modules/2.4.22/kernel/drivers/sound/via82cxxx_audio.o.gz:/lib/modules/2.4.22/kernel/drivers/sound/ac97_codec.o.gz \ /lib/modules/2.4.22/kernel/drivers/sound/soundcore.o.gz
Quoted 7 lines
Richard -- In a separate message, Peter reported having trouble with modprobe. It got me wondering if Slackware doesn't automatically run depmod when doing "make
modules_install" ... or maybe during boot/init. Slackware's init setup is so different from other major distros, this seems at least possible to me ... and it would explain Peter's success with insmod but failure with modprobe. I wondered if you knew.
Slackware is no different to any other distro when it comes to using programs like 'make' to compile a kernel, the command 'make modules_install' ends with the following, unless of course one tells 'make' to do otherwise in the Makefile of the kernel source.
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.22-ac4-3; fi Where "linux-2.4.22-ac4-3" is your kernel version and EXTRAVERSION.
I rather think the problem Peter is having is because he is copying Redhat modules into another kernel version, or at least thats the way i ""quickly"" read his mail.
IMHO Peter is experimenting, he is using modules from another distro, i would not even recomend using modules from another kernel version, let alone another distro.
He possably after copying those modules to the destination dir, did not do; depmod -a
If he did i am sure he would have gotten a lot of error messages about, "Unresolved symbols".
I suggest Peter uses the default installed kernel 2.4.22 from slackware 9.1 and try what i said, i can assue folks it will work IF they follow my words to the "TEE", after all it works for me.
On top of all that, if Peter wants he can have a copy of my presant .config file from which he can then see just what i compile into and as modules for my system considering i have one of these dam chipsets that just does not work properly like the folks at ALSA think.
Signature · 15 lines
If the Linux community is a bunch of theives because they try to imitate windows programs, then the Windows community is built on organized crime. Regards Richard [email protected] http://people.zeelandnet.nl/pa3gcu/ - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 3 lines · [email protected] said:
He possably after copying those modules to the destination dir, did not do; depmod -a If he did i am sure he would have gotten a lot of error messages about, "Unresolved symbols".
Correct I did not make depmod -a. I did now and got a few error messages in .../net. After that modprobe worked.
Quoted 2 lines · [email protected] said:
i would not even recomend using modules from another kernel version, let
alone another distro.
Then I copied all the .../modules/drivers from the SW Install Disk into SW made again depmod -a and got no error messages.
I removed /sbin/insmod via82cxxx_audio, etc. in rc.local and enabled in rc.modules /sbin/modprobe/via82cxxx_audio.
How I had lost the folder .../kernel/sound in SW beats me.
What did Lawson sometimes write: beware, rogue system administrator on the loose.
Quoted 2 lines · [email protected] said:
if Peter wants he can have a copy of my presant .config file from which he
can then see just
Thanks, I seem to be OK for the moment.
Regards
Signature · 7 lines
Peter - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 3 lines · [email protected] said:
He possably after copying those modules to the destination dir, did not do; depmod -a If he did i am sure he would have gotten a lot of error messages about, "Unresolved symbols".
Correct I did not make depmod -a. I did now and got a few error messages in .../net. After that modprobe worked.
Quoted 2 lines · [email protected] said:
i would not even recomend using modules from another kernel version, let
alone another distro.
Then I copied all the .../modules/drivers from the SW Install Disk into SW made again depmod -a and got no error messages.
I removed /sbin/insmod via82cxxx_audio, etc. in rc.local and enabled in rc.modules /sbin/modprobe/via82cxxx_audio.
How I had lost the folder .../kernel/sound in SW beats me.
What did Lawson sometimes write: beware, rogue system administrator on the loose.
Quoted 2 lines · [email protected] said:
if Peter wants he can have a copy of my presant .config file from which he
can then see just
Thanks, it's very kind. I seem to be OK for the moment.
Regards
Signature · 12 lines
Peter --6397E30459.1076664313/heisspf-- - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs