I can't access my CD-R. It's not showing up on the desktop but when I look at the Control Center/Index Tab/Information/Available Hardware it's showing up under CD-ROM like this:
CD-ROM
-MAT****ADVDROM SR-8586
-_NEC NR-7700A
The second one, NEC NR 7700A, is my CD-R. Does the OS think that both drives are one? Anyone know how to fix this?
muchas gracias,
nosmokey :)
BigFatJoe
01-16-2003, 01:26 AM
Is this scsi or ide/atapi? I'm assuming the computer/bios is recognizing the cdrom - check with "dmesg | less". If it is, then you may have a problem with scsi emulation. Or maybe its not trying to mount it correctly. Checking /etc/fstab and trying to mount it manually (through the terminal) are both good ideas. Then you can try to figure out any errors. Post those back, and we may be able to help. I'm not sure if you know, but one cannot mount audio cd's - try mounting instead with a data cd. Since you gave us little information, I'm just kicking around some ideas.
nosmokey
01-16-2003, 01:44 AM
Thanks for your reply.
Is this scsi or ide/atapi?
I don't know what this means.
check with "dmesg | less"
Hope I did this correctly...
VFS: Mounted root (ext2 filesystem) readonly.
Trying to move old root to /initrd ... okay
Freeing unused kernel memory: 152k freed
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
loopc: loaded (max 16 devices)
loopc: lc_init loopc0
loopc: fs block size: 2048
loopc: read buffer holds 8 fs blocks
loopc: uncompressed size 1660352k: 103772 blocks, block size 16384
loopc: 1622 chunks (64 blocks/chunk)
ISO 9660 Extensions: RRIP_1991A
scsi : 0 hosts left.
ieee1394: Host removed: Node[00:1023] GUID[00053f5105001297] [Linux OHCI-1394]
usb.c: deregistering driver hiddev
usb.c: deregistering driver hid
usb.c: USB disconnect on device 1
usb.c: USB disconnect on device 2
usb.c: USB bus 1 deregistered
usb.c: USB disconnect on device 1
usb.c: USB bus 2 deregistered
I tried the /etc/fstab and it said Permission denied
BigFatJoe
01-16-2003, 02:02 AM
Originally posted by nosmokey
I don't know what this means.
<snip>
Hope I did this correctly...
<snip>
I tried the /etc/fstab and it said Permission denied
1. if you don't know, I'll bet you have ide/atapi (they're pretty much standard for desktops, because they're cheaper)
; )
2. if you try "dmesg" all of the information that is displayed during boot will scroll by. the idea of "less" is to feed the output (that just scrolled by) to something you can manage. ie. what this is does, is shows a page at a time. so what you want to do is use the down arrow to scroll through the information until you get anything about your cdroms. Post that part back.
3. /etc/fstab:
you need root permissions. go to a terminal, type "su" and root password. then type "less /etc/fstab" and you again get a screen that you can scroll. Post any lines that seem related to your cdroms. Or post the whole thing, if you're not sure.
:EDIT:
when you're done perusing something with "less" press "q" to drop you back to the terminal.
nosmokey
01-16-2003, 02:11 AM
Results from dmesg:
VFS: Mounted root (ext2 filesystem) readonly.
Trying to move old root to /initrd ... okay
Freeing unused kernel memory: 152k freed
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
loopc: loaded (max 16 devices)
loopc: lc_init loopc0
loopc: fs block size: 2048
loopc: read buffer holds 8 fs blocks
loopc: uncompressed size 1660352k: 103772 blocks, block size 16384
loopc: 1622 chunks (64 blocks/chunk)
ISO 9660 Extensions: RRIP_1991A
scsi : 0 hosts left.
ieee1394: Host removed: Node[00:1023] GUID[00053f5105001297] [Linux OHCI-1394]
usb.c: deregistering driver hiddev
usb.c: deregistering driver hid
usb.c: USB disconnect on device 1
usb.c: USB disconnect on device 2
usb.c: USB bus 1 deregistered
usb.c: USB disconnect on device 1
usb.c: USB bus 2 deregistered
usb.c: deregistering driver usbdevfs
usb.c: deregistering driver hub
loopc: blocks read: uncompr 254, total 1311
loopc: min free memory: 18648
loopc: lc_done loopc0
Adding Swap: 248968k swap-space (priority 42)
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
loopc: lc_init loopc0
loopc: fs block size: 2048
loopc: read buffer holds 8 fs blocks
loopc: uncompressed size 1660352k: 103772 blocks, block size 16384
loopc: 1622 chunks (64 blocks/chunk)
ISO 9660 Extensions: RRIP_1991A
MSDOS FS: IO charset iso8859-1
Linux Tulip driver version 0.9.15-pre11 (May 11, 2002)
PCI: Found IRQ 9 for device 02:0b.0
PCI: Sharing IRQ 9 with 00:1f.4
eth0: ADMtek Comet rev 17 at 0xd800, 00:04:5A:4A:3B:B6, IRQ 9.
CSLIP: code copyright 1989 Regents of the University of California
PPP generic driver version 2.4.2
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb-uhci.c: $Revision: 1.275 $ time 19:32:08 Sep 25 2002
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 5 for device 00:1f.2
PCI: Setting latency timer of device 00:1f.2 to 64
usb-uhci.c: USB UHCI at I/O 0xef40, IRQ 5
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 9 for device 00:1f.4
PCI: Sharing IRQ 9 with 02:0b.0
PCI: Setting latency timer of device 00:1f.4 to 64
usb-uhci.c: USB UHCI at I/O 0xef80, IRQ 9
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
uhci.c: USB Universal Host Controller Interface driver v1.1
hub.c: USB new device connect on bus1/1, assigned device number 2
usb.c: USB device 2 (vend/prod 0x4b8/0x5) is not claimed by any active driver.
usb.c: registered new driver usblp
printer.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x04B8 pid 0x0005
printer.c: v0.11: USB Printer Device Class driver
PCI: Found IRQ 3 for device 02:0a.0
IPv6 v0.8 for NET4.0
IPv6 over IPv4 tunneling driver
isapnp: Scanning for PnP cards...
eth0: no IPv6 routers present
isapnp: No Plug & Play device found
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 64
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 66
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 68
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 70
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 72
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 74
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 76
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 78
Linux video capture interface: v1.00
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 64
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 66
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 68
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 70
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 72
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 74
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 76
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 78
end_request: I/O error, dev 02:00 (floppy), sector 0
hdd: DMA disabled
hdd: DMA disabled
hdd: DMA disabled
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
LVM version 1.0.5(mp-v6)(15/07/2002) module loaded
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 0
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 2
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 4
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 6
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 0
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 2
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 4
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 6
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 0
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 2
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 4
hdd: command error: status=0x51 { DriveReady SeekComplete Error }
hdd: command error: error=0x54
end_request: I/O error, dev 16:40 (hdd), sector 6
2. Put a data cd into your recorder and try to mount it with:
mount /dev/cdrecorder
Any errors?
nosmokey
01-16-2003, 02:40 AM
gary@linux:~> ls -l/dev/cdr*
ls: invalid option -- /
Try `ls --help' for more information.
gary@linux:~> mount /dev/cdrecorder
mount: /dev/cdrecorder is not a valid block device
gary@linux:~>
BigFatJoe
01-16-2003, 02:52 AM
1. its:
ls -l /dev/cdr*
not,
ls -l/dev/cdr*
2. You will most likely need to emulate scsi support (you want to burn cd's right?). lets see what modules you already have compiled. as root:
lsmod
it doesnt look like you're going to need to recompile the kernel. try (as root):
rm /dev/cdrecorder
ln -s /dev/sr1 /dev/cdrecorder
mount /dev/cdrecorder (remember to use data cd)
nosmokey
01-16-2003, 03:44 AM
gary@linux:~> su
Password:
linux:/home/gary # rm /dev/cdrecorder
linux:/home/gary # ln -s /dev/sr1 /dev/cdrecorder
linux:/home/gary # mount /dev/cdrecorder
mount: /dev/cdrecorder is not a valid block device
linux:/home/gary #
carlywarly
01-16-2003, 12:26 PM
Try cdrecord -scanbus, as root. Your cdrecorder should show up. It will have a scsi id number, like 1,0,0 or similar. Once you know what it's scsi id is, go into your /dev directory and look for sr0, sr1 scd0, scd1 or similar. One of these will be a link to the recorder. Then you need to make a symbolic link as in the previous post, using the correct device.
nosmokey
01-16-2003, 02:00 PM
Thanks for your reply.
Here's what I got:
linux:/home/gary # cdrecord -scanbus
Cdrecord 1.11a28 (i686-suse-linux) Copyright (C) 1995-2002 Jörg Schilling
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
mdwatts
01-16-2003, 07:23 PM
It would seem you do not have ide-scsi loaded.
Edit your bootloader config (as root) and add hdc=ide-scsi and hdd=ide-scsi if both your cdroms are on secondary master and slave.
Most likely you are using Grub, so edit /boot/grub/menu.lst or grub.conf and add the above to the kernel line.
I didn't see a kernel line anywhere...just what you see above. Did I do something wrong?
bwkaz
01-16-2003, 10:09 PM
Originally posted by nosmokey
"/boot/grub/menu.lst" [New File] Well, that "[New File]" marker means that that file doesn't exist. Apparently "edit" is symlinked to either vim or vi on your system -- you may want to use a different, possibly GUI-based, editor, but whatever works.
vi/vim put "new file" up when the filename you tell it doesn't exist. So try an ls /boot/grub to see what's in that directory.
Note that it's also possible that you don't use grub. It's the default on a lot of distros, but not all of them. On Mandrake 8.1, it actually wouldn't install right (for me anyway -- though that could have been my mistake), so I was forced to use lilo instead. If nothing is in the /boot/grub directory, then you aren't using grub.
If files are there, post their names and someone will know the right one to edit.
Most likely you are using Grub, so edit /boot/grub/menu.lst or grub.conf and add the above to the kernel line.
Some distros use grub.conf instead of menu.lst. Mine always uses menu.lst, so I am not really sure where grub.conf exists.
It could be in /etc.
ls -al /etc/grub*
Or
locate grub.conf
HuiLai
01-17-2003, 12:36 PM
According to Linux (doing a cdrecord -scanbus) and xcdroast i don't have a cd-rw drive just my normal cdrom.. i do though. its a ZIPCDP1024INT ATAPI from Iomega (went to their site, no linux drivers :mad: ) I checked out the HWconfigurator in kde and it saw it.. i can't acess it.. although in fstab i do have a mount point for it.
In fstab i have:
## this is my regular cdrom
/dev/cdrom1 /mnt/cdrom1 iso9660 noauto,owner,kudzu,ro 0 0
## this SHOULD be my cdrw
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0
I did a ls -l /dev/cdr*
it came up with:
[Hui@Local Hui]$ ls -l /dev/cdr*
lrwxrwxrwx 1 root root 8 Jan 15 09:34 /dev/cdrom -> /dev/hdd
lrwxrwxrwx 1 root root 9 Dec 4 01:40 /dev/cdrom1 -> /dev/scd
i thought to myself /dev/cdrom (should be my CDRW) is pointing to HDD?!?! woa! Freaky.. so.. question!
What should i do? Change something in FSTAB (hee hee i like that word) or something else?
TAIA
Hui
bwkaz
01-17-2003, 02:03 PM
If you don't have SCSI emulation set up properly, cdrecord will not find your drive. You have to pass hdd=ide-scsi (for example -- this assumes your CDRW is the secondary slave) to your kernel at boot time, using either grub's config file, or lilo's (which one to do depends on which bootloader you use). This is what we're trying to do with nosmokey's system.
In order for cdrecord -scanbus to work, you will have to get that hdd=ide-scsi passed to your kernel -- it will probably be hdd, because that's what you said your CD-RW drive is.
went to their site, no linux drivers :mad: ) It's that way with every CD-RW (and CD-ROM, and DVD, and hard disk) drive manufacturer. There is no such thing as an ATAPI driver specific to a device; it just doesn't exist. They all work exactly the same way.
nosmokey
01-17-2003, 03:12 PM
Okay, I typed ls -al /etc/grub* and got this:
gary@linux:~> ls -al /etc/grub*
ls: /etc/grub*: No such file or directory
gary@linux:~>
Then, locate grub.conf:
gary@linux:~> locate grub.conf
bash: locate: command not found
gary@linux:~>
Bummer - I did, however, learn what master and slave mean :) Do I need to tear open this box and look inside?
yinrunning
01-17-2003, 03:26 PM
no, you don't need to look inside. This is a software problem. As root or su, try:
$ less /etc/grub.conf
If that doesn't exist, then we'll all scratch our heads and think of something else to do!
Hey, HuiLai! Why you tryin to steal the thread? Get your own! This is confusing enough!
nosmokey
01-17-2003, 04:42 PM
gary@linux:~> less /etc/grub.conf
/etc/grub.conf: No such file or directory
gary@linux:~>
By the way, I'm using the Live Eval version of SuSE 8.1 - I don't know if this makes a difference or not but I understand that some applications are missing and maybe this has something to do with the problem? Just a thought.
firemoth
01-17-2003, 05:00 PM
oh in that case you can't edit any files permanately...AND you don't have a bootloader like grub to boot linux off your hard drive...thats why grub.conf didn't exist...
try all of these in order with a cd in the drive (data, not blank) until it works, as root
mount /dev/sr1 /mnt
mount /dev/scd1 /mnt
if that doesn't work, try this
mount /dev/sr0 /mnt
mount /dev/scd0 /mnt
also see that your burner is getting mounted
those above lines will mount the cd in the directory /mnt
the one that works you know is the burner
phoneguy
01-17-2003, 05:45 PM
SuSe 8.1 has a problem with recognizing CD- and DVD rom drives the following is from SuSe's website.
Hope this helps
ciao
Cannot Mount CD or DVD
o Deutsch o Magyarul
Email address:
Support knowledgebase (81_ide-scsi)
Applies to
SuSE Linux: Version 8.1
Symptom
Your computer is equipped with a CDRW drive and one or several "ordinary" CD drives. After installing SuSE Linux 8.1, the CD drives cannot be mounted.
Cause
Some modules are missing from the initrd.
From SuSE Linux 8.1 on, the CD drive support is no longer compiled and kept in the kernel, but implemented by way of modules (cdrom and ide-cd). As opposed to the module ide-scsi, those modules (cdrom and ide-cd) are not included in the Initrd. That is why the SCSI emulation reaches all drives and not only those listed in the kernel parameter hdX=ide-scsi.
Solution
Insert the modules cdrom and ide-cd in the variable INITRD_MODULES in the file
/etc/sysconfig/kernel
To do this, open the YaST Sysconfig Editor. Select Base-Administration -> Common-Basics -> initrd_modules and insert both modules before the module ide-scsi. Be careful not to remove any of the modules listed, since they are necessary for booting.
Now, execute as root user the command mk_initrd
To do this, start a terminal program like konsole or xterm and log in as root user with the command su -. Then enter the command mk_initrd. If your boot manager is LILO, reinstall it with the command lilo -v. This does not apply for GRUB. From SuSE Linux 8.1 on, GRUB is the standard boot loader.
nosmokey
01-17-2003, 06:44 PM
It doesn't look like the sysconfig editor is working. Again, perhaps this is because I'm using the Live Eval CD (nothing's actually saved on my hard drive - everything runs from the CD)
Maybe I should just wait until I buy the regular distribution and see what happens. I really wanted to try it out and see if it's going to work on my computer...
My experience with different distributions is very limited but I really do like this SuSE. Does RedHat or any of the others have this problem?
mdwatts
01-17-2003, 07:27 PM
Originally posted by nosmokey
By the way, I'm using the Live Eval version of SuSE 8.1 - I don't know if this makes a difference or not but I understand that some applications are missing and maybe this has something to do with the problem? Just a thought.
Now you tell us... :rolleyes:
:)
You cannot edit a readonly filesystem.
Either purchase the full version of SuSE or download and install another distro.
nosmokey
01-17-2003, 07:47 PM
Well, shoot. Hey, at least I'm learning, right? Thanks to everyone for your help. I'll let you know how it turns out when I purchase the full version.
Cheers!
yinrunning
01-17-2003, 08:12 PM
By the way, I'm using the Live Eval version of SuSE 8.1
Yeah, that would explain a few things! :D
Good luck with the full one! And you do know you can dual/triple/however-many-you-want -boot OS's, right?
So, you could have Win2K, XP, and SUSE all running off of the same HDD or multiple HDD's, just not at the same time. Grub would be the easiest way to get this done. It'll load itself up on boot and give you options for which OS you want.
nosmokey
01-17-2003, 08:20 PM
Yeah - I've got a nice new partition waiting for my Linux. I was dual booting with another distro earlier but that didn't work out so I'll order SuSE soon! Can't wait :)
TreeHugger
10-25-2003, 06:42 AM
This thread gave me all I needed to sort out scsi emulation, thanks to the search forums option. Thanx.
justlinux.com
Copyright Internet.com Inc. All Rights Reserved.