This is exactly what I used to get with the "init_pit()" stuff that
initialized the programmable interval timers (incorrectly, it seems,
even though the code looked ok). David has the same setup as I do, but
never saw this, so it probably depends on the firmware version (probably
the _very_ initial debugger code, not MILO).
Anyway, this problem is present with linux kernels 1.3.37-40 or
something like that. You should get the vmlinux-cabrio-1.3.35.gz kerbel
binary that David M-T made available, and that should work fine.
I guess I could also make my current cabrio kernel available, and then
you'd have a pre-1.3.44 system. It's stable for me, but no promises ;-)
> A couple of things I noticed, this model is a 300MHZ machine
> but the bogoMIPS number seems odd/low to me.
It's probably the pit initialization that messes up. It may be that the
some versions of the Cabriolet uses the "DRAM refresh timer" as a source
for the CPU timer ticks, and that could result in "interesting" problems
when the pit is reprogrammed.
> Milo tells me I have
> 32Mb however I've got 4 SIMMS of 16Mb each so should be 64Mb?
Hmm.. Is MILO hardcoded for this? Try giving it the MEMORY_SIZE define
(or whatever the name was - type "help" at the prompt).
> I don't have a hard-drive connected to it yet as I thought I
> would be using a SCSI Buslogic 946C however Milo complains
> that it doesn't know how to configure the host adapter and
> hangs if I try to load the linux kernel.
Hmm? The cabrio has a built-in NCR SCSI chipset, and that's the only
thing the MILO binaries probably support.
> I've already reinstalled the SIMMS but that didn't have any effect,
> What else should I try or is there anything else I should provide?
I'll try to upload my personal kernel to ftp.cs.helsinki.fi (in the
Kernel/test directory), but that contains only the NCR SCSI driver, not
the buslogic one. But if you don't see my binary, just get the older
1.3.35 kernel from David's sites (or a mirror: I use ftp.funet.fi myself
for most things).
Linus