| Milencho | Hey guys | 11:48 |
|---|---|---|
| Milencho | anyone who wants to help regarding wifi problems on 22.10 | 11:48 |
| Milencho | state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external | 11:48 |
| tomreyn | this message looks incomplete | 11:52 |
| Milencho | https://pastebin.com/uXqEhjKh | 11:53 |
| Milencho | this is from syslog removing/inserting the usb dongle | 11:53 |
| Milencho | anyone that have an idea how i can handle this without re-installing whole system | 11:55 |
| tomreyn | if i read this right then network manager is choosing not to manage this device because it seems to be managed by "something else" | 12:02 |
| tomreyn | there is also mention of the strongswan charon service accessing the device | 12:02 |
| SandyVujakovi[m] | I wonder why a VPN implementation would choose to manage hardware directly 🤔. | 12:44 |
| SandyVujakovi[m] | Assuming that this didn't find its way to your system by mistake, could you try temporarily disabling the VPN and seeing if that helps? Did you check if this sort of thing happens with the Ethernet controller as well? If it only happens with the USB WiFi dongle and only when the VPN is enabled, maybe it's some sort of hard-core security/privacy feature that ensures that you can only access the network through the VPN? | 12:44 |
| jeblad | Just upgraded to kinetic kudu beta, and it seems like there is a problem with the wifi driver (Broadcom 802.11 Linux STA from bcmwl-kernel-source) | 13:45 |
| jeblad | Could be that I've done something wrong, but it worked in 20.04 | 13:46 |
| jeblad | If wifi is enabled the screen freezes. I'm using X11. | 13:47 |
| SandyVujakovi[m] | Could you elaborate what the issue is? What kernel version did you have on 20.04? | 13:48 |
| jeblad | I don't know much more than the screen freezes and I can't interact with the system. Not sure what the kernel version was in 20.04, except it was updated. The filesystem is ZFS, so I should be able to dig out some info if necessary. | 13:51 |
| jeblad | Ah , kernel was 5.15.0-48-generic … | 13:52 |
| jeblad | WiFi is a BCM43b1 802.11 Hybrid Wireless Controller … (r587334) | 13:54 |
| jeblad | It seems like HID-devices on USB through dongles (Logitech Unifying and Bolt) stops working if the wireless card is enabled, in effect freezing the screen. | 13:58 |
| jeblad | Wired connection is a workaround, and it is enough to disable the wireless card in Settings | 14:01 |
| jeblad | The card is probably better known as a BCM4352 | 14:03 |
| SandyVujakovi[m] | Oh 👀 | 14:03 |
| jeblad | That doesn't sound good… =$ | 14:04 |
| SandyVujakovi[m] | No, I was just surprised that it messes with USB 😅. Could you go through the `dmesg` log and see if there's anything of note when enabling the WiFi? If you can't get the devices to register again and need to reboot after enabling WiFi, then you can see the log from the previous boot by running `journalctl --dmesg --boot=-1`. | 14:08 |
| SandyVujakovi[m] | Also, you should try installing an older version of the kernel if possible, ideally 5.15, to see if it's simply that the driver isn't ready for the new kernel version or if it's something else. | 14:11 |
| jeblad | I have some traces… Seems like NETDEV WATCHDOG: … transmit queue 0 timed out | 14:18 |
| jeblad | audit … apparmour="DENIED"… capname="net_admin" | 14:19 |
| jeblad | same for capname="perfmon" | 14:19 |
| jeblad | netdevice: wlp6s0: Incorrect netdev->dev_addr | 14:24 |
| jeblad | Last one is pretty early | 14:24 |
| Milencho | tomreyn, thanks for the help | 14:42 |
| Milencho | u said it's managed by something else - the wifi | 14:42 |
| Milencho | i've killed/deleted nework manager and it works | 14:43 |
| Milencho | now i've installed ersion 1.36.4 | 14:43 |
| Milencho | and it works like before, so hopefully they will fix it | 14:43 |
| tomreyn | jeblad: what prompted you to upgrade from 20.04 LTS to a pre-release version? | 17:09 |
| tomreyn | driver support for many broadcom wireless devices, such as yours, is sketchy / only possible through manually built modules for licensing reasons. | 17:11 |
| tomreyn | you'll better stay on LTS releases. 22.04 would have been a good upgrade target. | 17:12 |
| jeblad | Two identical machines, one for test/demo and one for development. Only real difference between them are the wifi card. | 17:14 |
| jeblad | There are a few bits'n'pieces that doesn't work properly in 20.04. I've been wondering whether I should skip Ubuntu for some time, but it seems I'm using it for a little longer. | 17:17 |
| Milencho | jeblad, i'm noobie but i will defenitely stop using non LTS versions | 17:43 |
| Milencho | even for home/desktop PC | 17:44 |
| jeblad | Using only LTS have drawbacks when you develop with libs that does not exist for those versions. Changing core libs, and then trying to make the system work is a pain. Using Vagrant and similar to make it work … well, it is possible but sometimes it is better to use bare metal. | 17:59 |
| jeblad | Ordered a new wifi card. :D | 18:15 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!