After upgrading from FC6 to F7 gnomebaker stopped working.
After poking around again I found that the reason is that gnomebaker is trying to open /dev/sr0 as the scsi recording device, but in my F7 that doesn't exist.
However these do exist:
[root@rjm src]# ls -l /dev/*sr0 lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/cdrom-sr0 -> scd0 lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/cdrw-sr0 -> scd0 lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/cdwriter-sr0 -> scd0 lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/dvdrw-sr0 -> scd0 lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/dvd-sr0 -> scd0 lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/dvdwriter-sr0 -> scd0
So I added the line:
ln -s /dev/scd0 /dev/sr0
to /etc/rc.d/rc5.d/S99local and gnomebaker works.
Why does it get it wrong? Well...
[root@rjm src]# cat /proc/sys/dev/cdrom/info CD-ROM information, Id: cdrom.c 3.20 2003/12/17
drive name: sr0 drive speed: 24 drive # of slots: 1 Can close tray: 1 Can open tray: 1 Can lock tray: 1 Can change speed: 1 Can select disk: 0 Can read multisession: 1 Can read MCN: 1 Reports media changed: 1 Can play audio: 1 Can write CD-R: 1 Can write CD-RW: 1 Can read DVD: 1 Can write DVD-R: 1 Can write DVD-RAM: 1 Can read MRW: 1 Can write MRW: 1 Can write RAM: 1
so I guess gnomebaker assumes there is a node called /dev/sr0, but obviously F7 is trying to be friendly by creating specific nodes based on the capabilities of the device and then I assume an application can open the appropriate device.
Should gnomebaker be changed? or would it be friendly for F7 to also create the generic node /dev/sr0 at startup as well as the capability specific nodes?
Thanks Rick
Rick Marshall wrote:
After upgrading from FC6 to F7 gnomebaker stopped working.
After poking around again I found that the reason is that gnomebaker is trying to open /dev/sr0 as the scsi recording device, but in my F7 that doesn't exist.
Do file bug reports for this and the hidd issues.
Rahul
On 6/29/07, Rick Marshall rjm@zenucom.com wrote:
After upgrading from FC6 to F7 gnomebaker stopped working.
After poking around again I found that the reason is that gnomebaker is trying to open /dev/sr0 as the scsi recording device, but in my F7 that doesn't exist.
However these do exist:
[root@rjm src]# ls -l /dev/*sr0 lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/cdrom-sr0 -> scd0 lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/cdrw-sr0 -> scd0 lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/cdwriter-sr0 -> scd0 lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/dvdrw-sr0 -> scd0 lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/dvd-sr0 -> scd0 lrwxrwxrwx 1 root root 4 2007-06-30 10:44 /dev/dvdwriter-sr0 -> scd0
So I added the line:
ln -s /dev/scd0 /dev/sr0
to /etc/rc.d/rc5.d/S99local and gnomebaker works.
Why does it get it wrong? Well...
[root@rjm src]# cat /proc/sys/dev/cdrom/info CD-ROM information, Id: cdrom.c 3.20 2003/12/17
drive name: sr0 drive speed: 24 drive # of slots: 1 Can close tray: 1 Can open tray: 1 Can lock tray: 1 Can change speed: 1 Can select disk: 0 Can read multisession: 1 Can read MCN: 1 Reports media changed: 1 Can play audio: 1 Can write CD-R: 1 Can write CD-RW: 1 Can read DVD: 1 Can write DVD-R: 1 Can write DVD-RAM: 1 Can read MRW: 1 Can write MRW: 1 Can write RAM: 1
so I guess gnomebaker assumes there is a node called /dev/sr0, but obviously F7 is trying to be friendly by creating specific nodes based on the capabilities of the device and then I assume an application can open the appropriate device.
Should gnomebaker be changed? or would it be friendly for F7 to also create the generic node /dev/sr0 at startup as well as the capability specific nodes?
Thanks Rick
Has a bug been filed for this yet? I can't find it. And I have the same problem, it affects gnomebaker as well as wodim on both of my F7 machines.
-P