Live data from Hacker News

The Framework Laptop 13

frame.work

221–230 of 335 posts

Re: The Framework Laptop 13

#221

"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?

Why not use US/UK layout? The product is mainly for programmers therefore I'm certain the demand for these layouts is low. Scandinavian/German etc layouts are a pain in the ass to write chars needed for programming to behind with.

Just map your keys so you get your umlauts with caps from where you are used to, not what your keyboard labels tell you.

Or just ä - caps+ a etc.

Re: The Framework Laptop 13

#222
post #199
post #2

I still hope to see a non-x86 version. The less bloat the better.

There should be at least two RISC-V microarchitectures next year that could potentially be used in this manner. Ventana Veyron, TBA before end of year, and Tenstorrent's Ascalon, TBA 2024, competitive with Zen5.

Veyron is a data center chip. I haven't seen TDP numbers but it's almost certainly unsuited for a laptop. Ascalon is IP and is AFAIK only available as such or as part of a data center machine learning chip.

I don't think the market forces are driving towards a RISC-V laptop chip (TH1520 is the only one that has mentioned notebook, but it's a very low-end Cortex-A72-class processor).

Hopefully this will improve eventually.

Re: The Framework Laptop 13

#223
post #188
post #147

Earlier quoted context omitted.

Indeed, I have been on Framework mailing list for 2 years and hate seeing these updates. It seems silly that Framework can't figure some way to ship orders to the rest of EU. No need for specific keyboard, just let us place orders.

Weird, perhaps a regulatory hurdle or different warranty requirements/costs?

I would expect that within EEA most of the regulations would be the same and I don't think it's the problem.

What you would need though is translated manuals and such by law. Maybe even localized support for warranties that could raise costs to enter a market.

This is only my assumption, but it would make sense, that's why they cover even smaller English speaking countries like Ireland. Or for example Germany is a big market, but they cover Austria too, because they have German language for free.

Re: The Framework Laptop 13

#225

I would love if there was an ARM flavour with 10+ hours of battery life under sustained use (like I can get on my M1).

The future is RISC-V not ARM. The former will be everywhere, the latter only in Apple devices.

ARM is probably the architecture in the majority of devices currently if you account for android phones and iphones.

Re: The Framework Laptop 13

#226
post #171

Earlier quoted context omitted.

Yes, since like 2012 with the MacBook Pro. That's how retina works. It's 2023 now.

And almost no PC laptop copies that concept. The benefit is simply not that compelling unless you are designing type faces maybe. But maybe we boring PC people just can’t miss what we don’t know. Like Bentley cars or Champagne when we can get Toyotas and sparkling wine. ;)

...or maybe it's just market segmentation to give PC plebs inferior tech? You seem to be proud of being what some marketing exec views as an unimportant low-margin value segment only good for getting rid of old stuff.

Re: The Framework Laptop 13

#228

Earlier quoted context omitted.

Having fpgas on-board feels like something that would have been a game-changer even pre-ai. Imagine if your Ryzen chip could do hardware encode/decode of h266 the moment the spec was finalized.

I can't find evidence it really made it out to consumers, & even less evidence there was any followup, but Intel did have a Xeon + Arria 10 GX FPGA chip, back in 2018: Xeon Gold 6138P with Arria 10 FPGA. https://www.anandtech.com/show/12773/intel-shows-xeon-scalab... At the hyperscaler level there's been a lot of adoption of SmartNICs, which are often FPGA based. That makes me feel like there's a pretty big market he…

Follow-on question, what makes FPGAs so dang expensive?

Re: The Framework Laptop 13

#229

I'm super happy for this and it's truly great to see framework continuing the quest, and I would still buy a new framework today (if they weren't out of stock) but it is very frustrating how out of stock nearly everything is from current and last generation. You can't even buy a new 12th gen intel at all, and the 11th gen important things (like US Keyboards) are out of stock. As a US English speaker with a a little S…

Replacement parts are available in the Marketplace, and both US English Input Covers and US English Keyboards are in stock, along with most other parts: https://frame.work/marketplace

For older generation systems (12th Gen and 11th Gen), our general intent is to sell out of the older generation just as we start shipments of the newer generation. We usually get pretty close, but sometimes we do have more or less demand than anticipated.

Re: The Framework Laptop 13

#230
post #108
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.

We've used the Intel AX210 on everything except the original 11th Gen pre-built systems which use AX201 and the Chromebook Edition, which uses AX211. AX210 on Ryzen is a YMMV situation. Neither Intel nor AMD will provide any guidance or support around the combination, and we don't have access to any of the needed source to resolve issues as they come up.

I've been using an AX210 on a Ryzen based laptop since early 2022.

I initially had issues with it causing the laptop to lockup hard, if iwlwifi module (AX210 driver) was loaded, on resume from suspend to disk. It was easy to work around using a hook script to down the interface and unload the module before suspend, and reload + up interface if it had been up at time of suspend. S3 suspend to ram / resume worked fine without the hack.

Currently 6.1 kernel (Debian testing). When I initially put the work around in place it was IIRC 5.6 kernel, so maybe not an issue anymore, but haven't bothered checking to see.

I only bought an Intel AX210 because it was cheapest tri-band card. The Intel card is pretty gimped (broken AP modes, breakage due to issues "magically" determining regulatory domain, Intel removed functionality in recent driver versions that could somewhat work around the first two issues so now impossible to mitigate, etc.). I would probably try a Mediatek card, if doing this today (in spite of my general policy of avoiding Mediatek). Last I checked, the equivalent Atheros chipset still had poor free driver support?!

Post reply on HN