this post was submitted on 08 Oct 2023
451 points (98.5% liked)

Technology

59596 readers
5069 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
L3s@lemmy.world
L3s@fry.gs
L4s@fry.gs
L4s@lemmy.world
enu@lemmy.world
451
Review: Framework Laptop finally gets an AMD Ryzen config—and it’s pretty good (arstechnica.com)
submitted 1 year ago by leo@lemmy.linuxuserspace.show to c/technology@lemmy.world
62 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Abbrahan@lemmy.world 10 points 1 year ago (2 children)

They were talking about the usb modules. The back two on either side (the ones closest to the screen) have an issues where the USB 4 Type C to USB A adapter is not fully going to sleep when nothing is plugged in. So ArsTechnica's reviewer most likely had one of the USB A modules plugged into those two USB 4 ports which causes their apparent poor battery life.

[–] TheHobbyist@lemmy.zip 5 points 1 year ago* (last edited 1 year ago)

Indeed. On both the picture at the top of the article and at the bottom, do we see them having the USB-A expansion card in the slot closest to the screen. If that's how it was configured for the battery test, it would show battery life in a non-optimal configuration.

Edit: this is only an issue on the AMD board.

[–] Nioxic@lemmy.dbzer0.com 2 points 1 year ago (1 children)

So.. a fixable issue.

[–] Abbrahan@lemmy.world 4 points 1 year ago

I believe Framework said they are looking into fixes for this issue, either with firmware patches or if neccesary a hardware revision of the USB A module. Current workaround is just to not put USB A into those two back slots.