Babbiorsetto

joined 8 months ago
[–] [email protected] 1 points 3 weeks ago (2 children)

You can just take it for what it is: How people respond when asked to grade their happiness from 1 to 10. Of course it's subjective, but it's interesting that arch users rate their happiness lower overall.

[–] [email protected] 24 points 3 months ago (6 children)

Fuck this. Fuck search engines. I'm going back to curated website lists.

[–] [email protected] 2 points 4 months ago (2 children)

It looks like there's no devices listed for that chipset yet. Assuming there were any, you would go to the device's page and check the table on the right for something like "probable linux drivers". If you want a plug and play experience you need to look for one where the drivers have been integrated into the kernel, and then make sure your system is using that kernel version or later. It's usually older devices whose drivers have been brought into the kernel, you won't find newer stuff that just works out of the box.

If you don't want to limit yourself to the ones with kernel drivers you'll usually be downloading the driver's source code from somewhere, then set up dkms to build and install them on every kernel update.

It's honestly not as bad as it sounds if you don't mind researching for a bit and running a couple commands.

Good luck

[–] [email protected] 8 points 4 months ago* (last edited 4 months ago) (8 children)

If you have a windows install USB lying around you could try to boot into that and run some commands to restore the EFI entry.

Source 1 Source 2 Source 3

These sources more or less describe the same steps to attempt recovery. The

[–] [email protected] 21 points 6 months ago

First thing that comes to mind is https://devdocs.io/about