After they hit a supply line issue earlier this year, I decided to try getting a Framework instead.
Been using my Framework laptop for a month or so now consistently for heavy programming work, and it is the best machine I've ever had. Thank you! It also was the catalyst to get me into using Linux (Ubuntu) which has been a huge blessing beyond what I expected.
I posted a photo of myself at a coffee shop to a Discord group, and someone saw the corner of the laptop. They asked "Is that a Macbook I see?" and I explained to them "Nah it's a Framework" and shared the link. Didn't really expect much beyond that, but actually they loved it. Several people looked at it and said "Wow! This sounds amazing! Actually... going to save this for later..."
Ubuntu: Ubuntu 22.04.1 LTS
Linux: 5.17.0-051700-generic
The only problems I've had so far is the "brightness" fn keys don't work, and bluetooth isn't great with certain devices like Airpods.The brightness keys isn't a big deal, can still set brightness in the OS. It's probably fixable through some manual keymapping.
Bluetooth is more annoying but I somehow doubt it's a hardware issue. I just ended up getting Sony wireless earbuds to complete my transition away from Apple.
That being said, I also tried to dual boot Windows. Windows really does not like the hardware, and the Framework driver install package (https://knowledgebase.frame.work/en_us/framework-laptop-bios...) had limited effect in fixing the issues. Lots of bugs with audio and graphics.
So, for now I would say it is too premature for Windows, but great for Linux!
You can enable the hotkey support by blacklisting the hid-sensor-hub driver: vi /etc/modprobe.d/framework-als-blacklist.conf Add the following: blacklist hid-sensor-hub And then restart
It worked, but it needed `hid_sensor_hub` with underscores! and `sudo update-initramfs -u` before the reboot
A sibling comment shared the fix for the brightness keys, but you can also grab that information from our setup guide for Ubuntu: https://guides.frame.work/Guide/Ubuntu+22.04+LTS+Installatio...
https://community.frame.work/t/audio-issues-windows-11/11726
https://community.frame.work/t/windows-no-audio-output-devic...
https://community.frame.work/t/windows-11-audio-no-longer-wo...
Thanks for the tip
Some people have been getting hard graphics lockups (seems to be an Intel 12th-gen GPU / GNOME issue that may be affecting more than just the Frameworks). I'm running Sway and have yet to have any lockups over a month and a half of usage, though. Here's the community discussion thread: https://community.frame.work/t/hard-freezing-on-fedora-36-wi...
* Getting out of sleep (deep RAM sleep, not hibernate)
* Handling password/fingerprint authentication once out of sleep
* Wifi rescan frequency
* Occasionally, plugging/unplugging external screens
And I've got no idea why. Once woken up and plugged to whatever I need to use, it's a really good laptop.
I've been considering a framework as a replacement actually!
One of the things I really care about is battery life + sleep performance.
The article mentions:
> .* At the same time, the Framework Laptop Chromebook Edition is our most power efficient product yet with optimizations from Google and Intel that allow for long-lasting battery life.
Can you provide some numbers around the battery life improvements? Sounds exciting! (And are these going to be backported to the normal 12th gen boards, or is it a feature of the unique mainboard/not firmware?)
Can you speak to the OS image as well? Is there any non-upstream drivers that are relied on? I notice lots of chromebooks have drivers that aren't in the regular upstream kernel, but just in the chromiumos source. I'm hoping that I could eventually swap OS' if needed w/o getting a new mainboard, and want to see how viable that is.
Thanks for the hard work, and in advance for the questions!
(P.S. like everyone else, AMD would be exciting if you don't know that :p)
[edit] one of my biggest disappointments in my slate is that it never received vm-in-vm support with the newer kernel. Is /dev/kvm available in the linux container? I _think_ that goes hand in hand with the steam supuport, but not sure
We actually did learn some things about the Intel re-timers through this product development that let us come up with ways to improve the behavior on the regular 12th Gen Framework Laptops. We are currently developing a firmware update for that that will improve both active and standby battery life.
Is this specific to Intel's 12th gen or can it also be ported to the 11th gen? I have an 11th gen Framework and am delighted with everything about the laptop except for battery life. If that could be improved, I would have absolutely no complaints whatsoever about the laptop.
Is there a sense that there is an untapped 'premium' chromebook audience or will this make sense even without that. Perhaps you're looking for large/discounted partnerships with educational organizations?
I'll need a new laptop soon, and would really love to see either and ideally both of those.
But for the company it's probably a good move. Get help from Google on battery optimisations, open up a new market and hopefully get a sizeable order from Google directly, all without a crazy amount of re-engineering...
you could gamble that they are and get the 11th gen intel kit, then upgrade once (if) an amd kit is released. or wait and see.
[1] https://www.johnlewis.com/google-pixelbook-go-ga00526-uk-lap...
There was a lot of love for the original Pixelbook, so I'm sure it will be an exciting prospect for many.
While cheap Chromebooks abound, the market for Chromebooks has matured significantly and a lot of vendors offer high quality 'premium' solutions that really meet people's needs, while typically costing less than say Apple's offerings. Framework is jumping on that bandwagon.
They're a niche market: C-level executives at companies that use Chromebooks, developers at those companies, Linux fans who will mostly use the Chromebook to run Linux apps. They make more economic sense as an adaptation of a laptop that is already being sold for other markets rather than as a dedicated product.
The Pixelbook line never did enough volume for Google to make money on it. It was a proof of concept, a way of showing that a Chromebook didn't have to just mean a low end and cheaply built Acer or the like, but could be something that higher end users would happily use and not be ashamed to be seen with when they do a presentation. Now that other companies are making premium Chromebooks, there is no longer a need for Google to produce them.
I noticed the 256GB of storage is different from the DIY options. I'm guessing this is driven by hardware support limitations for ChromeOS. I'm wondering if the same is true with the RAM.
The FAQ also says you can add memory and storage later, but I noticed the FAQ mentions "We recommend using modules from Google’s Chromebook compatibility lists, which can be viewed in our Knowledge Base, and are available for purchase on the Framework Marketplace." I didn't find that compatibility list anywhere in the Knowledge Base, but I did find this post (https://community.frame.work/t/introducing-the-framework-lap...) which seems to suggest you can upgrade to 64GB of RAM and 1TB of NVMe storage, though it's not clear if that's using parts that are on Google's compatibility list or not. Can you provide any clarity on this?
On the storage, we use Western Digital SN730 and SN740 drives, which are also what we put in the pre-built Framework Laptops. These are roughly equivalent to the SN750 and SN770 retail drives, respectively.
On the memory and storage, ChromeOS technically has an allow-list for memory and storage, though in practice we have seen modules not on the list work fine. We'll be adding that list onto the Knowledge Base. We will be making parts that are on the list available in the Framework Marketplace for guaranteed compatibility (the memory we already have, and we'll be introducing SN730/SN740 storage up to 1TB).
It'd be nice to see improvements in the mainboard of the standard laptops as well. I imagine, in theory, much of the firmware and OS improvements could be installed on one of them already.
> On the storage, we use Western Digital SN730 and SN740 drives, which are also what we put in the pre-built Framework Laptops.
Ah, now I see it. The pre-built one has 256GB & 512GB options that the DIY ones don't have. I'm always amused by how specs differ between OEM and non-OEM parts.
> On the memory and storage, ChromeOS technically has an allow-list for memory and storage, though in practice we have seen modules not on the list work fine. We'll be adding that list onto the Knowledge Base. We will be making parts that are on the list available in the Framework Marketplace for guaranteed compatibility (the memory we already have, and we'll be introducing SN730/SN740 storage up to 1TB).
Awesome. Thanks. These were really helpful answers. As feedback, I'd say it would be nice to be able to select different starting memory options in particular, but this is a really great offering.
- What kind of commitments did each party make to each other?
- Did Google request anything of Framework? What requests did Framework agree to? Which did they deny?
- What differentiates this product from the normal offering?
2. Does this come with the silly Chromebook keyboard that is missing two keys on the left side? If it does, is it compatible with the normal keyboard part?
3. When will you bring a motherboard with an AMD APU?
1. Could I swap mainboards to upgrade the 11th gen framework to the chromebook version? 2. Is the coreboot chip flashable with custom firmware? / Is the boot process locked?
This might well be the mainboard I've been waiting for. Congratulations on shipping this!
When switched into developer mode, it should be possible to update and customize firmware. There is a pretty active community for Chromebook firmware customization out there.
I'd also love to learn more about the motivation to create this laptop and the target audiences!
Edit: the article says “receives automatic updates for up to eight years” but an upper bound isn’t so helpful here.
https://support.google.com/chrome/a/answer/6220366?visit_id=...
If you purchase a brand new chromebook whose model has been sold for 3 years already you won't get 8 years of support.
Besides, now is a terrible time to start offering AMD laptops. You want them to drop a 6000-series laptop when the next-gen mobile Ryzen chips were announced less than a month ago? Have some patience!
Technically the only mobile Ryzen chips announced so far are based on Zen 2 which is about to become two generations old. Expect "next-gen" mobile chip announcements in January.
(The recent Zen 4 announcements have been for desktop parts.)
Here's the segmentation:
* Mendocino (Ryzen 7020 Series) - Everyday Computing
* Barcelo-R (Ryzen 7030 Series) - Mainstream Thin & Light
* Rembrandt-R (Ryzen 7035 Series) - Premium Thin & Light
* Phoenix Point (Ryzen 7040 Series) - Elite Ultrathin
* Dragon Range (Ryzen 7045 Series) - Extreme Gaming & Creator
But the product "launch" will, as you mention, likely take place at CES next year.
That being said, starting w/ Rembrandt, AMD now has full 40Gbps USB4 controllers built on-chip. I'm really looking forward to Ryzen 7040 because Phoenix looks great (Zen4 + RDNA3 on TSMC N4 - yes please) and hopefully USB4 support has matured enough on the AMD side that Framework is able to release something.
My understanding is that the I/O limitation is in the re-timers - currently the Framework uses 4X JHL8040R's (labeled as Burnside Bridge) directly connected to the iTBT: https://github.com/FrameworkComputer/Mainboard/blob/main/Ele... Apple used these for their first M1 MBAs as well: https://github.com/ThomasKaiser/Knowledge/blob/master/articl...
But both Apple and AMD are now using Kandou retimers:
* https://www.gizchina.com/2022/07/25/apple-completely-got-rid...
* https://kandou.com/matterhorn.html
* https://kandou.com/assets/downloads/product-briefs/KB8001-Pr...
> we’ve partnered with ChromeOS because of their commitment to long-lasting speed and transparency. The Framework Laptop Chromebook Edition is built with the Titan C security chip and receives automatic updates for up to eight years, all to keep your Chromebook fast and secure.
There are some other smaller differences. To keep the cost down, the top cover is aluminum-formed instead of CNCed, for compatibility reasons we weren't able to bring our fingerprint module in, and we were able to improve both audio quality and speaker loudness with an improved audio CODEC and louder transducers.
Would any collaboration with them regarding CoreBoot be helpful/desirable/possible/planned/etc. ?
This is what I was hoping when I got the announcement via email. The question is if this will be locked down to chromeos or if it's possible to install your own keys to load a linux distro while still retaining verified boot capabilities.
Forging is in no way inferior to CNC, on the contrary, a forget aluminium part should have more rigidity per unit of thickness, depending on the alloy.
I guess, you got to volumes big enough to open the mould for forging?
If you need an audio engineer, I can refer you one fellow. He worked at Apple, Harman, Asus, BBK, and is now looking to relocated from the East Bloc.
The formed top covers are thick aluminium foils that are folded by machines.
They did show signs of lack of rigidity in the usage of the laptops (it was shipped with the first Framework laptops, and later replaced by CNC for this very reason).
In the Markeplace I can see the new speakers but not the new audio board (or is the codec actually on the motherboard?).
They pointed me to this /gb/en/ url, which has the same chromebook slug but seems to just describe the regular 12th gen laptop: https://frame.work/gb/en/laptop-chromebook-12-gen-intel
So to be clear, no fingerprint reader for the Chromebook? Any chance of adding that in the future?
Is there any roadmap for wider distribution in Europe? Especially eastern part.
Do you honestly believe Google respects people?
What measures have you put in place to mitigate Google's surveillance of its users?
I couldn't find any marketing material pointing out the switches on the originals, so I assumed this was a change for the Chromebooks. But you're right, I managed to find an image of a Framework laptop where the switches are visible.
The ChromeOS doc page "Set Up Linux on your Chromebook" [0] links to a supported models list [1] which does NOT include Framework.
[0] https://support.google.com/chromebook/answer/9145439?hl=en
[1] https://sites.google.com/a/chromium.org/dev/chromium-os/chro...
source: https://community.frame.work/t/introducing-the-framework-lap...
Maybe the support sites will get updated to include Frame.Work
When you don't care about single-core performance and compatibility, there really isn't much reason to use x86 at all. For me personally, my priority is by far battery-life (and LTE support is a nice bonus).
I'm refraining from using Framework until they get an ARM device out to replace my current ARM chromebook (Acer Chromebook Spin 513, my NixOS configuration: https://github.com/L-as/NixOS-lazor)
There really isn't any other performant ARM chip that has more ports, enough to work in a framework 4 port type situation.
If we want to go beyond DP alt mode into USB 4 you could forget it.
I would imagine that regular Linux won't do as well as ChromeOS in terms of battery life, but perhaps still considerably better than the Windows mainboard+firmware.
What is the battery life when running Chrome OS?
If I wanted to, could I later put a full Linux or Windows in some sort of dual boot?
I work in metal fabrication (tradesperson) and run a laser cutter as my full time job, and have an interest in most things metallurgical.
Are you able to talk about the 50% post-consumer recycled aluminium. What were the pros / cons of 50% rather than higher or lower percentages.
How did you see the niche and do you still see it the same way now it is here?
What do you consider to be the value proposition for potential customers of this product?
What is your assessment of the TAM?
Do you have limits on how many differentiated products you are willing to pursue simultaneously in the market?
I've grown to rely on Windows Hello / Mac FaceID. It's disappointing not to have a bio metric option.
Keeping it as a Chromebook with ChromeOS, there are specific firmwares required for the Touchpad and Webcam that required us to create variants. The Fingerprint Module we have is also not compatible with ChromeOS.
I understand if you can't make promises here, I'm also on a product team :)
1. do you have any plans to provide expansion cards for ltr/5g connectivity?
2. do you have any plans to provide more memory for chromebook edition?