PiMiga 1.5 > Guru Meditation errors at boot >

[Noob-tech-ninja]

Hi there guys.

I was hoping that you could shed some light on an issue for me please

Background:
I've just obtianed the absolutley aweseome Pimiga 1.5 package for my Raspberry Pi 4.

I imaged the sd card with etcher (on linux)
I copied accross my ROMs to the Kicks folder

Things worked brilliantly, for about 30 mins.
I played a couple of games (quickly as a test)
Opened a couple of apps / programmes - They all opened and worked properly.
Everything seemed to be working well.

I was going to have a go on a few more games, and I wanted to use my
X-Box (360 ?) wired gamepad.

I plugged it in to one of the USB ports on the Pi, (It wasnt recognised which I was half expecting).
I then turned off the Pi. re-insterted the gamepad and rebooted,
I got to the Pimiga desktop, but the gamepad still wasnt recognised.

I performed another powercycle, with the gamepad attatched
and then I stared to get the Guru meditation errors when trying to boot
into the main Pimiaga desktop (see trouble shooting steps below for error).


Trouble shooting:
01. The Pi will boot.
02. Get a basic text screen that scrolls with some device info
03. Displays the "Rainbow" box for 0.5 secs
04. Displays the Pimiga 1.5 splash screen

05. Then I get a nice big honking Guru meditation error
and the screen hangs (see error message below)

06. I can hit F12 and get into the config screen for UAE
I can then restart or quit the programme, and either drop into the CLI
or restart the "Amiga" from the UAE config screen.

07. If I restart the "Amiga", I get back to the splash screen.
and I'll either get the Guru meditation error or I'll sometimes get into
a WB screen (but its massivley corrupt and the screen resolutions and
dimesions are warped.

But I cannot get back into the main Pimiaga Amiga desktop anymore


08. I've tried booting both with and without the gamepad attached
and neither works, I get the Guru meditation error message

09. I've ran a FS check using both (G-Parted & K-Partion manager)
on the boot and kicks partitions on the sd card.

However, I'm getting some strange results -

G-Parted is throwing out some errors (see bottom of this post)
However G-Parted has been twitchy for a while now, when trying to perform
FS checks on (Non-Linux) based FS - So I'm not entirley convinced that
there are any FS errors. (But I've included them for completeness)

K-Partition manager scans the FS and comes back clean with no errors
on the FS or partitions.


Device: Raspberry Pie 4 (4GB RAM)

OS: Pimiga 1.5 lite version (32 GB)


Guru meditation error codes
Error: 8000 0004 Task: 40401868



Host PC
OS: Linux - Ubuntu 18.04
DE: KDE version 5.12.9
Kernel: 4.15.0-140-generic



G Parted error message when trying to perform a FS check on the
"Boot" and "Kicks" partitions.

GParted 0.30.0 --enable-libparted-dmraid --enable-online-resize

Libparted 3.2

Check and repair filesystem (fat32) on /dev/sdh1  00:00:01    ( ERROR )
    	
calibrate /dev/sdh1  00:00:00    ( SUCCESS )
    	
path: /dev/sdh1 (partition)
start: 8192
end: 532479
size: 524288 (256.00 MiB)
check filesystem on /dev/sdh1 for errors and (if possible) fix them  00:00:01    
( SUCCESS )
    	
fsck.fat -a -w -v '/dev/sdh1'  00:00:01    ( SUCCESS )
    	
fsck.fat 4.1 (2017-01-24)
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "mkfs.fat"
Media byte 0xf8 (hard disk)
512 bytes per logical sector
512 bytes per cluster
32 reserved sectors
First FAT starts at byte 16384 (sector 32)
2 FATs, 32 bit entries
2064896 bytes per FAT (= 4033 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 4146176 (sector 8098)
516190 data clusters (264289280 bytes)
32 sectors/track, 64 heads
0 hidden sectors
524288 sectors total
Reclaiming unconnected clusters.
Checking free cluster summary.
/dev/sdh1: 338 files, 94358/516190 clusters
grow filesystem to fill the partition  00:00:00    ( ERROR )
    	
using libparted
libparted messages    ( INFO )
    	
GNU Parted cannot resize this partition to this size. We're working on it!
[

TIA for any help or advice that you can provide.

[indigolemon]

Quick question, when you say you powercycled - are you using F12 to access the menu and clicking Shutdown, then starting it again? If not, there is a chance you've caused an issue with the card by powering off when a write was ongoing ( unlike real Amiga's where you can just flip the power off )

I know it takes ages, but I'd use etcher and redo the card - I think that will be a lot less heartache than trying to repair the filesystem!

[Noob-tech-ninja]

Hi indigolemon

You ask a fair question, but yes I was power cycling properly.
Shutting down via the software and then once has shut down, using the power button
on the dedicated "clicker" button that came with my Pi 4

I hadnt re-flashed the SD card before I posted this. but I thought that would mask
the problem and I wouldnt learn anything (about the issue, or how to fix it).

10. Since then, I wiped, the SD card, and re-flashed it via etcher once more.
The issue remains, same as before, the Pi boots, gets to the Pimiga splash screen
and then either gets the Guru Meditation, or hangs, or reboots.

I've just bought some 32 GB and 128 GB, micro SD cards (and am awaiting delivery)
So I can test it again once they arrive.

[utukku]

Hiya, I suggest you go onto the Pimiga discord site. You will get lots of help there from ppl involved in the beta testing, as well as Chris who created it in the first place.


Utukku

[mcbpete]

Is the power supply providing enough amperage for the Pi ( https://www.raspberrypi.org/document...ower/README.md ) ? When I got my first Raspberry Pi I was just using a generic mobile phone charger plug and everything would seem to boot OK but after a while I'd get a load of read/write errors to the SD card, so much so the thing would eventually fail to boot and I'd have to write another image to the card, which again would eventually fail again and again ... until I changed the power supply to one that spat out enough Amps !

[Noob-tech-ninja]

OK, the issue has been resolved (which is great) but I'm not 100% on what
fixed it yet.

1. Bought and used a brand new 32GB micro-sd card

2. Re-downloaded the Pimiga 1.5 (lite ver), and flashed the sd card with
the newest downlaod (I used MD5SUM to see if there were any differences
- There wasnt, they have the exact same signatgure).

3. (As an aside) - I am current using the 1st (affected) mico-sd card
to run retro pi, on it without any issues at all.
So it doesnt appear to be a faulty sd card either.

Thank you to everyone who replied and made suggestions
much apprecated.

[FerociousAmiga]

Regarding your controller, IMO you would be better off with a USB TROOPER 2 joystick which is selectable in the PiMIGA Settings (F12) > Input and will give you that real retro joystick feel.

[stainy]

Initially.. I would say the kick rom... or maybe too many kick roms in youe kick partition ( this is what I would say from all the problems I`ve seen in the discord channel.)

[Hercules]

I would check the CRC / MD5 checksum of the image before writing it to your card with Win32Imager. A corrupt image can cause such problems.