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] .
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] .
