GeraltOfTrivia

I'd gladly do that, but unfortunately my git skills leave much to be desired. I could try to learn though However, I'm not sure the armbian team would appreciate the extra influx of people complaining about instability issues because of the higher clocks+bad PSUs.

The reason that the OPi1+ doesn't clock higher than 1,48 GHz with the recent kernel versions isnt (just) the cpu opp table itself, the entries for 1,8 GHz (and even 1,6 GHz in 5.4.20) exist. The problem is that in the DTB, the max microvolt value for dcdca or vdd-cpu is lower than what's needed for the cpu to switch to 1,6 GHz or higher. dcdca { regulator-always-on; regulator-min-microvolt = <0xc5c10>; regulator-max-microvolt = <0x107ac0>; (1080 mV) regulator-name = "vdd-cpu"; phandle = <0x6>; } opp@1640000000 { opp-hz = <0x0 0x61c06a00>; opp-microvolt = <0x11b340 0x11b340 0x11b340>; (1160 mV) clock-latency-ns = <0x3b9b0>; }; opp@1800000000 { clock-latency-ns = <0x3b9b0>; opp-hz = <0x0 0x6b49d200>; opp-microvolt-speed0 = <0x11b340>; opp-microvolt-speed1 = <0x10c8e0>; (1100 mV) opp-microvolt-speed2 = <0x10c8e0>; }; I tried this myself with my OPi1+ with kernel 5.5.0 by raising regulator-max-microvolt to 0x11b340 (1160 mV) and it successfully clocked to 1,8 GHz. YMMV. Sorry if this has already been mentioned elsewhere.

I've seen in your signature that you have OPi1+s, I've even tried some of your pre-built images, but mine refuses to boot unless I use a pre 5.1.5 dtb or modify the cpu opp table. Weird, but as long as there's a workaround, I'm not complaining.

I know this doesn't exactly answer your question, but the only way (at least for me) to get a working image for OPiOnePlus is to either copy a dtb file from an older image (kernel 5.1.5 and older works for me) to the new erimages or edit the dtb file of newer images and copy over the cpu opp table values from an older image (5.1.5 and older) to the new image. Otherwise I'm just stuck with endless bootloops. Makes no difference if I built the image myself or downloaded a pre-built one.

Thanks for the tip, I'll keep that in mind, it will definitely come in handy sooner or later.

Around 30mins iirc on an i7-4710MQ (4C/8T) 16GB RAM, SSD for a CLI image. Sometimes it takes an insane amount of time to download the toolchains and rootfs when you run the script for the first time, keep that in mind.

Kernel 4.4 is definitely more stable than 5.x kernels. However I have managed to achieve almost gigabit file transfer speeds with samba with 5.x kernels. With 4.4.x kernels, I can't get past 70 MB/sec with the exact same settings no matter what I do. I've noticed everything from occasional crashes to the system crashing every 5 minutes under mild load with 5.x kernels, which didn't happen with 4.4.x (same PSU). So your mileage may vary. Take it with a grain of salt, these are just my experiences so far. Oh and if you try the Armbian 5.x dev images and you run your M4 from your sd card, yeah those images are bugged (at least for me). For some reason mmc1 gets a frequency of 50 MHz instead of 150 MHz and the transfer rate is crippled at 22 MB/sec.

Actually for anyone who still wonders why they can't post, you need at least 10 posts to be able to participate in the Allwinner H6 forum. I somehow managed to post something there with 0 posts, and now that I need to post something again, I can't. Bummer.

Sorry to necro an old thread, but I didn't find a more suitable one and I didn't want to start a new one. Anyway, to the point. When I install or build any of the Armbian dev/nightly images with kernel 5.x, the sdcard is practically unusable after the installation. hdparm shows read/write speeds of max. 5 MB/sec. The reason is that unless the bus-width for mmc@4020000 is explicitly set to 4 bits in sun50i-h6-orangepi-one-plus.dtb mmc@4020000 { compatible = "allwinner,sun50i-h6-mmc", "allwinner,sun50i-a64-mmc"; reg = <0x4020000 0x1000>; clocks = <0x2 0x43 0x2 0x40>; clock-names = "ahb", "mmc"; resets = <0x2 0x12>; reset-names = "ahb"; interrupts = <0x0 0x23 0x4>; status = "okay"; #address-cells = <0x1>; #size-cells = <0x0>; pinctrl-names = "default"; pinctrl-0 = <0xb>; vmmc-supply = <0xc>; bus-width = <0x4>; cd-gpios = <0xd 0x5 0x6 0x1>; phandle = <0x2f>; }; the bus width defaults to 1 bit as seen in root@orangepi:~# cat /sys/kernel/debug/mmc0/ios clock: 50000000 Hz actual clock: 50000000 Hz vdd: 21 (3.3 ~ 3.4 V) bus mode: 2 (push-pull) chip select: 0 (don't care) power mode: 2 (on) bus width: 0 (1 bits) timing spec: 2 (sd high-speed) signal voltage: 0 (3.30 V) driver type: 0 (driver type B) which practically cripples the SD card interface. By default there is no bus-width entry in sun50i-h6-orangepi-one-plus.dtb for mmc@4020000. I don't know if this is Armbian specific or not or if this has been mentioned again, I just thought I'd share my findings in case this helps someone.