4 ms·
Haven't tried BT on my machine. It looks the drives were loaded correctly and there were no errors or warnings. But that shouldn't be really a big issue as the
by mrjin 2y ago
Haven't tried BT on my machine. It looks the drives were loaded correctly and there were no errors or warnings. But that shouldn't be really a big issue as the WIFI/BT on my machine is a Intel AX210, which is easy to obtain. I guess you can simply get one if your machine has a slot for it. I don't really have a T520, so cannot really tell if there were any other issues. To be sure what was the problem, you will need to read the error msg. Sometimes the error msg you see might not be the root cause. And also, you did not have hardware issue before does not mean you don't have a hardware issue now...
- criddell 2y agoI've bounced back and forth between Fedora and Windows a few times in the past month. Windows has no reboot or BT problems. The machine has previously had Ubuntu on it, but that was a few years ago. Ubuntu didn't have any problems so either it's Fedora-specific or kernel or driver changes since then are the root cause.
- mrjin 2y agoIt's most likely a driver issue. It depends on the nature of the issue. It can be as easy as turning some optional/3rd part repos on or as hard as debugging and fix in source code. I've done enough the later, and thus would simply steer away from that route. Intel cards seems to be supported pretty well. But it depends on the distribution. Last week I actually bounced between 3 distributions: Open Suse Leap, Debian and Fedora. OpenSuse failed to boot after installation, Debian lost all network config after finished installation and rebooted.