jca@pnet01.cts.com (John C. Archambeau) (05/18/89)
I have this nasty problem with my hard drive controller and Minix. It appears
that the receiver for the winchester task when I boot up the system is idle.
My guess is that the controller isn't receiving the proper commands or
initializing correctly. I know that if everything goes alright, the receiver
for the winchester task should be 'any.' I have applied the OMTI 5527A
patches to xt_wini.c, but the same thing goes (note that I did not apply the
part of the patch that changes NR_SECTORS to 26). Am I right with my
assumption about the controller being 'stuck' during initialization? I will
also point out that I am using a DTK AT/XT floppy drive controller in an AT
box. I have the floppy drive controller's BIOS disabled since my AT BIOS
is aware of the existance of all possible drive configurations. I also have
the jumper block set to "no hard drive in system" this is due to the fact that
if you have an XT controller in an AT, you have to deliberately lie to every
card in your system and the AT BIOS for it to work properly. Everything else
works, I can recompile the kernel with no problems, etc. This is Minix 1.3 (a
borrowed copy, I got tired of cross compiling my 'upgraded 1.2' from DOS and
Turbo C). I pretty much need an OMTI controller and a device driver guru to
come forward. So how about a little help here! I 'almost' have it working
100% And 10 Mb is waiting for Minix (1.3)!
Help!
JCA
P.S. I did do the setvec (XT_WINI_VECTOR ... ), nada...
UUCP: {nosc ucsd hplabs!hp-sdd}!crash!pnet01!jca
ARPA: crash!pnet01!jca@nosc.mil
INET: jca@pnet01.cts.com