+++ This bug was initially created as a clone of Bug #109475 +++ I use a onboard nVidia sound chip with a Realtek codec: ALC662 rev1. I installed alsa as kernel modules with snd-hda-intel. I've run alsaconf and it detected the sound card. /etc/init.d/alsasound runs, but when I try to run alsamixer to unmute my card it always returned this error: alsamixer: function snd_mixer_load failed: Invalid argument Reproducible: Always Possible solution: I think I solved the bug, but it may not be a permanent solution. This is what I have done: In the file /usr/src/linux/sound/pci/hda/patch_realtek.c nearly at the bottom I commented out the following lines: /* { .id = 0x10ec0662, .rev = 0x100101, .name = "ALC662 rev1", .patch = patch_alc662 }, */ and then I recompiled kernel and modules. Then the alsamixer runs and sound seems to be ok. It looks as if the original driver is doing wrong...
lspci -vv output for the soundcard, please.
00:05.0 Audio device: nVidia Corporation MCP61 High Definition Audio (rev a2) Subsystem: ASUSTeK Computer Inc. Unknown device 8290 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 (500ns min, 1250ns max) Interrupt: pin B routed to IRQ 23 Region 0: Memory at dfff8000 (32-bit, non-prefetchable) [size=16K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Masking: 00000000 Pending: 00000000 Capabilities: [6c] HyperTransport: MSI Mapping Enable- Fixed+
same here, with ALC861 lspci -vv: 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) Subsystem: Toshiba America Info Systems Unknown device ff10 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 22 Region 0: Memory at f0b40000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [60] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us ExtTag- RBE- FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed unknown, Width x0, ASPM unknown, Latency L0 <64ns, L1 <1us ClockPM- Suprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt- Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel
I have a M2N-MX SE ASUS MOBO which uses the MCP61 High Definition Audio / ALC662 chipset - snd-hda-intel module and exactly the same bug happens with me. Alsa support is installed in the kernel as modules. alsaconf works, detects audio as MCP61 High... and sets the appropriate values in modules.d/alsa But when I run alsamixer I get the following message: alsamixer: function snd_mixer_load failed: Invalid argument I think it has to do with unrecognized models as dmesg shows: hda_codec: Unknown model for ALC662, trying auto-probe from BIOS... when I try: modprobe snd_hda_intel model=3stack or model=asus which is my configuration. Also, amixer -c 0 controls reports: numid=3,iface=MIXER,name='Headphone Playback Switch' numid=17,iface=MIXER,name='PCM Playback Volume' numid=7,iface=MIXER,name='Front Mic Playback Switch' numid=6,iface=MIXER,name='Front Mic Playback Volume' numid=2,iface=MIXER,name='Front Playback Switch' amixer: Control hw:0 snd_hctl_elem_info error: Invalid argument But I'm using the back panel, not the front mic/playback etc...
same here ;( asus eee pc 701, gentoo-sources-2.6.23-r9 + two patches from geeentoo.com alsa-utils 1.0.14
here is the fix :) http://forums.gentoo.org/viewtopic-t-665534.html?sid=553db27df86cdedc17f6f6d9c39ae97a needs a model=3stack-dig option.
Works for me! Thanks Ilya. I guess it's resolved now.
Doesn't work for me. Still open.
(In reply to comment #8) > Doesn't work for me. Still open. Make sure you read /usr/src/linux/Documentation/sound/alsa/ALSA-Configuration.txt, find your model, and use that and maybe fiddle around a bit. Depending on your soundcard R Bar-On.. ALC861/660 3stack 3-jack 3stack-dig 3-jack with SPDIF I/O 6stack-dig 6-jack with SPDIF I/O 3stack-660 3-jack (for ALC660) uniwill-m31 Uniwill M31 laptop toshiba Toshiba laptop support asus Asus laptop support asus-laptop ASUS F2/F3 laptops auto auto-config reading BIOS (default) ALC861VD/660VD 3stack 3-jack 3stack-dig 3-jack with SPDIF OUT 6stack-dig 6-jack with SPDIF OUT 3stack-660 3-jack (for ALC660VD) 3stack-660-digout 3-jack with SPDIF OUT (for ALC660VD) lenovo Lenovo 3000 C200 dallas Dallas laptops hp HP TX1000 auto auto-config reading BIOS (default)
Already done that. I've gone through every single option and exactly the same thing happens. Ubuntu appears to have the same bug: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/192382
Could it be that aplay -l simply lists the support you've build for it into the kernel? For example, i deselected everything except intel hda Generic support, and now my PC shows this: card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic] Subdevices: 0/1 Subdevice #0: subdevice #0 Which is actually nonsense, cause it's, from what i expect, a ALC262 or something. Alsamixer, when i fire it up though, says: Chip: Realtek ID 262, while i didn't build support for the Realtek series. So what i actually wanna say is, if you build support in the module for one type or all at once, it might be using the wrong one automaticly cause it's detecting the whole shizzle wrong. Alsa does need to improve the support for the intel hda cards.
at a guess it's using the generic parser for the realtek-detected chip because you did not build the realtek parser into the kernel
(In reply to comment #12) > at a guess it's using the generic parser for the realtek-detected chip because > you did not build the realtek parser into the kernel Yup, but i was aiming at the idea that it _could_ start getting problems if i build it _with_ the realtek parser, and trying to help R Bar-On afaik. I'll try to replace the Generic parser with the Realtek parser soon, and give more info. On a side note, just remembered that the grml 0.2 x86_64 cd booted up and loaded alsa perfectly from start without doing any tricks, gonna see why that one went well, and report back with all the info i have.
I recompiled the kernel module with all options selected and unloaded and reloaded all the relevant modules. Still the same. By the way, this should be hardware ALL, as I have x86.
After massive restarts due to intensive testing, these are my results.. The card i have is, from what i should believe whatever i try, an ALC262. This would mean it's a Realtek card. Though, whatever parser i choose.. it _ONLY_ works if i _deselect all parsers_ except for the Generic one, leaving that as the only parser support in the snd-hda-intel module. Giving model types didn't give much difference either.
Ubuntu has fixed this. Apparently it's fixed in alsa-driver over there, so if the Gentoo people would be so kind as to pull the same fixes in Portage, I'd be very grateful.
(In reply to comment #16) > Ubuntu has fixed this. Apparently it's fixed in alsa-driver over there, so if > the Gentoo people would be so kind as to pull the same fixes in Portage, I'd be > very grateful. > Do you have a link that refers to this fix?
There are further problems apparently: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/192382
The Ubuntu defect that was referenced in comment #10 (https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/192382) does not describe the same problem. Although there is a similarity in that alsamixer fails with "snd_mixer_load failed" in both issues, there is a difference in the listed failure reason: Ubuntu bug: alsamixer: function snd_mixer_load failed: No such file or directory This issue: alsamixer: function snd_mixer_load failed: Invalid argument The Ubuntu bug was caused by an ALSA component version mismatch, which they fixed. This issue seems to have an invalid automatic selection of the model at its core, which is an ALSA bug at best. I have the same problem on Fedora, so it's not specific to Gentoo. On my system I was able to resolve the problem by adding one of the options listed in comment #9 (thanks Marvin!) You may need to experiment a bit, because the wrong choice will yield the same error as not specifying a "model=" value to the snd-hda-intel module at all.
Rudolf, is this any better as of 2.6.25? Anyone else who thinks they are affected by this bug should file new bug reports (assuming 2.6.25 is still broken). There is so much HDA hardware (and the errors always look the same) that it is easier to deal separately (even if it turns out to be the same fix). Thanks for your patience.
(In reply to comment #20) > Rudolf, is this any better as of 2.6.25? Daniel, what do you mean with "this"?
Can you play any audio and/or unmute your card under 2.6.25?
dmesg hda_codec: Unknown model for ALC262, trying auto-probe from BIOS... hda-codec: No codec parser is available ALSA device list: #0: HDA Intel at 0xd9320000 irq 22 grep SND /usr/src/linux-2.6.25-gentoo-r6/.config | grep -v \# CONFIG_SND=y CONFIG_SND_TIMER=y CONFIG_SND_PCM=y CONFIG_SND_OSSEMUL=y CONFIG_SND_MIXER_OSS=y CONFIG_SND_PCM_OSS=y CONFIG_SND_PCM_OSS_PLUGINS=y CONFIG_SND_RTCTIMER=y CONFIG_SND_HDA_INTEL=y CONFIG_SND_HDA_CODEC_REALTEK=y Fully operation without _any_ further warnings, errors, or problems yet. Awesome :)
(In reply to comment #23) > Can you play any audio and/or unmute your card under 2.6.25? > @Daniel: I can't use 2.6.25, because with emerge --sync done today I get sys-kernel/gentoo-sources only up to 2.6.23-r3, which I use actally or a masked 2.6.23-r5 version. Is that due to AMD64?
gentoo-sources-2.6.25-r6 is stable on amd64, I suggest following up in a user support forum to figure out why the new version is not available to you.. ("emerge =gentoo-sources-2.6.25-r6" should give you some hints)
(In reply to comment #26) > ("emerge =gentoo-sources-2.6.25-r6" should give you some hints) This emerge gave no hint - but it worked. I just had to handle some minor difficulties (for some hours...) to get the new kernel running, but now everything seems to be ok: - snd_hda_intel works only as a module, but not built into the kernel. - as I use nvidia graphics, I had to switch to a separate nvidia module to be able to start the graphical desktop with kernel 2.6.25 and I had to use x11-drivers/nvidia-drivers-169.12, which is masked for amd64, but works. - alsamixer is running and the sound is good!
I guess I better had not changed the kernel. I am still struggling with problems following the kernel change. I did an emerge -qvDNua world that finished without errors. Some time after that I lost the sound. First all seemd to be ok and kmplayer was able to play sound. Then I started alsamixer again, changed some loudness, and from then on there was no sound any more. - kmplayer says "mplayer buffering" but does not show any elapsed time and is silent. - mplayer started on a console seems to run but is silent too. - with alsamixer I can change any settings, mute or unmute... still no sound. - kmix and alsamixer show the same settings vice versa. - alsamixer shows Card: HDA NVidia, Chip: Realtek ALC662 rev1.
One point to mention that made no sense - but I couldn't detect how it came: Earlier kernel versions were built as arch/x86_64/boot/bzImage. Now when I make the kernel I get it as arch/x86/boot/bzImage. I looked into the Makefile but did't see any reason for that and uname -m still says "x86_64".
(In reply to comment #29) > One point to mention that made no sense - but I couldn't detect how it came: > Earlier kernel versions were built as arch/x86_64/boot/bzImage. Now when I make > the kernel I get it as arch/x86/boot/bzImage. > I looked into the Makefile but did't see any reason for that and > uname -m > still says "x86_64". Please refrain from discussing problems not related to this bug. It causes unneeded email traffic and comments and beside the fact that it may confuse people, i can imagine people unsubscribing from a bug just cause they're getting spammed with this.
@ kernel@gentoo.org: The error message "alsamixer: function snd_mixer_load failed: Invalid argument" is now gone, but sound does not work any more, and before, it did. See also http://forums.gentoo.org/viewtopic-t-697564-highlight-.html Should we now - close this bug and open a new one? - change the summary of this bug? Rudolf
Someone on the forums has claimed success with 2.6.27_rc3. Can you test with a git-sources-2.6.27_rc3-rX release and post back the results here.
I will try mid of september - until then I'm on holiday... Rudolf
I get the following error: emerge: there are no ebuilds to satisfy "git-sources-2.6.27_rc3-rX". please advice
X was a variable. :) Right now, the latest git-sources is git-sources-2.6.27_rc6-r5
when trying to emerge, I get - sys-kernel/git-sources-2.6.27_rc6-r5 (masked by: ~amd64 keyword)
Try referring to the documentation: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3#doc_chap2
I did as suggested: I put the line =sys-kernel/git-sources-2.6.27_rc6-r5 into the (new) file /etc/portage/package.unmask bur emerge still says !!! All ebuilds that could satisfy "sys-kernel/git-sources" have been masked. !!! One of the following masked packages is required to complete your request: - sys-kernel/git-sources-2.6.27_rc6-r5 (masked by: ~amd64 keyword) ...
This is the section of the document you need to check out. 3.b. Mixing Stable with Testing You're should be using /etc/portage/package.keywords Please test with gentoo-sources-2.6.27
(In reply to comment #39) > This is the section of the document you need to check out. > > 3.b. Mixing Stable with Testing > > You're should be using /etc/portage/package.keywords > > Please test with gentoo-sources-2.6.27 > I am facing the same difficulty. I created the file /etc/portage/package.keywords and populated it thus: media-sound/alsa-driver ~x86 media-sound/alsamixer-app ~x86 media-sound/alsaplayer ~x86 and then set about: # emerge git-sources only to return: !!! All ebuilds that could satisfy "sys-kernel/git-sources" have been masked. !!! One of the following masked packages is required to complete your request: - sys-kernel/git-sources-2.6.27_rc7-r5 (masked by: package.mask, ~x86 keyword) I suppose I populated the package.keywords file incorrectly, or created it wrong? Or I need to edit a package.mask file somewhere?
Please read your error messages. "One of the following masked packages is required to complete your request: - sys-kernel/git-sources-2.6.27_rc7-r5 (masked by: package.mask, ~x86 keyword)" This is saying that git-sources is masked by the ~x86 *keyword*. 1. Log into machine 2. su - root 3. remove these lines from /etc/portage/package.keywords media-sound/alsa-driver ~x86 media-sound/alsamixer-app ~x86 media-sound/alsaplayer ~x86 4. Put this line into /etc/portage/package.keywords =sys-kernel/git-sources-2.6.27-r4 5. emerge -a git-sources 6. configure, build and install this kernel 7. test your issue
I had no time up to now - sorry. Now I used vanilla-sources-2.6.27.5 for a new kernel Everything is OK except sound. Mixer is unmuted and everything looks as it should, but there is nothing to hear. Should I file a new bug or reopen this one?
Thanks for testing. OK, that is progress at least in some form :) If you apply the same "fix" as you mentioned in comment #0, does sound start working again?
No, I checked that, it doesn't work. When writing comment #0 alsamixer did not start, now it does without changig the file /usr/src/linux/sound/pci/hda/patch_realtek.c To me it looks as if there is another point where sound is blocked, one that alsamixer is not aware of.
Alright, some progress then. Please upgrade to the latest development kernel, currently v2.6.28-rc6, confirm the bug still exists there, and file a bug upstream at http://bugzilla.kernel.org When done, post the new URL here. Try to keep the history brief (no need to repeat everything that has happened here), just state that with earlier kernels you had no sound and this error message: alsamixer: function snd_mixer_load failed: Invalid argument and now you just have no sound but no error message. While under 2.6.28-rc6, please run "./alsa-info.sh --no-upload" and attach the output on the bug. You can get alsa-info.sh here: http://git.alsa-project.org/?p=alsa-driver.git;a=blob_plain;f=utils/alsa-info.sh Thanks!
I tried to upgrade to 2.6.28_rc6, but without success, because the graphics driver did not compile with an error message I did not understand: * Messages for package x11-drivers/nvidia-drivers-177.80: * * ERROR: x11-drivers/nvidia-drivers-177.80 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3710: Called linux-mod_src_compile * environment, line 2729: Called die * The specific snippet of code: * eval "emake HOSTCC=\"$(tc-getBUILD_CC)\" CROSS_COMPILE=${CHOST}- LDFLAGS=\"$(get_abi_LDFLAGS)\" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}"; * The die message: * Unable to emake HOSTCC=x86_64-pc-linux-gnu-gcc CROSS_COMPILE=x86_64-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/usr/src/linux HOST_CC=x86_64-pc-linux-gnu-gcc clean module
You shouldn't need to compile nvidia-drivers in order to simply boot into 2.6.28, test sound, and run alsa-info.
closed here and filed as a new bug at http://bugzilla.kernel.org/show_bug.cgi?id=12130
Now I found the error: hardware didn't work. After replacing the mainboard everything is fine...
