Sometimes root= points to an UUID instead of a partition, and when it does, you cannot just copy over cmdline.txt from another installation. Setting it, as you did and is default, to /dev/mmcblk0p2 is fine for nearly all Pi setups - UUID's are really only useful (in this context) if you have two or more bootable USB devices, and not sure in what order they get enumerated.

Glad you got it working!

Does "ifconfig -a" show you a hardware address on a line starting with "ether"? Do you get output from "iwlist scan"? If yes to both, it's not a firmware or hardware issue. If not, grep your dmesg for "brcmfmac"

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?

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.

Most welcome - especially the softvol "trick" is necessary for certain Raspberry Pi DAC's without hardware volume (the pHAT DAC and some Hifiberry models, for instance).

Hey, no, for some reason i still do not get notification mails - but we will see! this time tomorrow i might have some news, had to go to a concert last night and i keep missing tux on freenode - we should work on that! hahaha

Anyway, talk soon - come on freenode if you are bored!

And my /etc/asound.conf - this gives you OSS emulation and "native" ALSA with separate volume controls. Note: you have to use them before they show up in alsamixer.

-- CUT --

pcm.softvol {
    type softvol
    slave {
        pcm "dmix"
    }
    control {
        name "Default Playback Volume"
        card 0
    }
}
       
pcm.!default {
    type plug
    slave.pcm "softvol"
}

pcm.dsp0 {
    type plug
    slave.pcm "dmix"
    control.name "sbagen"
    control.card 0
}

# MPD volume
pcm.mpd {
        type softvol
        slave.pcm "plug:dmix"
        control.name "MPD Playback Volume"
        control.card 0
}

ctl.mpd {
        type hw
        card 0
}

-- CUT --

PS: Remember to install alsa-oss before trying this!

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!".

v8+ started shipping with 4.19.75. 4.19.93 came out for Raspbian/sid mid January. If you also have a Pi 3, i updated my guide elsewhere how to slap it on top of Ascii for Pi 3 and get it running on a Pi 4.

What is your purpose with this? Getting kernel 5.5 running? Tell me how i can help and what i need to set up.

Hey, i wonder why i didn't get topic reply emails anymore. In fact, i came for a look because this morning i started "upgrading" Devuan to 64 bit

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!

Hello!

I know terribly little about u-boot, however, i see no messages about mmc-bcm2835 and sdhost-bcm2835 (comparing with a Pi Zero here), so it really looks like a missing card reader driver to me.

Now, that delay i do know a little about, but no sureshot fix for it. It is something introduced with kernels 4.16 onwards (i believe), and related to how it gathers random data.

- Try installing haveged and reboot. It fixed things for some people (supposedly works without a hardware RNG).
- Try removing haveged, installing rng-tools and reboot. Fixed things for other people (supposedly requires a hardware RNG).
- Try removing rng-tools, plugging an 802.11 USB adapter and reboot. This fixed it for me on a Pi 2.

Let me know your results.