2 SCSI Controllers
Hello, I have an Intel server se7501WV2 with on SCSI Controller on board and a second one as an extra card. Build in is an Adaptec AIC7902 Ultra320 (two channel), extra is an Adaptec 29320LP-R PCI Single U320 (Chip AIC-7901X). Both use the same driver (aic79xx). If both are installed I get SCSI errors like (messages): Apr 11 14:20:41 localhost kernel: scsi0:0:0:0: Attempting to abort cmd f7531800: 0x28 0x0 0x 3a 0x28 0x5d 0xde 0x0 0x0 0x1 0x0 Apr 11 14:20:41 localhost kernel: Infinite interrupt loop, INTSTAT = 0scsi0: At time of recovery, card was not paused Apr 11 14:20:41 localhost kernel: Dump Card State Begins Apr 11 14:20:41 localhost kernel: scsi0: Dumping Card State at program address 0x26 Mode 0x22 Apr 11 14:20:41 localhost kernel: Card was paused Apr 11 14:20:41 localhost kernel: HS_MAILBOX[0x0] INTCTL[0x80] SEQINTSTAT[0x0] SAVED_MODE[0x11] Apr 11 14:20:41 localhost kernel: DFFSTAT[0x33] SCSISIGI[0x25] SCSIPHASE[0x0] SCSIBUS[0x0] Apr 11 14:20:41 localhost kernel: LASTPHASE[0x1] SCSISEQ0[0x40] SCSISEQ1[0x12] SEQCTL0[0x0] Apr 11 14:20:41 localhost kernel: SEQINTCTL[0x0] SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0] SSTAT0[0x10] I don't know what is wrong with this configuration. System is Debian Sarge, Kernel version is 2.4.27. I know that debian is not supported on Intel servers. -- Yours Henrik Kraft -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sarge bootet nach Tausch des SCSI Controllers nicht mehr
* Markus Rupprecht Mailing: Ich habe einfach keine Lust, den neuen Server Platt zu machen und mit dem richtigen Controller noch einmal alles neu zu installieren. Das muss man doch nachträglich noch ändern können. Das Laden der SCSI-Moduln über /etc/modules kommt zu spät, an der Stelle muß / ja schon da sein. Ohne Garantie, da ich ewig keine Standardkernel mehr verwendet habe: Mit Knoppix o.ä. booten, chroot ins tote System, in /etc/mkinitrd/modules das SCSI-Modul eintragen und mit mkinitrd eine neue initrd erstellen, die dann das Modul enthält. Einen Bootmanagereintrag erstellen, der die neue initrd verwendet, Bootsektor schreiben, booten, hoffen. Grüße, Andreas -- Don't read any sky-writing for the next two weeks. -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Sarge bootet nach Tausch des SCSI Controllers nicht mehr
Guten Tag, mein Problem: Ich habe mehrere Server mit dem MPT Fusion (LSI 1030) SCSI Controller. Alle mit debian sarge. Kernel 2.6.8-1-386 Nun habe ich einen weiteren Server aufgesetzt und erst spät bemerkt, dass der falsche SCSI Kontroller darin steckt (irgendein kleiner NCR, viel zu langsam). Nach dem Tausch des SCSI Kontrolers beginnt er zu booten, es kommt aber ziemlich schnell, dass er den pivot_root nicht machen kann, weil er die Datei nicht findet. (Möglicherweise will er da von /boot = /dev/sda1 auf / =/dev/sda3 umsteigen. Das ganze liegt nicht an grub, denn mit dem ncr geht es ja. Nun habe ich verglichen: Alte Server, neuer Server: kernel: gleiche Grösse initrd.img: gleiche Grösse System.map und config: absolut gleich Sind sind ja alle mit dem 2.6er kernel von Sarge installiert. /etc/modules: kein Eintrag für irgendeinen SCSI Kontroller. Scheinbar wird der fusion bei den alten und der ncr beim neuen Server automatisch geladen. Ein zusätzliches Eintragen des fusion (mtpbase und mptscsih) hat es auch nicht gebracht. Ich habe gegoogelt und gefunden, dass in conf.modules etwas wie alias scsi_hostadapter modulname hinein soll. Bei uns heisst die Datei wohl modules.conf, aber bei allen Servern steht da nichts in Richtung alias scsi_hostadapter... also kann es nicht wichtig sein. Ich habe einfach keine Lust, den neuen Server Platt zu machen und mit dem richtigen Controller noch einmal alles neu zu installieren. Das muss man doch nachträglich noch ändern können. Wenn jemand einen Tipp hat, wäre ich super dankbar. -- Mit freundlichen Grüssen Markus Rupprecht Mailing mailto:[EMAIL PROTECTED] -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Linux Driver for WD7193,WD7197,WD7296 SCSI Controllers
Hi!I hava a Western Digital WD7193 SCSI Controller and it is not compatible to the WD7000 Driver.If I don't get a driver for WD7193,WD7197,WD7296 or compatible SCSI Controllers I willnever be able to use Linux because my harddrives and CDRom drives are conntected to it.And there is not driver available from Western Digital. Can anybody help me please? Thank You,Andy
Re: Using Both IDE and SCSI Controllers
On Fri, Jun 05, 1998 at 02:35:32PM -0700, Allan Bart wrote: Hello, I was wondering if any of the users on this group have concurrently run both types of disk drives. i am planning to use an advansys 5140 and an internal ide controller on my old ast 486dx system. I used an ASUS SP3G with built-in ide and scsi (NCR). I booted off the 450MB ide and had a 100MB SCSI swap disk (yeah, disk not partition) and a 330MB SCSI root disk. -- Lee Bradshaw [EMAIL PROTECTED] (preferred) Alantro Communications [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Using Both IDE and SCSI Controllers
Hello Allan, I currently have a buslogic BT946 controller with one 1 gig conner scsi drive and then a 420 meg ide drive and an 850 ide drive. It all works fine. The scsi drive only has linux stuff on it and then one ide drive has a linux partition (/) for booting and that sort of stuff. Works fine. On 05-Jun-98 Allan Bart wrote: Hello, I was wondering if any of the users on this group have concurrently run both types of disk drives. i am planning to use an advansys 5140 and an internal ide controller on my old ast 486dx system. looking ro hear from you, allan bart == Allan W. Bart, Jr. Strategic Analyst _ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] [EMAIL PROTECTED] Dan Plaster -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Using Both IDE and SCSI Controllers
Hello, I was wondering if any of the users on this group have concurrently run both types of disk drives. i am planning to use an advansys 5140 and an internal ide controller on my old ast 486dx system. looking ro hear from you, allan bart == Allan W. Bart, Jr. Strategic Analyst _ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Using Both IDE and SCSI Controllers
My system runs an Adaptec 7xxx SCSI controller (and drive), three IDE drives and an IDE CD-Rom... Works... boots off of /dev/hda1 so I had to use LILO to boot anything off of /dev/sda1 On 05-Jun-98 Allan Bart wrote: I was wondering if any of the users on this group have concurrently run both types of disk drives. i am planning to use an advansys 5140 and an internal ide controller on my old ast 486dx system. -- http://benham.net/index.html -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS d+(-) s:+ a29 C++$ UL++ P+++$ L++ E? W+++$ N+(-) o? K- w+++$(--) O M-- V- PS-- PE++ Y++ PGP++ t+ 5 X R+ !tv b DI+++ D++ G++G+++ e h+ r* y+ --END GEEK CODE BLOCK-- -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Using Both IDE and SCSI Controllers
On 06/05/98 at 02:35 PM, Allan Bart [EMAIL PROTECTED] said: Hello, I was wondering if any of the users on this group have concurrently run both types of disk drives. i am planning to use an advansys 5140 and an internal ide controller on my old ast 486dx system. looking ro hear from you, I'm using a Symbios SCSI card(3 hard drives and a CD) and the onboard IDE(2 harddrives and a floppy). Works for me. George A computer virus can be said to either 1) trash your hard drive, 2) lock up your computer, or 3) slow down your computer over time. Sounds like windows to me. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SCSI Controllers
Rob Browning [EMAIL PROTECTED] writes: Dale Scheetz [EMAIL PROTECTED] writes: I would highly recommend Buss Logic to anyone needing a SCSI interface. That's my impression as well. I've also heard that for the truly performance crazed, DPT cards are the answer, but are also more expensive. ( This thread really should be moved to debian-user if continued. ) For low-cost, high-performance, well-maintained cards, though, I don't think you can beat NCR. ASUS has a Ultra-Wide card that you can find for $120 that has been benchmarked (for all that's worth) outperforming an Adaptec. Mike. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: scsi controllers, bsd file system
Rick Hawkins wrote: a-hah! I've gotten somewhere--but it's not good. Once I connected the three scsi devices, I found that it finds all 3. But . . . The last device in the list does not get a /dev/srX entry. Thus with jus a cd and a zip in the chain, the cd gets one, but not the zip. With both cd's the zip, both cd's but not the zip. with just a cd, nothing gets one. e.g.: I've not been following your troubles closely but this triggere a quick thought... Are you sure you don't have a SCSI bus termination problem?? Does altering the order of the devices change the behaviour? Stephen --- Normality is a statistical illusion. -- me -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: scsi controllers, bsd file system
On Wed, 25 Jun 1997, Rick Hawkins wrote: a-hah! I've gotten somewhere--but it's not good. Once I connected the three scsi devices, I found that it finds all 3. But . . . The last device in the list does not get a /dev/srX entry. Thus with jus a cd and a zip in the chain, the cd gets one, but not the zip. With both cd's the zip, both cd's but not the zip. with just a cd, nothing gets one. e.g.: scsi0 fdomain: BIOS version 3.4 at 0xc8000 using scsi id 7 scsi0 fdomain: TMC-18C30 chip at 0x140 irq 11 scsi0 : Future Domain TMC-16x0 SCSI driver, version 5.44 scsi : 1 host. Vendor: SONY Model: CD-ROM CDU-8001 Rev: 3.2i Type: CD-ROM ANSI SCSI revision: 01 CCS Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0 Vendor: IOMEGAModel: ZIP 100 Rev: D.09 Type: Direct-Access ANSI SCSI revision: 02 and there should be, but isn't, a recognition that the zip is id5 and sr1. Is SCSI termination correct for all tested combinations? The fdomain card should have a jumper (w4 usually) for termination. Is it in or out? If the board is not labeled, I can look up the setting. Are all devices on one cable or do you have both internal and external cables in use? Also, i think the nec drive has a problem. I can mount my kids cds as iso devices in the apple drive (don't know how far i could read, but at least the beginnings), but not on the nec (which hangs). Maybe testing the nec as the only device with proper termination at each end would help. I can't mount these cd's that you've so generously sent, though. I've tried iso9660 and ext2. Are they possibly msdos? (i'm compiling more modules for this at the moment). They are iso9660 and if you mount them on a dos or windows system they should even be readable, but with 8.3 filenames. I have tested a lot of them on my funky 2x soundblaster, which often gets errors on silver CD-ROMs and they play well. If you can pop them into somebody's w95 or dos pc, it will assure that they are readable. It's possible that the kid's CDs appear OK because the directory is small, hence less transfer needed to mount it. What message do you get when you try to mount these CD's? +--+ + Paul Wade Greenbush Technologies Corporation + + mailto:[EMAIL PROTECTED] http://www.greenbush.com/ + +--+ + http://www.greenbush.com/cds.html Special Linux CD offer + +--+ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: more on scsi controllers
At the boot: prompt type linux fdomain=0x230,11 If I'm wrong about the 'linux' correct me. I can't reboot right now to verify that. OK, i sort of seem to be there. I compiled the fdomain module (among others). The autoprobe doesn't work: modprobe fdomain=0x140,11 yields no response. insmod fdomain 0x140,11 happily returns. But then mount /dev/scd0 /cdrom/ hung the system. no mouse, no kb, no three-fingered salute, no telnet, no nothin' . . . :( rick -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: more on scsi controllers
Rick Hawkins [EMAIL PROTECTED] wrote: After the hints so far, it's clear that eata 's error messages have to do with using the same adresses as the second ide card (which is installed). I'm new to Linux, but I've been working on computers for years, so let me ask a question that's naive, yet (I hope) insightful :-) : Wouldn't an EATA driver be for Extended ATA, that is, EIDE? It doesn't seem to have much to do with SCSI. So yes, try removing it. Also: I'm also beginning to suspect my floppy has gone bad; i can't mount it, and when i last tired to boot, it didn't quite find it. It doesn't even spin/groan when i try to moutn. There's another 5.25 drive, but this thing's bios won't boot off b:, and i don't have any of those old things around, anyway :( On standard PCs, the A: or B: status of a disk is determined by whether it's before or after the twist in the controller cable. Just switch your other drive to the opposite position on the cable. -- Carl Fink [EMAIL PROTECTED] Manager, Dueling Modems Computer Forum http://dm.net -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: more on scsi controllers
Try making a 1.3 rescue disk and booting it with the fdomain parameters. If you watch the screen (fast) during boot, you should see whether it got the scsi controller OK or not. If that works, then it's just a matter of configuring the kernel and LILO on your system. On Tue, 24 Jun 1997, Rick Hawkins wrote: At the boot: prompt type linux fdomain=0x230,11 If I'm wrong about the 'linux' correct me. I can't reboot right now to verify that. OK, i sort of seem to be there. I compiled the fdomain module (among others). The autoprobe doesn't work: modprobe fdomain=0x140,11 yields no response. insmod fdomain 0x140,11 happily returns. But then mount /dev/scd0 /cdrom/ hung the system. no mouse, no kb, no three-fingered salute, no telnet, no nothin' . . . :( +--+ + Paul Wade Greenbush Technologies Corporation + + mailto:[EMAIL PROTECTED] http://www.greenbush.com/ + +--+ + http://www.greenbush.com/cds.html Special Linux CD offer + +--+ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: more on scsi controllers
-- using template mhl.format -- Date:Tue, 24 Jun 97 20:54:15 EDT To: Rick Hawkins [EMAIL PROTECTED] cc: debian-user@lists.debian.org From:Paul Wade [EMAIL PROTECTED] Subject: Re: more on scsi controllers X-Sender: [EMAIL PROTECTED] In-Reply-To: [EMAIL PROTECTED] MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Try making a 1.3 rescue disk and booting it with the fdomain parameters. If you watch the screen (fast) during boot, you should see whether it got the scsi controller OK or not. If that works, then it's just a matter of configuring the kernel and LILO on your system. I can't make the floppy at the moment; it seems not to work. However, I now have an appropriate kernel on the machine. Answering lilo with Linux fdomain=0x140,11 does not result in loading the module. However, insmod fdomain gives me (roughly; from another screen) scsi0 fdomain: BIOS version 3.4 at 0xc8000 using scsi id 7 scsi0 fdomain: TMC-1830 chip at 0x140 irq 11 scsi0: Future Domain TMC-16x0 SCSI driver, version 5.44 scsi : 1 host Vendor NEC Model: CD-ROM DRIVE:83 Rev: 1.0 Type: CD-ROM ANSI SCSI Revision: 01 Detected CD-ROM sr0 at scsi0, chanel 0, id0, lun0 is /dev/sr0 the correct device, then? So I tried ./MAKEDEV sr0, which gave me the device. Then bash-2.00# mount /dev/sr0 /cdrom -t iso9660 mount: block device /dev/sr0 is write-protected, mounting read-only which results in the cd making some noise, and the system hang. a couple of things: should it be /dev/scd0, or /dev/sdc0? it seems to be scd, but the howto referss consistently to sdc. is it possible that it simply needs several minute to load? There's another access a couple of minutes later. I suppose I'll leave it runnning see if it comes back by morning. rick -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: more on scsi controllers
On Tue, 24 Jun 1997, Rick Hawkins wrote: Try making a 1.3 rescue disk and booting it with the fdomain parameters. If you watch the screen (fast) during boot, you should see whether it got the scsi controller OK or not. If that works, then it's just a matter of configuring the kernel and LILO on your system. I can't make the floppy at the moment; it seems not to work. However, I now have an appropriate kernel on the machine. Answering lilo with Linux fdomain=0x140,11 does not result in loading the module. This is for passing the parameters to fdomain that is compiled into the kernel. However, insmod fdomain gives me (roughly; from another screen) scsi0 fdomain: BIOS version 3.4 at 0xc8000 using scsi id 7 scsi0 fdomain: TMC-1830 chip at 0x140 irq 11 scsi0: Future Domain TMC-16x0 SCSI driver, version 5.44 scsi : 1 host Vendor NEC Model: CD-ROM DRIVE:83 Rev: 1.0 Type: CD-ROM ANSI SCSI Revision: 01 Detected CD-ROM sr0 at scsi0, chanel 0, id0, lun0 is /dev/sr0 the correct device, then? It's acceptable to my system. So I tried ./MAKEDEV sr0, which gave me the device. Then bash-2.00# mount /dev/sr0 /cdrom -t iso9660 mount: block device /dev/sr0 is write-protected, mounting read-only This is the expected behavior. which results in the cd making some noise, and the system hang. This is not. a couple of things: should it be /dev/scd0, or /dev/sdc0? it seems to be scd, but the howto referss consistently to sdc. /dev/scd0 is it possible that it simply needs several minute to load? There's another access a couple of minutes later. Seconds but not minutes. This always works for me: mount -t iso9660 /dev/scd0 /cdrom ls -lR /cdrom is a good test When I get CD errors the messages pop up on whatever virtual console I am using. Same for the retries. So if the system hangs, I know why. I think booting from the standard 1.3 kernel will tell us what direction to go in. If it works, it's only a software problem. If not, then maybe a bad CD drive. Make sure to try it with more than 1 CD. I have an old soundblaster 2x that is awfully fussy about the media. I think the rescue disk kernel will allow you to do something like this: Boot: Linux fdomain=0x230,11 root=/dev/hda1 in which case you can login and try mounting the CD. You might have to MAKEDEV scd0 first. +--+ + Paul Wade Greenbush Technologies Corporation + + mailto:[EMAIL PROTECTED] http://www.greenbush.com/ + +--+ + http://www.greenbush.com/cds.html Special Linux CD offer + +--+ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
scsi controllers, bsd file system
grr. Still going :( I am about to connect more pieces here in the chain. Device 0 (i can't figure out how to change the id; the switches seem to do nothing) will be this troublesome NEC intersect drive. Device 3 is an ancient apple cdrom drive--it should be able to read the directory first few megs (if anyone understands how to recalibrate these ancient sony monstrosities with their timing slug, i'd be eternally grateful!). Device 5 is a zip, with my macbsd partitions. Which leads to the magic question: what type is a netbsd (but not their newfs) disk? is it still type 83? a5 (bsd386)? b7 (BSDI fs)? and is anyone out there using a trantor t160? The next step is to use the distribution kernel, but: how do i extract it from resc1440.bin? rick -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: scsi controllers, bsd file system
On Wed, 25 Jun 1997, Rick Hawkins wrote: grr. Still going :( I am about to connect more pieces here in the chain. Device 0 (i can't figure out how to change the id; the switches seem to do nothing) will be this troublesome NEC intersect drive. Device 3 is an ancient apple cdrom drive--it should be able to read the directory first few megs (if anyone understands how to recalibrate these ancient sony monstrosities with their timing slug, i'd be eternally grateful!). Device 5 is a zip, with my macbsd partitions. Which leads to the magic question: what type is a netbsd (but not their newfs) disk? is it still type 83? a5 (bsd386)? b7 (BSDI fs)? and is anyone out there using a trantor t160? The next step is to use the distribution kernel, but: how do i extract it from resc1440.bin? The file named 'linux' in /bo/disks-i386/current is a kernel. I think it's the same as the one in the rescue disk. It's the same size. You can mount the rescue image on loopback and copy files from it. mount resc1440.bin -r -t msdos -o loop /mnt/floppy1 +--+ + Paul Wade Greenbush Technologies Corporation + + mailto:[EMAIL PROTECTED] http://www.greenbush.com/ + +--+ + http://www.greenbush.com/cds.html Special Linux CD offer + +--+ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: scsi controllers, bsd file system
a-hah! I've gotten somewhere--but it's not good. Once I connected the three scsi devices, I found that it finds all 3. But . . . The last device in the list does not get a /dev/srX entry. Thus with jus a cd and a zip in the chain, the cd gets one, but not the zip. With both cd's the zip, both cd's but not the zip. with just a cd, nothing gets one. e.g.: scsi0 fdomain: BIOS version 3.4 at 0xc8000 using scsi id 7 scsi0 fdomain: TMC-18C30 chip at 0x140 irq 11 scsi0 : Future Domain TMC-16x0 SCSI driver, version 5.44 scsi : 1 host. Vendor: SONY Model: CD-ROM CDU-8001 Rev: 3.2i Type: CD-ROM ANSI SCSI revision: 01 CCS Detected scsi CD-ROM sr0 at scsi0, channel 0, id 3, lun 0 Vendor: IOMEGAModel: ZIP 100 Rev: D.09 Type: Direct-Access ANSI SCSI revision: 02 and there should be, but isn't, a recognition that the zip is id5 and sr1. Also, i think the nec drive has a problem. I can mount my kids cds as iso devices in the apple drive (don't know how far i could read, but at least the beginnings), but not on the nec (which hangs). I can't mount these cd's that you've so generously sent, though. I've tried iso9660 and ext2. Are they possibly msdos? (i'm compiling more modules for this at the moment). rick -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
more on scsi controllers
After the hints so far, it's clear that eata 's error messages have to do with using the same adresses as the second ide card (which is installed). However, those aren't the correct adressess. I actually have three scsi cards sitting here to choose from: 1) the nec card, which, on closer look, claims to be a Trantor T160. I find T1x8 refferences in the howto, but no T160. 2) a future domaine 1610, with TMX18XX chip (it really says XX). 3) an adaptec 1510, but it has a tiny external connector; we're still trying to find the cable. I can't figure out how to tell the first two where to look for the adress of the card. Also, i'm not clear on which drivers to use for the first two. Should I even have eata in my kernel? finally, which of these cards will have the best performance. rick -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: more on scsi controllers
On Tue, 24 Jun 1997, Rick Hawkins wrote: : :After the hints so far, it's clear that eata 's error messages have to :do with using the same adresses as the second ide card (which is :installed). However, those aren't the correct adressess. : :I actually have three scsi cards sitting here to choose from: : :1) the nec card, which, on closer look, claims to be a Trantor T160. I :find T1x8 refferences in the howto, but no T160. : :2) a future domaine 1610, with TMX18XX chip (it really says XX). Don't know about either of these :/ :3) an adaptec 1510, but it has a tiny external connector; we're still :trying to find the cable. I *do* know about these. Throw it very, very far. Adaptec makes great (IMHO) controolers these days, but this one sucks (as you can tell from the DB25 external connecter, I believe it is) I'd try 1) or 2) :) Somebody out there has to be using these things ... -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: more on scsi controllers
Looking at the kernel source, I would say try for the future domain first. It should be supported by a standard Debian kernel as a built-in (not modular) driver. Maybe if you're lucky it will autoprobe. On Tue, 24 Jun 1997, Nathan E Norman wrote: On Tue, 24 Jun 1997, Rick Hawkins wrote: : :After the hints so far, it's clear that eata 's error messages have to :do with using the same adresses as the second ide card (which is :installed). However, those aren't the correct adressess. : :I actually have three scsi cards sitting here to choose from: : :1) the nec card, which, on closer look, claims to be a Trantor T160. I :find T1x8 refferences in the howto, but no T160. : :2) a future domaine 1610, with TMX18XX chip (it really says XX). Don't know about either of these :/ :3) an adaptec 1510, but it has a tiny external connector; we're still :trying to find the cable. I *do* know about these. Throw it very, very far. Adaptec makes great (IMHO) controolers these days, but this one sucks (as you can tell from the DB25 external connecter, I believe it is) I'd try 1) or 2) :) Somebody out there has to be using these things ... +--+ + Paul Wade Greenbush Technologies Corporation + + mailto:[EMAIL PROTECTED] http://www.greenbush.com/ + +--+ + http://www.greenbush.com/cds.html Special Linux CD offer + +--+ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: more on scsi controllers
Looking at the kernel source, I would say try for the future domain first. It should be supported by a standard Debian kernel as a built-in (not modular) driver. Maybe if you're lucky it will autoprobe. no such luck :( bash-2.00# mount /dev/scd0 /cdrom/ -t iso9660 mount: the kernel does not recognize /dev/scd0 as a block device (maybe `insmod driver'?) bash-2.00# -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: more on scsi controllers
The first step is to see a host adaptor. dir /proc/scsi cat /proc/scsi/aha152x (in my case) give ioport, irq, and a whole bunch of cool techie words. If nothing is there, then we need to help it along a bit. The LILO argument is: fdomain=PORT_BASE,IRQ[,ADAPTER_ID] Does the card have jumpers? Somebody on this list might have docs. In the meantime I am looking for a spec on the www. On Tue, 24 Jun 1997, Rick Hawkins wrote: Looking at the kernel source, I would say try for the future domain first. It should be supported by a standard Debian kernel as a built-in (not modular) driver. Maybe if you're lucky it will autoprobe. no such luck :( bash-2.00# mount /dev/scd0 /cdrom/ -t iso9660 mount: the kernel does not recognize /dev/scd0 as a block device (maybe `insmod driver'?) bash-2.00# -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . +--+ + Paul Wade Greenbush Technologies Corporation + + mailto:[EMAIL PROTECTED] http://www.greenbush.com/ + +--+ + http://www.greenbush.com/cds.html Special Linux CD offer + +--+ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: more on scsi controllers
dir /proc/scsi cat /proc/scsi/aha152x (in my case) give ioport, irq, and a whole bunch of cool techie words. bash-2.00# dir /proc/scsi/ scsi bash-2.00# cat /proc/scsi/scsi Attached devices: none bash-2.00# dir /proc/scsi/ scsi bash-2.00# cat /proc/scsi/scsi Attached devices: none bash-2.00# If nothing is there, then we need to help it along a bit. The LILO argument is: fdomain=PORT_BASE,IRQ[,ADAPTER_ID] but what do i use for fdomain? or is fdomain literal? Does the card have jumpers? Somebody on this list might have docs. In the meantime I am looking for a spec on the www. I have port bases irq's; they're actually labeled by the jumpers (0x230,11) rick -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: more on scsi controllers
Use a standard kernel, like the rescue disk. At the boot: prompt type linux fdomain=0x230,11 If I'm wrong about the 'linux' correct me. I can't reboot right now to verify that. On Tue, 24 Jun 1997, Rick Hawkins wrote: dir /proc/scsi cat /proc/scsi/aha152x (in my case) give ioport, irq, and a whole bunch of cool techie words. bash-2.00# dir /proc/scsi/ scsi bash-2.00# cat /proc/scsi/scsi Attached devices: none bash-2.00# dir /proc/scsi/ scsi bash-2.00# cat /proc/scsi/scsi Attached devices: none bash-2.00# If nothing is there, then we need to help it along a bit. The LILO argument is: fdomain=PORT_BASE,IRQ[,ADAPTER_ID] but what do i use for fdomain? or is fdomain literal? Does the card have jumpers? Somebody on this list might have docs. In the meantime I am looking for a spec on the www. I have port bases irq's; they're actually labeled by the jumpers (0x230,11) rick -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] . +--+ + Paul Wade Greenbush Technologies Corporation + + mailto:[EMAIL PROTECTED] http://www.greenbush.com/ + +--+ + http://www.greenbush.com/cds.html Special Linux CD offer + +--+ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: more on scsi controllers
Use a standard kernel, like the rescue disk. At the boot: prompt type linux fdomain=0x230,11 If I'm wrong about the 'linux' correct me. I can't reboot right now to verify that. close. capital L. But it still didn't work :( I wonder if the eata is somehow interfering. I have a new kernel compiling, hope it's ready soon, without eata. I'll try again then. I'm also beginning to suspect my floppy has gone bad; i can't mount it, and when i last tired to boot, it didn't quite find it. It doesn't even spin/groan when i try to moutn. There's another 5.25 drive, but this thing's bios won't boot off b:, and i don't have any of those old things around, anyway :( But if things *really* go bad, there's always the stack of other hd's :) rick -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: more on scsi controllers
Isn't there a reserve=io_address, length option you can feed the kernel to protect against autoprobing? I've had experiences where another, unrelated driver got to a card first with an autoprobe and bolloxed everything up. Seems I used a boot line like linux reserve=blah,blah aic7xxx=blah,blah (or whatever card you're trying to get to work, I obviously was fighting with an adaptec) It's been a long time though, and I don't have a man page handy. -- Nathan Norman:Hostmaster CFNI:[EMAIL PROTECTED] finger [EMAIL PROTECTED] for PGP public key and other stuff Key fingerprint = CE 03 10 AF 32 81 18 58 9D 32 C2 AB 93 6D C4 72 -- On Tue, 24 Jun 1997, Rick Hawkins wrote: : : Use a standard kernel, like the rescue disk. : : At the boot: prompt type : : linux fdomain=0x230,11 : : If I'm wrong about the 'linux' correct me. I can't reboot right now to : verify that. : :close. capital L. But it still didn't work :( I wonder if the eata :is somehow interfering. I have a new kernel compiling, hope it's ready :soon, without eata. I'll try again then. I'm also beginning to suspect :my floppy has gone bad; i can't mount it, and when i last tired to boot, :it didn't quite find it. It doesn't even spin/groan when i try to :moutn. There's another 5.25 drive, but this thing's bios won't boot off :b:, and i don't have any of those old things around, anyway :( But :if things *really* go bad, there's always the stack of other hd's :) : :rick : : :-- :TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to :[EMAIL PROTECTED] . :Trouble? e-mail to [EMAIL PROTECTED] . : -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
