From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: "J.J. Berkhout" <j.j.berkhout@staalenberk.nl>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: Multiple errors with DVD drive
Date: Mon, 26 Sep 2022 14:39:31 +0000 [thread overview]
Message-ID: <YzG5ol9ta2vmb2qn@x1-carbon> (raw)
In-Reply-To: <43161bf3-5a92-ae25-fdc4-57ca2721b359@staalenberk.nl>
On Mon, Sep 26, 2022 at 02:59:19PM +0200, J.J. Berkhout wrote:
>
> OK, I got around to testing the patch.
> I used kernel 5.19.11 (from https://cdn.kernel.org/pub).
> After solving the problem with errors with the compilation (I removed
> the NVIDIA driver and switched to the nouveau driver) and space problems
> on my /boot partition (solved by using sudo make INSTALL_MOD_STRIP=1
> modules_install) I got the following results:
>
> Try 1:
> patching libata-core.c with the lines
> /* PIONEER BD-RW BDR-207M and PIONEER BD-RW BDR-205 have broken LPM
> support */
> { "PIONEER BD-RW DVR-207M", NULL, ATA_HORKAGE_NOLPM },
> { "PIONEER BD-RW DVR-205", NULL, ATA_HORKAGE_NOLPM },
>
> resulted in
> link_power_management_policy still "med_power_with_dipm"
> problem with pioneer DOES occur
Thanks for testing!
libata-core.c has this:
if (dev->horkage & ATA_HORKAGE_NOLPM) {
ata_dev_warn(dev, "LPM support broken, forcing max_power\n");
dev->link->ap->target_lpm_policy = ATA_LPM_MAX_POWER;
}
and
libata-sata.c:ata_scsi_lpm_show() has this:
return sysfs_emit(buf, "%s\n",
ata_lpm_policy_names[ap->target_lpm_policy]);
so
/sys/class/scsi_host/hostXXX/link_power_management_policy
should definitely show "max_performance" when the quirk is applied.
My suggestion was to try:
+ { "PIONEER BD-RW BDR-207M", NULL, ATA_HORKAGE_NOLPM },
However you tested:
+ { "PIONEER BD-RW DVR-207M", NULL, ATA_HORKAGE_NOLPM },
So I think that you simply did a typo in the name.
Looking at you dmesg again however:
[ 1.043657] ata1.00: ATAPI: PIONEER BD-RW BDR-207M, 1.60, max UDMA/100
[ 1.057988] scsi 0:0:0:0: CD-ROM PIONEER BD-RW BDR-207M 1.60 PQ: 0 ANSI: 5
It seems to print two different strings:
"PIONEER BD-RW BDR-207M"
"PIONEER BD-RW BDR-207M"
So I'm actually not really sure which is correct...
I guess try both and see which one that works? :)
Kind regards,
Niklas
next prev parent reply other threads:[~2022-09-26 15:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 12:38 Multiple errors with DVD drive J.J. Berkhout
2022-05-26 23:36 ` Damien Le Moal
2022-05-27 8:50 ` J.J. Berkhout
2022-05-27 10:32 ` J.J. Berkhout
2022-08-05 9:17 ` J.J. Berkhout
2022-09-20 10:05 ` J.J. Berkhout
2022-09-20 13:06 ` Niklas Cassel
[not found] ` <9756ac37-6790-7b83-5840-abe04f8ab838@staalenberk.nl>
2022-09-20 21:08 ` Niklas Cassel
2022-09-21 10:28 ` J.J. Berkhout
2022-09-21 11:58 ` Niklas Cassel
2022-09-21 12:38 ` J.J. Berkhout
2022-09-21 14:54 ` J.J. Berkhout
2022-09-21 18:32 ` Niklas Cassel
2022-09-26 12:59 ` J.J. Berkhout
2022-09-26 14:39 ` Niklas Cassel [this message]
2022-09-26 14:50 ` J.J. Berkhout
2022-09-22 22:08 ` Damien Le Moal
2022-09-23 12:07 ` J.J. Berkhout
2022-09-25 22:57 ` Damien Le Moal
2022-09-20 13:35 ` Niklas Cassel
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=YzG5ol9ta2vmb2qn@x1-carbon \
--to=niklas.cassel@wdc.com \
--cc=j.j.berkhout@staalenberk.nl \
--cc=linux-ide@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