Glad you got it working!

the only thing I don't understand is what you mean with

cf. with my output post #16

Anyway, everything works great, thanks for the instruction

Maybe that's the point. The 1 GB Pi has a wlan1 interface, and my Pi2 a wlan2. However, since I use both as WLAN AP, I bridged those interfaces with eth0 to the bridge interface br0 which is the only one to ask the DHCP server. The only explanation I have, is that the bridge does not succeed on the 2 GB having a wlan0 interface, and thus does not ask for an IP address.

I should better start with a blank SD card.

Btw: clean Raspbian or yan's image from https://dev1galaxy.org/viewtopic.php?id=3209&p=3 worked well

Since your wlan0 isn't even associated, it might be worth running wpa_supplicant manually in the foreground with logging to stdout, and see what happens when it tries to associate (you can probably use wpa_cli as well, never used it myself so cannot be of much help there).

Is your wireless access point locked on MAC addresses? Because the behaviour is the exact same as if you forgot to add the MAC of the 2GB Pi.

Does Raspbian or anything else get an IP address on your 2GB Pi?

Do you have a wlan0 interface at all?

wlan0 is present

output from raspbian:

$ iwconfig
lo        no wireless extensions.

wlan0     IEEE 802.11  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          
eth0      no wireless extensions.

The ouput of $ vcgencmd bootloader_config changed from

BOOT_UART=0
WAKE_ON_GPIO=1
POWER_OFF_ON_HALT=0
FREEZE_VERSION=0

to

[all]
BOOT_UART=0
WAKE_ON_GPIO=1
POWER_OFF_ON_HALT=0
DHCP_TIMEOUT=45000
DHCP_REQ_TIMEOUT=4000
TFTP_FILE_TIMEOUT=30000
TFTP_IP=
TFTP_PREFIX=0
BOOT_ORDER=0x1
SD_BOOT_MAX_RETRIES=3
NET_BOOT_MAX_RETRIES=5
[none]
FREEZE_VERSION=0

However, I'm not able to see devuan receiving an ip address. Also tried the SD card with devuan from Raspi4 - 1GB without success in my Pi4 - 2 GB.

https://www.raspberrypi.org/documentati … teeprom.md

If you are running a 32 bit Devuan you should be able to just pull a couple of packages for Raspbian, install, run and remove again. The updater will not work on a 64 bit system.

Note that i have no idea exactly what those update fix, apart from lowering the temperature and fixing some USB3 stuff.

Mine is a 4GB model, but i doubt it makes any difference. Tell me where it breaks for you and i'll try to think of a solution.

It boots up wright on the Pi2, but on the Pi4 (2GB) it does not receive an IP-address

# uname -a
Linux devuan 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linux

# cat /boot/cmdline.txt 
dwc_otg.fiq_fix_enable=2 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait rootflags=noload net.ifnames=0

On the Pi4 with 1GB everything works fine even with ascii (and newest hostapd). But the same card does not receive an IP on the version with 2GB of memory.

does this procedure only work with the version with 1GB of memory? I have no success with the 2GB version, or should I also upgrade to boewulf or even ceres? I'll try out and report.

Mine is a 4GB model, but i doubt it makes any difference. Tell me where it breaks for you and i'll try to think of a solution.

If you have a Pi 2 1.0 or 1.1, the easiest way of making a bootable SD card for the Pi 4 is like this:

- Grab a Devuan image for Pi 2 (sorry, 32 bit only when doing this on a Pi 2). For some reason i could never boot the Ascii image on my Pi 2, but Jessie worked fine.
- Boot it on your Pi 2 and set up networking.
- From http://archive.raspberrypi.org/debian/p … -firmware/ get raspberrypi-bootloader and raspberrypi-kernel - make sure they have matching version numbers and not older than 20190620.
- From http://archive.raspberrypi.org/debian/p … e-nonfree/ get the latest firmware-brcm80211.
- install all three with dpkg.

If it boots right, you should be running 4.19.50-v7l+. Shutdown, put the card into your Pi 4 and boot it up.

does this procedure only work with the version with 1GB of memory? I have no success with the 2GB version, or should I also upgrade to boewulf or even ceres? I'll try out and report.

To get around the problem of the vc4 module and to get the second monitor output to work you need Mesa 19.1.0 or later, that means an upgrade to beowulf and fixing a few dependancies.

By now, mesa 19.3.3 and llvm 9 are both in the Devuan repositories (at least on ceres) - awesome you got it working dual headed, i cannot try that since my adapters are too thick to fit side by side, but i have to try your "max_framebuffers" trick one day i get more slim HDMI adapters

And yes you are right, the HDMI output closest to the USB C power port is stronger - if you get no video during boot after switching from vc4-kms-v3d to vc4-fkms-v3d then try the other HDMI port, and depending on your monitor, you might need a power cycle to send it a "wake up" signal.

Sorry, i forgot to write i upgraded to ceres before starting everything - my bad!

Glad you both (and possibly others) made it work - thanks should go out to freenode #devuan-arm who went "we honestly have no idea - try it!".

- Grab a Devuan Ascii image for Pi 3.
- Boot it on your Pi 3 and set up networking.
- From http://archive.raspberrypi.org/debian/p … -firmware/ get raspberrypi-bootloader and raspberrypi-kernel - make sure they have matching version numbers and not older than 20200114 (kernel 4.19.93).
- From http://archive.raspberrypi.org/debian/p … e-nonfree/ get the latest firmware-brcm80211 (might actually be in the Devuan apt as well - forgot to check).
- install all three using dpkg with the --force-architecture parameter.
- Double check your /boot/cmdline.txt - especially the root= setting.
- Edit your /boot/config.txt - delete (or comment out) "kernel=kernel8.img", add "arm_64bit=1" on a separate line and finally replace "dtoverlay=vc4-kms-v3d" with "dtoverlay=vc4-fkms-v3d".
- Reboot.

If it boots at all, it will boot in 64 bit on any Pi 4 and Pi 3, and even the final Pi 2 revision 1.2 (which i do not own, but people tell me it is just an underclocked 2837).

Finally, update your system!

Caveat emptor - the above worked for me (i did, however, update to ceres before installing the three packages and rebooting). Enjoy Devuan aarch64 on your Pi 4!

PS: If you want the hardware specific bits (which usually live in /opt/vc), you have to wait. AFAIK, libraspberrypi(0,-bin,-dev) only exist in armhf versions so far, and i definitely cannot help there.

Step 1 - getting the above method up to speed with kernel packages from raspberrypi.org so people will have a "tedious but simple" way of getting Devuan running aarch64 on a Pi 4.
Step 2 - documenting it here.
Step 3 - coming over to help you

1+2 should be done this time tomorrow. Count me in for 3 after that, so we can get a "complex but accurate" version too!

It would be nice to get more people involved