public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Fredrick O Jackson <fred@electronsrus.com>
Cc: linux-kernel@vger.kernel.org,
	ALSA user list <alsa-user@lists.sourceforge.net>
Subject: Re: soundblaster pnp ide won't pnp
Date: Tue, 10 Jan 2006 20:25:34 -0500	[thread overview]
Message-ID: <1136942735.2007.120.camel@mindpipe> (raw)
In-Reply-To: <200601101916.28019@bits.electronsrus.com>

On Tue, 2006-01-10 at 19:16 -0600, Fredrick O Jackson wrote:
> ok, so far Ive tried with and without isapnp support in the kernel, I've 
> toggled the PNP OS, and ACPI switches in the bios, I've tried compiling the 
> drivers into the kernel (hd, ide, ide-disk, isapnp, ide-pnp, and others) on 
> 2.6.14, 2.6.15 and 2.4.27. I've used kernel command lines. I usually get 
> messages similar to that below (at the bottom). I also cannot find the 
> modules ide, ide-probe, or ide-detect which are documented in the 
> Documentation directory.
> 
> what method is recommended and what kernel would you suggest?
> 

> Jan 10 12:42:41 pthree kernel: ide: failed opcode was: unknown
> Jan 10 12:42:41 pthree kernel: ide2: reset: success
> Jan 10 12:43:11 pthree kernel: hde: irq timeout: status=0x50 { DriveReady 
> SeekComplete }
> 

You don't say whether you are trying to use the ALSA or OSS driver.  And
your dmesg has no mention at all of a sound card, it just shows that hde
is failing.

First, if you were trying to load the OSS driver, try the ALSA driver,
and post the output of dmesg when loading snd-sb16 and the output of
"cat /proc/asound/cards".

Lee


  reply	other threads:[~2006-01-11  1:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-11  1:16 soundblaster pnp ide won't pnp Fredrick O Jackson
2006-01-11  1:25 ` Lee Revell [this message]
2006-01-11  1:44   ` Fredrick O Jackson

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=1136942735.2007.120.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=fred@electronsrus.com \
    --cc=linux-kernel@vger.kernel.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