Am 04.09.2022 um 03:50 schrieb Stephen Walsh <vk3...@vk3heg.net>: >>> Amiga 3000 >>> Warpengine 68040@40Mhz >>> 128Mb ram on warpengine >> Uhm? How do you get the Warpengine with 128MB into an A3000? Usually >> there is not enough space on the Warpengine for 4x 32 MB SIMMs - or >> did you use 2x 64MB ones or 4x single sided 32 MB SIMM with two >> additional sockets? > That's not relevant to this, but my A3000 isn't in a desktop case.
Ok, in an A3000 tower case you might use the Warpengine for the A4000 with vertical sockets and not tilted sockets as in the A3000 desktop version of the Warpengine. > This is the debug output. > [ 0.000000] Linux version 5.18.0-4-m68k (debian-ker...@lists.debian.org) > (gcc-11 (Debian 11.3.0-5) 11.3.0, GNU ld (GNU Binutils for Debian) > 2.38.90.20220713) #1 Debian 5.18.16-1 (2022-08-10) > [ 0.000000] printk: console [debug0] enabled > [ 0.000000] Amiga hardware found: [A3000] VIDEO BLITTER AMBER_FF AUDIO > FLOPPY A3000_SCSI KEYBOARD MOUSE SERIAL PARALLEL A3000_CLK CHIP_RAM PAULA > DENISE_HR AGNUS_HR_PAL MAGIC_REKICK ZORRO3 > [ 0.000000] initrd: 0f7f81c2 - 10000000 > [ 0.000000] Ignoring memory chunk at 0x7800000:0x800000 before the first > chunk > [ 0.000000] Fix your bootloader or use a memfile to make use of this area! > [ 0.000000] Zone ranges: > [ 0.000000] DMA [mem 0x000000000a000000-0x000000ffffffffff] > [ 0.000000] Normal empty > [ 0.000000] Movable zone start for each node > [ 0.000000] Early memory node ranges > [ 0.000000] node 0: [mem 0x000000000a000000-0x000000000fffffff] > [ 0.000000] Initmem setup node 0 [mem > 0x000000000a000000-0x000000000fffffff] > [ 0.000000] Unable to handle kernel access at virtual address (ptrval) So, here is the error and a possible solution: using a memfile might help. http://amigadev.elowar.com/read/ADCD_2.1/Hardware_Manual_guide/node00D4.html and comparing with the memory lists shown in ShowConfig or SysInfo might help. It seems that it tries to move the kernel around, but is unable to do so. Might be when the new kernel is loaded to Chip Mem and the other memory types like Fast Mem are not recognized or ignored. By default it only uses one memory chunk with highest priority, IIRC, but maybe Geert or so will correct me. If things haven’t changed since my tries with BigRAM 256MB then you can only make use of a single memory chunk as RAM. More memory chunks like onboard memory can be used as ramdisk for swapping or so. -- Ciao... // Web: http://blog.windfluechter.net Ingo \X/ XMPP/Jabber: i...@jhookipa.net gpg pubkey: http://www.juergensmann.de/ij_public_key.asc
