From: mikeH <mikeH@notnowlewis.co.uk>
To: Tomasz Rola <rtomek@cis.com.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lost interrupt
Date: Wed, 08 May 2002 09:13:56 +0100 [thread overview]
Message-ID: <3CD8DE44.3090700@notnowlewis.co.uk> (raw)
In-Reply-To: <Pine.LNX.3.96.1020508042330.2702K-100000@pioneer>
Tomasz Rola wrote:
>hdparm -u0 /dev/hdX for every X in existing disks you have problems with.
>
>
>
>hdparm -d0a0u0 /dev/ide/host0/bus0/target0/lun0/disc (or /dev/hda).
>
>bye
>T.
>
>
>
Thanks, I tried that but to no avail :(
To expand on the problem :
I have a creative DVD 5x drive and some unbranded CD-RW drive. The
problem occurs on both when I try to rip audio.
I know for a fact they both have the capability to rip audio nicely, I
have seen them do it under a 2.2.X kernel, but now I'm running 2.4.18 (I
need 2.4 for my nvidia card)
However, hdparm returns this (on both drives, no matter what
slave/master dma/irq combo I use)...
HDIO_GET_MULTCOUNT failed: Invalid argument
I/O support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 0 (off)
keepsettings = 0 (off)
HDIO_GET_NOWERR failed: Invalid argument
readonly = 1 (on)
readahead = 0 (off)
HDIO_GETGEO failed: Invalid argument
busstate = 1 (on)
HDIO_GET_ACOUSTIC failed: Invalid argument
See the worrying "HDIO_GET_ACOUSTIC failed: Invalid argument" ?
I'm not sure who is maintaining that part of the kernel though.
Thanks for any help,
mikeH
next prev parent reply other threads:[~2002-05-08 8:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-07 22:04 lost interrupt mikeH
2002-05-08 2:36 ` Tomasz Rola
2002-05-08 8:13 ` mikeH [this message]
2002-05-08 13:02 ` Padraig Brady
2002-05-08 18:28 ` Tomasz Rola
2002-05-08 11:45 ` Padraig Brady
2002-05-08 12:02 ` Mike
-- strict thread matches above, loose matches on Subject: below --
2002-07-16 14:58 Lost Interrupt David Gironella Casademont
2002-07-17 1:27 ` Samuel Flory
2001-05-20 17:38 SoloCDM
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=3CD8DE44.3090700@notnowlewis.co.uk \
--to=mikeh@notnowlewis.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rtomek@cis.com.pl \
/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