sb live (emu10k1) stops working between 2.6.23.1 and 2.6.23.7 - Kernel

This is a discussion on sb live (emu10k1) stops working between 2.6.23.1 and 2.6.23.7 - Kernel ; Hello, I have an SB Live Value card which uses the emu10k1 driver. I use digital output to an external amplifier. This has worked fine for many years, up to and including kernel 2.6.23.1. Under 2.6.23.7, I have been unable ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: sb live (emu10k1) stops working between 2.6.23.1 and 2.6.23.7

  1. sb live (emu10k1) stops working between 2.6.23.1 and 2.6.23.7


    Hello,

    I have an SB Live Value card which uses the emu10k1 driver. I use digital
    output to an external amplifier. This has worked fine for many years, up
    to and including kernel 2.6.23.1. Under 2.6.23.7, I have been unable
    to get any audio output. I get the following errors when loading my
    asound.state under 2.6.23.7 using `alsactl restore`:
    alsactl: set_control:991: warning: name mismatch (IEC958 Playback
    Mask/IEC958 Playback Default) for control #222
    alsactl: set_control:993: warning: index mismatch (3/0) for control #222
    alsactl: set_control:993: warning: index mismatch (0/1) for control #223
    alsactl: set_control:993: warning: index mismatch (1/2) for control #224
    alsactl: set_control:985: warning: iface mismatch (3/2) for control #225
    alsactl: set_control:987: warning: device mismatch (2/0) for control #225
    alsactl: set_control:989: warning: subdevice mismatch (0/0) for control
    #225
    alsactl: set_control:991: warning: name mismatch (IEC958 Playback
    Default/SB Live Analog/Digital Output Jack) for control #225
    alsactl: set_control:993: warning: index mismatch (2/0) for control #225
    alsactl: set_control:995: failed to obtain info for control #225
    (Operation not permitted)

    I receive no errors when I load my asound.state under 2.6.23.1.

    Under 2.6.23.7, I get the message "No digital data" on my external
    amplifier, which normally I only see when the computer is powered down or
    rebooting. I do not get that message under 2.6.23.1, even when no audio
    is being played.

    I've tried copying down my alsamixer settings under 2.6.23.1, and
    re-entering them under 2.6.23.7, however I have still been unable to get
    any audio output.

    Here is the relevant part of my `lspci -v`:
    05:0d.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev
    08)
    Subsystem: Creative Labs CT4780 SBLive! Value
    Flags: bus master, medium devsel, latency 64, IRQ 23
    I/O ports at dce0 [size=32]
    Capabilities: [dc] Power Management version 2

    Please let me know if you need any more information, and please CC my
    e-mail address on any correspondence, since I am not subscribed to this
    list.

    thanks,
    Jim Faulkner

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  2. Re: sb live (emu10k1) stops working between 2.6.23.1 and 2.6.23.7


    I've done some more testing this morning, and it appears that the "ALSA:
    emu10k1 - Fix memory corruption" patch from 2.6.23.6 has broken digital
    output on my SB Live Value card. Simply replacing the 2.6.23.7 emumixer.c
    with the version included in 2.6.23.1 I was able to get digital output
    working again under 2.6.23.7.

    This does not appear to be a simple matter of adjusting the alsa mixer to
    compsensate for how the mixer controls are exposed to userspace. I have
    duplicated all alsamixer settings between 2.6.23.1 and stock 2.6.23.7 in
    the "F5" view all controls mode, but still received no audio output. I
    also tried adjusting other volume controls which normally do not need
    adjusting, but got nowhere. It appears that the 2.6.23.6 emu10k1 patch
    broke digital output entirely on this card.

    Just to add to the information in my first message, the SB Live card is
    connected from the yellow jack on the card to the "Digital Coax Input"
    connector on my external amplifier.

    thanks,
    Jim Faulkner


    On Fri, 16 Nov 2007, Jim Faulkner wrote:

    >
    > Hello,
    >
    > I have an SB Live Value card which uses the emu10k1 driver. I use digital
    > output to an external amplifier. This has worked fine for many years, up
    > to and including kernel 2.6.23.1. Under 2.6.23.7, I have been unable
    > to get any audio output. I get the following errors when loading my
    > asound.state under 2.6.23.7 using `alsactl restore`:
    > alsactl: set_control:991: warning: name mismatch (IEC958 Playback
    > Mask/IEC958 Playback Default) for control #222
    > alsactl: set_control:993: warning: index mismatch (3/0) for control #222
    > alsactl: set_control:993: warning: index mismatch (0/1) for control #223
    > alsactl: set_control:993: warning: index mismatch (1/2) for control #224
    > alsactl: set_control:985: warning: iface mismatch (3/2) for control #225
    > alsactl: set_control:987: warning: device mismatch (2/0) for control #225
    > alsactl: set_control:989: warning: subdevice mismatch (0/0) for control
    > #225
    > alsactl: set_control:991: warning: name mismatch (IEC958 Playback
    > Default/SB Live Analog/Digital Output Jack) for control #225
    > alsactl: set_control:993: warning: index mismatch (2/0) for control #225
    > alsactl: set_control:995: failed to obtain info for control #225
    > (Operation not permitted)
    >
    > I receive no errors when I load my asound.state under 2.6.23.1.
    >
    > Under 2.6.23.7, I get the message "No digital data" on my external
    > amplifier, which normally I only see when the computer is powered down or
    > rebooting. I do not get that message under 2.6.23.1, even when no audio
    > is being played.
    >
    > I've tried copying down my alsamixer settings under 2.6.23.1, and
    > re-entering them under 2.6.23.7, however I have still been unable to get
    > any audio output.
    >
    > Here is the relevant part of my `lspci -v`:
    > 05:0d.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev
    > 08)
    > Subsystem: Creative Labs CT4780 SBLive! Value
    > Flags: bus master, medium devsel, latency 64, IRQ 23
    > I/O ports at dce0 [size=32]
    > Capabilities: [dc] Power Management version 2
    >
    > Please let me know if you need any more information, and please CC my
    > e-mail address on any correspondence, since I am not subscribed to this
    > list.
    >
    > thanks,
    > Jim Faulkner
    >
    >

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  3. Re: sb live (emu10k1) stops working between 2.6.23.1 and 2.6.23.7

    At Sat, 17 Nov 2007 12:18:29 -0500 (EST),
    Jim Faulkner wrote:
    >
    >
    > I've done some more testing this morning, and it appears that the "ALSA:
    > emu10k1 - Fix memory corruption" patch from 2.6.23.6 has broken digital
    > output on my SB Live Value card. Simply replacing the 2.6.23.7 emumixer.c
    > with the version included in 2.6.23.1 I was able to get digital output
    > working again under 2.6.23.7.
    >
    > This does not appear to be a simple matter of adjusting the alsa mixer to
    > compsensate for how the mixer controls are exposed to userspace. I have
    > duplicated all alsamixer settings between 2.6.23.1 and stock 2.6.23.7 in
    > the "F5" view all controls mode, but still received no audio output. I
    > also tried adjusting other volume controls which normally do not need
    > adjusting, but got nowhere. It appears that the 2.6.23.6 emu10k1 patch
    > broke digital output entirely on this card.
    >
    > Just to add to the information in my first message, the SB Live card is
    > connected from the yellow jack on the card to the "Digital Coax Input"
    > connector on my external amplifier.


    It's no regression of the driver. The problem is just a wrong use of
    alsactl in your init script. It should use -F option to ignore
    unmatching elements, which is caused when a mixer element is removed
    or renamed.

    This problem doesn't happen so often (as we try to keep the
    compatibility as much as possible), so I didn't realize some distros
    still doing wrong for years.

    Anyway, this won't be a problem in future since I changed the default
    behavior of alsactl to with -F.


    Takashi
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

+ Reply to Thread