1. 16
  1.  

  2. 6

    So you’re telling me I have to find my beaglebone and try this out? Thanks a lot guys.

    For serious, the absence of a second stage bootloader is remarkably annoying. UBoot is fairly capable, but quirky, and I’ve found it’s trivial to crash it. The biggest hindrance is that since it loads kernels from msdos partitions, it requires a multi step dance to install a new one. And the OpenBSD kernel has a nonzero chance of chewing the filesystem to bits just because. And usually you want to keep this partition small, which limits the size of your kernels of yore collection. I basically gave up playing with my arm toys for this very reason.

    1. 2

      It’s unfortunate how little support there really is for ARM based systems besides operating systems such as Ubuntu and Debian. The surprising reality was realized when I got a Raspberry Pi and was having numerous issues trying to get FreeBSD running on it.

      1. 1

        Well, on the bright side, once you’ve got it worked out for a Raspberry Pi all Pis benefit. Less hardware silliness than PCs. :)

        1. 3

          I don’t think that’s true, since I was unable to boot FreeBSD on my Raspberry Pi 3 using a Raspberry Pi 2 image.

          1. 1

            I mean, there’re a lot fewer configurations of RPis than there are processors, mobos, and graphics chipsets, right?

            1. 3

              For a specific device, yes. But one might also say that once you get one 2015 think pad X1 Carbon working, all of them will work. Getting one rpi to work does very little to get similar devices like beaglebone working. But all of the hardware support for the X1 meant the asus zenbook works great too.

              ARM devices are different in different ways than PCs.

      2. 1

        What do you mean by “chewing the filesystem to bits”?

        1. 1

          Corrupting it. The msdos code is pretty fragile.

      3. 2

        \o/