I am having problems using the -current kernel (April 14) and my A530.  
When I boot up, I see this:

.
.
.
gvpbus0 at zbus0 rom 0xe90000  man/pro 2017/11
gtsc0 at gvpbus0: dmamask 0x1ffffff maxdma 65536
scsibus0 at gtsc0
gtsc0: target 0 now synchronous, period 256ns, offset=8.
gtsc0 targ 0 lun 0: (QUANTUM, MAVERICK 540S, 0901) SCSI2 0/direct fixed
sd0 at scsibus0: 516MB, 2853 cyl, 4 head, 92 sec, 512 bytes/sec
probe(gtsc0:1:0): non-media hardware failure, data = 00 00 00 00 43 00 00 
00 00 00
gtsc0 targ 1 lun 0: (QUANTUM, ELS170S, 4.07) SCSI2 0/direct fixed
sd1 at scsibus0: 163 MB, 1536 cyl, 4 head, 54 sec, 512 bytes/sec
.
.
.


A few notes:

* sd0 is my AmigaDOS drive, and sd1 is NetBSD's.

* The biggest difference between 1.0 and -current's startup diagnostics is 
  the "gtsc0: target 0 now synchronous" and "probe(gtsc0:1:0): non-media 
  hardware failure" parts.  

* I don't know if this is due to the "non-media hardware failure" or a 
  difference between 1.0 and -current, but when I attempted to mount my 
  AmigaDOS partitions, it fails, giving me a 'read only media' error.

* All disk access to sd1 seems to be ok, however.  

* When I reboot (Control-LAmiga-RAmiga), my A530 appears to be locked up. 
  The drive access light stays on, but nothing happens.  It takes an 
  actual physical power down to fix things.



I wonder if the problem is due to -current trying to set sd0 to be 
accesses synchronously.  Both the sd0 and sd1 have the sync option turned 
off in their RDB, but -current still says that "target 0 now synchronous".

Perhaps my A530 SCSI controller can not operate synchronously, and when 
it is set to do so, it locks up (although this only happens on reboot).

Is there some why to make -current access the drives only asynchronously, 
or does someone know what my lockup problem could be?



Thanks!


Jeff Thieleke