[2793] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

fdomain message

daemon@ATHENA.MIT.EDU (Scott Wilson)
Tue Nov 11 11:57:01 1997

From: Scott Wilson <wilson@scuch8.psc.sc.edu>
To: linux-scsi@vger.rutgers.edu
Date: 	Tue, 11 Nov 1997 10:55:24 -0500 (EST)
Cc: wilson@scuch8.psc.sc.edu (Scott Wilson)

Greetings,

	I'm running Linux 2.0.0 (Slackware) with a Future Domain TMC-1610M-NEC 
scsi card, and the fdomain driver.  Until recently, I booted Linux with no 
problems from a 325 MB Seagate scsi hard disk.  I had a multi-i/o card, but no 
IDE hard disk, just two floppy drives.  

	I then bought a 4.3 GB IDE drive (for the price).  I cabled it to the 
HDD connector on the i/o card and have partioned the way I want, and have put 
an ext2 file system on it with mk2efs.  The problem when I boot is that as the 
fdomain driver is initializing the scsi card I see the following:

scsi: Future Domain TMC-16x0 SCSI driver, version 5.41
scsi: 1 host
fdomain: target=2, command=0, status=8
vendor: DEC
<info on my three scsi devices>

I get the fdomain: target=2, etc message millions of times, which fill the 
screen, and scroll for about a minute.  Then, the boot process picks up with 
the vendor: DEC message, which is what I've always had, and I get to eventually 
boot Linux.  It looks to me like there is a timeout or some large number of 
times the fdomain driver tries to do something.  What should I do about this 
message?  Is the problem the fdomain driver, and if so, what is it complaining 
about?

	My scsi bus has an old (1x) :-) DEC RD42 cdrom drive at address 2, an
Iomega Zip drive at address 5 and my Seagate hard drive at address 6.  Prior to
cabling the new IDE drive, I didn't have a problem booting with these same
devices.

	Humbly submitted for your consideration, I am

-- 
Scott Wilson
Dept of Physics
Univ of South Carolina
Columbia, SC, USA

President, Midlands Astronomy Club

PGP Public Key on request, or finger wilson@scuch8.psc.sc.edu

"Most likely, the Year 2000 Problem will cause the failure of at least one 
company in the S&P 500.  I would not think it prudent to enter the year 
2000 without a large supply of bottled water and canned goods and a 
non-power-grid-dependent can opener.  Nor prudent to fly in the first week 
of 2000.  Indeed, if a two-year sabbatical on a South Sea island appeals, 
1999 July might be an ideal time to begin.  With any luck, most of the 
aircraft maintenance skipped during the first half of 2000 (in part 
because a constant flood of undeserved delinquency notices obscured the 
real delinquencies) will have been caught up by mid-2001."

home help back first fref pref prev next nref lref last post