LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Cant eject cdrom after slackware-current update (http://www.linuxquestions.org/questions/slackware-14/cant-eject-cdrom-after-slackware-current-update-93725/)

windsok 09-17-2003 06:13 AM

Cant eject cdrom after slackware-current update
 
i updated to slackware-current with swaret and now i cant seem to eject my cdrom, i unmount it and press the eject button and nothing happens.

this doesnt work either:

root@windsok:/# eject /dev/cdrom
eject: unable to eject, last error: Invalid argument

root@windsok:/var/swaret# eject -r /dev/cdrom
eject: unable to eject, last error: Device or resource busy

I can mount the cdrom and read the contents fine though, i just want to be able to change the cd in there! :cry:

Another problem is i cant figure out what device my dvd-rw drive is, how would i go about figuring this out?

thanks alot

linuxJaver 09-17-2003 07:43 AM

I've also problem with the cdrom since upgraded to the slackware current. Here below are the screen output :

[root@tx97e:/mnt]$ mount -t iso9660 /dev/cdrom /mnt/cdrom
mount: /dev/cdrom is not a valid block device
[root@tx97e:/mnt]$ mount -t iso9660 /dev/hdc /mnt/cdrom
mount: /dev/hdc is not a valid block device
[root@tx97e:/mnt]$ eject
eject: unable to eject, last error: Inappropriate ioctl for device
[root@tx97e:/mnt]$ eject /dev/cdrom
eject: unable to find or open device for: `/dev/cdrom'
[root@tx97e:/mnt]$ eject /dev/hdc
eject: unable to find or open device for: `/dev/hdc'

After lots of reading in /usr/doc/Linux-HOWTO/CDROM-HOWTO, I speculate the problem could be laid on the kernel. I installed the downloaded slackware-current from the mounted slackware.iso.

This has a little bit problem that at the end of the installation, no possibility is given for choosing which kernel to install as boot-kernel compared to installing directly from a burnt-CD. The only option is to install that kernel from the boot diskett (bare.ide ..). As this must be a very minim featured and highly hardware compatibile kernel, therefore it can not be expected too ( as said, only my speculation ..).

Possible solution:
Copy the desired kernel from a mounted slackware.iso, put in /boot, adjust lilo to boot the choosed kernel ..

Gonna test it later. My slackware.iso is moved to a ntfs partition. That can not be mounted (another problem) as like:

mount -o loop -t iso9660 /dev/ntfs1/slackware.iso /mnt/adir
(/dev/ntfs1 premounted)

=> I must boot into other kernel/release/distro/windows to gain access to the other kernels ..

linuxJaver 09-18-2003 10:52 PM

Oo, it was a mistake from me ..
I just read from the dmesg output that my cdrom was attached on hdd:

[root@tx97e:~/etc]$ dmesg | grep cdrom
hdd: attached ide-cdrom driver.

Tried mount -t iso9660 /dev/hdd /mnt/cdrom now working ..
:)

BearClaw 09-19-2003 05:30 AM

Try this: ls -l /dev/cdrom and ls -l /dev/scd0. I had the same problem after a few different current updates.

After entering the commands listed above, it turned out that I did not have permission to execute the cdrom dev. I then did:
#chmod 777 /dev/scd0 (or whatever is correct for you) and all was functional after that. Some of the current-updates change your config and/or permissions, so be aware, even on your security settings.

Good luck, BC


All times are GMT -5. The time now is 06:24 AM.