what about PI 4

[Blodo]

However attempting the same process with aarch64 does not work on the pi4. What ended up happening is becoming stuck on the initial boot screen which is just a colored rainbow image on screen.

Can confirm, just tried an aarch64 setup that boots and works fine on an rpi3, it gives the rainbow screen when the sd card is plugged into an rpi4. Software on it was updated yesterday so should include the firmware updates.

[lategoodbye]

AFAIK the aarch64 setup uses the mainline kernel, which doesn't have any RPI 4 support.

[graysky]

I think it does... https://github.com/raspberrypi/linux/commits/rpi-5.2.y

[lategoodbye]

You are pointing to the vendor kernel tree (which provides Arm64 support), but i was refering to mainline / kernel.org.

According to this PKGBUILD Arch is using the mainline kernel.

[graysky]

I see... what if you point the PKGBUILD to the vendor repo and build that? That is how linux-raspberrypi kernels are built.

[lategoodbye]

I don't have any intention to fix this. I only wanted to provide a possible reason, why it doesn't work. The RPI tree usually contains hacks which works fine with 32 bit, but causes issues with 64 bit.

[Blodo]

Anybody know if the aarch64 5.3 release candidate kernel has rpi4 support yet?

EDIT: some interesting info here: https://forum.manjaro.org/t/raspberry-p ... d/92325/60

does that mean the aarch64 kernel package needs to maybe be rebuilt with the aarch64 pi4 dtb? there's links to one in that thread above

[lategoodbye]

For those who are interested in the current upstream / mainline status:
https://lists.fedoraproject.org/archive ... GZ2Q77APK/

[MReimer]

Something is clearly not right.

Did someone ever try to use "top" or "pgrep"?

Code: Select all

[alarm@alarmpi ~]$ top
Segmentation fault (core dumped)
[alarm@alarmpi ~]$ pgrep bash
Segmentation fault (core dumped)


Edit: Would be great if someone could verify this problem (so I know that my Raspberry 4 didn't destroy the SD file system somehow).
If you have the problem, too, then run "pacman -S procps-ng" to reinstall procps-ng. Fixed this problem.

Edit2: Reinstalled the SD card. Problem doesn not exist.... So it seems like my Raspi 4 destroyed the file system somehow. I start so seriously regret having bought 4 RPi 4 boards...

[jmmec]

EDIT: the issue below may be covered in this post...

https://www.raspberrypi.org/forums/view ... 3&t=247867

----------

I'm seeing the following error with a V1 camera running latest ArchArm. Even though raspistill complains, it still captures an image and saves it to a file.

Code: Select all

$ /opt/vc/bin/raspistill -rot 180 -t 3000 -w 1920 -h 1080 -md 2 -e png -o test.png
mmal: mmal_vc_shm_init: could not initialize vc shared memory service
mmal: mmal_vc_component_create: failed to initialise shm for 'vc.camera_info' (7:EIO)
mmal: mmal_component_create_core: could not create component 'vc.camera_info' (7)
mmal: Failed to create camera_info component


I also have a python script that uses the PiCamera library, but it isn't as forgiving and raises an exception and exits:

Code: Select all

raise PiCameraMMALError(status, prefix)
picamera.exc.PiCameraMMALError: Failed to create MMAL component b'vc.camera_info': I/O error

In the /boot/config.txt I have:

Code: Select all

start_x=1
gpu_mem=128

I've tried with two different V1 cameras modules & cables which otherwise work fine on Pi3 & Pi2 devices for the tools above. I have some V2 cameras but they are currently in use so can't try them at the moment.

Any ideas?