From: Chris Pemberton <cjpembo@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: alsa-driver-1.0.14rc3 won't compile with kernel 2.6.20.3 when Processor family is Core2
Date: Thu, 10 May 2007 13:54:08 -0500 [thread overview]
Message-ID: <46436A50.8090703@gmail.com> (raw)
In-Reply-To: <s5hsla4iqn8.wl%tiwai@suse.de>
Takashi Iwai wrote:
> At Thu, 10 May 2007 11:17:22 -0500,
> Chris Pemberton wrote:
>
>> Takashi Iwai wrote:
>>
>>> At Wed, 09 May 2007 23:28:16 -0500,
>>> Chris Pemberton wrote:
>>>
>>>
>>>> Laptop has Pentium Dual Core and Intel HD Audio
>>>> Kernel is 2.6.20.3 compiled for Processor family Core2.
>>>> In-kernel alsa drivers are 1.0.14rc3 (cat /proc/asound/version) and
>>>> compile ok.
>>>> In-kernel drivers do not work for this sound card.
>>>>
>>>> Downloaded 1.0.14rc3 and applied patch_realtek.c
>>>> ./configure --prefix=/usr --with-cards=hda-intel
>>>> "make" gives the following error:
>>>>
>>>> make[1]: Entering directory `/usr/src/linux-2.6.20.3'
>>>>
>>>>
>>>>> /usr/src/linux-2.6.20.3/Makefile:491:
>>>>> /usr/src/linux-2.6.20.3/arch//Makefile: No such file or directory
>>>>>
>>>>>
>>>> If the kernel is compiled with Processor family = Pentium M, the
>>>> external alsa drivers compile clean and the soundcard works.
>>>>
>>>> So, Processor family = Core2 cannot be selected when using external
>>>> alsa-driver-1.0.14rc3.
>>>>
>>>>
>>> This should have been fixed on 1.0.14rc4. Give it a try.
>>>
>>>
>>> Takashi
>>>
>>>
>>>
>> Does 1.0.14rc4 contain the patch_realtek.c? Or will I have to apply the
>> patch there too?
>>
>
> It has since a few years ago. I don't know which patch you're
> referring, but most of patches have been already merged in 1.0.14rc4.
>
>
> Takashi
>
>
I recompiled my 2.6.20.3 kernel for core2, and tried alsa 1.0.14rc4 as
you suggested:
make[1]: Entering directory `/usr/src/linux-2.6.20.3'
CC [M] /usr/src/alsa-driver-1.0.14rc4/acore/memalloc.o
In file included from /usr/src/alsa-driver-1.0.14rc4/acore/memalloc.inc:13,
from /usr/src/alsa-driver-1.0.14rc4/acore/memalloc.c:1:
/usr/src/alsa-driver-1.0.14rc4/include/adriver.h: In function
'snd_pci_orig_save_state':
/usr/src/alsa-driver-1.0.14rc4/include/adriver.h:1168: error: too many
arguments to function 'pci_save_state'
/usr/src/alsa-driver-1.0.14rc4/include/adriver.h: In function
'snd_pci_orig_restore_state':
/usr/src/alsa-driver-1.0.14rc4/include/adriver.h:1172: error: too many
arguments to function 'pci_restore_state'
make[4]: *** [/usr/src/alsa-driver-1.0.14rc4/acore/memalloc.o] Error 1
make[3]: *** [/usr/src/alsa-driver-1.0.14rc4/acore] Error 2
make[2]: *** [_module_/usr/src/alsa-driver-1.0.14rc4] Error 2
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.20.3'
make: *** [compile] Error 2
Then I tried again it with the patch_realtek.c patch copied in 1.0.14rc4
and got the exact same error.
I've tried when newer kernels as well: no good with core2 in kernel.
Chris
prev parent reply other threads:[~2007-05-10 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 4:28 alsa-driver-1.0.14rc3 won't compile with kernel 2.6.20.3 when Processor family is Core2 Chris Pemberton
2007-05-10 9:07 ` Takashi Iwai
2007-05-10 16:17 ` Chris Pemberton
2007-05-10 16:34 ` Takashi Iwai
2007-05-10 18:26 ` Chris Pemberton
2007-05-10 18:54 ` Chris Pemberton [this message]
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=46436A50.8090703@gmail.com \
--to=cjpembo@gmail.com \
--cc=alsa-devel@alsa-project.org \
/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;
as well as URLs for NNTP newsgroup(s).