• pnutzh4x0r@lemmy.ndlug.org
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    4
    ·
    1 year ago

    Kinda disappointing as it shows a lack of care and support for Linux, but hopefully the fix will come out soon.

    I look forward to seeing the Linux numbers.

    • bitwolf@lemmy.one
      link
      fedilink
      arrow-up
      31
      ·
      1 year ago

      Been pretty involved with Framework, having the first gen and waiting for the AMD upgrade kit to ship.

      They’ve been pretty transparent about these bios issues to the backers, they’ve been sending emails on the updates and resolution steps between Framework, the bios manufacturer, and AMD.

      So yeah, this looks bad from the outside, but all of the stakeholders are on the same page and they’re really setting the example for how a company should treat their customers.

    • cobra89@beehaw.org
      link
      fedilink
      arrow-up
      9
      ·
      1 year ago

      It was a kernel regression that caused the issue, not sure that is entirely their fault. I would think that’s more on AMD and the kernel devs.

    • gears@sh.itjust.works
      link
      fedilink
      arrow-up
      17
      ·
      1 year ago

      It means a functionality that used to work stopped. It’s used in software development. It’s common for software to go through “regression testing” to see if everything old still works after a new feature is added.

  • mufasio@lemmygrad.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I’ve been waiting for a ryzen framework laptop since spring 2021. I’m in batch 1 and can’t wait to get my hands on it. I’m sure they will have these BIOS/firmware issues sorted out by launch, and I’ve been waiting this long so a couple more weeks isn’t that big of a deal.