Help : networks (wifi, bluetooth) keeps disconnecting after a few seconds


I’m new to this forum, please excuse if not on the right place. I’m not entirely new to Fedora, but I don’t understand much. I bought a new mini-PC (Geekom A5) recently and installed Fedora 39, alongside Windows 11 (that I may need for professional softwares). My main issue is about wifi and bluetooth.

I succeeded in connecting a bluetooth mouse, but the bluetooth keeps disconnecting and refuse to reconnect the mouse (most often, the bluetooth can’t find any device, or when it does it doesn’t accept to connect to the mouse). Same thing with wifi : I succeeded in connecting my wifi box, but then it keeps disconnecting and says it can’t find any wifi network.

I have 2 other issues that I don’t know if they can be related:

  • At every launch, Fedora warns the EFI only has 4,8 Mo free. I tried to resize it but it doesn’t work. The EFI partition currently has 105 Mo.
  • Also, the PC always launches Windows if I don’t enter the UEFI parameters to launch Fedora via “boot override”.

So: can someone help me understand why the networks keep disconnecting ? Thanks !

This is an AMD system. GeekOM “best mini PC compatible with Linux” only lists Intel models, so you may need to add different network hardware.

This has only 2 probes in the LHDB. One appears to have an extra 10ec:b852:1a3b:5470 PCIe network card shown as “working”. Both have IMC Networks USB bluetooth 13d3:3570 shown as “detected” but not “working” for the 2 Geekom probes.

Bluetooth in Linux has a history of weak support from some vendors, so I find it necessary to have a USB BT “dongle” for times when the linux support fails.

1 Like

Thanks, George. I don’t understand all the details, but what I gather from your message is that my computer’s components may not be working with Fedora so I may have to add an external bluetooth dongle. I thought every computer would run Linux, but it appears Iit’s not true for everything. I will inquire in that direction, thank you.

It depends on your definition of “run” – some people don’t even need keyboard, video, or mouse because they connect from a another system via network. Others don’t need working network. Linux has a different approach to power management from Windows, so there can be issues around wake and suspend, hibernation, etc.

The best low-cost linux systems are often 3 to 5-year-old “enterprise” grade models (often sold only in quantities over 1000) available from reputable dealers. After that much time, vendors have had time to provide robust linux drivers with feedback from users. The LHDB is a extremely helpful when considering a purchase, but requires some familiarity with the names of “buses” (the wiring and connectors used to transfer data: e.g., PCI, PCIe, USB, etc.) and how devices are identified.

For some popular low-cost models, individual users provide working drivers. The LHDB may have pointers to such drivers.

If you are shopping for a Bluetooth USB dongle, make sure the vendor a) says they support linux, and b) tell you which chipset they use. Some vendors will sell different USB dongles under the same model name. Again, the LHDB can be useful.

I’m very grateful for these explanations. I always need the “big picture” to understand anything, and it is difficult to find it as most people dive into technical details. You don’t give a simple solution to my network issue, but a path to a better understanding of Linux. Now I’ll be able to build a few more bricks of understanding. I explored a bit LHDB : difficult, but most useful.