Jump to content

CSC Armbian for RK3318/RK3328 TV box boards


jock
 Share

Recommended Posts

2 hours ago, MBB said:

I have flashed an X88 Pro 10 box and run rk3318-config.  Wifi is identified as BCM4334 correctly and works.  Bluetooth is found but using XFCE 'devices' option, finds none.  I tried a second model (H96 Max) and it behaves the same.  If I plug in a TP Link bluetooth adapter, devices are found and work fine.  Anyone else running into this?

That's strange bluetooth does not work, AP6334/BCM4334 should be well supported. My box has the same chip and works fine.

dmesg may give some hints about, also a photo of the board and the original dtb may help.

Link to comment
Share on other sites

Donate and support the project!

1 hour ago, jock said:

I guess that you have the bcm43342 wifi part; dmesg will tell what firmware is actually needed for bluetooth.

It may be that

Probably here the led has the polarity inverted (active low vs. active high) in the device tree.

Grazie a te, gentilissimo ;)

 

 

i have the same board of @markst precisely a X88-PRO-B-RK3318-D4-V1.2, but selled with a different name (QPLOVE Q9 4/128 [ram/emmc]) so maybe something is different, wifi works bth not.
And as the others guys with 4gb ram i can only use 2gb of ram.

image.thumb.png.e7232e08558b38a2eb81a5fbbb4e5f64.pngimage.thumb.png.b213be745e6bbdef98a3fb75a225f816.png

 

Firmware: BCM4330/4 wl0

Link to comment
Share on other sites

@MR01 looking at the dmesg screenshot you have a BCM4330 and not BCM43342 as @markst has, so they are totally different chips.

You probably have an AP6330 "package" on the board, which comprises of both wifi and bluetooth. BCM4330 is the wifi part, the bluetooth part is another completely different chip.

From that screenshot I can't say anything: those red lines are just for the wifi part. The seem errors, but are actually "information" messages (the guy who wrote the driver just used the wrong function call dev_err() instead of dev_info() probably)

Full dmesg is required because errors and messages about bluetooth may be scattered among the log.

Link to comment
Share on other sites

2 hours ago, jock said:

 

You probably have an AP6330 "package" on the board

AP6330 with a metal plate.

 

Quote

root@rk3318-box:~# dmesg | grep -i blue
[    8.009535] Bluetooth: Core ver 2.22
[    8.009740] NET: Registered PF_BLUETOOTH protocol family
[    8.009753] Bluetooth: HCI device and connection manager initialized
[    8.009783] Bluetooth: HCI socket layer initialized
[    8.009795] Bluetooth: L2CAP socket layer initialized
[    8.009840] Bluetooth: SCO socket layer initialized
[    8.161276] Bluetooth: HCI UART driver ver 2.3
[    8.161321] Bluetooth: HCI UART protocol H4 registered
[    8.161329] Bluetooth: HCI UART protocol BCSP registered
[    8.161498] Bluetooth: HCI UART protocol LL registered
[    8.161513] Bluetooth: HCI UART protocol ATH3K registered
[    8.161608] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    8.162107] Bluetooth: HCI UART protocol Intel registered
[    8.162679] Bluetooth: HCI UART protocol Broadcom registered
[    8.162847] Bluetooth: HCI UART protocol QCA registered
[    8.162864] Bluetooth: HCI UART protocol AG6XX registered
[    8.162956] Bluetooth: HCI UART protocol Marvell registered
[    8.551727] Bluetooth: hci0: BCM: chip id 62
[    8.552567] Bluetooth: hci0: BCM: features 0x0f
[    8.554381] Bluetooth: hci0: BCM4330B1
[    8.554418] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0000
[    8.563141] Bluetooth: hci0: BCM4330B1 'brcm/BCM4330B1.hcd' Patch
[    9.345127] Bluetooth: hci0: BCM4330B1 37.4 MHz Class 1 Ampak
[    9.345172] Bluetooth: hci0: BCM4330B1 (002.001.003) build 0000
[    9.345903] Bluetooth: hci0: BCM: Using default device address (43:30:b1:00:00:00)
[    9.358938] systemd[1]: Reached target Bluetooth.


Seems recognized and working NOW, yesterday didnt and i tried many times with many reboots, the only thing i did in late night (so right before now dmesg) was set in rc.local "ifconfig wlan0 down" because im using a powerfull external usb dongle.

So maybe when wifi is off bth works? Im not fond of kernel/drivers in general so maybe is no-sense.

I dont plan to use bth anyway.

Ps: im using this box as a powerfull switch WIFI>ETH because my house is on 2 plans and my only telephone port is in the plan down my actual pc and there must be the router....plus every plan is electrically "indipendent" with 2 different save-life (so i dont even try to use powerline), so for better signal i will put the box in a better position with a ethernet cable running side-wall from the box to my pc

dmesg.txt

Link to comment
Share on other sites

On 5/2/2022 at 2:45 PM, jock said:

That's strange bluetooth does not work, AP6334/BCM4334 should be well supported. My box has the same chip and works fine.

dmesg may give some hints about, also a photo of the board and the original dtb may help.

Board photo and dmesg attached.  Note this model is called "H96 max v11" which I gather is due to it shipping with Android 11.  It doesn't matter which LED overlay is selected, with either, bluetooth is detected but can't find any devices.  RK3318-config identifies WiFi as "BCM334/AmPak AP6334".  The markings on the chip itself, however, don't seem helpful.  Note the marking on the board is "KX 1943...".

PXL_20220504_193858652.jpg

dmesg_h96_max_v11

Link to comment
Share on other sites

@MBB these lines in dmesg are pretty clear:

[   13.024841] Bluetooth: hci0: BCM: chip id 83
[   13.025663] Bluetooth: hci0: BCM: features 0x0f
[   13.027568] Bluetooth: hci0: BCM43342A
[   13.027624] Bluetooth: hci0: BCM (001.002.003) build 0000
[   13.036065] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[   13.036111] Bluetooth: hci0: BCM: 'brcm/BCM.hcd'

 

There is no firmware for your bluetooth chip. The problem has been seen in the past, but has not been solved because we could not guess what is the filename the bluetooth driver is looking for.

It finally tries to look to /lib/firmware/brcm/BCM.hcd file and you should try to do a symbolic link to some of the bcm4334*.hcd firmware file to see if any of them works.

Now I don't remember which one works, but surely there is a discussion with a forum member that had this working, maybe the forum search tool can help you.

 

Link to comment
Share on other sites

4 hours ago, jock said:

@MBB these lines in dmesg are pretty clear:

[   13.024841] Bluetooth: hci0: BCM: chip id 83
[   13.025663] Bluetooth: hci0: BCM: features 0x0f
[   13.027568] Bluetooth: hci0: BCM43342A
[   13.027624] Bluetooth: hci0: BCM (001.002.003) build 0000
[   13.036065] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[   13.036111] Bluetooth: hci0: BCM: 'brcm/BCM.hcd'

 

There is no firmware for your bluetooth chip. The problem has been seen in the past, but has not been solved because we could not guess what is the filename the bluetooth driver is looking for.

It finally tries to look to /lib/firmware/brcm/BCM.hcd file and you should try to do a symbolic link to some of the bcm4334*.hcd firmware file to see if any of them works.

Now I don't remember which one works, but surely there is a discussion with a forum member that had this working, maybe the forum search tool can help you.

 

@jock, Thanks for the tip.  Now I understand how this is supposed to work.  I was able to get it working, but only using a symbolic link from BCM.hcd to BCM43342.hcd.  It looked like the filename would be BCM43342A1 (see dmesg below), but no such luck with that link.  In reading the previous posts, it seems @awawahad the same issue, but I may be reading it wrong.  So I am not sure how to cleanly fix this.  At least we know BCM43342.hcd works.  Happy to test anything you'd recommend.  But thank you for helping me get it at least working!

test

Link to comment
Share on other sites

3 hours ago, MR01 said:


The user @hannah had the same AP6330 and bth BCM4330B1 in a s905x3 box and fixed with meson-sm1-sei610-x96maxplus.dtb
Im adding this info for future reference and fixing/implementation @jock

meson-sm1-sei610-x96maxplus.dtb 46.07 kB · 1 download

Understand, but AP6330 should work both for wireless and bluetooth parts right now on rk3318/3328 - everything is already in place and implementation is right since, as you see, it works.

The issue you had must be investigated with more tests to get into the real cause (rfkill? wrong dtb? ...)

 

I have AP6330 in a rk3288 box and both wifi and bluetooth works well.

There are issue though when you do a lot of traffic at the same time with both devices, because co-existance is difficult on 2.4ghz channel and I never really digged into the issue.

 

Link to comment
Share on other sites

hi @jock, about rk3318-config , i'm using H96 Max rk3318 4/64 (Black PCB)

1. should i choose emmc DDR Mode or emmc HS200 Mode ? currently i don't choose any of these options since i'm not sure which one suits my device

2. there are LED Presets, but not H96Max, is one of them support my board ? currently i choose the last option (generic/unlisted)

 

kindly let me know if you need a photo of my device board to help me choose the right options

 

Thanks !

Link to comment
Share on other sites

7 minutes ago, Buqan Kaleng Kaleng said:

hi @jock, about rk3318-config , i'm using H96 Max rk3318 4/64 (Black PCB)

1. should i choose emmc DDR Mode or emmc HS200 Mode ? currently i don't choose any of these options since i'm not sure which one suits my device

2. there are LED Presets, but not H96Max, is one of them support my board ? currently i choose the last option (generic/unlisted)

 

kindly let me know if you need a photo of my device board to help me choose the right options

 

Thanks !

Hello @Buqan Kaleng Kaleng

1. you should try and see which one works for your board. You can enable both of them: and a valid board, the kernel will choose the best option and it will just work. On a so-so board it may happen that the kernel choice does not really work and the board may have issues to detect the internal eMMC; then you need to use to use multitool to manually tinker with /etc/armbianEnv.txt and do trial and error to find which one works for you. If you are not skilled enough or are afraid to lose the installed system, keep both of them disabled so the safest (but slowest) capability will be used

2. H96Max is the tv box market name; we don't use the market name because the same tvbox can contain many different boards: you have to open the case and see the signature printed on the board PCB

Link to comment
Share on other sites

2 minutes ago, Buqan Kaleng Kaleng said:

and also, is it ok to re-run rk3318-config and change some options/parameters after some days usage ?

will it cause any problem/conflicts with system ?

It is perfectly ok and safe to do: you may want to change and test other parameters, it will not cause any conflict of any kind, at least if you don't modify manually the overlays line in /etc/armbianEnv.txt

 

Link to comment
Share on other sites

8 hours ago, jock said:

Understand, but AP6330 should work both for wireless and bluetooth parts right now on rk3318/3328 - everything is already in place and implementation is right since, as you see, it works.

The issue you had must be investigated with more tests to get into the real cause (rfkill? wrong dtb? ...)

 

I have AP6330 in a rk3288 box and both wifi and bluetooth works well.

There are issue though when you do a lot of traffic at the same time with both devices, because co-existance is difficult on 2.4ghz channel and I never really digged into the issue.

 

Yeah, I already though of some co-existance issues so previously tried turning WiFi off completely.  That didn't help.  And with WiFi on, it works just fine with the BCM.hcd symlink to BCM43342.hcd .  I agree everything is there, but it seems it is looking for a different filename so doesn't find the working BCM43342.hcd file and only works via the fallback symlink I added. Since it can't find what it is looking for, seems it can't be any other existing file.  So how to guess the right name to symlink?  For now, the fallback works for me, but I agree, not a very universal solution.

Link to comment
Share on other sites

Hi everyone,
I'm looking to set up a minimal gui under wayland but it's not easy for a beginner.
I found https://github.com/arcbjorn/arc-arch-linux-installation-guide#for-full-desktop-gui
But it's based on arch linux and I struggle a bit to adapt..
So I'm trying to post here to see if some of us can manage a script for installing a minimal gui under wayland.. or if you think it's a waste of time to try this experiment (for the instant..)
Thanks again and again armbian is great..!

Link to comment
Share on other sites

2 hours ago, MX10.AC2N said:

Hi everyone,
I'm looking to set up a minimal gui under wayland but it's not easy for a beginner.
I found https://github.com/arcbjorn/arc-arch-linux-installation-guide#for-full-desktop-gui
But it's based on arch linux and I struggle a bit to adapt..
So I'm trying to post here to see if some of us can manage a script for installing a minimal gui under wayland.. or if you think it's a waste of time to try this experiment (for the instant..)
Thanks again and again armbian is great..!


I did install lightdm+lxde[core-minimal] on debian minimal without big problems.
But i removed all after finding out that hw accelleration didnt work on 5.15 kernel, so chrome will not run at all for example, and i old kernel was not running my usb dongle by default.

Link to comment
Share on other sites

19 hours ago, MR01 said:


I did install lightdm+lxde[core-minimal] on debian minimal without big problems.
But i removed all after finding out that hw accelleration didnt work on 5.15 kernel, so chrome will not run at all for example, and i old kernel was not running my usb dongle by default.

I guess lightdm+lxde are not under wayland but rather regular X.org.

About hw acceleration, what do you mean? Both 3D acceleration via GPU and hw video decoding through VPU works on all recent mainline kernels, Chrome is just not able to deal with them: that's a long way to get there.

Link to comment
Share on other sites

47 minutes ago, jock said:

I guess lightdm+lxde are not under wayland but rather regular X.org.

About hw acceleration, what do you mean? Both 3D acceleration via GPU and hw video decoding through VPU works on all recent mainline kernels, Chrome is just not able to deal with them: that's a long way to get there.


Chrome probably is missing OpenGL/OpenGL ES features that mainline kernel miss.
My bad on 3D with Lima driver.

Link to comment
Share on other sites

This subject is precisely my question: so 3D video acceleration is already enabled by default? In some post the developer had said that he had disabled it. Sorry if I didn't pay attention to some previous explanation, but I'm confused about this topic, even if I can disable/enable it through some command via Terminal.

Link to comment
Share on other sites

57 minutes ago, Sigma7 said:

This subject is precisely my question: so 3D video acceleration is already enabled by default? In some post the developer had said that he had disabled it. Sorry if I didn't pay attention to some previous explanation, but I'm confused about this topic, even if I can disable/enable it through some command via Terminal.

I may remember not so well because rk3318 received little attention lately, but it should be enable and provided via opensource Lima driver.

You can check if AccelMethod is set to "glamor" (enabled) or "none" (disabled) in /etc/X11/xorg.conf.d/40-serverflags.conf

As usual, it is wise to disable compositing for a bit better performance in a typical desktop usage.

Link to comment
Share on other sites

15 hours ago, jock said:

I may remember not so well because rk3318 received little attention lately, but it should be enable and provided via opensource Lima driver.

You can check if AccelMethod is set to "glamor" (enabled) or "none" (disabled) in /etc/X11/xorg.conf.d/40-serverflags.conf

As usual, it is wise to disable compositing for a bit better performance in a typical desktop usage.

i only have /etc/X11/xorg.conf.d/01-armbian-defaults.conf
I dont think i removed or deleted it by accident because i never installed DE in this installation of minimal.

Link to comment
Share on other sites

Hello, guys!

 

This would be my first post in the forum and I want to thank everyone contributing to the Armbian effort - I haven't had that much fun tinkering since forever!

 

My question is related to the RAM detection - I've scoured this thread as well as the possible other places for information, but couldn't find quite the same case, even though it's referenced at least 3 times inside this thread:

 

Multitool and Armbian only pick up 2 GB of ram; I've opened the box and there are 8 total K4B4G0446C chips on it (4 on each side). According to other posts, the data in the datasheet is shown in Gb instead of GB and, if my calcualtions are correct, it has 4 x 4 Gb, two on each side = 32 Gb = 4 GB RAM.

 

Is it possible that only one half is operational? If these are binned chips, is it possible for them to be halved? In all other cases regarding the RAM capacity that I've read about here the TV box already came with the wrong RAM size. In another forum users reported halving of the RAM after an Android firmware update, but there was an (Android) image that fixed the issue (I wouldn't know if it was fake or fixed a software bug).

 

The board is X88 PRO-B-RK3318-D4-V1.2 4 GB RAM (allegedly)/ 32GB ROM model (even though 64 ROM was ordered). As you can probably guess, before installing Armbian, Android reported 4 GB RAM/64 GB ROM, but all apps for filling up the RAM couldn't be installed.

 

Images of the board can be found here - https://imgur.com/a/wTQqXO5; armbian hardware log - http://ix.io/3XvN;

 

dmesg:

Spoiler

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.15.35-rockchip64 (root@armbianbuild) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #trunk SMP PREEMPT Sat Apr 23 11:35:27 UTC 2022
[    0.000000] Machine model: Rockchip RK3318 BOX
[    0.000000] efi: UEFI not found.
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000000200000-0x000000007fffffff]
[    0.000000] NUMA: NODE_DATA [mem 0x7fbb0100-0x7fbb1fff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000000200000-0x000000007fffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000200000-0x000000007fffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000200000-0x000000007fffffff]
[    0.000000] cma: Reserved 128 MiB at 0x0000000075800000
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] psci: SMC Calling Convention v1.2
[    0.000000] percpu: Embedded 29 pages/cpu s80856 r8192 d29736 u118784
[    0.000000] pcpu-alloc: s80856 r8192 d29736 u118784 alloc=29*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 515592
[    0.000000] Policy zone: DMA
[    0.000000] Kernel command line: root=UUID=555d5f40-230b-479b-a5a2-3add1353d307 rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=534ffe7a-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u   cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[    0.000000] Unknown kernel command line parameters "ubootpart=534ffe7a-01 cgroup_enable=memory cgroup_memory=1", will be passed to user space.
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off
[    0.000000] Memory: 1877100K/2095104K available (15872K kernel code, 2688K rwdata, 6532K rodata, 4288K init, 580K bss, 86932K reserved, 131072K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] trace event string verifier disabled
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu:     RCU event tracing is enabled.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4.
[    0.000000]     Trampoline variant of Tasks RCU enabled.
[    0.000000]     Rude variant of Tasks RCU enabled.
[    0.000000]     Tracing variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] Root IRQ handler: gic_handle_irq
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] random: get_random_bytes called from start_kernel+0x838/0xa1c with crng_init=0
[    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[    0.000002] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[    0.001376] Console: colour dummy device 80x25
[    0.001443] printk: console [tty1] enabled
[    0.001605] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[    0.001632] pid_max: default: 32768 minimum: 301
[    0.001795] LSM: Security Framework initializing
[    0.001854] Yama: becoming mindful.
[    0.002023] AppArmor: AppArmor initialized
[    0.002200] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.002234] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.006114] rcu: Hierarchical SRCU implementation.
[    0.009294] EFI services will not be available.
[    0.010086] smp: Bringing up secondary CPUs ...
[    0.011247] Detected VIPT I-cache on CPU1
[    0.011363] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.012829] Detected VIPT I-cache on CPU2
[    0.012938] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.014300] Detected VIPT I-cache on CPU3
[    0.014402] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.014603] smp: Brought up 1 node, 4 CPUs
[    0.014628] SMP: Total of 4 processors activated.
[    0.014640] CPU features: detected: 32-bit EL0 Support
[    0.014649] CPU features: detected: 32-bit EL1 Support
[    0.014661] CPU features: detected: CRC32 instructions
[    0.034786] CPU: All CPU(s) started at EL2
[    0.034856] alternatives: patching kernel code
[    0.037811] devtmpfs: initialized
[    0.060057] Registered cp15_barrier emulation handler
[    0.060098] Registered setend emulation handler
[    0.060507] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.060568] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.068854] pinctrl core: initialized pinctrl subsystem
[    0.070116] DMI not present or invalid.
[    0.071072] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.076237] DMA: preallocated 2048 KiB GFP_KERNEL pool for atomic allocations
[    0.077830] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.081064] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.081216] audit: initializing netlink subsys (disabled)
[    0.081650] audit: type=2000 audit(0.080:1): state=initialized audit_enabled=0 res=1
[    0.083253] thermal_sys: Registered thermal governor 'fair_share'
[    0.083270] thermal_sys: Registered thermal governor 'bang_bang'
[    0.083279] thermal_sys: Registered thermal governor 'step_wise'
[    0.083287] thermal_sys: Registered thermal governor 'user_space'
[    0.083834] cpuidle: using governor menu
[    0.084430] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.084639] ASID allocator initialised with 65536 entries
[    0.086508] Serial: AMBA PL011 UART driver
[    0.108447] platform ff3c0000.hdmi: Fixing up cyclic dependency with ff370000.vop
[    0.135034] rockchip-gpio ff210000.gpio0: probed /pinctrl/gpio0@ff210000
[    0.136466] rockchip-gpio ff220000.gpio1: probed /pinctrl/gpio1@ff220000
[    0.137857] rockchip-gpio ff230000.gpio2: probed /pinctrl/gpio2@ff230000
[    0.139094] rockchip-gpio ff240000.gpio3: probed /pinctrl/gpio3@ff240000
[    0.174472] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.174502] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.174516] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.174531] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    0.180690] cryptd: max_cpu_qlen set to 1000
[    0.261547] raid6: neonx8   gen()  1046 MB/s
[    0.329717] raid6: neonx8   xor()   775 MB/s
[    0.397909] raid6: neonx4   gen()  1071 MB/s
[    0.466057] raid6: neonx4   xor()   769 MB/s
[    0.534284] raid6: neonx2   gen()   992 MB/s
[    0.602419] raid6: neonx2   xor()   706 MB/s
[    0.670650] raid6: neonx1   gen()   886 MB/s
[    0.738809] raid6: neonx1   xor()   605 MB/s
[    0.807004] raid6: int64x8  gen()   745 MB/s
[    0.875219] raid6: int64x8  xor()   392 MB/s
[    0.943343] raid6: int64x4  gen()   830 MB/s
[    1.011525] raid6: int64x4  xor()   424 MB/s
[    1.079728] raid6: int64x2  gen()   707 MB/s
[    1.147887] raid6: int64x2  xor()   372 MB/s
[    1.216100] raid6: int64x1  gen()   526 MB/s
[    1.284243] raid6: int64x1  xor()   274 MB/s
[    1.284256] raid6: using algorithm neonx4 gen() 1071 MB/s
[    1.284267] raid6: .... xor() 769 MB/s, rmw enabled
[    1.284277] raid6: using neon recovery algorithm
[    1.288480] vcc_sd: supplied by vccio_3v3
[    1.289340] vcc_host_vbus: supplied by vcc_sys
[    1.290265] vcc_otg_vbus: supplied by vcc_sys
[    1.291217] iommu: Default domain type: Translated 
[    1.291233] iommu: DMA domain TLB invalidation policy: strict mode 
[    1.295584] vgaarb: loaded
[    1.296530] SCSI subsystem initialized
[    1.296943] libata version 3.00 loaded.
[    1.297423] usbcore: registered new interface driver usbfs
[    1.297519] usbcore: registered new interface driver hub
[    1.297595] usbcore: registered new device driver usb
[    1.298601] pps_core: LinuxPPS API ver. 1 registered
[    1.298614] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    1.298647] PTP clock support registered
[    1.299039] EDAC MC: Ver: 3.0.0
[    1.301466] NetLabel: Initializing
[    1.301491] NetLabel:  domain hash size = 128
[    1.301501] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    1.301663] NetLabel:  unlabeled traffic allowed by default
[    1.302705] clocksource: Switched to clocksource arch_sys_counter
[    1.413010] VFS: Disk quotas dquot_6.6.0
[    1.413158] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    1.414888] AppArmor: AppArmor Filesystem Enabled
[    1.429906] NET: Registered PF_INET protocol family
[    1.430198] IP idents hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    1.432849] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    1.432996] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    1.433433] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    1.433820] TCP: Hash tables configured (established 16384 bind 16384)
[    1.434124] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    1.434235] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    1.434637] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    1.434747] NET: Registered PF_XDP protocol family
[    1.434773] PCI: CLS 0 bytes, default 64
[    1.435604] Trying to unpack rootfs image as initramfs...
[    1.444189] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
[    1.445191] kvm [1]: IPA Size Limit: 40 bits
[    1.447809] kvm [1]: vgic interrupt IRQ9
[    1.448183] kvm [1]: Hyp mode initialized successfully
[    1.464627] Initialise system trusted keyrings
[    1.464737] Key type blacklist registered
[    1.465158] workingset: timestamp_bits=44 max_order=19 bucket_order=0
[    1.477155] zbud: loaded
[    1.480497] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    1.482042] fuse: init (API version 7.34)
[    1.486529] integrity: Platform Keyring initialized
[    1.559798] xor: measuring software checksum speed
[    1.568000]    8regs           :  1217 MB/sec
[    1.575131]    32regs          :  1401 MB/sec
[    1.584384]    arm64_neon      :  1072 MB/sec
[    1.584412] xor: using function: 32regs (1401 MB/sec)
[    1.584436] Key type asymmetric registered
[    1.584447] Asymmetric key parser 'x509' registered
[    1.584680] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[    1.585094] io scheduler mq-deadline registered
[    1.585113] io scheduler kyber registered
[    1.585534] io scheduler bfq registered
[    1.614244] dma-pl330 ff1f0000.dma-controller: Loaded driver for PL330 DMAC-241330
[    1.614289] dma-pl330 ff1f0000.dma-controller:     DBUFF-128x8bytes Num_Chans-8 Num_Peri-20 Num_Events-16
[    1.622198] vdd_arm: supplied by vcc_sys
[    1.623256] vdd_log: supplied by vcc_sys
[    1.625612] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[    1.631636] ff110000.serial: ttyS0 at MMIO 0xff110000 (irq = 21, base_baud = 1500000) is a 16550A
[    1.633596] ff130000.serial: ttyS2 at MMIO 0xff130000 (irq = 22, base_baud = 1500000) is a 16550A
[    1.633896] printk: console [ttyS2] enabled
[    1.635975] Serial: AMBA driver
[    1.638362] rockchip-vop ff370000.vop: Adding to iommu group 4
[    1.666107] loop: module loaded
[    1.675944] tun: Universal TUN/TAP device driver, 1.6
[    1.677843] thunder_xcv, ver 1.0
[    1.677940] thunder_bgx, ver 1.0
[    1.678039] nicpf, ver 1.0
[    1.679616] e1000e: Intel(R) PRO/1000 Network Driver
[    1.679639] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[    1.679778] igb: Intel(R) Gigabit Ethernet Network Driver
[    1.679789] igb: Copyright (c) 2007-2014 Intel Corporation.
[    1.679864] igbvf: Intel(R) Gigabit Virtual Function Network Driver
[    1.679873] igbvf: Copyright (c) 2009 - 2012 Intel Corporation.
[    1.680256] sky2: driver version 1.30
[    1.681448] VFIO - User Level meta-driver version: 0.3
[    1.685536] dwc2 ff580000.usb: supply vusb_d not found, using dummy regulator
[    1.685840] dwc2 ff580000.usb: supply vusb_a not found, using dummy regulator
[    1.699140] dwc2 ff580000.usb: DWC OTG Controller
[    1.699213] dwc2 ff580000.usb: new USB bus registered, assigned bus number 1
[    1.699296] dwc2 ff580000.usb: irq 50, io mem 0xff580000
[    1.699721] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[    1.699745] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.699761] usb usb1: Product: DWC OTG Controller
[    1.699774] usb usb1: Manufacturer: Linux 5.15.35-rockchip64 dwc2_hsotg
[    1.699787] usb usb1: SerialNumber: ff580000.usb
[    1.700897] hub 1-0:1.0: USB hub found
[    1.700980] hub 1-0:1.0: 1 port detected
[    1.703288] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.703360] ehci-pci: EHCI PCI platform driver
[    1.703432] ehci-platform: EHCI generic platform driver
[    1.706435] ehci-platform ff5c0000.usb: EHCI Host Controller
[    1.706501] ehci-platform ff5c0000.usb: new USB bus registered, assigned bus number 2
[    1.707145] ehci-platform ff5c0000.usb: irq 51, io mem 0xff5c0000
[    1.722806] ehci-platform ff5c0000.usb: USB 2.0 started, EHCI 1.00
[    1.723325] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[    1.723351] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.723367] usb usb2: Product: EHCI Host Controller
[    1.723380] usb usb2: Manufacturer: Linux 5.15.35-rockchip64 ehci_hcd
[    1.723392] usb usb2: SerialNumber: ff5c0000.usb
[    1.724498] hub 2-0:1.0: USB hub found
[    1.724613] hub 2-0:1.0: 1 port detected
[    1.725506] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.725574] ohci-pci: OHCI PCI platform driver
[    1.725700] ohci-platform: OHCI generic platform driver
[    1.726536] ohci-platform ff5d0000.usb: Generic Platform OHCI controller
[    1.726583] ohci-platform ff5d0000.usb: new USB bus registered, assigned bus number 3
[    1.726978] ohci-platform ff5d0000.usb: irq 52, io mem 0xff5d0000
[    1.791195] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.15
[    1.791235] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.791251] usb usb3: Product: Generic Platform OHCI controller
[    1.791265] usb usb3: Manufacturer: Linux 5.15.35-rockchip64 ohci_hcd
[    1.791277] usb usb3: SerialNumber: ff5d0000.usb
[    1.792402] hub 3-0:1.0: USB hub found
[    1.792496] hub 3-0:1.0: 1 port detected
[    1.794648] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    1.794797] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 4
[    1.795127] xhci-hcd xhci-hcd.0.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000000002010010
[    1.795248] xhci-hcd xhci-hcd.0.auto: irq 53, io mem 0xff600000
[    1.796082] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.15
[    1.796106] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.796123] usb usb4: Product: xHCI Host Controller
[    1.796138] usb usb4: Manufacturer: Linux 5.15.35-rockchip64 xhci-hcd
[    1.796155] usb usb4: SerialNumber: xhci-hcd.0.auto
[    1.797212] hub 4-0:1.0: USB hub found
[    1.797300] hub 4-0:1.0: 1 port detected
[    1.797999] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    1.798042] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 5
[    1.798077] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed
[    1.798244] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM.
[    1.798508] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.15
[    1.798530] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.798549] usb usb5: Product: xHCI Host Controller
[    1.798563] usb usb5: Manufacturer: Linux 5.15.35-rockchip64 xhci-hcd
[    1.798579] usb usb5: SerialNumber: xhci-hcd.0.auto
[    1.800008] hub 5-0:1.0: USB hub found
[    1.800091] hub 5-0:1.0: 1 port detected
[    1.801095] usbcore: registered new interface driver usb-storage
[    1.804992] mousedev: PS/2 mouse device common for all mice
[    1.807264] i2c_dev: i2c /dev entries driver
[    1.812310] dw_wdt ff1a0000.watchdog: No valid TOPs array specified
[    1.816434] sdhci: Secure Digital Host Controller Interface driver
[    1.816460] sdhci: Copyright(c) Pierre Ossman
[    1.816507] Synopsys Designware Multimedia Card Interface Driver
[    1.818149] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.819597] dwmmc_rockchip ff500000.mmc: IDMAC supports 32-bit address mode.
[    1.819677] dwmmc_rockchip ff500000.mmc: Using internal DMA controller.
[    1.819697] dwmmc_rockchip ff500000.mmc: Version ID is 270a
[    1.819744] dwmmc_rockchip ff520000.mmc: IDMAC supports 32-bit address mode.
[    1.819783] dwmmc_rockchip ff520000.mmc: Using internal DMA controller.
[    1.819802] dwmmc_rockchip ff520000.mmc: Version ID is 270a
[    1.819821] dwmmc_rockchip ff500000.mmc: DW MMC controller at irq 47,32 bit host data width,256 deep fifo
[    1.819901] dwmmc_rockchip ff520000.mmc: DW MMC controller at irq 48,32 bit host data width,256 deep fifo
[    1.820699] dwmmc_rockchip ff500000.mmc: Got CD GPIO
[    1.820786] mmc_host mmc2: card is non-removable.
[    1.822553] dwmmc_rockchip ff5f0000.mmc: IDMAC supports 32-bit address mode.
[    1.822648] dwmmc_rockchip ff5f0000.mmc: Using internal DMA controller.
[    1.822669] dwmmc_rockchip ff5f0000.mmc: Version ID is 270a
[    1.822848] dwmmc_rockchip ff5f0000.mmc: DW MMC controller at irq 58,32 bit host data width,256 deep fifo
[    1.823389] dwmmc_rockchip ff5f0000.mmc: allocated mmc-pwrseq
[    1.823415] mmc_host mmc4: card is non-removable.
[    1.823844] ledtrig-cpu: registered to indicate activity on CPUs
[    1.825733] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    1.826164] hid: raw HID events driver (C) Jiri Kosina
[    1.826430] usbcore: registered new interface driver usbhid
[    1.826444] usbhid: USB HID core driver
[    1.833755] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[    1.833761] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[    1.834925] mmc_host mmc4: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[    1.835502] drop_monitor: Initializing network drop monitor service
[    1.836816] NET: Registered PF_INET6 protocol family
[    1.914861] mmc_host mmc4: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[    1.916803] random: fast init done
[    1.919309] mmc4: new high speed SDIO card at address 0001
[    2.104300] mmc_host mmc2: Bus speed (slot 0) = 150000000Hz (slot req 150000000Hz, actual 150000000HZ div = 0)
[    2.507260] dwmmc_rockchip ff520000.mmc: Successfully tuned phase to 221
[    2.507423] mmc2: new HS200 MMC card at address 0001
[    2.509490] mmcblk2: mmc2:0001 BJNB4R 29.1 GiB 
[    2.514550]  mmcblk2: p1
[    2.516350] mmcblk2boot0: mmc2:0001 BJNB4R 4.00 MiB 
[    2.521722] mmcblk2boot1: mmc2:0001 BJNB4R 4.00 MiB 
[    2.526095] mmcblk2rpmb: mmc2:0001 BJNB4R 4.00 MiB, chardev (241:0)
[    3.075360] Freeing initrd memory: 15988K
[    3.134029] Segment Routing with IPv6
[    3.134131] In-situ OAM (IOAM) with IPv6
[    3.134286] NET: Registered PF_PACKET protocol family
[    3.134542] 8021q: 802.1Q VLAN Support v1.8
[    3.134644] Key type dns_resolver registered
[    3.136682] registered taskstats version 1
[    3.136719] Loading compiled-in X.509 certificates
[    3.142857] Loaded X.509 cert 'Build time autogenerated kernel key: e3efba69e3d901fe5208cf9edcc32162970960d8'
[    3.149111] zswap: loaded using pool zstd/z3fold
[    3.150744] Key type ._fscrypt registered
[    3.150774] Key type .fscrypt registered
[    3.150782] Key type fscrypt-provisioning registered
[    3.155122] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity=yes
[    3.182833] Key type encrypted registered
[    3.182893] AppArmor: AppArmor sha1 policy hashing enabled
[    3.243598] rockchip-vop ff370000.vop: using dedicated hwcursor plane
[    3.245993] rockchip-drm display-subsystem: bound ff370000.vop (ops vop_component_ops)
[    3.246591] dwhdmi-rockchip ff3c0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (inno_dw_hdmi_phy2)
[    3.247796] dwhdmi-rockchip ff3c0000.hdmi: registered DesignWare HDMI I2C bus driver
[    3.248869] rockchip-drm display-subsystem: bound ff3c0000.hdmi (ops dw_hdmi_rockchip_ops)
[    3.249371] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes
[    3.250356] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0
[    3.252022] of_cfs_init
[    3.252138] of_cfs_init: OK
[    3.256453] Freeing unused kernel memory: 4288K
[    3.278790] Run /init as init process
[    3.278810]   with arguments:
[    3.278823]     /init
[    3.278833]   with environment:
[    3.278843]     HOME=/
[    3.278851]     TERM=linux
[    3.278861]     ubootpart=534ffe7a-01
[    3.278871]     cgroup_enable=memory
[    3.278882]     cgroup_memory=1
[    4.185611] input: adc-keys as /devices/platform/adc-keys/input/input0
[    4.215138] gpio-syscon ff100000.syscon:gpio: can't read the data register offset!
[    4.259060] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes
[    4.342166] rk_gmac-dwmac ff550000.ethernet: IRQ eth_wake_irq not found
[    4.342203] rk_gmac-dwmac ff550000.ethernet: IRQ eth_lpi not found
[    4.342483] rk_gmac-dwmac ff550000.ethernet: PTP uses main clock
[    4.343417] rk_gmac-dwmac ff550000.ethernet: clock input or output? (output).
[    4.343462] rk_gmac-dwmac ff550000.ethernet: TX delay(0x30).
[    4.343480] rk_gmac-dwmac ff550000.ethernet: RX delay(0x10).
[    4.343531] rk_gmac-dwmac ff550000.ethernet: integrated PHY? (yes).
[    4.343718] rk_gmac-dwmac ff550000.ethernet: cannot get clock clk_mac_refout
[    4.343750] rk_gmac-dwmac ff550000.ethernet: cannot get clock clk_mac_speed
[    4.348858] rk_gmac-dwmac ff550000.ethernet: init for RMII
[    4.408152] rk_gmac-dwmac ff550000.ethernet: User ID: 0x10, Synopsys ID: 0x35
[    4.408209] rk_gmac-dwmac ff550000.ethernet:     DWMAC1000
[    4.408224] rk_gmac-dwmac ff550000.ethernet: DMA HW capability register supported
[    4.408237] rk_gmac-dwmac ff550000.ethernet: RX Checksum Offload Engine supported
[    4.408248] rk_gmac-dwmac ff550000.ethernet: COE Type 2
[    4.408260] rk_gmac-dwmac ff550000.ethernet: TX Checksum insertion supported
[    4.408271] rk_gmac-dwmac ff550000.ethernet: Wake-Up On Lan supported
[    4.408520] rk_gmac-dwmac ff550000.ethernet: Normal descriptors
[    4.408545] rk_gmac-dwmac ff550000.ethernet: Ring mode enabled
[    4.408556] rk_gmac-dwmac ff550000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    5.384309] EXT4-fs (mmcblk2p1): mounted filesystem with writeback data mode. Opts: (null). Quota mode: none.
[    5.945917] systemd[1]: System time before build time, advancing clock.
[    5.977831] systemd[1]: Inserted module 'autofs4'
[    6.054830] systemd[1]: systemd 249.11-0ubuntu3.1 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT +GNUTLS -OPENSSL +ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP -LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[    6.056424] systemd[1]: Detected architecture arm64.
[    6.063580] systemd[1]: Hostname set to <armbian>.
[    6.218273] dw-apb-uart ff130000.serial: forbid DMA for kernel console
[    7.341557] systemd[1]: Queued start job for default target Graphical Interface.
[    7.344753] random: systemd: uninitialized urandom read (16 bytes read)
[    7.371718] systemd[1]: Created slice Slice /system/modprobe.
[    7.372759] random: systemd: uninitialized urandom read (16 bytes read)
[    7.378098] systemd[1]: Created slice Slice /system/serial-getty.
[    7.378934] random: systemd: uninitialized urandom read (16 bytes read)
[    7.383660] systemd[1]: Created slice User and Session Slice.
[    7.385266] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[    7.388403] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    7.389941] systemd[1]: Reached target Remote File Systems.
[    7.390665] systemd[1]: Reached target Slice Units.
[    7.391541] systemd[1]: Reached target Swaps.
[    7.392220] systemd[1]: Reached target System Time Set.
[    7.393417] systemd[1]: Reached target Local Verity Protected Volumes.
[    7.398665] systemd[1]: Listening on Syslog Socket.
[    7.400737] systemd[1]: Listening on fsck to fsckd communication Socket.
[    7.402005] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    7.404878] systemd[1]: Listening on Journal Audit Socket.
[    7.406868] systemd[1]: Listening on Journal Socket (/dev/log).
[    7.409108] systemd[1]: Listening on Journal Socket.
[    7.412508] systemd[1]: Listening on udev Control Socket.
[    7.414509] systemd[1]: Listening on udev Kernel Socket.
[    7.425166] systemd[1]: Mounting Huge Pages File System...
[    7.436890] systemd[1]: Mounting POSIX Message Queue File System...
[    7.449655] systemd[1]: Mounting Kernel Debug File System...
[    7.461814] systemd[1]: Mounting Kernel Trace File System...
[    7.477572] systemd[1]: Starting Restore / save the current clock...
[    7.493163] systemd[1]: Starting Set the console keyboard layout...
[    7.508107] systemd[1]: Starting Create List of Static Device Nodes...
[    7.522427] systemd[1]: Starting Load Kernel Module configfs...
[    7.536782] systemd[1]: Starting Load Kernel Module drm...
[    7.550316] systemd[1]: Starting Load Kernel Module fuse...
[    7.566352] systemd[1]: Started Nameserver information manager.
[    7.569350] systemd[1]: Reached target Preparation for Network.
[    7.572879] systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
[    7.590209] systemd[1]: Starting Load Kernel Modules...
[    7.604956] systemd[1]: Starting Remount Root and Kernel File Systems...
[    7.619979] systemd[1]: Starting Coldplug All udev Devices...
[    7.645140] systemd[1]: Mounted Huge Pages File System.
[    7.647281] systemd[1]: Mounted POSIX Message Queue File System.
[    7.649762] systemd[1]: Mounted Kernel Debug File System.
[    7.652073] systemd[1]: Mounted Kernel Trace File System.
[    7.658123] systemd[1]: Finished Restore / save the current clock.
[    7.665333] systemd[1]: Finished Create List of Static Device Nodes.
[    7.669809] EXT4-fs (mmcblk2p1): re-mounted. Opts: commit=600,errors=remount-ro. Quota mode: none.
[    7.671459] systemd[1]: modprobe@configfs.service: Deactivated successfully.
[    7.675247] systemd[1]: Finished Load Kernel Module configfs.
[    7.706122] systemd[1]: modprobe@drm.service: Deactivated successfully.
[    7.709447] systemd[1]: Finished Load Kernel Module drm.
[    7.713335] systemd[1]: modprobe@fuse.service: Deactivated successfully.
[    7.716536] systemd[1]: Finished Load Kernel Module fuse.
[    7.727029] systemd[1]: Finished Load Kernel Modules.
[    7.732567] systemd[1]: Finished Remount Root and Kernel File Systems.
[    7.748683] systemd[1]: Mounting FUSE Control File System...
[    7.760724] systemd[1]: Mounting Kernel Configuration File System...
[    7.761943] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
[    7.775553] systemd[1]: Starting Load/Save Random Seed...
[    7.789110] systemd[1]: Starting Apply Kernel Variables...
[    7.803702] systemd[1]: Starting Create System Users...
[    7.829910] systemd[1]: Mounted FUSE Control File System.
[    7.832138] systemd[1]: Mounted Kernel Configuration File System.
[    7.894842] systemd[1]: Finished Create System Users.
[    7.937672] systemd[1]: Starting Create Static Device Nodes in /dev...
[    7.951704] systemd[1]: Finished Apply Kernel Variables.
[    8.035931] systemd[1]: Finished Create Static Device Nodes in /dev.
[    8.101561] systemd[1]: Starting Rule-based Manager for Device Events and Files...
[    8.109018] systemd[1]: Finished Set the console keyboard layout.
[    8.118879] systemd[1]: Reached target Preparation for Local File Systems.
[    8.134086] systemd[1]: Mounting /tmp...
[    8.157565] systemd[1]: Mounted /tmp.
[    8.159467] systemd[1]: Reached target Local File Systems.
[    8.172448] systemd[1]: Starting Load AppArmor profiles...
[    8.186762] systemd[1]: Starting Armbian ZRAM config...
[    8.201875] systemd[1]: Starting Set console font and keymap...
[    8.232271] systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
[    8.256340] systemd[1]: Starting Set Up Additional Binary Formats...
[    8.280469] systemd[1]: Finished Tell Plymouth To Write Out Runtime Data.
[    8.309575] systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 389 (systemd-binfmt)
[    8.342665] systemd[1]: Mounting Arbitrary Executable File Formats File System...
[    8.364528] systemd[1]: Finished Set console font and keymap.
[    8.437368] systemd[1]: Mounted Arbitrary Executable File Formats File System.
[    8.455519] systemd[1]: Finished Set Up Additional Binary Formats.
[    8.520645] audit: type=1400 audit(1652264221.988:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=401 comm="apparmor_parser"
[    8.540147] audit: type=1400 audit(1652264222.008:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=402 comm="apparmor_parser"
[    8.540355] audit: type=1400 audit(1652264222.008:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=402 comm="apparmor_parser"
[    8.607790] audit: type=1400 audit(1652264222.076:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=403 comm="apparmor_parser"
[    8.607967] audit: type=1400 audit(1652264222.076:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-helper" pid=403 comm="apparmor_parser"
[    8.608082] audit: type=1400 audit(1652264222.076:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=403 comm="apparmor_parser"
[    8.608217] audit: type=1400 audit(1652264222.076:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/{,usr/}sbin/dhclient" pid=403 comm="apparmor_parser"
[    8.684351] audit: type=1400 audit(1652264222.152:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session" pid=400 comm="apparmor_parser"
[    8.684412] audit: type=1400 audit(1652264222.152:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session//chromium" pid=400 comm="apparmor_parser"
[    8.692749] audit: type=1400 audit(1652264222.160:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=407 comm="apparmor_parser"
[    8.756035] systemd[1]: Started Rule-based Manager for Device Events and Files.
[    8.977910] zram: Added device: zram0
[    8.979470] zram: Added device: zram1
[    8.980830] zram: Added device: zram2
[    8.997316] systemd[1]: Finished Coldplug All udev Devices.
[    9.040261] systemd[1]: Starting Helper to synchronize boot up for ifupdown...
[    9.041795] systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped.
[    9.042435] systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch when bootsplash is active being skipped.
[    9.042944] systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped.
[    9.043606] systemd[1]: Reached target Local Encrypted Volumes.
[    9.076810] systemd[1]: Finished Helper to synchronize boot up for ifupdown.
[    9.172790] zram0: detected capacity change from 0 to 2028448
[    9.625256] systemd[1]: Finished Load AppArmor profiles.
[    9.675554] systemd[1]: Starting Raise network interfaces...
[    9.692460] systemd[1]: Starting Load AppArmor profiles managed internally by snapd...
[    9.795501] systemd[1]: Finished Load AppArmor profiles managed internally by snapd.
[   10.030159] systemd[1]: Found device /dev/ttyS2.
[   10.274325] mc: Linux media interface: v0.10
[   10.280197] lima ff300000.gpu: gp - mali450 version major 0 minor 0
[   10.280281] lima ff300000.gpu: pp0 - mali450 version major 0 minor 0
[   10.280344] lima ff300000.gpu: pp1 - mali450 version major 0 minor 0
[   10.280394] lima ff300000.gpu: l2 cache 8K, 4-way, 64byte cache line, 128bit external bus
[   10.280408] lima ff300000.gpu: l2 cache 64K, 4-way, 64byte cache line, 128bit external bus
[   10.286456] rk3328-codec ff410000.codec: spk_depop_time use default value.
[   10.300152] lima ff300000.gpu: bus rate = 491520000
[   10.300191] lima ff300000.gpu: mod rate = 491520000
[   10.409858] [drm] Initialized lima 1.1.0 20191231 for ff300000.gpu on minor 1
[   10.415736] videodev: Linux video capture interface: v2.00
[   10.626758] systemd[1]: Finished Raise network interfaces.
[   10.673912] Registered IR keymap rc-empty
[   10.674097] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0
[   10.674475] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter
[   10.674864] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc0/input1
[   10.742353] rockchip-rga ff390000.rga: HW Version: 0x04.00
[   10.746953] rockchip-rga ff390000.rga: Registered rockchip-rga as /dev/video0
[   10.763584] rockchip-iep ff3a0000.iep: Adding to iommu group 5
[   10.789078] rockchip_vdec: module is from the staging directory, the quality is unknown, you have been warned.
[   10.790919] rockchip-iep ff3a0000.iep: Device rockchip-iep registered as /dev/video1
[   10.813674] hantro_vpu: module is from the staging directory, the quality is unknown, you have been warned.
[   10.829006] hantro-vpu ff350000.video-codec: Adding to iommu group 2
[   10.830108] hantro-vpu ff350000.video-codec: registered rockchip,rk3328-vpu-dec as /dev/video2
[   10.862817] rkvdec ff360000.video-codec: Adding to iommu group 3
[   10.870435] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   10.874617] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   11.050005] brcmfmac: F1 signature read @0x18000000=0x16044330
[   11.059041] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4
[   11.063418] brcmfmac mmc4:0001:1: Direct firmware load for brcm/brcmfmac4330-sdio.rockchip,rk3318-box.bin failed with error -2
[   11.065605] usbcore: registered new interface driver brcmfmac
[   11.229592] random: crng init done
[   11.229626] random: 7 urandom warning(s) missed due to ratelimiting
[   11.246220] systemd[1]: Finished Load/Save Random Seed.
[   11.251210] systemd[1]: Condition check resulted in First Boot Complete being skipped.
[   11.251474] systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
[   11.251790] systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
[   11.362842] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4330-sdio for chip BCM4330/4
[   11.363026] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[   11.363220] Adding 1014220k swap on /dev/zram0.  Priority:5 extents:1 across:1014220k SSFS
[   11.363800] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4330/4 wl0: Oct 25 2011 19:34:12 version 5.90.125.104
[   11.402880] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 184
[   11.402918] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 188
[   11.402925] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 192
[   11.402931] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 196
[   11.402938] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 200
[   11.402945] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 204
[   11.402952] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 208
[   11.402958] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 212
[   11.402964] ieee80211 phy0: brcmf_construct_chaninfo: Ignoring unexpected firmware channel 216
[   11.467823] systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[   11.533112] systemd[1]: Starting Load/Save RF Kill Switch Status...
[   11.612314] zram1: detected capacity change from 0 to 102400
[   11.628438] systemd[1]: Started Load/Save RF Kill Switch Status.
[   11.698016] systemd[1]: Finished Armbian ZRAM config.
[   11.753062] systemd[1]: Starting Armbian memory supported logging...
[   11.808462] systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped.
[   11.808760] systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch when bootsplash is active being skipped.
[   11.808902] systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped.
[   11.809087] systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
[   11.809322] systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
[   11.809512] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
[   11.836213] EXT4-fs (zram1): mounted filesystem without journal. Opts: discard. Quota mode: none.
[   12.738767] rc rc0: two consecutive events of type space
[   15.535918] systemd[1]: Finished Armbian memory supported logging.
[   15.571573] systemd[1]: Starting Journal Service...
[   15.831243] systemd[1]: Started Journal Service.
[   15.897123] systemd-journald[690]: Received client request to flush runtime journal.
[   32.848153] PPP generic driver version 2.4.2
[   32.860377] NET: Registered PF_PPPOX protocol family
[   32.920063] l2tp_core: L2TP core driver, V2.0
[   32.931787] l2tp_netlink: L2TP netlink interface
[   32.940407] l2tp_ppp: PPPoL2TP kernel driver, V2.0
[   33.166157] kauditd_printk_skb: 17 callbacks suppressed
[   33.166189] audit: type=1400 audit(1652264246.632:29): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=1779 comm="cupsd" capability=12  capname="net_admin"
[   33.235896] Initializing XFRM netlink socket
[   33.972870] loop0: detected capacity change from 0 to 8
[   34.426212] rk_gmac-dwmac ff550000.ethernet eth0: PHY [stmmac-1:00] driver [Rockchip integrated EPHY] (irq=POLL)
[   34.429428] rk_gmac-dwmac ff550000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0
[   34.451379] rk_gmac-dwmac ff550000.ethernet eth0: No Safety Features support found
[   34.451437] rk_gmac-dwmac ff550000.ethernet eth0: PTP not supported by HW
[   34.452951] rk_gmac-dwmac ff550000.ethernet eth0: configuring for phy/rmii link mode
[   35.188688] aufs 5.15.5-20220404
[   36.515200] rk_gmac-dwmac ff550000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[   36.642850] ieee80211 phy0: brcmf_p2p_create_p2pdev: timeout occurred
[   36.642891] ieee80211 phy0: brcmf_cfg80211_add_iface: add iface p2p-dev-wlan0 type 10 failed: err=-5
[   36.643055] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   37.559117] audit: type=1400 audit(1652264251.027:30): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=2057 comm="apparmor_parser"
[   38.334074] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[   38.342972] Bridge firewalling registered
[   49.263161] br-0bd3b294c334: port 1(veth6856f94) entered blocking state
[   49.263304] br-0bd3b294c334: port 1(veth6856f94) entered disabled state
[   49.265807] device veth6856f94 entered promiscuous mode
[   49.278991] br-8434d8787933: port 1(vethc85a00a) entered blocking state
[   49.279083] br-8434d8787933: port 1(vethc85a00a) entered disabled state
[   49.281939] device vethc85a00a entered promiscuous mode
[   49.284601] br-1b43b55041dd: port 1(vethbb04420) entered blocking state
[   49.294909] br-1b43b55041dd: port 1(vethbb04420) entered disabled state
[   49.296827] device vethbb04420 entered promiscuous mode
[   49.302587] br-402a81a6d00f: port 1(vethfad7534) entered blocking state
[   49.302680] br-402a81a6d00f: port 1(vethfad7534) entered disabled state
[   49.304148] device vethfad7534 entered promiscuous mode
[   49.337851] br-e007e0a39ec1: port 1(veth42f55ce) entered blocking state
[   49.337933] br-e007e0a39ec1: port 1(veth42f55ce) entered disabled state
[   49.338421] device veth42f55ce entered promiscuous mode
[   49.343358] br-1b43b55041dd: port 1(vethbb04420) entered blocking state
[   49.343412] br-1b43b55041dd: port 1(vethbb04420) entered forwarding state
[   49.355182] br-1b43b55041dd: port 1(vethbb04420) entered disabled state
[   49.370226] br-402a81a6d00f: port 1(vethfad7534) entered blocking state
[   49.370282] br-402a81a6d00f: port 1(vethfad7534) entered forwarding state
[   49.382073] br-402a81a6d00f: port 1(vethfad7534) entered disabled state
[   49.391607] br-8434d8787933: port 1(vethc85a00a) entered blocking state
[   49.391662] br-8434d8787933: port 1(vethc85a00a) entered forwarding state
[   49.393145] br-e007e0a39ec1: port 1(veth42f55ce) entered blocking state
[   49.393197] br-e007e0a39ec1: port 1(veth42f55ce) entered forwarding state
[   49.436518] br-8434d8787933: port 1(vethc85a00a) entered disabled state
[   49.437263] br-e007e0a39ec1: port 1(veth42f55ce) entered disabled state
[   50.252198] hdmi-audio-codec hdmi-audio-codec.3.auto: Only one simultaneous stream supported!
[   50.252240] hdmi-audio-codec hdmi-audio-codec.3.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22
[   50.252268]  ff000000.i2s-i2s-hifi: soc_pcm_open() failed (-22)
[   57.241997] eth0: renamed from veth33194ce
[   57.309083] IPv6: ADDRCONF(NETDEV_CHANGE): vethbb04420: link becomes ready
[   57.309759] br-1b43b55041dd: port 1(vethbb04420) entered blocking state
[   57.309813] br-1b43b55041dd: port 1(vethbb04420) entered forwarding state
[   57.310369] IPv6: ADDRCONF(NETDEV_CHANGE): br-1b43b55041dd: link becomes ready
[   57.750046] eth0: renamed from veth5871f8c
[   57.778974] IPv6: ADDRCONF(NETDEV_CHANGE): veth42f55ce: link becomes ready
[   57.779611] br-e007e0a39ec1: port 1(veth42f55ce) entered blocking state
[   57.779689] br-e007e0a39ec1: port 1(veth42f55ce) entered forwarding state
[   57.780150] IPv6: ADDRCONF(NETDEV_CHANGE): br-e007e0a39ec1: link becomes ready
[   59.088501] eth0: renamed from vethb275f98
[   59.116724] IPv6: ADDRCONF(NETDEV_CHANGE): vethc85a00a: link becomes ready
[   59.117231] br-8434d8787933: port 1(vethc85a00a) entered blocking state
[   59.117288] br-8434d8787933: port 1(vethc85a00a) entered forwarding state
[   59.117773] IPv6: ADDRCONF(NETDEV_CHANGE): br-8434d8787933: link becomes ready
[   59.367406] eth0: renamed from veth92157ad
[   59.392327] IPv6: ADDRCONF(NETDEV_CHANGE): veth6856f94: link becomes ready
[   59.392784] br-0bd3b294c334: port 1(veth6856f94) entered blocking state
[   59.392833] br-0bd3b294c334: port 1(veth6856f94) entered forwarding state
[   59.393205] IPv6: ADDRCONF(NETDEV_CHANGE): br-0bd3b294c334: link becomes ready
[   59.533757] eth0: renamed from veth8f60455
[   59.555035] IPv6: ADDRCONF(NETDEV_CHANGE): vethfad7534: link becomes ready
[   59.555494] br-402a81a6d00f: port 1(vethfad7534) entered blocking state
[   59.555550] br-402a81a6d00f: port 1(vethfad7534) entered forwarding state
[   59.555947] IPv6: ADDRCONF(NETDEV_CHANGE): br-402a81a6d00f: link becomes ready

 

I tried extracting the device tree file, but was able to get 11 different files; if they would be of help, I can also provide them here. Unfortunately, I do not have a UART module, but am willing to search for one locally.

 

Thank you in advance and have a nice day!

Link to comment
Share on other sites

@cmuki Well, the ways of the chinese cheap tv boxes are infinite... we have seen fake Androids that show more hardware or different hardware; in a case we have also seen a fake amlogic s905x chip which in reality was a rockchip rk322x chip: they altered both the serigraphy printed on the chip itself and the Android software to make it appear as an amlogic. The guy was not able to let armbian run until he finally tried rk322x image and voilà... it worked!

 

So it could be quite possible that your box is advertised with a fake specs (and indeed the eMMC is detected as a 32Gb part and not 64 as advertised), and even the chips are somehow fake, disconnected or broken.

There could obviously be a bug in the code, that even won't surprise me. To be really sure of the amount of RAM you have available you need the serial UART: at the very beginning, the boot process will show the amount of memory banks you have and their size. That's the source of truth, because it is a binary provided by rockchip itself.

 

If you still have Android installed (or did a backup), you can read that info during boot and that will provide a reliable info.

Link to comment
Share on other sites

@jock, thank you for you swift reply! I'll try to get my hands on a UART module in the next couple of weeks and report back.

 

Hopefully the information will be helpful for other members of the forum as well!

Link to comment
Share on other sites

20 hours ago, MR01 said:

i only have /etc/X11/xorg.conf.d/01-armbian-defaults.conf
I dont think i removed or deleted it by accident because i never installed DE in this installation of minimal.

To update the Lima driver question ON or OFF
dmesg | grep lima

[    7.913523] lima ff300000.gpu: gp - mali450 version major 0 minor 0
[    7.913612] lima ff300000.gpu: pp0 - mali450 version major 0 minor 0
[    7.913675] lima ff300000.gpu: pp1 - mali450 version major 0 minor 0
[    7.913731] lima ff300000.gpu: l2 cache 8K, 4-way, 64byte cache line, 128bit                                                                                                              external bus
[    7.913746] lima ff300000.gpu: l2 cache 64K, 4-way, 64byte cache line, 128bit                                                                                                              external bus
[    7.915008] lima ff300000.gpu: bus rate = 491520000
[    7.915046] lima ff300000.gpu: mod rate = 491520000
[    7.917641] [drm] Initialized lima 1.1.0 20191231 for ff300000.gpu on minor 1

 

Link to comment
Share on other sites

1 hour ago, MR01 said:

To update the Lima driver question ON or OFF
dmesg | grep lima

[    7.913523] lima ff300000.gpu: gp - mali450 version major 0 minor 0
[    7.913612] lima ff300000.gpu: pp0 - mali450 version major 0 minor 0
[    7.913675] lima ff300000.gpu: pp1 - mali450 version major 0 minor 0
[    7.913731] lima ff300000.gpu: l2 cache 8K, 4-way, 64byte cache line, 128bit                                                                                                              external bus
[    7.913746] lima ff300000.gpu: l2 cache 64K, 4-way, 64byte cache line, 128bit                                                                                                              external bus
[    7.915008] lima ff300000.gpu: bus rate = 491520000
[    7.915046] lima ff300000.gpu: mod rate = 491520000
[    7.917641] [drm] Initialized lima 1.1.0 20191231 for ff300000.gpu on minor 1

 

 

Lima driver for 3D is active and working pretty fine since a long time, the only reason it was disabled for X.org was the slower performances in desktop usage due to missing "optimizations" in modesetting X.org driver.

This causes buffers being moved back and forth and thus degraded performance but, as you confirm, 3D is enabled for X.org too.

 

For any other usage unrelated to X.org (including Wayland/Weston, Kodi, OpenGL games, ...) Lima driver and 3D acceleration have always been available.

 

Link to comment
Share on other sites

Posted (edited)

Dear @jock,

 

Today I managed to buy a UART converter - sadly, these are the first rows of the boot log (copy-pasted the output from Putty window to a txt file):

DDR version 1.16 20190713
ID:0xFFF
In
DDR3
333MHz
Bus Width=32 Col=11 Bank=8 Row=15 CS=1 Die Bus-Width=16 Size=2048MB
ddrconfig:2
OUT

 

It seems that the RAM is, as Armbian was able to detect, 2 GB. Only this ddrconfig: 2 value is peculiar.

 

I've attached the whole output, but don't know if there is something else relevant, which is missing from it

 

Thank you once again for your support! If I can provide any further information, I'm available.

 

Best regards!

 

EDIT: Using the DDR Version I was able to find this comment from chess12 and there are three differences between our outputs :

1. Row=16 instead of 15

2. Size=4096

3. ddrconfig:3

 

 

boot log.txt

Edited by cmuki
new information
Link to comment
Share on other sites

@cmuki

Assuming the boot you provided is from the original image, I think there is no extra questions to ask: if the ddrbin says that you have 2048 megabytes, that is so.

The ddrbin, which is the first piece of code that is executed at all and initializes the board DDR memory, is the most reliable source from this point of view.

 

Going on with the bootstrap phase, u-boot says the same:

U-Boot 2017.09-gaa00306-201224-dirty #foxluo (Jan 19 2021 - 14:31:53 +0800)

PreSerial: 2, raw, 0xff130000
DRAM:  2 GiB

 

And obviously even the linux android kernel also detects 2 gigabytes of total RAM:

[    0.000000] Memory: 1955884K/2064384K available (14910K kernel code, 2056K rwdata, 8884K rodata, 3968K init, 2806K bss, 75732K reserved, 32768K cma-reserved)

 

That's it, fake hardware specs; the manufacturer altered the Android image somehow to show fake specs and maybe something is wrong with the DDR chips too (are they have been reprinted? are they just fake chips or not really connected to the board? who knows...)

Link to comment
Share on other sites

I had a problem with this wireless chip. Is this familiar to anyone? In one of the system messages I saw this as BCM 4334B1 / 6334. It can scan networks with the minimal image but cannot connect. Is there an overlay?

 

Spoiler

bcm4334B1.thumb.jpg.4008e43b4510562a072766f2f39ae6d4.jpg

 

Link to comment
Share on other sites

I can't help answer this question directly as I haven't encountered this module before, nor the problem of one being discovered but not connecting.  That said, there are many different part numbers for what is essentially the same module.  As a general rule of thumb, look at the last two digits and compare to the Broadcom part numbers.  In this case, it would likely be a brcm4334 as discovered.  If it ends in 30, it would likely be a brcm4330.  Of course, that doesn't explain why it doesn't connect.  I'll defer to @jock or others that have more experience with these things...

Link to comment
Share on other sites

 Share

×
×
  • Create New...