Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Clark <stephen.clark@earthlink.net>
To: alsa-devel@lists.sourceforge.net
Subject: Re: 2.6.12 sound problem
Date: Thu, 28 Jul 2005 10:05:07 -0400	[thread overview]
Message-ID: <42E8E613.9050008@earthlink.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0507270912370.8129@tm8103.perex-int.cz>

Jaroslav Kysela wrote:

>On Tue, 26 Jul 2005, 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.
>>    
>>
>
>It looks like an interrupt problem. Try acpi=off and some other switches 
>like pci=biosirq etc.
>
>						Jaroslav
>
>-----
>Jaroslav Kysela <perex@suse.cz>
>Linux Kernel Sound Maintainer
>ALSA Project, SUSE Labs
>
>  
>
Hi Jaroslav,

I am booting with acpi=off pci=noacpi,usepirqmask appended to my command
line - if I dont
the kernel hangs at various times and places.

Steve



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September
19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  reply	other threads:[~2005-07-28 14:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 23:34 2.6.12 sound problem Stephen Clark
2005-07-27  7:14 ` Jaroslav Kysela
2005-07-28 14:05   ` Stephen Clark [this message]
2005-07-28 14:11 ` Stephen Clark
  -- strict thread matches above, loose matches on Subject: below --
2005-08-01  3:06 Yuan, Hang
2005-07-29 10:21 Yuan, Hang
2005-07-29 12:41 ` Stephen Clark
2005-07-30  3:05   ` Stephen Clark
2005-07-26 17:08 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=42E8E613.9050008@earthlink.net \
    --to=stephen.clark@earthlink.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --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