| View previous topic :: View next topic |
| Author |
Message |
queen
Veteran
Joined: 19 Jul 2005
Posts: 1642
|
 Posted: Mon Feb 04, 2008 7:20 am Post subject: sound doesn't work |
 |
|
I have a | Code: | | Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) |
Sound used to work before I made changes in the kernel to make it for high definition audio. Unfortunatelly, I don't have a backup. ;-(
Here is the current situation of errors that I get:
| Code: | /etc/init.d/alsasound restart
* WARNING: you are stopping a boot service.
* Storing ALSA Mixer Levels ...
alsactl: save_state:1253: No soundcards found...
* Error saving levels. [ !! ]
* Killing processes using ALSA ... [ ok ]
* Unloading ALSA modules ... [ ok ]
* Loading ALSA modules ...
* Could not detect custom ALSA settings. Loading all detected alsa drivers.
* Unable to find any ALSA drivers. Have you compiled alsa-drivers correctly?
* ERROR: Failed to load necessary drivers [ ok ]
* Restoring Mixer Levels ...
alsactl: unrecognized option `---'
Usage: alsactl <options> command
Available options:
-h,--help this help
-f,--file # configuration file (default /etc/asound.state or /etc/asound.names)
-F,--force try to restore the matching controls as much as possible
-d,--debug debug mode
-v,--version print version of this program
Available commands:
store <card #> save current driver setup for one or each soundcards
to configuration file
restore <card #> load current driver setup for one or each soundcards
from configuration file
names <card #> dump information about all the known present (sub-)devices
into configuration file (DEPRECATED)
* Errors while restoring defaults, ignoring |
| Code: | cat /usr/src/linux/.config | grep SND_HDA
CONFIG_SND_HDA_INTEL=y
|
| Code: | cat /usr/src/linux/.config | grep -i sound
# Sound
CONFIG_SOUND=y
# Advanced Linux Sound Architecture
# Open Sound System
# CONFIG_SOUND_PRIME is not set
|
My current /etc/make.conf is | Code: | grep ALSA /etc/make.conf
ALSA_CARDS="intel8x0,intel8x0m" |
I can't launch alsamixer | Code: | | alsamixer: function snd_ctl_open failed for default: No such device |
| Code: | cat /usr/src/linux/.config | grep SND
CONFIG_SND=y
CONFIG_SND_TIMER=y
CONFIG_SND_PCM=y
CONFIG_SND_HWDEP=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=y
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_PCM_OSS_PLUGINS=y
CONFIG_SND_SEQUENCER_OSS=y
CONFIG_SND_RTCTIMER=m
CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
# CONFIG_SND_DYNAMIC_MINORS is not set
CONFIG_SND_SUPPORT_OLD_API=y
# CONFIG_SND_VERBOSE_PROCFS is not set
# CONFIG_SND_VERBOSE_PRINTK is not set
CONFIG_SND_DEBUG=y
# CONFIG_SND_DEBUG_DETECT is not set
CONFIG_SND_MPU401_UART=m
CONFIG_SND_VX_LIB=m
CONFIG_SND_AC97_CODEC=y
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
CONFIG_SND_MPU401=m
# CONFIG_SND_ADLIB is not set
# CONFIG_SND_AD1816A is not set
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_ALS100 is not set
# CONFIG_SND_AZT2320 is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_DT019X is not set
# CONFIG_SND_ES968 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_MIRO is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set
# CONFIG_SND_WAVEFRONT is not set
# CONFIG_SND_AD1889 is not set
# CONFIG_SND_ALS300 is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS5530 is not set
# CONFIG_SND_CS5535AUDIO is not set
# CONFIG_SND_DARLA20 is not set
# CONFIG_SND_GINA20 is not set
# CONFIG_SND_LAYLA20 is not set
# CONFIG_SND_DARLA24 is not set
# CONFIG_SND_GINA24 is not set
# CONFIG_SND_LAYLA24 is not set
# CONFIG_SND_MONA is not set
# CONFIG_SND_MIA is not set
# CONFIG_SND_ECHO3G is not set
# CONFIG_SND_INDIGO is not set
# CONFIG_SND_INDIGOIO is not set
# CONFIG_SND_INDIGODJ is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_FM801 is not set
CONFIG_SND_HDA_INTEL=y
# CONFIG_SND_HDSP is not set
# CONFIG_SND_HDSPM is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=y
# CONFIG_SND_INTEL8X0M is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_PCXHR is not set
# CONFIG_SND_RIPTIDE is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_AC97_POWER_SAVE is not set
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set
# CONFIG_SND_USB_CAIAQ is not set
CONFIG_SND_VXPOCKET=m
CONFIG_SND_PDAUDIOCF=m
# CONFIG_SND_SOC is not set
|
Any help will be appreciated. I followed the alsa guide but it didn't help. |
|
| Back to top |
|
 |
jomen
Guru
Joined: 04 Jan 2006
Posts: 536
Location: Leipzig, Germany
|
| Posted: Mon Feb 04, 2008 4:48 pm Post subject: |
|
|
From this:
| Code: | cat /usr/src/linux/.config | grep SND_HDA
CONFIG_SND_HDA_INTEL=y |
and this:
| Code: | cat /usr/src/linux/.config | grep -i sound
# Sound
CONFIG_SOUND=y
# Advanced Linux Sound Architecture
# Open Sound System
# CONFIG_SOUND_PRIME is not set |
I take it you compiled the alsa drivers into the kernel - not as modules - nothing to load...
this:
| Code: | grep ALSA /etc/make.conf
ALSA_CARDS="intel8x0,intel8x0m" |
in /etc/make.conf is needed when you build alsa-drivers not by using the in-kernel-drivers but when you build them from media-sound/alsa-driver ebuild.
You only need one kind - in-kernel or externally built modules - or - as you have done - no modules at all but compiled in.
I don't know if you could have both as modules - you can only use one or the other I'd say.
And you can't load modules when there are drivers already in the kernel I guess.
Not sure what to make of the error-message while starting alsa since the drivers should be there - just not as modules.
I always build the drivers as modules - I can remember problems when they where compiled in.
_________________
Cheers |
|
| Back to top |
|
|
queen
Veteran
Joined: 19 Jul 2005
Posts: 1642
|
| Posted: Thu Feb 14, 2008 7:54 am Post subject: |
|
|
| jomen wrote: | From this:
| Code: | cat /usr/src/linux/.config | grep SND_HDA
CONFIG_SND_HDA_INTEL=y |
and this:
| Code: | cat /usr/src/linux/.config | grep -i sound
# Sound
CONFIG_SOUND=y
# Advanced Linux Sound Architecture
# Open Sound System
# CONFIG_SOUND_PRIME is not set |
I take it you compiled the alsa drivers into the kernel - not as modules - nothing to load...
this:
| Code: | grep ALSA /etc/make.conf
ALSA_CARDS="intel8x0,intel8x0m" |
in /etc/make.conf is needed when you build alsa-drivers not by using the in-kernel-drivers but when you build them from media-sound/alsa-driver ebuild.
You only need one kind - in-kernel or externally built modules - or - as you have done - no modules at all but compiled in.
I don't know if you could have both as modules - you can only use one or the other I'd say.
And you can't load modules when there are drivers already in the kernel I guess.
Not sure what to make of the error-message while starting alsa since the drivers should be there - just not as modules.
I always build the drivers as modules - I can remember problems when they where compiled in. |
I compiled in the kernel. This is what I usually do. I tried to make it as module as well, but for some reason I can't emerge alsa-drivers. When I open the computer I get this error: | Code: | Sound server informational message:
Error while initializing the sound driver:
device /dev/dsp can't be opened (No such file or directory)
The sound server will continue, using the null output device. |
Built in and module don't work together as per alsa guide. I deleted the ALSA_CARDS="intel8x0,intel8x0m" and left only ALSA_CARDS="hda-intel" in /etc/make.conf
Any ideas how to continue on from here? I prefer built in the kernel. |
|
| Back to top |
|
|
jomen
Guru
Joined: 04 Jan 2006
Posts: 536
Location: Leipzig, Germany
|
| Posted: Thu Feb 14, 2008 5:13 pm Post subject: |
|
|
I did not make clear what I meant previously:
a) either compile Alsa using the drivers provided with the kernel-source
You don't need to give anything in /etc/make.conf then - this is only needed when using an ebuild
b) or compile the drivers using the ebuild - you then need to give the sound-card in /etc/make.conf
c) in both cases (though there is no other way when using the ebuild...) - compile Alsa as modules!
except: CONFIG_SOUND - the "Sound card support" - this can (more likely: should?) be built into the kernel.
Every other Alsa-related things should be modules.
http://alsa.opensrc.org/index.php/TroubleShooting - the second section...
See if it works...for me the kernel-drivers work very well - so: no ALSA_CARDS="intel8x0" or such needed in /etc/make.conf.
I have an additional config-file from a long time ago - don't know if this is still needed to make everything work as expected.
I just still have it and did not test without it.
the file is:
/etc/modules.d/alsa
| Code: | # Alsa 0.9.X kernel modules' configuration file.
# $Header: /var/cvsroot/gentoo-x86/media-sound/alsa-utils/files/alsa-modules.conf-rc,v 1.4 2004/11/16 01:31:22 eradicator Exp $
# ALSA portion
alias char-major-116 snd
# OSS/Free portion
#alias char-major-14 soundcore
##
## IMPORTANT:
## You need to customise this section for your specific sound card(s)
## and then run `update-modules' command.
## Read alsa-driver's INSTALL file in /usr/share/doc for more info.
##
## ALSA portion
alias snd-card-0 snd-intel8x0
#alias snd-card-1 snd-intel8x0m
## OSS/Free portion
alias sound-slot-0 snd-card-0
#alias sound-slot-1 snd-card-1
##
# OSS/Free portion - card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
## OSS/Free portion - card #2
#alias sound-service-1-0 snd-mixer-oss
#alias sound-service-1-3 snd-pcm-oss
#alias sound-service-1-12 snd-pcm-oss
alias /dev/mixer snd-mixer-oss
alias /dev/dsp snd-pcm-oss
alias /dev/midi snd-seq-oss
# Set this to the correct number of cards.
options snd cards_limit=1 |
[edit]
made a minor addition to the text above - and:
I just removed the file mentioned above - and everything still works after reboot - so: forget worrying about this for now...it appears it is not needed anymore
_________________
Cheers
Last edited by jomen on Thu Feb 14, 2008 5:35 pm; edited 1 time in total |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54304
Location: 56N 3W
|
| Posted: Thu Feb 14, 2008 5:27 pm Post subject: |
|
|
queen,
Its better to build snd-intel-hda as a module, as you will almost certainly need some trial and error with module parameters to make it work.
A a module, you can unload it then reload it with new parameters. As a built in, you have to reboot.
Thats the only advantage of modules over built in.
You need to turn off all the sound related debug. Thats for developers only. It will spam your logs and cause issues of its own.
For module parameters to try, look in /usr/src/linux/Documentation/sound/alsa/ALSA-Configuration.txt
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Bloodsurfer
Guru
Joined: 07 Dec 2005
Posts: 361
Location: Wolfstein, Germany (Rhineland-Palatinate)
|
| Posted: Thu Feb 14, 2008 6:21 pm Post subject: |
|
|
I'm having the same problem as the original poster.
I always used compiled-in alsa-drivers (snd-hda-intel). Worked for about a year, without a problem since I first set this machine up.
Now I updated to 2.6.24 and with that alsa stopped working. I made no changes - same .config as before, everything compiled in. Error messages are the same like in the first posting here.
Did also try to compile the drivers as modules. I can load them by hand, it still doesn't recognize any soundcard.
Still works fine with old kernel. Any ideas?
_________________
SiberianSniper: my girlfriend's name ends with .c
Clete2: Uber geek! W00t! I'd rather have it end in .cpp... <insert name>.cpp
Dralnu: ...why not <name>.o? Then she's ready for linking...
SiberianSniper: or <name>.ko, so she's ready for insertion? |
|
| Back to top |
|
|
jomen
Guru
Joined: 04 Jan 2006
Posts: 536
Location: Leipzig, Germany
|
| Posted: Thu Feb 14, 2008 8:14 pm Post subject: |
|
|
...as for me - I had nothing but trouble until I compiled alsa completely as modules.
...this is a long time ago - and this is what Alsa always suggested...
The only thing I have built into the kernel is the general option "Sound card support" - everything below that are only modules.
The last section of the page (the link I gave above) may be of help as it suggests that the drivers that come with the kernel are not up to date.
If I would have problems I'd use the stable or even latest ebuild for alsa-drivers instead - "Sound card support" still compiled into kernel...
HTH
[editet slightly to (try to) straighten out my grammar]
_________________
Cheers |
|
| Back to top |
|
|
queen
Veteran
Joined: 19 Jul 2005
Posts: 1642
|
| Posted: Sat Feb 16, 2008 8:04 pm Post subject: |
|
|
| jomen wrote: | ...as for me - I had nothing but trouble until I compiled alsa completely as modules.
...this is a long time ago - and this is what Alsa always suggested...
The only thing I have built into the kernel is the general option "Sound card support" - everything below that are only modules.
The last section of the page (the link I gave above) may be of help as it suggests that the drivers that come with the kernel are not up to date.
If I would have problems I'd use the stable or even latest ebuild for alsa-drivers instead - "Sound card support" still compiled into kernel...
HTH
[editet slightly to (try to) straighten out my grammar] |
The only problem is that if I use as module I can't emerge alsa-drivers. It fails. As per alsa guide if I put it as module I need to emerge alsa-drivers. |
|
| Back to top |
|
|
queen
Veteran
Joined: 19 Jul 2005
Posts: 1642
|
| Posted: Sat Feb 16, 2008 8:12 pm Post subject: |
|
|
| NeddySeagoon wrote: | queen,
Its better to build snd-intel-hda as a module, as you will almost certainly need some trial and error with module parameters to make it work.
A a module, you can unload it then reload it with new parameters. As a built in, you have to reboot.
Thats the only advantage of modules over built in.
You need to turn off all the sound related debug. Thats for developers only. It will spam your logs and cause issues of its own.
For module parameters to try, look in /usr/src/linux/Documentation/sound/alsa/ALSA-Configuration.txt |
I will remove the debug information from the kernel. The main problem is that if I use as module I can't emerge alsa-drivers as alsa guide suggests. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54304
Location: 56N 3W
|
| Posted: Sat Feb 16, 2008 8:25 pm Post subject: |
|
|
queen,
Do not emerge alsa-drivers. It provides the same functionality as the kernel alsa.
Unless your sound chip is very new, kernel alsa is preferred.
Follow the Gentoo ALSA guide except for the emerge alsa-driver step.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
jomen
Guru
Joined: 04 Jan 2006
Posts: 536
Location: Leipzig, Germany
|
| Posted: Sat Feb 16, 2008 11:46 pm Post subject: |
|
|
| Quote: | | The only problem is that if I use as module I can't emerge alsa-drivers. It fails. As per alsa guide if I put it as module I need to emerge alsa-drivers. |
I don't get it...
and - without actually checking it - that is not what this guide says
You need drivers - yes - of course.
But:
You don't need media-sound/alsa-driver!
Just select the alsa- drivers that come with the kernel.
As modules.
Not built in.
The only thing that does not need to be a module but can be built in is the general sound support: CONFIG_SOUND
You need "alsa-utils" for the init-script, the mixer and alsactl to unmute your card - too.
_________________
Cheers |
|
| Back to top |
|
|
queen
Veteran
Joined: 19 Jul 2005
Posts: 1642
|
| Posted: Sun Feb 17, 2008 9:35 am Post subject: |
|
|
| NeddySeagoon wrote: | queen,
Do not emerge alsa-drivers. It provides the same functionality as the kernel alsa.
Unless your sound chip is very new, kernel alsa is preferred.
Follow the Gentoo ALSA guide except for the emerge alsa-driver step. |
I managed to solve the problem partially as module in the kernel, as you suggested. I can restart alsasound, get kmix normally with all the features. The only problem is this: | Code: | modprobe snd-hda-intel
WARNING: Error inserting snd (/lib/modules/2.6.23-gentoo-r3/kernel/sound/core/snd.ko): Invalid module format |
Is it critical? If yes, how can I solve it?
The sound system is | Code: |
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) |
which I believe isn't too new.
The weird part is that on a laptop, with the same audio device, same kernel, audio is built in the kernel (no module) and it works. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54304
Location: 56N 3W
|
| Posted: Sun Feb 17, 2008 1:20 pm Post subject: |
|
|
queen,
That error should stop your sound from working as snd.ko is created by CONFIG_SOUND.
If it works with that error, you have allowed your modules and kernel to het out of step and have managed to get a kernel install with both
CONFIG_SOUND=M and CONFIG_SOUND=Y.
If it doesn't work, there is more information in dmesg.
Regardless of the root cause, the fix is always to rebuild and reinstall your kernel following a so you get rid of the leftovers from previous builds.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
rastman
Apprentice
Joined: 22 Jan 2007
Posts: 210
|
| Posted: Mon Feb 18, 2008 2:57 pm Post subject: |
|
|
I have the same problem. Everything worked fine with .23 kernel. The new 24-r2 gives those problems.
| Code: | /etc/init.d/alsasound restart
* WARNING: you are stopping a boot service.
* Storing ALSA Mixer Levels ...
alsactl: save_state:1497: No soundcards found...
* Error saving levels. [ !! ]
* Killing processes using ALSA ... [ ok ]
* Unloading ALSA modules ... [ ok ]
* Loading ALSA modules ...
* Loading: snd-card-0 ... [ ok ]
* Loading: snd-seq-oss ... [ ok ]
* Loading: snd-mixer-oss ... [ ok ]
* Loading: snd-pcm-oss ... [ ok ]
* ERROR: Failed to load necessary drivers [ ok ]
* Restoring Mixer Levels ...
alsactl: unrecognized option `---'
Usage: alsactl <options> command
Available options:
-h,--help this help
-f,--file # configuration file (default /etc/asound.state or /etc/asound.names)
-F,--force try to restore the matching controls as much as possible
(default mode)
-P,--pedantic don't restore mismatching controls (old default)
-d,--debug debug mode
-v,--version print version of this program
Available commands:
store <card #> save current driver setup for one or each soundcards
to configuration file
restore <card #> load current driver setup for one or each soundcards
from configuration file
names <card #> dump information about all the known present (sub-)devices
into configuration file (DEPRECATED)
* Errors while restoring defaults, ignoring |
| Code: | uname -a
Linux localhost 2.6.24-gentoo-r2 #2 SMP Mon Feb 18 15:24:44 CET 2008 x86_64 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz GenuineIntel GNU/Linux |
dmesg
| Code: | ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 22
PCI: Setting latency timer of device 0000:00:1b.0 to 64
hda-codec: No codec parser is available
hda-intel: no codecs initialized
ACPI: PCI interrupt for device 0000:00:1b.0 disabled
|
|
|
| Back to top |
|
|
queen
Veteran
Joined: 19 Jul 2005
Posts: 1642
|
| Posted: Mon Feb 18, 2008 9:21 pm Post subject: |
|
|
| NeddySeagoon wrote: | queen,
That error should stop your sound from working as snd.ko is created by CONFIG_SOUND.
If it works with that error, you have allowed your modules and kernel to het out of step and have managed to get a kernel install with both
CONFIG_SOUND=M and CONFIG_SOUND=Y.
If it doesn't work, there is more information in dmesg.
Regardless of the root cause, the fix is always to rebuild and reinstall your kernel following a so you get rid of the leftovers from previous builds. |
Unfortunately, make clean didn't help. I can start alsamixer, kmix and configure. But there is no sound and I also get the error when I try to modprobe snd-hda-intel. I also tried to modprobe snd-usb-audio because I want to use usb headsets. |
|
| Back to top |
|
|
Bloodsurfer
Guru
Joined: 07 Dec 2005
Posts: 361
Location: Wolfstein, Germany (Rhineland-Palatinate)
|
| Posted: Sat Feb 23, 2008 10:39 pm Post subject: |
|
|
| Bloodsurfer wrote: | I'm having the same problem as the original poster.
I always used compiled-in alsa-drivers (snd-hda-intel). Worked for about a year, without a problem since I first set this machine up.
Now I updated to 2.6.24 and with that alsa stopped working. I made no changes - same .config as before, everything compiled in. Error messages are the same like in the first posting here.
Did also try to compile the drivers as modules. I can load them by hand, it still doesn't recognize any soundcard.
Still works fine with old kernel. Any ideas? |
My sound still doesn't work. It just says "no soundcard found". I have everything compiled as modules now, that doesn't change a thing. Did make clean too, recompiled various times, no change.
Still works fine with kernels before 2.6.24...
_________________
SiberianSniper: my girlfriend's name ends with .c
Clete2: Uber geek! W00t! I'd rather have it end in .cpp... <insert name>.cpp
Dralnu: ...why not <name>.o? Then she's ready for linking...
SiberianSniper: or <name>.ko, so she's ready for insertion? |
|
| Back to top |
|
|
rastman
Apprentice
Joined: 22 Jan 2007
Posts: 210
|
|
| Back to top |
|
|
Bloodsurfer
Guru
Joined: 07 Dec 2005
Posts: 361
Location: Wolfstein, Germany (Rhineland-Palatinate)
|
| Posted: Sun Feb 24, 2008 10:48 am Post subject: |
|
|
Doesn't solve it, I had that option enabled... 
_________________
SiberianSniper: my girlfriend's name ends with .c
Clete2: Uber geek! W00t! I'd rather have it end in .cpp... <insert name>.cpp
Dralnu: ...why not <name>.o? Then she's ready for linking...
SiberianSniper: or <name>.ko, so she's ready for insertion? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54304
Location: 56N 3W
|
| Posted: Sun Feb 24, 2008 11:49 am Post subject: |
|
|
queen,
Lets concentrate on one sound device at a time. MAking two work is four times the problem.
Look in /dev/snd and check you have only one controlCx file, where x is 0.
Ensure its the sound card (that includes USB headsets) you want to make work by looking in lsmod.
You should see snd-hda-intel or snd-usb-audio but not both. If both are listed, remove both and modprobe the one you want to work with. Thats the only way to know which card is sound card 0 when neither works.
Open the mixer of your choice and mute everything except PCM and Master. Set their sliders around 70% and test.
Many sound chips can operate at either the SPDI/F or Analogue sample rates but not both at the same time.
Such devices default to SPDI/F if any SPDI/F options are enabled and you get no analogue operation at all.
As a result, it all looks like its working (it actually is) but you can't hear anything.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
queen
Veteran
Joined: 19 Jul 2005
Posts: 1642
|
| Posted: Thu Feb 28, 2008 10:14 am Post subject: |
|
|
| NeddySeagoon wrote: | queen,
Lets concentrate on one sound device at a time. MAking two work is four times the problem.
Look in /dev/snd and check you have only one controlCx file, where x is 0.
Ensure its the sound card (that includes USB headsets) you want to make work by looking in lsmod.
You should see snd-hda-intel or snd-usb-audio but not both. If both are listed, remove both and modprobe the one you want to work with. Thats the only way to know which card is sound card 0 when neither works.
Open the mixer of your choice and mute everything except PCM and Master. Set their sliders around 70% and test.
Many sound chips can operate at either the SPDI/F or Analogue sample rates but not both at the same time.
Such devices default to SPDI/F if any SPDI/F options are enabled and you get no analogue operation at all.
As a result, it all looks like its working (it actually is) but you can't hear anything. |
Hello Neddy
Sorry for the late reply. I checked | Code: | | /dev/snd and I have controlC0 |
| Code: | lsmod
Module Size Used by
snd_usb_audio 52448 1
snd_usb_lib 14592 1 snd_usb_audio
snd_rawmidi 18208 1 snd_usb_lib
snd_hwdep 9988 1 snd_usb_audio
snd_pcm_oss 33696 0
snd_mixer_oss 15872 1 snd_pcm_oss
snd_seq_oss 25984 0
snd_seq_midi_event 7680 1 snd_seq_oss
snd_seq 35536 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 8588 3 snd_rawmidi,snd_seq_oss,snd_seq |
So the usb headsets are found ok. I see in kmix configuration that I have logitec usb headset and hda-intel. I selected hda-intel. And enabled PCM. In kmix I don't see Master as well. In alsamixer I see PCM but no Master.
| Code: | | Bus 005 Device 002: ID 046d:0a02 Logitech, Inc. |
Right now I still don't hear anything. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54304
Location: 56N 3W
|
| Posted: Thu Feb 28, 2008 6:48 pm Post subject: |
|
|
queen,
Its not clear to me if you are looking at your USB or Intel sound hardware.
Your lsmod shows snd_usb_audio but not snd-intel-hda so only your USB driver is loaded unless snd-intel-hda is build into the kernel, which would be really bad news from the alsa debug point of view.
Lets check your kernel | Code: | | zgrep HDA /proc/config.gz |
should show either # CONFIG_SND_HDA_INTEL is not set or CONFIG_SND_HDA_INTEL = m
If it shows =y, you will have problems because you will almost certainly need some trial and error with the model= kernel option when the module loads. If your driver is built in, its difficult to pass it module parameters in this way, it can be done but the trail and error needs a reboot for every try.
By defualt, your sound appllcations use sound device 0. When you have several sound devices, which one is which is poorly defined.
Sound device 0 is always the first on started, which can very from boot to boot. Thats why we need to make your devices work one at a time, then fix their names.
USB sound devices usually just work, so lets work with that one first.
Check that when lsmod shows snd_usb_audio you have a /dev/snd/controlC0 and no other /dev/snd/controlCx entries.
That confirms that your headset is the default sound device.
Hang the headset round your neck, *not* over your ears, or this may be painful.
Play some music, unmute PCM and turn the level up. Do the same for Master if you have it.
A good test application is something you can force to use ALSA, like mplayer, with the -ao alsa option.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
queen
Veteran
Joined: 19 Jul 2005
Posts: 1642
|
| Posted: Fri Feb 29, 2008 5:28 am Post subject: |
|
|
| NeddySeagoon wrote: | queen,
Its not clear to me if you are looking at your USB or Intel sound hardware.
Your lsmod shows snd_usb_audio but not snd-intel-hda so only your USB driver is loaded unless snd-intel-hda is build into the kernel, which would be really bad news from the alsa debug point of view.
Lets check your kernel | Code: | | zgrep HDA /proc/config.gz |
should show either # CONFIG_SND_HDA_INTEL is not set or CONFIG_SND_HDA_INTEL = m |
I am sure I configured hda_intel as module as you adviced me in previous post. That's how I managed to get a proper alsamixer with all the settings, which I didn't have before.
I used copy/paste from the lsmod, so there is a chance I didn't copied everything that was related to snd. I also have in /etc/modules.d/kernel-2.6 snd-hda and snd-usb (The names of the modules are fine, because I wrote them down when I was in the kernel) AND there was a reboot 2 days ago. BUT to be totally sure that hda-intel is indeed loaded, I will check it on sunday when I return back to work.
| Quote: |
USB sound devices usually just work, so lets work with that one first.
Check that when lsmod shows snd_usb_audio you have a /dev/snd/controlC0 and no other /dev/snd/controlCx entries.
That confirms that your headset is the default sound device. |
I am sure there was only /dev/snd/controlC0 and nothing else.
| Quote: | Play some music, unmute PCM and turn the level up. Do the same for Master if you have it.
A good test application is something you can force to use ALSA, like mplayer, with the -ao alsa option. |
I played with mplayer before these instructions, both wav and mp3. For wav it selected pcm library and for mp3 the mp3 library. But there was no sound in both cases, although I didn't select the -ao alsa option. I will try it on sunday and see what happens.
Thank you so far. |
|
| Back to top |
|
|
queen
Veteran
Joined: 19 Jul 2005
Posts: 1642
|
| Posted: Sun Mar 02, 2008 7:58 am Post subject: |
|
|
here are the results: | Code: | zgrep HDA /proc/config.gz
CONFIG_SENSORS_HDAPS=m
CONFIG_SND_HDA_INTEL=m |
| Code: | lsmod |grep snd
snd_usb_audio 52448 1
snd_usb_lib 14592 1 snd_usb_audio
snd_rawmidi 18208 1 snd_usb_lib
snd_hwdep 9988 1 snd_usb_audio
snd_pcm_oss 33696 0
snd_mixer_oss 15872 1 snd_pcm_oss
snd_seq_oss 25984 0
snd_seq_midi_event 7680 1 snd_seq_oss
snd_seq 35536 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 8588 3 snd_rawmidi,snd_seq_oss,snd_seq
snd_hda_intel 216732 1
snd_pcm 47492 3 snd_usb_audio,snd_pcm_oss,snd_hda_intel
snd_timer 18308 2 snd_seq,snd_pcm
snd 33508 15 snd_usb_audio,snd_rawmidi,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer
snd_page_alloc 10504 2 snd_hda_intel,snd_pcm
usbcore 92296 8 snd_usb_audio,snd_usb_lib,usbhid,ohci_hcd,uhci_hcd,usb_storage,ehci_hcd |
BUT
| Code: |
ls /dev/snd/control*
/dev/snd/controlC0 /dev/snd/controlC1 If I have the usb headsets plugged in, and only ControlC0 if the headsets are not plugged in. |
Is that OK? |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54304
Location: 56N 3W
|
| Posted: Sun Mar 02, 2008 2:53 pm Post subject: |
|
|
queen,
Thats OK if its consistant. For testing, do the following, with your headset connected.
Run lsmod and check you have both | Code: | snd_usb_audio
snd_hda_intel |
Now do | Code: | modprobe -r snd_usb_audio
modprobe -r snd_hda_intel |
to remove them both.
Lastly | Code: | | modprobe snd_usb_audio |
After that sequence, only snd_usb_audio is loaded and we know its your default sound device.
Run the mixer of your choice, unmute PCM (it will hot have a master) set the slider to about 70% and test.
This is the easy one, we will make it work as the default device before we try anything else.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
queen
Veteran
Joined: 19 Jul 2005
Posts: 1642
|
| Posted: Wed Mar 05, 2008 7:53 pm Post subject: |
|
|
| NeddySeagoon wrote: | queen,
Thats OK if its consistant. For testing, do the following, with your headset connected.
Run lsmod and check you have both | Code: | snd_usb_audio
snd_hda_intel |
Now do | Code: | modprobe -r snd_usb_audio
modprobe -r snd_hda_intel |
to remove them both.
Lastly | Code: | | modprobe snd_usb_audio |
After that sequence, only snd_usb_audio is loaded and we know its your default sound device.
Run the mixer of your choice, unmute PCM (it will hot have a master) set the slider to about 70% and test.
This is the easy one, we will make it work as the default device before we try anything else. |
I ran the commands you said. I remained with /dev/snd/controlC1. I read a little bit in google about the usb headset. Many other distributions have the problem with usb headsets. I checked with normal headsets and it works. 
I was a little bit lazy to put the normal headsets because it's on the back of the pc and it was kind of hard to reach there. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Multimedia
