Hi, Have just installed a BusLink 52x-24x-52x CD-RW drive onto a system that alho has a Zip drive. Have followed the hash of advice from (1) the CD-Writing How-to, (2) the SuSE 7.1 Configuration Manual, and (3) http://seismo.ethz.ch/linux/xcdroast.html. After (1) and (2), I could at least mount and read the CDROM as /dev/hdb (via append="hdb=ide-scsi" in /etc/lilo.conf). After (3), however, even this fails to occur. Furthermore, xcdroast (run as root) fails to detect anything to do with this drive, which replaces an older 2x-CDROM. In the interest of giving someone more knowledgeable a starting point, I'll start with (a) the boot message pertaining to the SCSI devices, (b) the relevant entries of my /etc/fstab (which no longer make sense to me), and (c) the output of the test recommended in the CD-Writing How-to. (a) boot message scsi0 : SCSI host adapter emulation for IDE ATAPI devices Vendor: IOMEGA Model: ZIP 100 Rev: 13.A Type: Direct-Access ANSI SCSI revision: 00 Detected scsi removable disk sda at scsi0, channel 0, id 0, lun 0 Vendor: LITE-ON Model: LTR-52246S Rev: 6S02 Type: CD-ROM ANSI SCSI revision: 02 Detected scsi CD-ROM sr0 at scsi0, channel 0, id 1, lun 0 sr0: scsi3-mmc drive: 52x/52x writer cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.12 sda : READ CAPACITY failed. sda : status = 0, message = 00, host = 0, driver = 28 sda : extended sense code = 2 sda : block size assumed to be 512 bytes, disk size 1GB. sda: I/O error: dev 08:00, sector 0 unable to read partition table Device not ready. Make sure there is a disc in the drive. VFS: Disk change detected on device sd(8,0) sda : READ CAPACITY failed. sda : status = 0, message = 00, host = 0, driver = 28 sda : extended sense code = 2 sda : block size assumed to be 512 bytes, disk size 1GB. sda: I/O error: dev 08:00, sector 0 unable to read partition table Device not ready. Make sure there is a disc in the drive. VFS: Disk change detected on device sd(8,0) sda : READ CAPACITY failed. sda : status = 0, message = 00, host = 0, driver = 28 sda : extended sense code = 2 sda : block size assumed to be 512 bytes, disk size 1GB. sda: I/O error: dev 08:00, sector 0 unable to read partition table VFS: Disk change detected on device sd(8,4) SCSI device sda: 196608 512-byte hdwr sectors (101 MB) sda: Write Protect is off sda: sda4 (b) /etc/fstab lines (new) /dev/cdrecorder /cdrecorder auto ro,noauto,user 0 0 /dev/cdrom /cdrom auto ro,noauto,user 0 0 (old line that worked was:) /dev/hdb /cdrom iso9660 ro,noauto,user 0 0 (for what it's worth, ls -l /dev/cdr* gives) lrwxrwxrwx 1 root root 3 Dec 11 02:07 /dev/cdrom -> hdb (c) test results (I just compiled a kernel that supposedly has the required modules, despite the protetstations of this test to the contrary....) Ensure the module sg is loaded automatically next time. insmod: sg: no module by that name found Ensure the module sr_mod is loaded automatically next time. insmod: sr_mod: no module by that name found The following is only needed for IDE/ATAPI CD writers. Cdrecord 1.9 (i686-suse-linux) Copyright (C) 1995-2000 J�rg Schilling Linux sg driver version: 3.1.17 Using libscg version 'schily-0.1' scsibus0: 0,0,0 0) 'IOMEGA ' 'ZIP 100 ' '13.A' Removable Disk 0,1,0 1) 'LITE-ON ' 'LTR-52246S ' '6S02' Removable CD-ROM 0,2,0 2) * 0,3,0 3) * 0,4,0 4) * 0,5,0 5) * 0,6,0 6) * 0,7,0 7) * Thanks in advance for your time, patience, and advice. Steve Miller __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
On Wednesday 11 December 2002 08.53, Steve Miller wrote:
sr0: scsi3-mmc drive: 52x/52x writer cd/rw xa/form2 <snip> (b) /etc/fstab lines (new)
/dev/cdrecorder /cdrecorder auto ro,noauto,user 0 0
/dev/cdrom /cdrom auto ro,noauto,user 0 0
(old line that worked was:)
/dev/hdb /cdrom iso9660 ro,noauto,user 0 0
I can't believe this worked while the drive was using ide-scsi
(for what it's worth, ls -l /dev/cdr* gives)
lrwxrwxrwx 1 root root 3 Dec 11 02:07 /dev/cdrom -> hdb
As root do this: ln -s /dev/sr0 /dev/cdrecorder rm /dev/cdrom ln -s /dev/sr0 /dev/cdrom After that you should be able to mount the CD using either "mount /cdrom" or "mount /cdrecorder".
0,1,0 1) 'LITE-ON ' 'LTR-52246S ' '6S02' Removable CD-ROM
Looks good to me. Anders
Hi, Followed your advice (below).
As root do this:
ln -s /dev/sr0 /dev/cdrecorder rm /dev/cdrom ln -s /dev/sr0 /dev/cdrom
After that you should be able to mount the CD using either "mount /cdrom" or "mount /cdrecorder".
I was able to mount and correctly read the CD as /cdrom, but not as /cdrecorder. I shut down to pick up again later. On restarting, I logged on as root to set up xcdroast, which I'd been unable to do. Again, xcdroast failed to see the CDRW (but did see the Zip drive). On further inspection, I determined that I could not even mount the CD as /cdrom. A possibly related problem: I can't set up the medium in YaST: When I try to set up the CD, I select SCSI ("/dev/sr?") and then the menu gives me oncy choices starting with "scd". Is the solution here to put in more links ("ln -s /dev/scd0 /dev/cdrom") or does the failure of /dev/sr0 to show up indicate another problem? Thanks again, Steve Miller __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
On Wednesday 11 December 2002 17.19, Steve Miller wrote:
Hi,
Followed your advice (below).
As root do this:
ln -s /dev/sr0 /dev/cdrecorder rm /dev/cdrom ln -s /dev/sr0 /dev/cdrom
After that you should be able to mount the CD using either "mount /cdrom" or "mount /cdrecorder".
I was able to mount and correctly read the CD as /cdrom, but not as /cdrecorder.
Did you umount /cdrom before trying to mount /cdrecorder? You can't mount the same device twice.
I shut down to pick up again later.
On restarting, I logged on as root to set up xcdroast, which I'd been unable to do. Again, xcdroast failed to see the CDRW (but did see the Zip drive). On further inspection, I determined that I could not even mount the CD as /cdrom.
Was the ide-scsi module loaded? Try adding ide-scsi to the INITRD line in /etc/sysconfig/kernel file and running mk_initrd
A possibly related problem: I can't set up the medium in YaST: When I try to set up the CD, I select SCSI ("/dev/sr?") and then the menu gives me oncy choices starting with "scd". Is the solution here to put in more links ("ln -s /dev/scd0 /dev/cdrom") or does the failure of /dev/sr0 to show up indicate another problem?
/dev/scd0 and /dev/sr0 are identical. They are two names for the same thing. Some parts of the system use one name, others use the other. It is of no significance Anders
Hi, Thanks for the sr/scd info. The oddness is halfway over, thanks to your help. YaST can sometimes see the installation medium now. (See below.) The following still has me scratching my head, though ....
Was the ide-scsi module loaded? Try adding ide-scsi to the INITRD line in /etc/sysconfig/kernel file and running mk_initrd
I don't have that file (/etc/sysconfig/kernel). Nor can I find a file named "kernel" anywhere else that looks like a configuration file or a set of boot instructions. What I have done (due to written instructions) is added "/sbin/modprobe ide-scsi" to the end of the file /etc/init.d/boot.local. When I use the test script from the CD-RW How-to, it seems to think I have /can load/have loaded (?) the module as I get the following message. Using /lib/modules/2.4.2/kernel/drivers/scsi/ide-scsi.o After I do this test, (1) YaSt is now able to see the installation medium and (2) I am suddenly able to mount the CD (as /cdrom, but still not as /cdrecorder): Pre-test: csmiller@elfenix:~ > mount /cdrom mount: /dev/cdrom: unknown device Post-test: elfenix:~ > mount /cdrom elfenix:~ > umount /cdrom elfenix:~ > mount /cdrecord mount: can't find /cdrecord in /etc/fstab or /etc/mtab (But /cdrecord IS in /etc/fstab.) I take it that what you are telling me I should do is to somehow make sure my system loads this ide-scsi module. (Perhaps the test I ran causes this to occur.) If so, might there be another way to make sure this happens? Thanks again, Steve Miller __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
On Wednesday 11 December 2002 22.15, Steve Miller wrote:
Was the ide-scsi module loaded? Try adding ide-scsi to the INITRD line in /etc/sysconfig/kernel file and running mk_initrd
I don't have that file (/etc/sysconfig/kernel). Nor can I find a file named "kernel" anywhere else that looks like a configuration file or a set of boot instructions.
Ah, yes, that's because I'm either an idiot or blind or (not unlikely) both :) Only now did I realise that the subject was "on 7.1". sysconfig/kernel didn't appear until 8.0. My bad.
What I have done (due to written instructions) is added "/sbin/modprobe ide-scsi" to the end of the file /etc/init.d/boot.local.
That should be enough, yes.
When I use the test script from the CD-RW How-to, it seems to think I have /can load/have loaded (?) the module as I get the following message.
Using /lib/modules/2.4.2/kernel/drivers/scsi/ide-scsi.o
After I do this test, (1) YaSt is now able to see the installation medium and (2) I am suddenly able to mount the CD (as /cdrom, but still not as /cdrecorder):
Pre-test:
csmiller@elfenix:~ > mount /cdrom mount: /dev/cdrom: unknown device
Post-test:
elfenix:~ > mount /cdrom elfenix:~ > umount /cdrom elfenix:~ > mount /cdrecord mount: can't find /cdrecord in /etc/fstab or /etc/mtab
(But /cdrecord IS in /etc/fstab.)
I take it that what you are telling me I should do is to somehow make sure my system loads this ide-scsi module.
If you can mount /cdrom then ide-scsi is loaded. You can double check with lsmod | grep ide-scsi but it should be loaded. As for /cdrecord, in your previous mail you called it /cdrecorder and not /cdrecord. Check which it should be. Anders
I keep getting a invalid argument paswwordfd. Does anybody know how to fix this?? This my 7th day using Linux, so I don't know much. In other word, I need step by step instructions on how to solve this. Thanks Matt In Alaska --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.427 / Virus Database: 240 - Release Date: 12/6/2002
On Wednesday 11 December 2002 21:38, Matthew Dunaway wrote:
I keep getting a invalid argument paswwordfd. Does anybody know how to fix this?? This my 7th day using Linux, so I don't know much. In other word, I need step by step instructions on how to solve this.
Can you tell us: Your distribution (I guess SuSE) and version (8.0? 8.1?) The desktop environment (KDE? Gnome?) What program gives you the error (if you can identify it) What, exactly, you are trying to do when you get the error. Then we might be able to help you... Dylan -- "Sweet moderation Heart of this nation Desert us not, we are Between the wars"
On 12/12/2002 05:38 AM, Matthew Dunaway wrote:
I keep getting a invalid argument paswwordfd. Does anybody know how to fix this?? This my 7th day using Linux, so I don't know much. In other word, I need step by step instructions on how to solve this.
A step by step is impossible without more info. What version? What were you doing/trying to do when you got this error, and which program? The answer to your problem is a spelling error. It is spelled passwordfd.so, and is probably found in the files under /etc/ppp/peers/ HTH -- Joe & Sesil Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.
Hi Could You give us a bit more information about this problem, like where it happens, what program are You using etc... The description You gave does not help us to solve the problem. Jaska. Viestissä Keskiviikko 11. Joulukuuta 2002 23:38, Matthew Dunaway kirjoitti:
I keep getting a invalid argument paswwordfd. Does anybody know how to fix this?? This my 7th day using Linux, so I don't know much. In other word, I need step by step instructions on how to solve this.
Thanks Matt In Alaska --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.427 / Virus Database: 240 - Release Date: 12/6/2002
Hi, After watching things stop working after an earlier reboot, I've been rebooting between troubleshoots. So I'll start with my results after rebooting:
grep record /etc/fstab /dev/cdrecorder /cdrecorder auto ro,noauto,user 0 0
So it's /cdrecorder. And ...
mount /cdrom mount: /dev/cdrom: unknown device mount /cdrecorder mount: mount point /cdrecorder does not exist
The test you suggested gets:
lsmod | grep ide-scsi
(i.e., nothing.). Now I run the other test again. (Script is appended below, after my name.) It seems that I have the module, but it's not loading automatically.
lsmod | grep ide-scsi ide-scsi 7840 0
mount /cdrom ls -lt /cdrom | head -1 total 112691 umount /cdrom mount /cdrecorder mount: mount point /cdrecorder does not exist
But this did cause the CD-RW to start spinning. Nothing shows up if I run mount alone. So I seem to have a couple of problems: (1) how can I get the system to summon the ide-scsi module when I try to mount the CD? (It runs my parallel port printer by loading modules just fine.), and (2) is there some way to tell the system about "legal" mount points? Test file is below. On reviewing my results, it seems that the script loaded the module the first time (i.e., it complained about no auto-load.). I'm going through the insmod man page now, but if you see what I need to do right away, that would help a lot. Thanks, Steve ****** test `whoami` = 'root' || echo "You must be root to execute the commands." cdrecord -scanbus > /dev/null if ! (pidof kerneld || test -f "/proc/sys/kernel/modprobe"); then echo "Neither kerneld nor kmod are running to automatically load modules." fi report_no_autoload() { echo "Ensure the module $1 is loaded automatically next time." } if test ! -f "/proc/scsi/scsi"; then report_no_autoload scsi_mod && insmod scsi_mod fi if ! grep "^........ sg_" /proc/ksyms > /dev/null; then report_no_autoload sg && insmod sg fi if ! grep "^........ sr_" /proc/ksyms > /dev/null; then report_no_autoload sr_mod && insmod sr_mod fi if ! grep "^........ loop_" /proc/ksyms > /dev/null; then report_no_autoload loop && insmod loop fi if ! grep iso9660 /proc/filesystems > /dev/null; then report_no_autoload iso9660 && insmod iso9660 fi echo "The following is only needed for IDE/ATAPI CD writers." if ! grep ide-scsi /proc/ide/drivers > /dev/null; then report_no_autoload ide scsi && insmod ide-scsi fi cdrecord -scanbus __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
On Wednesday 11 December 2002 23.22, Steve Miller wrote:
mount /cdrecorder
mount: mount point /cdrecorder does not exist
This means that the directory /cdrecorder doesn't exist. This may be a non-issue though. If you only have one optical device there is little reason to have two mount points and two entries in fstab.
The test you suggested gets:
lsmod | grep ide-scsi
(i.e., nothing.).
Very strange indeed. If you had a line that modprobes ide-scsi in /etc/init.d/boot.local it should be loaded. Do you get any error messages in /var/log/messages that could be an indication of why the modprobe fails? Double check the entry in boot.local, to make sure there aren't any spelling mistakes.
So I seem to have a couple of problems: (1) how can I get the system to summon the ide-scsi module when I try to mount the CD? (It runs my parallel port printer by loading modules just fine.), and (2) is there some way to tell the system about "legal" mount points?
Any directory is a legal mount point. If you get an error saying there's a problem with the mountpoint it simply mountpoint (directory) doesn't exist.
Test file is below. On reviewing my results, it seems that the script loaded the module the first time (i.e., it complained about no auto-load.). I'm going through the insmod man page now, but if you see what I need to do right away, that would help a lot.
You could experiment with the file /etc/modules.conf to get the module to autoload, but by far the simplest way is to have the modprobe line in boot.local you said you had. Let's see if we can understand why that fails. When you run the below script, which of the error messages get printed? Anders
Hi, Thanks, Anders, for all the help! You helped me move quickly past several problems and enabled me to reach a workable solution more quickly than I would have otherwise. (I start a new job Monday and may not have time to do much on the home computer for awhile.) As I worked on this again, I failed to check /var/log/messages/, but a quick look at it now shows complaints of several modules (none pertinent to this problem) not being found. I ended up compiling all suggested modules into the kernel and now have no problems accessing either the /cdrom or the /zip. (This is OK with me for now as I have >350 MB RAM.) Nevertheless, I may have a more fundamental problem with module loading. From an earlier kernel (with modularized ide-scsi/cdrom access, I have this error message: Dec 13 12:09:14 elfenix insmod: /lib/modules/2.4.2/kernel/drivers/cdrom/cdrom.o: insmod block-major-11 failed (I have had trouble before with modules, too, and resorted to the same non-modular solution.) At any rate, I am going to try to forge ahead now with xcdroast problems (separate post). As for the module loading difficulties, I plan to set those aside for now. I may install (i.e., NOT upgrade to) 8.1 (or is it 8.2 now?) where, if I recall, I don't need ide-sci emulation any more. I am considering this since some time back, I somehow managed to upgrade from 6.1 to 7.1. With the number of things that were changed between 6.1 and 7.1, I can't help but wonder if something might have affected my ability to load modules automatically..... Thanks, Steve __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
participants (6)
-
Anders Johansson -
Dylan -
jaakko tamminen -
Joe Morris (NTM) -
Matthew Dunaway -
Steve Miller