> > ahsc0 targ5 lun0 <Quantum LP105S 9101094053.1> SCSI2 direct fixed
> > sd5 at scsibus1: 100MB, 1211 cyl, 4 head, 42 sec, 512 bytes/sec
> > ahsc0 targ6 lun0 <Quantum LP240S GM240S01X6.4> SCSI2 direct fixed
> > sd5 at scsibus1: 234MB, 1818 cyl, 4 head, 65 sec, 512 bytes/sec
> > zthreebus0 at mainbus0
> > 
> > here the machine hangs with the HD light on steady. When I press a key
> > I get a panic with the PC at 0001A34E.
> 
>   Maybe you are the first on to test the A3000 driver code?  I don't
> know if Chris Hopps had anyone try out the A3000 or A2091 driver.
> Neither he nor I have an A3000 to test A3000-specific things on.
> 
>   Oh oh - I found what may be the problem:  a3000dmaintr() calls
> sbicintr, but passes the controller number instead of the sbic_softc
> pointer.  Try changing "sbicintr(i)" to "sbicintr(dev)".  The A2091
> driver has the same bug (atzsc.c).
> 
> Michael
> 
You were right :) I changed the 'i' to a 'dev' and after zthreebus0 at
mainbus0 it kept on going, but not very far. I get lots of hd types
which were depreciated, then it went to fsck where it right away comes
back with:
/dev/rsd6a CANNOT SEEK: BLK 16
/dev/rsd6a UNEXPECTED INCONSISTENCY run fsck manually. 
manually didn't help either. 
Also I keep on getting: can not map ld.so errors....
cp complains about wrong arguments. 
When I try to go into mulit user mode lots of errors come flying along
the screen until it says:
init getty repeating too quickly on port /dev/ite0, sleeping.
(Actually I had this error a couple of weeks ago when I was running
old binaries with a new kernel) 

Does this mean that I need to have the rest of the source tree
recompiled in order to use the new kernels?


Arthur.

__
Arthur Hoffmann					58/1 Dickward Drive
						Fannie Bay N.T. 0820
						Darwin - Australia.
hoffmann@it.ntu.edu.au				Tel.:(0061/)89/818926



------------------------------------------------------------------------------