![]() The main problem is that it seems that the Connman service is automatically running at boot and *disabling* the Wi-Fi radio using RF-kill!Īs long as the user never goes into the Connman UI to power on the Wi-Fi radio (where it stores the Wi-Fi power state), then the Connman service will disable the Wi-Fi radio at every boot, breaking other means of connecting to Wi-Fi, for instance, using "/etc/network/interfaces". "/etc/network/interfaces" gets populated with the user's Wi-Fi SSID and password that were inputted into the Debian installer, but that's not the main problem. However, if there happens to be a further problem with "/etc/network/interfaces", then the user may still not be able to connect, and won't have an obvious way in a GUI to rectify this. Without connman, the Wi-Fi adapter will stay enabled and will automatically connect based on the contents of "/etc/network/interfaces". That way, at least the Wi-Fi radio wouldn't get RF-killed at boot. TL DR: A workaround is to not ship Debian LXQt with connman/cmst. I tested a fresh net install of Debian with LXQt and was able to determine the cause. It's a good feature to have whatever WiFi that is configured in the installer carry over to work in the installed OS - but *not* if it silently breaks in subsequent boots, if the user has run connman, or whatever. I don't know what the best solution would be for the Debian installer. However, if you set managed=true, then NetworkManager *will* use interfaces defined in /etc/network/interfaces.īut the best advice I've read online says that people shouldn't generally just be setting managed=true. I believe this means that network-manager will, similar to connman, not manage network interfaces defined in /etc/network/interfaces. Maybe the "bug" is that the Debian 12 installer (I used the netinst disc) is populating our /etc/network/interfaces file with our WiFi interface & SSID configuration, and then the presence of that causes connman to not be able to manage it on subsequent boots?Īfter I learned of this, I started playing around with network-manager, plus nm-tray, as an alternative to connman, but I believe an entry in /etc/network/interfaces may *also* keep network-manager from connecting, so this isn't necessarily a bug in connman.īy default, network-manager's conf file (/etc/NetworkManager/nf) contains the setting: Connman and Gnome Network manager do not contradict each other? Can i remove Connman? Gnome NM seems more up to date. Still, i don't understand HOW such problem happened? I definitely didn't edit the interfaces file, neither did i enable DHCP or smth anywhere. I must mention here that before i had here Debian 11 XFCE and i had no such problems there. ![]() I can see in tray under the "Wi-fi networks" that "device not managed" I gave a try to network-manager-gnome - same. This situation is seen both in LXDE and LXQTĪt first i thought that the problem is in Connman, i have installed "network-manager" and tried to use nmtui. But when i switch to wireless services option all is empty. After restart i can't see any network connections, though wi-fi is working.Ĭonnman shows me that wi-fi is powered and on, green. Then i logged into LXQT, there i had to manually connect to wi-fi with Connman. I checked the Connman settings, it was complex, but still fine. I logged into LXDE, the internet is working out of the box, if i remember correctly, all seems fine. During the installation process the wi-fi network was found and laptop connected. I have installed it using Debian live DVD. Hello! I have recently installed Debian 12 with LXDE and LXQT on the one of my old machines.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |