Hello everyone,
Until now, the wifi tether worked. However, after the upgrade I did last night, it stopped working.
I have tried to reboot but no luck.
$ cat /proc/device-tree/model
Raspberry Pi 3 Model B Rev 1.2
$ sudo connmanctl technologies
/net/connman/technology/bluetooth
Name = Bluetooth
Type = bluetooth
Powered = False
Connected = False
Tethering = False
/net/connman/technology/ethernet
Name = Wired
Type = ethernet
Powered = True
Connected = True
Tethering = False
/net/connman/technology/wifi
Name = WiFi
Type = wifi
Powered = False
Connected = False
Tethering = False
TetheringIdentifier = something
TetheringPassphrase = <removed>
$ sudo connmanctl enable wifi
Enabled wifi
$ sudo connmanctl tether wifi on
Error enabling wifi tethering: Not supported
I see no obvious errors in the journal for connman.service but there are some with wpa_supplicant. Especially the Failed to start AP functionality worries me:
$ sudo journalctl -b --unit wpa_supplicant.service
-- Logs begin at Thu 2016-11-03 18:16:42 CET, end at Wed 2019-11-13 18:51:16 CET. --
Nov 13 11:02:59 rasposmc systemd[1]: Starting WPA supplicant...
Nov 13 11:02:59 rasposmc wpa_supplicant[414]: Successfully initialized wpa_supplicant
Nov 13 11:02:59 rasposmc systemd[1]: Started WPA supplicant.
Nov 13 11:02:59 rasposmc wpa_supplicant[414]: WPS: Converting push_button to virtual_push_button for WPS 2.0 compliance
Nov 13 11:03:00 rasposmc wpa_supplicant[414]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
Nov 13 11:03:00 rasposmc wpa_supplicant[414]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Nov 13 11:03:00 rasposmc wpa_supplicant[414]: WPS: Converting push_button to virtual_push_button for WPS 2.0 compliance
Nov 13 11:03:00 rasposmc wpa_supplicant[414]: wlan0: Failed to start AP functionality
Nov 13 14:30:22 rasposmc wpa_supplicant[414]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
Nov 13 14:30:22 rasposmc wpa_supplicant[414]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Nov 13 18:18:24 rasposmc wpa_supplicant[414]: WPS: Converting push_button to virtual_push_button for WPS 2.0 compliance
Nov 13 18:18:37 rasposmc wpa_supplicant[414]: wlan0: Failed to initiate sched scan
Nov 13 18:19:04 rasposmc wpa_supplicant[414]: wlan0: Failed to initiate sched scan
Nov 13 18:20:25 rasposmc wpa_supplicant[414]: wlan0: Failed to initiate sched scan
Nov 13 18:24:28 rasposmc wpa_supplicant[414]: wlan0: Failed to initiate sched scan
Nov 13 18:29:28 rasposmc wpa_supplicant[414]: wlan0: Failed to initiate sched scan
Nov 13 18:30:17 rasposmc wpa_supplicant[414]: nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
Nov 13 18:30:18 rasposmc wpa_supplicant[414]: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
Nov 13 18:49:44 rasposmc wpa_supplicant[414]: WPS: Converting push_button to virtual_push_button for WPS 2.0 compliance
Nov 13 18:49:57 rasposmc wpa_supplicant[414]: wlan0: Failed to initiate sched scan
Nov 13 18:50:24 rasposmc wpa_supplicant[414]: wlan0: Failed to initiate sched scan
From the apt-get logs, it doesn’t seem that either the wpa_supplicant nor the connman package got upgraded.
What could be wrong ?
Unfortunately the driver in the new kernel does not appear to have tethering support. The only way to get that working at the moment is to downgrade.
@darwindesign Thanks for the reply.
I have been looking at downgrading the kernel, being new to this on debian so please bear with me 
.
I see that two kernel versions are still on the system:
- 4.14.78-4-osmc
- 4.19.55-6-osmc
After some googling, I tried
$ sudo apt-get install --reinstall rbp2-image-4.14.78-4-osmc
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reinstallation of rbp2-image-4.14.78-4-osmc is not possible, it cannot be downloaded.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Removing the new kernel gives the following, which seems to want to remove too much:
$ sudo apt-get remove rbp2-image-4.19.55-6-osmc
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
rbp2-device-osmc rbp2-image-4.19.55-6-osmc rbp2-kernel-osmc
0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
After this operation, 70.6 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
What’s the best way to downgrade ?
Alternatively, how could I ensure to have the old kernel boot and fix the kernel package to not be upgraded until a fix is out ?
It’s not good to remove the current kernel. Good decision.
Try this one:
sudo dpkg-reconfigure rbp2-image-4.14.78-4-osmc
then reboot.
$ sudo dpkg-reconfigure rbp2-image-4.14.78-4-osmc
Running depmod.
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.14.78-4-osmc /boot/vmlinuz-4.14.78-4-osmc
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal-osmc 4.14.78-4-osmc /boot/vmlinuz-4.14.78-4-osmc
run-parts: executing /etc/kernel/postinst.d/inform-updater 4.14.78-4-osmc /boot/vmlinuz-4.14.78-4-osmc
run-parts: executing /etc/kernel/postinst.d/process-vmlinuz-rbp 4.14.78-4-osmc /boot/vmlinuz-4.14.78-4-osmc
Going for a reboot now 
Hurray. Got kernel 4.14.78-4-osmc after upgrade and the wifi tethering works again 
.
Would it be a good idea to do sudo apt-mark hold rbp2-image-4.14.78-4-osmc to keep this version around until the driver is fixed ? Secondly, how would I know it’s fixed (except by trial and error) ?
1 Like
The only time any system updates install is if you agree to the command prompt that comes up in Kodi. You can set the frequency to check for updates to ‘never’ in the MyOSMC app. Kodi add-ons will still update though as that is a seperate system. As far as to when this may be fixed I think that would be a raspberry pi foundation question as it is their driver being used.
Thanks @darwindesign and @dillthedog.
I will head over to the RPi foundation to check with them.
1 Like
The same happened to me yesterday, good to see a solution here. Can you point me to the topic you are having with RPi foundation if it is a forum there too?
Please come back to us once you hear back with more info, thanks
Hello,
I have the same problem. I use a Rpi3 and I cannot activate tethering anymore.
I am on kernel 4.19.55-6-osmc.
I tried to do a sudo dpkg-reconfigure rbp2-image-4.14.78-4-osm but I get the following:
sudo dpkg-reconfigure rbp2-image-4.14.78-4-osmc
dpkg-query: package ‘rbp2-image-4.14.78-4-osmc’ is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
/usr/sbin/dpkg-reconfigure: rbp2-image-4.14.78-4-osmc is not installed
Since it was a clean install, is it possible that I don’t have the old kernel present? If this is the case, how can I roll back? Is rolling back the only option still?
You can do a clean install of an older version which is available on the download page.
Hey! Thanks for the quick answer!
Is it possible to just doiwnload the kernel from an older version and roll back? I’ve already spent some time configuring the whole thing.
The My OSMC add-on has a backup function for Kodi specific settings and userdata that could be used to transfer to a new install.
Hi guys,
Any news on this topic. Is the WiFi tethering working on the newest kernel?
Thx and stay healthy