jpegxguy

Members
  • Content Count

    32
  • Joined

  • Last visited

About jpegxguy

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. In light of a recent change of role for this Renegade board (It'll be a small headless server on a different location from me), I've switched it to Armbian! The changes I've made besides the usual config are: GPT (Not necessary: I just like the checksumming + backup partition table) and U-Boot switch to legacy channel because that channel has the ums U-Boot command. I figured Armbian would be less risky for stability, especially for kernel upgrades on a device I don't have physical access to. The armbian-config and relevant utilities are nice too.
  2. Yeah, I just like the Arch way of things. I started with Ubuntu like most people, and I do run Debian on one of the machines, but on my laptop I use Arch™ As for Debian being "better" I mean in the sense of "even being doable",. I brought the U-Boot upstreaming topic here because this distro does care to bring U-Boot and the like to more boards than other distros, especially ones that are not ARM-specific. As I mentioned, I didn't even know some defconfig for Renegade had been upstreamed! It was only Rock64 before, haha
  3. That's true, and I think Armbian is essentially the only way if you plan on using these boards' hardware, like hardware acceleration e.t.c. I do look around in the armbian build repo and there are always nice patches and fixes in the patch/ directory. I have SD cards with Armbian, Arch and other distros, and I only stick to Arch on headless because I'm less familiar with debian packaging. If I wanted to run anything more damanding than SMB or a torrent client I'm pretty sure Armbian is the only distro with support for these ARM boards' quirks. Generic distros like Debian, or Ubuntu or Arch are
  4. There would be a lack of maintenance because 5.7 is not an lts version. 5.4 does exist though which is nice. Wait, why for 2 weeks? I was thinking I wouldn't be able to boot anything past 5.8.0.
  5. Armbian's kernels are fine! What I mean is that with the rockchip U-Boot I had before, I would not be able to run kernels past 5.8, at least on the distro I run on that card (Arch), which would be a problem for security in the future. I'd be stuck on 5.7 for example, with 5.10 being out... (e.t.c)
  6. Thinking longterm, I don't want to be stuck to legacy kernels. Of course I like the ums in the legacy uboot, it's just my solution for now
  7. Thanks. Well for my headless needs, performance is fine, so I'll keep the mainline U-Boot to boot Linux 5.8
  8. I definitely agree that it's not your concern if it's an Arch issue. I wanted to post because the whole mainline experiment with U-Boot. I really appreciate this project and its efforts with these funky Rockchip boards! So UMS is not an upstream thing? Is it that it needs a lot of board-specific patches? EDIT: # grep ddr /sys/kernel/debug/clk/clk_summary clk_ddrmon 0 0 0 24000000 0 0 50000 pclk_ddrphy 1 1 0 75000000 0 0 50000 pclk_ddr
  9. Thanks for the answer! Yes it would be awesome if UMS was enabled! cat: /sys/class/devfreq/dmc/trans_stat: No such file or directory Specifically, there is nothing under the devfreq directory. I'm running Linux 5.8 on ArchLinuxARM. The guys on the archlinuxARM forum are having (at least one of them) the same issue of getting stuck in "Starting kernel..." when using Rock64 and Linux 5.8, so it's not isolated to Renegade Maybe it has something to do with that distro's specific Linux 5.8 version?
  10. It seems the Linux kernel 5.8+ on aarch64 is incompatible with the U-Boot from 2017, at least on the RK3328 boards. This apparently affects the Rock64 as well as my own Renegade. Essentially U-Boot gets stuck on "Starting kernel..." In this post https://archlinuxarm.org/forum/viewtopic.php?f=23&t=14657&start=10 they fix it by recompiling u-boot, newer version from upstream In addition to the existing rock64 defconfig, it seems that the defconfig for the Renegade was finally upstreamed on May! https://github.com/u-boot/u-boot/commit/bab972948e152e468fa5ab34764769fc4cddc
  11. Have you tried the upstream kernel or are you using the vendor 4.4.something? Sorry if the question's been answered before
  12. I gotta be honest with you, I do like the finicking! Plus I'm tight on money. So I'll play around with uboot and its commands any day. I just found out that USB Mass Storage emulation works fine for playing around with the emmc from a PC! I never mentioned Armbian in my post. Armbian is very important and I'm thankful it exists. As far as I'm aware armbian is the only ready out-of-the-box experience for this board (the ones from Firefly are old and they crash a lot) I'm using an Armbian U-Boot with Archlinux on this board for months now. I was talking about Rockchi
  13. I just want to mention this happens regularly. I thought I'd found a version that doesn't do it but now I have no idea how to escape it. Maybe it's random. All I know is perhaps I should buy an RPi 4 to use as a NAS and have this just to play with. It's not supported at all by the guys that sell it, while all the non-Rockchip boards in the LibreComputer lineup have fine support. It's a shame
  14. I've been using Arch Linux Arm with the generic linux-aarch64 kernel for a while now on my LibreComputer Renegade. Works nicely and I don't have to stay with an outdated vendor kernel. That said, I use it as a headless server. I don't know what limitations there would be when it comes to graphics performance.
  15. It was mentioned to me by email that the ethernet TX issue I describe here plagues this board as well (my board is the LibreComputer Renegade). It seems like the exact parameters might depend on each specific device, in which case the "best" solution would be some kind of "autoconfiguration" for the PBL, but that is in a future TODO. More about the issue andthe discussion here: https://patchwork.kernel.org/patch/10880481/ Eventually this patch was merged for the Renegade upstream: https://patchwork.kernel.org/patch/11017833/