RPI3 - WiFi stops working after rpi-update

[bigpino67]

Hello everyone

Everything works fine before i did one of the following :

Code: Select all

sudo apt-get update
sudo apt-get upgrade
sudo rpi-update

Now, I have not been able to make the WiFi works once again.

When the rpi is booting, i got the message : Failed to start Configure Bluetooth Modems connected by UART. When I see this error, WiFi is not working anymore. Also, when I run raspi-config, and the network options for wifi, I get the message "No wireless interface found". Usually, it happens when I've complete a fresh install on a externall HDD (not happening on sd card) and these lines had fix the problem :

Code: Select all

sudo apt-get install raspberrypi-sys-mods
sudo apt-get install --reinstall pi-bluetooth
sudo reboot

But they don't solve the problem I have right now.

Please, help me!

[fruitoftheloom]

Hello everyone

Everything works fine before i did one of the following :

Code: Select all

sudo apt-get update
sudo apt-get upgrade
sudo rpi-update

Now, I have not been able to make the WiFi works once again.

When the rpi is booting, i got the message : Failed to start Configure Bluetooth Modems connected by UART. When I see this error, WiFi is not working anymore. Also, when I run raspi-config, and the network options for wifi, I get the message "No wireless interface found". Usually, it happens when I've complete a fresh install on a externall HDD (not happening on sd card) and these lines had fix the problem :

Code: Select all

sudo apt-get install raspberrypi-sys-mods
sudo apt-get install --reinstall pi-bluetooth
sudo reboot

But they don't solve the problem I have right now.

Please, help me!

rpi-update is not recommended as installs a testing kernel / firmware:

https://www.raspberrypi.org/documentati ... i-software

[bensimmo]

Don't use rpi-update unless you need to, what part are you testing?
hopefully people building thoose testing parts will be along to help.

Try

Code: Select all

sudo apt install --reinstall raspberrypi-bootloader raspberrypi-kernel

To go back.

[bigpino67]

Is there a way to get back to the firmware dated near September 14th 2018, which is the date I 've install my system?

[bensimmo]

See my added edit above, it'll (should) go back to the most current stable version.

That from the updating documents on the site.
https://www.raspberrypi.org/documentati ... pdating.md

[bigpino67]

I still get the error even after running :

Code: Select all

sudo apt-get install --reinstall raspberrypi-bootloader raspberrypi-kernel

[bigpino67]

I've also run this :

Code: Select all

systemctl status hciuart.service

Result :

Code: Select all

● hciuart.service - Configure Bluetooth Modems connected by UART
   Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Fri 2018-12-07 17:32:07 UTC; 1min 40s ago
  Process: 303 ExecStart=/usr/bin/btuart (code=exited, status=1/FAILURE)

Dec 07 17:32:07 Rpi3-Domotique btuart[303]: Can't set line discipline: Invalid argument
Dec 07 17:32:07 Rpi3-Domotique btuart[303]: Can't initialize device: Invalid argument
Dec 07 17:32:07 Rpi3-Domotique btuart[303]: bcm43xx_init
Dec 07 17:32:07 Rpi3-Domotique btuart[303]: Flash firmware /lib/firmware/brcm/BCM43430A1.hcd
Dec 07 17:32:07 Rpi3-Domotique btuart[303]: Set BDADDR UART: b8:27:eb:f0:1f:80
Dec 07 17:32:07 Rpi3-Domotique btuart[303]: Set Controller UART speed to 921600 bit/s
Dec 07 17:32:07 Rpi3-Domotique systemd[1]: hciuart.service: Control process exited, code=exited status=1
Dec 07 17:32:07 Rpi3-Domotique systemd[1]: Failed to start Configure Bluetooth Modems connected by UART.
Dec 07 17:32:07 Rpi3-Domotique systemd[1]: hciuart.service: Unit entered failed state.
Dec 07 17:32:07 Rpi3-Domotique systemd[1]: hciuart.service: Failed with result 'exit-code'.

[DarkPlatinum]

Its probably best to save yourself a lot of time just rewriting an image. Just transfer you data files over in /home/pi.

[bigpino67]

I have a lot of work done on this system. All my smart home solutions run on this RPI.

Even if I start from a fresh install, i have to go through rpi-update again. What should I do?

[bensimmo]

what are you using that rpi-update gives you ?
but if you must
then after the
sudo apt full-upgrade
and if it works there take and backup image

or wait till the Techs spot this and know what may have gone wrong.
Maybe read github for reports on problems with the testing you are doing.

[bigpino67]

I am not testing anything special. It's in the procedure to install JeeDom. It's an application to smarten your house. I also have a z-wave dongle to communicate with my smart objects or bluetooth. I also need WiFi when i try to synchronize objects for the first time because the range is really short.

That's all i wanna do with my rpi3.

[bensimmo]

Get another SD card if you have one and start again, it may just be quicker.
If you ever see instructions to run rpi-update, don't.
You probably don't need to especially if the instructions are more than a few weeks old.
If it comes from here and they have a RP Trading/engineer tag and it is testing things out and is a recent post then give it a go.


I don't know how to fix it or debug the fix.
Perhaps they, JeeDom do.
It may just be quicker to start again and copy thing over.
If the error crops up again...

Is there anything on their forums, tickets or GitHub?

[bigpino67]

I've been able to rollback to an older version using rpi-update and the hash of a commit on github rpi firmware.

Now, my WiFi and Bluetooth works again!

GitHub Firmware : https://github.com/raspberrypi/firmware/commits/master

I've selected the commit of Oct 23, 2018 (kernel: Bump to 4.14.78 …). So I've run this command :

Code: Select all

sudo rpi-update 45c6ee3cd7f36a2376b691affbc02dfc689b8056

[bensimmo]

Excellent, now take a backup quick, lol.

[MrEngman]

I've been able to rollback to an older version using rpi-update and the hash of a commit on github rpi firmware.

Now, my WiFi and Bluetooth works again!

GitHub Firmware : https://github.com/raspberrypi/firmware/commits/master

I've selected the commit of Oct 23, 2018 (kernel: Bump to 4.14.78 …). So I've run this command :

Code: Select all

sudo rpi-update 45c6ee3cd7f36a2376b691affbc02dfc689b8056

Just checked the commit you used as you say you chose it from https://github.com/raspberrypi/firmware/commits/master and I'm really surprised that you appear to say it works. I can't think why it will as it is an invalid commit as far as rpi-update is concerned.

Running the command you say you used gives me an error

Code: Select all

sudo rpi-update 45c6ee3cd7f36a2376b691affbc02dfc689b8056
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** Performing self-update
 *** Relaunching after update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** Invalid hash given

The commits you should be using should be from https://github.com/Hexxeh/rpi-firmware/commits/master and to go back to kernel 4.14.78-v7+ #1156 as you appear to be doing the command should be

Code: Select all

sudo rpi-update 27ed1a386e52c24c9eb76b7dd7306a7016fb6669

[bigpino67]

Looks like we don't see the same informations :


https://github.com/raspberrypi/firmware ... fc689b8056

Code: Select all

kernel: Bump to 4.14.78  …

@popcornmix
popcornmix committed on 23 Oct
firmware: Move to driver based backlight
See: #1063

[MrEngman]

Looks like we don't see the same informations :


https://github.com/raspberrypi/firmware ... fc689b8056

Code: Select all

kernel: Bump to 4.14.78  …

@popcornmix
popcornmix committed on 23 Oct
firmware: Move to driver based backlight
See: #1063

I see the same info using that link and commit but as I said rpi-update uses the commits from https://github.com/Hexxeh/rpi-firmware

https://github.com/Hexxeh/rpi-firmware/ ... 7016fb6669 shows

Code: Select all

kernel: Bump to 4.14.78...
@popcornmix
popcornmix committed on 23 Oct

firmware: Move to driver based backlight
See: raspberrypi/firmware#1063

which is the same as the raspberrypi/firmware commit you use but the Hexxeh/rpi-firmware commits are configured to use rpi-update, unlike the raspberrypi/firmware commits.

And running the command you say you used and the one I use shows the following

Code: Select all

pi@Pi-0-d:~ $ sudo rpi-update 45c6ee3cd7f36a2376b691affbc02dfc689b8056
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** Performing self-update
 *** Relaunching after update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** Invalid hash given
pi@Pi-0-d:~ $ sudo rpi-update 27ed1a386e52c24c9eb76b7dd7306a7016fb6669
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** Performing self-update
 *** Relaunching after update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
#############################################################
This update bumps to rpi-4.14.y linux tree
Be aware there could be compatibility issues with some drivers
Discussion here:
https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=197689
##############################################################
 *** Downloading specific firmware revision (this will take a few minutes)

When using the command you use it gives an error while the one I use to revert to kernel 4.14.78 works.

[bigpino67]

It's weird but I can confirm you that did the trick too! I got the same display as yours and it starts to download.