You are not logged in.

#1 2006-12-21 05:38:44

aku
Member
From: Greendale, Finland
Registered: 2006-11-25
Posts: 24

CD eject issues ? [SOLVED]

Hi, I'm having one strange problem after the update..
I did a fresh install to 0.8, and now I cannot eject a cd, unless (in KDE) I right-click on the mounted cd icon, and select "unmount". Then when I press the eject button on my cd-drive, it ejects.
I used to get "eject" from command line to work, but now it gives me :

[aku@pinguboxi ~]$ eject
Error: could not determine real path of the device: No such file or directory
eject: unmount of `/media/K3b40data40project' failed

How can I get automount to work so, when I press the physical eject button on the cd drive, it would automount and eject ?
/aku

Offline

#2 2006-12-21 13:14:12

mr.MikyMaus
Member
From: disabled
Registered: 2006-03-31
Posts: 285

Re: CD eject issues ? [SOLVED]

you have to update your /etc/fstab to match new device names mapping.. On my computer, dvdrw is now known as /dev/sr0 and fstab looks like this:

[miky@ghoulie ~]$ grep sr0 /etc/fstab
/dev/sr0             /mnt/cd    iso9660 ro,user,noauto,unhide   0      0
/dev/sr0             /mnt/dvd    udf   ro,user,noauto,unhide   0      0

-miky


What happened to Arch's KISS? systemd sure is stupid but I must have missed the simple part ...

... and who is general Failure and why is he reading my harddisk?

Offline

#3 2006-12-21 13:55:43

Snarkout
Member
Registered: 2005-11-13
Posts: 542

Re: CD eject issues ? [SOLVED]

You don't have a path there - I'm not sure eject explicitly needs one, but I've always used one.


Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein

Offline

#4 2006-12-21 14:01:20

Snarkout
Member
Registered: 2005-11-13
Posts: 542

Re: CD eject issues ? [SOLVED]

mr.MikyMaus wrote:

you have to update your /etc/fstab to match new device names mapping.. On my computer, dvdrw is now known as /dev/sr0 and fstab looks like this:

[miky@ghoulie ~]$ grep sr0 /etc/fstab
/dev/sr0             /mnt/cd    iso9660 ro,user,noauto,unhide   0      0
/dev/sr0             /mnt/dvd    udf   ro,user,noauto,unhide   0      0

-miky

My symlinks changed, but /dev/cdrom and /dev/dvd still point at /dev/sr0, albeit through links in /dev/cd/.  Also, is an fstab entry for optical discs still actually needed?  I've seen people say yes and no - in my own case I can't tell the difference - my drive seems to function exactly the same with versus without.


Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein

Offline

#5 2006-12-21 14:09:40

aku
Member
From: Greendale, Finland
Registered: 2006-11-25
Posts: 24

Re: CD eject issues ? [SOLVED]

Thanks! I'll try it a bit later, and I'll post the results..

/aku

Offline

#6 2006-12-21 14:21:06

mr.MikyMaus
Member
From: disabled
Registered: 2006-03-31
Posts: 285

Re: CD eject issues ? [SOLVED]

Snarkout wrote:

My symlinks changed, but /dev/cdrom and /dev/dvd still point at /dev/sr0, albeit through links in /dev/cd/.

Mine did as well, but I had difficulties with cdrecord (or whatever is it now), and also with other applications relying on fstab when I pointed them to either /dev/dvd or /dev/cdrom, etc..

I don't know why. All I care about is that it works with my actual fstab smile

Snarkout wrote:

Also, is an fstab entry for optical discs still actually needed?  I've seen people say yes and no - in my own case I can't tell the difference - my drive seems to function exactly the same with versus without.

I cannot see why not? It's good to have some default mount options, isn't it?

I am a console man, so writing

$ mount /mnt/dvd

is quite comfortable compared to

# mount -t udf /dev/sr0 /mnt/dvd
Snarkout wrote:

You don't have a path there - I'm not sure eject explicitly needs one, but I've always used one.

from 'man eject':

The device corresponding to <name> is ejected. The name can be a device file or mount point, either a full path or with the leading "/dev", "/media" or "/mnt" omitted. If no name is specified, the default name "cdrom" is used.

For me, until I had rewritten my /etc/fstab to it's present state, eject did not work after upgrade to 2.6.19.x kernel series, regardless the /dev/cdrom symlink pointed to correct device (or at least I think it did).

Therefore I think updating fstab should correct aku's problem.

-miky


What happened to Arch's KISS? systemd sure is stupid but I must have missed the simple part ...

... and who is general Failure and why is he reading my harddisk?

Offline

#7 2006-12-21 14:52:11

Snarkout
Member
Registered: 2005-11-13
Posts: 542

Re: CD eject issues ? [SOLVED]

Well there you go - my reasoning was the same as your fstab reasoning - a full path is always better.  Thanks for the response!


Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein

Offline

#8 2006-12-23 10:28:02

aku
Member
From: Greendale, Finland
Registered: 2006-11-25
Posts: 24

Re: CD eject issues ? [SOLVED]

Thanks Miky & Snark !
I modified my /etc/fstab,

it used to look like this :

/dev/cdrom           /mnt/cd   iso9660   ro,user,noauto,unhide   0      0
/dev/dvd               /mnt/dvd  udf          ro,user,noauto,unhide   0      0
/dev/fd0               /mnt/fl   vfat                   user,noauto             0      0

and I changed it to :

/dev/sr0               /mnt/cd   iso9660   ro,user,noauto,unhide   0      0
/dev/sr0               /mnt/dvd  udf          ro,user,noauto,unhide   0      0
/dev/fd0               /mnt/fl   vfat                   user,noauto             0      0

and it works ('eject' from the command line, or pressing the button on the drive) !
Thanks for the help !

/aku

Offline

Board footer

Powered by FluxBB