Hi Frameworkers,

I’ve just updated my 11th-gen Intel Framework 13 to Windows 11 after fighting it for two and half hours. The normal error messages that are so vague they’re meaningless, having to run a downloadable installer as admin because Windows Update can’t manage it, freeing up an extra 25GB of disk space, and culling particular background processes before running the tool. I must learn about dual-booting Linux soon, arrrgh!

Now “successfully” running Win11 and running the Framework driver package installer - three times - I have no Bluetooth. This died first when completing Windows updates in preparation for the update, and then is still MIA.

The installer claims to have installed the Bluetooth driver but I can’t see it in device manager, add any devices or turn it on anywhere.

Help? :(

https://preview.redd.it/4by647c167zb1.png?width=437&format=png&auto=webp&s=6c815a694839e5652dcbf4c6b82a979c7fb2c5ac

https://preview.redd.it/zsd0k8b7y6zb1.png?width=937&format=png&auto=webp&s=f70c993d641cafcd56aa5e49620936c8e3a1e53f

  • chic_luke@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I had not really thought about that, but you’re right. The example holds throughout my experience. I use Linux daily nowdays, but I used to be a Windows power user.

    I can confidently claim Linux is easier to use than Windows. And I mean it seriously, I’m not trying to be controversial. It’s nowhere near as complex as Windows and structurally many things are easier, it has less abstraction, so, whereas it might require a bit of a learning curve in some places, when you’ve done it, you’re done because you fundamentally already know how it works. Also, while the GUIs are now slowly starting to get better and cover more of the experience, for the most part, Linux distros don’t make many attempts to hide the underlying workings to the end user, and documentation is provided for anything, so if you’re curious to know how anything works, you can just read up on it and get a decent grasp.

    Windows tries to hide how it works from the user, and that is what causes it to be so hard to debug. When something breaks on Linux, after a few years of experience and a “clinical eye”, I can pretty much always accurately guess where in the stack the disruption has happened. Maybe it takes 2 or 3 takes to get it right, but at the end of the day, I have a honest grasp of how a modern Linux system is put together and I can get my hands dirty. On Windows it’s… not that simple. I feel like I am talking multiple shots in the dark and just guessing semi randomly hoping that the next attempt will fix it instead of leaving my system in an even more broken state. Because the admin tools are there - regedit, powershell, event log, performance monitor, whatever you want - but it feels like doing surgery “blindfolded” in a way. Trusting what you read on some forum and hoping this long ass powershell command will do it.