Re: Version(s) working with BlizzardPPC

[Andreas <aw...@sw...>]

Hi Kulwant

On Tue, 2003-12-23 at 23:41, Kulwant Bhogal wrote:

> Hi Andi, all,
> 
> >> I will put the clock stuff back to how it was originally and collect
> >> some debug output to post here. Watch this space.
> 
> > Cool! Please do so!! Or at least try to look up the symbols in the
> > System.map as Geert mentioned in another mail (I think there's a
> > System.map delivered with the kernel lha for the amigaOS side).
> 
> OK. Attached is the DMESG and BOOTMESG captured output.

Hmm, could you maybe resend it as text/plain (explicitely set the type
in yam since it doesn't recognise the .log suffix and assumes
octet-stream as type)

> errr, could you expand on the symbols thing a little?

They would be found in the System.map-2.4.x-apus file IIRC..

> What exactly am I
> looking for

The numbers you've posted here earlier from the kernel panic.

> and what do I do with it once I've found it?

Look up the corresponding names to the numbers, then post it here.

> I've got a sysmap.gz file where I decompressed the downloaded files and I
> tried a untgz (is that the right thing to do?) on it and got the following: 
> 
> 9.System-S:Linux-Apus/boot2> untgz sysmap.gz ram:
> Extracting archive "sysmap.gz" to "ram:":
> extracting c0009290 T _get_PVR
> c0009298 T _set_L2CR
> c00092b0 t thisIs750
> c00092d0 t disableCache
> c00092f4 t loadLoop
> c0009310 t flushLoop
> c000932c t dontDisableCache
> c0009350 t invalCompleteLoop
> c000936c t noInval
> c0009374 t enableCache
> c0009384 T _get_L2CR
> c00093a0, size 0 bytes: FAILED, unable to open file (210)

Because there is nothing to extract. The text you see above (c00... t
...) is what is contained in the System.map file. untgz seems to think
these would be seperate files inside the archive, which is plain wrong.

But there must be a plain text System.map somewhere when you unpack the
lha archive on the amiga side. IIRC it's in the boot directory created
by the archive.

PS: Michel suggested to ask you if you've got any expansion cards
sitting on the clock port, since these may interfere with the clock port
driver somehow to the point of a kernel panic. Try to remove everything
from the clock port (except the clock itself), and try to boot.

-- 
Best wishes,
Andi