Hello therion23,
Can you join us on trying to get a arm64 version of Devuan, running in RaspberryPi Here ?

It would be nice to get more people involved

Kernel 5.5 is out, but not yet on the mirrors..
So I will await its release and will make new kernels..

I read a bit about ARMSTUB... which seems to be a thing that is executed by the graphics card or so..
I start to think that we need it somehow

You guys can comfirm you are able to boot with 'Raspbian Buster Lite' from '2019-09-26' ?
There are no armstub there( at least not visible.. )... maybe in 'start.elf'..don't know..

Without a serial connector we can only guess

You are right uther,
Any person that has a RaspberryPi4, would be nice to helping us out.
Maybe someone could have a usb-serial adapter( plus rpi4.. ) and can help.

For what I read, the booting process of raspberry pi4 is a lot different from the older versions..
The boot-loader is loaded from flash, as soon ad the processor starts to initialise on boot(  what previously was known as 'bootcode.bin'.. now is in that flash.. )..

Indeed, I also read about it, the bootloader is been updated because it was very basic, with only sd-card support( at beginning.. ), but here we are also only using sd-card, anyway..
Nevertheless, could be that the developing of it changes the way things were working..
There are also the fact that its not possible yet to use the 4GB Ram, due to the fact that only the 1st 1GB RAM is dma capable..
So 'config.txt', will need one more thing at least..
total_mem=3072

I updated the share with newer kernels, from linux-mainline to 5.5-rc7( with last week developments.. )

We need at least, has additions, in 'config.txt':
arm_64bit=1
kernel=RPi4_u-boot.bin
total_mem=3072

Tomorrow( ..or Today... 5:24H here.. ) maybe I will release a new Image If I find evidences of what is missing..

Hello Uther,
Was a pleasure!

Sad we don't succeed at first try,
But we are not so far away from success, we are almost there..

Thanks for your help on debugging, and trying out this image!
Ok, we will wait until you have some spare time to test, no problem.

EDIT: I think I found out why it doesn't boot
I tried a git pull to update my mainline branch...and I think I forgot to explicitly tell on the Makefile that I want vmlinux uncompressed

The first image was nice on this, but I believe the second as this fault..
I will check everything again.. not that 5.5-rc7 is here..

Best Regards,
tux

No problem
At least we know that the alpha kernel, or the config.txt was wrong..

yeah I should have done the same way, try the beta image
Please, don't forget to try with arm_64bit=1 in '/boot/config.txt'..
If that doesn't work, try also with 'arm_control=0x200'

if it doesn't work, try something different..
Comment line kernel=RPi4_u-boot.bin, change it to kernel=vmlinuz-5.5.0-rc6+

thanks..

No problem...that packages are or will be installed inside the system, once it boot up
Indeed there are there already a kernel, vmlinuz...
But don't worry with that.. it says 'vmlinuz' instead of 'vmlinux' but it his a uncompressed image ( 'vmlinux' ), the name is for a compressed one.. don't pay attention to it

There are several packages because one of main failures in distributions is that they provide a kernel but forget to provide the headers, and libc-dev so if you really want to make development you are stopped right there..
To ensure that everyone has the tools to proceed in its projects all the packages are provided

EDIT: Dont install linux-image-5.5.0-rc6+-2-dbg_arm64.deb
You can copy them to sdcard( exclude dbg package.. ), and when system boot's up, install them:

dpkg -i linux-headers-5.5.0-rc6+-2_arm64.deb  linux-image-5.5.0-rc6+-2_arm64.deb  linux-libc-dev_5.5.0-rc6+-2_arm64.deb

No, the new Image has the ext2 corrected fo vfat:

# <file system>	<dir>	<type>	<options>		<dump>		<pass>
/dev/mmcblk0p1		/boot	vfat	defaults		0		2
/dev/mmcblk0p2		/	ext4	defaults,noatime	0		1
/dev/zram0 		none    swap    pri=1			0		0
/dev/zram1 		none    swap    pri=2			0		0
/dev/zram2 		none    swap    pri=4			0		0
/dev/zram3 		none    swap    pri=3			0		0

This preliminary Image needs editing '/etc/fstab', you can burn the image in a card and the edit fstab on the card
Next image will have that corrected..

root Passwd: 'tor'
devuan Passwd: 'devuan'

Things that would be interesting would be,
a) If you have a serial debugger, connect to the uart, and get all the information about bootloader/boot process.
b) Find if thermal zones do exist, what temps system have..if something really out of what to be expected..
find /sys/class/thermal -name thermal_\* -exec ls -l {} \; -exec cat {}/temp \;
c) Get information about cpuinfo, and if it is correct..
'cat /proc/cpuinfo'
d) get information about swap, and system memory:
swapon -a && free -m
e) check swap quantity and algos( it should be 'lz4' )
swapon --show
find /sys/class/block -name zram\* -exec cat {}/comp_algorithm \;
f) List Loaded Modules:
lsmod

I updated the shared folder with '.condig' file for kernel 5.5, 'bcm2711_defconfig',
Updated also the generated kernel/KernelHeaders/Modules/Libc_headers( for this updated .config )

Feel free to provide information that you also think would be useful, like WiFi/Bluetooth, or adjust the config file
Share your thoughts

Thanks a lot for your work

I assume the default kernel that comes in Raspbian is the '4.19.75-v7l+' ?
Have you tested the WiFi/Bluetooth , and the network?

Can you do, in the default image,and kernel, as root:

dmesg

You can use any site available, I usually use: paste2, others use another service they like

Best Regards,
tux

Yup
What is the memory size of the version you have?

Hello,
I would make a Image of RPi4, but I don't own one..
If you agree in be a beta tester, sure I will do!!

I Built a image for RPi's using the CPU 'arm1176jzf-s':
rpi-a-plus
rpi-a
rpi-b-plus
rpi-b-rev2
rpi-b
rpi-cm1-io1
rpi-zero-w
rpi-zero
rpi-2-b
rpi-3-a-plus
rpi-3-b-plus
rpi-3-b
rpi-cm3-io3

Its a server type Image..

Hello,
My kernel '.config'  is yet very crude.. and I trusted it too much( to bad for me..I paid the price )

You were straight to the point
My rpi1B v1.0 is up and running
its consuming now 17MB of Ram..

So bootcode.bin->start.elf->u-boot-> real kernel..

I still have some annoyances, the iface 'eth0' gets renamed to something very absurd..
and maybe I don't have yet all modules that I need enabled.. :S

For example the CPU Activity led, is only blinking, not reflecting the load, or processing my PI have..
I will recompile also a u-boot with support for HardFloat operations..

I still need to do a lot of checkings on it..

The driver in Kernel 5.3.11, seems to be working now, about 14 seconds, a lot less from the 211 before.. but more checking is needed..

About rng-tools:
You can use in '/etc/default/rng-tools' a device like '/dev/urandom' it is the only way I could boot a 'Orange PI one Plus', because the TRNG hardware isn't yet supported( will be in kernel 5.4 I believe )..
You can try this solution has a last resort..

I will update, with my findings about what I could optimise
Thanks a lot to put me in the right track!!