I have a DVD-ROM and DVD+RW drive and after booting up (say when I upgrade my kernel) udev does not properly assign devices to HDC and HDD. Only HDD appears to be assigned and so typing in eject causes the HDD device to eject and HDC is not usable. However, if I go into root and type in udevstart, everything is working fine again. I have tried custom rules, but to no avail. Reproducible: Always Steps to Reproduce: 1.Reboot the computer 2.Attempt to access DVD drive on HDC 3. Actual Results: The drive accessed is my DVD+RW drive that is HDD. Expected Results: I should be accessing the DVD-ROM drive on HDC I have posted this problem on the forums thinking that creating some custom rules would do the trick, but none of them seem to work. I suspect the computer is not restarting udev when it boots up or not using the rules. In 10-local.rules I have: # Two rules for creating CD-ROM BUS=="ide", KERNEL=="hdc", SYMLINK+="cdrom", GROUP="cdrom" BUS=="ide", KERNEL=="hdd", SYMLINK+="cdrom1", GROUP="cdrom" This is the lowest rule number
You did not specify which udev-version you are using. Please attach info and reopen bug.
Hi, Sorry about that. I am using udev-103. Alex
This cdrom-problem should be fixed with udev-104 ebuilds. Just try to delete (or save and move away) your custom cd-rules, and update to udev-104-r8.
Upgrading seems to have done the trick, thanks. If I have any more problems, I will let you know. Alex
*** This bug has been marked as a duplicate of bug 158060 ***
