[07:19] <xubuntu1w> After installing Xubuntu on Ubuntu 19.10 ARM64 bit (Rasberry Pi4B) all works fine but the WiFi. The wlan0 leases an address but there's no IP connectivity (e.g. cannot ping the router). All works fine from eth0. Anyone got any clues? Thanks.
[07:36] <tomreyn> you may need to create or edit /lib/firmware/brcm/brcmfmac43455-sdio.txt
[07:37] <tomreyn> it should say 0x44200100 from what i can find online
[07:37] <tomreyn> xubuntu1w: ^
[07:40] <tomreyn> https://wiki.ubuntu.com/ARM/RaspberryPi#WiFi
[08:42] <xubuntu87w> Brilliant tomreyz! Thank you. As per the link you posted, I applied the latest wifi driver setup rebooted and now WiFi IP connectivity works. Many thanks. :-)
[08:48] <tomreyn> :) you're welcome
[09:18] <xubuntu95w>  /nick SteveB
[12:12] <sherman> hi
[16:38] <Gusj> Hi there, I upgraded from Xubuntu 18.04 LTS to 19.04 and then to 19.10, now my wifi sometimes connects and sometimes not, I can see through commands that the wifi is on (i turn it on or off) but I don't see any of the servers around me including my own, like the list is not populated.. and the inverted triangle icon stays empty, If I reboot, then it might work
[17:05] <brainwash> Gusj: I would check if restarting the network manager service helps
[17:06] <diogenes_> Gusj, also the router.
[17:14] <Gusj> brainwash: Yes, thank you, I have tried, 'sudo service network-manager force-reload' and 'service network-manager restart' and it has no effect
[17:15] <Gusj> what works is just rebooting.. which is strange, I don't see how the router would be an issue since the other machines connect normally and even that machine connected normally in 18.04
[17:15] <brainwash> command should be "sudo systemctl restart network-manager"
[17:20] <Gusj> brainwash: Thank you, just did tried it to the same effect, I can see wifi is enabled, but I don't see any of the ssids around me, including mine, which is feet away from the laptop
[17:22] <sublevel> You could try:   sudo iwlist wlp3s0 scan      (replacing wlp3s0 with the name of your wifi interface)
[17:23] <sublevel> I used to use that as a workaround on lubuntu 16.04 when I had a similar issue
[17:26] <Gusj> sublevel: ahh thank you, the output is: wlp1s0   No scan results
[17:27] <sublevel> That sounds like a different problem then I'm afraid
[17:36] <lplpefefe> hi
[17:40] <Gusj> sublevel: I do no understand what that means? If I reboot it will probably connect,
[17:41] <Gusj> and since it did not happen with 18.04 i feel that it should be something specific in terms of narrowing down possible source for the prob
[17:42] <sublevel> All I know is that it would kick my wifi back into action and display lots of info about the scan results
[17:42] <sublevel> hi lplpefefe
[17:44] <lplpefefe> somehow this is the only channel I can access with hexchat and only through 94.125.182.252 If I try the regular way (chat.freenode.net) it cycles: * Looking up chat.freenode.net  * Unknown host. Maybe you misspelled it. Cycling to next server in freenode...
[17:44] <lplpefefe> but I am now connected and can browse, so...
[17:44] <lplpefefe> im on xubuntu 19.10, upgraded a week ago. The problem started after upgrading
[17:45] <lplpefefe> help appreciated
[17:46] <lplpefefe> irssi and webchat don't work either
[17:47] <sublevel> Can you connect to other irc networks OK?
[17:47] <lplpefefe> neither
[17:49] <sublevel> DNS issue?  Can you ping the domain name?
[17:53] <lplpefefe> am I doing this wrong? I executed ping www.chat.frenode.net
[17:53] <lplpefefe> ping: www.chat.frenode.net: Name or service not known
[17:54] <sublevel> Not sure why you're adding www. ,  try just ping chat.freenode.net
[17:55] <lplpefefe> lack of knowledge
[17:55] <lplpefefe> same result sublevel
[18:00] <sublevel> I don't know what to suggest to begin working out what the issue is, maybe someone else here has an idea.  Rebooting your modem/router and the computer itself probably worth a try if you haven't already
[18:00] <lplpefefe> the router?
[18:00] <lplpefefe> ok