[Bug 526774] Re: kernel trace and misbehaviour when mapping pktcdvd devices
sergio.callegari
sergio.callegari at gmail.com
Tue Jun 8 11:53:00 UTC 2010
Some more testing
Things seem to (partially) work on some harware. I have tested with a
detachable usb dvd writer, with some positive result (see the
following). However things are completely broken with some other
hardware (again see the following).
PARTIAL success story
With a usb LG dvd writer, things work, but with tons of quirks with
DVD-RW media
Instructions from the udftools package say
1) format the media
dvd+rw-format -force /dev/sr0
OK
2) grow an empty session
growisofs -Z /dev/sr0=/dev/zero
NOT OK
you need to stop growisofs before end, otherwise it overburns the medium and errors out.
3) Format the packet device in UDF format.
mkudffs --utf8 --spartable=2 --media-type=dvdrw /dev/pktcdvd/0
Assuming that you have set up the packet writing device with pktsetup 0 /dev/sr0 or via the config file of udftools
NOT OK
you need to use /dev/pktcdvd/pktcdvd0 for this to succeed.
Similarly, if you had done pktsetup pktdisk /dev/sr0, you would need to use /dev/pktcdvd/pktcdvd0 and not /dev/pktcdvd/pktdisk as expected.
This seems to me as a significant bug. However it is not clear to me what difference should exist between the named packet device and /dev/pktcdvd/pktcdvd0
FULL FAILURE HISTORY
With an LG DVD RAM GH22NP20, nothing works at all.
You just get tons of
end_request: I/O error, dev sr0, sector 13721801512
[11336.826259] sr 0:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[11336.826266] sr 0:0:0:0: [sr0] Sense Key : Illegal Request [current]
[11336.826274] sr 0:0:0:0: [sr0] Add. Sense: Illegal mode for this track
[11336.826283] sr 0:0:0:0: [sr0] CDB: Read(10): 28 00 0c 78 84 ca 00 00 01 00
[11336.826298] end_request: I/O error, dev sr0, sector 13721801512
or
pktcdvd: detected zero packet size!
in the kernel messages.
Please propagate upstream.
--
kernel trace and misbehaviour when mapping pktcdvd devices
https://bugs.launchpad.net/bugs/526774
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.
More information about the kernel-bugs
mailing list