SatyrSack

It makes more sense to me to have the switches appear as red when the device has the ability to record you. When color is used as an indicator for something, the general convention is that red is negative. Meaning that there is a greater possibility of something going wrong when a red indicator is being displayed. You could argue that "webcam is not working for some reason" is a negative, and that seeing the bright red indicator can bring your attention to the switch as a hint to how to fix the issue. I would argue against that by stating that having a webcam record you when you do not want it to is a much bigger potential negative than the webcam not recording when you do want it to.

Also:

• When a traditional video camera displays a red indicator light, that means the camera is recording.
• On the underside of the Framework 16, the expansion module latches are red when disengaged

We’re excited to share a preview of a Framework Laptop 13 Mainboard with a new CPU architecture today, and it’s probably not the one you think it is. The team at DeepComputing has built the first ever partner-developed Mainboard, and it uses a RISC-V processor! This is a huge milestone both for expanding the breadth of the Framework ecosystem and for making RISC-V more accessible than ever. We designed the Framework Laptop to enable deep flexibility and personalization, and now that extends all the way to processor architecture selection. DeepComputing is demoing an early prototype of this Mainboard in a Framework Laptop 13 at the RISC-V Summit Europe next week, and we’ll be sharing more as this program progresses.

There is excellent philosophical alignment between RISC-V and Framework. Both are built on the idea that an open ecosystem is more powerful than the sum of its parts. To explain why, first we’ll go into what RISC-V even is. RISC-V is a fully open Instruction Set Architecture (ISA), which is the interface point between software and hardware. It’s a defined set of instructions that software is compiled and assembled into that the processor executes to run the actual program. x86 (or the latest version, x86-64) is the most common ISA for PCs today, and it’s what is used in the processors for each Framework Laptop we’ve shipped to date. The x86 ISA was invented by Intel, extended on by AMD, and is proprietary, with Intel and AMD being effectively the only two companies able to use and create processors around it. ARM is another popular ISA, owned by Arm Holdings. Arm licenses the ARM architecture out, which enables companies to pay a license fee for cores to make their own processors that leverage it. What makes RISC-V unique is that it is an entirely open architecture, which means that anyone can extend on it and create their own processors that use it without paying a fee. RISC-V International is the collaborative organization that exists to help develop the standard and define common versions to ensure cross-compatibility of hardware and software. There are hundreds of companies now developing cores and chips around RISC-V, but most of these have been hidden away in embedded applications. The DeepComputing RISC-V Mainboard is one of the first instances of leveraging this ecosystem for the main processor in a consumer-facing product.

All of this is what makes RISC-V unique from an ecosystem enablement perspective. The actual technology is equally interesting. The base instruction set of RISC-V is simple and streamlined, while there are a number of extensions enabling high performance and specialized compute. This means that RISC-V cores can be developed for anything from tiny control CPUs embedded inside a sensor (the Fingerprint Reader we’ve used in Framework Laptops since 2021 actually has a RISC-V core!) to monstrous multi-hundred-core server processors. The DeepComputing RISC-V Mainboard uses a JH7110 processor from StarFive which has four U74 RISC-V cores from SiFive. SiFive is the company that developed CPU cores using the RISC-V ISA, StarFive is the processor designer that integrated those CPU cores with other peripherals, DeepComputing created a Mainboard leveraging that processor, and Framework makes laptops that can use the Mainboard. The power of an open ecosystem!

This Mainboard is extremely compelling, but we want to be clear that in this generation, it is focused primarily on enabling developers, tinkerers, and hobbyists to start testing and creating on RISC-V. The peripheral set and performance aren’t yet competitive with our Intel and AMD-powered Framework Laptop Mainboards. This board also has soldered memory and uses MicroSD cards and eMMC for storage, both of which are limitations of the processor. It is a great way to start playing with RISC-V though inside of a thin, light, refined laptop. The Mainboard will be able to drop into any Framework Laptop 13 chassis or into the Cooler Master Mainboard Case. DeepComputing is also working closely with the teams at Canonical and Red Hat to ensure Linux support is solid through Ubuntu and Fedora. We’ll continue to keep you up to date as we work with the team at DeepComputing to complete development of this new Mainboard and enable access to it. You can sign up in the Framework Marketplace to get notified when we have updates.

We have a couple of other updates around scaling access to Framework Laptop 13. The first is that just like we did for Framework Laptop 16 last week, today we’re sharing open source CAD for the Framework Laptop 13 shell, enabling development of skins, cases, and accessories. The second is that we now have Framework Laptop 13 Factory Seconds systems available with British English and German keyboards, making entering the ecosystem more affordable than ever. We’re eager to continue growing a new Consumer Electronics industry that is grounded in open access, repairability, and customization at every level.

Neat diagram that I hadn't seen before. I plan to keep this image saved so I can refer to it and make sure I am using adequate ports as I swap cards around.

https://knowledgebase.frame.work/en_us/expansion-card-slot-functionality-on-framework-laptop-16-rkUjGm7cn

I am interested in checking out the historical growth of a particular community. Lemmy Explorer crawls for data about the Lemmyverse every 24 hours or something, and that data is made available on their website. But I can only find where to download the latest data. Is there somewhere that I can find historical data? Does Lemmy Explorer archive these anywhere, or does it just overwrite the previous data each time it crawls?

Our final assembly factory for Framework Laptop 16 and all of our sub suppliers are now up and running smoothly. We had a few bumps as we ramped, with an early material shortage on the RGB Macropad and product serialization and data systems issues delaying some of the keyboard versions. All of those issues are now resolved, and we’re on our way to utilizing full manufacturing capacity. We’re currently aiming for an approximately 5 day cadence between sending out “preparing your batch” emails from batch to batch, with a goal to speed that up to 4 days as we reach peak factory output. We sent out the email to Batch 4 late last week and plan to send the Batch 5 email this week. We expect to fulfill all Batch 5 and most Batch 6 orders before the end of Q1 and all current pre-orders before the end of Q2. We’ll be updating the timing that appears on your order in your user account to reflect this. We optimize manufacturing throughput by scheduling larger runs of each configuration, which means we will have anywhere from 1 to 4 different batches in the midst of fulfillment at any given time.

We also wanted to provide an update on the the open issues that we shared in earlier emails:

1. Keyboard deflection - We shared an improvement in an earlier email which involves adding five additional rubber pads around the Mainboard to provide additional support to the keyboard. In parallel to our manufacturing partner completing qualification testing on this, we’ve started dogfooding it internally in Framework. If you’re not familiar with “dogfooding”, it comes from the idea of “eating your own dog food”, or making sure you’re testing what you’re making before others do. As we mentioned in the earlier email, once we complete testing, assuming the results are positive we will roll this into new production and share a form for existing Framework Laptop 16 owners to request a kit of pads.
2. Secondary SSD may disappear - AMD has provided us with the necessary BIOS fix, which we’re now testing as part of an overall Framework Laptop 16 BIOS update. Our initial testing on it is positive. Once this BIOS is ready, we’ll share it into the Community first as a Beta release before the final release.
3. Display frozen after smart MUX switching - AMD has shared an updated graphics driver with us that has the fix for this along with some new features and performance improvements. This is also currently in our test process, and it will follow the same release path as the BIOS update.

Thanks again for your patience, and we’re excited to get your Framework Laptop 16 to you (or the rubber pads and software updates if you already have yours).

The first Framework Laptop 16’s are now in customers’ hands, with more Batch 1 units in transit to those who have received shipment notices. Both our factory and our fulfillment warehouse are now on Lunar New Year holiday, so the next set of units will ship and production will resume on February 15th in Taiwan. That will include the remaining Batch 1 orders along with the first Batch 2 systems. We’ll remain in continuous production from there, with most of our total factory capacity allocated to Framework Laptop 16 manufacturing.

The various modules that make up the range of Framework Laptop 16 configurations are also in ongoing production at our module suppliers. Our keyboard vendor ran into an unexpected component shortage on the RGB Macropad though that delayed the start of production on it. We expedited the missing component from a US distributor to avoid further delays in their China-based supply chain and it arrived just before the keyboard factory shut down for the holiday. Production of RGB Macropad will begin directly when the factory re-opens on February 19th (the New Year holiday in China is longer), after which modules will ship to our factory in Taiwan to be packaged and then to our warehouse to ship as part of laptop orders.

One other update we’d like to share is the deeper research we’ve done on feedback a few press reviewers had on keyboard deflection. We performed additional measurements on multiple units and found that there is some unit to unit variation, but that there is a greater range across the span of a keyboard in areas that could deflect more or less depending on the support structure below it. The target we’ve set is under 0.6mm of deflection when pressed with 400 grams of force, which puts the keyboard on par with the behavior on Framework Laptop 13. You can see a measurement below on one system with the keyboard aligned to the left, with some keys exceeding the 0.6mm limit:

The improvement on this that we’re currently testing is a set of five additional rubber pads in the locations marked in red in the image below. Our initial testing shows that with these in place, regardless of keyboard position, deflection is below the 0.6mm limit with 400 grams of force. Once we can validate that this is the best solution, we’ll roll it into production and ship rubber pad kits to those with existing Framework Laptop 16 units who are interested in receiving it. We’ll share a request form when this is ready.

We’re happy to share that we started our mass production ramp of Framework Laptop 16 this week. We received quantities of the final CPU heatsink (after a brief pause sitting in Taiwan Customs), which was the last gating item for getting the manufacturing line moving. Lunar New Year means that both our factory and our fulfillment warehouse will be closed from Feb 8th through Feb 14th, so we’re working on producing and fulfilling as many units as we can ahead of that. For those of you in Batch 1, we’re also sending out the Batch 1 preparation email tomorrow. We’ll be sequencing through the remaining batches as quickly as we can. We’ll continue on additional update emails to keep each of you who have pending pre-orders up to date on production, though we may not stick to the two week email cadence now that we’re up and running.

You’ve probably also seen press reviews go live earlier this week. We flagged in the last email that press units came from an earlier build with some issues that we’ve since fixed. We wanted to share the full set of changes and improvements we’ve made for all customer units for your reference:

1. High frequency noise from Mainboard - We identified an incorrect capacitor value that results in a high pitched noise during high load while using a 28V or 36V power adapter. This is resolved on customer units.
2. Buzzing noise from Graphics Module - We identified a scenario where the inductors on the Graphics Module can buzz under high variations in load. We’ve updated the Graphics Module inductor assembly on customer units to resolve this.
3. CPU thermal module performance - Our thermal module supplier improved their vapor chamber soldering process, which reduced thermal resistance. While this was only intended to improve manufacturing yield, it actually ended up improving thermal performance too. All press units passed the same pass/fail criteria that we use for CPU performance on customer units though, so we consider press unit CPU benchmarking to be a fair representation of what customers will receive.
4. Liquid metal barrier adjustments - We made some adjustments to the liquid metal application process to prevent any leakage risk on customer units.
5. Cold GPU performance - For GPU benchmarks, on a cold first run the scores may have been lower than subsequent warm runs. We resolved this through a BIOS update that we provided to reviewers partway through the review cycle. Some reviewers may have benchmarked ahead of that time. We know that LTT was on the newer BIOS in their benchmarking.
6. DPC_Watchdog_Violation blue screen - There was a system stability issue that occurred primarily when scrolling the touchpad that could result in a blue screen. This was an issue that The Verge ran into, and we’ve since resolved it in the BIOS that is on customer systems.
7. Speaker attenuated on left or right channel - There was a bug in the smart amp DSP driver in which the left or right channel may be attenuated at certain times. We saw a reviewer specifically call out that audio sounded shifted. We found the root cause of this and resolved it in the driver on customer systems.
8. Touchpad Module sliding friction - The mechanical structure that the Touchpad Module slides into is slightly deformed on some press units, resulting in higher sliding friction. This is resolved on customer systems.
9. Display alignment - On some press units, the display was slightly misaligned in a way that resulted in the bezel covering the edge of the active area. We bypassed screening for this during press unit manufacturing, but are checking for this during production of all customer units.
10. Display color gamut - In the Windows OS image that was on press units, we did not have the color profile necessary for wide color gamut. We have since added this in the Driver Bundle. Note that the initial batches of pre-built systems also have a Windows image that will not have the color profile pre-loaded, but installing the Driver Bundle loads it.
11. Minor fit and finish in the Input Modules - There are some mechanical refinements in customer systems that improve the alignment of the pins in the Mid Plate to the holes in the Input Modules, as well as reduce visible gaps along the top edges of Spacer Modules. There are also minor improvements in the flatness of the Touchpad Module and Touchpad Spacers in customer systems. 

There are also a few issues that we are still tracking, but which we aren’t holding production for: 

1. Keyboard deflection - We’ve seen largely positive feedback on the input deck feel, but also specifically saw LTT’s video in which they flagged keyboard deflection and the workaround they applied. We’re investigating whether there could have been either an issue on that unit or a scenario that can result in the mid plate not being flat. In either case, if we find that there is an improvement we can apply on this, we will do so and ship out any parts necessary for that to customers whose units have already shipped.
2. Secondary SSD may disappear - We found that the secondary SSD (the M.2 2230 SSD) may not be visible on some boots or may rarely disappear during sleep. We’ve debugged this issue with AMD, who have traced it back to a bug in the platform firmware. They are releasing the fix to us, which we will include in a BIOS update. We’ll share BIOS updaters for Windows and Linux when this is ready, as well as roll the BIOS into the factory for new system production.
3. Display frozen after smart MUX switching - We’ve seen instances where after closing a graphics-heavy application, the display will freeze as the display switches from the discrete GPU to integrated graphics on the APU. AMD has root caused this issue, and is preparing a driver update that resolves it. We believe there are reviewers who have also seen this issue, potentially including The Verge. Once AMD provides us the driver, we’ll package it up as part of a Driver Bundle.

We’ll keep you up to date as we go.

Again, the best part first:

We’re happy to share that we’ve started mass production manufacturing this week, with the first units leaving the factory before the end of January. These will go directly to our fulfillment warehouse in Taiwan and then out to Batch 1 customers. Pre-orders are still open, and we expect to fulfill all current batches before the end of the first half of this year.

Full email below:

The first press reviews of Framework Laptop 16 are now live. Check out some of the early feedback:

"Framework 16 truly feels like someone brought my personal hardware wishlist to reality. I’m not only impressed by the extreme modularity, but also the thought and care put into this premium feeling device."

– iFixit

"The other new party trick, the bespoke upgradeable removable AMD graphics card is so sick."

– Alex Clark, Linus Tech Tips

"Framework has built on top of something incredible and seems to be the only company that has managed to make modular laptops actually work."

– Joel Loynds, Dexerto

"I was blown away by the additional customizability available with this 16-inch laptop thanks to the larger form factor while the motherboard, I/O ports, and other upgradeable options with prior Framework Laptops remain available."

– Michael Larabel, Phoronix

"I was surprised to find that while this laptop looks big it feels surprisingly light in my hands."

– Alex Wawro, Tom’s Guide

This is the largest batch of review units we’ve ever shipped, and we expect more reviews to trickle in over the next week. For context on our press units, many companies ramp into production, manufacture a large quantity to fill retail channels, and cherry pick some golden units from that as review samples. For us, because we’re entirely direct to consumer, our ramp is extremely fast, and units go to customer hands immediately. That means to get press units out weeks ahead of time to provide a sufficiently long review period, we send out production-intent qualification units. The “intent” part of that is that these are usually functionally identical to what ships to consumers.

With Framework Laptop 16 though, the product is complex enough that we identified issues during manufacturing qualification that we’ve since fixed. Changes and improvements we’ve made on all customer systems include resolving some instances of audible electrical noise in the Mainboard and the Graphics Module, reducing sliding friction on the Touchpad Module, optimizing the thermal resistance of the CPU heatsink, making improvements to the liquid metal application process, fixing a couple of instances where a firmware bug could result in a blue screen on Windows, resolving an issue where the left or right speaker channel could be attenuated in Windows, improving the fan control algorithm on the Graphics Module, and a number of smaller fit and finish refinements related to the Bezel and Input Modules. In retrospect, we would have loved to get these improvements into the units we sent to reviewers, but it's most important that our customers have a system that works smoothly.

Framework Laptop 16 has the largest set of pre-orders we’ve ever had on a product, and we doubled our factory capacity in the second half of 2023 in preparation to work through this as quickly as possible. We’re happy to share that we’ve started mass production manufacturing this week, with the first units leaving the factory before the end of January. These will go directly to our fulfillment warehouse in Taiwan and then out to Batch 1 customers. Pre-orders are still open, and we expect to fulfill all current batches before the end of the first half of this year.

###Framework Laptop 16 resources Whether or not you’ve ordered a Framework Laptop 16, you can now also get your eyes on the setup guides and documentation around the product. We’ve launched a centralized resources page that has links out to all the information and tools you need. This includes beta web and desktop utilities for Windows and Linux for configuring Input Modules like the LED Matrix. We’re trying something new with our step-by-step Quick Start guides as well. Since many of the modular interfaces on Framework Laptop 16 are pretty novel (for example, the hot swappable input devices), the guides have short videos for each step alongside the written instructions. Let us know what you think!

Most important bit for those as eager to get their preorder as I am:

This means that if the final qualification process doesn’t uncover any issues, we’ll send the first “We’re preparing your batch” emails to Batch 1 customers in late January.

In our first four updates, we shared progress as we identified and closed engineering issues and manufactured our production qualification units of Framework Laptop 16. We’ve now shipped a large number of press units, for which reviews will start to appear later this month. Note that the issues we’re calling out below are ones that are present on press review units that are fixed on customer units. This means rather than cherry picking perfect units for press, we’ve ended up with some minor areas where you’ll see improvements beyond what reviewers have.

We’re happy to share that there are no new unresolved issues in this update. The main item gating the mass production schedule remains the CPU heatsink, which we have an update on below. Rather than doing a quick patch to get manufacturing yield above the threshold, Cooler Master spent the last two weeks overhauling their manufacturing process, building new test fixturing, and outputting validation samples. This means we have a complete solution to the original issue, but one which took a bit more time. We have the first production quantities of the final heatsink arriving at our laptop factory the week of January 22nd, and our goal is to output the first set of Batch 1 customer systems from the factory before the end of January, after which they will go to our warehouse to prepare for shipments.

This means that if the final qualification process doesn’t uncover any issues, we’ll send the first “We’re preparing your batch” emails to Batch 1 customers in late January.

New issues

No new unresolved issues!

In progress

1. Yield issues on CPU thermal system - We’ve split this into two line items to go deeper into each. First, on the CPU heatsink, Cooler Master was able to adjust their vapor chamber soldering process to resolve the yield issue, and actually improved the thermal performance overall as a result. They also developed a new production test fixture to screen each manufactured module more thoroughly to ensure it meets the quality spec before shipping out. To vet all of this, Cooler Master is now preparing a small batch of heatsinks using the final mass production manufacturing and test process. These will be completed on 1/12, and to accelerate the system-level test schedule, will be hand carried from Cooler Master’s factory outside Shanghai to our laptop factory in Taoyuan. At that point, we’ll build them into a small number of production qualification laptops to ensure they also pass our system level manufacturing tests. To further pull in the schedule, rather than waiting for the results of the system tests, we’re “risk buying” enough heatsinks to cover Batch 1 and part of Batch 2. This means that Cooler Master is going directly into mass production, with us accepting and taking liability for the risk that we find an issue with the material during the system-level tests. This might sound frightening, but it’s a relatively common scenario in manufacturing, and appropriately balancing risks is a core responsibility of our Supply Chain Team!
2. Liquid metal installation - In parallel to the CPU heatsink qualification, we’re qualifying the final recipe for liquid metal thermal pad and containment barrier installation. We’ve iterated on several configurations and put them through some extreme torture tests. For example, we ran Prime95 on units sitting in six orientations on a vibration table for three hours, we put systems through high-G shock while running Prime95, and we are running an extended period of thermal cycling. All of this is to build confidence that the final configuration is robust to handling and aging. All of this is set to intercept the heatsink schedule.

Resolved issues

1. Tuning capacitor noise - We found and resolved one additional scenario that could result in a high pitch noise coming from the Mainboard when using >20V power adapters.
2. Touchpad row sliding friction - We found and resolved a material quality issue that could result in excess friction in sliding the Touchpad Module and Touchpad Spacers on and off.

In our first update email, we gave a quick overview of where we are on starting Framework Laptop 16 manufacturing and a list of open issues. There are still a handful of firmware items that are open and module production dates that are pending for full system production. However, we’ve made excellent progress in the last two weeks, and we’re happy to share that Mainboard mass production has started! This means the first set of final Mainboards are flowing down the manufacturing line this week at our factory in Taiwan. We’ll run them through the normal testing procedures and hold them while we prepare for full system manufacturing.

We’re eager to close out the rest of the opens, build the first units, and get them out to you all. We have a list of the remaining open items below, along with the issues from the last update that are now resolved.

New issues

1. High pitched airflow noise in the Graphics Module fan - We identified an airflow path in the Graphics Module fan that could result in a high pitch noise. This is another issue that was resolved in DVT2, but we found a regression in it during pre-mass production sample checking. Our supplier was able to resolve the issue with an adjustment to one of the internal mechanical parts in the fan that guides the airflow path. We’re now determining whether there is any impact to the schedule from needing to adjust tooling and rework already produced fans, but we don’t expect this to be the long pole in the schedule.

In progress

1. The fans have a small chirping noise on startup - Our fan supplier was able to root cause the issue and revise the fan to remove the chirping noise. The initial production schedule for updated fans is currently the longest pole for our system production schedule, so we’re working closely with the supplier to find ways to shorten it.
2. Power tuning during heavy loading - Our graphics card provider was able to revise the card and is proceeding into production on it. Even though the issue is resolved, we’re tracking it as “in progress” since Graphics Module manufacturing is one of the longer pole items on our production schedule. We’re also continuing to tune firmware to maximize performance across different power scenarios (on full battery, on low battery, on a 100W adapter, on a 180W adapter, on a 240W adapter, etc)
3. Graphics Module compatibility issues in Linux - We’re still working closely with the team at AMD to debug Linux compatibility issues on the Graphics Module. Our current assumption is that VBIOS firmware needs to be modified. Linux compatibility is extremely important, and we’re committed to making sure it is smooth before launch.
4. USB-PD firmware is in the process of completion - With the Framework Laptop 16 being the first product on the market supporting 180W and 240W USB-C along with a complex scheme for handling Expansion Cards, our USB-PD firmware is complicated. Implementation is nearly complete, and we also want to ensure we do sufficient testing before our target 12/8 mass production internal firmware release.
5. LED Matrix module schedule is trending late - We’re working with the supplier to pull in their schedule to meet launch timing, but it is still trending late.

Resolved issues

1. Cosmetic issues on aluminum forming parts using high recycled material content - We’ve completed process tuning and set cosmetic criteria that gives good results without resulting in excessive yield loss for production. In parallel, we’re working with the aluminum parts supplier on an improved source for post-consumer recycled material to use in the long run.
2. Our Numpad vendor used out of spec resistors - Our supplier was able to build new interface boards with the correct resistors, and their overall module production is on schedule.
3. Tuning capacitor noise - Our supplier was able to switch some capacitors to low noise variants and adjust the slew rate on some power rails, which substantially reduced noise.
4. Expansion Bay Interposer manufacturing yields - The interposer manufacturer was able to tune the tooling and assembly process on the custom connector, and yields are at the level required for production. The timing of production quantities is currently on track to meet our system production. We’re really excited about this connector, and will be sharing more detail in an upcoming blog post on how it enables GPU modularity.
5. Late display firmware update - We were able to roll out a new EDID into panel production that enables DCI-P3 correctly, and panel deliveries are on track for system production.

Slightly confusing, and not necessarily directly piracy-related. I run OpenVPN on my Netgear router that allows me to connect to devices on my home network while I am away from home. It works great for most devices, but I cannot connect to any devices that are running Mullvad VPN. Disabling Mullvad on those devices allows me to connect. Also, if I SSH into a device that does not run Mullvad, I can use that SSH session to then communicate with those Mullvad devices. Any ideas?