On Jan 25, 2013, at 11:20 AM, Mark Cave-Ayland wrote:
On 25/01/13 09:48, Mark Morgan Lloyd wrote:
On 24/01/13 09:27, Mark Morgan Lloyd wrote:
I've got one of those machines, set up for OS and Linux (i.e. it's a bit fragile and I'd rather not try installing anything else on it). If that sounds useful tell me what to do.
Thanks! I think perhaps a tarball of /proc/device-tree from Linux is what I need? There may be a utility to dump the tree from OS X too, but I'm not exactly sure what it is.
My OS is 9 (I think), I only use it for transferring control to Linux. You have off-list mail created as below, note error messages of the type indicated:
0 2>root@pye-dev-05:/# tar -czf proc_device-tree.tar.gz /proc/device-tree tar: Removing leading `/' from member names tar: /proc/device-tree/perch: file changed as we read it ..
Let me know if there's anything else I can do to help.
Hi Mark,
Thanks for doing this. So I've had a play with PearPC and I can make the CMD646ATA fail during its start method similar to the way that QEMU does by commenting out the IDE interface IRQ entry from the "interrupt-map" property. This seems to support my theory that the problem is related to interrupt mapping.
Now AIUI g3beige is an "Old World" Mac and so the interrupt information should be held in the "AAPL,interrupts" property. I've verified that both QEMU and OpenBIOS calculate the irq_line in the same way (based upon device id), however I do see that some of the "AAPL,interrupts" values contain more than one integer. I wonder what this is supposed to represent?
ATB,
Mark.
I just wanted to add that my Ubuntu Linux 5 CD also fails to boot because of a problem with the CMD646 controller. Here is the error message:
[c0149ee4] ide_pci_register_driver+0x54/0x5c [f100e634] cmd64x_ide_init+0x18/0x28 [cmd64x] cmd64x: can't be loaded missing kernel or user mode driver cmd64x