Zero 2 W support

[jal]

Hi,

Just a quick report back - flashed with ArchLinuxARM-rpi-4-latest.tar.gz, it booted.
Updated (pi4 kernel), still boots, wifi works. Thanks to all in the thread.

[MrGreen]

Am guessing from arm7l I am still running 32bit. Really wanted to try 64bit, not sure it is even possible or supported by archlinuxarm. Quite impressed anyway by the speed of Pi Zero 2, still limited buy 512mbs of ram.... zram, larger swap etc... Can of course look at lowering gpu mem as I run mostly headless.

[graysky]

So use the 64-bit image... others in this thread have confirmed aarch64 support.

[StuartIanNaylor]

I didn't read the forums just did a cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb after the pi3 install.

Worked fine but after a reboot with a pacman -Syu the pi boots shows the console then the display connection is lost?

Is this something new as was expecting that to work and confused why console boots but not display?

I can ssh in but no display on the pi after the full upgrade?

$this->bbcode_second_pass_code('', '[drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:72:crtc-3] flip_done timed out')

Yeah just get this and not really sure what that one is as new to me

$this->bbcode_second_pass_code('', 'Nov 14 15:31:42 alarmpi kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:72:crtc-3] flip_done timed out
Nov 14 15:31:42 alarmpi kernel: Console: switching to colour frame buffer device 240x67
Nov 14 15:31:52 alarmpi kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:72:crtc-3] flip_done timed out
Nov 14 15:32:03 alarmpi kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CONNECTOR:32:HDMI-A-1] flip_done timed out
Nov 14 15:32:13 alarmpi kernel: [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [PLANE:66:plane-3] flip_done timed out
Nov 14 15:32:23 alarmpi kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:72:crtc-3] flip_done timed out')

I will try a full install on a pi3A+ then transfer to zero2 without my 1st dtb hack

I just did the Pi4 install and its the same.

so far all I can think of is to remark out the KMS driver

$this->bbcode_second_pass_code('', '#dtoverlay=vc4-kms-v3d')

[dingausmwald]

I have the same problem sometimes with updated latest rpi4 image.
Don't know if this is the proper workaround but disconnecting usb otg cable and hdmi and plugging it in after boot did the trick.

Another thing: did anyone got bluetooth to work?
bluetoothctl says: No default controller available

rfkill wont list any bluetooth, just wlan

bluetooth.service just runs fine

btusb is loaded

$this->bbcode_second_pass_code('', '$ dmesg | grep Blue
[ 29.787928] Bluetooth: Core ver 2.22
[ 29.788056] Bluetooth: HCI device and connection manager initialized
[ 29.788148] Bluetooth: HCI socket layer initialized
[ 29.788815] Bluetooth: L2CAP socket layer initialized
[ 29.788859] Bluetooth: SCO socket layer initialized
[ 2060.033662] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 2060.033698] Bluetooth: BNEP filters: protocol multicast
[ 2060.033728] Bluetooth: BNEP socket layer initialized')

after reboot bluetooth service is inactive (dead), btusb is gone

[graysky]

$this->bbcode_second_pass_quote('dingausmwald', 'I') have the same problem sometimes with updated latest rpi4 image.
Don't know if this is the proper workaround but disconnecting usb otg cable and hdmi and plugging it in after boot did the trick.

$this->bbcode_second_pass_quote('graysky', '
')Which kernel?

[StuartIanNaylor]

As far as I can tell all images work but the only one I haven't tried is the Pi4-64bit as with only 512mb of mem one of your priorities is going to conserve memory.
I guess if your going to run ML or other heavy SIMD operations then 64bit might be an option in 512mb of ram. but its really counter intuitive to have the Pi4 image and also the 64bit.

The issue I am facing seems to be one that is facing all Pi's that unless you have a Pi4 Raspberry have done something very unusual where the new kernel & KMD driver runs but breaks backward and VC4 compatibility as its not just Zero2, Pi3A, Pi3 variants are the same.

The fake KMS seems to partially work but currently just guessing and hacking working solutions.

The Zero2 is essentially a Pi3 with 512mb of ram ontop and with the Pi3 arch install just `cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb` and until you update apart from new wifi/bt drivers it works.
Then after update/upgrade you should wifi/bt drivers but you hit the KMS problem that causes a reversion on VC4 but works on VC6.

I will give the Pi4-Arm64 image a go but not expecting the KMS driver to work as I have essentially a Pi3 and more importantly a VC4 gpu.

[ArchNewbie1]

Hello Guys,
I have bought A Rasperry Pi Zero2W anymore and i want to use a very lightweight Systems Like Arch in IT,but when i was in the Homepage their was No Image Form the Pi Zero 2W.I also searched for an Image Form the Frist Zero,but their wasn't an Image.I know that the Pi Zero 2 uses thebsame Soc AS the Pi3.Would IT possible to use the Image of the Pi 3 in this Case?Thank you for your answers

[graysky]

MOD NOTE - merged