Create a symlink from /dev/dvd to /dev/sr2

[rrfish72]

Trying to get dvd to play and this is what I was informaed to do. How is this done? Here is my fstab:

# /etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
/dev/hda3 / ext3 defaults,errors=remount-ro 0 1

proc /proc proc defaults 0 0
/dev/fd0 /floppy vfat defaults,users,showexec,umask=022 0 0
usbdevfs /proc/bus/usb usbdevfs defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/sr0 /cdrom iso9660 defaults,users,noexec 0 0
/dev/cdrom1 /cdrom1 iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/sr2 /dvd iso9660 defaults,ro,users,noexec 0 0
/dev/cdaudio /cdaudio iso9660 defaults,ro,users,noexec,noauto 0 0
/dev/cdrom1 /mnt/auto/cdrom1 auto users,noauto,exec,ro 0 0
# Added by KNOPPIX
/dev/hda1 /mnt/hda1 ntfs noauto,users,exec,umask=000,uid=knoppix,gid=knoppi x 0 0
# Added by KNOPPIX
/dev/hda5 /mnt/hda5 ext2 users,exec 0 0


Is this set right? Any help in resolving this would be appreciated.

[Cuddles]

Trying to get dvd to play and this is what I was informaed to do. How is this done? Here is my fstab:

# /etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
/dev/hda3 / ext3 defaults,errors=remount-ro 0 1

proc /proc proc defaults 0 0
/dev/fd0 /floppy vfat defaults,users,showexec,umask=022 0 0
usbdevfs /proc/bus/usb usbdevfs defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/sr0 /cdrom iso9660 defaults,users,noexec 0 0
/dev/cdrom1 /cdrom1 iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/sr2 /dvd iso9660 defaults,ro,users,noexec 0 0
/dev/cdaudio /cdaudio iso9660 defaults,ro,users,noexec,noauto 0 0
/dev/cdrom1 /mnt/auto/cdrom1 auto users,noauto,exec,ro 0 0
# Added by KNOPPIX
/dev/hda1 /mnt/hda1 ntfs noauto,users,exec,umask=000,uid=knoppix,gid=knoppi x 0 0
# Added by KNOPPIX
/dev/hda5 /mnt/hda5 ext2 users,exec 0 0


Is this set right? Any help in resolving this would be appreciated.

Ouch! My fstab never looked like that, pointing to your sr0 and sr2 devices, that is...

First off, where is your sr1 device? Is sr1 symlink'ed to cdrom1, and why do you have two entries for /dev/cdrom1 - each one is pointing to a different mount point...

Here is what my fstab file looks like:

root@Morpheus:~# cat /etc/fstab
# /etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
/dev/hda5 / ext3 defaults,errors=remount-ro 0 1
/dev/hda6 /home auto defaults,auto 0 2
/dev/hda3 none swap defaults 0 0
usbdevfs /proc/bus/usb usbdevfs defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/hda1 /mnt/hda1 ext3 noauto,users,exec 0 0
proc /proc proc defaults 0 0
/dev/hdc1 /mnt/hdc1 vfat defaults,users,noauto,exec,umask=000 0 0
/dev/hdc2 /mnt/hdc2 ext3 defaults,users,noauto,exec 0 0
/dev/sda1 /mnt/sda1 vfat noauto,users,exec,noatime,umask=000 0 0
/dev/fd0 /floppy vfat defaults,user,noauto,showexec,umask=022 0 0
/dev/dvd /dvd iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/cdaudio /cdaudio iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/cdaudio1 /cdaudio1 iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/cdrom /cdrom iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/cdrom1 /cdrom1 iso9660 defaults,ro,user,noexec,noauto 0 0
root@Morpheus:~#

And I have symlinks for all my CDROM and DVD devices that "point" to my sr# devices...
Like so:

root@Morpheus:~# ls -la /dev/cdrom*
lrwxrwxrwx 1 root root 3 Jul 2 08:58 /dev/cdrom -> sr0
lrwxrwxrwx 1 root root 3 Jul 2 08:59 /dev/cdrom1 -> sr1
root@Morpheus:~# ls -la /dev/cdaudio*
lrwxrwxrwx 1 root root 3 Jul 2 08:57 /dev/cdaudio -> sr0
lrwxrwxrwx 1 root root 3 Aug 7 10:19 /dev/cdaudio1 -> sr1
root@Morpheus:~# ls -la /dev/dvd
lrwxrwxrwx 1 root root 3 Jul 2 08:57 /dev/dvd -> sr0
root@Morpheus:~#

to create a symlink, do the following, in a root Konsole screen:
ln -sf linkto linkfrom

Where "linkto" is the target for the link, and "linkfrom" is the source...

So if you wanted to create a symbolic link, that is "forced" ( i.e. if a link already exists, remove it, and make this one, for it ) -=- between /dev/dvd and /dev/sr0 - do the following:

ln -sf /dev/sr0 /dev/dvd

With the above, using /dev/dvd would ultimately point to the "real" device on /dev/sr0 - the "symlink" here would make a nicer way of knowing what "device" is actually represents - a dvd device -=- whereas, sr0 doesn't give much of a clue what the actual device is, by name.

Hope this helps,
Ms. Cuddles

[rrfish72]

Here is what I get :

root@3[knoppix]# ls -la /dev/dvd
lrwxrwxrwx 1 root root 10 Aug 6 02:05 /dev/dvd -> /dev/cdrom
root@3[knoppix]# ls -la /dev/sr0
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr0 -> scd0
root@3[knoppix]# ls -la /dev/sr1
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr1 -> scd1
root@3[knoppix]# ls -la /dev/sr2
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr2 -> scd2
root@3[knoppix]# ls -la /dev/cdrom1
ls: /dev/cdrom1: No such file or directory
root@3[knoppix]# ls -la /dev/cdrom
ls: /dev/cdrom: No such file or directory

That is how my fstab pretty much came. I changed the cdrom to sr0 and that made my cdrom work. I changed /dev/dvd/dvd to /dev/sr2/dvd and that did nothing for me. Now I'm trying to fix my dvd drive. It reads the dvd disc as files and won't play anything. I was wondering why I had 2 entries for the cdrom myself. So what do I need to change to get this to work?

[bradleyko]

sorryy to bother u guys in this topic but u seem very knowledagable about knoppix think u could help me with my problem please

[OErjan]

just inform us of the exact nature of your problem and we will try (more polite to do it in a new post but..)

[Cuddles]

Trying to get dvd to play and this is what I was informaed to do. How is this done? Here is my fstab:

# /etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
/dev/hda3 / ext3 defaults,errors=remount-ro 0 1

proc /proc proc defaults 0 0
/dev/fd0 /floppy vfat defaults,users,showexec,umask=022 0 0
usbdevfs /proc/bus/usb usbdevfs defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/sr0 /cdrom iso9660 defaults,users,noexec 0 0
/dev/cdrom1 /cdrom1 iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/sr2 /dvd iso9660 defaults,ro,users,noexec 0 0
/dev/cdaudio /cdaudio iso9660 defaults,ro,users,noexec,noauto 0 0
/dev/cdrom1 /mnt/auto/cdrom1 auto users,noauto,exec,ro 0 0
# Added by KNOPPIX
/dev/hda1 /mnt/hda1 ntfs noauto,users,exec,umask=000,uid=knoppix,gid=knoppi x 0 0
# Added by KNOPPIX
/dev/hda5 /mnt/hda5 ext2 users,exec 0 0


Is this set right? Any help in resolving this would be appreciated.

Hmm, I think a "re-vamp" is needed, considering your last post... I think the problem is, seeing your last post, you have /dev/dvd pointing to sr2, and /dev/cdrom pointing to sr0, but you have a symlink for /dev/dvd pointing to /dev/cdrom - thus, dvd is on sr2 but points to your cdrom device which is on sr0 - this is impossible.

Your sr# links are suposed to be linked to scd# devices - mine are the same way,

root@Morpheus:~# ls -la /dev/sr?
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr0 -> scd0
lrwxrwxrwx 1 root root 4 Aug 7 10:18 /dev/sr1 -> scd1
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr2 -> scd2
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr3 -> scd3
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr4 -> scd4
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr5 -> scd5
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr6 -> scd6
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr7 -> scd7
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr8 -> scd8
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr9 -> scd9
root@Morpheus:~#

sr0 -> scd0 -=- sr1 -> scd1 -=- etc... So these are fine... Leave your sr# links as they are...

Here is what I would do: ( do all of this in a root Konsole )

1 ) Do a "cd /dev" - so that you are in the dev directory / folder
2 ) Do a "umount /dev/device" on any mounted CD-ROM or DVD devices that are mounted. We are going to be changing some things, and don't want the devices mounted. So, if your DVD is mounted, you would want to do a "umount /dev/dvd" or something like that.
3 ) I am still not sure what device you have connected to sr1, your fstab file appears to be for only devices sr0 and sr2, but "sr" numbers usually are sequencial, so, either sr2 is actually sr1, or something that is on sr1 isn't being included in your fstab.
4 ) From what I can tell, from your fstab file, you have the following "mount points" -=- /cdrom /cdrom1 /dvd and lastly /cdaudio -=- if you do a "ls -la /" you should have these "mount points" as folders / directories off of the "/" ( root ) device.
5 ) From what I can tell, from your fstab file, you have the following devices going to these mount points -=- /cdrom = sr0 -=- /cdrom1 = unknown -=- /dvd = sr2 -=- and lastly, /cdaudio = unknown. Whichever device has the "audio cable" connected to your sound card, is usally setup as your /cdaudio device. In my case, my dvd has the audio cable to my sound card, so, my /cdaudio links to my sr0, and my /dvd links to my sr0.

First of all, we will only be "playing" with the fstab entries that are for your CD-ROM's and DVD devices, this is what you had:

/dev/sr0 /cdrom iso9660 defaults,users,noexec 0 0
/dev/cdrom1 /cdrom1 iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/sr2 /dvd iso9660 defaults,ro,users,noexec 0 0
/dev/cdaudio /cdaudio iso9660 defaults,ro,users,noexec,noauto 0 0
/dev/cdrom1 /mnt/auto/cdrom1 auto users,noauto,exec,ro 0 0


And this would be my suggestion:

/dev/cdrom /cdrom iso9660 defaults,users,noexec 0 0
/dev/cdrom1 /cdrom1 iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/dvd /dvd iso9660 defaults,ro,users,noexec 0 0
/dev/cdaudio /cdaudio iso9660 defaults,ro,users,noexec,noauto 0 0
# /dev/cdrom1 /mnt/auto/cdrom1 auto users,noauto,exec,ro 0 0 - commented out...


I would also check to make sure that you have the "mount point" folders in existance. You should have four folders in the / folder; dvd, cdrom, cdrom1, and cdaudio - if not, you will want to create these folders to hold the data/files/structure of there respective devices. You can do this with "mkdir [directoryname/foldername]" - so, if you don't have a /dvd folder, you would do the following in a root Konsole: mkdir /dvd

Now, you will want to create those symlinks, that appear not to exist in your /dev folder...

Going off what you have in your fstab, I can detect the entries for sr0 and sr2, but dont have a clue about sr1 - more input to determine what symlink that should be...

We need a symlink for all the devices you mentioned in your fstab file. So we need a link for /dev/cdrom, /dev/cdrom1, /dev/dvd, and lastly, /dev/cdaudio

So, still being in the /dev folder, in a root Konsole, we would do the following:

ln -sf sr0 /dev/cdrom
ln -sf sr2 /dev/dvd

If your sr1 is the entries for /cdrom1 and/or /cdaudio then you would create those symlinks like this:

ln -sf sr1 /dev/cdrom1
ln -sf sr1 /dev/cdaudio

If, on the other hand, your /cdrom1 and/or your /cdaudio are duplicates of either your /cdrom device or your /dvd device, then you would create the symlinks replacing the correct "sr#" in the above two commands.

If this gets your cdrom and dvd working as they should be, I would then, go back to your fstab file, and remove the "duplicate" entry that we commented out above. I prefer to test by commenting out something, and not just "out right" deleting something. That way, if something goes "funny", you can always go back and un-comment out, if need be.

So, after this, you should have the following symlinks:

/dev/sr0 -> scd0
/dev/sr2 -> scd2
/dev/dvd -> sr2
/dev/cdrom -> sr0
/dev/cdrom1 -> unsure of this device, and can't guess to where it should go...
/dev/cdaudio -> unsure of this device, and can't guess to where it should go...

As far as the device to mount points go, this will be the outcome:

/dev/dvd has a mount point of /dvd
/dev/cdrom has a mount point of /cdrom
/dev/cdrom1 has a mount point of /cdrom1
and lastly
/dev/cdaudio has a mount point of /cdaudio

Hopefully, this is a little more descriptive of your devices, and the folders where, when these devices are mounted, all make sense, and the symbolic links have nice descriptive names for the devices, instead of having to deal with sr#'s or scd#'s - :D

Hope this helps,
Ms. Cuddles

[rrfish72]

Now this is what I get when I try a cd:

Could not mount device.
The reported error was:
mount: Too many levels of symbolic links

And this for a dvd:

Could not mount device.
The reported error was:
mount: /dev/dvd is not a valid block device

I changed the icon to point to /dev/cdrom1 and it gives me a Play Files window with directories on one side and files on the other. What do I do there?

I changed the fstab:
/dev/cdrom /cdrom iso9660 defaults,users,noexec 0 0
/dev/cdrom1 /cdrom1 iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/dvd /dvd iso9660 defaults,ro,users,noexec 0 0
/dev/cdaudio /cdaudio iso9660 defaults,ro,users,noexec,noauto 0 0
#/dev/cdrom1 /mnt/auto/cdrom1 auto users,noauto,exec,ro 0 0

and did all the symlinks:
rwxrwxrwx 1 root root 9 Aug 8 14:19 /dev/sr0 -> /dev/scd0
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr1 -> scd1
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr2 -> scd2
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr3 -> scd3
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr4 -> scd4
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr5 -> scd5
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr6 -> scd6
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr7 -> scd7
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr8 -> scd8
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr9 -> scd9

The only thing funny I see is the sr0 entry. How do I change that?

[Cuddles]

Ok, I can see a few typo's, my mistake, in the fstab file:

change these two lines in your fstab file:

/dev/cdrom /cdrom iso9660 defaults,users,noexec 0 0
/dev/dvd /dvd iso9660 defaults,ro,users,noexec 0 0

to the following: ( we want the two devices to be noauto - so they don't automatically mount )

/dev/cdrom /cdrom iso9660 defaults,users,noexec,noauto 0 0
/dev/dvd /dvd iso9660 defaults,ro,users,noexec,noauto 0 0

ALSO, while you are changing the fstab file, make sure that your dvd, cdrom, and cdaudio entries have the ,noauto and also have ,users and ,ro in them - the "noauto" means that the device is not automatically mounted, the "ro" will only mount the device as Read-Only, and you want them all to be the same, using "users".

To get that funny sr0 symlink corrected, go into a root Konsole window, do a cd /dev, and then do the following:

ln -sf scd0 /dev/sr0

do me a favor, I need to get a complete picture of what is set, how it is set, and what you have...
After doing the above, copy and paste the following information into a reply here: ( run each command in a root Konsole window, and copy/paste the output of all the commands into a reply here. )

cat /etc/fstab
ls -la /dev/sr?
ls -la /dev/cdrom*
ls -la /dev/cdaudio*
ls -ls /dev/dvd*

I don't think you can "view" a dvd, you can "play" a dvd device, with a dvd in the device, but you can't open the dvd and look at the files - you can open a cd-rom device if it has data on the cd, but if it is a audio cd, you won't be able to "view" it, but will be able to "play" the audio cd. If the dvd device has a DATA CD in it, then you should be able to open and view the files, but not if it has a DVD in the device.

I use Xine, or Caffeine, to view/play dvd media, I use XMMS, or Caffeine, to play audio CD's, if my DVD or CD-ROM devices have a DATA CD in them, then I can open them to view the files.

I think we need to look at all the symlinks, with what you have in fstab, to find out about the errors you are getting - the symlink too many levels error has to mean that we have a long chain of symlinks for our access -=- which shouldn't be that many - we should have a symlink chain like such: /dvd/dvd -> /dev/sr2 -> /dev/scd2 -=- all your other cdrom devices should be "closely" the same length as this, which is not that long.

If you want to test the access of your dvd or cdrom devices, you should load a data cd into the device, and then you should be able to "mount" the device, and open the device to view the files. If you load a audio cd into either device, then you should use a program that plays audio cd's to access the device, and it should play the audio cd, like KsCD, Caffiene, or XMMS. If you load a DVD into the /dev/dvd device, you should use a program that plays DVD media to access the device, and it should play the DVD, like Xine, or Caffeine, etc...

The fstab file changes we are making are for access to DATA CD's in the cdrom and dvd devices - not for playing DVD's or playing AUDIO CD's - though I think the /dev/dvd and the /dev/cdaudio devices are used for the player programs to locate the "proper" devices from within the respective programs. i.e. a DVD player program will try and use the device /dvd when you ask it to play a dvd. Whereas, XMMS will look for /cdrom devices for audio.

For this testing, we should be using DATA CD's in both devices, since we are changing entries in the fstab file, if you have any "icons" on your desktop that "point" to the cdrom, cdaudio, or dvd devices, you should delete them, and make them new - icons store the mount point in them, and since the last edit we made did change some of those mount points, the icons would need to be changed to reflect those changes too. You can either delete the icons and make new ones, or, you can edit the "properties" of the icons and make sure that they are pointing to the correct "mount point".

I'll be waiting for the output of the information requested, and maybe we can get you running :D ( I know we can, it just is taking longer than I expected )

Ms. Cuddles

[rrfish72]

lrwxrwxrwx 1 root root 4 Aug 9 21:05 /dev/sr0 -> scd0
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr1 -> scd1
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr2 -> scd2
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr3 -> scd3
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr4 -> scd4
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr5 -> scd5
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr6 -> scd6
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr7 -> scd7
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr8 -> scd8
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr9 -> scd9

root@0[etc]# ls -la /dev/cdrom*
ls: /dev/cdrom*: No such file or directory
root@0[etc]# ls -la /dev/cdaudio*
lrwxrwxrwx 1 root root 3 Aug 8 20:27 /dev/cdaudio -> sr1
root@0[etc]# ls -ls /dev/dvd*
0 lrwxrwxrwx 1 root root 3 Aug 8 20:27 /dev/dvd -> sr2

After I did mkdir /dev/cdrom:

root@0[etc]# ls -la /dev/cdrom
total 40
drwxr-xr-x 2 root root 4096 Aug 9 21:12 .
drwxr-xr-x 13 root root 36864 Aug 9 21:12 ..

What is that?

I don't know if this is right, again.

And now this is what I get :

Could not mount device.
The reported error was:
mount: special device /dev/cdrom1 does not exist

Could not mount device.
The reported error was:
mount: /dev/dvd is not a valid block device

[Cuddles]

Ok, here is what we need to do:

Do the following in a root Konsole:

rmdir /dev/cdrom
mkdir /cdrom
mkdir /dvd
mkdir /cdaudio
mkdir /cdrom1

When you do the mkdir commands, you might get an error reporting that the "File exists", that is fine, I just want to make sure you have the Devices "Mount Points" folders existing.

Please -=- I need two pieces of information from you -=- One I asked for in my last posting, and it was not supplied, and the other, I have yet to find, or know, what they should link to... SO,

Please post the output of cat /etc/fstab - and lastly:

Please fill me in on the following devices should "ultimately" point to what sr#

dvd = sr2 ?
cdrom = sr0 ?
cdrom1 = ?
cdaudio = sr1 ?

Let me take a guess on your hardware... You have two CD-ROM devices, and a DVD device, in essense, sr0, sr1, and sr2 -=- am I right????? ( if so, then /dev/cdrom1 should point to sr1 -=- right ????? )

One last detail, when you are testing these devices, are you putting a DATA CD into the device to have it open with, or are you placing AUDIO or DVD discs into the device?

Ms. Cuddles

[rrfish72]

root@4[knoppix]# cat /etc/fstab
# /etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
/dev/hda3 / ext3 defaults,errors=remount-ro 0 1

proc /proc proc defaults 0 0
/dev/fd0 /floppy vfat defaults,users,showexec,umask=022 0 0
usbdevfs /proc/bus/usb usbdevfs defaults 0 0
sysfs /sys sysfs defaults 0 0


/dev/cdrom /cdrom iso9660 defaults,ro,users,noexec,noauto 0 0
/dev/cdrom1 /cdrom1 iso9660 defaults,ro,user,noexec,noauto 0 0
/dev/dvd /dvd iso9660 defaults,ro,users,noexec,noauto 0 0
/dev/cdaudio /cdaudio iso9660 defaults,ro,users,noexec,noauto 0 0
#/dev/cdrom1 /mnt/auto/cdrom1 auto users,noauto,exec,ro 0 0
# Added by KNOPPIX - took out noauto after ntfs
/dev/hda1 /mnt/hda1 ntfs users,exec,ro,umask=000,uid=knoppix,gid=knoppix 0 0
# Added by KNOPPIX
/dev/hda5 none swap defaults 0 0

I have a cd writer and a dvd rom drive. That's why it's so confusing to me because I don't know what the cdrom and cdrom1 are and which one is supposed to be the one I set up to use.

root@4[knoppix]# ls -la /dev/sr?
lrwxrwxrwx 1 root root 4 Aug 9 21:05 /dev/sr0 -> scd0
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr1 -> scd1
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr2 -> scd2
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr3 -> scd3
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr4 -> scd4
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr5 -> scd5
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr6 -> scd6
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr7 -> scd7
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr8 -> scd8
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr9 -> scd9

I beleive sr0 should be the cdrom which is the same as cdrom1.
sr1 should be the dvd rom drive.
That's all the drives except for my zip drive and my floppy. The zip drive I need, but that's another day.
I usually try the dvd drive with a dvd in itopens it and can see various files about the movie.
I try opening them but it gives me a Play Files window and I don't know what to do from there. I can play my backup music from cds saved as files but I can't play audio cds. I try both and get those error messages.

rrfish72

[Cuddles]

Ok, rrfish72,

I think we are getting closer, and by the way, thanks for the output of the fstab file...

Here is what I want to do:

First, I noticed one of your cdrom devices is using "user" - /dev/cdrom1 - can you change that entry to "users" ?

Second, can you check in your /etc/group file, and make sure all the user name accounts are on the line "users" -=- i.e. like this:


users:x:100:cuddles,raz


Make sure all your user name accounts are listed, like my two user account names are listed...

Third, reboot your system, and upon returning into your system, in a root Konsole, do the following:
root@Morpheus:~# dmesg

scroll up to near the top of the output, and locate where your hard drives and CD-ROM devices are being detected... They will say something like this:

hda: NameOfManufacturer ...
hdb: NameOfManufacturer ...
hdc: NameOfManufacturer ...
hdd: NameOfManufacturer ...

On your DVD and CD-ROM devices, it should say something about "passing xxx to SCSI emulation..." -=- and a little further down in your listing, you will see your DVD and CD-ROM devices listed again, but this time, it will be assigning them to SR#'s - this is the diffinitive solution for setting up your devices... If I think ( what I think ) is going on here, is, that we have interpretted your DVD as sr2, and I think its actually supposed to be sr1 - I think...

In my setup, my DVD is sr0, and my CD-RW is sr1 - since my audio cable is connected to my DVD device ( I wanted to be able to hear my DVD's through my sound card, and felt listening to CD-AUDIO discs though my re-writter was not that important ) I set my cdaudio to sr0 as well...

So, from my fstab file: ( also through looking at my "dmesg" output )

Hard Drive = hda
DVD = hdb -=- which is translated to sr0 ( SCSI emulation )
Hard Drive = hdc
CD-RW = hdd -=- which is translated to sr1 ( SCSI emulation )

Thus, this is how my devices are set-up:
DVD -> sr0
cdrom -> sr0
cdaudio -> sr0
cdrom1 -> sr1
cdaudio1 -> sr1

I think, if I am right, which you looking at your "dmesg" output will confirm, is:

cdrom = sr0
cdrom1 = sr1
DVD = sr1

Not sure where your audio cable is connect to, so I can't guess on where to put your /cdaudio device - it can be either your CD-RW or your DVD - but, if we get it wrong, it isn't that hard to change a symlink to the right device...

If I am right, the problem with your DVD is that we are trying to link it to the wrong sr# - but I want to be sure, before we proceed.. The reason why I want you to reboot before you do a "dmesg" is that, at least on my system, when I connect to the internet, I get a lot of "junk" that gets put into my system log file, and if I try to do a dmesg some time after booting and connecting to the internet, my screen floods with other messages that overflow what I really want to see, the boot stuff. ( not sure if your system does the same thing, so I am suggesting the reboot )

You can either post the "snippet" of dmesg that does the assigning of sr#'s in a new post, or you can just post your own type of this assignment - i.e. sr0 = "this" and sr1 = "this" and sr2 = "this" kind of thing... Also, if you know where your audio cable is connected to, that can help in setting up the cdaudio symlink as well...

I'll be waiting for your response,
Ms. Cuddles

[rrfish72]

Now my dvd drive is acting as my cdrom cdrom1 and cdaudio drive. I've followed all of what was instructed to do and I think I'm getting closer but need alittle more tweaking.

[Cuddles]

Now my dvd drive is acting as my cdrom cdrom1 and cdaudio drive. I've followed all of what was instructed to do and I think I'm getting closer but need alittle more tweaking.

RRFish72, I think you are thinking that Knoppix/Linux is going to do the same thing that Windows does... When you put any media in a CD-ROM, or DVD drive in Windows, Windows examines the media, and determines what "player" is to be used, and starts the "player" for you. Hence, if you put a CD-Audio disc in a CD-ROM drive, Windows will start a "audio CD player" for you, if its a DVD disc, in a DVD Drive, Windows will start you DVD Player, for you...

This is NOT the same in Linux, or Knoppix... You need to know what to start, and do it yourself... If you try to open, or mount anything other than a DATA CD, you will get errors on not being able to read, or mount, the disc... You need to open the right program depending on the type of media you put in the drive, Knoppix will not do it for you...

So, if you put a DATA CD in either your CD-ROM writter, or your DVD drive, you can mount it, or open it for reading, just like your hard drives -=- BUT, if the media inserted in either your WRITTER or DVD drive is AUDIO, you need to OPEN a CD PLAYER program to read the information, and play the disc; something like Kaffeine, XMMS, CD Player, etc... ( you do not open or mount the drive ) -=- This holds true with your DVD drive as well, if you put a DVD disc into your DVD drive, you do NOT open the drive, nor do you mount the drive, you use a PROGRAM that reads the disc that is made to play DVD's with...

When I put a AUDIO CD in my DVD or CD-RW device - I use XMMS, CD Player, or Kaffeine - and point them to the device that has the AUDIO CD in them, and play them using the program...

When I put a DVD in my DVD device - I use XINE, or Kaffeine - and point them to the DVD device, and play the DVD using the program...

When I put a DATA CD in either my CD-RW or DVD device - then I can open it through Konq., or mount it, and then view it, or use a COMMAND LINE WINDOW, and go to the mount point and view the data on the CD - but you can not do this with anything other than a DATA CD - doing this with a AUDIO or DVD disc, will only cause an error - because they are not DATA, but rather AUDIO or MOVIE discs...

As I suggested before: ( try the following )

*** Put a DATA CD in either drive, and try to mount / view them...

*** Put an AUDIO CD in either drive, and use XMMS to play them...

*** Put a DVD in your DVD drive, and use XINE or Kaffeine to play them...

and thell me what happens - Knoppix will NOT be able to OPEN or MOUNT "audio" or "dvd" discs in either drives - and will cause an error - this is normal... Maybe it isn't the same as Windows, but then again, Knoppix isn't Windows, so don't think its going to do the same thing as Windows does...

Ms. Cuddles

[rrfish72]

Now this is starting to bother me. When I put any kind of disc in the rom drive it tells me the device does not exist. When I try to play an audio cd with kaffeine or cd player or xmms none of them recognize the drive or can see the disc in the drive.

When I insert a dvd in the dvd drive it can open with konqueror and I see files that are about trying to install inter-actual video player but nothing about the movie. When I try to view with xine, it closes by inself in about 5 seconds, which I read is another issue that needs an update. With kaffeine the drive is not recognized and I cannot find anything about pointing to the drive to get it to read the movie.

I have another question about something I've been messing with. When I right click the cdrom icon to change what device it should point to, it seems as though when /dev/cdrom, /dev/cdrom1, or /dev/dvd are selected for those devices it gives me the error message of the device does not exist. When I choose /dev/cdaudio for any icon they seem to point only to the dvd drive. It still does not act like a dvd drive in the sense that I can't get it to play a movie. That is the time when it reads the files about installing the inter-actual video player.

I still am stumped and think there is something simple that is not being done. I hope you can still help me with this even though I think you've told me everything to do and how to do it.

[Cuddles]

RRFish72,

You are correct, if the DVD disc has DATA programs, like you said, Inter-Active Media Player, for playing the DVD in Windows, you will be able to "mount" the disc, and view it, the files that is...

A DVD movie, is just like an AUDIO CD, it is made up of individual files, that when played, link together to make the movie - in the case of an AUDIO CD, the "link" is the table of contents, which tells the Audio Player what songs are on the CD, what the names are, and the order in which they are to be played -=- on a DVD, basically the same thing, except the table of contents tells a DVD Player what "movie segments" are to be played and in which order - or "chapters".

Chances are, the icons that are on your desktop, can be wrong, if they were generated by Knoppix during the install - I always delete my ROM desktop icons, and make them brand new again. That way, they are correct, have the name I want, and have the right "mount point".

Xine and Kaffeine both use the same DVD libs, in fact, Kaffeine is a "off-shoot" of Xine, the same way that Knoppix is a "off-shoot" of Debian Sid. Xine and Kaffeine both need the dvdcss2 ( I think this is the right lib spelling ) to be able to play DVD's.

Xine and Kaffeine, when playing a DVD, will use the /dvd symlink, device, for playing a DVD

XMMS, CD Player, Xine, and Kaffeine, will try and use the /cdaudio symlink / device when playing a CD AUDIO disc, though XMMS can be "pointed" to the /cdrom and /cdrom1 devices as well. ( in XMMS, use the "Play Device" and change it to /cdaudio or /cdrom or /cdrom1 to get it to play other locations )

This all goes back to "two posts ago", when I said we need the output of dmesg - I think you will find you only have two sr#'s - sr0 and sr1 - one of them is your CD-RW, and the other wll be your DVD...

As I said before, the audio cable will determine which of the sr#'s should be /cdaudio, and /cdrom and /cdrom1 will point to each sr#, and the /dvd will point to the sr# of your DVD.

In my case, as I showed before, is what mine looks like:

DVD -> sr0
cdrom -> sr0
cdaudio -> sr0
cdrom1 -> sr1
cdaudio1 -> sr1

I made the /cdaudio1 link /device myself. With the above symlinks, on my system, you can see that both my DVD and CD-RW have a /cdrom device, my DVD is just /cdrom, and my CD-RW is /cdrom1 -=- my audio cable is connected from the DVD to my sound card, so it is set as my /cdaudio device. Technically, I can "mount" a data disc in ANY of these devices, I can also play an AUDIO CD using the /dvd device, if I can "point" the cd player program to a device ( like XMMS ).

The reason for all the devices, and names, is purely descriptive, and more for the understanding for the user, not the programs. Unless you are using Xine and Kaffeine, both these programs want to use the "nice named" devices. If you use Xine or Kaffeine to play a DVD, they will only look to the /dvd device, if you are playing a AUDIO CD, with these programs, they will only look to the /cdaudio device ( note that, in my case, I have a /cdaudio1 device, this device is never used, and both of these programs will not even see a device other than the /cdaudio one )

Lastly, you need to realize that these "devices" are simply symlinked devices, that "point" to there respective sr#'s, and in turn, point to there respective scd#'s -=- the "devices" are given "nice" names, so that you don't have to worry about what the "gut level" device is... e.g. scd0 = my DVD device, or sr0 = my DVD - /dvd and /cdaudio and cdrom all "point" to that same "low level" device, and are nicer names to use, and remember...

To Go Any Farther:
***** It would be nice to know what device ( CD-RW or DVD ) has your sound cards audio cable attached to it...
***** Determine exact device assignment through examining the output of dmesg...
***** Ensure ( from above ) that each device ( /cdaudio, /cdrom, /cdrom1, /dvd ) are symlinked properly ( i.e. /dvd -> sr0 -> scd0 ... /cdaudio -> ???? ... etc... )
***** Place data cd's in both devices, and ensure they both can be opened with newly created "desktop" icons...
***** Ensure that both devices can be mounted and viewed through a CLI ( Konsole )...
***** Place AUDIO CD's in both devices, and ensure that both can play the audio cd's through whatever CD Player program you want to use... ( xmms is good for this, because you can "point" it to each device, and then select play )
***** And, Lastly, place a DVD in the DVD device, and ensure that whatever DVD Plaer software program you want to use, can play the movie. ( if you haven't gotten the dvd lib yet, this will be needed for this test, by this time )

Realize, that these steps are not intended to "stall", or "delay" the completion of getting this working, but, rather, to ensure that when each "step" is completed, that we "build" on what has been worked out, and is working... If we went right after your DVD, and got it working, it may be at the cost of your CD-RW not working. ( I think your DVD is working, but you don't have the lib, and that is why Xine and Kaffeine are closing down )

I think the following have been completed:
symlink's
*** sr#'s to scd#'s - are OK
*** everything ( except /cdaudio - need to know the cable thing ) are linked correctly

I think you can "mount" data cd's in any of the devices, except /cdaudio ( see above )

I think you can "play" audio cd's in any of the devices, INCLUDING the /cdaudio -=- I would just like to be sure your /cdaudio device is really the right device with the audio cable

I think your DVD device is working, we just need the lib to be sure, ( I think this is the problem only right now )

-=- I think "everything" is working, and is linked correctly, excluding the /cdaudio device, and should be able to work - data cd's, audio cd's, and with the lib, the dvd device... But, I just want to make sure that you have it all working before I say - it's done...

You have already proven that you can get to your /dvd device, and able to view files on it, just can't play movies - hence the lib is needed... You might try a AUDIO CD in your /dvd device, and use XMMS to "point" to the /dvd device, and I think you will be able to play the audio cd in the device... You may be able to do the same thing with your /cdrom and /cdrom1 devices...

Be sure than in XMMS, you go into "options" and then "preferances", make the "tab" at the top set to "Audio I/O Plugins", and make sure that "CD Audio Player" has a check in the "Enable plugin" - then "Apply", "Ok"... Then go to the menu in XMMS, and "point" the "Play Location" to the device you have the audio cd in... like /dvd, or /cdrom, or /cdrom1 -=- to get into the XMMS menu, click the little "sound wave" in the upper left corner of the XMMS skin / interface...

I think you may find, the only thing not working, is the DVD player - and that may only be due to the missing lib for Xine or Kaffeine.

Ms. Cuddles

[Cuddles]

ONE MORE THING

If you mount, or open, any ROM device, be sure you un-mount, or umount, the device...

If you open your /dvd device for viewing in Konq., the /dvd. and any other device that is "linked" with that sr# - are "mounted" as a data cd - you want to make sure that all ROM devices are unloaded, if you want to "play" them -=- considering that Xine, Kaffeine, CD Player, and XMMS all mount the devices on there own, you don't want to have them mounted yourself...

This could be a reason why you are getting some errors... As for Kaffeine saying that no media, or no DVD is loaded in the device -=- I get that error a few times myself, and I never mount my dvd's, it can be something within Kaffeine that "detects" incorrectly, and just yells an error - falsely, that is... If I get that error, and I do have a dvd in the device, I just click "play dvd" again, and it works, usually... ( read: finicky program )

Maybe, this is paranoia, in the case of unmounting ROM devices, but, heck, I've never mounted a dvd while, or before, I was going to "play" it -=- I just put the DVD in the /dvd device, start up Kaffeine, select "play DVD" from the menu, and I'm watching the movie... when I am done watching, I push "stop", and remove my DVD movie from the device... At this time, I can either put another DVD in the drive, and go through the same "play DVD", or close down Kaffeine. Works about 99.9% of the time, the other 0.01% of the time, I get the /dvd device has no media error message, in which case, I just try "play DVD" again, and it usually works the second time...

As for an AUDIO CD, I never mount, or open, them either. Either before, while, or during, playing them. I just put an audio cd in the device, start up XMMS, or kaffeine, select the Play Location ( in the case of XMMS ) click OK, and then press PLAY - most of the time, in the case of XMMS, selecting a "Play Location", usually fires up "Play" on the audio cd for me, and I get music. Again, I have never "mounted" any of these devices, unless I was looking at a DATA CD - DVD and AUDIO CD's I just play them, and never mounted them, either before or during playing them.

Hopefully, this helps,
Ms. Cuddles

[rrfish72]

When I dmesg I do not get any info about my drives after I did an upgrade. It prints repeatedly 'JEDEC: found no ICH2 ROM device at location zero. ' Also goes to 1,2, and back to 0. I saw all the drive info before the upgrade, now I get nothing about the drive. I do get other details about the computer but not like it was before. This message also appears during the boot process into knoppix. See post:

http://www.knoppix.net/forum/viewtopic.php?t=12923

When I change both icons to cdaudio device they read from the dvd drive and can read data cds. 'ERROR: No plugin found to handle this resource' is the message kaffeine gives me when I try to play a dvd. This is because to the lib thing right?

When both icons point to the correct devices they do not work that way. I can not even read a data cd in either. I cant find the audio cable without the dmesg working right, is there any other way to do it. Could I see it by opening my computer?

[Cuddles]

When I dmesg I do not get any info about my drives after I did an upgrade. It prints repeatedly 'JEDEC: found no ICH2 ROM device at location zero. ' Also goes to 1,2, and back to 0. I saw all the drive info before the upgrade, now I get nothing about the drive. I do get other details about the computer but not like it was before. This message also appears during the boot process into knoppix. See post:

http://www.knoppix.net/forum/viewtopic.php?t=12923
No problem on dmesg output, I don't have a clue what JEDEC is, or what it does, never heard of it... I find nothing about "jedec" from either man or info, but, when I do a locate, it appears it is a form of driver, I find it in my Kernel Source tree, under /drivers/mtd/chips as jedec_probe... If I was going to take a guess on what it is, I might guess it was for JAZZ disc support... Not having a JAZZ drive on, or configured on, my system - it isn't loaded...

For an alternate way of finding your sr#'s - try the following: KMenu -> System -> Info Center -=- and click the SCSI on the left pane, see what shows up on the right side pane...


When I change both icons to cdaudio device they read from the dvd drive and can read data cds. 'ERROR: No plugin found to handle this resource' is the message kaffeine gives me when I try to play a dvd. This is because to the lib thing right?
I think the error is from the lib... /cdaudio must be symlinked to your /dvd device then... Your /dvd symlink should be pointing to the same sr# as your /cdaudio symlink ( you should check to make sure this is correct. )


When both icons point to the correct devices they do not work that way. I can not even read a data cd in either. I cant find the audio cable without the dmesg working right, is there any other way to do it. Could I see it by opening my computer?
Yes, best way to be sure where your audio cable is going from and to, is to "physically" look at it - not sure if there is a way to do this without doing this... You might want to shutdown your computer, power it off, open it up, and find the audio cable - if your sound card is on your motherboard, you will find a thin ( 4 wire ) cable from one of your ROM drives, and you should follow it to either your motherboard, or to a seperately mounted PCI card - which will have your sound card connections on the "Back Plane"...

Once you get your sr#'s from within Info Center, check the following, replacing the sr#'s for your devices for what I have shown...

/dvd -> sr0 -> scd0
/cdaudio -> sr0 -> scd0
/cdrom -> sr0 -> scd0
/cdrom1 -> sr1 -> scd1

Key:
"->" = symlink - check to ensure that the link exists, with a ls -la /dev/xxxx

You should have a symlink that points like this: from -> to, and the "from" should be in the form of: /dev/device - like: /dev/dvd

/dev/cdrom should point to sr0, which in turn, /dev/sr0 should point to scd0
/dev/cdrom1 should point to sr1, which in turn, /dev/sr1 should point to scd1

/dev/dvd should point to the correct /dev/sr# that Info Center says your dvd device is on...
/dev/cdaudio should point to the correct /dev/sr# that you find the "physical" audio cable going from to your sound card...

/cdrom and /cdrom1 always point to there respective sr#'s - this is a "standard"...

Once you determine your dvd and cdaudio devices, make those changes in your symlinks, also, enusre that your cdrom and cdrom1 devices are symlinked to there respective sr#'s... Then....

Post back the following output:
# ls -la /dev/sr*
# ls -la /dev/dvd
# ls -la /dev/cdaudio
# ls -la /dev/cdrom*

Check your fstab file entries for the above devices, and ensure that the "mount point" folders exist... as an example:

My DVD fstab file entry line shows my "mount point" to be /dvd
So do the following to make sure the folder exists for it:
# ls -la /dvd
the above command will either list out a directory listing, or show an error, like this:
ls: /xxx: No such file or directory
where "xxx" is what you had in the ls -la command...

If the folder doesn't exist, then make a note of it, and post back, with the other output above, that "this folder did not exist" - and we will be sure to create one for it, on the next steps.

After this, we will know the fstab file is done, we will be done with all the symlinks, everything should be pointing to there correct devices, and should work, unless you find some directories don't exist, in that case, mounting a device that doesn't have a directory for its mount point, will probably error. And if the lib thing isn't resolved, then trying to use Xine or Kaffeine to play a dvd will still have an error, as well.

If you have all the symlinks correct, and mount point directories are existing, and we still get device errors, even when trying to mount, or view, a ROM device, we may need to start "digging" a little deeper, possibly into permissions, and such. ( ? )

This should keep you a little busy for a while, and should give you a few things to check, resolve, change, and test - ( you might want to make a note of what device has the audio cable on it, for future referance, it doesn't hurt to know this info, later on, as well )

Ms. Cuddles

[rrfish72]

I believe the dvd is working correct now. I found out the the dvd drive is scsi1 which is sr1 and had to change all the links. That made me change the cdrom drive to sr0 which points to scd0, which the info told me that the cd writer(cdrom) is scd0. Now I can read data cds everytime with no problem but still no movies because of the missing plugin(lib thing). I cannot play audio cds though. I right click and select xmms and a play files screen opens and then I'm lost again. I try kaffeine and another error about no plugin to handle this resource.

By changing the sr#'s and having the cdrom point to sr0 --> scsi0 that should have made the drive able to read data cds anyway right. But it can't. When I try to mount or open it says 'Too many levels of symbollic links'.
Now this is the output of ls -la /dev/cdrom:

total 40
drwxr-xr-x 2 root root 4096 (date)(time) .
drwxr-xr-x 13 root root 36864 (date)(time) ..
1 root root 3 (date)(time) sr0 --> sr0

That output does not seem to be correct after seeing what the rest of the outputs were. It should have been /dev/cdrom --> sr0 like the output of /dev/cdrom1 --> sr1 which I beleive is correct. I even did ln -sf sr0 /dev/cdrom which after I did came back with the last line: 1 root root 3 (date)(time) sr0 --> sr0. I know it has to be /dev/cdrom --> sr0 doesn't it.

All the sr#'s pointed to the same #scsi. /dev/dvd went to sr2 which I changed to sr1. /dev/cdaudio went to sr1 which I left alone because of the audio cable thing which I didnt check yet but will soon.... /dev/cdrom* gave the above goofy output (I think it's goofy).
ls -la /dvd gave me a directory listing.

OTHER: I've download the lib thing and need help installing. It is sitting in my home directory and I think it is the right one. Any other way to do it like through apt-get.

[Cuddles]

I believe the dvd is working correct now. I found out the the dvd drive is scsi1 which is sr1 and had to change all the links. That made me change the cdrom drive to sr0 which points to scd0, which the info told me that the cd writer(cdrom) is scd0. Now I can read data cds everytime with no problem but still no movies because of the missing plugin(lib thing). I cannot play audio cds though. I right click and select xmms and a play files screen opens and then I'm lost again. I try kaffeine and another error about no plugin to handle this resource.

By changing the sr#'s and having the cdrom point to sr0 --> scsi0 that should have made the drive able to read data cds anyway right. But it can't. When I try to mount or open it says 'Too many levels of symbollic links'.
Now this is the output of ls -la /dev/cdrom:

total 40
drwxr-xr-x 2 root root 4096 (date)(time) .
drwxr-xr-x 13 root root 36864 (date)(time) ..
1 root root 3 (date)(time) sr0 --> sr0

That output does not seem to be correct after seeing what the rest of the outputs were. It should have been /dev/cdrom --> sr0 like the output of /dev/cdrom1 --> sr1 which I beleive is correct. I even did ln -sf sr0 /dev/cdrom which after I did came back with the last line: 1 root root 3 (date)(time) sr0 --> sr0. I know it has to be /dev/cdrom --> sr0 doesn't it.
To tell you the truth, I think you might have hit on "why /cdrom isn't working", with that ls -la /dev/cdrom output... First, you are right, the symlink should be /dev/cdrom -> sr0 -=- but, since you appear to ALSO have gotten a directory listing with the command, as well, my concern is that you might have a "directory" called /dev/cdrom, which is giving you that "too many symlinked" error... You should also check to be sure that you haven't inadvertantly set sr0 not to scd0, make sure that /dev/cdrom points to sr0, and that sr0 points to scd0...

As for that directory thing... Check to see that you don't have a "d... root root ... cdrom" inside /dev -=- I think this directory could have "accidently" been created during the whole fiasco with your ROM devices mount points... Check that your ROM entries in your fstab file are like the following:

DEVICE ___ MOUNT POINT
/dev/dvd = /dvd
/dev/cdaudio = /cdaudio
/dev/cdrom = /cdrom
/dev/cdrom1 = /cdrom1

If the above is true in your FSTAB file, then a /dev/cdrom directory is NOT supposed to exist, if you find a directory, named cdrom under the /dev folder, then you should rmdir /dev/cdrom from a root Konsole... Then make sure you still have the same output from a ls -la command on your /dev/cdrom as you do with /cdrom1 output. This should resolve the error you are getting from mounting your /cdrom device.


All the sr#'s pointed to the same #scsi. /dev/dvd went to sr2 which I changed to sr1. /dev/cdaudio went to sr1 which I left alone because of the audio cable thing which I didnt check yet but will soon.... /dev/cdrom* gave the above goofy output (I think it's goofy).
ls -la /dvd gave me a directory listing.
You are right, the output is "goofy", see above for possible correction...
The reason for the ls -la commands on your mount point directories, was to ensure that you have a directory existing for when you mount your device( s ). Looking at the above, example I gave for your fstab file ROM entries, each one of those "mount points" should have a directory existing, or when you mount the device, it will not have a place to put the files from the device in.


OTHER: I've download the lib thing and need help installing. It is sitting in my home directory and I think it is the right one. Any other way to do it like through apt-get.
Ah, here is the output text, I use it myself, and was given this from Stephen, as a resolve for that pesky dvd lib problem... ( note, that the original way to get the lib, was supposed to be able to be done through apt-get, but the site that holds the lib gives a message: "videolan... Site Not Found" - so apt-get won't work anymore... You need to get the lib another way, and then "force" the lib into Debian through dpkg... )

wget http://download.videolan.org/pub/libdvdcss/1.2.8/deb/libdvdcss2_1.2.8-1_i386.deb
dpkg -i libdvdcss2_1.2.8-1_i386.deb
You will want to do this in a root Konsole... This is the exact same lib that I have ALWAYS had a problem with in either Xine, or Kaffeine, when dealing with DVD playing. This is also the same version that I have running fine in my install as well...

Lastly, on playing any media, do not right click on the icon on the desktop for the device. Open up the player program, let's say its CD AUDIO, and you want to open XMMS. Once XMMS is open, left click on the "wave" symbol in the upper left corner of XMMS, select "Play Location", when the window for that pops up, either select the /cdrom or /cdrom1 in the drop-down box, or simply just type in /cdrom or /cdrom1 in the box, and then click on the OK. If its a DVD, then you will want to use either Xine, or Kaffeine, both of these programs "assume" the device is going to be /dvd by default - so don't right-click on the desktop icon for the device, start the player program ( Xine, or Kaffeine ), and select the device to be played - the option button for DVD in Xine, or in Kaffeine, select "Play" and follow that menu down till you get to the DVD menu item. I "never" right click and select a program the device should be played with, it can get you into trouble, as you have seen - let the player program do all the work for you...

I think the "end" is in sight, ... with the lib in place, you should be able to play DVD's, with the resolve of /dev/cdrom as a directory, you should be able to mount your /cdrom device, with the help with Xine, Kaffeine, and XMMS being started first, and letting them go to the device, I think you might have CD AUDIO playing and DVD playing working ... ( hopefully, if not, we will see what we need to do, if that is necessary )

Ms. Cuddles

[rrfish72]

Here is what I did:

root@1[knoppix]# cd ../..
root@1[/]# rmdir cdrom
root@1[/]# mkdir cdrom
root@1[/]# cd cdrom
root@1[cdrom]# dir
root@1[cdrom]# ln -sf sr0 /dev/cdrom
root@1[cdrom]# ls -la /dev/cdrom
total 40
drwxr-xr-x 2 root root 4096 Sep 2 22:12 .
drwxr-xr-x 13 root root 36864 Sep 2 22:09 ..
lrwxrwxrwx 1 root root 3 Sep 2 22:12 sr0 -> sr0

What else should be done?

After doing the lib thing the dvd finally can play dvds. Thank you so much. But now I can't paly audio cds with kaffiene and get these error messages:

The source can't be read.
Maybe you don't have enough rights for this, or source doesn't contain data (e.g: no disc in drive). (/dev/dvd) and in kaffiene window : Error: no plugin found to handle this resource.
Is this another lib thing?

[Cuddles]

...

root@1[/]# rmdir cdrom
root@1[/]# mkdir cdrom
root@1[/]# cd cdrom
root@1[cdrom]# dir
root@1[cdrom]# ln -sf sr0 /dev/cdrom
root@1[cdrom]# ls -la /dev/cdrom
total 40
drwxr-xr-x 2 root root 4096 Sep 2 22:12 .
drwxr-xr-x 13 root root 36864 Sep 2 22:09 ..
lrwxrwxrwx 1 root root 3 Sep 2 22:12 sr0 -> sr0

What else should be done?
Hmmmm,

All you did in that exercise of rmdir and mkdir, is put back the "same" thing, and you still have the sr0 pointing to sr0...

Here is what I would do...

root@xxx# cd /dev/cdrom
root@xxx[cdrom]# rm sr0
root@xxx[cdrom]# rm cdrom
root@xxx[cdrom]# cd /dev
root@xxx[dev]# rm sr0
root@xxx[dev]# rm cdrom
root@xxx[dev]# rmdir cdrom
root@xxx[dev]# ln -sf scd0 /dev/sr0
root@xxx[dev]# ln -sf cdrom /dev/sr0
root@xxx[dev]#

You have a /dev/cdrom directory, this is not proper, so I would delete all files, the symlink in the /dev/cdrom directory, it belongs in /dev, and no /dev/cdrom directory -=- So, in the above code sample; move to the /dev/cdrom directory, remove all files from that directory, move up one directory, then remove all symlinks that "point" or are "pointed to" /cdrom, remove the /dev/cdrom directory, and lastly, rebuild all the /dev/cdrom symlinks "in the /dev" directory.

This should take out the "directory listing" you get with a ls -la /dev/cdrom, and you should just get a symlink now...

Try XMMS for cd audio discs - Kaffeine for DVD's - for now - maybe its a setting in Kaffeine that isn't letting you play a audio cd - follow what I suggested for playing an audio cd in XMMS, a few posts ago - you want to be sure that the "plugin" for "CD Audio" is enabled in XMMS, and then change the "Play Location" to the device that has the audio cd in it...

I'll check back with ya, I'm currently under the "gun" at the moment at work, and don't have much time to work on this at the moment...

Ms. Cuddles

[rrfish72]

root@1[cdrom]# rm sr0
rm: cannot lstat `sr0': No such file or directory
root@1[cdrom]# rm cdrom
rm: remove symbolic link `cdrom'? y
root@1[cdrom]# cd /dev
root@1[dev]# rm sr0
rm: remove symbolic link `sr0'? y
root@1[dev]# rm cdrom
rm: cannot remove directory `cdrom': Is a directory
root@1[dev]# rmdir cdrom
root@1[dev]# ln -sf scd0 /dev/sr0
root@1[dev]# ln -sf cdrom /dev/sr0
root@1[dev]# ls -la /dev/cdrom
ls: /dev/cdrom: No such file or directory
root@1[dev]# cd
root@1[root]# cd
root@1[root]# ls -la /dev/cdrom
ls: /dev/cdrom: No such file or directory
root@1[root]# cd ..
root@1[/]# ls -la /dev/cdrom
ls: /dev/cdrom: No such file or directory
root@1[/]#

root@1[/]# ls -la /dev/sr*
lrwxrwxrwx 1 root root 5 Sep 3 10:42 /dev/sr0 -> cdrom
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr1 -> scd1
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr10 -> scd10
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr11 -> scd11
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr12 -> scd12
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr13 -> scd13
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr14 -> scd14
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr15 -> scd15
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr16 -> scd16
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr2 -> scd2
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr3 -> scd3
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr4 -> scd4
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr5 -> scd5
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr6 -> scd6
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr7 -> scd7
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr8 -> scd8
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr9 -> scd9

ln -sf scd0 /dev/sr0 gives
lrwxrwxrwx 1 root root 4 Sep 3 10:45 /dev/sr0 -> scd0
which is I thought what we wanted. Is there a link in there somewhere that is missing.

[Cuddles]

I think the following:

lrwxrwxrwx 1 root root 5 Sep 3 10:42 /dev/sr0 -> cdrom

is wrong - you need to have /dev/cdrom pointing to sr0 -=- in the above it is backwards, but, since you did the resymlink of sr0, you no longer have a symlink for cdrom...

Take a look at all the symlinks your have for /cdrom1 device, and make then the same for /cdrom, replacing the "1" for "0" (zero)... i.e. /dev/cdrom1 -> sr1 -=- /dev/cdrom should then point to sr0, etc...

From the output of what you were doing, I was correct, you DID have a /dev/cdrom directory, proven by when you did the "rmdir /cdrom" from within the /dev directory...

You should have the following output, when doing the stated commands:

root@Morpheus:~# ls -la /dev/scd?
brw-rw---- 1 root burning 11, 0 May 30 2001 /dev/scd0
brw-rw---- 1 root burning 11, 1 May 30 2001 /dev/scd1
brw-rw---- 1 root cdrom 11, 2 May 30 2001 /dev/scd2
brw-rw---- 1 root cdrom 11, 3 May 30 2001 /dev/scd3
brw-rw---- 1 root cdrom 11, 4 May 30 2001 /dev/scd4
brw-rw---- 1 root cdrom 11, 5 May 30 2001 /dev/scd5
brw-rw---- 1 root cdrom 11, 6 May 30 2001 /dev/scd6
brw-rw---- 1 root cdrom 11, 7 May 30 2001 /dev/scd7
brw-rw---- 1 root cdrom 11, 8 May 30 2001 /dev/scd8
brw-rw---- 1 root cdrom 11, 9 May 30 2001 /dev/scd9
root@Morpheus:~# ls -la /dev/sr?
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr0 -> scd0
lrwxrwxrwx 1 root root 4 Aug 7 10:18 /dev/sr1 -> scd1
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr2 -> scd2
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr3 -> scd3
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr4 -> scd4
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr5 -> scd5
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr6 -> scd6
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr7 -> scd7
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr8 -> scd8
lrwxrwxrwx 1 root root 4 Jul 2 07:02 /dev/sr9 -> scd9
root@Morpheus:~# ls -la /dev/cdrom*
lrwxrwxrwx 1 root root 3 Jul 2 08:58 /dev/cdrom -> sr0
lrwxrwxrwx 1 root root 3 Jul 2 08:59 /dev/cdrom1 -> sr1
root@Morpheus:~#


If not, make the needed changes to reflect what is not correct...
Ms. Cuddles
EDIT: hit the "submit" too fast,...

You might not have the "burning" group yet, unless you've run K3b, since it is used for your CD-RW, it creates the group "burning" during its setup program... You should also note that the permissions on my sr#'s and cdrom devices, are Owner=all access, Group=all access, and World / Other=all access... Two ways you can do this, ( 1 ) set up a special "group" like users and chgrp all the devices to that "users" group, set "group" permissions to "all", then remove any permissions for "World / Other", or, ( 2 ) the way I did, all have all access.

Number ( 2 ) is not the most secure way of setting permissions up, but I don't have "sensitive" data on my ROM drives, so an "attack" on my ROM devices is not severe... If on the other hand, you want more of a "secure" install, go with the idea in Number ( 1 )...
END EDIT

[rrfish72]

Totally confused again. Can you do a step by step please???? I did change sr0 to point to cdrom1 and when I try to mount or open a data disc I get : Could not mount device.
The reported error was:
mount: Too many levels of symbolic links

root@0[/]# ls -la /dev/cdrom1
lrwxrwxrwx 1 root root 3 Sep 3 12:28 /dev/cdrom1 -> sr0

root@0[/]# ls -la /dev/sr?
lrwxrwxrwx 1 root root 4 Sep 3 10:45 /dev/sr0 -> scd0
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr1 -> scd1
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr2 -> scd2
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr3 -> scd3
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr4 -> scd4
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr5 -> scd5
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr6 -> scd6
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr7 -> scd7
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr8 -> scd8
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr9 -> scd9

root@0[/]# ls -la /dev/scd?
lrwxrwxrwx 1 root root 4 Aug 8 20:17 /dev/scd0 -> scd0
brw-rw-rw- 1 root cdrom 11, 1 May 30 2001 /dev/scd1
brw-rw---- 1 root cdrom 11, 2 May 30 2001 /dev/scd2
brw-rw---- 1 root cdrom 11, 3 May 30 2001 /dev/scd3
brw-rw---- 1 root cdrom 11, 4 May 30 2001 /dev/scd4
brw-rw---- 1 root cdrom 11, 5 May 30 2001 /dev/scd5
brw-rw---- 1 root cdrom 11, 6 May 30 2001 /dev/scd6
brw-rw---- 1 root cdrom 11, 7 May 30 2001 /dev/scd7
brw-rw---- 1 root cdrom 11, 8 May 30 2001 /dev/scd8
brw-rw---- 1 root cdrom 11, 9 May 30 2001

Like I said... confused. Now I'm not sure what's pointing where.

Oh yeah, under the gun. Got a mental picture of that. Pretty bad.

[Cuddles]

Totally confused again. Can you do a step by step please???? I did change sr0 to point to cdrom1 ( <--- WRONG - you need /cdrom to point to sr0 ) and when I try to mount or open a data disc I get : Could not mount device.
The reported error was:
mount: Too many levels of symbolic links

root@0[/]# ls -la /dev/cdrom1
lrwxrwxrwx 1 root root 3 Sep 3 12:28 /dev/cdrom1 -> sr0 Nope

root@0[/]# ls -la /dev/sr?
lrwxrwxrwx 1 root root 4 Sep 3 10:45 /dev/sr0 -> scd0
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr1 -> scd1
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr2 -> scd2
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr3 -> scd3
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr4 -> scd4
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr5 -> scd5
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr6 -> scd6
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr7 -> scd7
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr8 -> scd8
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr9 -> scd9

root@0[/]# ls -la /dev/scd?
lrwxrwxrwx 1 root root 4 Aug 8 20:17 /dev/scd0 -> scd0 Nope
brw-rw-rw- 1 root cdrom 11, 1 May 30 2001 /dev/scd1
brw-rw---- 1 root cdrom 11, 2 May 30 2001 /dev/scd2
brw-rw---- 1 root cdrom 11, 3 May 30 2001 /dev/scd3
brw-rw---- 1 root cdrom 11, 4 May 30 2001 /dev/scd4
brw-rw---- 1 root cdrom 11, 5 May 30 2001 /dev/scd5
brw-rw---- 1 root cdrom 11, 6 May 30 2001 /dev/scd6
brw-rw---- 1 root cdrom 11, 7 May 30 2001 /dev/scd7
brw-rw---- 1 root cdrom 11, 8 May 30 2001 /dev/scd8
brw-rw---- 1 root cdrom 11, 9 May 30 2001 ???? did you just "clip" the output here???

Like I said... confused. Now I'm not sure what's pointing where.

Oh yeah, under the gun. Got a mental picture of that. Pretty bad.

Ok, from the output, here is what is wrong...
( 1 ) scd0 is now a symlink, it needs to look like /dev/scd1, but with a (zero) 0 ( scd0 is supposed to be a Block Device, designated by a b in the first position )
( 2 ) /dev/cdrom1 needs to point to sr1, not to sr0
( 3 ) you didn't provide the symlink output for /dev/cdrom, but it should be symlinked to sr0

Not sure how you would get your scd0 back, you might try a rm /dev/scd0, then a cp /dev/scd1 /dev/scd0 -=- not sure if this will work, you try it, and examine the output of ls -la /dev/scd? to see if scd0 is "like" scd1...

Then, examine the output of ls -la /dev/cdrom*, if /dev/cdrom is symlinked to sr0, leave that one alone... If /dev/cdrom1 is symlinked to sr0, you want to do a ln -sf sr1 /dev/cdrom1 - and another ls -la /dev/cdrom* should have /dev/cdrom pointing to sr0, and /dev/cdrom1 pointing to sr1.

Before doing anything more, at this point, lets re-check our outputs:

Post the output of the following:
ls -la /dev/scd?
ls -la /dev/sr?
ls -la /dev/cdrom*
ls -la /dev/dvd
ls -la /dev/cdaudio

Lastly, check if the "group" on scd0 is the same as the other scd# devices, it should be "cdrom" - I'll double check when I see your posted output of the above commands, if it isn't the right group, it isn't that hard to change it...

Ms. Cuddles

[rrfish72]

root@2[etc]# rm /dev/scd0
rm: remove symbolic link `/dev/scd0'? y

root@2[etc]# cp /dev/scd1 /dev/scd0

cp: reading `/dev/scd1': Input/output error

root@2[/]# cp /dev/scd1 /dev/scd0
cp: overwrite `/dev/scd0'? y
cp: reading `/dev/scd1': Input/output error

root@2[/]# ls -la /dev/scd?
-rw-r--r-- 1 root root 0 Sep 4 19:36 /dev/scd0
brw-rw-rw- 1 root cdrom 11, 1 May 30 2001 /dev/scd1
brw-rw---- 1 root cdrom 11, 2 May 30 2001 /dev/scd2
brw-rw---- 1 root cdrom 11, 3 May 30 2001 /dev/scd3
brw-rw---- 1 root cdrom 11, 4 May 30 2001 /dev/scd4
brw-rw---- 1 root cdrom 11, 5 May 30 2001 /dev/scd5
brw-rw---- 1 root cdrom 11, 6 May 30 2001 /dev/scd6
brw-rw---- 1 root cdrom 11, 7 May 30 2001 /dev/scd7
brw-rw---- 1 root cdrom 11, 8 May 30 2001 /dev/scd8
brw-rw---- 1 root cdrom 11, 9 May 30 2001 /dev/scd9
root@2[/]#

root@2[/]# ls -la /dev/sr?
lrwxrwxrwx 1 root root 4 Sep 3 10:45 /dev/sr0 -> scd0
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr1 -> scd1
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr2 -> scd2
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr3 -> scd3
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr4 -> scd4
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr5 -> scd5
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr6 -> scd6
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr7 -> scd7
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr8 -> scd8
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr9 -> scd9

root@2[/]# ls -la /dev/cdrom*
ls: /dev/cdrom*: No such file or directory

root@2[/]# ls -la /dev/dvd
lrwxrwxrwx 1 root root 3 Sep 1 20:38 /dev/dvd -> sr1

root@2[/]# ls -la /dev/cdaudio
lrwxrwxrwx 1 root root 3 Sep 1 21:07 /dev/cdaudio -> sr1

root@2[/]# ls -la /dev/cdrom1
ls: /dev/cdrom1: No such file or directory

No cdrom directory or cdrom. Here is what I did again:

root@2[/]# mkdir /dev/cdrom
root@2[/]# ln -sf sr0 /dev/cdrom
root@2[/]# mkdir /dev/cdrom1
root@2[/]# ln -sf sr1 /dev/cdrom1
root@2[/]# ls -la /dev/cdrom*
/dev/cdrom:
total 40
drwxr-xr-x 2 root root 4096 Sep 4 19:44 .
drwxr-xr-x 14 root root 36864 Sep 4 19:44 ..
lrwxrwxrwx 1 root root 3 Sep 4 19:44 sr0 -> sr0

/dev/cdrom1:
total 40
drwxr-xr-x 2 root root 4096 Sep 4 19:44 .
drwxr-xr-x 14 root root 36864 Sep 4 19:44 ..
lrwxrwxrwx 1 root root 3 Sep 4 19:44 sr1 -> sr1

root@2[dev]# ls -la /dev/cdrom?
total 40
drwxr-xr-x 2 root root 4096 Sep 4 19:44 .
drwxr-xr-x 14 root root 36864 Sep 4 19:53 ..
lrwxrwxrwx 1 root root 3 Sep 4 19:44 sr1 -> sr1
root@2[dev]# ls -la /dev/cdrom
total 40
drwxr-xr-x 2 root root 4096 Sep 4 19:54 .
drwxr-xr-x 14 root root 36864 Sep 4 19:53 ..
lrwxrwxrwx 1 root root 3 Sep 4 19:54 sr0 -> sr0

I know I'm trying to get the same output as this:

root@2[dev]# ls -la /dev/dvd
lrwxrwxrwx 1 root root 3 Sep 1 20:38 /dev/dvd -> sr1

Where the first sr# should be the /dev/cdrom or /dev/cdrom1. Is that correct to have these in there too:
drwxr-xr-x 2 root root 4096 Sep 4 19:54 .
drwxr-xr-x 14 root root 36864 Sep 4 19:53 ..

[Cuddles]

Ok, here is the problem, you keep creating directories for cdrom, under /dev - evident by my output:

root@Morpheus:/var/log# cd /etc
root@Morpheus:/etc# cd /dev
root@Morpheus:/dev# cd cdrom
bash: cd: cdrom: Not a directory
root@Morpheus:/dev# cd cdrom1
bash: cd: cdrom1: Not a directory
root@Morpheus:/dev# cd dvd
bash: cd: dvd: Not a directory
root@Morpheus:/dev# cd cdaudio
bash: cd: cdaudio: Not a directory
root@Morpheus:/dev#

If you do the exact same commands I have above, you will find, that you have a directory /dev/cdrom - and a /dev/cdrom1 -=- note in my above code, I don't have one, for either of these two.................

The copy of the scd1 to scd0 failed, and since I figured you didn't have a symlink for /dev/cdrom, I wasn't sure if you had a /dev/cdrom1 either, which I was expecting to create, after we got the scd0 block device right - we are now back where we started again - we have a broken scd0, we have a directory for /dev/cdrom and not a symlink, and now, we also have a /dev/cdrom1 directory instead of a symlink too..... :roll:

Here is what I suggest, rm the /dev/cdrom/cdrom and the /dev/cdrom1/cdrom1 - then rmdir the /dev/cdrom and the /dev/cdrom1 directories...............

Hopefully, someone else can give input on how you can create the scd0 block device, and remove the current /dev/scd0 you currently have... Then, I would suggest you do a ln -sf sr0 /dev/cdrom and a ln -sf sr1 /dev/cdrom1, but only after you can get the scd0 corrected...

( I need a vacation... )
Ms. Cuddles

[Markus]

Well, I think Cuddles is doing just fine here, but lets see it in a nutshell:

First list the scd's with:
ll /dev/scd[01]
Should look like:
root@fujibox:/dev# ll scd[01]
brw-rw-rw- 1 root cdrom 11, 0 Nov 14 2003 scd0
brw-rw-rw- 1 root cdrom 11, 1 Nov 14 2003 scd1

Remove the ones that aren't working:
rm /dev/scd0 /dev/scd1

Then create the missing devices:
mknod -m 666 /dev/scd0 b 11 0
mknod -m 666 /dev/scd1 b 11 1

Then remove the faulty symlinks:
rm /dev/cdrom /dev/cdrom1 /dev/dvd

Skip the sr? and do:
ln -s /dev/scd0 /dev/cdrom
ln -s /dev/scd1 /dev/cdrom1
ln -s /dev/scd1 /dev/dvd
Should look like:
root@fujibox:/dev# ll cdrom cdrom1 dvd
lrwxrwxrwx 1 root cdrom 9 Sep 5 14:18 cdrom -> /dev/scd0
lrwxrwxrwx 1 root cdrom 9 Apr 28 19:58 cdrom1 -> /dev/scd1
lrwxrwxrwx 1 root cdrom 9 Aug 10 13:53 dvd -> /dev/scd1

Recreate mountpoints just to be sure:
rmdir /cdrom /cdrom1 /dvd
mkdir /cdrom /cdrom1 /dvd

Change group to cdrom:
chgrp cdrom /dev/scd0 /dev/scd1 /dev/cdrom /dev/cdrom1 /dev/dvd /cdrom /cdrom1 /dvd

And use lines like these in fstab:
/dev/cdrom /cdrom iso9660 defaults,ro,users,noexec,noauto,uid=markus,gid=mar kus 0 0
/dev/cdrom1 /cdrom1 iso9660 defaults,ro,users,noexec,noauto,uid=markus,gid=mar kus 0 0
/dev/dvd /dvd iso9660 defaults,ro,users,noexec,noauto,uid=markus,gid=mar kus 0 0

[rrfish72]

Now this is what I get:

root@0[knoppix]# ll /dev/scd[01]
-rw-r--r-- 1 root root 0 Sep 4 19:36 /dev/scd0
brw-rw-rw- 1 root cdrom 11, 1 May 30 2001 /dev/scd1
root@0[knoppix]# rm /dev/scd0 /dev/scd1
rm: remove regular empty file `/dev/scd0'? y
rm: remove block special file `/dev/scd1'? y
root@0[knoppix]# mknod -m 666 /dev/scd0 b 11 0
root@0[knoppix]# mknod -m 666 /dev/scd1 b 11 1
root@0[knoppix]# rm /dev/cdrom /dev/cdrom1 /dev/dvd
rm: cannot remove directory `/dev/cdrom': Is a directory
rm: cannot remove directory `/dev/cdrom1': Is a directory
rm: remove symbolic link `/dev/dvd'? y
root@0[knoppix]# ln -s /dev/scd0 /dev/cdrom
root@0[knoppix]# ln -s /dev/scd1 /dev/cdrom1
root@0[knoppix]# ln -s /dev/scd1 /dev/dvd
root@0[knoppix]# ll cdrom cdrom1 dvd
ls: cdrom: No such file or directory
ls: cdrom1: No such file or directory
ls: dvd: No such file or directory
root@0[knoppix]# rmdir /cdrom /cdrom1 /dvd
root@0[knoppix]# mkdir /cdrom /cdrom1 /dvd
root@0[knoppix]# chgrp cdrom /dev/scd0 /dev/scd1 /dev/cdrom /dev/cdrom1 /dev/dvd /cdrom /cdrom1 /dvd
root@0[knoppix]# ll cdrom cdrom1 dvd
ls: cdrom: No such file or directory
ls: cdrom1: No such file or directory
ls: dvd: No such file or directory

root@0[/]# ls -la /dev/cdrom*
/dev/cdrom:
total 40
drwxr-xr-x 2 root cdrom 4096 Sep 5 06:58 .
drwxr-xr-x 14 root root 36864 Sep 5 06:59 ..
lrwxrwxrwx 1 root root 9 Sep 5 06:58 scd0 -> /dev/scd0
lrwxrwxrwx 1 root root 3 Sep 4 19:54 sr0 -> sr0

/dev/cdrom1:
total 40
drwxr-xr-x 2 root cdrom 4096 Sep 5 06:58 .
drwxr-xr-x 14 root root 36864 Sep 5 06:59 ..
lrwxrwxrwx 1 root root 9 Sep 5 06:58 scd1 -> /dev/scd1
lrwxrwxrwx 1 root root 3 Sep 4 19:44 sr1 -> sr1

I don't know what was done but I'll try it.

DVD drive still works right but cannot even read a data disc with cdwriter (cdrom).

[Markus]

rm -rf /dev/cdrom /dev/cdrom1
ln -s /dev/scd0 /dev/cdrom
ln -s /dev/scd1 /dev/cdrom1


root@0[knoppix]# ll cdrom cdrom1 dvd
ls: cdrom: No such file or directory
ls: cdrom1: No such file or directory
ls: dvd: No such file or directory Try ll /dev/cdrom /dev/cdrom1 /dev/dvd /cdrom /cdrom1 /dvd

If the dvd works don't touch it :)

[rrfish72]

root@2[knoppix]# rm -rf /dev/cdrom /dev/cdrom1
root@2[knoppix]# ln -s /dev/scd0 /dev/cdrom
root@2[knoppix]# ln -s /dev/scd1 /dev/cdrom1
root@2[knoppix]# ll /dev/cdrom /dev/cdrom1 /dev/dvd /cdrom /cdrom1 /dvd
lrwxrwxrwx 1 root root 9 Sep 5 09:51 /dev/cdrom -> /dev/scd0
lrwxrwxrwx 1 root root 9 Sep 5 09:51 /dev/cdrom1 -> /dev/scd1
lrwxrwxrwx 1 root cdrom 9 Sep 5 06:59 /dev/dvd -> /dev/scd1

/cdrom:
total 0

/cdrom1:
total 0

/dvd:
total 0

root@2[knoppix]# ls -la /dev/cdrom*
lrwxrwxrwx 1 root root 9 Sep 5 09:51 /dev/cdrom -> /dev/scd0
lrwxrwxrwx 1 root root 9 Sep 5 09:51 /dev/cdrom1 -> /dev/scd1

Why weren't the sr#'s needed? I see you bypassed that.

That's it. Everything works now. Thank you very much again for you help.

[Markus]

root@2[knoppix]# ll /dev/cdrom /dev/cdrom1 /dev/dvd /cdrom /cdrom1 /dvd
lrwxrwxrwx 1 root root 9 Sep 5 09:51 /dev/cdrom -> /dev/scd0
lrwxrwxrwx 1 root root 9 Sep 5 09:51 /dev/cdrom1 -> /dev/scd1
lrwxrwxrwx 1 root cdrom 9 Sep 5 06:59 /dev/dvd -> /dev/scd1

/cdrom:
total 0

/cdrom1:
total 0

/dvd:
total 0

root@2[knoppix]# ls -la /dev/cdrom*
lrwxrwxrwx 1 root root 9 Sep 5 09:51 /dev/cdrom -> /dev/scd0
lrwxrwxrwx 1 root root 9 Sep 5 09:51 /dev/cdrom1 -> /dev/scd1 Looking good.


Why weren't the sr#'s needed? I see you bypassed that. It was just another symlink causing cdrom->sr0->scd0 , no point in having sr0 in the middle when you can go cdrom->scd0


That's it. Everything works now. Thank you very much again for you help. No problem, and thank Cuddles instead for doing all the groundwork

[Cuddles]

Thx Markus for the assist, I was starting to see the "trees" individually, instead of the "forest"...

RRFish72 - Kewl to hear you got it "ALL" working now, funny that the install got it all wrong, in the first place - mine just needed a "small" amount of "tinkering" to get my devices working...

Ms. Cuddles

[Markus]

root@2[knoppix]# ll /dev/cdrom /dev/cdrom1 /dev/dvd /cdrom /cdrom1 /dvd
lrwxrwxrwx 1 root root 9 Sep 5 09:51 /dev/cdrom -> /dev/scd0
lrwxrwxrwx 1 root root 9 Sep 5 09:51 /dev/cdrom1 -> /dev/scd1
lrwxrwxrwx 1 root cdrom 9 Sep 5 06:59 /dev/dvd -> /dev/scd1

/cdrom:
total 0

/cdrom1:
total 0

/dvd:
total 0

root@2[knoppix]# ls -la /dev/cdrom*
lrwxrwxrwx 1 root root 9 Sep 5 09:51 /dev/cdrom -> /dev/scd0
lrwxrwxrwx 1 root root 9 Sep 5 09:51 /dev/cdrom1 -> /dev/scd1 Looking good. Hehe, I spoke too soon. The group is supposed to be cdrom, owner can be root. So this is still needed:
chgrp cdrom /dev/cdrom /dev/cdrom1
You should also check / with
cd /
ll
If needed do:
chgrp cdrom /cdrom /cdrom1 /dvd

[rrfish72]

root@0[zip]# chgrp cdrom /dev/cdrom /dev/cdrom1
chgrp: cannot access `/dev/cdrom': No such file or directory
chgrp: cannot access `/dev/cdrom1': No such file or directory
root@0[zip]# cd ../..
root@0[/]# chgrp cdrom /dev/cdrom /dev/cdrom1
chgrp: cannot access `/dev/cdrom': No such file or directory
chgrp: cannot access `/dev/cdrom1': No such file or directory
root@0[/]# cd dev
root@0[dev]# sudo chgrp cdrom /dev/cdrom /dev/cdrom1
chgrp: cannot access `/dev/cdrom': No such file or directory
chgrp: cannot access `/dev/cdrom1': No such file or directory
root@0[dev]# cd /
root@0[/]# ll
total 144
drwxr-xr-x 2 root root 4096 Sep 3 06:20 bin
drwxr-xr-x 3 root root 4096 Sep 5 01:48 boot
drwxr-xr-x 2 root root 4096 Aug 6 02:16 cdaudio
drwxr-xr-x 2 root cdrom 4096 Sep 5 06:59 cdrom
drwxr-xr-x 2 root cdrom 4096 Sep 5 06:59 cdrom1
drwxr-xr-x 12 root root 36864 Sep 5 16:46 dev
drwxr-xr-x 2 root cdrom 4096 Sep 5 06:59 dvd
drwxr-xr-x 151 root root 8192 Sep 5 16:52 etc
drwxr-xr-x 2 root root 4096 Apr 14 2001 floppy
drwxrwsr-x 4 root staff 4096 Sep 3 05:29 home
drwxr-xr-x 2 root root 4096 Apr 14 2001 initrd
drwxr-xr-x 9 root root 8192 Sep 3 06:24 lib
drwx------ 2 root root 16384 Aug 6 02:05 lost+found
-rw------- 1 root root 6291 Aug 6 02:34 mbox
drwxr-xr-x 18 root root 4096 Sep 3 10:49 mnt
drwxr-xr-x 2 root root 4096 Apr 6 20:20 none
drwxr-xr-x 3 root root 4096 Apr 18 07:35 opt
dr-xr-xr-x 89 root root 0 Sep 5 12:45 proc
drwxr-xr-x 13 root root 4096 Sep 5 10:07 root
drwxr-xr-x 2 root root 8192 Sep 3 06:24 sbin
drwxr-xr-x 8 root root 0 Sep 5 12:45 sys
lrwxrwxrwx 1 root root 8 Aug 6 02:07 tmp -> /var/tmp
drwxr-xr-x 15 root root 4096 Feb 29 2004 usr
drwxr-xr-x 16 root root 4096 Jan 26 2004 var
lrwxrwxrwx 1 root root 13 Aug 6 02:17 vmlinuz -> /boot/vmlinuz
root@0[/]# ls -la /dev/cdrom*
ls: /dev/cdrom*: No such file or directory

I guess so. Now the cd writer does not work again. What happened after a reboot.

[Markus]

root@0[/]# ls -la /dev/cdrom*
ls: /dev/cdrom*: No such file or directory

I guess so. Now the cd writer does not work again. What happened after a reboot. What the.... did you do a knoppix or beginner style install which overwrites the devices on a reboot?
BTW, your / is fine.
I'm at work now, I'll look into it after getting home, unless someone has a fix for recreation of the removable devices.

[rrfish72]

I did a knopix style. Why is that important?

[Cuddles]

Markus,

I am going to guess that the etc/fstab needs to be changed, and then all the symlinks, again...

Unless, you know how to disable the autoconfig thing, or get his autoconfig to re-create it all correctly each time... ( ? )

Ms. Cuddles

[Cuddles]

As a matter of information, RRFish72, with the new Knoppix v3.4, the installer has more options, than just the "usual" Debian Style...

Beginner and Knoppix Style installs, are "basically" the same as the "Debian Style", except that they still do the "autoconfiguration" that the Live CD does, each time you boot... Whereas, the "Debian Style" install, does an "autoconfiguration" once, during the install, and then leaves everything alone after that...

The reason why it "makes a differance" which install you used, is for the exact same reason you don't have everything you had setup before your reboot, and after the reboot, everything seems to have been "re-done" again, and this now explains why when I first started to work with you on this whole thing, why everything was so "weird" compared to what I have. With the Beginner and Knoppix Style installs, you are still doing an autoconfiguration of your devices every time you reboot. Some things are "sticking" after you reboot, but, some things are not, like the etc/fstab file entries, and your symlinks for your devices.

Even with the Debian Style install, which I have, you still can have "some things" replace on a reboot, but, in my case, the fstab file and my symlinks, do not get overwritten every time I reboot...

Thats all,
Ms. Cuddles
PS -=- I knew the new installer options were gonna come-round and bite us in the rear, having more options, especially ones that are not explained what they do, or how they work, can end up to cause situations like this...

[Markus]

Oh well, installing Knoppix style does explain this mess as Cuddles noted. Let's see if we can find a solution other than reinstalling debian style.
The first thing to do is add nofstab to the "append" line in /etc/lilo.conf and after saving the file make sure to run lilo as root by typing lilo -v or /sbin/lilo -v . It should say something like Added Linux, Added Windows. This will keep you fstab intact after a reboot.
Now is the time to recreate the symlinks and check that /dev/cdrom, /dev/cdrom1, /dev/dvd, /cdrom, /cdrom1 and /dvd still exist, and tell us what exists and what doesn't.
Not sure about the autoconfig script as I haven't even seen the new knoppix version let alone done a knoppix style install. If you want to take a shot at it, it's at /etc/init.d/knoppix-autoconfig. While looking at the version in Kanotix BH5 I would start at commenting out with a # the following:
AUTOMOUNTS="floppy cdrom"
# Add new devices to /etc/fstab and /etc/auto.mnt
for i in /dev/cdrom?*; do
if [ -L $i ]; then
addautomount "$i" "ro"
fi
done
NB: You should know how to restore it if you're going to edit knoppix-autoconfig.

You could perhaps try a short script and have it start with a high Snumber like 99.
Say you created a script called fixdrives with the following content:

#!/bin/sh
rm -rf /dev/cdrom /dev/cdrom1 /dev/dvd
ln -s /dev/scd0 /dev/cdrom
ln -s /dev/scd1 /dev/cdrom1
ln -s /dev/scd1 /dev/dvd
chmod 770 /dev/cdrom /dev/cdrom1 /dev/dvd
chgrp cdrom /dev/cdrom /dev/cdrom1 /dev/dvd

Place it in /etc/init.d and do a chmod 700 /etc/init.d/fixdrives , then do (including the dot at the end): update-rc.d fixdrives start 99 5 .

Although it might be easier to just add it to the end of /etc/init.d/bootmisc.sh , not the #!bin/sh line though

PS: This is probably also the reason why you're ZIPdrive isn't working. We had it working and lost it probably after a reboot.
I wish people would install debian style unless they need autodetection :)


PS -=- I knew the new installer options were gonna come-round and bite us in the rear, having more options, especially ones that are not explained what they do, or how they work, can end up to cause situations like this... Well said!

[rrfish72]

Got the nofstab in lilo and ran lilo -v. Don't know how to restore the file. Just know how to comment things out and uncommment them. Will that work. Want to know before I change things. Should I just go ahead and add this to init.d/bootmisc.sh?

[Cuddles]

RRFish72,

Maybe you can post what your /etc/fstab file looks like now, with that nofstab entry in LILO, that should allow changes to "stick" now...

The bootmisc.sh script file sounds good, place it down at the bottom, and put a few comments with it, so later, when this all fades away, you will know why, and what it is doing...

For the time being, put the lines at the bottom of the bootmisc.sh file, and comment them out, until we can figure out how bad the fstab file is... ( also, you might try to change the /etc/fstab file and the bootmisc.sh file, like add a comment at the bottom of them, save them, and then reboot - just to check that the files aren't being "re-created" after you reboot, like the fstab file was doing )

Ms. Cuddles

[rrfish72]

Here is the fstab:

# /etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
/dev/hda3 / ext3 defaults,errors=remount-ro 0 1

proc /proc proc defaults 0 0
/dev/fd0 /floppy vfat defaults,users,showexec,umask=022 0 0
usbdevfs /proc/bus/usb usbdevfs defaults 0 0
sysfs /sys sysfs defaults 0 0

/dev/sda4 /mnt/zip vfat defaults,noauto,users,noatime,umask=000 0 0
/dev/cdrom /cdrom iso9660 defaults,ro,users,noexec,noauto,uid=knoppix,gid=kn oppix 0 0
/dev/cdrom1 /cdrom1 iso9660 defaults,ro,users,noexec,noauto,uid=knoppix,gid=kn oppix 0 0
/dev/dvd /dvd iso9660 defaults,ro,users,noexec,noauto,uid=knoppix,gid=kn oppix 0 0
/dev/cdaudio /cdaudio iso9660 defaults,ro,users,noexec,noauto 0 0
#/dev/cdrom1 /mnt/auto/cdrom1 auto users,noauto,exec,ro 0 0
# Added by KNOPPIX - took out noauto after ntfs and added auto after exec and ro after exec
/dev/hda1 /mnt/hda1 ntfs users,exec,auto,umask=000,uid=knoppix,gid=knoppix 0 0
# Added by KNOPPIX
/dev/hda5 none swap defaults 0 0


This is what was added before to help my zip drive work properly and it looks like things are not being changed back to the originl or recreated again. These are just a few lines at the end:

if [ "$EDITMOTD" != no ]
then
uname -a > /etc/motd.tmp
sed 1d /etc/motd >> /etc/motd.tmp
mv /etc/motd.tmp /etc/motd
fi

#
# Save kernel messages in /var/log/dmesg
#
dmesg > /var/log/dmesg
#This was added by rrfish72
modprobe imm
insmod usb-storage

But I added this to it anyway and will try the chmod 700 /etc/init.d/fixdrives and update-rc.d fixdrives start 99 5 . after a reply back to see if this is what should be done.

#Added for a test
#rm -rf /dev/cdrom /dev/cdrom1 /dev/dvd
#ln -s /dev/scd0 /dev/cdrom
#ln -s /dev/scd1 /dev/cdrom1
#ln -s /dev/scd1 /dev/dvd
#chmod 770 /dev/cdrom /dev/cdrom1 /dev/dvd
#chgrp cdrom /dev/cdrom /dev/cdrom1 /dev/dvd

Uncomment out, run ( chmod 700 /etc/init.d/fixdrives and update-rc.d fixdrives start 99 5 .) . Is that correct?

What is this line for?: #!/bin/sh Is that # supposed to be the 99 thing Markus was talking about?

All of my icons stay to what I set them at through code: 'chmod 0 /usr/bin/mkdesktophdicons'

[Cuddles]

RRFish72,

What Markus was suggesting was two possible ways to do the fix, one was to create a file, called fixdrives, and place the following in it:

#!/bin/sh
rm -rf /dev/cdrom /dev/cdrom1 /dev/dvd
ln -s /dev/scd0 /dev/cdrom
ln -s /dev/scd1 /dev/cdrom1
ln -s /dev/scd1 /dev/dvd
chmod 770 /dev/cdrom /dev/cdrom1 /dev/dvd
chgrp cdrom /dev/cdrom /dev/cdrom1 /dev/dvd

and then, do the following:

Place it in /etc/init.d and do a chmod 700 /etc/init.d/fixdrives , then do (including the dot at the end): update-rc.d fixdrives start 99 5 .

Although it might be easier to just add it to the end of /etc/init.d/bootmisc.sh , not the #!bin/sh line though

But, as Markus said in that last line, you could simply just add the following code:

rm -rf /dev/cdrom /dev/cdrom1 /dev/dvd
ln -s /dev/scd0 /dev/cdrom
ln -s /dev/scd1 /dev/cdrom1
ln -s /dev/scd1 /dev/dvd
chmod 770 /dev/cdrom /dev/cdrom1 /dev/dvd
chgrp cdrom /dev/cdrom /dev/cdrom1 /dev/dvd

within your bootmisc.sh file, at the bottom. If you wanted to create the file, then you would have put the line: #!/bin/sh at the top of that file, it tells Knoppix that the file is a script, you would have needed to change the file to executable, and then would have needed to place the file in the boot up init.d -=- but we opted to just put the commands in the /etc/init.d/bottmisc.sh file - so you don't need the #!/bin/sh now, nor do you need to do a change on the file we didn't use, or need to add it into the init.d

Since you ensured that your bootmisc.sh file isn't being recreated, nor is your fstab file, I think you can uncomment those lines in your bootmisc.sh file now, and try a reboot... First test you should do, upon completion of your reboot, is to test to see that your symlinks exist for your devices -=- within any Konsole, user or root, ls -la /dev/cdrom* /dev/dvd /dev/cdaudio

If all goes well, you should have symlinks for all the devices, your fstab file should remain intact, and the above devices should work... ( again )

Ms. Cuddles

[rrfish72]

Something is happening to that to not get it to stick. The changes made to the dvd drive stuck. Now if I ln -sf /dev/scd0 /dev/cdrom then the drive plays all discs. But that has to be done everytime I want to use the drive after a bootup. This is the output:

root@0[knoppix]# ls -la /dev/cdrom* /dev/dvd /dev/cdaudio
ls: /dev/cdrom*: No such file or directory
lrwxrwxrwx 1 root root 3 Sep 1 21:07 /dev/cdaudio -> sr1
lrwxrwxrwx 1 root cdrom 9 Sep 5 06:59 /dev/dvd -> /dev/scd1

root@0[knoppix]# ls -la /dev/sr*
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr1 -> scd1
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr10 -> scd10
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr11 -> scd11
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr12 -> scd12
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr13 -> scd13
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr14 -> scd14
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr15 -> scd15
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr16 -> scd16
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr2 -> scd2
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr3 -> scd3
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr4 -> scd4
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr5 -> scd5
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr6 -> scd6
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr7 -> scd7
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr8 -> scd8
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr9 -> scd9

root@0[knoppix]# ln -sf /dev/scd0 /dev/cdrom
root@0[knoppix]# ls -la /dev/cdrom
lrwxrwxrwx 1 root root 9 Sep 10 08:54 /dev/cdrom -> /dev/scd0

Now the drive works. How to get the changes to stay in place in the question now?

[Markus]

Let's try a different approach and hope that knoppix doesn't notice it, if /dev/cdrom is being recreated all the time, try naming it /dev/cddrive instead.
Comment out this line in fstab: /dev/cdrom /cdrom iso9660 defaults,ro,users,noexec,noauto,uid=knoppix,gid=kn oppix 0 0
Add this line to it: /dev/cddrive /cdrom iso9660 defaults,ro,users,noexec,noauto,uid=knoppix,gid=kn oppix 0 0

Then do:
ln -s /dev/scd0 /dev/cddrive
chgrp cdrom /dev/cddrive

Now, hopefully you'll have the symlink intact after a reboot, check with:
ll /dev/cddrive

[rrfish72]

Hate to tell you this but I just reinstalled debian style and did alitte work and now everything works. I just couldn't wait any longer. Thanks for all the help you gave.

[Markus]

No need to feel sorry about that, wise decision IMHO.

[Cuddles]

Hate to tell you this but I just reinstalled debian style and did alitte work and now everything works. I just couldn't wait any longer. Thanks for all the help you gave.

I agree with Markus, sometimes I wonder why they gave so many options when you run the installer - it has only been to the confusion of the user, and, in your case, not being able to do what you should be able to do, and that is, use your computer system and the hardware that is installed on it...

Just as a mental note RRFish72 -=- I found this out myself - if you are using the "experimental" kernel 2.6.6, you can not change the "modules" file, it gets "re-created" during a re-boot - if you need to add some module during boot, you will want to change the "modules-2.6.6" file instead... ( if you are using Knoppix v3.4 - since they have two kernels on that version, they used this method to keep the kernel files seperate, just letting you know what I found out, the hard way :D )

Glad to see you are running good now :), and sorry that it had to take doing a re-install :(,
Ms. Cuddles
EDIT: changed some typos I made, and...
ADDED: Didn't realize that you had another thread on your ZIP Drive, you might find that my entry in this posting, on the "modules" file, may be of concern, if you are going to be adding any modules into your newly re-installed Knoppix...
END ADDED
END EDIT