* Ken Schneider [06-06-04 16:25]:

You might also try

eject /media/dvd

Ken, eject and umount are not available *if* an application is using the device. lsof or fuser will divulge the process/proccess id-number so you can kill that process. Usually a device appears *stuck* because you have an application open utilizing that device or left konqueror there or killed konqueror and it's *fast-load* stub remains there. Killing the subject process will release the drive. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos

* Ken Schneider [06-06-04 19:45]:

This is true, but the poster stated that he could mount/umount the drive. I was only pointing out a command that could be used to eject the media after a umount command was issued.

original poster: umount /media/dvd unmounts it apparently, but the dvd refuses to come out., "apparently", although a successful umount would release the dvd ?? -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos

* fx fraipont [06-07-04 01:02]:

None of this releases the DVD, however.

This must be something caused by a yast online update, because it did nor happen right after I installed 9.1

Just now, I've tried to burn a dvd, which went smoothly before: I got an error message in k3b saying: can't unmount /dev/hdc. What happens is that inserting a blank launches submount apparently, and k3b can't unmount, so can't control the drive for burning.

Did you try killing the submount process? -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos

Patrick Shanahan wrote:

* fx fraipont [06-07-04 01:02]:

...

None of this releases the DVD, however.

This must be something caused by a yast online update, because it did nor happen right after I installed 9.1

Just now, I've tried to burn a dvd, which went smoothly before: I got an error message in k3b saying: can't unmount /dev/hdc. What happens is that inserting a blank launches submount apparently, and k3b can't unmount, so can't control the drive for burning.

Did you try killing the submount process?

umount /dev/hdc did the trick, but this kind of problem just should not happen... fxf

Patrick Shanahan wrote:

* fx fraipont [06-07-04 06:29]:

...

umount /dev/hdc did the trick, but this kind of problem just should not happen...

You said that you *did* that, umount /dev/hdc. Is that what you did? That *is* the proper way to un-mount. You can also use the directory name given the mount point, ie: /dev/hdc or /media/hdc or ... ( the assignment in /etc/fstab).

OK let me recap, because I get the impression people are getting confused. When I say DVD stuck inside, I mean stuck inside. lsof | grep dvd returns nothing I Can't find any process acessing /dev/hdc Of course eject /dev/hdc does not work. When I first posted, I rebooted because I needed to burn a DVD. This is something that happened repeatedly to me with 9.0, and when I installed 9.1, it mercifully disappeared completely, courtesy of the very civil supermount which would mount when needed and unmount on the sly when you pressed the eject button. For some unknown reason, it does not seem to work that way; to illustrate that, when I wanted to burn my dvd , inserting the blank I supposed triggered supermount, and k3b burning aborted with the error message "can't unmount /dev/hdc". Unmounting with umount /dev/hdc solved the problem, and allowed k3b to burn. My gripe is that something that worked flawlessly at first (supermount) does not seem to anymore, and I don't know why. Here's the content of my fstab: /dev/dvd /media/dvd subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/dvdrecorder /media/dvdrecorder subfs fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppy subfs fs=floppyfss,procuid,nodev,nosuid,sync 0 0 fxf ~

I noticed that whenever I put in a CD or DVD, no matter if its data or audio or video that Kscd comes up and grabs it. (Yeah that's that shiny cd icon right down there in the dock area). And after you finished your business with Yast or whatever its STILL down there holding a grip on /media/cdrom so it won't eject even after you unmount it. (You have to kill Kscd first) I'm sure that isn't the problem of the original poster, because Patrick Shanahans first suggestion (fuser /media/cdrom) would have brought that into the open, but I thought I'd mention it nevertheless.... :-) As an afterthought: how can you prevent this silly behaviour of Kscd? Best regards, Jos Op dinsdag 8 juni 2004 00:49, schreef BandiPat:

On Monday 07 June 2004 11:53 am, fx fraipont wrote: [...]

If you haven't made any changes in your /etc/fstab yet, try this: Remove the config file $HOME/.kde/share/config/susepluggerrc

Restart KDE. The file will be recreated of course, but just like a new install. This will also set the SuSE hardware tool to ask you about what to do with a cd/dvd when inserted. Uncheck the "do not ask again" block, to keep it asking and see if that helps at all. This is just a thought, don't know if it will help, hinder or blow up your machine. ;o)

If you have made changes to your /etc/fstab, that could be your problem. Again, just a thought and something to check.

Regards, Lee -- --- KMail v1.6.2 --- SuSE Linux Pro v9.1 --- Registered Linux User #225206 On any other day, that might seem strange...

-- Jos van Kan

* Doug McGarrett [06-06-04 19:07]:

It seems kinda dumb, but if you write (as root) and after umounting the device, eject /media/cdrom or perhaps eject /dev/cdrom the drawer should come out and you can snag your disk. This may also happen with your CD, and the cure is the same.

Have you not read the rest of the thread? From my post: ..Ken, eject and umount are not available *if* an application is using the device. lsof or fuser will divulge the process/proccess id-number so you can kill that process. Usually a device appears *stuck* because you have an application open utilizing that device or left konqueror there or killed konqueror and it's *fast-load* stub remains there. Killing the subject process will release the drive. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org HOG # US1244711 Photo Album: http://wahoo.no-ip.org/photos

John Andersen wrote:

...

umount /media/dvd unmounts it apparently, but the dvd refuses to come out., which means I have to reboot my computer to change the DVD. SuSE can't really be ready for the desktop ... (I've been here since 5.3 ...)

fx

If you are sure its unmounted, then its a hardware issue, not a SuSE issue. Time to streighten a stiff paperclip... You know the drill.

Right, I've tried that before, it does release the CD/DVD, bur the drive is useless afterwards until the next reboot.... FX