Red Hat Bugzilla – Bug 161725
SATA DVD-Recorder Plextor 716SA not detected
Last modified: 2013-07-02 22:25:40 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):
Steps to Reproduce:
1. Buy a PX716SA
2. Plug it into your SATA-Controller
3. Try to get it work ;-)
same here. SATA-hdd works without problems
This works for me:
[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
recreated modprobe.conf & hwconf
installed new kernel
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (18.104.22.168). 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.
Still an issue on 2.6.13-1.1526_FC4smp
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.
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 22.214.171.124 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
Created attachment 121729 [details]
from working 126.96.36.199 - lsmod; lspci; ls /dev/cd* /dev/dv*
Created attachment 121730 [details]
from failing 2.6.14 - lsmod; lspci; ls /dev/cd* /dev/dv*
I got it working (on both standard 188.8.131.52 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.
Please note that kudzu-184.108.40.206-1 generates a modprobe.conf that won't work.
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.
still not detected with current kernel 2.6.14-1.1656_FC4smp
Kernel 2.6.15-1.1830_FC4smp seems to work. Drive got detected - burning via k3b
2.6.15-1.1831_FC4smp seems to work for me too, I think this bug can be closed.