Re: Audigy4 support

[wwp <subscript@free.fr>]

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

Hello Takashi,


On Fri, 24 Feb 2006 20:02:22 +0100 Takashi Iwai <tiwai@suse.de> wrote:

> At Fri, 24 Feb 2006 19:58:35 +0100,
> wwp wrote:
> > 
> > Hello Takashi,
> > 
> > 
> > On Fri, 24 Feb 2006 19:25:54 +0100 Takashi Iwai <tiwai@suse.de> wrote:
> > 
> > > At Wed, 22 Feb 2006 19:40:29 +0100,
> > > wwp wrote:
> > > > 
> > > > [1  <multipart/mixed (7bit)>]
> > > > [1.1  <text/plain; US-ASCII (quoted-printable)>]
> > > > Hello all,
> > > > 
> > > > 
> > > > I've got a brand new Audigy4 PCI sound-card, running on Debian
> > > > unstable (kernel 2.6.15, feat. Alsa 1.0.10+1.0.11-rc2-2).
> > > > 
> > > > I'm able to get PCM out but can't get line-in to work: the alsa mixer
> > > > allows un-muting line-in but I can't get the input selector in
> > > > audacity for instance.
> > > > 
> > > > 
> > > > The exact model is a Creative SoundBlaster Audigy 4 retail (purchase
> > > > date: 20060219, UK) w/ remote controler RM-1500.
> > > > 
> > > > 0000:00:0a.0 0401: 1102:0008
> > > > Here was lspci says:
> > > > 
> > > > 0000:00:0a.0 Multimedia audio controller: Creative Labs SB0400 Audigy2
> > > > Value Subsystem: Creative Labs: Unknown device 1021
> > > > 		 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV-
> > > > VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF-
> > > > FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR-
> > > > <PERR- Latency: 32 (500ns min, 5000ns max) Interrupt: pin A routed to
> > > > IRQ 12 Region 0: I/O ports at d400 [size=64]
> > > > 		 Capabilities: [dc] 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-
> > > > 
> > > > 
> > > > I've found that the emu10k1 sources (checked at 1.0.11-rc3) don't
> > > > include the card IDs, would the attached patch do it? Would that one
> > > > be enough to get proper line-in support?
> > > 
> > > Are you sue that the patch really works for you?
> > > 1102:2008 are _not_ subsystem IDs but the normal PCI IDs.
> > > 
> > > The subsystem number in the emu10k1's chip table is what you get as
> > > the serial number in /proc/asound/cards (perhaps 0x10211102).
> > 
> > Well, I never said that the patch worked neither that I've applied it :-).
> > No, I just wrote it as I assumed, wrongly, that it was a possible
> > solution to submit before I set up a customized kernel configuration from
> > the sources. Sorry for this confusion.
> > 
> > Here's what `cat /proc/asound/cards` shows:
> > 
> > 0 [Audigy2        ]: Audigy2 - Audigy 2 Value [Unknown]
> >                      Audigy 2 Value [Unknown] (rev.0, serial:0x10211102)
> > at 0xd400, irq 12 1 [UART           ]: MPU-401 UART - MPU-401 UART
> >                      MPU-401 UART at 0x330, irq 5
> > 
> > 
> > Now.. what to do? Should I provide more information? What to expect?
> 
> Try subsystem=0x10211102 module option with snd-emu10k1.
> It assumes that the subsystem is the given model.
> 
> If that works, please create a write patch with correct parameters :)
>    .vendor = 0x1102, .device = 0x0008, .subsystem = 0x20121102
>    ...
> and check whether the driver works without extra module option.

Ouch! Seems that my cable was the culprit, line-in works now w/ a new cable
(wtf??). I'm really sorry for the noise. Anyway I'm still interested in
making Alsa recognizing this card.. what's next step, do you have all the
necessary information now?


Regards,

-- 
wwp

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]