[Pkg-libburnia-devel] Bug#789260: libburn4: Incompatibility with Plextor PX-608CU burner
undelborg at gmail.com
Mon Jun 22 21:42:25 UTC 2015
I've downloaded 3.18.16 longterm kernel and plan to compile it on my system.
Linux Mint (which is OK) uses kernel 3.13 and fedora 22 uses kernel 4.0
In fact there is a lot of UAS/USB bugs reported for kernel 3.16 (and some
for 3.15 and 3.17).
Controllers you mentioned are USB 3.0. My drive is definitely USB 2.0.
However, if it looks like a duck, swim like a duck and quacks like a
duck... I'll definitely need to try new kernel.
2015-06-22 21:34 GMT+03:00 Thomas Schmitt <scdbackup at gmx.net>:
> > I have found some interesting discussion about UAS bugs in kernel 3.16:
> > https://lists.debian.org/debian-kernel/2014/07/msg00318.html
> UAS ... google ... wikipedia ...
> Well, it would be the natural way to perform SG_IO with a USB
> device. Burn programs issue SCSI commands and UAS is designed
> for transporting them. Wikipedia has:
> "Version 3.18-rc4 of the Linux kernel disables buggy UAS
> implementation in xHCI host controllers Etron EJ168,
> ASMedia ASM1042, and VIA VL80x."
> But i understand that UAS is quite a new protocol.
> Is your drive's USB controller young enough ? (Actually
> i assume the drive is SATA or IDE and the box has a
> USB-SATA or USB-IDE bridge bridge.)
> > An here comes the output from my kern.log:
> > Jun 22 15:12:02 D-NESTERKIN kernel: [ 1.508233] usb 3-2: Product:
> > USB Storage Adapter
> They really give few clue about age and version of the
> drive-side USB controller.
> I googled for "PLEXTOR USB Storage Adapter" "UAS" and found
> nearly nothing. Descriptions of UAS refer to hard disks and
> SSDs, rather than optical drives. But - as stated - i expect
> it to depend on the USB-SATA or USB-IDE controller of the
> drive box.
> In any case, recent changes in USB are obvious suspects.
> Now i'm curious whether the working and non-working Linuxes
> show a pattern with kernel revisions.
> Have a nice day :)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pkg-libburnia-devel