🚀 go-pugleaf

Dave Campana <103207.3640@CompuServe.COM> wrote:

I don't have a SCSI controller, so I am just taking pity.  I will go
over the obvious things, and hopefully this will help.
-	Do you know the controller works under another operating 
	system?
-	You have  a boot disk with scsi support.  You have tried
copying 
	it again?  
-	Get another copy of rawrite from the net at sunsite or a
mirror.
-	You have read the FAQ in the comp.os.linux.announce
-	You have looked over the Howto's at
	http://sunsite.unc.edu/mdw/HOWTO/HOWTO-INDEX-3.html

Not much help, but maybe some places to look for info.

Good Luck!


>Please take pity on me!......
>I am failing in my attempts to get linux running.  I have a 
>DX4-100 with a Future domain 1680 (ver 3.5). I have tried 
>Yggdrasil and A newly purchased WGS pro (the easiest to install?).

>My problem is no scsi host detected.  I have tried downloading a 
>boot image from 1.2.13 (which lists up to version 3.5) but no joy. 
>I am sure I have been at this for to long and am missing something 
>simple but I cant find it. 

>Thanks in advance

>-- 
>Dave

Dave Campana <103207.3640@CompuServe.COM> writes:
>Please take pity on me!......
>I am failing in my attempts to get linux running.  I have a 
>DX4-100 with a Future domain 1680 (ver 3.5). I have tried 
>Yggdrasil and A newly purchased WGS pro (the easiest to install?).

>My problem is no scsi host detected.  I have tried downloading a 
>boot image from 1.2.13 (which lists up to version 3.5) but no joy. 
>I am sure I have been at this for to long and am missing something 
>simple but I cant find it. 

greetings:
  misery loves company.  after giving up on a nec810 based board, i
decided to try a borrowed future domain tmc-1680.  it has bios v3.6
in it, and my 1.2.5 kernel source says it works w/ v3.5.  i presume
that v3.6 hasn't broken anything, but i get a 0 scsi hosts detected
error message.  anybody got a clue?

later,
kc       (looking for clues in all the wrong places)
-- 
"ooooh, crumbs!"if the world is nite, shine my life like a lite"live your life
with PASSION"hey waiter, there's a transvestite in my soup"hey mister, are you
tall?"all alone in the nite"son of a son of a sailor"John DeArmond fanclub #13
"he's dead, jim"he's not dead, he's electroencephalographically challenged" kc

Kenneth C. King wrote:
> 
> Dave Campana <103207.3640@CompuServe.COM> writes:
> >Please take pity on me!......
> >I am failing in my attempts to get linux running.  I have a
> >DX4-100 with a Future domain 1680 (ver 3.5). I have tried
> >Yggdrasil and A newly purchased WGS pro (the easiest to install?).
> 
> >My problem is no scsi host detected.  I have tried downloading a
> >boot image from 1.2.13 (which lists up to version 3.5) but no joy.
> >I am sure I have been at this for to long and am missing something
> >simple but I cant find it.
> 
> greetings:
>   misery loves company.  after giving up on a nec810 based board, i
> decided to try a borrowed future domain tmc-1680.  it has bios v3.6
> in it, and my 1.2.5 kernel source says it works w/ v3.5.  i presume
> that v3.6 hasn't broken anything, but i get a 0 scsi hosts detected
> error message.  anybody got a clue?
> 
> later,
> kc       (looking for clues in all the wrong places)<snip>

With v3.6, I think you have to add the signature to the driver file in 
the kernel sources and recompile. Damned long time since I've looked at 
them, but the file should be in /usr/src/linux/drivers/scsi. Look for 
fdomain.h. I've got a 1680 v3.5 and have two external hdds and an 
external tape drive hanging off it. Works fine. Hope this helps.

bmcarth@ix.netcom.com

Dave Campana (103207.3640@CompuServe.COM) wrote:
: Please take pity on me!......
: I am failing in my attempts to get linux running.  I have a 
: DX4-100 with a Future domain 1680 (ver 3.5). I have tried 
: Yggdrasil and A newly purchased WGS pro (the easiest to install?).

: My problem is no scsi host detected.  I have tried downloading a 
: boot image from 1.2.13 (which lists up to version 3.5) but no joy. 

Short answer:  

You probably need to recompile your kernel, after patching fdomain.c
to add the "BIOS signature string" of your 1680 card.

Details:

I had this same problem.  I'm still a newbie, but eventually puzzled
out what to do.  To succeed, you must have enough of Linux installed
and working to rebuild your kernel; hope that's not Catch-22.  
  
The following steps worked for me, but I'm not implying
any warranty!  Use at your own risk!  

This refers to kernel version 1.2.13.  In the kernel sources, 
look at fdomain.c around line 370.  You'll find there a list of 
BIOS signature strings recognized by the code.  Immediately above, 
there is a declaration of what some of the other data fields mean 
(sig_offset, sig_length, BIOS major and minor numbers, etc.).

If the signature on your card doesn't match one of these, it won't
work.  Boot DOS and use debug.exe (carefully!) to find and inspect
the area of high memory where the SCSI card's BIOS code is.  Mine
was at CA00, so what I did from bare DOS was:

           C:\> debug
           -d ca00:0000
                   (look at the first several bytes and write them down
                    carefully)
           -q
           C:\>
  
If your Future Domain card doesn't identify itself at CA00, try looking at
other addresses. 

Edit future domain.c to add the string to the list, and fill in the other
fields for offset, length, etc.  The line I added was

  { "FUTURE DOMAIN CORP.  V3.6008/18/93",                  5, 34,  3,  6, 0 },

but this won't work for you unless it matches your card exactly.  Put in
whatever is appropriate.  Rebuild your kernel, run lilo, etc. and it may
work.  Actually, fdomain.c contains numerous warnings that patching it 
this way may not suffice, but it worked for me.  I sent my patch to the
author, but haven't looked at whether it has been incorporated anywhere.

Hope this helps, and happy Linux-ing.

Duff McRoberts
rdm@csn.net