public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Alnie <alnieb@yahoo.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Issues w/ Creative Labs [SB X-Fi	Xtreme	Audio]	CA0110-IBG
Date: Tue, 24 Feb 2015 23:32:53 -0800	[thread overview]
Message-ID: <54ED7AA5.1080806@yahoo.com> (raw)
In-Reply-To: <s5hr3te5v33.wl-tiwai@suse.de>

On 02/24/2015 11:06 PM, Takashi Iwai wrote:
> At Tue, 24 Feb 2015 22:51:41 -0800,
> Alnie wrote:
>>
>>
>>
>> On 02/24/2015 10:28 PM, Takashi Iwai wrote:
>>> [Please don't top-post]
>>>
>>> At Wed, 25 Feb 2015 04:37:18 +0000 (UTC),
>>> Alnie wrote:
>>>>
>>>> I've just submitted this...
>>>> http://www.alsa-project.org/db/?f=b49e28f0fdd3120b3c222b4ff377c3e290baf497
>>>>
>>>> Although, I do agree the problem seems deeper than the driver. Could be something unique to my laptop/hardware. Although, as I've mentioned, the card has been working fine in Win 7. I double checked my BIOS and it's at latest version. Based on what I've seen, I feel a bit hopeless trying to reach out to Creative Labs about this. Do you think that would be a worthwhile endeavor?
>>>
>>> What kind of card is it, BTW?  When looking at your original post, I
>>> noticed that the card provides its own PCI bridge and there is no
>>> kernel driver binding to it.
>>>
>>>    05:00.0 PCI bridge: Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG PCI to PCIe Bridge (prog-if 00 [Normal decode])
>>>          Physical Slot: 3
>>>          Flags: bus master, fast devsel, latency 0
>>>          Bus: primary=05, secondary=06, subordinate=0c, sec-latency=36
>>>          Memory behind bridge: f4300000-f43fffff
>>>          Capabilities: [50] Power Management version 3
>>>          Capabilities: [60] MSI: Enable- Count=1/16 Maskable- 64bit+
>>>          Capabilities: [80] Subsystem: Creative Labs Device 0040
>>>          Capabilities: [90] Express PCI-Express to PCI/PCI-X Bridge, MSI 00
>>>          Capabilities: [100] Advanced Error Reporting
>>>
>>>    06:00.0 Audio device: Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG
>>>          Subsystem: Creative Labs SB1040
>>>          Flags: bus master, fast Back2Back, medium devsel, latency 32, IRQ 19
>>>          Memory at f4300000 (32-bit, non-prefetchable) [size=16K]
>>>          Capabilities: [dc] Power Management version 3
>>>          Kernel driver in use: snd_hda_intel
>>>
>>>
>>> Takashi
>>> _______________________________________________
>>> Alsa-devel mailing list
>>> Alsa-devel@alsa-project.org
>>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>>
>>
>> it's an expresscard 54 audio card. more details...
>> http://www.notebookreview.com/notebookreview/creative-soundblaster-x-fi-xtreme-audio-for-notebook-review/
>
> OK.  Could you show the lspci -nv output, too?  Usually some pcie
> hotplug driver (either pcieport, shpchp, acpiphp, etc) should be bound
> to a PCI bridge device.  Check the kernel message.  You might see
> something related there...
>
>
> Takashi
>

00:1b.0 0403: 8086:293e (rev 03)
	Subsystem: 17aa:20f2
	Flags: bus master, fast devsel, latency 0, IRQ 17
	Memory at fc420000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
	Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [100] Virtual Channel
	Capabilities: [130] Root Complex Link
	Kernel driver in use: snd_hda_intel

00:1c.0 0604: 8086:2940 (rev 03) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 00008000-00008fff
	Memory behind bridge: c0000000-c01fffff
	Prefetchable memory behind bridge: 00000000c0200000-00000000c03fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: 17aa:20f3
	Capabilities: [a0] Power Management version 2
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Root Complex Link
	Kernel driver in use: pcieport

00:1c.3 0604: 8086:2946 (rev 03) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=05, subordinate=0c, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: f4300000-f7efffff
	Prefetchable memory behind bridge: 00000000f4000000-00000000f40fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: 17aa:20f3
	Capabilities: [a0] Power Management version 2
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Root Complex Link
	Kernel driver in use: pcieport

00:1c.4 0604: 8086:2948 (rev 03) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=0d, subordinate=14, sec-latency=0
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: fa000000-fbffffff
	Prefetchable memory behind bridge: 00000000f4100000-00000000f41fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: 17aa:20f3
	Capabilities: [a0] Power Management version 2
	Capabilities: [100] Virtual Channel
	Capabilities: [180] Root Complex Link
	Kernel driver in use: pcieport


[    0.476508] pcieport 0000:00:1c.0: irq 24 for MSI/MSI-X
[    0.476709] pcieport 0000:00:1c.3: irq 25 for MSI/MSI-X
[    0.476901] pcieport 0000:00:1c.4: irq 26 for MSI/MSI-X
[    0.477063] pcieport 0000:00:1c.0: Signaling PME through PCIe PME 
interrupt
[    0.477140] pcieport 0000:00:1c.3: Signaling PME through PCIe PME 
interrupt
[    0.477316] pcieport 0000:00:1c.4: Signaling PME through PCIe PME 
interrupt

  reply	other threads:[~2015-02-25  7:32 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <54E10F0C.7070802@yahoo.com>
2015-02-15 21:33 ` Issues w/ Creative Labs [SB X-Fi Xtreme Audio] CA0110-IBG Alnie
2015-02-16 16:05   ` Takashi Iwai
2015-02-16 19:03     ` Alnie
2015-02-16 19:52       ` Takashi Iwai
2015-02-22 20:47         ` Alnie
2015-02-22 20:55           ` Alnie
2015-02-24 15:37             ` Takashi Iwai
2015-02-24 18:14               ` Alnie
2015-02-24 19:52                 ` Takashi Iwai
2015-02-24 20:10                   ` Alnie
2015-02-24 20:39                     ` Takashi Iwai
2015-02-24 21:30                       ` Alnie
2015-02-25  4:37                         ` Alnie
2015-02-25  6:28                           ` Takashi Iwai
2015-02-25  6:51                             ` Alnie
2015-02-25  7:06                               ` Takashi Iwai
2015-02-25  7:32                                 ` Alnie [this message]
2015-02-25  7:48                                   ` Takashi Iwai
2015-02-25  8:01                                     ` Alnie
     [not found]                                     ` <54ED7FED.9080600@yahoo.com>
2015-02-25  8:06                                       ` Takashi Iwai
2015-02-25  8:21                                         ` Alnie
2015-02-25  8:23                                           ` Takashi Iwai
2015-02-25  8:30                                             ` Alnie
2015-03-03  3:37 Alnie
2015-03-03  6:10 ` Takashi Iwai
2015-03-03  7:22   ` Alnie
2015-03-03  7:48     ` Takashi Iwai
2015-03-03  9:21       ` Alnie
2015-03-03 21:51         ` Alnie
2015-03-03 21:58           ` Alnie
2015-03-03 22:07           ` Takashi Iwai
2015-03-04  2:12             ` Alnie
2015-03-04  8:00               ` Takashi Iwai
2015-03-04  9:01                 ` Alnie
2015-03-04  9:35                   ` Takashi Iwai
2015-03-06 22:38                     ` Alnie
2015-03-06 22:50                       ` Alnie
2015-03-06 23:31                     ` Alnie
2015-03-07  7:56                       ` Takashi Iwai
2015-03-07 16:28                         ` Alnie
2015-03-07 16:32                           ` Takashi Iwai
2015-03-07 18:06                             ` Alnie
2015-03-09 15:22                               ` Alnie
2015-03-09 16:00                                 ` Takashi Iwai
2015-03-12  3:59                                   ` Alnie
2015-03-12  6:19                                     ` Takashi Iwai
2015-03-13  2:41                                       ` Alnie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54ED7AA5.1080806@yahoo.com \
    --to=alnieb@yahoo.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox