• theunknownmuncher@lemmy.world
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    2 days ago

    The only thing I could see being an issue with a desktop motherboard are built-in wifi, bluetooth, or sound chips, and that’s really not been an issue to worry about for years. Complete non-issue for any Intel chipsets, which are basically all officially supported. I think otherwise I really only see like Realtek, which is supported. At worst you just need to install proprietary drivers.

    Sounds like framework’s motherboard has poorly implemented ACPI, but this would not be an issue for manufacturers for typical desktop hardware (ASUS, ASRock, MSI, Gigabyte)

    • e0qdk@reddthat.com
      link
      fedilink
      arrow-up
      4
      ·
      2 days ago

      I’m not complaining about Framework’s HW there; my old desktop (which uses an ASUS MB, IIRC) had that issue. I’m on my own figuring out WTF is going wrong between the CPU, the kernel, quirks of the motherboard, BIOS, GPU – or whatever else might be causing it to enter a boot loop if I try to suspend and then resume the system.

      If I had a similar problem with the Framework system, I could go to Framework and say “Fix it!” and expect to get help because they officially support the configuration. That’s my point.

    • jonathan@piefed.social
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 days ago

      Last two mainboards I bought had incompatible wifi cards. The first of those also had some weird issue with aspm that meant it ran hotter than it should have needed to.