From: Stephen Clark <stephen.clark@earthlink.net>
To: Andrew Morton <akpm@osdl.org>
Cc: sclark46@earthlink.net, linux-kernel@vger.kernel.org
Subject: Re: 2.6.12 sound problem
Date: Fri, 29 Jul 2005 23:13:52 -0400 [thread overview]
Message-ID: <42EAF070.5050001@earthlink.net> (raw)
In-Reply-To: <20050729014150.6e97dfd2.akpm@osdl.org>
Andrew Morton wrote:
>(Please do reply-to-all when dealing with kernel stuff)
>
>Stephen Clark <stephen.clark@earthlink.net> wrote:
>
>
>>Takashi Iwai wrote:
>>
>>
>>
>>>At Tue, 26 Jul 2005 19:35:55 -0400,
>>>Stephen Clark wrote:
>>>
>>>
>>>
>>>
>>>>Hello List,
>>>>
>>>>
>>>>I recently upgraded my laptop, HP Pavilion N5430, from a 2.4.21 kernel
>>>>to 2.6.12. As a result of
>>>>doing this my sound no longer works correctly. It plays the same thing
>>>>repeatedly some number
>>>>of times - if it plays at all.
>>>>
>>>>Any ideas on how to debug this would be appreciated.
>>>>
>>>>Additional info I don't see any interrupts in /proc/interrupts for the
>>>>Allegro which is on int 5.
>>>>I just tried the same laptop with knoppix and a 2.4.27 kernel and sound
>>>>works great and I do
>>>>see interrupts for Allegro on int 5.
>>>>
>>>>
>>>>
>>>>
>>>The irq problem is likely related with ACPI.
>>>Try to boot once with pci=noacpi.
>>>
>>>
>>>Takashi
>>>-
>>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>>the body of a message to majordomo@vger.kernel.org
>>>More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>Please read the FAQ at http://www.tux.org/lkml/
>>>
>>>
>>>
>>>
>>>
>>Hi Takashi,
>>
>>I have boot the 2.6.12 kernel with acpi=off pci=noacpi,usepirqmask or I
>>get a panic or a hang.
>>
>>
>
>It's just really awful that 2.4 simply worked and 2.6 requires a sprinkle
>of obscure kernel parameters. I shudder to think how long it took you to
>work them out.
>
>
>
>>I don't have to do this with 2.4.27, anybody know why?
>>
>>
>>
>
>Perhaps you could send the `dmesg -s 1000000' output?
>
>
>
Hi Andrew,
Thanks for the response.
I found a better solution to my problem with my HP N5430 laptop over on
the alsa-devel list, my sound had quit working also. The new
solution, which was pointed out to me by Henry Yuan was to boot with
lapic. I had noticed in the dmesg output that a lapic existed but was
turned off by the bios, and a pseudo local apic was being used, this
caused problems with APCI and my sound.
If you would still like the dmesg I would be glad to send it.
Steve
next prev parent reply other threads:[~2005-07-30 3:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 23:35 2.6.12 sound problem Stephen Clark
2005-07-27 4:23 ` Lee Revell
2005-07-27 15:31 ` Stephen Clark
2005-07-27 8:26 ` Takashi Iwai
2005-07-27 15:31 ` Stephen Clark
2005-07-29 8:41 ` Andrew Morton
2005-07-29 9:05 ` [PATCH] mm/slab.c : prefetchw the start of new allocated objects Eric Dumazet
2005-07-29 9:17 ` Andrew Morton
2005-07-29 10:08 ` Ingo Molnar
2005-07-30 19:31 ` David S. Miller
2005-07-30 3:13 ` Stephen Clark [this message]
2005-07-30 15:56 ` 2.6.12 sound problem Stephen Clark
2005-07-31 19:25 ` 2.6.13rc4 hang Stephen Clark
2005-08-01 13:11 ` Stephen Clark
-- strict thread matches above, loose matches on Subject: below --
2005-07-25 19:16 2.6.12 sound problem Stephen Clark
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=42EAF070.5050001@earthlink.net \
--to=stephen.clark@earthlink.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sclark46@earthlink.net \
/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