Bug 161725 - SATA DVD-Recorder Plextor 716SA not detected
SATA DVD-Recorder Plextor 716SA not detected
Status: CLOSED ERRATA
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
4
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Garzik
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-26 12:26 EDT by Michael Metz
Modified: 2013-07-02 22:25 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-19 00:27:07 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
from working 2.6.13.4 - lsmod; lspci; ls /dev/cd* /dev/dv* (4.08 KB, text/plain)
2005-12-02 01:23 EST, Steve Wendt
no flags Details
from failing 2.6.14 - lsmod; lspci; ls /dev/cd* /dev/dv* (4.07 KB, text/plain)
2005-12-02 01:24 EST, Steve Wendt
no flags Details

  None (edit)
Description Michael Metz 2005-06-26 12:26:53 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Description of problem:
My new DVD-Recorder PX716SA is not detected by Fedora. It's a SATA-Drive.
It's correctly detected by BIOS (can boot from it). My SATA-HDD works also.

How can I help? Which information do you need?

Version-Release number of selected component (if applicable):
kernel-2.6.11-1.1369_FC4SMP

How reproducible:
Always

Steps to Reproduce:
1. Buy a PX716SA
2. Plug it into your SATA-Controller
3. Try to get it work ;-)

Additional info:
Comment 1 Stefan Neufeind 2005-06-26 16:10:52 EDT
same here. SATA-hdd works without problems
Comment 2 Steve Wendt 2005-06-28 21:46:37 EDT
This works for me:
http://www.linuxquestions.org/questions/history/281321
Comment 3 Dave Jones 2005-07-15 17:48:02 EDT
[This comment has been added as a mass update for all FC4 kernel bugs.
 If you have migrated this bug from an FC3 bug today, ignore this comment.]

Please retest your problem with todays 2.6.12-1.1398_FC4 update.

If your problem involved being unable to boot, or some hardware not being
detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE*
installing any kernel updates.
If in doubt, you can recreate this file using..

mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak
mv /etc/modprobe.conf /etc/modprobe.conf.bak
kudzu


Thank you.
Comment 4 Michael Metz 2005-07-16 02:47:19 EDT
recreated modprobe.conf & hwconf
installed new kernel
nothing changed
Comment 5 Dave Jones 2005-09-30 02:35:38 EDT
Mass update to all FC4 bugs:

An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (2.6.13.2). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.

Please retest with this update, and update this bug if necessary.

Thanks.
Comment 6 Michael Metz 2005-09-30 03:34:45 EDT
Still an issue on 2.6.13-1.1526_FC4smp
Comment 7 Dave Jones 2005-11-10 14:36:25 EST
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.

Thank you.
Comment 8 Steve Wendt 2005-12-02 01:21:23 EST
Tested 2.6.14-1.1644_FC4smp, and it doesn't work for me; I get no /dev entries.
 I haven't been able to get standard 2.6.14.3 to work, either.  It seems that
the ENABLE_ATAPI define has been replaced with a module parameter; is the
correct usage of that to add a line like this to /etc/modprobe.conf?
options libata-core atapi_enabled=1
Comment 9 Steve Wendt 2005-12-02 01:23:31 EST
Created attachment 121729 [details]
from working 2.6.13.4 - lsmod; lspci; ls /dev/cd* /dev/dv*
Comment 10 Steve Wendt 2005-12-02 01:24:31 EST
Created attachment 121730 [details]
from failing 2.6.14 - lsmod; lspci; ls /dev/cd* /dev/dv*
Comment 11 Steve Wendt 2005-12-03 00:06:21 EST
I got it working (on both standard 2.6.14.3 and 2.6.14-1.1644_FC4smp).  The
source module is libata-core.c, but the module name is libata - but that was
only part of the problem.  What I had to do:

1) add "options libata atapi_enabled=1" to /etc/modprobe.conf
2) remove "alias scsi_hostadapter1 ata_piix" from /etc/modprobe.conf
3) rebuild initrd image with mkinitrd
4) reboot, and it works! 

Note that ata_piix still gets loaded, so the load order must be the important
thing.  I'm glad that the kernel no longer needs modified (even if it was just a
simple #define) for this to work.  I guess the next step is getting it to work
without needing the extra option.
Comment 12 Steve Wendt 2005-12-03 00:15:41 EST
Please note that kudzu-1.1.116.3-1 generates a modprobe.conf that won't work.
Comment 13 Dave Jones 2006-02-03 01:51:51 EST
This is a mass-update to all currently open kernel bugs.

A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

Thank you.
Comment 14 Michael Metz 2006-02-05 03:12:20 EST
still not detected with current kernel 2.6.14-1.1656_FC4smp
Comment 15 Michael Metz 2006-02-05 11:44:07 EST
Kernel 2.6.15-1.1830_FC4smp seems to work. Drive got detected - burning via k3b
was successful.
Comment 16 Steve Wendt 2006-02-16 23:25:40 EST
2.6.15-1.1831_FC4smp seems to work for me too, I think this bug can be closed.

Note You need to log in before you can comment on or make changes to this bug.