You are not logged in.
- Topics: Active | Unanswered
#176 Re: Installation » Devuan on Raspberry Pi 4 - now also aarch64 » 2019-11-23 20:38:27
Hello therion23,
I tried with a Rpi1, compile a kernel, uboot, and try to boot the device..
I am stuck there..
On 'config.txt'
kernel=my-u-boot.bin
then created the boor.cmd, and scr script file, and I can boot the kernel..
The problem is that it hangs waiting for '/dev/mmbblk0p2'
So,
rpi1 execute:
1) - 'bootcode.bin', then bootcode.bin, reads 'config.txt', were it knows about my pseudo kernel( u-boot ) 'kernel=my-u-boot.bin'.
2) - It passes to VC4 to load 'start.elf'
3) - 'start.elf'( I believe ?! ) load my u-boot..
3) - my u-boot is loaded, which instructs to load the Real Kernel..
The problem... Kernel Hangs, waiting for '/dev/mmcblk0p2' 
Here are the logs taken from ttyAMA0:
port is : /dev/ttyUSB0
flowcontrol : none
baudrate is : 115200
parity is : none
databits are : 8
escape is : C-a
local echo is : no
noinit is : no
noreset is : no
nolock is : no
send_cmd is : sz -vv
receive_cmd is : rz -vv
imap is :
omap is :
emap is : crcrlf,delbs,
Terminal ready
)
## Executing script at 02400000
## Error: Can't overwrite "ethaddr"
## Error inserting "ethaddr" variable, errno=1
switch to partitions #0, OK
mmc0 is current device
12655 bytes read in 9 ms (1.3 MiB/s)
4898976 bytes read in 221 ms (21.1 MiB/s)
Kernel image @ 0x008000 [ 0x000000 - 0x4ac0a0 ]
## Flattened Device Tree blob at 02600000
Booting using the fdt blob at 0x2600000
Using Device Tree in place at 02600000, end 0260616e
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 5.3.11 (tuxd3v@desktop0) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36))) #10 Fri Nov 22 18:58:43 WET 2019
[ 0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] OF: fdt: Machine model: Raspberry Pi Model B
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] cma: Reserved 8 MiB at 0x0e800000
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 60900
[ 0.000000] Kernel command line: earlyprintk=serial,ttyAMA0,115200 console=ttyAMA0,115200n8 console=tty1 root=/dev/mmcblk0p2 rw rootwait rootfstype=ext4 elevator=noop fsck.repair=no smsc95xx.turbo_mode=N dwc_otg.lpm_enable=0 kgdboc=ttyAMA0,115200 selinux=0 noinitrd
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
[ 0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[ 0.000000] Memory: 224072K/245760K available (6889K kernel code, 665K rwdata, 2188K rodata, 468K init, 781K bss, 13496K reserved, 8192K cma-reserved)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] ftrace: allocating 24939 entries in 49 pages
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] random: get_random_bytes called from start_kernel+0x2e8/0x518 with crng_init=0
[ 0.000024] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
[ 0.000084] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
[ 0.000181] bcm2835: system timer (irq = 27)
[ 0.000717] Console: colour dummy device 80x30
[ 0.001220] printk: console [tty1] enabled
[ 0.001315] Calibrating delay loop... 697.95 BogoMIPS (lpj=3489792)
[ 0.050370] pid_max: default: 32768 minimum: 301
[ 0.050974] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.051049] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.052850] CPU: Testing write buffer coherency: ok
[ 0.054651] Setting up static identity map for 0x8200 - 0x8238
[ 0.055914] devtmpfs: initialized
[ 0.063740] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
[ 0.064288] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.064380] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[ 0.065901] pinctrl core: initialized pinctrl subsystem
[ 0.067862] NET: Registered protocol family 16
[ 0.071960] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.076890] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
[ 0.076971] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.077173] Serial: AMBA PL011 UART driver
[ 0.119919] SCSI subsystem initialized
[ 0.120275] usbcore: registered new interface driver usbfs
[ 0.120432] usbcore: registered new interface driver hub
[ 0.121020] usbcore: registered new device driver usb
[ 0.123563] clocksource: Switched to clocksource timer
[ 1.544513] VFS: Disk quotas dquot_6.6.0
[ 1.544721] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.545158] FS-Cache: Loaded
[ 1.545574] CacheFiles: Loaded
[ 1.546008] simple-framebuffer f6fb000.framebuffer: framebuffer at 0xf6fb000, 0x300000 bytes, mapped to 0x(ptrval)
[ 1.546090] simple-framebuffer f6fb000.framebuffer: format=a8r8g8b8, mode=1024x768x32, linelength=4096
[ 1.572117] Console: switching to colour frame buffer device 128x48
[ 1.595073] simple-framebuffer f6fb000.framebuffer: fb0: simplefb registered!
[ 1.616069] thermal_sys: Registered thermal governor 'step_wise'
[ 1.616929] NET: Registered protocol family 2
[ 1.618970] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[ 1.619515] TCP established hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 1.619977] TCP bind hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 1.620393] TCP: Hash tables configured (established 2048 bind 2048)
[ 1.620926] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 1.621324] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 1.622195] NET: Registered protocol family 1
[ 1.624019] RPC: Registered named UNIX socket transport module.
[ 1.624377] RPC: Registered udp transport module.
[ 1.624644] RPC: Registered tcp transport module.
[ 1.635374] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1.647450] hw perfevents: no irqs for PMU, sampling events not supported
[ 1.658382] hw perfevents: enabled with armv6_1176 PMU driver, 3 counters available
[ 1.672981] Initialise system trusted keyrings
[ 1.684376] workingset: timestamp_bits=14 max_order=16 bucket_order=2
[ 1.713463] FS-Cache: Netfs 'nfs' registered for caching
[ 1.726013] NFS: Registering the id_resolver key type
[ 1.736825] Key type id_resolver registered
[ 1.747181] Key type id_legacy registered
[ 1.757432] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 1.770306] Key type asymmetric registered
[ 1.780643] Asymmetric key parser 'x509' registered
[ 1.790870] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[ 1.801620] io scheduler mq-deadline registered
[ 1.811990] io scheduler kyber registered
[ 1.836484] bcm2835-rng 20104000.rng: hwrng registered
[ 1.870326] brd: module loaded
[ 1.896340] loop: module loaded
[ 1.907862] Loading iSCSI transport class v2.0-870.
[ 1.919594] usbcore: registered new interface driver smsc95xx
[ 1.930373] usbcore: registered new interface driver usb-storage
[ 1.941229] mousedev: PS/2 mouse device common for all mice
[ 1.953892] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[ 1.965277] sdhci: Secure Digital Host Controller Interface driver
[ 1.975797] sdhci: Copyright(c) Pierre Ossman
[ 1.986095] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.997306] ledtrig-cpu: registered to indicate activity on CPUs
[ 2.008264] hidraw: raw HID events driver (C) Jiri Kosina
[ 2.018757] usbcore: registered new interface driver usbhid
[ 2.028797] usbhid: USB HID core driver
[ 2.039867] bcm2835-mbox 2000b880.mailbox: mailbox enabled
[ 2.050636] Initializing XFRM netlink socket
[ 2.060524] NET: Registered protocol family 17
[ 2.070349] Key type dns_resolver registered
[ 2.081652] registered taskstats version 1
[ 2.091048] Loading compiled-in X.509 certificates
[ 2.109931] 20201000.serial: ttyAMA0 at MMIO 0x20201000 (irq = 81, base_baud = 0) is a PL011 rev2
[ 3.009889] random: fast init done
[ 3.912321] printk: console [ttyAMA0] enabled
[ 3.927686] raspberrypi-firmware soc:firmware: Attached to firmware from 2019-09-30 14:41
[ 3.948148] vchiq: vchiq_init_state: slot_zero = (ptrval)
[ 3.971479] Waiting for root device /dev/mmcblk0p2...
[ 212.003677] random: crng init doneCan you see the amount of time it took to initialize rng?
Maybe I need to configure it.. don't know, but I already tried, without success..maybe I am doing something wrong..
The objective...
Get Rid of Every Blob RaspberryPi trows at it..
Till now I am unsuccessful on that
Have you any advice?
Thanks in Advance,
Best Regards,
tux
#177 Devuan Derivatives » [ ARM ] Desktop » 2019-11-22 05:28:01
- tuxd3v
- Replies: 2
Hello guys,
I have seen some serious work here!! 
I need to partner with someone to build a Devuan ARM desktop version..
Is there any one interested?
I was mostly focused in { Fluxbox, Enlightment, EDE }, and themes for it..
Why not lxde or lxqt?
Its because a lot of ARM hardware has 1GB Ram Available..
So the Idea would be to Create a Lean Desktop to "fit almost them all", so it has to be max around 100MB, and without big Applications, that alone consumes all Ram memory..
Even tough that a browser will need to be provided( and here, to have functionality you need a decent browser, which entails big amount of resources..), the Idea is to have some constraints were it makes sense..
Can Any One provide his thoughts about something like this?
One Place that I have as the first reference was by fsmithred, in This Thread
I would like to have more suggestions, also from you guys
#178 Re: ARM Builds » RPi3A+/3B/3B+/(4B) » 2019-11-22 05:18:57
I am trying by make a bootable Image for rpi..
But I only have versions 1( version 2.1 died a year ago )
So I am short to compare..
For what I saw they have several kernels for different boards, I don't know if they "flash" uboot into the beginning of the sd-card, because 1st partition starts at 4MB.. exactly the size I have for the boot-loader..
It would be nice to have a fluxbox or Enlightenment version of devuan optimised
I already compiled a optimised version, of fluxbox, but it would only works in armv7- armhf( it will not in rpi v1, its too much optimized for armv7... the vfp of arm1176jzf-s will not handle it.. )..
On Par with this, I also compiled the ARM Mali Open Stack( Lima + Panfrost ).. for armhf and for arm64, but no Image yet..
#179 Re: ARM Builds » RPi3A+/3B/3B+/(4B) » 2019-11-21 15:55:49
Thanks for your help fellas.
You welcome
#180 Re: ARM Builds » RPi3A+/3B/3B+/(4B) » 2019-11-20 13:26:42
Thanks for the links. I have downloaded the RPi3 64bit version, but it extracts to a folder full of system folders, & I know the RPi usually has a FAT partition, as well as the Linux one.
Not quite sure what to do with them, do I copy the Rasbian FAT files to a FAT partition, & then all these system files into an EXT filesystem? Or do the /boot files go onto a FAT partition, & the rest onto a Linux filesystem?
Thanks for your help.
Hello,
You Welcome.
I believe that you need 2 file-systems, since '/boot/cmdline.txt', states in the kernel bootargs 'root=/dev/mmcblk0p2'( it assumes a second partition.. )
2 partitions.
1st Partition - copy /boot/* contents to it..
2nd Partition - copy all the rest to it( excluding /boot )..
There are still some doubts about the initial boot part, but I believe your line of thinking is correct
#181 Re: ARM Builds » RPi3A+/3B/3B+/(4B) » 2019-11-19 18:51:57
Hello Camtaf,
There are already images for rpi1,rpi2,rpi3 here, by @parazyd
What is still missing is a Image for rpi4,
But @parazyd landed support in the embedded sdk, 3 months ago..
You can see it in the arm-sdk, tough I don't know the level of support..
I don't have a rpi4, if I had, I would test it..
Best Regards,
tux
#182 ARM Builds » [ ARMHF ] build for Olimex OlinuXino Lime2 » 2019-11-17 03:22:22
- tuxd3v
- Replies: 1
Hello All,
This is the aarch32( armhf ) counterpart, for Linux Sunxi, Allwinner A20 Hardware..
In the next Iterations, will be also there a 'Desktop' build type..
In this case, there is a v0.5beta Server build.
Features & Versions:
1) - Arm Trusted Firmware - Mainline ( built for armhf )
U-boot boot-loader - v201910 ( built for armhf )
2) - Linux Kernel - Stable 5.7.0 + Lima driver + Cedrus driver ( built for armhf )
3) - UserSpace - Devuan Beowulf ( for armhf )
4) - Changelog - Kernel Update, HDMI Audio driver, UPS Monitoring, WireGuard VPN Kernel Driver
5) - Known Problems - Activating Zram, doesn't hapen automatically, but it should need more investigation..
1) BootLoader( aarch32.. only u-boot )
Disk Partitioning scheme:
# parted /dev/mmcblk0
(...)
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 101MB 99.6MB primary ext2
2 101MB 1500MB 1399MB primary ext4a) - Bootloader( Arm Trusted Firmware + U-Boot ), is between [ beginning - 1st partition ]( starting at sector 16( 8KiB ), til 1MiB )
a1) - The Bootloader will search for a file called 'boot.scr', and after initialise the u-boot environment, will execute that script..
a2) - In 'boot.scr', for this image, it will point to 'Olimex Olinuxino Lime2' Device Tree Binary File by default( was tested there.. )..
a3) - IF you have other board than 'Olimex Olinuxino Lime2', please Read Bellow in the 'Notes Section'..
b) - 1st Partition( after BootLoader ) is mounted as '/boot'
c) - 2nd Partition is mounted as rootfs '/'
NOTA!
The Bootloader in a) usually takes ~600KiB..
Each time a bootloader is built, all area [ 8KiB - 1MiB ], needs to be clean first( so that you can flash the new bootloader.. because could still be there any bits of the previous one.. which could lead to unpredictable consequences.. ).
If you have Other Board than 'Olimex Olinuxino Lime2', situation described in a3):
The 'boot.cmd' script( format, Human Readable ):
# Send debug info to uart, and also display
setenv stdout serial,vga
setenv stderr serial,vga
setenv bootargs debug=on console=ttyS0,115200 earlyprintk root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait fsck.repair=yes panic=15
setenv fdtfile sun7i-a20-olinuxino-lime2.dtb
load mmc 0:2 0x43000000 usr/lib/linux-image-5.7.0/${fdtfile}
load mmc 0:1 0x42000000 vmlinuz
bootz 0x42000000 - 0x43000000Write this Image, to a sd-card.
Mount 1st Partition in '/mnt',
mount /dev/sdb1 /mntThen change the 'boot.cmd' script to point to your board..
# You can find a list of supported boards 'dtb' files in: '/usr/lib/linux-image-5.4.6'
# Edit the file 'boot.cmd', with 'vi' for example.
# change the line:
setenv fdtfile sun7i-a20-olinuxino-lime2.dtbto
setenv fdtfile your_board.dtbSave the file,
# Generate the real script file( binary ), 'boot.scr'
mkimage -C none -A arm -T script -d /mnt/boot.cmd /mnt/boot.scrDone!
2) Linux Kernel
Packages:
There are 3 packages installed( in the future will be at least the graphics drivers more.. ):
# dpkg -l |grep -E "(linux-.*(headers|image|libc-dev))"
ii linux-headers-5.7.0 5.7.0-5 armhf Linux kernel headers for 5.7.0 on armhf
ii linux-image-5.7.0 5.7.0-5 armhf Linux kernel, version 5.7.0
ii linux-libc-dev:armhf 5.7.0-5 armhf Linux support headers for userspace developmentThe target will be to reach, at least the Linux kernel 5.{7,8}( since there still are few things that need support, but not much.. ), and of course.. work improve the Device Tree Bindings, for each board, when possible.. most important things missing HDMI Audio Codec( see 5.d), included now ), and keypad driver..
3) UserSpace -Users & Passwords:
a) root - password 'toor'
b) devuan - password 'devuan'
NOTA!
SSH is enabled, so that you can login, but root login, is disabled, you should login as 'devuan', only then switch to 'root', if you want to.. for that,
After Login as 'devuan', issue:
sudo su -And type your 'devuan' password, that's it..
4) ChangeLog
a) - Migration to Devuan Beowulf
b) - sun4i_ss prng driver( no more need to use /dev/urandom in rng-tools config.. )
c) - Realtek Network Driver( not generic one.. )
d) - Micrel Network Driver( Newer Boards come with it.. )
e) - Audio sun4i_codec Driver.. see Section 5d)
f) - Kernel Update to 5.7.0
g) - sun4i-csi - Camera{ BT656, Parallel }, activated
h) - Hardware VPU Decode Acceleration, now supports( MJPEG, MPEG2, H.264, HEVC/H.265 )
i) - 3d Graphics Kernel Driver( Lima )
j) - UPS Monitoring Script
k) - WireGuard VPN Kernel Driver( present in Linux since 5.6 kernel )
5) Known Problems or Things to test
a) - Activating Zram, doesn't happen automatically( but it should.. need more investigation.. ).
b) - Testing is needed, on camera interfaces { BT656, Parallel } merged in Kernel 5.5.0 for Allwinner A20 drivers sun4i-csi ..
c) - Compile V4l2 Cedrus driver, test it via libvdpau..
d) - HDMI Audio Codec, was submitted in January 2020, Included here as a V3 patch!Tested and Working OK!
e) - Lima Kernel Driver, needs the Userspace Kernel Side( Lima Mesa Driver )
f) - Tests on UPS monitoring Script, shows it his working OK!
g) - WireGuard VPN, needs Compilation of Userspace tools, and testing..
For this image, to reach more Supported Hardware and Users, your help is also needed
Testing this image, posting your feedback, and improvements..
SHA256sum:
$ sha256sum devuan_beowulf_3.0.0_armhf_olinuxino_lime2_0.5.img.xz
9ca1c9293ac6a0edea431d04b4face2fbbe914c1422eb5704da4864c706a4ae9 devuan_beowulf_3.0.0_armhf_olinuxino_lime2_0.5.img.xzBest Regards,
tux
#183 ARM Builds » [ ARM64 ] build, for Orange PI One Plus » 2019-11-14 03:35:44
- tuxd3v
- Replies: 0
Hello All,
As you probably know, there are an effort, to bring Sunxi Hardware to mainline( Leaving behind each proprietary, vendor builders, tool-chains, and blobs.. we hope ) here :
This release is a major release for this board, as it brings the board to a stable, and almost complete full feature,situation..
This is a revision v0.8 Server build.
Features & Versions:
1) - Arm Trusted Firmware - v2.3 ( built for arm64 )
U-boot boot-loader - v2020.07 ( built for arm64 )
2) - Linux Kernel - Stable 5.8.1 ( built for arm64 )
3) - UserSpace - Devuan Beowulf ( for arm64 )
4) - ChangeLog - ATF v2.3, Uboot v2020.07, kernel 5.8.1,{ DVFS, IOMMU, Message Box, SPI } new Allwinner H6 drivers, wireguard vpn driver
5) - Problems & to be done - After coming to Beowulf, its impossible to auto-mount zramfs as swap, automatically..after reboot network doesn't start, duo to regulator vcc-gmac-3v3. not being enabled in that situation( only in reboot situation )
1) BootLoader( ATF + u-boot )
Disk Partitioning scheme:
# parted /dev/mmcblk0
(...)
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 101MB 99.6MB primary ext2
2 101MB 1700MB 1599MB primary ext4a) - Bootloader( Arm Trusted Firmware + U-Boot ), is between [ beginning - 1st partition ]( starting at sector 16( 8KiB ), til 1MiB )
a1) - The Bootloader will search for a file called 'boot.scr', and after initialise the u-boot environment, will execute that script..
a2) - In 'boot.scr', for this image, it will point to 'Orange PI One Plus' Device Tree Binary File by default( was tested there.. )..
a3) - If you have other board than 'Orange PI One Plus', please Read Bellow in the 'Notes Section'..
b) - 1st Partition( after BootLoader ) is mounted as '/boot'
c) - 2nd Partition is mounted as rootfs '/'
NOTA!
The Bootloader in a) usually takes ~600KiB..
Each time a bootloader is built, all area [ 8KiB - 1MiB ], needs to be clean first( so that you can flash the new bootloader.. because could still be there any bits of the previous one.. which could lead to unpredictable consequences.. ).
If you have Other Board than 'Orange PI One Plus', situation described in a3):
The 'boot.cmd' script( format, Human Readable ):
# setup MAC address
setenv ethaddr 7E:8C:70:59:B5:70
# set console to tty0
setenv console tty0
# Send debug info to uart, and also display
setenv stdout serial,vga
setenv stderr serial,vga
setenv bootargs debug=on earlyprintk=serial,tty0,115200n8 console=tty0 console=ttyS0,115200 earlyprintk root=/dev/mmcblk0p2 rw rootfstype=ext4 fsck.repair=yes rootwait
setenv fdtfile allwinner/sun50i-h6-orangepi-one-plus.dtb
load mmc 0:2 0x43000000 usr/lib/linux-image-5.8.1/${fdtfile}
load mmc 0:1 0x42000000 vmlinuz
booti 0x42000000 - 0x43000000Write this Image, to a sd-card, then mount it, and change the 'boot.cmd' script to point to your board..
# You can find a list of supported boards in: '/usr/lib/linux-image-5.8.1/allwinner'
# Edit the file 'boot.cmd', with 'vi' for example.
# change the line:
setenv fdtfile allwinner/sun50i-h6-orangepi-one-plus.dtbto
setenv fdtfile allwinner/your_board.dtbSave the file,
# Generate the real script file( binary ), 'boot.scr'
mkimage -C none -A arm64 -T script -d boot.cmd boot.scr2) - Linux Kernel
Packages:
There are 3 packages installed( in the future will be at least Userspace Panfrost mesa-3d graphics drivers more.. for a desktop version..):
~# dpkg -l |grep -E "(linux-.*(headers|image|libc-dev))"
ii linux-headers-5.8.1 5.8.1-3 arm64 Linux kernel headers for 5.8.1 on arm64
ii linux-image-5.8.1 5.8.1-3 arm64 Linux kernel, version 5.8.1
ii linux-libc-dev:arm64 5.8.1-3 arm64 Linux support headers for userspace developmentThe target will be to reach, at least Linux kernel 5.8, or more if needed, have lot of new features for ARM hardware.. ), and also work in the Device Tree Bindings, for each board..
3) - UserSpace -Users & Passwords:
1) root - password 'toor'
2) devuan - password 'devuan'
NOTA!
SSH is enabled, so that you can login, but root login, is disabled, you should login as 'devuan', only then switch to 'root', if you want to.. for that,
After Login as 'devuan', issue:
sudo su -And type your 'devuan' password, that's it..
4) - Changelog
a) kernel update to 5.5.0 5.6.3,5.8.1
b) Thermal driver( as patch )., will be officially added to kernel 5.6..( added on kernel 5.6.3 )
c) Hardware VPU Decode Acceleration, now supports( MJPEG, MPEG2, H.264, HEVC/H.265 )( CEDRUS driver )
d) 3d Video Driver - Pandrost( Kernel Side )
e) Allwiner Crypto Driver
f) { IR, RTC, SPDIF } Kernel Driver test Handlers, including decoders for RAW IR( NEC, RC5(x/sz), RC6, JVC, Sony. SANYO, Sharp, MCE Keyboard/mouse, XMP )
g) Its now possible to boot, without assigning '/dev/urandom' to crng, but a dedicated TRNG driver will come, possibly on 5.6 Kernel it will possibly be merged in the next month, so expect it for 5.7 maybe....
h) PWM driver
i) PMU driver
j) disable red Led, change green to trigger [activity]
k) addition of { DVFS, IOMMU, Message Box, SPI } drivers... DVFS enabled from [ 480 MHz - 1.80 GHz ]( if you pretend to use it in a continuous full load situation, prepare a small heatsink, and small fan above, it would stay ~70°C on those conditions.. )
5) - Problems and testings to be done..
a) After migration to beowulf, its impossible, for now, to automount zramfs as swap, automatically.. we are issuing swapon -a in '/etc/rc.local'.
it could be related with several packages, including those( most probably): init init-system-helpers initscripts insserv eudev mawk sed
b) Testing is needed, on camera interfaces { BT656, Parallel } merged in Kernel 5.4 for Allwinner Multiple aarch64 SoCs drivers sun8i-csi ..
c) Compile V4l2 Cedrus driver, test it via libvdpau..
d) Test IR driver shipped in Kernel 5.4 for Allwinner A64/H6..
e) Compile UserSpace Mesa Panfrost Driver stack( userspace counterpart for kernel space one.. )
f) USB Driver is still in PIO mode, no DMA yet, and uses some CPU, with transfers rate of ~10MB/s..
g) Test PWM
h) If you reboot your board{ reboot | shutdown -r now }, vcc-gmac-3v3 regulator, doesn't appear enabled( more investigation is needed.. use shutdown -h now, or press the power button.. ).
For this image, to reach more Supported Hardware and Users, your help is also needed
Testing devuan-beowulf-sunxi-arm64-0.8-beta, and posting your feedback.
SHA256sum:
$ sha256sum devuan_beowulf_3.0.0_arm64_orangepi_one_plus_0.8.img.xz
8cc1d5ab28945b0532a770242b46e0a9e34a6123f87d536ae6c9920480a57a16 devuan_beowulf_3.0.0_arm64_orangepi_one_plus_0.8.img.xzBest Regards,
tux
Board footer
