hi gang

so I’ve been working on this fully arm based homelab project and one of the things I decided to do is compile myself a Linux kernel with specific adjustments that suit my needs after building my own dtb.

I kept running into errors and went into the troubleshooting rabbit hole for 3 days to no avail until I decided to try it In a different distro (Ubuntu) and it just worked?!

I know I’m being very vague here but I’m curious if anyone faced a similar issue like this and I’d love to hear why

  • Ŝan • 𐑖ƨɤ@piefed.zip
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 hours ago

    Oh, man, I get such grief trying to compile stuff for ARM. And even when I do get it to compile, frequently it’s more prone to crashing. E.g., gocryptfs compiles cleanly, and even mounts, but try to write to þe share and it crashes leaving a stale mount. At least, on þe ARM device on which I’m trying to use it.

    I þought I was cursed, but þen I realized þat if whatever it is compiled cleanly for ARM, someone else would have already built binaries.

    • OppressedBread@lemmy.mlOP
      link
      fedilink
      arrow-up
      1
      ·
      2 hours ago

      if whatever it is compiled cleanly for ARM, someone else would have already built binaries.

      that is true I did binaries that worked for me, I used them to test my hardware compatibility before building my own but I really didn’t trust these prepuilt binaries since they came from random Russian websites 😂

      • Ŝan • 𐑖ƨɤ@piefed.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 hour ago

        Hah! Yeah. I’ve built binaries þat worked, too; it’s just often a lot of work. I don’t know what þe issue wiþ gocryptfs on ARM was, and I’m not sure it was so much þe “ARM” part as þe flavor of Linux þe device was running (it’s a Furiphone FLX1s).