Hello,

I had some time again to test stuff on my faithful 9500 and I replaced
the battery so it remembers OF settings again :)

the only kernel I can use with reliability is a kernel michael prepared
for me in november of the past year. Now I read that nerbsd 2.0.2 is out
and I wonder if there had been progress... I compile my kernel now and I
get:

NetBSD 3.99.3 (gandalf_generic1) #13: Sat Apr 16 21:35:53 CEST 2005
        multix@gandalf:/usr/src/sys/arch/macppc/compile/gandalf_generic1
total memory = 176 MB
avail memory = 165 MB
mainbus0 (root)
cpu0 at mainbus0: 604e (Revision 2.4), ID 0 (primary)
cpu0: HID0 8000c084<EMCP,ICE,DCE,SGE,BHT>
cpu0: 200.00 MHz
bandit0 at mainbus0
pci0 at bandit0 bus 0
pci0: i/o space, memory space enabled
pchb0 at pci0 dev 11 function 0
pchb0: Apple Computer Bandit Host-PCI Bridge (rev. 0x03)
tlp0 at pci0 dev 13 function 0: DECchip 21143 Ethernet, pass 3.0
tlp0: interrupting at irq 23
tlp0: Ethernet address 00:00:c5:53:0c:bf
tlp0: 21143 reset block
tlp0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ofb0 at pci0 dev 15 function 0: Matrox MGA Millennium 2064W ("Storm")
ofb0: 640 x 480, 8bpp
wsdisplay0 at ofb0 kbdmux 1: console (std, vt100 emulation)
wsmux1: connecting to wsdisplay0
obio0 at pci0 dev 16 function 0: addr 0xf3000000
esp0 at obio0 offset 0x10000 irq 12: NCR53C94, 25MHz, SCSI ID 7
scsibus0 at esp0: 8 targets, 8 luns per target
mc0 at obio0 offset 0x11000: irq 14,2,3: address 00:a0:40:22:12:c1
zsc0 at obio0 offset 0x13000: irq 15,16
zstty0 at zsc0 channel 0
zstty1 at zsc0 channel 1
awacs at obio0 offset 0x14000 not configured
swim3 at obio0 offset 0x15000 not configured
adb0 at obio0 offset 0x16000 irq 18: 2 targets
aed0 at adb0 addr 0: ADB Event device
akbd0 at adb0 addr 2: extended keyboard
wskbd0 at akbd0: console keyboard, using wsdisplay0
ams0 at adb0 addr 3: 1-button, 100 dpi mouse
wsmouse0 at ams0 mux 0
mesh0 at obio0 offset 0x18000 irq 13: 50MHz, SCSI ID 7
scsibus1 at mesh0: 8 targets, 8 luns per target
nvram0 at obio0 offset 0x1d000
scsibus0: waiting 2 seconds for devices to settle...
scsibus1: waiting 2 seconds for devices to settle...
sd0 at scsibus1 target 0 lun 0: <QUANTUM, FIREBALL SE4.3S, PJ0A> disk
fixed
sd0: 4110 MB, 7637 cyl, 4 head, 275 sec, 512 bytes/sect x 8418816
sectors
probe(mesh0:0:1:0): max sync rate 10.00Mb/s
sd1 at scsibus1 target 1 lun 0: <IBM OEM, DFHSS4F, 4141> disk fixed
sd1: drive offline
cd0 at scsibus1 target 3 lun 0: <MATSHITA, CD-ROM CR-8005A, 4.0i> cdrom
removable
boot device: sd1
root on sd1a dumps on sd1b
root file system type: ffs
mesh0: timeout state 3
mesh0: intr/msk 00/07, exc 00, err 00, st0/1 21/40
mesh: resetting DMA


note the last messages, the typical scsi/mesh/sync troubles...
I don't remember which magic michael used last time. I think he forced
sync on for some devices. This means in any case that negotiation still
has troubles.
I wanted to try improvments since I read that so much work on interrupt
handling was done and the kernel I currently use gets very, very
unresponsive during disk access for example. A cvs update can cause up
to a temporary freeze of the UI.

cheers,

   Riccardo