Re: ide-scsi CDRW and a real SCSI CDROM
Kirk Strauser wrote: I'm running `unstable' on a system with a Samsung IDE CDRW and a Panasonic SCSI CDROM. I've followed various instructions culled from mailing lists, HOWTOs, etc., but I'm still having problems with getting the two to play nicely together. If I enable ide-scsi for the CDRW, I can't find the real SCSI CDROM anywhere. If I don't enable ide-scsi, then the SCSI CDROM is available, but the CDRW is only writeable via ATAPI. Can someone point me toward some documentation on using ide-scsi on a system with real SCSI devices? Many thanks. The real scsi will appear under sdxx such as sda1. There's a cd-write howto, and a scsi howto. scsitools is also useful. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi CDRW and a real SCSI CDROM
At 2003-09-01T11:12:07Z, Russell Shaw [EMAIL PROTECTED] writes: The real scsi will appear under sdxx such as sda1. Except that it doesn't. In fact, it's not even detected in dmesg. What I've done so far: 1) Added this to my grub boot parameters: hde=scsi ignore=hde 2) Created an /etc/modutils/cdrw: # First, get the ide-cd drive to not latch onto /dev/hdd options ide-cd ignore=hde # # # Set up an alias for /dev/scd0 to load sr_mod alias scd1 sr_mod # # # Now get ide-cd followed by ide-scsi loaded before the SCSI drivers pre-install sgmodprobe ide-scsi pre-install sr_modmodprobe ide-scsi pre-install ide-scsi modprobe ide-cd 3) Ran update-modules. 4) Added `ide-scsi' and `sg' to /etc/modules. 5) Rebooted. Anything I missed -- Kirk Strauser pgp0.pgp Description: PGP signature
Re: ide-scsi CDRW and a real SCSI CDROM
On Mon, 01 Sep 2003 10:45:55 -0500 Kirk Strauser [EMAIL PROTECTED] wrote: 1) Added this to my grub boot parameters: hde=scsi ignore=hde Don't know if this is the problem, but this is my line from /etc/lilo.conf append=hdc=ide-scsi hdd=ide-scsi -- -johann koenig Now Playing: Bow Wow Wow - Louis Quatorze : Punk Lives (Disc 2) Today is Prickle-Prickle, the 25th day of Bureaucracy in the YOLD 3169 My public pgp key: http://mental-graffiti.com/pgp/johannkoenig.pgp pgp0.pgp Description: PGP signature
Re: ide-scsi CDRW and a real SCSI CDROM
Kirk Strauser wrote: At 2003-09-01T11:12:07Z, Russell Shaw [EMAIL PROTECTED] writes: The real scsi will appear under sdxx such as sda1. Except that it doesn't. In fact, it's not even detected in dmesg. What I've done so far: 1) Added this to my grub boot parameters: hde=scsi ignore=hde 2) Created an /etc/modutils/cdrw: # First, get the ide-cd drive to not latch onto /dev/hdd options ide-cd ignore=hde # # # Set up an alias for /dev/scd0 to load sr_mod alias scd1 sr_mod # # # Now get ide-cd followed by ide-scsi loaded before the SCSI drivers pre-install sgmodprobe ide-scsi pre-install sr_modmodprobe ide-scsi pre-install ide-scsi modprobe ide-cd 3) Ran update-modules. 4) Added `ide-scsi' and `sg' to /etc/modules. 5) Rebooted. Anything I missed Does lsmod show the low-level driver for the scsi card? If not, put it in /etc/modules. Does lsmod show the rest of the drivers you've attempted? http://www.linuxdocs.org/HOWTOs/SCSI-2.4-HOWTO/index.html http://www.tldp.org/HOWTO/SCSI-Generic-HOWTO/ Drivers for card and scsi system in: cat /proc/scsi Before doing all that stuff in /etc/modutils, i'd try the driver install sequence by hand one step at a time, then duplicate the working sequence with /etc/modules and /etc/modutils. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: ide-scsi CDRW and a real SCSI CDROM
On Sun, 2003-08-31 at 13:09, Kirk Strauser wrote: I'm running `unstable' on a system with a Samsung IDE CDRW and a Panasonic SCSI CDROM. I've followed various instructions culled from mailing lists, HOWTOs, etc., but I'm still having problems with getting the two to play nicely together. If I enable ide-scsi for the CDRW, I can't find the real SCSI CDROM anywhere. If I don't enable ide-scsi, then the SCSI CDROM is available, but the CDRW is only writeable via ATAPI. Can someone point me toward some documentation on using ide-scsi on a system with real SCSI devices? Many thanks. Okay. Tricky. First off I'd like to thank the American Public... (err oops wrong forum) Now seriously, I am to assume you have setup a proper grub stanza in /boot/grub/menu.lst title Linux-ide-scsi root (hd0,0) kernel /vmlinuz-2.4.20-xfs ro \ root=/dev/hda2 hde=ide-scsi initrd /initrd.img-2.4.20-xfs Then you have put in your SCSI Controller's module in /etc/modules as well as sr_mod and any other modules needed. You should be able to get at your IDE-CD-RW and your Panasonic SCSI CD-ROM. -- greg, [EMAIL PROTECTED] REMEMBER ED CURRY! http://www.iwethey.org/ed_curry Sound barricades itself into rolls of peautbutter when you speak. signature.asc Description: This is a digitally signed message part
Re: ide-scsi CDRW and a real SCSI CDROM
At 2003-09-01T17:01:05Z, Greg Folkert [EMAIL PROTECTED] writes: Then you have put in your SCSI Controller's module in /etc/modules as well as sr_mod and any other modules needed. I am a complete toolshed. I actually realized that I hadn't loaded my SCSI adapter module about 2 minutes after I posted this morning. Thanks for the accurate advice, and sorry for wasting anybody's time. -- Kirk Strauser pgp0.pgp Description: PGP signature
Re: ide-scsi CDRW and a real SCSI CDROM
On Mon, Sep 01, 2003 at 09:12:07PM +1000, Russell Shaw wrote: Kirk Strauser wrote: I'm running `unstable' on a system with a Samsung IDE CDRW and a Panasonic SCSI CDROM. I've followed various instructions culled from mailing lists, HOWTOs, etc., but I'm still having problems with getting the two to play nicely together. If I enable ide-scsi for the CDRW, I can't find the real SCSI CDROM anywhere. If I don't enable ide-scsi, then the SCSI CDROM is available, but the CDRW is only writeable via ATAPI. Can someone point me toward some documentation on using ide-scsi on a system with real SCSI devices? Many thanks. The real scsi will appear under sdxx such as sda1. There's a cd-write howto, and a scsi howto. scsitools is also useful. sdxx is for hard drives - CD drives appear as /dev/scdx. I have a SCSI CD-RW which is /dev/scd0. Unfortunately I don't have any IDE CD drives on that box, so I'm afraid I can't help on the main problem. -- Pigeon Be kind to pigeons Get my GPG key here: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x21C61F7F pgp0.pgp Description: PGP signature
ide-scsi CDRW and a real SCSI CDROM
I'm running `unstable' on a system with a Samsung IDE CDRW and a Panasonic SCSI CDROM. I've followed various instructions culled from mailing lists, HOWTOs, etc., but I'm still having problems with getting the two to play nicely together. If I enable ide-scsi for the CDRW, I can't find the real SCSI CDROM anywhere. If I don't enable ide-scsi, then the SCSI CDROM is available, but the CDRW is only writeable via ATAPI. Can someone point me toward some documentation on using ide-scsi on a system with real SCSI devices? Many thanks. -- Kirk Strauser pgp0.pgp Description: PGP signature
Re: SOLVED IT! Permissions and scsi cdrom?
I found the answer! Sg0 sg1, etc. for generic scsi, which get used somehow but aren't actually linked to scd0 and scd1 or /cdrom etc., has permissions that don't allow you to access them as a user. since sg0 and sg1 etc. don't belong to the cdrom group either, this doesn't help any. I changed my permissions for the relevant sg drives to 766 (actually, I think 666 would have been ok) and now abcde and cdparanoia work fine for me as a user. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SOLVED IT! Permissions and scsi cdrom?
On Fri, 5 Apr 2002, Cheryl Homiak wrote: I found the answer! Sg0 sg1, etc. for generic scsi, which get used somehow but aren't actually linked to scd0 and scd1 or /cdrom etc., has permissions that don't allow you to access them as a user. since sg0 and sg1 etc. don't belong to the cdrom group either, this doesn't help any. I changed my permissions for the relevant sg drives to 766 (actually, I think 666 would have been ok) and now abcde and cdparanoia work fine for me as a user. you got it! in my case, the device is sg3... chmodded it to 666 and made sure to change the generic scsi device name in grip: config:rip. thanks -- Dave Mallery, K5EN (r/h 7.2 krud; debian woody+ximian) PO Box 520 Ramah, NM 87321 no gates .~. no windows... /V\ /( )\ running GNU/Linux ^^-^^ (Linux TM Linus Torvalds) free at last! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Permissions and scsi cdrom?
I now have both a cdrom and a cdrw on my machine. They are both ide/atapi but i am using scsi emulation; the cdrw is scd0 and the cdrom is scd1. I have no problem accessing the cdrom or the cdrw as far as mounting or listening to audio cds. However, when I try to run abcde and/or cdparanoia I get errors about unable to open cdrom. when I run cdparanoia with the -v option, the indication is Checking /dev/cdrom for cdrom... Testing /dev/cdrom for cooked ioctl() interface /dev/scd1 is not a cooked ioctl CDROM. Testing /dev/cdrom for SCSI interface No generic SCSI device found to match CDROM device /dev/scd1 Yet when I run abcde and/or cdparanoia as root, there is no problem. I assume this is some kind of permissions problem, but I can't seem to find the source of it. /dev/cdrom is the symlink to /dev/scd1 and /dev/cdrecord is the symlink to /dev/scd0. I am also a member of the cdrom group. I didn't have any trouble with these programs before converting to scsi. Can anybody see what I need to change here? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Permissions and scsi cdrom?
On Sat, 30 Mar 2002, Cheryl Homiak wrote: I now have both a cdrom and a cdrw on my machine. They are both ide/atapi but i am using scsi emulation; the cdrw is scd0 and the cdrom is scd1. I have no problem accessing the cdrom or the cdrw as far as mounting or listening to audio cds. However, when I try to run abcde and/or cdparanoia I get errors about unable to open cdrom. when I run cdparanoia with the -v option, the indication is Checking /dev/cdrom for cdrom... Testing /dev/cdrom for cooked ioctl() interface /dev/scd1 is not a cooked ioctl CDROM. Testing /dev/cdrom for SCSI interface No generic SCSI device found to match CDROM device /dev/scd1 on a r/h machine that works: orch:~ cdparanoia -Qsv cdparanoia III release 9.8 (March 23, 2001) Checking /dev/cdrom for cdrom... Testing /dev/cdrom for cooked ioctl() interface /dev/scd0 is not a cooked ioctl CDROM. Testing /dev/cdrom for SCSI interface generic device: /dev/sg1 ioctl device: /dev/scd0 notice the /dev/sg1 generic device zorch:~ ll /dev/cdrom lrwxrwxrwx1 root root9 Feb 7 16:23 /dev/cdrom - /dev/scd0 zorch:~ ll /dev/scd0 brw---1 dmallery disk 11, 0 Aug 30 2001 /dev/scd0 zorch:~ ll /dev/sg1 crw---1 dmallery disk 21, 1 Aug 30 2001 /dev/sg1 zorch:~ one machine over, running woody: bilbo:~ cdparanoia =Qsv /dev/cdrom exists but isn't accessible. By default, cdparanoia stops searching for an accessible drive here. Consider using -sv to force a more complete autosense of the machine. More information about /dev/cdrom: Checking /dev/cdrom for cdrom... Testing /dev/cdrom for cooked ioctl() interface /dev/scd0 is not a cooked ioctl CDROM. Testing /dev/cdrom for SCSI interface No generic SCSI device found to match CDROM device /dev/scd0 bilbo:~ ll /dev/cdrom lrwxrwxrwx1 root audio 3 Mar 12 12:29 /dev/cdrom - sr0 bilbo:~ ll /dev/sr0 lrwxrwxrwx1 root audio 4 Mar 12 12:29 /dev/sr0 - scd0 bilbo:~ ll /dev/scd0 brw-rw-rw-1 dmallery audio 11, 0 Jun 13 2001 /dev/scd0 bilbo:~ groups dmallery audio i guess this is a common problem... i wish someone could explain this generic device Yet when I run abcde and/or cdparanoia as root, there is no problem. I assume this is some kind of permissions problem, but I can't seem to find the source of it. /dev/cdrom is the symlink to /dev/scd1 and /dev/cdrecord is the symlink to /dev/scd0. I am also a member of the cdrom group. I didn't have any trouble with these programs before converting to scsi. Can anybody see what I need to change here? ^ we -- Dave Mallery, K5EN (r/h 7.2 krud; debian woody+ximian) PO Box 520 Ramah, NM 87321 no gates .~. no windows... /V\ /( )\ running GNU/Linux ^^-^^ (Linux TM Linus Torvalds) free at last! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
IDE/SCSI cdrom
Hey guys. I have a burner that I'm using in Linux via scsi emulation, and a normal ATAPI CD-ROM. Under 2.2.18, by adding append=hdc=ide-scsi to my lilo.conf file, I forced my burner to be handled by the scsi emulation driver. My cdrom on /dev/hdd was left as an IDE device. Now, I'm running kernel 2.4.4, with the same config. For some reason though, the ide-scsi module is grabbing both devices. I want it to just grab /dev/hdc, and not /dev/hdd. I tried adding append=hdd=ide-cd before the above append line, but that didn't help. Any ideas? Thanks, Mike -- Michael P. Soulier [EMAIL PROTECTED] With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead. -- RFC 1925 pgpy7hLttGZcc.pgp Description: PGP signature
Re: install help with a SCSI CDROM on a 486
ummm... does it say something like no pci bios found in the bootup messages? I had a compaq 486 that had scsi and net built in and never could get linux to run on it. Compaq had done something funny with the pci bios. It was located above normal accessable memory. There was a tool to relocate the pci bios down to where it was supposed to go (available for download from compaq). This was back in the deb 1.1 or 1.2 days (just after the switch to elf). The it says something that no pci found as well is correct since it only has ISA, the SCSI card is not builtin but was a bought Adaptec. The program is called movepci you need to load movepci.sys with DOS prior to loading Linux. A common problem also with Netware since this patch was originally for it. I really don't think that this is the problem since the SCSI card is a typical ISA card(i.e. IRQ 10, mem add 0x140, SCSI adapter#7). The problem is that Linux doesn't find on autoprobe and you must pass the parameters to it. The problem is that I cannot find a straight definitive answer on where this is done. This is starting to remind me of trying to get an honest answer out of a politician.
install help with a SCSI CDROM on a 486
I've been fighting this Debian install for 3 weeks and am about tired of it. If I don't get an answer here, then I am taking the damn CD to the skeet range. OK, here is what I got: Debian 2.1 bootable CD, official type that comes in the box, has the Debian tm logo on it and the O'Rielly cow book in the box with it Desired packages: Perl(full install not just the basic package), Python, gcc, apache/httpd, mySQL Compaq Prolinea 4/66 20megsRAM a 486 Fujitsu 4.3 HD partitioned as: hda1 := 2048 hda5 := 1024 copied the Debian CD here in /Debian using xcopy in DOS hda6 := 1024 copied W31 W95 here to make it easier to reinstall hda7 := 0033 Linux swap from previous install attempts hda8 := 0033 somehow generated in one of the install attempts, delete later Netgear/Bay Network EA201 D2 NIC Adaptec AVA-1505A hooked to an internal IBM/Matsuhita CR-503-C CDROM is at SCSI#3 during DOS bootup it shows the card as Host Adapter #0 Port 140h Interrupt 10 Host Adapter SCSI ID = 7 One of the references that I found is at http://customer.support.redhat.com/rhoaprod/plsql/xxrh_know_pkg.srch2?p_id=1 20 and its example was aha152x=0x340,10,7 however, I believe that I should have aha152x=0x140,10,7 due to the IO address Now I can click Win95 Start, Shutdown to DOS, go to the CDROM as I:\ in Win98DOS, cd install, invoke boot.bat, select color, select USA keyboard, partition hda1 as ext2~Write~yes,~Quit initactivate swap hda7, init /dev/hda1, skip the bad block check since it has been done about 20 times without finding anything, mount as /, Install Operating System Kernel and Modules, Select CDROM as medium, select /dev/scd0 : SCSI, and bleewy NO SCSI ADAPTER DETECTED The question remains, where do I tell Debian to aha152x=0x140,10,7 in this process?? I don't see a place to pass these parameters to the install program. What am I missing??? Also, when I get to modules, what module do I load for the NIC?? Any help will be appreciated, Will
Re: install help with a SCSI CDROM on a 486
On Fri, 14 Apr 2000, [EMAIL PROTECTED] wrote: I've been fighting this Debian install for 3 weeks and am about tired of it. If I don't get an answer here, then I am taking the damn CD to the skeet range. OK, here is what I got: Debian 2.1 bootable CD, official type that comes in the box, has the Debian tm logo on it and the O'Rielly cow book in the box with it Desired packages: Perl(full install not just the basic package), Python, gcc, apache/httpd, mySQL Compaq Prolinea 4/66 20megsRAM a 486 Fujitsu 4.3 HD partitioned as: hda1 := 2048 hda5 := 1024 copied the Debian CD here in /Debian using xcopy in DOS hda6 := 1024 copied W31 W95 here to make it easier to reinstall hda7 := 0033 Linux swap from previous install attempts hda8 := 0033 somehow generated in one of the install attempts, delete later Netgear/Bay Network EA201 D2 NIC Adaptec AVA-1505A hooked to an internal IBM/Matsuhita CR-503-C CDROM is at SCSI#3 during DOS bootup it shows the card as Host Adapter #0 Port 140h Interrupt 10 Host Adapter SCSI ID = 7 One of the references that I found is at http://customer.support.redhat.com/rhoaprod/plsql/xxrh_know_pkg.srch2?p_id=1 20 and its example was aha152x=0x340,10,7 however, I believe that I should have aha152x=0x140,10,7 due to the IO address Now I can click Win95 Start, Shutdown to DOS, go to the CDROM as I:\ in Win98DOS, cd install, invoke boot.bat, select color, select USA keyboard, partition hda1 as ext2~Write~yes,~Quit initactivate swap hda7, init /dev/hda1, skip the bad block check since it has been done about 20 times without finding anything, mount as /, Install Operating System Kernel and Modules, Select CDROM as medium, select /dev/scd0 : SCSI, and bleewy NO SCSI ADAPTER DETECTED The question remains, where do I tell Debian to aha152x=0x140,10,7 in this process?? I don't see a place to pass these parameters to the install program. What am I missing??? You don't have to tell it to the install program, you have to tell it to the kernel. When you boot the cd you get the kernel boot: line on the very first screen; you have to enter the params here. You can also get some help by pressing F1.
RE: install help with a SCSI CDROM on a 486
I've been fighting this Debian install for 3 weeks and am about tired of it. If I don't get an answer here, then I am taking the damn CD to the skeet range. OK, here is what I got: Debian 2.1 bootable CD, official type that comes in the box, has the Debian tm logo on it and the O'Rielly cow book in the box with it Desired packages: Perl(full install not just the basic package), Python, gcc, apache/httpd, mySQL Compaq Prolinea 4/66 20megsRAM a 486 ummm... does it say something like no pci bios found in the bootup messages? I had a compaq 486 that had scsi and net built in and never could get linux to run on it. Compaq had done something funny with the pci bios. It was located above normal accessable memory. There was a tool to relocate the pci bios down to where it was supposed to go (available for download from compaq). This was back in the deb 1.1 or 1.2 days (just after the switch to elf). The newer kernels should pick up on this, I think. Check your boot up messages to confirm that it does recognize the pci bus. If it does, then using the boot options (as mentioned in another response) should get you there. If not, I'll look through the dust and see if I still have that utility from Compaq. jim Fujitsu 4.3 HD partitioned as: hda1 := 2048 hda5 := 1024 copied the Debian CD here in /Debian using xcopy in DOS hda6 := 1024 copied W31 W95 here to make it easier to reinstall hda7 := 0033 Linux swap from previous install attempts hda8 := 0033 somehow generated in one of the install attempts, delete later Netgear/Bay Network EA201 D2 NIC Adaptec AVA-1505A hooked to an internal IBM/Matsuhita CR-503-C CDROM is at SCSI#3 during DOS bootup it shows the card as Host Adapter #0 Port 140h Interrupt 10 Host Adapter SCSI ID = 7 One of the references that I found is at http://customer.support.redhat.com/rhoaprod/plsql/xxrh_know_pkg.srch2?p_id =1 20 and its example was aha152x=0x340,10,7 however, I believe that I should have aha152x=0x140,10,7 due to the IO address Now I can click Win95 Start, Shutdown to DOS, go to the CDROM as I:\ in Win98DOS, cd install, invoke boot.bat, select color, select USA keyboard, partition hda1 as ext2~Write~yes,~Quit initactivate swap hda7, init /dev/hda1, skip the bad block check since it has been done about 20 times without finding anything, mount as /, Install Operating System Kernel and Modules, Select CDROM as medium, select /dev/scd0 : SCSI, and bleewy NO SCSI ADAPTER DETECTED The question remains, where do I tell Debian to aha152x=0x140,10,7 in this process?? I don't see a place to pass these parameters to the install program. What am I missing??? Also, when I get to modules, what module do I load for the NIC?? Any help will be appreciated, Will -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null
Re: install help with a SCSI CDROM on a 486
Lewis, James M. wrote: I've been fighting this Debian install for 3 weeks and am about tired of it. If I don't get an answer here, then I am taking the damn CD to the skeet range. OK, here is what I got: Debian 2.1 bootable CD, official type that comes in the box, has the Debian tm logo on it and the O'Rielly cow book in the box with it [snip] One of the references that I found is at http://customer.support.redhat.com/rhoaprod/plsql/xxrh_know_pkg.srch2?p_id =1 20 and its example was aha152x=0x340,10,7 however, I believe that I should have aha152x=0x140,10,7 due to the IO address [snip] The question remains, where do I tell Debian to aha152x=0x140,10,7 in this process?? I don't see a place to pass these parameters to the install program. What am I missing??? aha, indeed. that looks like a job for lilo, the linux loader. it reads a file /etc/lilo.conf which contains various setup directives like that. there's a liloconfig program that may help or hinder, depending on what you need to tweak. check man lilo man lilo.conf man lilo.config of course, i could be wrong. :) Also, when I get to modules, what module do I load for the NIC?? that's beyond me, just yet. (i know how you feel--i've been trying to get my debian going for about three weeks too... but i think i'm finally there!) Any help will be appreciated, Will
Upgrading kernel, scsi cdrom, xcdroast
A few days ago I made a fresh standard install of slink, after that I did an upgrade pointing to frozen my apt-get, which came out very smoothly (only procmail was not found). Any way, after having upgraded I decided to upgrade my kernel also, so I did apt-get -f install kernel-source-2.2.14, run bz2cat, make menuconfig, make dep, make bzImage, make bzlilo(?-quoting from memory, followed instructions in kernel howto), make bzdisk. The problem: uname -a shows kernel 2.2.14, but despite making sure that SCSI generic support was added for CDroms, when I run xcdroast it tells me that my kernel does not have scsi support. Where is the mistake? Also, what would be a better way, more debian-like, of creating my own kernel image? I found make-kpkg somehow more difficult than the method outlined in the howto. Thnks, Antonio.
begging for help, PCMCIA-SCSI-CDROM - I am close, but no cigar :(
Hello, I am on my knees begging for help at this point :) - :( I am trying to get my JVC XR-W2040 CDROM drive to work under debian linux as my other CDROM is very flaky even when it is sometimes seen at bootup. I think I am EXTREMELY close, and would really appreciated any help. I have been studying the PCMCIA-Howto, but can't get any farther on my own. I even re-installed 2.1 debian last night, to erase previous attempts and start clean. The system actually sees it as a JVC CDROM, on PCMCIA-SCSI adapter which is a new media bus toaster. It says it is at sr0, but something is going wrong, and it is not really seen. I am not sure if the statement about reseting the SCSI bus for the second half of retries is an error or not. ? I have included much information in this post in an attempt to allow someone with experience to perhaps see what is wrong. It may be as simple as trying to use IRQ3, when it might actually be using IRQ3 for a serial device. There is really only one serial port on my thinkpad 560, I have no idea why it tries to configure 2 of them. I have included below: (if more is needed I will comply ASAP) what I added to /etc/pcmcia/config cardctl config output (looks OK to me) cardctl ident output (looks OK to me) /var/run/stab (says both sockets are empty) /var/log/daemon.log (appears to actually load the SCSI modules) dmesg output (complete, notice the 2 serial ports, and the JVC CDROM at sr0) (from /etc/pcmcia/config) device aha152x_cs #jm class scsi module aha152x_cs class scsi module scsi/scsi_mod,scsi/sd_mod,scsi/sr_mod,aha152x_cs (cardctl config) Socket 0: Vcc = 5.0, Vpp1 = 0.0, Vpp2 = 0.0 Socket 1: Vcc = 5.0, Vpp1 = 0.0, Vpp2 = 0.0 Interface type is memory and I/O IRQ 3 is exclusive, level mode, enabled Function 0: Config register base = 0x0100 Option = 0x60 I/O window 1: 0x0100 to 0x011f, auto sized (cardctl ident) Socket 0: product info: Hayes, OPTIMA 336 + FAX for PCMCIA, 533PAM, V4.4 manfid: 0x010a, 0x function: 2 (serial) Socket 1: product info: New Media, SCSI, Bus Toaster manfid: 0x0057, 0xd302 function: 0 (multifunction) (/var/log/daemon.log) Oct 9 19:17:08 debian cardmgr[102]: starting, version is 3.0.5 Oct 9 19:17:08 debian cardmgr[102]: watching 2 sockets Oct 9 19:17:08 debian cardmgr[102]: initializing socket 1 Oct 9 19:17:08 debian cardmgr[102]: socket 1: New Media Bus Toaster SCSI Oct 9 19:17:08 debian kerneld: started, pid=109, qid=0 Oct 9 19:17:08 debian cardmgr[102]: executing: 'insmod /lib/modules/2.0.36/scsi/scsi_mod.o' Oct 9 19:17:08 debian cardmgr[102]: executing: 'insmod /lib/modules/2.0.36/scsi/sd_mod.o' Oct 9 19:17:08 debian cardmgr[102]: executing: 'insmod /lib/modules/2.0.36/scsi/sr_mod.o' Oct 9 19:17:09 debian cardmgr[102]: executing: 'insmod /lib/modules/2.0.36/pcmcia/aha152x_cs.o' (dmesg output) Memory: sized by int13 088h Console: 16 point font, 400 scans Console: colour VGA+ 80x25, 1 virtual console (max 63) pcibios_init : BIOS32 Service Directory structure at 0x000fd870 pcibios_init : BIOS32 Service Directory entry at 0xfd880 pcibios_init : PCI BIOS revision 2.10 entry at 0xfd8c0 Probing PCI hardware. Calibrating delay loop.. ok - 53.04 BogoMIPS Memory: 22748k/24576k available (728k kernel code, 384k reserved, 716k data) Swansea University Computer Society NET3.035 for Linux 2.0 NET3: Unix domain sockets 0.13 for Linux NET3.035. Swansea University Computer Society TCP/IP for NET3.034 IP Protocols: IGMP, ICMP, UDP, TCP VFS: Diskquotas version dquot_5.6.0 initialized Checking 386/387 coupling... Ok, fpu using exception 16 error reporting. Checking 'hlt' instruction... Ok. Intel Pentium with F0 0F bug - workaround enabled. alias mapping IDT readonly ... ... done Linux version 2.0.36 ([EMAIL PROTECTED]) (gcc version 2.7.2.3) #1 Sun Feb 21 18:29:09 EST 1999 Starting kswapd v 1.4.2.2 Real Time Clock Driver v1.09 tpqic02: Runtime config, $Revision: 0.4.1.5 $, $Date: 1994/10/29 02:46:13 $ tpqic02: DMA buffers: 20 blocks, at address 0x1f0400 (0x1f037c) Ramdisk driver initialized : 16 ramdisks of 4096K size loop: registered device at major 7 hda: IBM-DTNA-22110, 2016MB w/96kB Cache, CHS=1024/64/63 ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Floppy drive(s): fd0 is 1.44M FDC 0 is a National Semiconductor PC87306 md driver 0.36.3 MAX_MD_DEV=4, MAX_REAL=8 Partition check: hda: hda1 hda2 hda5 hda6 VFS: Mounted root (ext2 filesystem) readonly. Adding Swap: 50364k swap-space (priority -1) Serial driver version 4.13 with no serial options enabled tty00 at 0x03f8 (irq = 4) is a 16550A tty01 at 0x02f8 (irq = 3) is a 16550A Linux PCMCIA Card Services 3.0.5 kernel build: 2.0.36 unknown options: [pci] [cardbus] Intel PCIC probe: Cirrus PD6729 PCI at port 0x3e0 ofs 0x00, 2 sockets host opts [0]: [ring] [1/6/8] [1/20/8] host opts [1]: [ring] [1/6/8] [1/20/8] ISA irqs (default) = 3,4,5,7,9,10,11,12 status change on irq 11 cs: IO port probe 0x1000-0x17ff: excluding 0x15e8-0x15ef cs: IO port probe
Re: begging for help, PCMCIA-SCSI-CDROM - I am close, but no cigar :(
On Sat, 9 Oct 1999, John Miskinis wrote: I am trying to get my JVC XR-W2040 CDROM drive to work under debian linux as my other CDROM is very flaky even when it is sometimes seen at bootup. I think I am EXTREMELY close, and would really appreciated any help. I have been studying the PCMCIA-Howto, but can't get any farther on my own. I even re-installed 2.1 debian last night, to erase previous attempts and start clean. Hey, debian linux is not windows ;-) [...] I have included much information in this post in an attempt to allow someone with experience to perhaps see what is wrong. It may be as simple as trying to use IRQ3, when it might actually be using IRQ3 for a serial device. There is really only one serial port on my thinkpad 560, I have no idea why it tries to configure 2 of them. I have included below: (if more is needed I will comply ASAP) tty00 at 0x03f8 (irq = 4) is a 16550A tty01 at 0x02f8 (irq = 3) is a 16550A AFAIK your TP 560 has a IR port, this is one of two ports, the other is the serial port. Martin -- If the box says 'Windows 95 or better', it should run on Linux, right? - anonymous For public PGP-key: finger [EMAIL PROTECTED]
PCMCIA-SCSI-CDROM - Requested xconsole info
Hello (and Thanks for continued help), I have included the xconsole output, when I insert the card after the system is up. I also included what is output when I pulled out the card, as it notes that the SW INT is set and Why?. I also made the /dev/sr0 device from /dev with: mkmod -m 777 sr0 b11 1 (this is what went to xconsole when I put in the card) Oct 10 11:06:37 debian cardmgr[101]: socket 1: New Media Bus Toaster SCSI Oct 10 11:06:37 debian kernel: cs: memory probe 0x0d-0x0d: clean. Oct 10 11:06:37 debian cardmgr[101]: executing: 'insmod /lib/modules/2.0.36/scsi/scsi_mod.o' Oct 10 11:06:37 debian cardmgr[101]: executing: 'insmod /lib/modules/2.0.36/scsi/sd_mod.o' Oct 10 11:06:37 debian cardmgr[101]: executing: 'insmod /lib/modules/2.0.36/scsi/sr_mod.o' Oct 10 11:06:37 debian cardmgr[101]: executing: 'insmod /lib/modules/2.0.36/pcmcia/aha152x_cs.o' Oct 10 11:06:39 debian kernel: aha152x: processing commandline: ok Oct 10 11:06:39 debian kernel: aha152x: BIOS test: passed, detected 1 controller(s) Oct 10 11:06:39 debian kernel: aha152x0: vital data: PORTBASE=0x100, IRQ=9, SCSI ID=7, reconnect=enabled, parity=enabled, synchronous=disabled, delay=100, extended translation=disabled Oct 10 11:06:39 debian kernel: aha152x: trying software interrupt, ok. Oct 10 11:06:39 debian kernel: scsi0 : Adaptec 152x SCSI driver; $Revision: 1.18 $ Oct 10 11:06:39 debian kernel: scsi : 1 host. Oct 10 11:06:42 debian kernel: Vendor: JVC Model: XR-W2040 Rev: 1.12 Oct 10 11:06:42 debian kernel: Type: CD-ROM ANSI SCSI revision: 02 Oct 10 11:06:42 debian kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0 Oct 10 11:06:42 debian kernel: scsi0 channel 0 : resetting for second half of retries. Oct 10 11:06:42 debian kernel: SCSI bus is being reset for host 0 channel 0. (when I removed card later, I saw) Oct 10 11:22:43 debian kernel: aha152x: SWINT is set! Why? Oct 10 11:22:43 debian kernel: QUEUE STATUS: Oct 10 11:22:43 debian kernel: issue_SC: Oct 10 11:22:43 debian kernel: current_SC: Oct 10 11:22:43 debian kernel: none Oct 10 11:22:43 debian kernel: disconnected_SC: Oct 10 11:22:43 debian kernel: enabled interrupts (ENSELDO ENSELDI ENSELINGO ENSWRAP ENSDONE ENSPIORDY ENDMADONE ENSELTIMO ENATNTARG ENPHASEMIS ENBUSFREE ENSCSIPERR ENPHASECHG ENREQINIT ) Oct 10 11:22:43 debian kernel: Device busy??? __ Get Your Private, Free Email at http://www.hotmail.com
Re: PCMCIA-SCSI-CDROM - Requested xconsole info
On Sun, 10 Oct 1999, John Miskinis wrote: Hello (and Thanks for continued help), I have included the xconsole output, when I insert the card after the system is up. I also included what is output when I pulled out the card, as it notes that the SW INT is set and Why?. I also made the /dev/sr0 device from /dev with: mkmod -m 777 sr0 b11 1 (this is what went to xconsole when I put in the card) Oct 10 11:06:37 debian cardmgr[101]: socket 1: New Media Bus Toaster SCSI Oct 10 11:06:37 debian kernel: cs: memory probe 0x0d-0x0d: clean. Oct 10 11:06:37 debian cardmgr[101]: executing: 'insmod /lib/modules/2.0.36/scsi/scsi_mod.o' Oct 10 11:06:37 debian cardmgr[101]: executing: 'insmod /lib/modules/2.0.36/scsi/sd_mod.o' Oct 10 11:06:37 debian cardmgr[101]: executing: 'insmod /lib/modules/2.0.36/scsi/sr_mod.o' Oct 10 11:06:37 debian cardmgr[101]: executing: 'insmod /lib/modules/2.0.36/pcmcia/aha152x_cs.o' Oct 10 11:06:39 debian kernel: aha152x: processing commandline: ok Oct 10 11:06:39 debian kernel: aha152x: BIOS test: passed, detected 1 controller(s) Oct 10 11:06:39 debian kernel: aha152x0: vital data: PORTBASE=0x100, IRQ=9, SCSI ID=7, reconnect=enabled, parity=enabled, synchronous=disabled, delay=100, extended translation=disabled Oct 10 11:06:39 debian kernel: aha152x: trying software interrupt, ok. Oct 10 11:06:39 debian kernel: scsi0 : Adaptec 152x SCSI driver; $Revision: 1.18 $ Oct 10 11:06:39 debian kernel: scsi : 1 host. Oct 10 11:06:42 debian kernel: Vendor: JVC Model: XR-W2040 Rev: 1.12 Oct 10 11:06:42 debian kernel: Type: CD-ROM ANSI SCSI revision: 02 Oct 10 11:06:42 debian kernel: Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0 Oct 10 11:06:42 debian kernel: scsi0 channel 0 : resetting for second half of retries. Oct 10 11:06:42 debian kernel: SCSI bus is being reset for host 0 channel 0. And then there should come sooner or later a message like cardmgr: executing: './scsi start sr0' or something like this ... but obvious this doesn't happen ... perhaps (I have no personal experience with PCMCIA scsi cards :) the wrong driver, here a quote from /usr/doc/pcmcia-cs/SUPPORTED.CARDS.gz: [ Be careful. Many vendors. particularly CD-ROM vendors, seem to switch controller chips more or less at will. Generally, they'll use a different product code, but not always: older (supported) New Media Bus Toaster cards are not easily distinguishable from the current Symbios-based cards, which use the contributed 53c500 driver, distributed separately. ] Try this: Have a look at /etc/pcmcia/config and change card New Media Bus Toaster SCSI version New Media, SCSI, Bus Toaster bind aha152x_cs in card New Media Bus Toaster SCSI version New Media, SCSI, Bus Toaster bind sym53c500_cs so that the other driver is loaded. Restart PCMCIA services (/etc/init.d/pcmcia restart) and insert the card again... (To mount the drive, a mount /cdrom should be suficient, after the card is recogniced correctly ... acording to the source code). Martin PS: If that won't work, consider compiling a newer version of PCMCIA service... -- If the box says 'Windows 95 or better', it should run on Linux, right? - anonymous For public PGP-key: finger [EMAIL PROTECTED]
Re: hardware block size on scsi cdrom
Strange, I thought the default block size for an ISO9660 filesystem was 2048. I'm not sure what this block size refers too. I'm not sure what exactly would happen if you changed it. Pierfrancesco Caci wrote: I have a scsi cdrom (Plextor) and a scsi cdwriter (Yamaha). They both have a jumper to set the block size to 1024 bytes or to 512 bytes. The manuals say that for Unix 512 is the good value. Do you have any suggestions? What does this value mean, after all? Pf -- --- Pierfrancesco Caci | mailto:[EMAIL PROTECTED] - http://gusp.infogroup.it ik5pvx| http://www.geocities.com/SoHo/Lofts/8999 Firenze - Italia | Office for the Complication of Otherwise Simple Affairs Linux penny 2.2.10 #1 Tue Jun 15 21:03:12 CEST 1999 i586 unknown -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null -- Jens B. Jorgensen [EMAIL PROTECTED]
hardware block size on scsi cdrom
I have a scsi cdrom (Plextor) and a scsi cdwriter (Yamaha). They both have a jumper to set the block size to 1024 bytes or to 512 bytes. The manuals say that for Unix 512 is the good value. Do you have any suggestions? What does this value mean, after all? Pf -- --- Pierfrancesco Caci | mailto:[EMAIL PROTECTED] - http://gusp.infogroup.it ik5pvx| http://www.geocities.com/SoHo/Lofts/8999 Firenze - Italia | Office for the Complication of Otherwise Simple Affairs Linux penny 2.2.10 #1 Tue Jun 15 21:03:12 CEST 1999 i586 unknown
SCSI cdrom mounting, #2
To: The Debian Gang - A howdy to all: Since I posted my message yesterday on debian-user about having problems mounting my Hitachi CDR-1750S cdrom I have found out some additional information. As a review, the problems is that when I give the following command mount -t iso9660 /dev/scd0 /mnt my Debian system starts a continous one line message loop that can't be broken out of: not even Ctrl-Alt-Del. Please see my previous message for more details of what I did. Now the additional information. 1. I decided to try out the possibility that there was a termination problem, or bad cable, in my external SCSI line. Therefore I put a termination plug on the outside of my SCSI card and tried to mount something with the above mount command. Of course, nothing would be able to mount, but I wanted to see if the endless one line message loop happened. It did not, and returned the following error message. mount: the kernel does not recognize /dev/scd0 as a block device (maybe `insmod driver'?) 2. Therefore, I moved the termination plug so that there was a cable from the SCSI card to the Hitachi cdrom, and the termination plug was used to terminate the SCSI line after the cdrom. I left the Hitachi cdrom off, and issued the same mount command. There was no endless one line message loop and the follow error message received. SCSI error: host 0 id 3 lun 0 return code = 2701 o(very small o)Sense class 0, sense error 0, extended sense 0 These two lines were repeated many times with a few additional lines thrown in. 3. I next turned the Hitchi cdrom on and ran the same mount command listed above. Under these conditions, Debian went into the endless one line loop bit again. By the way, for those who have not seen my first post on this, the endless one line message is as follows. Aiee scheduling in interrupt 001260b1 4. Lastly, again as a check, I boot my main Slackware partition and again run the same mount command, and the Hitachi cdrom is mounted and functional. CONCLUSION - Well, I'm still stumped for a solution to this problem. Does anyone have any suggestions as to where I go from here toward a solution? Wes Jennings * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * We must be land stewards. . . . for our future depends on it! * * Wes Jennings, soil scientist [EMAIL PROTECTED] 1-253-474-5432 * * Puget Land Consultants P.O. Box 9635 Tacoma, WA 98409 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
scsi cdrom
Hello I hope I'm not in the dark about this due to mental deficiancy. I can't seem to mount my cdrom. I have a buslogic bt946c controlling a 1gig drive and a chinon 1X cdrom. It recognizes the cdrom at boot buty I cannot mount it. I either get special device not found error or not a valid block device error. Is this a common newbie (yes, I am) error? Thanks Paul -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: scsi cdrom
I hope I'm not in the dark about this due to mental deficiancy. I can't seem to mount my cdrom. I have a buslogic bt946c controlling a 1gig drive and a chinon 1X cdrom. It recognizes the cdrom at boot buty I cannot mount it. I either get special device not found error or not a valid block device error. Is this a common newbie (yes, I am) error? Could you please give the command you use to mount CD-ROM? During boot you see messages from the kernel about recognized devices. It should say that it sees the CD-ROM as a device (something like) /dev/sr0 You would then mount it with mount -t iso9660 /dev/sr0 /mnt Alex Y. -- _ _( )_ ( (o___ +---+ | _ 7 |Alexander Yukhimets| \()| http://pages.nyu.edu/~aqy6633/ | / \ \ +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: scsi cdrom
On Wed, 27 May 1998, Phlip wrote: Date: Wed, 27 May 1998 18:17:38 -0700 From: Phlip [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: scsi cdrom Resent-Date: 28 May 1998 01:15:17 - Resent-From: debian-user@lists.debian.org Resent-cc: recipient list not shown: ; Hello I hope I'm not in the dark about this due to mental deficiancy. I can't seem to mount my cdrom. I have a buslogic bt946c controlling a 1gig drive and a chinon 1X cdrom. It recognizes the cdrom at boot buty I cannot mount it. I either get special device not found error or not a valid block device error. Is this a common newbie (yes, I am) error? Thanks Paul Well, I had(and still have at times) I forget that cdroms are represented in /dev as scd _not_ sd[123456]. George -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: scsi cdrom
On Wed, May 27, 1998 at 06:17:38PM -0700, Phlip wrote: I hope I'm not in the dark about this due to mental deficiancy. I can't seem to mount my cdrom. I have a buslogic bt946c controlling a 1gig drive and a chinon 1X cdrom. What name do you try? It should be /dev/scd0 if it is the only SCSI cdrom you have. It could also be necessary to load the SCSI-cdrom driver before, so if the sequence # modprobe sr_mod # mount /dev/scd0 /cdrom does not work, I don't know what could be wrong. Are you using a custom (i.e. not shipped with debian) kernel? Nils -- *-* | Quotes from the net: L Linus Torvalds, W Winfried Truemper | | Lthis is the special easter release of linux, more mundanely called 1.3.84 | | WUmh, oh. What do you mean by special easter release?. Will it quit | * Wworking today and rise on easter? * pgpYjapMjGYti.pgp Description: PGP signature
Debian 1.2 installation - how to mount scsi cdrom????
Hi,
I'm trying to install debian on a second computer here at work from
cd-rom. I got the base system installed from floppy OK, and the cd rom was
apparently detected, but i don't have a clue how to mount it. I was
expecting a /dev/scd0 block device, but there's none, just sda, sdb, etc.
which are already used for the two hard disks. sdc won't work either.
Here's the last section of boot messages from dmesg:
NCR53c406a: no available ports found
scsi-ncr53c7,8xx : at PCI bus 0, device 15, function 0
scsi-ncr53c7,8xx : NCR53c810 at memory 0x3e00, io 0xff00, irq 15
scsi0 : burst length 8
scsi0 : reset ccf to 3 from 0
scsi0 : NCR code relocated to 0x2fc600 (virt 0x002fc600)
scsi0 : test 1 started
Failed initialization of WD-7000 SCSI card!
PPA: unable to initialise controller at 0x378, error 2
scsi0 : NCR53c{7,8}xx (rel 17)
scsi : 1 host.
scsi0 : target 0 accepting asynchronous SCSI
scsi0 : setting target 0 to asynchronous SCSI
Vendor: QUANTUM Model: MAVERICK 540S Rev: 0901
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
scsi0 : target 1 accepting asynchronous SCSI
scsi0 : setting target 1 to asynchronous SCSI
Vendor: DEC Model: DSP3053LS Rev: 442E
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
scsi0 : target 4 accepting asynchronous SCSI
scsi0 : setting target 4 to asynchronous SCSI
Vendor: NEC Model: CD-ROM DRIVE:500 Rev: 2.5
Type: CD-ROM ANSI SCSI revision: 02
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 4, lun 0
scsi : detected 1 SCSI cdrom 2 SCSI disks total.
SCSI device sda: hdwr sector= 512 bytes. Sectors= 1057758 [516 MB] [0.5 GB]
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 1046532 [511 MB] [0.5 GB]
Ethernet Bridge 002 for NET3.035 (Linux 2.0)
Partition check:
sda: sda1
sdb: sdb1 sdb2
VFS: Mounted root (ext2 filesystem) readonly.
Adding Swap: 16588k swap-space
JAVA Binary support v1.01 for Linux 1.3.98 (C)1996 Brian A. Lantz
PS/2 auxiliary pointing device detected -- driver installed.
lp1 at 0x0378, (polling)
Thanks for any help - i can't install the rest of the system unless i
get the cd mounted!
Martin
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: Debian 1.2 installation - how to mount scsi cdrom????
On Thu, Oct 30, 1997 at 04:51:02PM +, Waller Martin MEJ wrote: I'm trying to install debian on a second computer here at work from cd-rom. I got the base system installed from floppy OK, and the cd rom was apparently detected, but i don't have a clue how to mount it. I was expecting a /dev/scd0 block device, but there's none, just sda, sdb, etc. which are already used for the two hard disks. sdc won't work either. [ I assume you have a SCSI CD-Rom drive ] cd to /dev and there type the following : MAKEDEV scd which will hopefully create devices scd0, scd1, ..., scd7 to access your CD. Yours will probably be /dev/scd0 then, and you should create a link /dev/scd0 - /dev/cdrom olive -- Olivier Tharan, [EMAIL PROTECTED] Ooops. Save your work, everyone. FAST! -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Debian 1.2 installation - how to mount scsi cdrom????
Waller Martin MEJ wrote: Hi, I'm trying to install debian on a second computer here at work from cd-rom. I got the base system installed from floppy OK, and the cd rom was apparently detected, but i don't have a clue how to mount it. I was expecting a /dev/scd0 block device, but there's none, just sda, sdb, etc. which are already used for the two hard disks. sdc won't work either. Here's the last section of boot messages from dmesg: ... scsi0 : target 4 accepting asynchronous SCSI scsi0 : setting target 4 to asynchronous SCSI Vendor: NEC Model: CD-ROM DRIVE:500 Rev: 2.5 Type: CD-ROM ANSI SCSI revision: 02 Detected scsi CD-ROM sr0 at scsi0, channel 0, id 4, lun 0 ^^^ | Here it is: /dev/sr0 -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight http://lfix.co.uk/oliver PGP key from public servers; key ID 32B8FAA1 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
SCSI CDROM, ID 0, not recognized or driveable
The following message is a courtesy copy of an article that has been posted as well. I have a Toshiba 4X Internal CDROM. Upon booting my PC, the scan of controller 0 reveals that the CDROM is indeed on SCSI controller 0. However, when Debian Linux 1.3 boots up, it says scsi: detected 0 hosts and attempting to install from CDROM fails because non of the options for CDROM are recognized. Any idea how to make this CDROM recognizable? -- Terrence Brannon * [EMAIL PROTECTED] * http://quake.usc.edu/~brannon -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
SCSI cdrom
I'm trying to install Debian 1.2 to my PPRO with the SCSI hard disk and CD-ROM. I have successfully installed the kernel and the base disks. Now, I want to install all packages from the CDROM. However, there is no /dev/sr0 or /dev/scd0, which means I cannot mount the CD-ROM. I try to run MAKEDEV in /dev, it conplains about some unexpected } in makedec.cfg. Can anybody please help? By the way, the SCSI-cdrom is recognized at the booting time. Xiaoming Ding -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: SCSI cdrom
Edit /etc/makedev.cfg to remove the omit { }. It's a syntax error.
We'll make a point release after New Years with this fixed.
Bruce
--
Bruce Perens K6BP [EMAIL PROTECTED]
Finger [EMAIL PROTECTED] for PGP public key.
PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: How to activate SCSI CDROM after install ?
I think you haven't loaded the driver for your SCSI controller. The message about the NCR53c406a seems to indicate you don't have one of those. Try using the modprobe tool, or you can build a custom kernel with the driver linked in. Thanks Bruce -- Bruce Perens K6BP [EMAIL PROTECTED] Finger [EMAIL PROTECTED] for PGP public key. PGP fingerprint = 88 6A 15 D0 65 D4 A3 A6 1F 89 6A 76 95 24 87 B3 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
