We appreciate the contributions many of you have been able to make towards repairing the storm damage and keeping a roof over our heads. With your help we’ve been able to complete much of the critical work. There is still work to be done to secure the house and your continued support will be a huge help.
Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.
@blackwinnayoshi I see there are Intel Smart Sound Technology drivers in the list and was wondering if you had any problems with the SST Detection Verification driver from Intel? The one that is installed with the Intel(R) UHD Graphics 620 on my laptop causes my device to glitch on boot-up (confetti static then freeze) it happens with all the Linux Distros too. Microsoft actually included a downloaded driver that fixes it in Windows 11 This is the driver that does the glitching and is installed with SDIO as well as the current Intel Drivers Installer.
@blackwinnayoshi I see there are Intel Smart Sound Technology drivers in the list and was wondering if you had any problems with the SST Detection Verification driver from Intel?
I don't think so, everything seems fine.
77 additional drivers, most of them from a Samsung Galaxy Book 1 Go:
Thanks! they'll be in next week's update.77 additional drivers, most of them from a Samsung Galaxy Book 1 Go:
Squeezing in a further 22 drivers before the update. Of those, 17 are newer versions of ones that were in the previous attachments, 2 were ones I couldn't fit into the previous attachment's 20MB limit, 1 is an ARM64-specific version of ASIX's network driver, and 2 are from an Apple Boot Camp MSI.
@dandelionsprout so how does something like SDIO cope with installing drivers on arm architecture?
Using a Samsung Galaxy Book Go 1 as my test device for ARM64 (and to some extent ARM32) stuff, it clearly struggles when it comes to SDIO. The few (Around 2-6) drivers that show up as updatable on it in SDIO 2.0.4, end up with Error 103 installation failure when trying to update them. Presumably this means the error-affected drivers are x64-only, but I lack full confirmation of it at the moment.
@dandelionsprout DolbyAPO SWC Device_3.31001.1011.0 seems to be missing a file: DAX3API.exe
I seem to recall that's Windows saying it has the better driver already.Using a Samsung Galaxy Book Go 1 as my test device for ARM64 (and to some extent ARM32) stuff, it clearly struggles when it comes to SDIO. The few (Around 2-6) drivers that show up as updatable on it in SDIO 2.0.4, end up with Error 103 installation failure when trying to update them. Presumably this means the error-affected drivers are x64-only, but I lack full confirmation of it at the moment.
I saw some new arm drivers coming up this week so see if any are useful.
In regards to DAX3API.exe, I was previously of the belief that the .exe was just a bootstrapper of some kind and not a core component of the actual driver. I'll see if I can upload a corrected driver tomorrow (Sunday) at latest.
And here's one of even higher importance: The Qualcomm Adreno 618 iGPU driver. Despite my best efforts to compress it as hard as I could, I can only hope the upload system is okay with a 22.3 MB file.
Edit: Nevermind, the post system threw a "Filesize too big" error but decided to post the comment itself anyway.
@glenn Hello,
I suggest adding the UHD 630 driver to make it easier to install the driver for the CPU's integrated graphics.
Thanks
<a title="UHD 630 driver link" href=" removed link " target="_blank" rel="noopener"> removed link