Skip to contentSkip to conversation

0x10b9:0x5461 not supported?

DISCUSSION Dirk 3 participants 11 messages Jul 20, 2005 – Jul 21, 2005

lore
Share & tools
lore
#1 lore raw
Quoted 3 lines · Dirk

http://pciids.sourceforge.net/iii/?i=10b95461

Doesn't work with snd_hda_intel or anything else I tried...

We don't have any documentation for this chip.

The CVS version of this driver assumes that this chip is compatible with the Intel HDA controller; please test it.

HTH
Clemens

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

author
#2 lore raw
Quoted 5 lines · Clemens Ladisch
Quoted 2 lines · Dirk

http://pciids.sourceforge.net/iii/?i=10b95461

Quoted 10 lines
Quoted 3 lines

Doesn't work with snd_hda_intel or anything else I tried...

We don't have any documentation for this chip.

The CVS version of this driver assumes that this chip is compatible with the Intel HDA controller; please test it.

That's exactly what I tried. I also tried the hacked alsa-driver from the download pages of Realtek and the Mainboard manufacturer. But nothing worked. The driver loads fine but there is no mixer and no sound.

The mainboard description
(http://www.asus.com/prog/spec.asp?m=P5RD1-V&langs=01) says it's a Realtek ALC 861... but "lspci -n" identifies (0x10b9) ALi and not RealTek... :-/

ALi's site doesn't list this card or chip (I looked for "5461" and "M5461") at all. So I guess the mainboard description is right and lspci is "wrong"... Dunno..

Dirk

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

#3 lore raw

Hi,

Did you try to add this pci id in pci_device_id azx_ids table in file hda_intel.c ?

Peter Zubaj

Quoted 35 lines · Dirk
Quoted 5 lines · Clemens Ladisch
Quoted 2 lines · Dirk

http://pciids.sourceforge.net/iii/?i=10b95461

Quoted 10 lines
Quoted 3 lines

Doesn't work with snd_hda_intel or anything else I tried...

We don't have any documentation for this chip.

The CVS version of this driver assumes that this chip is compatible with the Intel HDA controller; please test it.

That's exactly what I tried. I also tried the hacked alsa-driver from the download pages of Realtek and the Mainboard manufacturer. But nothing worked. The driver loads fine but there is no mixer and no sound.

The mainboard description
(http://www.asus.com/prog/spec.asp?m=P5RD1-V&langs=01) says it's a Realtek ALC 861... but "lspci -n" identifies (0x10b9) ALi and not RealTek... :-/

ALi's site doesn't list this card or chip (I looked for "5461" and "M5461") at all. So I guess the mainboard description is right and lspci is "wrong"... Dunno..

Dirk

Quoted 10 lines

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

author
#4 lore raw

Hey!
I tried that right now (Kernel 2.6.12.3).

sound/pci/hda/hda_intel.c

/* PCI IDs */

static struct pci_device_id azx_ids[] = {
        { 0x8086, 0x2668, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 }, /* ICH6 */
        { 0x8086, 0x27d8, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 }, /* ICH7 */
        { 0x8086, 0x269a, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 }, /* ESB2 */
        { 0x10b9, 0x5461, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 }, /* test */
        { 0, }
};

and after reloading the module it says

ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout [...]

and it doesn't look like it will stop anytime soon...

Dirk

Quoted 66 lines

Hi,

Did you try to add this pci id in pci_device_id azx_ids table in file hda_intel.c ?

Peter Zubaj

Quoted 41 lines · Dirk
Quoted 12 lines · Clemens Ladisch
Quoted 7 lines · Dirk

http://pciids.sourceforge.net/iii/?i=10b95461

Doesn't work with snd_hda_intel or anything else I tried...

Quoted 8 lines

We don't have any documentation for this chip.

The CVS version of this driver assumes that this chip is compatible with the Intel HDA controller; please test it.

That's exactly what I tried. I also tried the hacked alsa-driver from the download pages of Realtek and the Mainboard manufacturer. But nothing worked. The driver loads fine but there is no mixer and no sound.

The mainboard description
(http://www.asus.com/prog/spec.asp?m=P5RD1-V&langs=01) says it's a Realtek ALC 861... but "lspci -n" identifies (0x10b9) ALi and not RealTek... :-/

ALi's site doesn't list this card or chip (I looked for "5461" and "M5461") at all. So I guess the mainboard description is right and lspci is "wrong"... Dunno..

Dirk

Quoted 12 lines

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Quoted 13 lines

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

#5 lore raw

This looks like old alsa version. Could you try alsa CVS version ?

Peter Zubaj

Quoted 113 lines · Dirk

Hey!
I tried that right now (Kernel 2.6.12.3).

sound/pci/hda/hda_intel.c

/* PCI IDs */

static struct pci_device_id azx_ids[] = {
        { 0x8086, 0x2668, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 }, /* ICH6 */
        { 0x8086, 0x27d8, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 }, /* ICH7 */
        { 0x8086, 0x269a, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 }, /* ESB2 */
        { 0x10b9, 0x5461, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 }, /* test */
        { 0, }
};

and after reloading the module it says

ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout [...]

and it doesn't look like it will stop anytime soon...

Dirk

Quoted 66 lines

Hi,

Did you try to add this pci id in pci_device_id azx_ids table in file hda_intel.c ?

Peter Zubaj

Quoted 41 lines · Dirk
Quoted 12 lines · Clemens Ladisch
Quoted 7 lines · Dirk

http://pciids.sourceforge.net/iii/?i=10b95461

Doesn't work with snd_hda_intel or anything else I tried...

Quoted 8 lines

We don't have any documentation for this chip.

The CVS version of this driver assumes that this chip is compatible with the Intel HDA controller; please test it.

That's exactly what I tried. I also tried the hacked alsa-driver from the download pages of Realtek and the Mainboard manufacturer. But nothing worked. The driver loads fine but there is no mixer and no sound.

The mainboard description
(http://www.asus.com/prog/spec.asp?m=P5RD1-V&langs=01) says it's a Realtek ALC 861... but "lspci -n" identifies (0x10b9) ALi and not RealTek... :-/

ALi's site doesn't list this card or chip (I looked for "5461" and "M5461") at all. So I guess the mainboard description is right and lspci is "wrong"... Dunno..

Dirk

Quoted 12 lines

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Quoted 13 lines

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Quoted 10 lines

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

author
#6 lore raw

I checked out alsa-kernel and alsa-driver...

cd alsa-driver
./cvscompile
make install
make install-modules

didn't work (I'd read INSTALL) there were still the old drivers in /lib/modules/2.6.12.3/.../sound/
so I'd...

ln -sf alsa-driver /usr/src/linux/sound
cd /usr/src/linux
make modules_install
modprobe snd-hda-intel

which didn't work either (snd_hda_intel: unknown symbol...)

...I guess I never done this before

Give me a quick HOWTO and I'll continue..

Dirk

Quoted 4 lines

This looks like old alsa version. Could you try alsa CVS version ?

It was the alsa stuff included in 2.6.12.3.

Quoted 48 lines

Peter Zubaj

Quoted 42 lines · Dirk

Hey!
I tried that right now (Kernel 2.6.12.3).

sound/pci/hda/hda_intel.c

/* PCI IDs */

static struct pci_device_id azx_ids[] = {
       { 0x8086, 0x2668, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 }, /* ICH6 */
       { 0x8086, 0x27d8, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 }, /* ICH7 */
       { 0x8086, 0x269a, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 }, /* ESB2 */
       { 0x10b9, 0x5461, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0 }, /* test */
       { 0, }
};

and after reloading the module it says

ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout ALSA sound/pci/hda/hda_intel.c:442: azx_get_response timeout [...]

and it doesn't look like it will stop anytime soon...

Dirk

Quoted 9 lines

Hi,

Did you try to add this pci id in pci_device_id azx_ids table in file hda_intel.c ?

Peter Zubaj

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

#7 lore raw
In reply to Dirk
Quoted 4 lines · Dirk

The mainboard description
(http://www.asus.com/prog/spec.asp?m=P5RD1-V&langs=01) says it's a Realtek ALC 861... but "lspci -n" identifies (0x10b9) ALi and not RealTek... :-/

The PCI device is an HDA controller, the Realtek chip is an HDA codec. HDA is a specification for a bus to connect these two.

It has been confirmed that the controller isn't compatible with the Intel HDA controller, so you don't need to try to get it to compile. We have to try to get documentation from ALi.

Regards,
Clemens

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

author
#8 lore raw
Quoted 14 lines · Clemens Ladisch
Quoted 6 lines · Dirk

The mainboard description
(http://www.asus.com/prog/spec.asp?m=P5RD1-V&langs=01) says it's a Realtek ALC 861... but "lspci -n" identifies (0x10b9) ALi and not RealTek... :-/

The PCI device is an HDA controller, the Realtek chip is an HDA codec. HDA is a specification for a bus to connect these two.

Quoted 9 lines

It has been confirmed that the controller isn't compatible with the Intel HDA controller, so you don't need to try to get it to compile. We have to try to get documentation from ALi.

Regards,
Clemens

Ok, just let me know then if I can be of any help...

Dirk

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

author
#9 lore raw
In reply to Clemens Ladisch
Quoted 14 lines · Clemens Ladisch
Quoted 6 lines · Dirk

The mainboard description
(http://www.asus.com/prog/spec.asp?m=P5RD1-V&langs=01) says it's a Realtek ALC 861... but "lspci -n" identifies (0x10b9) ALi and not RealTek... :-/

The PCI device is an HDA controller, the Realtek chip is an HDA codec. HDA is a specification for a bus to connect these two.

Quoted 10 lines

It has been confirmed that the controller isn't compatible with the Intel HDA controller, so you don't need to try to get it to compile. We have to try to get documentation from ALi.

Regards,
Clemens

One last thing...

Maybe this does help a little:
http://dlsvr01.asus.com/pub/ASUS/mb/socket775/P5RD1-V/Audio_Linux.zip

It's the driver (with sources) from the mainboard manufacturer (It didn't work for me though....)

Dirk

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click

#10 lore raw
Quoted 4 lines · Dirk

Maybe this does help a little:
http://dlsvr01.asus.com/pub/ASUS/mb/socket775/P5RD1-V/Audio_Linux.zip

It's the driver (with sources) from the mainboard manufacturer

It tries to access the ALi controller in the same way as the Intel controller.

It may be possible that the ALi chip was designed to be compatible with Intel's, but that they got some detail wrong. Or that the driver gets some detail wrong. There's no way to know without docs

Regards,
Clemens

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click