kernel 2.6.14.x and alsamixer problems

kernel 2.6.14.x and alsamixer problems

[Jon]

Greetings all. Ever since I upgraded to linux-2.6.14 and up, I get this
error when running 'alsamixer'


ALSA lib simple_none.c:1216:(simple_add1) helem (MIXER,'Front Playback
Volume',0,0,0) appears twice or more
alsamixer: function snd_mixer_load failed: Invalid argument


It does it with alsa-1.0.9 and 1.0.10... I use alsa
{driver,lib,oss,utils} on my box and leave the kernel sound section
alone. As soon as I switch back to 2.6.13.4 it plays nice once again
which is confusing to me...... I'm using the emu10k1 chip (SB Live!
Value 5.1). Any insight on this matter would be greatly appreciated...

Jon


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click

Re: kernel 2.6.14.x and alsamixer problems

[Jon]

Jon wrote:

>Greetings all. Ever since I upgraded to linux-2.6.14 and up, I get this
>error when running 'alsamixer'
>
>
>ALSA lib simple_none.c:1216:(simple_add1) helem (MIXER,'Front Playback
>Volume',0,0,0) appears twice or more
>alsamixer: function snd_mixer_load failed: Invalid argument
>
>
>It does it with alsa-1.0.9 and 1.0.10... I use alsa
>{driver,lib,oss,utils} on my box and leave the kernel sound section
>alone. As soon as I switch back to 2.6.13.4 it plays nice once again
>which is confusing to me...... I'm using the emu10k1 chip (SB Live!
>Value 5.1). Any insight on this matter would be greatly appreciated...
>
>Jon
>
>  
>
Opps... Sorry. Posted to the wrong list although I have a feeling it
might eventually need to be here as well.


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click

Re: kernel 2.6.14.x and alsamixer problems

[James Courtier-Dutton]

Jon wrote:
> Greetings all. Ever since I upgraded to linux-2.6.14 and up, I get this
> error when running 'alsamixer'
> 
> 
> ALSA lib simple_none.c:1216:(simple_add1) helem (MIXER,'Front Playback
> Volume',0,0,0) appears twice or more
> alsamixer: function snd_mixer_load failed: Invalid argument
> 
> 
> It does it with alsa-1.0.9 and 1.0.10... I use alsa
> {driver,lib,oss,utils} on my box and leave the kernel sound section
> alone. As soon as I switch back to 2.6.13.4 it plays nice once again
> which is confusing to me...... I'm using the emu10k1 chip (SB Live!
> Value 5.1). Any insight on this matter would be greatly appreciated...
> 
> Jon
> 
> 

Does you alsa-lib version match your alsa-driver version.
Use the troubleshooter on
http://alsa.opensrc.org/TroubleShooting
to find out.


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click

Re: kernel 2.6.14.x and alsamixer problems

[Jon]

James Courtier-Dutton wrote:

> Jon wrote:
>
>> Greetings all. Ever since I upgraded to linux-2.6.14 and up, I get this
>> error when running 'alsamixer'
>>
>>
>> ALSA lib simple_none.c:1216:(simple_add1) helem (MIXER,'Front Playback
>> Volume',0,0,0) appears twice or more
>> alsamixer: function snd_mixer_load failed: Invalid argument
>>
>>
>> It does it with alsa-1.0.9 and 1.0.10... I use alsa
>> {driver,lib,oss,utils} on my box and leave the kernel sound section
>> alone. As soon as I switch back to 2.6.13.4 it plays nice once again
>> which is confusing to me...... I'm using the emu10k1 chip (SB Live!
>> Value 5.1). Any insight on this matter would be greatly appreciated...
>>
>> Jon
>>
>>
>
> Does you alsa-lib version match your alsa-driver version.
> Use the troubleshooter on
> http://alsa.opensrc.org/TroubleShooting
> to find out.
>
Yes, I'm always carefull to run matching versions. As soon as I upgraded 
to the 2.6.14 kernel, this started happening. I hadn'nt even touched my 
alsa packages, except alsa-driver ofcourse. I used the same version but 
just compiled the new modules against the new kernel. I've found other 
people having the same problem on the web, but the posts ussually go 
unanswered... :-(


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click

Re: kernel 2.6.14.x and alsamixer problems

[James Courtier-Dutton]

Jon wrote:
> James Courtier-Dutton wrote:
> 
>> Jon wrote:
>>
>>> Greetings all. Ever since I upgraded to linux-2.6.14 and up, I get this
>>> error when running 'alsamixer'
>>>
>>>
>>> ALSA lib simple_none.c:1216:(simple_add1) helem (MIXER,'Front Playback
>>> Volume',0,0,0) appears twice or more
>>> alsamixer: function snd_mixer_load failed: Invalid argument
>>>
>>>
>>> It does it with alsa-1.0.9 and 1.0.10... I use alsa
>>> {driver,lib,oss,utils} on my box and leave the kernel sound section
>>> alone. As soon as I switch back to 2.6.13.4 it plays nice once again
>>> which is confusing to me...... I'm using the emu10k1 chip (SB Live!
>>> Value 5.1). Any insight on this matter would be greatly appreciated...
>>>
>>> Jon
>>>
>>>
>>
>> Does you alsa-lib version match your alsa-driver version.
>> Use the troubleshooter on
>> http://alsa.opensrc.org/TroubleShooting
>> to find out.
>>
> Yes, I'm always carefull to run matching versions. As soon as I upgraded 
> to the 2.6.14 kernel, this started happening. I hadn'nt even touched my 
> alsa packages, except alsa-driver ofcourse. I used the same version but 
> just compiled the new modules against the new kernel. I've found other 
> people having the same problem on the web, but the posts ussually go 
> unanswered... :-(
> 

Can you post the output from the troubleshooting steps here please.



-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click

Re: kernel 2.6.14.x and alsamixer problems

[Jon Grosshart]

[-- Attachment #1: Type: text/plain, Size: 5883 bytes --]

On 11/20/05, James Courtier-Dutton <James@superbug.co.uk> wrote:
>
> Jon wrote:
> > James Courtier-Dutton wrote:
> >
> >> Jon wrote:
> >>
> >>> Greetings all. Ever since I upgraded to linux-2.6.14 and up, I get
> this
> >>> error when running 'alsamixer'
> >>>
> >>>
> >>> ALSA lib simple_none.c:1216:(simple_add1) helem (MIXER,'Front Playback
> >>> Volume',0,0,0) appears twice or more
> >>> alsamixer: function snd_mixer_load failed: Invalid argument
> >>>
> >>>
> >>> It does it with alsa-1.0.9 and 1.0.10... I use alsa
> >>> {driver,lib,oss,utils} on my box and leave the kernel sound section
> >>> alone. As soon as I switch back to 2.6.13.4 <http://2.6.13.4> it plays
> nice once again
> >>> which is confusing to me...... I'm using the emu10k1 chip (SB Live!
> >>> Value 5.1). Any insight on this matter would be greatly appreciated...
> >>>
> >>> Jon
> >>>
> >>>
> >>
> >> Does you alsa-lib version match your alsa-driver version.
> >> Use the troubleshooter on
> >> http://alsa.opensrc.org/TroubleShooting
> >> to find out.
> >>
> > Yes, I'm always carefull to run matching versions. As soon as I upgraded
> > to the 2.6.14 kernel, this started happening. I hadn'nt even touched my
> > alsa packages, except alsa-driver ofcourse. I used the same version but
> > just compiled the new modules against the new kernel. I've found other
> > people having the same problem on the web, but the posts ussually go
> > unanswered... :-(
> >
>
> Can you post the output from the troubleshooting steps here please.
>
>

I sure can.. Sorry about that. Here is the output from aadebug


[root@jaguar ~/Desktop] ./aadebug
ALSA Audio Debug v0.1.0 - Tue Nov 22 00:29:54 EST 2005
http://alsa.opensrc.org/index.php?page=aadebug
http://www.gnu.org/licenses/gpl.txt

Kernel ----------------------------------------------------
Linux jaguar 2.6.14.2 <http://2.6.14.2> #1 SMP Wed Nov 16 15:38:45 EST 2005
i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux

Loaded Modules --------------------------------------------
snd_pcm_oss 48544 0
snd_mixer_oss 17664 2 snd_pcm_oss
snd_emu10k1 117412 1
snd_rawmidi 21408 1 snd_emu10k1
snd_seq_device 7948 2 snd_emu10k1,snd_rawmidi
snd_ac97_codec 91936 1 snd_emu10k1
snd_pcm 81412 3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec
snd_timer 22148 2 snd_emu10k1,snd_pcm
snd_ac97_bus 2816 1 snd_ac97_codec
snd_page_alloc 9352 2 snd_emu10k1,snd_pcm
snd_util_mem 4352 1 snd_emu10k1
snd_hwdep 7968 1 snd_emu10k1
snd 49124 9
snd_pcm_oss,snd_mixer_oss,snd_emu10k1,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer,snd_hwdep

Proc Config -----------------------------------------------
CONFIG_SOUND=m
# CONFIG_SND is not set
# CONFIG_SOUND_PRIME is not set

Modprobe Conf ---------------------------------------------
alias snd-card-0 snd-emu10k1
alias sound-slot-0 snd-emu10k1

Proc Asound -----------------------------------------------
Advanced Linux Sound Architecture Driver Version 1.0.10.
Compiled on Nov 18 2005 for kernel 2.6.14.2 <http://2.6.14.2> (SMP).
0 [Live ]: EMU10K1 - SB Live [Unknown]
SB Live [Unknown] (rev.10, serial:0x80661102) at 0xdda0, irq 21
4: [0- 0]: hardware dependent
8: [0- 0]: raw midi
19: [0- 3]: digital audio playback
18: [0- 2]: digital audio playback
26: [0- 2]: digital audio capture
25: [0- 1]: digital audio capture
16: [0- 0]: digital audio playback
24: [0- 0]: digital audio capture
0: [0- 0]: ctl
33: : timer
00-00: EMU10K1 (FX8010)
00-00: emu10k1 : ADC Capture/Standard PCM Playback : playback 32 : capture 1
00-01: emu10k1 mic : Mic Capture : capture 1
00-02: emu10k1 efx : Multichannel Capture/PT Playback : playback 8 : capture
1
00-03: emu10k1 : Multichannel Playback : playback 1
cat: /proc/asound/seq/clients: No such file or directory

Dev Snd ---------------------------------------------------
controlC0 midiC0D0 pcmC0D0p pcmC0D2c pcmC0D3p
hwC0D0 pcmC0D0c pcmC0D1c pcmC0D2p timer

CPU -------------------------------------------------------
model name : Intel(R) Pentium(R) 4 CPU 3.00GHz
cpu MHz : 2992.835
model name : Intel(R) Pentium(R) 4 CPU 3.00GHz
cpu MHz : 2992.835

RAM -------------------------------------------------------
MemTotal: 514840 kB
SwapTotal: 1020116 kB

Hardware --------------------------------------------------
00:00.0 Host bridge: Intel Corporation 82875P/E7210 Memory Controller Hub
(rev 02)
02:02.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)



Now, I still have sound... Somewhat.... It comes out the back two speakers
but not the front two. I can use the gnome sound control to atleast get it
to where I can hear something... I just can't open alsamixer and tweak it
out...
>From the Troubleshooting list:


1.) I am using alsa-driver and not the built-in kernel modules

2.) [root@jaguar ~/Desktop] cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 1.0.10.
Compiled on Nov 18 2005 for kernel 2.6.14.2 <http://2.6.14.2> (SMP).

3.) [root@jaguar ~/Desktop] grep VERSION_STR /usr/include/alsa/version.h
#define SND_LIB_VERSION_STR "1.0.10"

4.) [root@jaguar ~/Desktop] cat /proc/asound/cards
0 [Live ]: EMU10K1 - SB Live [Unknown]
SB Live [Unknown] (rev.10, serial:0x80661102) at 0xdda0, irq 21

[root@jaguar ~/Desktop] lspci | egrep audio
02:02.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 0a)


5.) [root@jaguar ~/Desktop] alsamixer
ALSA lib simple_none.c:1216:(simple_add1) helem (MIXER,'Front Playback
Volume',0,0,0) appears twice or more

alsamixer: function snd_mixer_load failed: Invalid argument

6.) I hate to admit it, but I ussually only run as root. From step 6 and
beyond, it seems pretty trivial to do.



Let me know if there is anything else I can provide and thank you James for
your help. I really do apprecieate it...

[-- Attachment #2: Type: text/html, Size: 8982 bytes --]

Re: kernel 2.6.14.x and alsamixer problems

[Jon Grosshart]

[-- Attachment #1: Type: text/plain, Size: 7460 bytes --]

On 11/22/05, Jon Grosshart <jgrosshart@gmail.com> wrote:
>
> On 11/20/05, James Courtier-Dutton <James@superbug.co.uk> wrote:
> >
> > Jon wrote:
> > > James Courtier-Dutton wrote:
> > >
> > >> Jon wrote:
> > >>
> > >>> Greetings all. Ever since I upgraded to linux-2.6.14 and up, I get
> > this
> > >>> error when running 'alsamixer'
> > >>>
> > >>>
> > >>> ALSA lib simple_none.c:1216:(simple_add1) helem (MIXER,'Front
> > Playback
> > >>> Volume',0,0,0) appears twice or more
> > >>> alsamixer: function snd_mixer_load failed: Invalid argument
> > >>>
> > >>>
> > >>> It does it with alsa-1.0.9 and 1.0.10... I use alsa
> > >>> {driver,lib,oss,utils} on my box and leave the kernel sound section
> > >>> alone. As soon as I switch back to 2.6.13.4 it plays nice once again
> > >>> which is confusing to me...... I'm using the emu10k1 chip (SB Live!
> > >>> Value 5.1). Any insight on this matter would be greatly
> > appreciated...
> > >>>
> > >>> Jon
> > >>>
> > >>>
> > >>
> > >> Does you alsa-lib version match your alsa-driver version.
> > >> Use the troubleshooter on
> > >> http://alsa.opensrc.org/TroubleShooting
> > >> to find out.
> > >>
> > > Yes, I'm always carefull to run matching versions. As soon as I
> > upgraded
> > > to the 2.6.14 kernel, this started happening. I hadn'nt even touched
> > my
> > > alsa packages, except alsa-driver ofcourse. I used the same version
> > but
> > > just compiled the new modules against the new kernel. I've found other
> > > people having the same problem on the web, but the posts ussually go
> > > unanswered... :-(
> > >
> >
> > Can you post the output from the troubleshooting steps here please.
> >
> >
>
> I sure can.. Sorry about that. Here is the output from aadebug
>
>
> [root@jaguar ~/Desktop] ./aadebug
> ALSA Audio Debug v0.1.0 - Tue Nov 22 00:29:54 EST 2005
> http://alsa.opensrc.org/index.php?page=aadebug
> http://www.gnu.org/licenses/gpl.txt
>
> Kernel ----------------------------------------------------
> Linux jaguar 2.6.14.2 #1 SMP Wed Nov 16 15:38:45 EST 2005 i686 Intel(R)
> Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
>
> Loaded Modules --------------------------------------------
> snd_pcm_oss            48544  0
> snd_mixer_oss          17664  2 snd_pcm_oss
> snd_emu10k1           117412  1
> snd_rawmidi            21408  1 snd_emu10k1
> snd_seq_device          7948  2 snd_emu10k1,snd_rawmidi
> snd_ac97_codec         91936  1 snd_emu10k1
> snd_pcm                81412  3 snd_pcm_oss,snd_emu10k1,snd_ac97_codec
> snd_timer              22148  2 snd_emu10k1,snd_pcm
> snd_ac97_bus            2816  1 snd_ac97_codec
> snd_page_alloc          9352  2 snd_emu10k1,snd_pcm
> snd_util_mem            4352  1 snd_emu10k1
> snd_hwdep               7968  1 snd_emu10k1
> snd                    49124  9
> snd_pcm_oss,snd_mixer_oss,snd_emu10k1,snd_rawmidi,snd_seq_device,snd_ac97_codec,snd_pcm,snd_timer,snd_hwdep
>
> Proc Config -----------------------------------------------
> CONFIG_SOUND=m
> # CONFIG_SND is not set
> # CONFIG_SOUND_PRIME is not set
>
> Modprobe Conf ---------------------------------------------
> alias snd-card-0 snd-emu10k1
> alias sound-slot-0 snd-emu10k1
>
> Proc Asound -----------------------------------------------
> Advanced Linux Sound Architecture Driver Version 1.0.10.
> Compiled on Nov 18 2005 for kernel 2.6.14.2 (SMP).
> 0 [Live           ]: EMU10K1 - SB Live [Unknown]
>                      SB Live [Unknown] (rev.10, serial:0x80661102) at
> 0xdda0, irq 21
>   4: [0- 0]: hardware dependent
>   8: [0- 0]: raw midi
>  19: [0- 3]: digital audio playback
>  18: [0- 2]: digital audio playback
>  26: [0- 2]: digital audio capture
>  25: [0- 1]: digital audio capture
>  16: [0- 0]: digital audio playback
>  24: [0- 0]: digital audio capture
>   0: [0- 0]: ctl
>  33:       : timer
> 00-00: EMU10K1 (FX8010)
> 00-00: emu10k1 : ADC Capture/Standard PCM Playback : playback 32 : capture
> 1
> 00-01: emu10k1 mic : Mic Capture : capture 1
> 00-02: emu10k1 efx : Multichannel Capture/PT Playback : playback 8 :
> capture 1
> 00-03: emu10k1 : Multichannel Playback : playback 1
> cat: /proc/asound/seq/clients: No such file or directory
>
> Dev Snd ---------------------------------------------------
> controlC0  midiC0D0  pcmC0D0p  pcmC0D2c  pcmC0D3p
> hwC0D0     pcmC0D0c  pcmC0D1c  pcmC0D2p  timer
>
> CPU -------------------------------------------------------
> model name      : Intel(R) Pentium(R) 4 CPU 3.00GHz
> cpu MHz         : 2992.835
> model name      : Intel(R) Pentium(R) 4 CPU 3.00GHz
> cpu MHz         : 2992.835
>
> RAM -------------------------------------------------------
> MemTotal:       514840 kB
> SwapTotal:     1020116 kB
>
> Hardware --------------------------------------------------
> 00:00.0 Host bridge: Intel Corporation 82875P/E7210 Memory Controller Hub
> (rev 02)
> 02:02.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev
> 0a)
>
>
>
> Now, I still have sound... Somewhat.... It comes out the back two speakers
> but not the front two. I can use the gnome sound control to atleast get it
> to where I can hear something... I just can't open alsamixer and tweak it
> out...
> From the Troubleshooting list:
>
>
> 1.) I am using alsa-driver and not the built-in kernel modules
>
> 2.) [root@jaguar ~/Desktop] cat /proc/asound/version
> Advanced Linux Sound Architecture Driver Version 1.0.10.
> Compiled on Nov 18 2005 for kernel 2.6.14.2 (SMP).
>
> 3.) [root@jaguar ~/Desktop] grep VERSION_STR /usr/include/alsa/version.h
> #define SND_LIB_VERSION_STR     "1.0.10"
>
> 4.) [root@jaguar ~/Desktop] cat /proc/asound/cards
> 0 [Live           ]: EMU10K1 - SB Live [Unknown]
>                      SB Live [Unknown] (rev.10, serial:0x80661102) at
> 0xdda0, irq 21
>
>       [root@jaguar ~/Desktop] lspci | egrep audio
> 02:02.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev
> 0a)
>
>
> 5.) [root@jaguar ~/Desktop] alsamixer
> ALSA lib simple_none.c:1216:(simple_add1) helem (MIXER,'Front Playback
> Volume',0,0,0) appears twice or more
>
> alsamixer: function snd_mixer_load failed: Invalid argument
>
> 6.) I hate to admit it, but I ussually only run as root. From step 6 and
> beyond, it seems pretty trivial to do.
>
>
>
> Let me know if there is anything else I can provide and thank you James
> for your help. I really do apprecieate it...
>
>

Well, I did some more testing and here's what I came up with. I rolled back
to 2.6.13.4, deleted /etc/asound.state, reran alsoconf and I have no
problems now, with alsa-{lib,utils,oss,driver} 1.0.{9 ,10}.. Using
2.6.14.xwith alsa-{lib,utils,oss,driver}
1.0.{9 ,10} it gives me the same error with simple_none.c when I run
alsamixer. If that's not a problem with the kernel then I don't what is...

I don't get it. Looks like I'll be sticking with 2.6.13.4 for the time
being... Hopefully someone here is still investigating the matter because
I'm not the only one it's happening to. Granted, most similar errors I've
found on google have to do with simple.c and not simple_none.c.... I'm sure
if I new C a little bit better I could find the offending line and fix it
myself before I compile alsa-lib... Maybe... I don't know...

I'll still check back here from time to time in anticipation... :-) Thanks
again for your help James.

[-- Attachment #2: Type: text/html, Size: 11015 bytes --]

Re: kernel 2.6.14.x and alsamixer problems

[Lee Revell]

On Fri, 2005-11-25 at 17:09 -0500, Jon Grosshart wrote:

Try this patch:

--- /home/rlrevell/cvs/alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c~     2005-11-05 16:25:13.000000000 -0500
+++ /home/rlrevell/cvs/alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c      2005-11-25 15:28:47.000000000 -0500
@@ -752,9 +752,16 @@
         .emu10k1_chip = 1,
         .ac97_chip = 1,
         .sblive51 = 1} ,
+       /* Tested by Alexandr 25th Nov 2005 */
+       {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80661102,
+        .driver = "EMU10K1", .name = "SB Live 5.1 [SB0220]", 
+        .id = "Live",
+        .emu10k1_chip = 1,
+        .ac97_chip = 1,
+        .sblive51 = 1} ,
        /* Tested by Thomas Zehetbauer 27th Aug 2005 */
        {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80651102,
-        .driver = "EMU10K1", .name = "SB Live 5.1 [SB0220]", 
+        .driver = "EMU10K1", .name = "SB Live 5.1 [SB0222]", 
         .id = "Live",
         .emu10k1_chip = 1,
         .ac97_chip = 1,





-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

Re: kernel 2.6.14.x and alsamixer problems

[Jon Grosshart]

[-- Attachment #1: Type: text/plain, Size: 1823 bytes --]

On 11/25/05, Lee Revell <rlrevell@joe-job.com> wrote:
>
> On Fri, 2005-11-25 at 17:09 -0500, Jon Grosshart wrote:
>
> Try this patch:
>
> --- /home/rlrevell/cvs/alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c~
> 2005-11-05 16:25:13.000000000 -0500
> +++
> /home/rlrevell/cvs/alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c      2005-11-25
> 15:28:47.000000000 -0500
> @@ -752,9 +752,16 @@
>          .emu10k1_chip = 1,
>          .ac97_chip = 1,
>          .sblive51 = 1} ,
> +       /* Tested by Alexandr 25th Nov 2005 */
> +       {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80661102,
> +        .driver = "EMU10K1", .name = "SB Live 5.1 [SB0220]",
> +        .id = "Live",
> +        .emu10k1_chip = 1,
> +        .ac97_chip = 1,
> +        .sblive51 = 1} ,
>         /* Tested by Thomas Zehetbauer 27th Aug 2005 */
>         {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80651102,
> -        .driver = "EMU10K1", .name = "SB Live 5.1 [SB0220]",
> +        .driver = "EMU10K1", .name = "SB Live 5.1 [SB0222]",
>          .id = "Live",
>          .emu10k1_chip = 1,
>          .ac97_chip = 1,
>
>
>
>
Well, I tried that just for grins but no joy. I even compiled ALL alsa
packages against the modified C file just incase lib and utils used it.. It
doesn't seem (to me) that this is a driver problem or a problem with my card
not being identified correctly. As near as I can tell, that just adds SB0222
to the index list of cards and possibly corrects a subsystem ID for SB0220.
Thanks tho. I appreciate any effort given. I still get that error when
running alsamixer tho.

Now, I haven't tried using the kernel modules yet. I don't see how that will
do anything as alsa-driver uses the same kernel source to build it's
modules... :-) Any further thought is most welcome.

[-- Attachment #2: Type: text/html, Size: 2903 bytes --]

Re: kernel 2.6.14.x and alsamixer problems

[Jon Grosshart]

[-- Attachment #1: Type: text/plain, Size: 3304 bytes --]

On 11/26/05, Jon Grosshart <jgrosshart@gmail.com> wrote:
>
>
> On 11/25/05, Lee Revell <rlrevell@joe-job.com> wrote:
> >
> > On Fri, 2005-11-25 at 17:09 -0500, Jon Grosshart wrote:
> >
> > Try this patch:
> >
> > --- /home/rlrevell/cvs/alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c~
> > 2005-11-05 16:25:13.000000000 -0500
> > +++
> > /home/rlrevell/cvs/alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c      2005-11-25
> > 15:28: 47.000000000 -0500
> > @@ -752,9 +752,16 @@
> >          .emu10k1_chip = 1,
> >          .ac97_chip = 1,
> >          .sblive51 = 1} ,
> > +       /* Tested by Alexandr 25th Nov 2005 */
> > +       {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80661102,
> > +        .driver = "EMU10K1", .name = "SB Live 5.1 [SB0220]",
> > +        .id = "Live",
> > +        .emu10k1_chip = 1,
> > +        .ac97_chip = 1,
> > +        .sblive51 = 1} ,
> >         /* Tested by Thomas Zehetbauer 27th Aug 2005 */
> >         {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80651102,
> > -        .driver = "EMU10K1", .name = "SB Live 5.1 [SB0220]",
> > +        .driver = "EMU10K1", .name = "SB Live 5.1 [SB0222]",
> >          .id = "Live",
> >          .emu10k1_chip = 1,
> >          .ac97_chip = 1,
> >
> >
> >
> >
> Well, I tried that just for grins but no joy. I even compiled ALL alsa
> packages against the modified C file just incase lib and utils used it.. It
> doesn't seem (to me) that this is a driver problem or a problem with my card
> not being identified correctly. As near as I can tell, that just adds SB0222
> to the index list of cards and possibly corrects a subsystem ID for SB0220.
> Thanks tho. I appreciate any effort given. I still get that error when
> running alsamixer tho.
>
> Now, I haven't tried using the kernel modules yet. I don't see how that
> will do anything as alsa-driver uses the same kernel source to build it's
> modules... :-) Any further thought is most welcome.
>


I did sit down and mess around with simple_none.c in alsa-lib and I got
everything to work. I can see your approach Lee with regards to the
subdevice. It does seem like it may be complaining about not finding the
subdevice ID.. However, this is what I did....

--- alsa-lib-1.0.10/src/mixer/simple_none.c.orig    2005-08-24 06:41:
16.000000000 -0400
+++ alsa-lib-1.0.10/src/mixer/simple_none.c    2005-11-26
14:58:10.000000000-0500
@@ -1214,8 +1214,7 @@
                 snd_hctl_elem_get_index(helem),
                 snd_hctl_elem_get_device(helem),
                 snd_hctl_elem_get_subdevice(helem));
-        err = -EINVAL;
-        goto __error;
+        return 0;
     }
     simple->ctls[type].elem = helem;
     simple->ctls[type].type = snd_ctl_elem_info_get_type(info);

I really hate to do that, but this is the main reason why I switched to *nix
long ago.... If there's a problem, there's always a solution... All 6
speakers work and sound great now. I still get the error ofcourse but
atleast alsamixer doesn't crap out now. I suppose I could move up a few
lines and eliminate the SNDERR echo.... I'll leave it so it reminds me I'm
still running a hack.

And... I still hope to see a fix from within the kernel someday if that is
truely where the problem lies. Thanks again...

[-- Attachment #2: Type: text/html, Size: 5154 bytes --]

Re: kernel 2.6.14.x and alsamixer problems

[Jon Grosshart]

[-- Attachment #1: Type: text/plain, Size: 4394 bytes --]

On 11/26/05, Jon Grosshart <jgrosshart@gmail.com> wrote:
>
>
>
> On 11/26/05, Jon Grosshart <jgrosshart@gmail.com> wrote:
> >
> >
> > On 11/25/05, Lee Revell < rlrevell@joe-job.com> wrote:
> > >
> > > On Fri, 2005-11-25 at 17:09 -0500, Jon Grosshart wrote:
> > >
> > > Try this patch:
> > >
> > > ---
> > > /home/rlrevell/cvs/alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c~
> > > 2005-11-05 16:25:13.000000000 -0500
> > > +++
> > > /home/rlrevell/cvs/alsa/alsa-kernel/pci/emu10k1/emu10k1_main.c      2005-11-25
> > > 15:28: 47.000000000 -0500
> > > @@ -752,9 +752,16 @@
> > >          .emu10k1_chip = 1,
> > >          .ac97_chip = 1,
> > >          .sblive51 = 1} ,
> > > +       /* Tested by Alexandr 25th Nov 2005 */
> > > +       {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80661102,
> > > +        .driver = "EMU10K1", .name = "SB Live 5.1 [SB0220]",
> > > +        .id = "Live",
> > > +        .emu10k1_chip = 1,
> > > +        .ac97_chip = 1,
> > > +        .sblive51 = 1} ,
> > >         /* Tested by Thomas Zehetbauer 27th Aug 2005 */
> > >         {.vendor = 0x1102, .device = 0x0002, .subsystem = 0x80651102,
> > > -        .driver = "EMU10K1", .name = "SB Live 5.1 [SB0220]",
> > > +        .driver = "EMU10K1", .name = "SB Live 5.1 [SB0222]",
> > >          .id = "Live",
> > >          .emu10k1_chip = 1,
> > >          .ac97_chip = 1,
> > >
> > >
> > >
> > >
> > Well, I tried that just for grins but no joy. I even compiled ALL alsa
> > packages against the modified C file just incase lib and utils used it.. It
> > doesn't seem (to me) that this is a driver problem or a problem with my card
> > not being identified correctly. As near as I can tell, that just adds SB0222
> > to the index list of cards and possibly corrects a subsystem ID for SB0220.
> > Thanks tho. I appreciate any effort given. I still get that error when
> > running alsamixer tho.
> >
> > Now, I haven't tried using the kernel modules yet. I don't see how that
> > will do anything as alsa-driver uses the same kernel source to build it's
> > modules... :-) Any further thought is most welcome.
> >
>
>
> I did sit down and mess around with simple_none.c in alsa-lib and I got
> everything to work. I can see your approach Lee with regards to the
> subdevice. It does seem like it may be complaining about not finding the
> subdevice ID.. However, this is what I did....
>
> --- alsa-lib-1.0.10/src/mixer/simple_none.c.orig    2005-08-24 06:41:
> 16.000000000 -0400
> +++ alsa-lib-1.0.10/src/mixer/simple_none.c    2005-11-26 14:58:
> 10.000000000 -0500
> @@ -1214,8 +1214,7 @@
>                  snd_hctl_elem_get_index(helem),
>                  snd_hctl_elem_get_device(helem),
>                  snd_hctl_elem_get_subdevice(helem));
> -        err = -EINVAL;
> -        goto __error;
> +        return 0;
>      }
>      simple->ctls[type].elem = helem;
>      simple->ctls[type].type = snd_ctl_elem_info_get_type(info);
>
> I really hate to do that, but this is the main reason why I switched to
> *nix long ago.... If there's a problem, there's always a solution... All 6
> speakers work and sound great now. I still get the error ofcourse but
> atleast alsamixer doesn't crap out now. I suppose I could move up a few
> lines and eliminate the SNDERR echo.... I'll leave it so it reminds me I'm
> still running a hack.
>
> And... I still hope to see a fix from within the kernel someday if that is
> truely where the problem lies. Thanks again...
>


O.k... Sorry if this is getting spammy now... I've been diging around in the
kernel for awhile and I see what you were getting at with the patch Lee....
I had the same idea awhile ago until I realized it was the same exact thing
you suggested. You just used my subdevice ID and made a new section. If you
grep for 80661102 in 2.6.13.4 it doesn't even show up however... So, my card
must have been identifying itself as something else... Or something...

I have some serious screenburn at the moment. Please forgive. I ran a diff
between the 2.6.14 and 2.6.13.4 emu10k1_main.c files... I tried
incrementally reverting back to a 2.6.13.4 state to no avail.... I even went
so far as to roll back the entire emu10k1 folder... Same alsamixer error....
I'm lost it would seem.

I guess I'll just stick with my lame alsa-lib hack for now.... :-)

[-- Attachment #2: Type: text/html, Size: 6561 bytes --]