Arch Linux

lilsirecho

Veteran

Registered: 2003-10-24

Posts: 5,000

cdrom connected USB IDE adapter no play audio file:///root/D

The cdrom is connected via` USB-IDE adapter through a USB2.0 hub.

In udev, this requires an entry in udev rules to assign the devices connected to the USB hub.

This can be done with the following entry:
============================================================
BUS=="usb", SYSFS{product}=="USB2.0 Storage Device",   SYSFS{idProduct}=="6830", SYSFS{idVendor}=="04b4", 
KERNEL=="sd?[1-9]", NAME="%k", MODE="0666", symlink+="zdrive%n"
============================================================
This can be modified to reflect desired symlink.  Basically it allows devices connected to the hub to be addressed via the KERNEL entry [1-9] with the preamble ='sd? which identifies the devices as HDD.

Changing the KERNEL== to KERNEL==sc? [0] changes the devices addressed to cd devices cdrom0.

Thusly changed, the BUS=="usb" does connect the cdrom installed on the hub and the OS displays a media window requesting whether to play the audio CD which is inserted in the cdrom device.

If play is selected, the kscd icon appears but an error accompanies the display as follows:
============================================================
CD-ROM read or access error (or no audio disc in drive).
Please make sure you have access permissions to:
/dev/scd0
============================================================

Because the system recognized the cdromand the insertion of the audio cd, the path must be correct.

What is needed to allow permission from the udev gods?

---

Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: cdrom connected USB IDE adapter no play audio file:///root/D

It's probably the group ownership. Hard disks should be root:disk, cdrom/dvd etc should be root:optical. In a normal setup, this is handled by the default udev rules - in your case, you should create two rules, one for sd?, one for sc?, and add the required GROUP="<groupname>" to each one.

lilsirecho

Veteran

Registered: 2003-10-24

Posts: 5,000

Re: cdrom connected USB IDE adapter no play audio file:///root/D

I have tried the following within the group listing ..#Permissions for IDE CD devices:
============================================================
# permissions for IDE CD devices
BUS=="usb", SYSFS{product}=="USB2.0 Storage Device",   SYSFS{idProduct}=="6830", SYSFS{idVendor}=="04b4", 
KERNEL=="sc?[0-9]", NAME="%k", MODE="0666", symlink+="cdrom0", GROUP="optical"
BUS=="ide", KERNEL=="hd[a-z]", SYSFS{removable}=="1", PROGRAM="/bin/cat /proc/ide/%k/media", RESULT=="cdrom0", NAME="%k", GROUP="optical"
============================================================
I also added a second item in USB devices:
=============================================================
BUS=="usb", SYSFS{product}=="USB2.0 Storage Device",   SYSFS{idProduct}=="6830", SYSFS{idVendor}=="04b4", 
KERNEL=="sc?[0-9]", NAME="%k", MODE="0666", symlink+="cdrom0", GROUP="optical"
BUS=="usb", SYSFS{product}=="USB2.0 Storage Device",   SYSFS{idProduct}=="6830", SYSFS{idVendor}=="04b4", 
KERNEL=="sc?[0-9]", NAME="%k", MODE="0666", symlink+="cdrom0", GROUP="audio"
=============================================================

Neither of these two has corrected the problem and have been there prior to your post.

The cdrom responds to data cd's and dvddata and video dvd's since it is a cdrw/dvdrom device.  No audio disc will play.

There is another entry in the BUS=="usb" which addresses the HDD's with a KERNEL=="sd?{1-9] designator.  This performs correctly for fstab defined HDD's.

I have no designator for HDC or HDD in fstab, expecting these to be USB controlled cd/dvd devices.

I have googled madly and find little definitive data for a hub connected usb system in udev.  The usbview data calls out the usb 2.0 hub but does not list any item tied to it (?).

Perhaps your suggestion may be the answer but the coding is still incorrect within my udev file.

---

Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit!     X-ray confirms Iam spineless!