On 08/25/2013 01:17 PM, Baho Utot wrote: > On 08/25/2013 01:13 PM, Bruce Dubbs wrote: >> Baho Utot wrote: >>> On 08/25/2013 12:17 PM, Bruce Dubbs wrote: >>>> Baho Utot wrote: >>>>> On 08/25/2013 11:36 AM, Bruce Dubbs wrote: >>>>>>> I have found that when there is not a cd/dvd in the drive there is no >>>>>>> symlink /dev/cdrom so maybe eject then finds nothing to eject? >>>>>>> After a cd/dvd/ is placed into the drive /dev/cdrom is there and eject >>>>>>> works. >>>>>> What version of udev are you using? There is nothing that I know of >>>>>> that should remove the /dev/cdrom symlink. The symlink should be >>>>>> created when the system boots. Is this perhaps a usb cdrom? >>>>>> >>>>>> Do you have /dev/sr0? >>>>> udev 204 >>>>> >>>>> This is on a Dell lapdog tye cd/dvd/ is internal >>>>> >>>>> Yes /dev/sr0 is there >>>>> >>>>> I should have a new system built with 206 sometime today as it is still >>>>> building >>>> I really don't think there should be a difference for cdroms between >>>> udev 204 and 206. Try 'dmesg|grep -i cdrom' That should indicate >>>> whether the kernel found the device. When udev is started in the boot >>>> scripts, it should create a symlik from >>> [ 1.471298] cdrom: Uniform CD-ROM driver Revision: 3.20 >>> >>> find / -name 60-cdrom_id.rules >>> >>> /lib/udev/rules.d/60-cdrom_id.rules >>> >>> >>>> 60-cdrom_id.rules: >>>> >>>> KERNEL=="sr0", SYMLINK+="cdrom", OPTIONS+="link_priority=-100" >>> Yes it is there >>> >>>> Note that in /etc/udev/rules.d there are a couple of cdrom related >>>> rules. It should generate /etc/udev/rules.d/70-persistent-cd.rules. >>>> >>>> You might want to try to trace through that. >>>> >>>> -- Bruce >>>> >>> I have >>> /etc/udev/rules.d/70-persistent-net.rules >>> /etc/udev/rules.d/81-cdrom.rules >>> /etc/udev/rules.d/83-cdrom-symlinks.rules >> One thing you might try is this. Change the bootscripts to not run >> udevd (or the retry). The system should come up fine, but some symlinks >> or permissions may be missing/wrong. >> >> The run from the command line as root: >> >> /lib/udev/udevd --debug |tee /run/udev-debug.log >> >> You should be able to get some info about how udev perceives the cdrom. >> >> -- Bruce >> > Ok I will try that later after the current build finishes > I have finished my build and I have checked it and found eject works like it is supposed to.
The previous build was SVN-20130624 and the current build is SVN-20130822 The only things different are a few packages glibc, udev, boot scripts and kernel etc. The build was scripted and only packages differences between the two version was changed. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
