From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Emmanuel Fleury <emmanuel.fleury@labri.fr>
Cc: axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [libata] atapi_enabled problem
Date: Thu, 20 Apr 2006 08:28:52 -0700 [thread overview]
Message-ID: <20060420082852.f679a376.rdunlap@xenotime.net> (raw)
In-Reply-To: <44477D93.50501@labri.fr>
On Thu, 20 Apr 2006 14:24:51 +0200 Emmanuel Fleury wrote:
> Hi,
>
> I'm a bit puzzled, I have a Fujistu-Siemens P7120 (see:
> http://www.labri.fr/perso/fleury/index.php?page=p7120) and the DVD-ROM
> wasn't detected at all at boot time.
>
> After googling a bit I found this page:
> http://www.thinkwiki.org/wiki/Problems_with_SATA_and_Linux
>
> So, I tried to compile the kernel with built-in ATAPI and S-ATA support
> (not as modules but embedded in the kernel) and I tried to pass
> libata.atapi_enabled=1 at boot time through kernel options. The
> DVD-drive was recognized at boot but generate tons of errors:
>
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> sr0: CDROM (ioctl) error, command: <6>Test Unit Ready 00 00 00 00 00 00
> sr: Current [descriptor]: sense key: Medium Error
> Additional sense: Unrecovered read error - auto reallocate failed
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
> ata1: translated ATA stat/err 0x51/20 to SCSI SK/ASC/ASCQ 0x3/11/04
> ata1: no sense translation for error 0x20
> ata1: no sense translation for status: 0x51
>
> Then I decided to just modify drivers/scsi/libata-core.c changing the
> line "atapi_enabled = 0" into "atapi_enabled = 1". Then everything
> worked as a charm.
>
> I have no explanation yet for this behaviour (passing kernel options
> should behave the same than changing the code the way I did I suppose).
Yes, it should and it has worked for quite a few people in the past.
I suspect something more like a typo. Anyway, recent kernels
(after 2.6.16, so 2.6.17-rc*) already have atapi_enabled set to 1.
> Does anyone has an idea ?
---
~Randy
next prev parent reply other threads:[~2006-04-20 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 12:24 Emmanuel Fleury
2006-04-20 14:45 ` Emmanuel Fleury
2006-04-20 15:07 ` Emmanuel Fleury
2006-04-20 15:28 ` Randy.Dunlap [this message]
2006-04-20 15:48 ` Emmanuel Fleury
2006-04-20 16:31 ` Randy.Dunlap
2006-04-21 8:23 ` Emmanuel Fleury
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=20060420082852.f679a376.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=axboe@suse.de \
--cc=emmanuel.fleury@labri.fr \
--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
Powered by JetHome