@Kieran_Levin and I have been working on it, but we got a bit more swamped/behind than we anticipated this week. We will make a quick post here as soon as it’s available, we appreciate your patience as I know quite a few have been waiting for this.
2 Likes
Tested on a 1165G7 without issue
1 Like
@iaredavid interesting finding, I guess we may have attempted to load the eGPU option rom and display video via the eGPU during the firmware update. We will suggest to unplug any eGPU devices during the update.
2 Likes
Intel Smart Sound is causing issues for me when I use external USB speakers (Yamaha THR II, actually a guitar amp).
When the device is plugged in, trying to start any app that uses sound either has a massive delay or just crashes / gives “not responding”. This includes the Sounds control panel, Sounds settings window, Spotify, or just clicking the volume icon in the taskbar.
I was able to resolve this by manually uninstalling Smart Sound via Device Manager.
1 Like
The Beta Driver bundle only nets 39 minutes of sleep before hibernating due to the following ‘problem’ device:
Intel(R) Smart Sound Technology (Intel(R) SST) Audio Controller (\_SB.PC00.HDAS)
EDIT:
Re-running the driver update bundle seems to have solved this, and now sleep power draw is much lower.
Hey everyone, we wanted to give you a quick update.
We have been reviewing and working to debug the issues noted in this thread before we push any further updates (thanks for all the reports again!). With that said, the Linux beta is taking a bit longer, but as soon as we have more information we will post again here!
7 Likes
If you are taking suggestions for future BIOS revisions, I’d love to be able to specify the USB-A as a boot priority whenever something is plugged into it by default.
2 Likes
If you are talking about USB-A vs something in USB-C modules, I think the operating system is clueless about the difference as both types are passed through USB-C.
1 Like
I was thinking of being able to specify a boot priority of modules in the BIOS pre-OS. Maybe being able to give preference to a specific idVendor/idProduct.
While installing multiple OSes (from the 250gb modules as opposed to the nvme), it would sometimes make the plugged in Ventoy USB-A no longer the default boot device requiring you to change the boot order. Ideally, the 250gb modules would be treated like drives and the open USB-A/C would be treated like temporary drives. While it’s just an inconvenience, it would be nice to specify that “temporary” drives take precedence over “permanent” drives.
4 Likes
Do you have any details on the hold ups that remain or a rough ETA? I appreciate you guys keeping up communication about this. It’s always a nice surprise when linux ins’t completely ignored
5 Likes
@malachid try going into the bios menu and go to Boot-> New Boot Device Priority.
I think if you change it to Last, it will boot from the last attached device as the first priority.
2 Likes
I’ll try that. I wasn’t clear on what First/Last were supposed to indicate. During the testing I had tried both options, but the list didn’t seem to change. Probably should have tried rebooting after changing that rather than looking at the boot order list.
1 Like
I have been swapping NVMe’s between a win10 install (fully up to date) and a Linux install (Slackware-current). I updated the bios with the windows NVMe and it went smoothly, took about a minute after EFI flash (32GB RAM, non-vPro i7). I still have occasional bugs, but they are not performance related. One was, if i plugin different USB-C power adapters, I’ve once had the screen blank and the fingerprint reader light go out and things went non-responsive. then after un-plugging then re-plugging the USB-C power adapter (not the frame.work one, but an 80 watt I usually use on another laptop) the screen and square light came back on. I was then able to wake the screen and login. The system hadn’t gone to sleep it didn’t look like. I once had a similar thing happen (pre UEFI update) when I plugged in a USBC 3.1 NVMe drive caddy. At the time the laptop was on battery power so I assumed it drew too much power. I tried again after connecting the charger and it was fine. Each only happened once. If i can find a way to reproduce, i’ll post steps. I’m very happy with the laptop so far. Keyboard, screen resolution and auto-disabling the touchpad while typing in linux are all excellent.
1 Like
By the way, Frame.Work team, Intel Driver’s Update utility has found that Intel XE GPU, BT and WiFi drivers from the Aug 31/2021 bundle are outdated and offered to update all three. So far I’ve spent one day testing all 3-- everything works smoothly. What is important, the XE GPU from Sep 7 from Intel is faster than this beta-bundled version ~7% in both 3d games and Machine Learning( OpenVino). Also, I have to admit that new BT driver has resolved the tiny issue I had when some BT headsets had interference with BT mouse( sometimes mouse cursor was freezing when playing sound, sometimes sound was clicking when mouse moves). Although, I can’t see any WiFi driver changes/improvements, it’s stable and works like a charm.
Long story short guys, I believe you definitely need to upgrade your bundle with the latest drivers. Yours are already outdated.
2 Likes
Here’s the thing with drivers. It isn’t as simple as, Company X (in this case Intel), updated their drivers, toss the new one in the bundle!
Once a company releases a new driver there is a very long, intensive amount of testing that a company has to go through to validate that the driver will work with their hardware and not break anything or cause any conflicts with other drivers or devices. Intel releases a generic driver that they say works. The key here is generic. They don’t promise that it will work with everything on the market. That’s up to companies like Framework, HP, Dell, Lenovo, etc. to do their own validation to make sure that the drivers work properly on their systems.
TL;DR - drivers take a lot of validation work to ensure they don’t break anything. Intel doesn’t validate for companies. This takes a long time.
3 Likes
I have a sneaking suspicion, that my woes about the power adapter, or what I thought might be the bios, is related to the magnetic sensor. I have had this happen a few times now, and it is always when I’ve had my laptop on another laptop, that I just checked, and yes, it has a magnet in it as well. Not sure if there is any other cause, but so far, it appears this is an issue with the frame.work thinking I’ve closed the lid. Interesting though, I’ve found when it thinks the lid is closed (or at least when its positioned just right over my other laptop) the keyboard is shut off, the light from the power button goes out, but the touch-pad still functions. Its an interesting “failure” mode. Well, not failure. Sharing in case people have similar situations. So far i’ve seen, headphones in my friends pocket lock the screen, other laptops, and having a magnetic tool on my desk. I feel better knowing i’m not losing my mind. 
5 Likes
So, how’s the linux version going?
9 Likes
I must say that without upgrade to 3.03 I couldn’t turn on the laptop if it wasn’t connected to a charger.
Do I have to try to make a windows to go usb drive or something? I have a win10 pro license but no windows partition. On this machine I was hoping to finally not actually need to carve out hundreds of gigs of my hd just to boot into windows once every 2 years to install a firmware update. I was hoping to only use windows from a vm on odd occasions, and have the option to move the whole vm off to an external drive when not needed 90% of the time.
If the linux bios installer isn’t going to be forthcoming any time soon, can there at least be some kind of stand-alone bootable image? In the old days, I could take dos firmware updaters and just pop them onto a freedos bootable usb stick in 2 seconds, boot, run, done.
If firmware updaters must be Windows apps these days, can they at least possibly maybe run from ReactOS so that there can be a legally redistributable fully self-contained bootable image, or at least directions?
I used to also make bootale “BartPE” disks, an earlier version of windows-on-a-bootable-cd but that required using actual windows files which are not legal to redistribute. But it worked to run firmware updaters and malware scanners etc.
… I’m going to see if I can get ReactOS to work just out of curiosity. It’s unlikely to be solid enough, but I think it would be awesome if it could work so it’s worth trying.
2 Likes