On 4/15/05, Oliver Schonefeld <oschonef@techfak.uni-bielefeld.de> wrote:
> Hello port-cobalt@NetBSD.ORG,
>=20
> I recently got hold of a Cobalt RAQ (not RAQ2) and trying to install NetB=
SD
> on it. Using the restore CDs (for 1.6.1) i got it to work and now I am
> trying to upgrade it to 2.0.2.
> After some fiddling I got a kernel compiled, but 1.6.1 and 2.0.2 are
> refusing to use UltraDMA; the kernel seems to lose the irq for the ide ch=
ip:
>=20
> pcib0: VIA Technologies VT82C586 (Apollo VP) PCI-ISA Bridge, rev 39
> viaide0 at pci0 dev 9 function 1
> viaide0: VIA Technologies VT82C586 (Apollo VP) ATA33 controller
> viaide0: bus-master DMA support present
> viaide0: primary channel configured to compatibility mode
> viaide0: primary channel interrupting at irq 14
> atabus0 at viaide0 channel 0
> viaide0: secondary channel configured to compatibility mode
> viaide0: secondary channel ignored (disabled)
> VIA Technologies VT83C572 USB Controller (USB serial bus, revision 0x02) =
at
> pci0 dev 9 function 2 not configured
> wd0 at atabus0 drive 0: <IBM-DTTA-351010>
> wd0: drive supports 16-sector PIO transfers, LBA addressing
> wd0: 9671 MB, 19650 cyl, 16 head, 63 sec, 512 bytes/sect x 19807200 secto=
rs
> wd0: 32-bit data port
> wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 2 (Ultra/33)
> wd0(viaide0:0:0): using PIO mode 4, Ultra-DMA mode 2 (Ultra/33) (using DM=
A
> data transfers)
> boot device: wd0
> root on wd0a dumps on wd0b
> viaide0:0:0: lost interrupt
>         type: ata tc_bcount: 512 tc_skip: 0
>=20
> Is this a general problem on RAQs or is there a way to fix this? If i use
> flags 0x0ffc for wd, the RAQ used PIO mode 4 just fine)
>=20
> I also have problems invoking fdisk (just to display the mbr partition
> table); the kernel panics. fdisk was from the old 1.6.1 userland, build.s=
h
> release was running also)
>=20
> trap: address error (load or I-fetch) in kernel mode
> status=3D0x2, cause=3D0x8010, epc=3D0xc24701d2, vaddr=3D0xc24701d2
> pid=3D2382 cmd=3Dnbmake usp=3D0x7fffde70 ksp=3D0xc3703980
> Stopped in pid 2382.1 (nbmake) at       0xc24701d2:trap: address error (l=
oad
> or I-fetch) in kernel mode
> status=3D0x2, cause=3D0x8410, epc=3D0x801d67dc, vaddr=3D0xc24701d2
> pid=3D2382 cmd=3Dnbmake usp=3D0x7fffde70 ksp=3D0xc37037e8
>      Stopped in pid 2382.1 (n
> bmake) at       0x801d67dc:     lw      v0,0(v0)
> db> trace
> 801d6770+6c (c24701d2,0,0,3a) ra 800ab688 sz 32
> 800ab648+40 (c24701d2,0,0,3a) ra 800af734 sz 24
> 800af530+204 (c24701d2,0,0,3a) ra 801d7b0c sz 40
> 801d7aa0+6c (c24701d2,0,0,3a) ra 801ddc9c sz 32
> trap+26c (c24701d2,0,0,3a) ra 801d5568 sz 152
> 801d5484+e4 (c24701d2,0,0,3a) ra 0 sz 0
> User-level: pid 2382.1
>=20
> Thanks,
> Regards,
> Oliver
>=20
> P.S: full boot log and dmesg attached (for the dma case)
> --
> --------------------------------------------------------
> And remember: "To Infinity And Far Beyond ... Somehow?!"
>=20
> Hi! I'm a .signature virus! Copy me in your ~/.signature
> to help me spread!             <- Save this lifeform ;-)
>=20
>=20
>=20

I' m going from memory here but if it's serving me correctly, yes,
that's a problem with the Raq1's, and no there's no fix.

Also watch out for the cron in /etc/daily as it invokes /etc/security
which runs fdisk and will crash the box every night if you don't
disable it.  I just commented it out, I think.