• Content Count

  • Joined

  • Last visited

  1. 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-r
  2. 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.
  3. 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
  4. I have the RockPiS, too; quite nice, but very difficult to find here (Italy) and it's quite slower. Power efficiency is not much higher, by the way. In absolute terms, using "7zr b" as benchmark, RockPi-S gives 2327, OrangePiZero2 3739 (1.6x) Using "7zr b" MIPS / MHz as an IPC figure, the RockPi-S gives 1.78, while the OPIzero2 gives 2.54. Using "7zr b" MIPS / W as an efficiency figure, RockPi-S gives 1450, OPIZero2 1246 Also, microSD speed is almost 2x on the OPI02. A very nice board (at 20 Eur!), if only we could iron out USB support.
  5. The board is very good. IMHO, one of the best out there! And I have so many SBCs... maybe 10 or more. Let me summarize: Small and cheap Draws little power, thanks to the 28nm SOC Does not run hot, at all, not even with the (quite bad) Orange kernel (which loads one core at 100% all the time), not even at 1.5 GHz Has onboard audio MicroSD is quite fast, among the fastest actually I see it as the best SBC for battery-powered projects, or whenever heat dissipation is an issue
  6. We know that 5.11.0RC1, patched by jernej and then by hexdump, had USB port working. I tried using their DTS with Armbian current unstable image (kernel 5.11.11), but USB did not work. So, I would guess, something occurred between 5.11.0RC1 and 5.11.11, which did break USB for the OrangePiZero2. I tried building their 5.11.0RC1 on the OPI itself; but it did not boot (dropped to a shell within initramfs: no microSD visible to the kernel) Now I am trying a few local builds of 5.11.0RC1 with different kernel configs. Not easy, because each build takes fore
  7. A summary of my (fruitless, at the moment) efforts: Working on OrangePiZero2 512 MB, headless, so command line only: can't comment about GUI, graphic driver etc. - Armbian Unstable boots, but: CPU works at low clockspeed (I would say about 1.0-1.2 GHz but with something like "powersave" or anyway a conservative governor); overall is not very responsive, in particular it's very slow at building anything There are lots of drivers loaded, so the available RAM is scarce (about 300 MB) and leads to swapping when compiling Ethernet does not work at 1000 mbit/s,
  8. @hexdump thanks for your support. I'm reading through your "readme.616" now, and have a few doubts. You write: # make defconfig # /compile/doc/stable-aw/misc.616/options/enable-docker-options.sh # /compile/doc/stable-aw/misc.616/options/enable-additional-options.sh make oldconfig which is not very clear to me. Apart from the "docker options", which are not interesting to me ATM, why did you comment out the other lines? Why do you perform a "make oldconfig"? Thanks!
  9. @Henry Delphing I'm trying to set up an "OrangePi kernel building" environment on one of my SBCs, a Rock64 2GB running Armbian stable. It's a difficult task, because documentation is often obsolete, sparse and conflicting; plus, every pre-cooked build environment is quite rigid about what to build and from which source. Anyway, my goal is to replicate Hexdump's kernel: clone jernej's sources, apply hexdump's patches, load hexdump's kernel config and build. Then sort out which of the various DTSs actually enables USB on the PiZero2. If and when I'll reach my goal, I'll post
  10. I'm an Armbian newbie. As for now, following the guide at https://docs.armbian.com/Developer-Guide_Build-Preparation/ , I think I have a working build environment. Where should I copy your kernel source, config etc. (from https://github.com/hexdump0815/linux-mainline-and-mali-allwinner-h6-kernel) within the Armbian "build/" folder? It looks like: -rwxrwxr-x 1 8569 Apr 5 15:07 compile.sh drwxrwxr-x 13 4096 Apr 5 15:07 config drwxrwxr-x 2 4096 Apr 5 15:07 lib -rw-rw-r-- 1 18026 Apr 5 15:07 LICENSE drwxrwxr-x 3 4096 Apr 5 15:08 output drwxrwxr-x 5 4096 Apr 5 15:07 p
  11. You mean, on my lowly 512 MB OrangePiZero2? Aren't 512 MB too scarce to build a kernel? That's good to know! I mean, back in the times I used to build 1.x on a 32 MB 80386, but Linux kernels were tiny in comparison
  12. Thank you! Will study how to cross-compile a kernel, outside the "standard" Armbian scripts. I'm new to cross-compiling and also to kernel building for ARM boards (u-boot, DTB etc.), so it's going to be fun
  13. Good catch. Added the phys references to usb@5101000 and usb@5101400, but unfortunately it does not work yet. Host controllers show up in dmesg, but the USB port remains "dead": does not even power peripherals. It will take a longer wait it seems, thanks anyway!
  14. First of all, thanks for your support. Much appreciated. It seems to me, that changes in that commit are already present in my decompiled DTS (from kernel 5.11.11-sunxi64 Thu Apr 1): I see the same phys references in USB nodes. It's a bit hard without the labels, but phys = <0x15 0x01> seem to correspond to your phys = <&usbphy 1> and so on usb@5100000 { compatible = "allwinner,sun50i-h616-musb\0allwinner,sun8i-a33-musb"; reg = <0x5100000 0x400>; clocks = <0x02 0x72>; resets = <0x02 0x32>; interrupts