Within the last fortnight I had ne1: device timeout which you (Bill,
Matthias et al) pointed out immediately was due to an incorrectly set
irq (set to jumperless), but what can I do about

vr0: device timeout ?

vr0 at pci0 dev 15 function 0: VIA VT3043 (Rhine) 10/100 Ethernet
vr0: interrupting at irq 5
vr0: Ethernet address: 00:50:ba:a1:6d:50
ukphy0 at vr0 phy 8: Generic IEEE 802.3u media interface
ukphy0: OUI 0x006040, model 0x0000, rev. 0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

irq's in use are:

pckbc0: using irq 1 for kbd slot
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
vr0: interrupting at irq 5
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
lpt0 at isa0 port 0x378-0x37b irq 7
uhci0: interrupting at irq 10
pckbc0: using irq 12 for aux slot
pciide0: primary channel interrupting at irq 14
pciide0: secondary channel interrupting at irq 15

Cheers,

Patrick