32 pointsby mrtz9 months ago8 comments
  • aba_cz9 months ago
    I've seen/fixed similar issue in someone else's Windows 10 notebook few days ago. It seems to have been caused by wifi having the same ssid for 2.4 GHz and 5 GHz and not-that-great signal so OS was for some reason "constantly" switching between those two. After forcing it to use just 5 GHz it went from 1 Mbps to 100 Mbps. Reading this sooner would have prevented my headache.
  • jauntywundrkind9 months ago
    You can set BandModifier2_4GHz=0.01 to make 2.4GHz 1/100th as preferred in the excellent excellent iwd daemon (or 0 for disable).

    https://man.archlinux.org/man/iwd.config.5.en#Rank

    • yjftsjthsd-h9 months ago
      Oh that's clever - not disabling/forcing it outright, but preferring one frequency over the other(s).
  • edarchis9 months ago
    Cross-compiling ? Aren't M1 and Pi both ARM processors ? I've been building apps for my M1 to run on Pi without any issue. Some optimization options maybe ?
    • nappy-doo9 months ago
      Cross compiling is really defined as different platforms, not limiting it to instruction sets. Also, the M1 is an ARM, but the instruction sets aren't exactly the same.
    • jcelerier9 months ago
      If the app leverages the page size in some way you can get into very subtle crashes - app is built on M1 (with 16k page size), page size is stored in a constant in the binary because it's a macro, then you trt to access the entire range of a page in a pi (4k pages) - and things break.
    • mrtz9 months ago
      Cross-compilling from MacOS to Linux. By default OCaml does dynamic linking of all C dependencies. Even with static linking there is a dependency on libc (or the MacOS equivalent) as far as I remember. I had some success so far with Rust, Nim and Go using a musl toolchain[1], but no luck for OCaml. At the moment I'm just using a docker container which mirrors the Debian distribution running on the Pi.

      [1] https://github.com/messense/homebrew-macos-cross-toolchains

  • mkesper9 months ago
    For reliability I suppose you always want LAN.
    • yjftsjthsd-h9 months ago
      Of course wired network is almost always faster, more reliable, and easier (no selecting ssid, no password, just plug in and it works), but it's not always an option; in an apartment you may not be able to do wired, or placement of the machine can render it impractical.
  • Havoc9 months ago
    You can also get pretty cheap usb 2.5gbe dongles that work well with the pis
    • 9 months ago
      undefined
  • akhileshwar099 months ago
    it showing the website is not secure.
    • oarsinsync9 months ago
      The website uses http, not https
  • 9 months ago
    undefined
  • phoronixrly9 months ago
    [flagged]
    • Hikikomori9 months ago
      Price?
      • tucosan9 months ago
        If you don't need the pinouts, it's likely cheaper to get a used thin client or a N100 based machine. You'd get similar power draw, plus a case and a PSU.
        • dtech9 months ago
          It doesn't seem even close. Rasberry Pi 4 starts at €40 or so, while the cheapest N100 PC my amazon query returns is €180.
          • yjftsjthsd-h9 months ago
            I suspect that either you care about performance and the pi loses badly, or you care about price and the pi 4 loses to... probably other pis, actually. Or used x86 off eBay. Or you care about absolute power consumption and again other pis win.
          • echoangle9 months ago
            Used thin clients start at 20€, that’s unbeatable (because they include case and PSU, allow SATA Harddrives, replaceable RAM…)
          • oarsinsync9 months ago
            > while the cheapest N100 PC my amazon query returns is €180

            Check AliExpress. Much cheaper for N100s.

          • Citizen_Lame9 months ago
            Raspberry Pi 4 cannot be compared to N100. It's miles behind.
    • FirmwareBurner9 months ago
      The SW ecosystem and the community were always the selling point for the Pi, never the HW, that always sucked ass compared to the competition.