Ancient Thinkpad running Mint 9 cannot get sound to endure re-boot
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
Well!
The contrary machine!!
I was just preparing to follow your instructions re the USB problem, and it now reads both the thumb and the SDcard no problem!!
Good to have recourse to that information though for future!
So you have sound with a fresh install after manually loading the sound module? But adding the sound module to /etc/modules doesn't result in sound after a reboot still?
I haven't yet tried it:
This is the current state of the file:-
/etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
lp
last time I got this far, someone on the Mint forum suggested I just add "snd cs-4236" on the line below "lp".
But that didn't work!
The fact that I mistakenly edited the folder "modutils" rather than the file "modules", and consequently buggered up the install might have had some marginal effect.
Do I perhaps also need to list "snd cs-46xx", which was the first one that I mounted today.
And what about the one that now appears on the tab of the Alsa mixer "cs-4239" do I also add an entry for that on the modules file, if so, would it be "snd cs-4239"??
cs-4239 shouldn't come into play. That is supported by the cs-4236 module (in theory).
It seems a little odd to me that both snd_cs46xx and snd_cs4636 together make it work. From what I can find, it looks like most people have the opposite experience, having both modules load breaks sound. But if that is what works, hey.
So I would definitely try disabling the quick start BIOS thing first off. And then add one or both of the snd_cs46xx modules to /etc/modules. Quick and easy way, just copy and paste this
Code:
echo "snd_cs46xx
snd_cs4236" | sudo tee -a /etc/modules
Edit to remove one or the other if that doesn't work.
cs-4239 shouldn't come into play. That is supported by the cs-4236 module (in theory).
It seems a little odd to me that both snd_cs46xx and snd_cs4636 together make it work. From what I can find, it looks like most people have the opposite experience, having both modules load breaks sound. But if that is what works, hey.
So I would definitely try disabling the quick start BIOS thing first off. And then add one or both of the snd_cs46xx modules to /etc/modules. Quick and easy way, just copy and paste this
Code:
echo "snd_cs46xx
snd_cs4636" | sudo tee -a /etc/modules
Edit to remove one or the other if that doesn't work.
I'm presuming that "snd_cs4636" is a typo and should be "snd_cs4236"
Should I not do that before trying to disable "quick boot", since that would of course involve the dreaded re-boot in order to get into BIOS
just been trying to get a reasonable amount of volume using Exaile and the equaliser,and "replay gain" but not good.
sound level is low even on full volume and distorts, also breaks up or disappears with mouse movement.
Maybe it's all too much for this slow processor?
I'm presuming that "snd_cs4636" is a typo and should be "snd_cs4236"
Should I not do that before trying to disable "quick boot", since that would of course involve the dreaded re-boot in order to get into BIOS
Yes, I corrected the typo.
/etc/modules is just a list of modules to load at boot. In most cases it's unneeded as hardware is detected and the appropriate modules automatically loaded. So regardless, we won't know it that resolves the problem without rebooting, I'm afraid.
/etc/modules is just a list of modules to load at boot. In most cases it's unneeded as hardware is detected and the appropriate modules automatically loaded. So regardless, we won't know it that resolves the problem without rebooting, I'm afraid.
Yeah...scary!
So I take it that it will be OK to edit "modules" before re-booting.
I'll just do that edit, then re-boot and disable quickboot...see if the sound survives!
OK, back again...no sound, tried the same terminal commands that succeeded in activating the sound, but this time it hasn't worked
The responses were different this time:- ~ $ sudo modprobe cs-46xx
[sudo] password for hexeta:
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
FATAL: Module cs_46xx not found.
Then the other one:- ~ $ sudo modprobe cs-4236
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
FATAL: Module cs_4236 not found.
~ $ sudo modprobe cs-46xx
[sudo] password for hexeta:
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
FATAL: Module cs_46xx not found.
Then the other one:-
~ $ sudo modprobe cs-4236
WARNING: All config files need .conf: /etc/modprobe.d/blacklist, it will be ignored in a future release.
WARNING: All config files need .conf: /etc/modprobe.d/ndiswrapper, it will be ignored in a future release.
FATAL: Module cs_4236 not found.
I think the not found is because it's snd_cs46xx and snd_cs4236.
Since posting I've just tried removing both cs_46xx and cs_4236, and then re-mounting them..........twice.
Each time, I got as far as re mounting cs_46xx, and the machine froze before terminal completed and I had to do a hard shutdown and re-boot.
The second time this happened, I noticed as the desktop was building, that two volume controls appeared in the "panel" (is that the taskbar in windows speak lol), and lo I do have sound!
No idea what I did that's caused this abberation
Removed one volume control, and sound appears to have survived...are there any "system sounds" that should be heard?
I think the not found is because it's snd_cs46xx and snd_cs4236
Oh dear! that's me being lazy!
instead of copying and pasting from my leafpad crib sheet of terminal commands, I just copied that from one of the posts!!
Since it seems to be working, I think I'll quit whilst I'm ahead and not attempt to mount or dismount anything else!
Just run Term command "lsmod | less" and this is the response:- snd_seq_midi_event 6003 2 snd_seq_oss,snd_seq_midi
snd_seq 47263 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_m
idi_event
xircom_cb 6813 0
snd_timer 19098 4 snd_wss_lib,snd_opl3_lib,snd_pcm,snd_seq
ndiswrapper 184677 0
snd_seq_device 5700 6 snd_opl3_lib,snd_seq_dummy,snd_seq_oss,snd_seq_m
idi,snd_rawmidi,snd_seq
snd 54148 17 snd_cs4236,snd_wss_lib,snd_opl3_lib,snd_hwdep,s
nd_mpu401_uart,snd_cs46xx,snd_pcm_oss,snd_ac97_codec,snd_mixer_oss,snd_pcm,snd_s
eq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
psmouse 63245 0
soundcore 6620 1 snd
yenta_socket 20408 2
lp 7028 0
rsrc_nonstatic 10015 1 yenta_socket
shpchp 28820 0
pcmcia_core 32964 2 yenta_socket,rsrc_nonstatic
snd_page_alloc 7076 3 snd_wss_lib,snd_cs46xx,snd_pcm
serio_raw 3978 0
i2c_piix4 8335 0
parport 32635 2 ppdev,lp
dm_raid45 81647 0
xor 15028 1 dm_raid45
fbcon 35102 71
tileblit 2031 1 fbcon
font 7557 1 fbcon
bitblit 4707 1 fbcon
softcursor 1189 1 bitblit
usbhid 36110 0
vga16fb 11385 1
intel_agp 24177 1
hid 67032 1 usbhid
vgastate 8961 1 vga16fb
agpgart 31724 1 intel_agp
(END)
Does that confirm that all sound modules that are needed are there??
Suppose I really need to bite the bullet and re-boot again.
perhaps that is more useful
I just don't understand the difference between the commands "lsmod" and "lsmod | less".
I thought that the "| less" bit just meant that it would stop at the bottom of the screen and advance using the cursor keys, but the information seems to be presented differently!
Less is just a pager. You're piping the output of lsmod to less, which displays one page at a time. It shouldn't change the output at all, just how it's displayed.
Better for your needs is probably grep.
Code:
lsmod | grep snd
This will display just the modules with the string "snd" in them, which is all we're looking for. Grep is a text search utility, much more powerful than the simple use we are putting it to currently.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
