more kubuntu problems - sound

[tlo]

Im having another kubuntu problem that im finally getting around to solving. I don't have sound. there used to be a message saying some stuff on boot, but it didn't pop up this time. but when i go to system settings, it tells me "libasound.so.2: cannot open shared object file. No such file or directory". There is a post about Gentoo on a 3880 (i use a 3880) where he had the same problems and he solved them (something about the ALSA drivers) but i tried his methods and the commands arent the same, and i don't really follow what he was doing. Can someone help me out here?

[seablade]

apt-get install alsa-lib

Or something along those lines, make sure you have both the alsalib and the alsa driver(Whcih I would bet you probably have the driver) installed. Firmware and tools and the like probably aint a bad idea either.

Seablade

[tlo]

the driver and libraries are installed, but no sound. someone else had this same problem in gentoo on their 3880 (there's a post about it somewhere) and said something was wrong with the alsa driver, but i don't know what it was talking about.

[seablade]

I would probably have to be there then, but check your boot messages to see if alsa is loaded at all during boot. If it is are there any errors(I dont believe you said there were but just double checking;)

If it isnt, try running the init.d script yourself and see what the output is. Should be something like '/etc/init.d/alsasound start' and youll probably have to run it as root. Where is this other thread you are referring to though?

Seablade

[tlo]

this is the link to the thread i was talking about (http://www.notebookforums.com/showthread.php?t=87568&highlight=3880+gentoo)

i also had to blacklist "snd-hda-intel" because it was causing the hotplug subsystem to hang on bootup. is this part of the problem? the alsa-init script ran fine, and said it started alsa. It also loads up fine at boot without errors.

[seablade]

lsmod and see if snd_hda_intel is listed? Actually go ahead and post up all the alsa modules(they are typically prefixed with snd) that are running on your machine.

Glancing at other threads it seems there are some custom options that have to be passed to that module in order for it to work correctly on your machine. Unfortunatly that is going to be over my head probably, but if the module is running that might not the specific problem in this case.

Seablade

[tlo]

there are no snd modules. this is my lsmod:
odule Size Used by
ipv6 217408 6
binfmt_misc 10888 1
nvidia 4085552 14
rfcomm 34972 0
l2cap 22404 5 rfcomm
bluetooth 43012 4 rfcomm,l2cap
speedstep_centrino 7380 1
cpufreq_powersave 1920 0
cpufreq_stats 5124 0
cpufreq_userspace 4444 1
cpufreq_ondemand 5916 0
cpufreq_conservative 6820 0
freq_table 4484 2 speedstep_centrino,cpufreq_stats
pcmcia 24584 4
tc1100_wmi 6916 0
video 16004 0
battery 9604 0
container 4608 0
i2c_acpi_ec 5760 0
i2c_core 19728 1 i2c_acpi_ec
button 6672 0
pcc_acpi 11392 0
sony_acpi 5516 0
ac 4996 0
dev_acpi 11396 0
hotkey 9508 0
af_packet 20232 2
irtty_sir 7808 0
sir_dev 17324 1 irtty_sir
irda 159804 2 irtty_sir,sir_dev
crc_ccitt 2176 1 irda
rtc 11832 0
yenta_socket 22540 2
rsrc_nonstatic 12032 1 yenta_socket
pcmcia_core 44932 3 pcmcia,yenta_socket,rsrc_nonstatic
ipw2200 92680 0
firmware_class 9472 1 ipw2200
ieee80211 27012 1 ipw2200
ieee80211_crypt 5636 2 ipw2200,ieee80211
ohci1394 30644 0
sk98lin 166872 0
tpm_nsc 6528 0
tpm 9504 1 tpm_nsc
shpchp 80612 0
pci_hotplug 24628 1 shpchp
intel_agp 21276 1
agpgart 32328 2 nvidia,intel_agp
nls_cp437 5888 1
ntfs 92016 1
dm_mod 50364 1
tsdev 7616 0
evdev 9088 0
sr_mod 15652 0
sbp2 21128 0
ieee1394 90936 2 ohci1394,sbp2
psmouse 26116 0
mousedev 10912 1
parport_pc 31812 0
lp 11460 0
parport 32072 2 parport_pc,lp
md 40656 0
reiserfs 217200 1
thermal 13192 0
processor 23100 2 speedstep_centrino,thermal
fan 4740 0
ehci_hcd 29448 0
uhci_hcd 28048 0
usbcore 104316 3 ehci_hcd,uhci_hcd
ide_cd 36996 0
cdrom 33952 2 sr_mod,ide_cd
ide_disk 16128 4
ide_generic 1664 0
ata_piix 9476 0
ahci 11268 0
libata 47876 2 ata_piix,ahci
scsi_mod 124872 4 sr_mod,sbp2,ahci,libata
piix 9476 1
ide_core 125268 4 ide_cd,ide_disk,ide_generic,piix
unix 24624 186
vesafb 8088 0
capability 5000 0
commoncap 6784 1 capability
vga16fb 12232 1
vgastate 8320 1 vga16fb
softcursor 2432 2 vesafb,vga16fb
cfbimgblt 2944 2 vesafb,vga16fb
cfbfillrect 3840 2 vesafb,vga16fb
cfbcopyarea 4480 2 vesafb,vga16fb
fbcon 34176 72
tileblit 2560 1 fbcon
font 8448 1 fbcon
bitblit 5248 1 fbcon
tristan@tristan-ubuntu:~$
i saw someone else had gone to their sound config file and replaced intel (the intel part of snd-hda-intel?) with their soundcard type. where is this file, and will that solve mine?

[seablade]

Hmm I may have made some bad assumptions..

Do you know what chipset your soundcard is first off? Do you even use the snd_hda_intel driver?

Have you tried running alsaconf?

Can you see if there is any snd modules loaded after you run the init.d script? If there isnt there is something seriously wrong with your setup as it isnt loading the modules.

Seablade

[tlo]

i think maybe, from what i read off of somewhere where a guy had the same problem on a z71v (similar lappy) that they had the hda_intel driver listed to be the driver used, but their card was something else. i ran the alsa load command and the alsa-utils start command, and lsmod showed nothing different. i can't find anything called alsaconf, and it isnt in my init.d folder, nor was it a valid bash command. sager's website lists my card as a " ALC880 Audio CODEC / WOW ASP." where do i tell my computer what driver to use so i can see if it is trying to use the wrong driver?

[seablade]

alsaconf is a small alsa configuration program, not real sure which package it is in, probably alsa_tools or alsa_util so you may want to apt-get those. It would be in your sbin most likely, so try to find it with root, not with a normal suer.

Try that first, it may be the easiest method of doing this. If it doesnt work then we will move on to finding out exactly what chipset you have if we can.

Seablade

[tlo]

i have alsa-utils (apt-cache search had no alsa-tools) and i ran it (from /etc/init.d)
sh alsa-utils start and it said "Setting up ALSA...................................[ok]
but still no snd module. was it supposed to ask me feedback and whatnot to configure it?

[seablade]

Yep. GOtta find out what package alsaconf is in for you...

Seablade

[seablade]

Hmm apparently in debian at least alsaconf is a seperate package, so try apt-get install alsaconf and see if that works.

Seablade

[seablade]

err well actually after looking through the ubuntu forums... apparently alsaconf is purposefully removed from the alsa-utils package...

Not a clue why.

I did find these directions to give a shot though if you care to...


System -----> Preferences ------> MultiMedia Systems Selector ----> Audio ---->Input ----> Click on the arrows and highlight ALSA -----> Test ----> Close


And see what happens when you do that I suppose.

Seablade

[seablade]

Or if you want to go through the alsaconf route it can be installed by compiling the alsa-utils package from source.

Yea I do understand why people say if it dont work in Ubuntu just leave it now;) Still cant figure out why they dont let you at least get alsaconf via some means.

Seablade

[seablade]

Actually several solutions for getting sound working if it doesnt by default in Ubuntu seem to be compile alsa from source... interesting

Seablade

[c0bblers]

The intel-hda driver was a bit iffy until recentish (few months I think) I was compiling from CVS for my Z71V. The most recent releases of alsa-driver have been fine for me though so you might want to try grabbing hold of a recent tarball and using that.

[seablade]

Hmm good to know about, yea it looks like it would be best for you to download and install those drivers by hand. Does Ubuntu use the userspace driver or do they compile it with the kernel?

Seablade

[c0bblers]

It's a binary distro so I'm 99% sure they compile as much as possible as modules. Downloading and compiling the alsa-driver package against the current kernel's source tree should splat over the original ones (technical speak there ;)).

EDIT: That it unless they've updated the drivers already or something in the apt repository. If they're updated it might be worth taking out the driver from the blacklist and crossing your fingers.

[tlo]

i just updated and upgraded my system, and it still hung when i unblacklisted it, so it isn't updated in the repository. im gonna download and compile the new ones like you said, and see what happens

[seablade]

When you download and compile them from source we can go about setting them up like normal, leave them blacklisted in hot/coldplug and let the alsa script set them up and see if that helps.

Seablade

[seablade]

You also might wanna see if modprobing snd_hda_intel will cause any errors or a hangup before you begin. I forgot I might some assumptions I shouldnt have in this thread and I dont believe you mentioned trying that yet.

Seablade

[tlo]

# sudo modprobe snd-hda-intel
sh: line 1: 7441 Segmentation fault modprobe --ignore-install snd-hda-intel
FATAL: Error running install command for snd_hda_intel

im gonna try compiling that driver, and i also downloaded tools and utilities. do i need to recompile those as well or will that be done when i do the driver?

[tlo]

im installing the alsa driver by how the install file says, and i got this at the end:
cat WARNING

WARNING!!! The mixer channels for the ALSA driver are muted by default!!!
**************************************************************************
You would use some ALSA or OSS mixer to set the appropriate volume.


but ksoundwhatever doesnt have it on mute

[seablade]

The warning is normal, check alsamixer to see if they are muted. It is by default and the warning is there only because that is the SINGLE most common mistake people make is assuming something is broken when all it is is muted.

You should go ahead and install alsa-lib alsa-tools alsa-util and the works really IMO. You probably could get by without, but I would go ahead and do it.

Seablade

[tlo]

well, i think there was def something wrong, because when i was doing the install for alsa driver, i found that i had no pre-existing /dev/snd folder, which i assume is the folder that holds all of the sound configs and drivers and whatnot

[tlo]

hooray, i got all of the things for alsa, ran all their installers or configs, ran alsaconf (which was probably what i really needed) and now i have snd-hda-intel running. when i get home im gonna find a soundfile to play, and then, on to video codecs. thanks guys for all your help, couldn't of done it without you. reps all around!

[seablade]

Cool beans, just make sure your unmuted before you play the file.

Have fun.

Seablade