Rock64 fedora core 29 boot issue: Help please?

[forwardbackwards]

I've been trying to get opensuse Tumbleweed to boot on my 2Gb rock64.

The image I used was downloaded from:
https://download.opensuse.org/repositori...ip/images/

After dd'ing the image to the emmc, I installed the Arch u-boot using this install guide:
https://archlinuxarm.org/platforms/armv8...hip/rock64

Using these kernel arguments in grub2/grub.cfg . I'm able to see where the boot process stops:

$linux ($root)//Image-4.19.5-1-default ${extra_cmdline} loglevel=7 earlycon=uart8250,mmio32,0xff130000 console=ttyS0,1500000n8 splash=silent plymouth.enable=0  root=UUID=d90c3637-cea7-412c-8aa7-e3a5a47dad39 rw

So after unpacking the initramfs, it stops after saying it can't open the rtc.

[ 29.068003] Freeing initrd memory: 30036K
[ 29.071144] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
[ 29.072396] kvm [1]: 8-bit VMID
[ 29.074816] kvm [1]: vgic interrupt IRQ1
[ 29.075557] kvm [1]: Hyp mode initialized successfully
[ 29.081276] Initialise system trusted keyrings
[ 29.082177] workingset: timestamp_bits=44 max_order=19 bucket_order=0
[ 29.083355] zbud: loaded
[ 29.086027] pstore: using deflate compression
[ 29.101879] Key type asymmetric registered
[ 29.102309] Asymmetric key parser 'x509' registered
[ 29.102901] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244)
[ 29.103982] io scheduler noop registered
[ 29.104388] io sched[ 29.104995] io scheduler cfq registered (default)
[ 29.105[ 29.105954] io scheduler bfq registered
[ 29.115404] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 29.136242] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 29.163163] Serial: AMBA driver
[ 29.164563] msm_serial: driver initialized
[ 29.167928] cacheinfo: Unable to detect cache hierarchy for CPU 0
[ 29.170729] libphy: Fixed MDIO Bus: probed
[ 29.172295] mousedev: PS/2 mouse device common for all mice
[ 29.181473] ledtrig-cpu: registered to indicate activity on CPUs
[ 29.182859] EFI Variables Facility v0.08 2004-May-17
[ 29.183463] efivars: get_next_variable: status=8000000000000007
[ 29.184227] hidraw: raw HID events driver © Jiri Kosina
[ 29.189808] NET: Registered protocol family 10
[ 29.227610] Segment Routing with IPv6
[ 29.230255] registered taskstats version 1
[ 29.230691] Loading compiled-in X.509 certificates
[ 29.231347] zswap: loaded using pool lzo/zbud
[ 29.261624] cryptd: max_cpu_qlen set to 1000
[ 29.290314] Key type big_key registered
[ 29.318665] Key type encrypted registered
[ 29.319101] AppArmor: AppArmor sha1 policy hashing enabled
[ 29.319728] ima:p found, activating TPM-bypass!
[ 29.320325] ima: Allocated h[ 29.320986] evm: Initialising EVM extended attributes:
[ 229.321845] evm: security.apparmor
[ 29.322192] evm: security.61] evm: HMAC attrs: 0x1
[ 29.370627] hctosys: unable to open rtc device (rtc0)

checking for rtc in the device tree blob show no entry:
fdtdump rk3328-rock64.dtb |grep rtc

Checking the kernel config does show 2 entries:
cat config-4.19.5-1-default |grep rtc
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
CONFIG_RTC_SYSTOHC_DEVICE="rtc0"

When I boot ayuran's bionic image I see that the rtc is provided by:
  dmesg
    rk808-rtc rk808-rtc: rtc core: registered rk808-rtc as rtc0

I posted this same info on opensuse's arm mailing list, but I haven't gotten any response yet.
  https://lists.opensuse.org/opensuse-arm/...00016.html

I don't know how to fix this, but maybe this information will help you.

Thanks.

Mark

Awesome .... This looks like it could be helpful with what looks like an early console thanks! 

As for your issue... Did you check to see if the rtc is actually provided in your opensuse initramfs?   Did you check ayufans dtb for the rtc entry?  Possibly add his rtc entry to your dtb. 

I'm currently sorting through the opensuse and fedora grub2 patches to look at the differences between the two.  Going to take a wee bit.  I found a few differences and started creating patches.  

Cheers!