Re: cdrom help
Well, I gotta open the case and check. It worked about 2 years ago when this box had Windows on it. Yes, I've been in the box since then and might have bumped the wire loose or something. As far as the settings in KMix, I have all the volumes maxed(I'll probably be either deafened or scared witless when it does finally work) and have played with about every variation of muting/unmuting that I can imagine. So, I'll open the case when I get a chance and check it out. Jim On Tuesday, January 15, 2002 1:10, Dave Anselmi wrote: Jim Conner wrote: [...] As for fixing cd audio, it's on that big to-do list that's a mile long. It's not critical, I get all other sounds, but would be nice to have working. If you have sound working generally, there are only 2 things I can think of to add for CD audio. First, you need a wire connecting your CD's audo port to your sound card. Second, you may need to unmute or otherwise adjust the CD audio channel in your mixer. Dave ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users -- 1:42pm up 22:25, 2 users, load average: 0.00, 0.06, 0.07 Running Caldera W3.1 - Linux - because life is too short for reboots... _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
On Mon, 14 Jan 2002 04:15, Tim Wunder wrote: Upon investigation, I made a WAG that the reason I needed to load ide-scsi during boot was that I had IDE CDROM support compiled into the kernel. Bugger, bugger, bugger. I *forgot* all about that wrinkle. You are right sir. -- http://linux.nf -- [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
On Mon, 14 Jan 2002 03:30, Ken Moffat wrote: ln -s /dev/srX /dev/scdX PMFJI .. I have /dev/scd0 and /dev/scd1 for cd-rw and dvd. Should I do step 3 above? Yes. It does no harm. Jan 13 07:23:05 localhost kernel: sr1: CDROM not ready. Make sure there a symlink will fix that. I assume supermount is looking for media. Annoying. Correct. The bottom line here is simply to understand that both srX and scdX refer to the same animal. How you organise YOUR system is one of the best features of Linux. You can. -- http://linux.nf -- [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
devfs was Re: cdrom help
On Mon, 14 Jan 2002 02:57, David A. Bandel wrote: If you have something better (than devfs), I know lots of folks who would like to hear your idea of how to do it. We have no argument about the 'goodness' of devfs. devfs is going to happen, because it has to. I have run devfs (past tense) I agreed with it, it did not agree with me. I admire your ability to use it. Richard Gooch has a *lot* of documentation to catch up on because 80% of what is there is a 1998 argument as to why devfs is needed (in preference to other alternatives). It is scant, to non-existent, on HOW to use it. so you need to tell whoever owns the sr_mod module that he's got to rename is scd_mod because he's wrong -- no? This is facetious. The point being that the ramifications of implementing scdX in preference to srX were not thought out fully. Redhat is not alone, unique or the leader of this new wrinkle. And, I'd fight anyone who said the kernel must change because of *any* distro. _because_ sr_mod is hardwired, _because_ many automounters hunt srX, this new approach may die a death and everyone will revert to srX. Right now, there is confusion everywhere about the duality of scdX /srX and there's no magic-cure. I don't argue the author must change, I point out the reasons why thingz iz as they iz. My view is that the dynamic assignment of devfs will rule the day and things will revert. I've been using devfs since it came out. I prefer it. It may not be perfect, but it's a damn site better than creating thousands of useless device nodes No contest. -- http://linux.nf -- [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: devfs was Re: cdrom help
On Mon, 14 Jan 2002 23:39:31 +1130 Mike Andrew [EMAIL PROTECTED] spewed into the bitstream: On Mon, 14 Jan 2002 02:57, David A. Bandel wrote: If you have something better (than devfs), I know lots of folks who would like to hear your idea of how to do it. We have no argument about the 'goodness' of devfs. devfs is going to happen, because it has to. But if there's a better way to implement it, that would be a good thing. As it stands, it's not that it's good, bad, or indifferent, it's that it's the _only_ way to dynamically create what you need. I have run devfs (past tense) I agreed with it, it did not agree with me. Sorry to hear that. I haven't had any problems with it or I'd have abandoned it long ago. But it works well enough I just stick with it. I admire your ability to use it. Richard Gooch has a *lot* of documentation to catch up on because 80% of what is there is a 1998 argument as to why devfs is needed (in preference to other alternatives). It is scant, to non-existent, on HOW to use it. True. I'd say the documentation is the code, but it's nearly unintelligible to any but a kernel hacker (which I ain't). so you need to tell whoever owns the sr_mod module that he's got to rename is scd_mod because he's wrong -- no? This is facetious. The point being that the ramifications of implementing scdX in preference to srX were not thought out fully. Redhat is not alone, unique or the leader of this new wrinkle. And, I'd fight anyone who said the kernel must change because of *any* distro. True. I should have put a tongue in cheek emoticon with this. But I haven't seen any use of scd#, only of sr#. OTOH, I don't run RH or direct derivitives (at least not direct enough to have RH's problems). _because_ sr_mod is hardwired, _because_ many automounters hunt srX, this new approach may die a death and everyone will revert to srX. Right now, there is confusion everywhere about the duality of scdX /srX and there's no magic-cure. I don't argue the author must change, I point out the reasons why thingz iz as they iz. My view is that the dynamic assignment of devfs will rule the day and things will revert. Documentation is great. And you can document the use of scd# forever. But until devfs + all the major distros implement it (and RH and a few of its followers aren't all the major distros), it's nothing but words. And a number of distros do use devfs (gentoo and sorcerer come to mind, so I'm not exactly alone). Meanwhile, any documentation should probably cover both (as much of an annoyance as that is). I've been using devfs since it came out. I prefer it. It may not be perfect, but it's a damn site better than creating thousands of useless device nodes No contest. -- Focus on the dream, not the competition. -- Nemesis Racing Team motto Internet (H323) phone: 206.28.187.30 ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
Found another wrinkle on my system. This may affect some and not others depending on hardware and such. If you have DMA turned on when you compiled the kernel, it will enable DMA for the cdrom and cdrw. This will cause a kernel oops when you mount the cd and the only way out is the reset button. I got around it by doing this. I put these two lines in /etc/rc.d/rc.local: hdparm -d0 /dev/hdd hdparm -d0 /dev/hde Please change this to reflect your appropriate drives. It turns off DMA for the two drives and every thing works just perfect. Well, almost, cd audio doesn't work no matter what I try. Although I haven't tried the obligatory sacrificial chicken on the keyboard. :) Jim On Monday, January 14, 2002 6:39, Mike Andrew wrote: On Mon, 14 Jan 2002 04:15, Tim Wunder wrote: Upon investigation, I made a WAG that the reason I needed to load ide-scsi during boot was that I had IDE CDROM support compiled into the kernel. Bugger, bugger, bugger. I *forgot* all about that wrinkle. You are right sir. -- 1:42pm up 23 days, 15:21, 3 users, load average: 0.10, 0.12, 0.16 Running Caldera W3.1 - Linux - because life is too short for reboots... _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
This has correccted the problem. Thanks. (again) On Mon, 14 Jan 2002 23:12:26 +1130 Mike Andrew [EMAIL PROTECTED] wrote: On Mon, 14 Jan 2002 03:30, Ken Moffat wrote: ln -s /dev/srX /dev/scdX PMFJI .. I have /dev/scd0 and /dev/scd1 for cd-rw and dvd. Should I do step 3 above? Yes. It does no harm. Jan 13 07:23:05 localhost kernel: sr1: CDROM not ready. Make sure there a symlink will fix that. I assume supermount is looking for media. Annoying. Correct. The bottom line here is simply to understand that both srX and scdX refer to the same animal. How you organise YOUR system is one of the best features of Linux. You can. -- http://linux.nf -- [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users -- Ken Moffat [EMAIL PROTECTED] ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
RE: cdrom help
Folks, This topic has raised a lot of questions, and even touched on an area where I may be able to contribute (for a change). The question was raised about whether to copy the CD image to hard drive before burning to CDRW. That will work more reliably in some cases, and won't hurt. The usual cause of problems during a burn is when the write buffer gets empty. For some reason CDRW software (on board) can't seem to accommodate this (YMMV according to manufacturer). So, if you are copying from a *fast* CDROM to a slow CDRW, this may never be a problem. If, however, they run at the same speed, or are on the same bus where a data transfer conflict can slow things down, you might be safer to copy to HD and burn from there. This is a *great* reason to insure that you don't have both CDs on the same IDE bus, BTW. I have seen this problem occur on a 16x read and a 4x write, but the processor and bus were the limiting factors. Hope this helps. In Harmony's Way, and In A Chord, Tom :-}) +--+ | Thomas A. Condonemail: [EMAIL PROTECTED] | | Computer Engineer phone: (360) 315-7609| | Barbershop Bass SingerSailor and Singer of Chanties | | Left Handed and In My Right Mind | +--+ /\ \ / X ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL / \ ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
On Sun, 13 Jan 2002 04:56, Rick Sivernell wrote: I am having continual problems with cdroms. I have the following scsi id 4 42x scsi cdrom scsi id 5 Yamaha 6x4x16 cdwriter hdc is a 52x ide cdrom drive [snippetty hack] Rick, your problem is your misunderstanding of srX and scdX they are BOTH the same thing. Viz. [root@RSivernell rick]# ll /dev/sc* | more brw-rw-r-- 1 rick disk 11, 0 Oct 11 13:07 /dev/scd0 brw-rw-r-- 1 root disk 11, 1 Oct 11 13:07 /dev/scd1 brw--- 1 rick root 11, 0 Oct 11 13:07 /dev/sr0 brw--- 1 rick disk 11, 1 Oct 11 13:07 /dev/sr1 note the major / minor numbers? They are identical. First. modern distros deprecate the use of srX, get rid of them, literally. Promise from me that you can do no harm by deleting them. 2) you don't appear to have /dev/scd2. Do a mknod 3) ln -s /dev/srX /dev/scdX iterate X 0, 1 and 2 Each of your cd roms (all THREE) will iterate scd0, scd1 and finally scd2. Which is what is *impossible* to say as it depends on the order of module load, AND, which gets mounted first. (Blame the crappy scsi framework on Linux for that one, it's a brothel) As a fair and reasonable guess, your system (regardless of what you think you have in /etc/fstab) is as follows scd0 = hdc (because of append statement) scd1 = writer (lun #4) scd2 = reader (lun #5) /dev/cdrom /mnt/cdrom iso9660 ro,user,noauto,exec 0 0 /dev/cdwriter /mnt/sr0 iso9660 ro,user,noauto,exec 0 0 /dev/cdrom2 /mnt/scd1 is09660 ro,user,noauto,exec 0 0 so that YOU don't get confused, scrap out all references to srX in both the fstab, and, obviously, the /mnt folder, replace them with the direct scdX name. again, scrap all symlinks to mysterious items like cdrom etc and use direct /dev/scdX's. By all means, change back after it's settled down, but first work in the literal world (kde makes special use of the name 'cdrom' incidentally) *Temporarily* disable automounters Finally, reboot, place a cd in each drive and mount each scdX to find out who is what. There *will be* a timing race between the hdc and the other devices. If it is mounted FIRST, it will *probably* affect the scdX order because it's device minor node doesn't get registered until the cdrom.o module is loaded. Thus, I don't want to complicate things here, but *if* it's mounted first it will be scd0, *if* not, it might be scd2. You are going to have to play. All else fails? post here tail -50 /var/log/messages immediately after a reboot -- http://linux.nf -- [EMAIL PROTECTED] _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
On Mon, 14 Jan 2002 02:19:15 +1130 Mike Andrew [EMAIL PROTECTED] spewed into the bitstream: On Sun, 13 Jan 2002 23:36, David A. Bandel wrote: modern distros deprecate the use of srX, get rid of them, literally. Promise from me that you can do no harm by deleting them. What's your source for this? /usr/src/linux/Documentation/devices.txt plus That's what I get for not reading every word of every piece of documentation with every new relaese. now I have to wonder when this happened. :-(. OTOH, if I spent all my time rereading every single document with every single release of every single package, I might be up to reading in kernel version 1.2.10 about now. Maybe up to 2.2.18 in 2005. latest releases of most Distros (RH7.1/2 eg) only have /dev/scdX nodes. not srX nodes. Most of what RH does is wrong, so don't use them as a measure of anything. I run 2.4.17 w/ devfs all bets are off. devfs is a good idea, badly implemented, attrociously documented. It doesn't work with the LABEL=/ statement in /etc/fstab If you have something better, I know lots of folks who would like to hear your idea of how to do it. The reason for devfs is the explosion of devices and the limited major/minor numbers available. In fact, devfs is supposed to do away with the device numbers problem because there aren't enough numbers for every device in the world. While you may not have but a few devices connected to your system, if you had one that either didn't have a major/minor because there were no more, or because another device you're using is using the major/minor this new device needs, you're SOL (sorry, out of luck). when I modprobe ide-scsi then sr_mod, the only devices created are sr0 and sr1. These devices are created dynamically by sr_mod. Being pedantic, modules don't do this. devfs intercepts the registration and makes (and destoys) nodes on the fly. It picks up on the internally named 'sr' labels because, by convention, the names of device drivers are associated, programatically, with /dev/names. sr_mod, is an unfortunate choice. so you need to tell whoever owns the sr_mod module that he's got to rename is scd_mod because he's wrong -- no? Ignoring devfs for the moment, the only thing any driver, and any application, looks for is major / minor numbers, you can call the thing, and address the thing, as /dev/elephants for all that it matters. (it's just a lookup to the major/minor number). yes, I know how major/minors work (currently). But that's also their drawback. While I don't call any device foo, I have created device nodes with this name just to show how it works to others. kernel messages invoked by sr_mod refer to it's device nodes as sr0 ... etc. BUT, these are hardwired internal printk messages of sr_mod. Popular useage these days is /dev/scd0. So, the guy that programs sr_mod is as lost as I am (or hasn't read the recent documentation changes and/or doesn't take RH as gospel). Regardless, the point being is that both names /dev/scdX AND /dev/srX mean the same thing, they are both the same major minors and cause added confusion in an already confused and idiotic scsi node tree. ( I am referring to both the dynamic assignment of /dev/sxx anything, and the tree jumps to accomodate a squillion scsi minor nodes). No, it doesn't. You can't create that many device nodes because of the limitation of the major/minor numbers. If it were not recommended to use scdX, and, if distros hadn't already pre-empted this by removing /dev/srX nodes, I would just as emphatically reverse my stance and remove scdX anything. Whatever whichway, the duality causes problems. (witness the screams in /etc/fstab by many users) To be truthfull David, I hadn't considered devfs, it's an added wrinkle to the mess. I've been using devfs since it came out. I prefer it. It may not be perfect, but it's a damn site better than creating thousands of useless device nodes (which, BTW, take up inodes/disk space). On my personal distro (mine, Chiriqui Linux, the one I created which boots from a CD and runs in RAM mounting /usr from the CD) uses devfs -- or I would have to create each device by hand for just what I need or I'd waste precious space). Sure would like to hear your idea of a replacement for devfs. Ciao, David A. Bandel -- Focus on the dream, not the competition. -- Nemesis Racing Team motto Internet (H323) phone: 206.28.187.30 ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
On Sun, 13 Jan 2002 08:27:28 -0500 Tim Wunder [EMAIL PROTECTED] wrote: After reading that bedtime reading page, it's a wonder anything works... I'm always amazed anything works (when I'm at the controls). -- Ken Moffat [EMAIL PROTECTED] ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
Previously, Tim Wunder chose to write: Yeah, I know, replying to my own post, yada, yada snip My COL3.1 apparently uses both srx and scdx to refer to the same things: brwxrwxrwx 2 root disk 11, 0 Apr 27 2001 /dev/scd0 brw--- 1 dad root 11, 1 Apr 27 2001 /dev/scd1 brw--- 1 dad root 11, 0 Apr 27 2001 /dev/sr0 brw-rw-r-- 1 root disk 11, 1 Apr 27 2001 /dev/sr1 Interesting to note the user/group for my devices. Not sure what's going on there... sr0 and scd0 are my SCSI CDRW, sr1 and scd1 are my IDE CD-ROM, /dev/hdd. I happen to have hdd=ide-scsi in my menu.lst. I also have ide-scsi loaded as a module in /etc/modules/default. Everything works, but it sure seems horked. Guess I'll try to play around with it some to see if I can figger out what's going on. It is likely only the only thing this task will accomplish, though, is breakage... I'll start by removing the /dev/sr0 and sr1 files and take hdd=ide-scsi out of grub's menu.lst file and see what happens. Well, I removed the /dev/sr0 and sr1 files and took hdd=ide-scsi out of grub's menu.lst file and, upon first reboot, my ide CD-ROM was no longer seen by xcdroast as a scsi device. In order for my IDE CD-ROM to be seen as a scsi device, I had to add hdd=ide-scsi to the kernel line in my menu.lst file. This is contrary to what the bedtime reading document states. So I set out to determine why. Upon investigation, I made a WAG that the reason I needed to load ide-scsi during boot was that I had IDE CDROM support compiled into the kernel. I tested my WAG by recompiling the kernel with IDE-CDROM support as a module. Upon reboot with this new kernel, I am able to access my IDE-CDROM using xcdroast. Now, off to figure out why I can't access my IDE-ZIP drive with this same kernel. But that should be another thread... Tim ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
On Sun, 13 Jan 2002 22:06,David A. Bandel scribed: On Sun, 13 Jan 2002 21:33:19 +1130 Mike Andrew [EMAIL PROTECTED] spewed into the bitstream: [snip] modern distros deprecate the use of srX, get rid of them, literally. Promise from me that you can do no harm by deleting them. What's your source for this? I run 2.4.17 w/ devfs (the latest). At boot, I have neither scd# nor sr# devices, but when I modprobe ide-scsi then sr_mod, the only devices created are sr0 and sr1. These devices are created dynamically by sr_mod. The info is built into the module. If what you say is true, then I don't understand why I only get sr# and not scd#. David, I am in no way in either your or Mikes' league; However I have noticed in differing distros that srX is missing in some and not in others. -- Keith Antoine aka 'skippy' 18 Arkana St, The Gap, Queensland 4061 Australia PH:61733002161 Retired Geriatric, Sometime Electronics Engineer, Knowall, Brain in storage ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
On Mon, 14 Jan 2002 02:45,Tim Wunder scribed: Now thats interesting and i'll have a look at mine. Well, I removed the /dev/sr0 and sr1 files and took hdd=ide-scsi out of grub's menu.lst file and, upon first reboot, my ide CD-ROM was no longer seen by xcdroast as a scsi device. In order for my IDE CD-ROM to be seen as a scsi device, I had to add hdd=ide-scsi to the kernel line in my menu.lst file. This is contrary to what the bedtime reading document states. So I set out to determine why. Upon investigation, I made a WAG that the reason I needed to load ide-scsi during boot was that I had IDE CDROM support compiled into the kernel. I tested my WAG by recompiling the kernel with IDE-CDROM support as a module. Upon reboot with this new kernel, I am able to access my IDE-CDROM using xcdroast. Now, off to figure out why I can't access my IDE-ZIP drive with this same kernel. But that should be another thread... Tim ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users -- Keith Antoine aka 'skippy' 18 Arkana St, The Gap, Queensland 4061 Australia PH:61733002161 Retired Geriatric, Sometime Electronics Engineer, Knowall, Brain in storage ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
On Saturday 12 January 2002 14:45 pm, Rick Sivernell wrote: I am not getting a stable cdrom operation all the time. On all CD drives? or just the IDE one? -- ++ + Bruce S. Marshall [EMAIL PROTECTED] Bellaire, MI 01/12/02 15:35 + ++ The flush toilet is the basis of western civilization. - Alan Coult ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
Previously, Rick Sivernell chose to write: On Sat, 12 Jan 2002 15:12:15 -0500 Tim Wunder [EMAIL PROTECTED] wrote: Ok now have read the BedTime reader. What I get is 1 If cdrom is not IDE-RW then hdx=ide-scsi is not needed, especially if you have real scsi cdroms writers. As long as you don't you want your cd burning software to see it, yes. 2. if you have 3 cdrom drives you should have sr0 sr1 sr2 etc for list of the drives you have. If they are all scsi or emulated as scsi by the ide-scsi module. 3. If you have 3 or more drivbes all ypou have is /sev/sr0 / sr1, do you need to creat a new device for the remaining cddrives. If so, how or what is the propper meth to perform this. I don't follow this. AFAIK, all devices identified by the kernel and the ide-scsi module will have their device names created automagically. FWIW, I believe mknod is the command you need to use to create devices. But I'm not convinced that's what you want to do. Recommendation: Remove all symlinks in /dev Remove the kernel line hdc=ide-scsi Re-boot the system and look at your /dev directory. As I understand it, you should then have /dev/sr0: SCSI CD-ROM or CDRW /dev/sr1: SCSI CDRW or CD-ROM /dev/hdc: IDE CD-ROM If you want the IDE CD-ROM to be seen by xcdroast, or your preferred CD burning software, you'll need to load the ide-scsi module during the boot process (refer to the Bedtime reading to find the right place according to your distro). That should give you a third device, /dev/sr2, which should be the IDE-CDROM as seen thru scsi-emulation. Test the config by placing a data CD in each drive, one by one, and mounting it, 'mount -tiso9660 /dev/srx /mnt/whatever' Then, create the /dev/cdrom, /dev/cdwriter, /dev/whatever symlinks you want. HTH, Tim ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
On Sat, 12 Jan 2002 16:02:53 -0500 Tim Wunder [EMAIL PROTECTED] wrote: Recommendation: Remove all symlinks in /dev Remove the kernel line hdc=ide-scsi Re-boot the system and look at your /dev directory. As I understand it, you should then have /dev/sr0: SCSI CD-ROM or CDRW /dev/sr1: SCSI CDRW or CD-ROM /dev/hdc: IDE CD-ROM PMFJI Here is what worked for me. I have 1 cdrw and one dvd, both shown as scsi, and the devices are scd0 and scd1. (I've seen somewhere that sr0 and sr1 are outdated. (?)) And I use the lilo line append=hdb=ide-scsi hdc=ide-scsi This works in Redhat7.1, ELX and Libranet. I deleted my cdrom links in /dev (cdrom-hdb and cdrom1-hdc) and replaced them with ln -s /dev/scd0 /dev/cdrom ln -s /dev/scd1 /dev/cdrom1 Just another alternative to investigate. The stepbystep site was a big help. http://linux.nf -- Ken Moffat [EMAIL PROTECTED] ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
On Sat, 12 Jan 2002 13:15:18 -0800 Ken Moffat [EMAIL PROTECTED] wrote: On Sat, 12 Jan 2002 16:02:53 -0500 Tim Wunder [EMAIL PROTECTED] wrote: Recommendation: Remove all symlinks in /dev Remove the kernel line hdc=ide-scsi Re-boot the system and look at your /dev directory. As I understand it, you should then have /dev/sr0: SCSI CD-ROM or CDRW /dev/sr1: SCSI CDRW or CD-ROM /dev/hdc: IDE CD-ROM PMFJI Here is what worked for me. I have 1 cdrw and one dvd, both shown as scsi, and the devices are scd0 and scd1. (I've seen somewhere that sr0 and sr1 are outdated. (?)) And I use the lilo line append=hdb=ide-scsi hdc=ide-scsi This works in Redhat7.1, ELX and Libranet. I deleted my cdrom links in /dev (cdrom-hdb and cdrom1-hdc) and replaced them with ln -s /dev/scd0 /dev/cdrom ln -s /dev/scd1 /dev/cdrom1 Just another alternative to investigate. Yes, elx only uses /dev/scd... /dev/sr... do not exist. -- Collins Richey - Denver Area WWTLRD? - FreeBSD 4.4 + xfce + sylpheed ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
Previously, Ken Moffat chose to write: On Sat, 12 Jan 2002 16:02:53 -0500 Tim Wunder [EMAIL PROTECTED] wrote: Recommendation: Remove all symlinks in /dev Remove the kernel line hdc=ide-scsi Re-boot the system and look at your /dev directory. As I understand it, you should then have /dev/sr0: SCSI CD-ROM or CDRW /dev/sr1: SCSI CDRW or CD-ROM /dev/hdc: IDE CD-ROM erm, make that /dev/scd0: SCSI CD-ROM or CDRW /dev/scd1: SCSI CDRW or CD-ROM /dev/hdc: IDE CD-ROM PMFJI Here is what worked for me. I have 1 cdrw and one dvd, both shown as scsi, and the devices are scd0 and scd1. (I've seen somewhere that sr0 and sr1 are outdated. (?)) And I snip I stand corrected. (jeez, and I JUST read the damn bedtime reading page, too!) Tim ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
On Sat, 12 Jan 2002 16:37:36 -0500 Tim Wunder [EMAIL PROTECTED] wrote: (I've seen somewhere that sr0 and sr1 are outdated. (?)) And I snip I stand corrected. (jeez, and I JUST read the damn bedtime reading page, too!) Tim I didn't mean to correct, just offer an alternative. I've heard that both can work, depending on the distro. -- Ken Moffat [EMAIL PROTECTED] ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
List Thanks for response. Need to add some info here. Running ew 3.1.1 using kde 2.2 /var/log/messages: Jan 11 06:31:40 RSivernell kernel: Adaptec aic7850 SCSI adapter Jan 11 06:31:40 RSivernell kernel: aic7850: Single Channel A, SCSI Id=7, 3/255 SCBs Jan 11 06:31:40 RSivernell kernel: scsi ID 6 Jan 11 06:31:40 RSivernell kernel: Vendor: ARCHIVE Model: 4326XX 03813-XXX Rev: 645a scsi ID 5 Jan 11 06:31:40 RSivernell kernel: Vendor: YAMAHAModel: CRW6416S Rev: 1.0b Jan 11 06:31:40 RSivernell kernel: Type: CD-ROM ANSI SCSI revision: 02 scsi ID 4 Jan 11 06:31:40 RSivernell kernel: Vendor: TOSHIBA Model: CD-ROM XM-6401TA Rev: 1009 Jan 11 06:31:40 RSivernell kernel: Type: CD-ROM ANSI SCSI revision: 02 IDE CDROM: Jan 11 06:31:40 RSivernell kernel: scsi1 : SCSI host adapter emulation for IDE ATAPI devices Jan 11 06:31:40 RSivernell kernel: Vendor: E-IDE Model: CD-ROM 52X/AKHRev: A62 Jan 11 06:31:40 RSivernell kernel: Type: CD-ROM ANSI SCSI revision: 02 . Jan 11 06:32:36 RSivernell kernel: Attached scsi CD-ROM sr0 at scsi0, channel 0, id 5, lun 0 Jan 11 06:32:36 RSivernell kernel: Attached scsi CD-ROM sr1 at scsi0, channel 0, id 6, lun 0 Jan 11 06:32:36 RSivernell kernel: Attached scsi CD-ROM sr2 at scsi1, channel 0, id 0, lun 0 Jan 11 06:32:36 RSivernell kernel: (scsi0:A:5): 10.000MB/s transfers (10.000MHz, offset 15) Jan 11 06:32:36 RSivernell kernel: sr0: scsi3-mmc drive: 16x/16x writer cd/rw xa/form2 cdda tray Jan 11 06:32:36 RSivernell kernel: Uniform CD-ROM driver Revision: 3.12 Jan 11 06:32:36 RSivernell kernel: sr1: scsi-1 drive Jan 11 06:32:36 RSivernell kernel: sr2: scsi3-mmc drive: 8x/52x cd/rw xa/form2 cddatray [root@RSivernell rick]# ll /dev/cd* | more lrwxrwxrwx1 root root3 Jan 10 15:49 /dev/cdrom - /dev/sr1 lrwxrwxrwx1 root root8 Jan 12 14:38 /dev/cdrom2 - /dev/sr2 no sr2 lrwxrwxrwx1 root root3 Jan 12 10:59 /dev/cdwriter - /dev/sr0 [root@RSivernell rick]# ll /dev/sr* | more brw---1 rick root 11, 0 Oct 11 13:07 /dev/sr0 brw---1 rick root 11, 1 Oct 11 13:07 /dev/sr1 [root@RSivernell rick]# ll /dev/scd* | more brw-rw-r--1 rick disk 11, 0 Oct 11 13:07 /dev/scd0 brw-rw-r--1 root disk 11, 1 Oct 11 13:07 /dev/scd1 if scd? replaces sr?, why does caldera still use sr?? The on desktop Icon use ICON URLs on Desktop /auto/cdrom for /dev/sr1 /auto/cdwriter for /dev/sr0 /dev/sr2 for /mnt/sr2 there is not any /dev/sr2 or /dev/scd2 I have removed from grub/menu.lst hdc=ide-scsi rebooted. All is the same as before. The most stable cd drive is my cdwriter @ /dev/sr0. cheers -- Rick Sivernell Dallas, Texas 75287 972 306-2296 [EMAIL PROTECTED] Caldera Open Linux eWorkStation 3.1 Registered Linux User .~. / v \ /( _ )\ ^ ^ In Linux we trust! ___ Linux-users mailing list Archives, Digests, etc at http://linux.nf/mailman/listinfo/linux-users
Re: cdrom help
Somewhat inexperienced at this SCSI setup, but looking at my system the real SCSI CD's are sr0 and sr1. The sr? values are assigned based on the SCSI id number. In fact I recently (yesterday) had a problem adding a SCSI dvd as SCSI id 0 on a system that already had SCSI id 4 and 5 because the SCSI id 4 device had already been linked as sr0. After the new dvd was added as SCSI id 0 the new dvd became sr0 and the pre-existing SCSI id 4 device become sr1. The links did not automatically change and the new dvd assumed the identity of the SCSI device which was sr0. What I am suggesting is that your SCSI cd system is as follows: /dev/sr0 scsi id 4 42x cdrom /dev/sr1 scsi id 5 cdwriter /dev/scd1emulation 52x ide cdrom This does not agree with the info that you provided, but on my system the lower SCSI id device gets the lower sr? value. To solve my problem the /dev/dvd and /dev/cdrecorder were removed (rm). Then new links were established for /dev/sr0 - /dev/dvd and /dev/sr1 - /dev/cdrecorder. Until these links were established on the system fstab did not reflect the physical system. Having only ever worked on two SCSI systems treat the above comments with caution. On Sat, 2002-01-12 at 12:45, Rick Sivernell wrote: List I am having continual problems with cdroms. I have the following scsi id 4 42x scsi cdrom scsi id 5 Yamaha 6x4x16 cdwriteronly one that seems to work all the time scsi id 6 scsi dat 4mm tape drive not a problem ow. hdc is a 52x ide cdrom drivethere on bootup but do anything and it disappears or hangs system I have set kernal line to hdc=ide-scsi, verify below. I get 3 icons on the desktop and most of the time they say they are mounted, cd drive cdwriter. I am not getting a stable cdrom operation all the time. Please correct me if I am wrong, I know you guys will g with pleasure. The system boots up and sees the true scsi as scd? and the ide as hd?. Thus the scd0 scd1 for my scsi cdrom drives, there are no scsi hard drives in this system, the ide-scsi as sr0. A mout point in /auto should be for /dev/cdrom - sr0 as cdrom, a second for /dev/cdwriter - /dev/scd0 as /auto/cdwriter, /dev/cddrive 2 - /dev/scd1 as /auto/cdrom2. What is going wrong, or do I need to provide more info. I have read the sxs @linux.nf. not quite sure here. hda is a 60g harddrive ide ile setups: [root@RSivernell rick]# ll /dev/ta* | more lrwxrwxrwx1 root root3 Dec 21 03:23 /dev/tape - st0 [root@RSivernell rick]# ll /dev/cd* | more lrwxrwxrwx1 root root3 Jan 10 15:49 /dev/cdrom - sr1 lrwxrwxrwx1 root root9 Jan 12 10:55 /dev/cdrom2 - /dev/scd1 lrwxrwxrwx1 root root6 Dec 21 03:01 /dev/cdu31a - sonycd brw-rw-r-- 1 root disk24, 0 Oct 11 13:07 /dev/cdu535 lrwxrwxrwx1 root root3 Jan 12 10:59 /dev/cdwriter - sr0 [root@RSivernell rick]# ll /dev/sc* | more brw-rw-r--1 rick disk 11, 0 Oct 11 13:07 /dev/scd0 brw-rw-r--1 root disk 11, 1 Oct 11 13:07 /dev/scd1 [root@RSivernell rick]# ll /dev/sr* | more brw---1 rick root 11, 0 Oct 11 13:07 /dev/sr0 brw---1 rick disk 11, 1 Oct 11 13:07 /dev/sr1 [root@RSivernell rick]# cat /etc/fstab devpts /dev/pts devpts gid=5,mode=620 0 0 /proc /proc proc defaults 0 0 none /proc/bus/usb usbdevfs defaults 0 0 /dev/cdrom /mnt/cdrom iso9660 ro,user,noauto,exec 0 0 /dev/cdwriter /mnt/sr0 iso9660 ro,user,noauto,exec 0 0 /dev/cdrom2 /mnt/scd1 is09660 ro,user,noauto,exec 0 0 /dev/fd0 /mnt/floppy auto defaults,user,noauto 0 0 none /dev/shm shm defaults 0 0 /dev/hda1 / reiserfs defaults 1 1 /dev/hda5 /opt reiserfs defaults 1 1 /dev/hda3 /home reiserfs defaults 1 1 /dev/hda2 /boot ext2 defaults 1 1 /dev/hda13 /backup ext2 defaults 1 1 /dev/hda12 /archive reiserfs defaults 1 1 /dev/hda11 /projects reiserfs defaults 1 1 /dev/hda10 /import_export reiserfs defaults 1 1 /dev/hda14 swap swap defaults 0 0 /dev/hda6 /u01 reiserfs user 0 0 /dev/hda7 /u02 reiserfs user 0 0 /dev/hda8 /u03 reiserfs user 0 0 /dev/hda9 /uo4 reiserfs user 0 0 [root@RSivernell rick]# cat /etc/mtab /dev/hda1 / reiserfs rw 0 0 devpts /dev/pts devpts rw,gid=5,mode=620 0 0 /proc /proc proc rw 0 0 none /proc/bus/usb usbdevfs rw 0 0 /dev/hda5 /opt reiserfs rw 0 0 /dev/hda3 /home reiserfs rw 0 0 /dev/hda2 /boot ext2 rw 0 0 /dev/hda13 /backup ext2 rw 0 0 /dev/hda12 /archive reiserfs rw 0 0 /dev/hda11 /projects reiserfs rw 0 0 /dev/hda10 /import_export reiserfs rw 0 0 /dev/hda6 /u01 reiserfs rw,noexec,nosuid,nodev 0 0 /dev/hda7 /u02 reiserfs rw,noexec,nosuid,nodev 0 0 /dev/hda8 /u03 reiserfs rw,noexec,nosuid,nodev 0 0 /dev/hda9 /uo4 reiserfs rw,noexec,nosuid,nodev 0 0 RSivernell:(pid503) /auto nfs
