Yep, the eject and close commands do work. No problems at all. The inquiry command led to a 'misbehaving' drive. If I issue inquiry the drive makes some strange noises, almost like on power-on. Maybe there is some SCSI bus reset going on? That's the same effect when using cd-info or mplayer with libcdio on the drive.
@idle command: I don't know, how can I find this out without using mmc-tool? Can hdparm possibly issue such a command? I also know sdparm but is seems a bit complex for me (who has no SCSI device programming knowledge). @manual: At least there is nothing in the original manual that was shipped with the drive. And I can't find any detailed technical infos on the net. I have found some information about the drive in the Feurio! drive DB. I've sent the Feurio team a mail asking for help, maybe they reply maybe not. I'm going to install cdrdao and cdrecord and do some checking with them. Also going to check the speed setting commands from mmc-tool. @example: I really don't know what to change there to make the drive behave correctly. Probably related to my SCSI knowledge lack :D R. Bernstein wrote: > The strace output shows that the mmtool ioctl commands to get inquiry > and eject don't report an errors. Did eject work? Did anything work? > > Sending an idle command via start/stop gave an error return but it may > be that the drive doesn't support that command. Does it support this > command? Inquiry didn't give an ioctl error but I didn't look like it > returned any results. > > Do you have or can you find a manual for this device that describes > the features it supports (MMC-1?, MMC-2?) and/or describes the commands to > get to do what it needs? > > Another approach is to modify example/mmc1.c or example/mmc2.c to get > them to do something useful. > > _______________________________________________ Libcdio-help mailing list [email protected] http://lists.gnu.org/mailman/listinfo/libcdio-help
