Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Framework Laptop 13

frame.work

Post reply on HN
Print view View original

201–210 of 335 posts

Re: The Framework Laptop 13

#201

Post by Laaas »

rektide wrote: post #77

There's a "Ryzen AI" on these AMD cores that is really a modest sized fpga, supposedly. Linux has been landing some support for interfacing with this- calling it XDNA (on a new "CDX" bus) - but no signs yet that users can program it. Would be a fun thing to get exposed to users. Fingers crossed that actually happens; I could definitely see this being very vendored up, that it ends up only really running a couple pred…

Source (CES 2023): https://www.youtube.com/live/OMxU4BDIm4M?feature=share&t=137...

Textual rehash: https://www.tomshardware.com/news/amd-brings-chiplets-zen-4-...

Re: The Framework Laptop 13

#202

Post by bo1024 »

taraharris wrote: post #164

Is there any proprietary firmware on these? If this is truly open, I'm excited, otherwise I do not care one bit. (Scrolling down the comments, I am honestly disappointed that I am the only person asking this question. Or does everyone else already know and I'm just out of touch?)

Don’t think so; you might want to look at Purism, which I think is quite a bit closer. https://puri.sm/

Re: The Framework Laptop 13

#203

Post by jeffbee »

estebank wrote: post #96
jeffbee wrote: post #66

Earlier quoted context omitted.

The Framework wifi card for Intel is an AX201 implementation, which means the only thing on the card is the RF and the rest of the wireless functions are in the Intel SoC. You can't use an AX201 with anything but an Intel platform because of CNVi.

The modern/hardware equivalent of a WinModem.

A good quip but an imperfect analogy. As WinModem victims may remember, the WinModem DSP was in software. No part of a CNVi radio is in software. It is only a question as to which circuit board contains which parts of the wireless stack.

Re: The Framework Laptop 13

#204

Post by f_devd »

sowbug wrote: post #65
f_devd wrote: post #11

Earlier quoted context omitted.

It might be a bit of tinkering but you can enable suspend-then-hibernate with logind/systemd which gives you a similar setup to Macbooks but slightly slower to wake from deep sleep as it needs to go through post/grub again. With the bigger battery provide and new CPU I do hope it lasts longer when idle though.

Does that require a LUKS unlock step?

I believe so, I remember an article on hibernation+luks being more difficult to set up

Re: The Framework Laptop 13

#205

Post by uoaei »

prettyStandard wrote: post #90
candiddevmike wrote: post #81

I wish their mainboard became an actual motherboard spec (something like LAPTOP-ATX), it seems like it's proprietary. Would open the door for more folks to build swappable laptop boards.

They seem to be doing everything they can to make it not proprietary. I'm not sure if there's more that they can do.

We could call it a "new standard" that's so new the format hasn't been recognized by the wider industry. Although there was that Cooler Master case for mainboard only that can turn it into a headless server, so it's beginning to trickle into mainstream awareness.

Re: The Framework Laptop 13

#206

Post by f_devd »

hutzlibu wrote: post #69
f_devd wrote: post #11

Earlier quoted context omitted.

It might be a bit of tinkering but you can enable suspend-then-hibernate with logind/systemd which gives you a similar setup to Macbooks but slightly slower to wake from deep sleep as it needs to go through post/grub again. With the bigger battery provide and new CPU I do hope it lasts longer when idle though.

"It might be a bit of tinkering" Thats an understatement. I never made suspend-then-hibernate work reliable on linux and I tried it over the years on different systems. So I just had developed the habit of always entering hibernation, if I intend to close the lid for longer. On windows suspend-then-hibernate never failed so far. Drivers are just the crux with linux in too many cases. Not much you can do about it, exc…

For the framework 13th gen it only required running a fairly recent kernel (>=6.1) for it to work, but that's definitely hindsight

Re: The Framework Laptop 13

#208

Post by duffyjp »

zen_1 wrote: post #98
duffyjp wrote: post #88

Earlier quoted context omitted.

Huh really? I put an AX210 wifi 6E card in my absolutely ancient Intel i7-2600 Optiplex and it works great.

As I understand it, the AX2X0 cards will work with any CPU, while the AX2X1 cards need CNVi support (so a newer intel SoC)

Luckily I ordered the AX210 over the AX211 because the AX210 was cheaper. :P

Re: The Framework Laptop 13

#209

Post by Tade0 »

theshrike79 wrote: post #198

"We haven’t opened ordering in your region yet, but we’re looking forward to getting there!" ...I've been waiting for two years with money in hand. Please let me pay you, please? Printing a set of keycaps for Scandinavian layouts can't be _that_ expensive?

I feel your pain as I am waiting to do the same.

Apparently it's not just the keycaps but also stuff like warranty, returns etc. - quite a lot of legal bullshit before the product can reach you.

I haven't seen any official announcement for a Ryzen Framework 16 though, so for me specifically it doesn't change much for now.

Re: The Framework Laptop 13

#210

Post by unethical_ban »

jeffbee wrote: post #66
codedokode wrote: post #30

> If you're upgrading your Framework Laptop to the new Mainboard, remember that you'll need ... a Ryzen-compatible RZ616 or similar WiFi card. Why does WiFi card need to be "compatible" with CPU? Isn't it enough to be compatible with PCI-Express? Or are there backdoors that do not work with Intel-backdoor-compatible WiFi cards?

The Framework wifi card for Intel is an AX201 implementation, which means the only thing on the card is the RF and the rest of the wireless functions are in the Intel SoC. You can't use an AX201 with anything but an Intel platform because of CNVi.

This is good info.

It would be nicer if they rephrased it "non-intel locked" to properly assign blame for the lack of modularity. This isn't a Ryzen thing.

Post reply on HN