Ubuntu
alsa-driver package

no sound on Toshiba U205 laptop core 2 duo

Asked by eddski

I have no sound in my laptop, and have tried multiple fixes and none worked. I may have had some sound when I first installed 8.10, but I was almost immediately prompted for updates and now I have nothing. Below includes much info about my laptop from some commands I had read. Any help would be appreciated as this is the last hurdle to cutting ties to m$.
I have a Toshiba U205-5044 core2 duo 2GHz

This is my output from the command aplay -l :

**** List of PLAYBACK Hardware Devices ****

E: shm.c: shm_open() failed: Read-only file system ##not sure what this line means
card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]

  Subdevices: 1/1

  Subdevice #0: subdevice #0

card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem]

  Subdevices: 1/1

  Subdevice #0: subdevice #0

*********************************************************************************

this is my output from the command asoundconf list :

Names of available sound cards:

Intel

*********************************************************************************

here is the output from the lspci command :

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)

00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)

00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)

00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02)

00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02)

00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02)

00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02)

00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02)

00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)

00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)

00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)

00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02)

02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)

03:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network Connection (rev 02)

03:0b.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller

03:0b.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller

03:0b.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD)

03:0b.3 SD Host controller: Texas Instruments PCIxx12 SDA Standard Compliant SD Host Controller

**********************************************************************************

this is the output from the command cat /proc/asound/cards :

 0 [Intel ]: HDA-Intel - HDA Intel

                      HDA Intel at 0xd8080000 irq 22

the output for lsmod | grep snd :

snd_hda_intel 384176 3

snd_pcm_oss 46848 0

snd_mixer_oss 22784 1 snd_pcm_oss

snd_pcm 83204 2 snd_hda_intel,snd_pcm_oss

snd_seq_dummy 10884 0

snd_seq_oss 38528 0

snd_seq_midi 14336 0

snd_rawmidi 29824 1 snd_seq_midi

snd_seq_midi_event 15232 2 snd_seq_oss,snd_seq_midi

snd_seq 57776 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event

snd_timer 29960 2 snd_pcm,snd_seq

snd_seq_device 15116 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq

snd 63268 15 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device

soundcore 15328 1 snd

snd_page_alloc 16136 2 snd_hda_intel,snd_pcm

I hope this is not too much, I'm new and getting frustrated eith this last hurdle.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu alsa-driver Edit question
Assignee:
No assignee Edit question
Solved by:
eddski
Solved:
Last query:
Last reply:
Revision history for this message
Tom (tom6) said : 		#1

Ok this link might help

https://help.ubuntu.com/community/SoundTroubleshooting

You might have been through it before and it starts very basic "make sure the speaker plug is in the green socket", "use the mixer console to make sure all the various sliders are up high and nothing's muted" lol (yes mum, lol) but it's amazing how often some of these trivial things are overlooked (at least i often do) and some of the later parts get a bit more advanced.

There is also this link but this is hopelessly advanced for me so good luck with it!
http://alsa.opensrc.org/index.php/TroubleShooting

Good luck and regards from
Tom :)

Revision history for this message
Mark Rijckenberg (markrijckenberg) said : 		#2

Hi,

Step 1: Open Terminal from "Applications->Accessories->
Terminal"

Step 2: Run the following commands (copy/paste each command into the Terminal and then hit <enter>)

sudo aptitude update
sudo aptitude install gnome-alsamixer asoundconf-gtk

Step 3: copy-paste the following command into the Terminal:

gksudo gedit /etc/modprobe.d/alsa-base

and add these lines to the end of the file:

# Keep snd-pcsp from beeing loaded as first soundcard
options snd-pcsp index=-2
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
options snd-hda-intel model=toshiba
options snd-hda-intel enable_msi=1

If that toshiba model option does not help, try one of these alternatives:

 AD1988/AD1988B/AD1989A/AD1989B
   3stack 3-jack
   3stack-dig ditto with SPDIF
  6stack 6-jack
   6stack-dig ditto with SPDIF
   laptop 3-jack with hp-jack automute
   laptop-dig ditto with SPDIF
   auto auto-config reading BIOS (default)
   toshiba Toshiba laptops

Step 4: Then navigate to System>Preferences>Sound and change everything to ALSA

Step 5; reboot and retest sound after every change you make to the alsa-base file

Step 6: Experiment with the audio settings in gnome-alsamixer and asoundconf-gtk until you get sound (hopefully). Both tools can be launched through the Terminal

Regards,

Mark

Revision history for this message
eddski (drakski) said : 		#3

thsnks for the help, but I think I found the problem. I have a dual bot w/ windows and the volume for xp was all the way down. When I turned it up all the way in xp and rebooted to Ubuntu, I had all the sound I needed. I'm not sure if that sounds(funny) correct, but I have sound and now I need to work on a multimedia player. Thanks for your help.

Revision history for this message
Tom (tom6) said : 		#4

Lol! Sounds (pardon the pun) like you have Ubuntu installed inside Windows using the Wubi? At the menu for choosing between Windows and Ubuntu is there only 1 choice for Ubuntu? IF so then you'll need to 'migrate' your Ubuntu onto it's own space using part 8 of section 8 of this guide
https://wiki.ubuntu.com/WubiGuide

If you have the menu that includes "recovery mode", "memtest" and "Other Operating Systems" then i really wouldn't bother getting rid of Windows. Most of us have kept this type of dual-boot but just made it default to boot into Ubuntu fairly fast. There are several tweaks to get this setup just about perfect.

Good luck and regards from
Tom :)

Revision history for this message
eddski (drakski) said : 		#5

I know it sounds funny, Tom, but I have a /boot as primary, and 6 logicals inside an extended, windows is no where around it.
I would like a believable explanation, but I checked it twice. I do not even know what wubi is, but I have seen it mentioned. I have the 2nd choice w/rm, memtst and OOS. I do not want to remove windows because my family uses it.

Revision history for this message
Tom (tom6) said : 		#6

Ok, most of us have a working Windows because the two OS's can help each other sometimes if one has a problem. Also it's good to use for some stuff sometimes anyway. Having the 2nd choice shows that you have set things up properly already and having your own style already is a good thing!

It's weird that Windows volume affects Ubuntu but odd stuff happens sometimes <shrugs>. Yeh, i would love to know why too but the fact of fixing it and knowing what to do if the same thing happens again is enough for me right now.

Thanks, good luck and regards from
Tom :)

PS it might be worth posting a bug report about this. Look up at the top right of the page this thread is on and click on the "Create bug report", i would give it a title such as "Volume affected by Windows, not a Wubi!?" lol, good luck ;)