Hi Geert,

Geert Uytterhoeven schrieb:
> What did Amiboot detect without the `-p` option (you may want ti try `-d')?
> Does it assume a 68882 FPU?
>   
Without supplying the '-p' parameter amiboot didn't output anything at
all, it just froze the amiga directly after entering the command.
> Have you tried `debug=mem', and running the AmigaOS dmesg afterwards?
>   
I didn't know about the AmigaOS dmesg, thanks for telling me! I attached
the dmesg output of it.
> I'd expected this to be the topology issue, but that change doesn't seem
> to be in 3.1.4. I'll see whether I can reproduce this.
>   
Call Trace: [<0000ffff>] mm_release+0xa1/0xa4
 [<002b84fa>] topology_sysfs_init+0x0/0x1e

Seems to prove that, do you think
http://www.spinics.net/lists/linux-m68k/msg04709.html would solve the issue?
> Do you know what clock chip is used on the A603? I had a quick look on the
> net, but couldn't find it (I did see a picture of an A604 with a partially
> covered chip that said M6242). If you can't find it, I can ask Jens.
>
> Currently, Linux assumes an A2000 clock chip, which is an Oki MSM6242.
> If it's a Ricoh RP5C01, you have to modify arch/m68k/amiga/config.c to
> select an A3000 clock chip on A600.
>   
The kernel outputs: "Amiga hardware found: (...) A2000_CLK (...)", can i
rely on that message, or should i get the A603 out of the case and check
the chip to be sure?
>> and the PCMCIA network card (some card with NE2000-chip, it works
>> flawlessly under AmigaOS with cnet.device and NetBSD, when inserting the
>> apne module i get "ethernet PCMCIA card inserted", followed by "device
>> not found". Maybe i'm missing a device file here?).
>>     
>
> Sorry, cannot help you there.
>   
OK, i will keep you informed if i find a solution for the PCMCIA-card.
> Thanks for your report!
>   
Thanks for helping me! :-)


Regards
Patrick