Re: 2.6.24-rc2 breaks nVidia MCP51 High Definition Audio

Previous thread: [poll] Is the megafreeze development model broken? by ciol on Wednesday, November 7, 2007 - 3:56 pm. (11 messages)

Next thread: compat_sys_times() bogus until jiffies >= 0. by David Brown on Wednesday, November 7, 2007 - 3:47 pm. (36 messages)
From: Gerhard Mack
Date: Wednesday, November 7, 2007 - 3:39 pm

hello,

This worked fine in 2.6.23 but now the kernel no longer sees my audio 
controller.

00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev 
a2)
00:10.1 0403: 10de:026c (rev a2)

Let me know if I can provide more info or test patches.

	Gerhard

--
Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.
-

From: Andrew Morton
Date: Wednesday, November 7, 2007 - 4:21 pm

Please provide the output of `dmesg -s 1000000' for both 2.6.23
and 2.6.24-rc3, thanks.

Are you sure that the driver is suitably configured?  Sometimes
we like to fiddle config options so that a `make oldconfig' will go and
unconfigure drivers which you need.
-

From: Gerhard Mack
Date: Wednesday, November 7, 2007 - 5:07 pm

Found an option for generic HD audio and enabled that with only marginally 
better results.  Now instead of not detecting my card it's showing a 
single volume control in the mixer and not providing any sound at all.

2.6.23:
Advanced Linux Sound Architecture Driver Version 1.0.14 (Fri Jul 20 
09:12:58 2007 UTC).
ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [AAZA] -> GSI 22 (level, low) 
-> IRQ 22
PCI: Setting latency timer of device 0000:00:10.1 to 64
ALSA device list:
  #0: HDA NVidia at 0xfe024000 irq 22
GACT probability on

2.6.24-rc2:
Advanced Linux Sound Architecture Driver Version 1.0.15 (Tue Oct 23 
06:09:18 2007 UTC).
ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [AAZA] -> GSI 22 (level, low) 
-> IRQ 22
PCI: Setting latency timer of device 0000:00:10.1 to 64
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[0011d8000101f761]
ALSA device list:
  #0: HDA NVidia at 0xfe024000 irq 22
GACT probability on

 

--
Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.
From: Takashi Iwai
Date: Wednesday, November 7, 2007 - 8:41 pm

At Wed, 7 Nov 2007 19:07:07 -0500 (EST),

Both look OK.

Please show your kernel config and /proc/asound/card0/codec#*
contents.  Did you choose CONFIG_SND_HDA_CODEC_* properly?

Also, please be more specific about your hardware.  The implementation
of HD-audio stuff is deifferent greatly among products.  It's very
important to know what kind of machine (h/w vendor, product name,
model, etc) to identify whether the configuration is known or not
(i.e. it was really supported or it worked just casually).


Takashi
-

From: Gerhard Mack
Date: Thursday, November 8, 2007 - 6:38 am

The machine is an Asus M2NPV-VM motherboard with an Nforce MCP51 chpset. 
and there is not an CONFIG_SND_HDA_CODEC_ option for NVIDIA so I selected 
generic instead.

Pci info:
00:10.1 Audio device: nVidia Corporation MCP51 High Definition 
Audio (rev a2)
00:10.1 0403: 10de:026c (rev a2)

	Gerhard

--
Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.
From: Takashi Iwai
Date: Thursday, November 8, 2007 - 8:41 am

At Thu, 8 Nov 2007 08:38:18 -0500 (EST),

That's the problem.   MCP51 is the controller chip, not a codec chip.
It's always supported by snd-hda-intel driver.  CONFIG_SND_HDA_CODEC_*
are configs to choose codec chips.

Simply select all CONFIG_SND_HDA_CODEC_*=y if you are not sure (as
they are default=y).  I guess CONFIG_SND_HDA_CODEC_ANALOG=y should
suffice but selecting others won't hurt except for a small memory
footprint.


Takashi
-

From: Gerhard Mack
Date: Thursday, November 8, 2007 - 12:51 pm

Codec: Analog Devices AD1986A
Address: 0
Vendor Id: 0x11d41986
Subsystem Id: 0x104381b3
Revision Id: 0x100500

Works like a charm now,

 thanks.

	Gerhard

--
Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.
-

Previous thread: [poll] Is the megafreeze development model broken? by ciol on Wednesday, November 7, 2007 - 3:56 pm. (11 messages)

Next thread: compat_sys_times() bogus until jiffies >= 0. by David Brown on Wednesday, November 7, 2007 - 3:47 pm. (36 messages)