Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Necroposting, I know, but just in case someone else googles up this thread as I did. The MPI3508 3.5" screen is cheap and sold a ton apparently. So the problem is, the display is actually 480x320 but identifies itself as 1024x768 (!), which is not correct as size and not even as aspect ratio (4:3 vs. actual 3:2) Trying to force 480x320 in armbianEnv.txt does not work, the display shows nothing; probably there are no proper timings in the kernel/DTB/whatever for such low an HDMI resolution. So the trick is using 720x480, which is 1.5x the actual resolution. The aspect ratio is correct, the timings are there, and after all it's even quite readable. So in /boot/armbianEnv.txt add: extraargs=video=HDMI-A-1:720x480@60 disp_mode=720x480 and then recompile boot.scr: mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr Display should run fine. fbset reports: mode "720x480" geometry 720 480 720 480 32 timings 0 0 0 0 0 0 0 accel true rgba 8/16,8/8,8/0,0/0 endmode which may be added to /etc/fb.modes Hope this helps, despite not being optimal.
  2. Nice!! Is it stock Armbian, or did you have to patch something/rebuild kernel/rebuild uboot / etc?
  3. I would test it gladly. Is it OK to install it on an Armbian Unstable? It's what I have now. If you advice against it, no problem, will reinstall.
  4. You may try with the latest Unstable kernel (based upon 5.11.x), but I don't think WiFi works even with that one.
  5. I think hexdump added some DTS patches to: https://github.com/jernejsk/linux-1/tree/h616-hdmi Me, I was unable to "integrate" that kernel into mainline. But I'm a newbie.
  6. I think he was referring to Armbian, which does not reboot even with genuine Sandisk cards. I seem to remember that at a certain point, amid various kernel reconfig/rebuilds, I had it rebooting properly by disabling "Enable suspend to disk" and disabling "Enable hibernate" in kernel Power Management section. But I'm not 100% sure.
  7. Confirmed. At some point, rebuilding the latest mainline kernel from the Unstable branch, I managed to have the board rebooting properly; but it was in the middle of many tests and never managed to succeed again.
  8. Indeed. For example, my Rock64 and my Neo3 are stable at 1.3 GHz with -25mV and -50mV respectively vs. default OPP values. Silicon lottery. It's still strange that H6 DTS lacks a proper OPP. Maybe with Unstable kernel, based upon 5.11 mainline? Some patches for H6 were included in 5.11 and accompaining DTS.
  9. The OP asked for undervolting, not underclocking. @hcacIt's strange that the DTS lacks the OPP with the microvolts for each frequency step. Could you post it?
  10. Maybe my problem is a bit different then. My Rock64 (with both Armbian Stable and Unstable) does not reboot after "sudo poweroff": it performs the shutdown sequence, but does not really "power off". It is halted, does not respond to login or ping, but the peripherals are still powered and the board still draws the typical idle current (about 220 mA); the heatsink stays warm too.
  11. This sounds like good news!! Maybe poor little H616 is going to get some love by mainline kernel? Fingers crossed!! Arm updates in Linux 5.12 Removal of several obsolete 32-bit Arm platforms – efm32, picoxcell, prima2, tango, u300, zx, and c6x, as well as associated device drivers. Allwinner Allwinner H616 and H616-R – Initial support including pin controllers, clocks Allwinner/sunxi power management Various DTS changes ...
  12. @firewire10000 Hi, I can confirm this behaviour, both with the Stable image (kernel 5.10.21) and with the latest Unstable from yesterday (kernel 5.11.15). Unfortunately I don't know how to fix it. I tried rebuliding the kernel from the latest "Edge", with CPU Power Management enabled, but nothing changed. The Rock64 is not supported by Armbian, so if powerdown is important to you, I would advice sticking with Ayufan images.
  13. Ok, so let's see the steps I followed. 1. Installed Armbian Unstable for OrangePi Zero2: https://imola.armbian.com/dl/orangepizero2/nightly/Armbian_21.05.0-trunk.77_Orangepizero2_hirsute_edge_5.11.11.img.xz 2. Forced ethernet at 100 mbit/s, otherwise it did not work: added in /etc/rc.local ethtool -s eth0 speed 100 duplex full autoneg off 3. Downloaded hexdump's precompiled kernel (derived from jernej's 5.11.0rc1 kernel): https://github.com/hexdump0815/linux-mainline-and-mali-allwinner-h6-kernel/releases/download/5.11.0-rc1-stb-616%2B/5.11.0-rc1-stb-616+.tar.gz 4. Extracted the various parts and fixed the symlinks: Image -> Image-5.11.0-rc1-stb-616+ uInitrd -> uInitrd-5.11.0-rc1-stb-616+ dtb -> dtb-5.11.0-rc1-stb-616+ 5. Inside dtb-5.11.0-rc1-stb-616+, created a new folder "allwinner" and moved the 3 .dtb there; otherwise, initramfs would not find them 6. Rebooted. Voilà, we now have a working mainline-ish kernel (patched 5.11.0rc1) with USB support! [ 57.289791] usb 2-1: new high-speed USB device number 2 using ehci-platform [ 57.454110] usb-storage 2-1:1.0: USB Mass Storage device detected [ 57.454976] scsi host0: usb-storage 2-1:1.0 [ 59.122397] scsi 0:0:0:0: Direct-Access Lexar USB Flash Drive 1100 PQ: 0 ANSI: 6 [ 59.124408] sd 0:0:0:0: [sda] 125038592 512-byte logical blocks: (64.0 GB/59.6 GiB) [ 59.125522] sd 0:0:0:0: [sda] Write Protect is off [ 59.125549] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 [ 59.126563] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 59.163290] sda: sda1 sda2 [ 59.168389] sd 0:0:0:0: [sda] Attached SCSI removable disk
  14. Partial success. I was able to boot @hexdump 's precompiled kernel (using Armbian "unstable" image). This kernel indeed has USB working! I am not able to rebuild this kernel by myself, but at least we have a mainline-ish kernel with working USB! More details later, have to go now.
  15. Not the same results.. maybe different revisions? and my OrangePiZero2 never got past 61 degrees, and that's without an heatsink. I added a tiny heatsink, and it stayed below 52 degrees even after repeating 7zr benchmarks
  • Create New...