Wi-Fi in 5.30

Does anyone know how to double-check whether it’s a Wi-Fi-capable one or not?

I have an RPi3B that has no networking, the relevant chip may have failed. *SDIODevices and *SDIOSlots are the tests.

Two examples, good and broken

Does anyone know how to double-check whether it’s a Wi-Fi-capable one or not?

I have an RPi3B that has no networking, the relevant chip may have failed. *SDIODevices and *SDIOSlots are the tests.

If it’s not in the list of SDIO devices the chip’s toasted (it would appear regardless of whether any driver had tried to set it up).
If it does appear, load the WLanBWFM module and see what *WBWInfo reports – a Pi 3B should have a BCM43438 controller same as the ZeroW and Zero2W.

Some diagnostics from the RPi400 which fails to connect to WiFi and the RPi4B which is OK.
Different Interface controller??
Interface controller: BCM43456
Running time : 0d, 0h 3m 51s
Interface media : 802.11 channel 0, 0.0GHz, half duplex

The ROOL stand definitely had a Pi 400 on it with WiFi happily networked all day at the recent show. No idea what revision it was, it’s just whatever was in the show box, but David I see you say “rev 0”. I remember the torture of updating the Pi 400’s Micrel Ethernet PHY but that was a rev 1.0 versus rev 1.1 wasn’t it?

I remember the torture of updating the Pi 400’s Micrel Ethernet PHY

That was certainly coming to mind for me when I found that one Pi worked and the other didn’t, but it might indeed be something else.

If the chip truly has failed then that’s no big loss: I have the Wi-Fi HAT anyway (I tried physically disconnecting it just in case), and was just curious about whether I still needed it.

*sdiodevices
Bus Slt  RCA Fun  Description        Capacity     Vendor    Product Rev Date
  0   0  59B4  0  SDHC card          3839 Mbytes  JE        USD     1.0 2014-09
*sdioslots
Bus Slt  Voltage  Width  Frequency
  0   0   3.3 V   4-bit   50 MHz SDR
  1   0   3.3 V   4-bit   50 MHz SDR

However someone has reported that the ROOL WiFi can co-exist with the ROD stack

I’m happy to confirm that both can co-exist. As per David P.‘s instructions, I replaced ROOL’s !InetSetup by ROD’s one, and everything works fine now.

If you are updating your boot sequence at anytime then I would suggest uninstalling the ROD stack and also Pinboard 2 as well before doing so and then reinstalling afterwards as things can get really messed up.

This is certainly true for the ROD stack (see my former post), but I haven’t noticed any problem so far with Pinboard 2. Is there anything particular that I should look at?

Out of the box WiFi support

I’ve just built a fresh SD for a Pi3 with 5.30 HD4 / OS and the latest stable Pi firmware and the Network Interfaces looks the way it always has…“PPP” and “Ethernet over USB” being the only options. It doesn’t have “BCM43 WiFi” shown here

I don’t see any ROM Modules related to Wi-Fi, so am not sure how to get it to appear in the Interface list.

I know it works as my other SD has the ROD stack and that connects to Wi-Fi okay, as does Linux.

*SDIODevices shows:

0 0 59B4 0 SDHC card  ...
1 0 0001 1 SDIO non-standard function   Broadcom A9A6
1 0 0001 2 SDIO non-standard function   Broadcom A9A6

Do I have an unsupported/unique chipset?

but I haven’t noticed any problem so far with Pinboard 2. Is there anything particular that I should look at?

I found that updating the !Boot sequence to the latest build meant that the Pinboard configure application reverted tpo the ROOL one and thus I had to reinstall the ROD configuration application within the Boot sequence again as i got errors reported.

It might be others see something different but getting back to a standard as possible ROOL !Boot setup is in my opinion a safer base to progress from.

I’m happy to confirm that both can co-exist

I’m ahhpy to confirm the same.

I uninstalled the ROD stack , plus Pinboard 2, updated the disc image with the 5.30 one and the WiFi addon and made sure that it was all working and then tested the ROOL Wifi setup before reinstalling the ROD one.

Done a Pi4B, I’ll try a 3B I have later.

Well done to all involved.

I’ve just built a fresh SD for a Pi3 with 5.30 HD4 / OS and the latest stable Pi firmware and the Network Interfaces looks the way it always has…“PPP” and “Ethernet over USB” being the only options. It doesn’t have “BCM43 WiFi” shown here

Do you have the additional components installed? As far as I can tell, Wi-Fi is only “Out of the box” for people using the pre-made SD image. For people upgrading or installing manually, you’ll need the “On board WiFi drivers” archive from the download page.

FWIW WiFi lit up just fine on both an RPi3B+ and RPi3A+. That is particularly handy on the RPi3A+ as it has no ethernet.

The problematic RPi400 made its opinion known when on a startup there was a noticeable click and it went to the network recovery option. A search of the rear of the machine showed there was no card in it. I was sure I had inserted a card but these days, who knows. The card could not be found where it would have been with rest of the cards but a bit later an itinerant card was observed in a strange place at the far side of the desk! The card then would not stay in the slot. Clearly the WiFi failure caused the RPi400 to forcibly eject the card breaking the SD card retaining clip thereby ensuring it was jolly well not going back in again.

you’ll need the “On board WiFi drivers” archive from the download page.

That will be the piece I’m missing. From the News announcement I presumed “out of the box” meant it was in the HD4 zip as that’s what it refers to in “Getting started”. There’s no mention of separate downloads being required.

I see NVMe is also a separate download, so I’ll look at adding options for both to Partition Manager when creating a Boot drive.

On the PartMan front, Jon. It would be good to have a 5.28 build available for testing purposes.

An observation- PartMan coped reasonably well with the 5.28 files being removed over the weekend by ROOL. ;) Perhaps it’s a topic for another thread.

I’ll try a 3B I have later.

So tried the 3B and it works OK but stymied by only having 2.4Ghz capability.

@Paul Sprangers

The best approach to handling the 5.30 update is to run the ROD TCP/IP install program and choose the UnInstall option which will remove the stack and reset it back to “normal”. Ideally do this before 5.30 disc image install. Then once you have put that on, re-install the stack in the same way. but click “Install” rather than “Uninstall”.

This avoids the situation where 5.30 components over-write ROD TCP/IP stack elements with versions that are not aware of them.

Regarding Pinboard 2, it wouldn’t surprise me if the setup utility overwrote Pinboard 2’s setup with a v1 only edition, so reinstalling that afterwards is probably a good plan too. I haven’t had a chance to confirm this yet, though – it is merely speculation.

Users of R-Comp Interactive machines will be receiving updates in the next couple of weeks, once we’ve a) tested things and b) created and checked suitable easy-to-install updates.

So tried the 3B and it works OK but stymied by only having 2.4Ghz capability.

Ah, that is why I couldn’t see my router.

I activated the 2.4Ghz WiFi and could see it.
Tried to connect but got a timeout but the button now showed “Disconnect” and the password is greyed.
Thought I may have used the wrong password so tried to disconnect but got a timeout and the dialog remains unchanged.
Had to reboot to be able to retry again, and managed to notice that the problem was that I did not configure the password of the 2.4GHz Wifi.

It is now working and it reconnects automatically at startup.

Another issue is selecting both the “BMC43 WiFi” and “Ethernet over USB”:
- when I rebooted with non-working WiFi, I got a “duplicate route” error box on entry of the desktop.
- when I rebooted with working WiFi, Ethernet over USB was forcibly disabled. This should normally be the reverse!

The problematic RPi400 made its opinion known when on a startup there was a noticeable click and it went to the network recovery option. A search of the rear of the machine showed there was no card in it. I was sure I had inserted a card but these days, who knows. The card could not be found where it would have been with rest of the cards but a bit later an itinerant card was observed in a strange place at the far side of the desk! The card then would not stay in the slot. Clearly the WiFi failure caused the RPi400 to forcibly eject the card breaking the SD card retaining clip thereby ensuring it was jolly well not going back in again.

I managed to damage a Pi 400’s uSD socket too. Trying to bend the retaining spring back with tweezers was a fools errand so I got a strip of replacement sockets from Digikey. If you want one drop me an email and I’ll go look which box they’re in.

I remember the torture of updating the Pi 400’s Micrel Ethernet PHY

That was certainly coming to mind for me when I found that one Pi worked and the other didn’t, but it might indeed be something else.

If the chip truly has failed then that’s no big loss: I have the Wi-Fi HAT anyway (I tried physically disconnecting it just in case), and was just curious about whether I still needed it.

*sdiodevices
Bus Slt  RCA Fun  Description        Capacity     Vendor    Product Rev Date
  0   0  59B4  0  SDHC card          3839 Mbytes  JE        USD     1.0 2014-09

There’s no wireless or Bluetooth reported there – I’d say that one’s toast.

Clearly the WiFi failure caused the RPi400 to forcibly eject the card breaking the SD card retaining clip thereby ensuring it was jolly well not going back in again.

I got a strip of replacement sockets from Digikey. If you want one drop me an email and I’ll go look which box they’re in.

Thanks for the offer but I am even worse with hardware than I am with C. The RPi400 is still working and it has better chance of staying that way if I leave it alone. USB boot suffices.

ROOL WiFi is good here on a CM4. (That has Interface controller: BCM43455.)

Pi 400 with RISC OS 5.30 using the standalone archive, but I’m not currently able to connect to a network. After clicking Connect in the WiFi manager, I just get a “Timed out while connecting” error.
My Pi400 rev 0 does the same! The card was working just fine in the RPi4.

My Pi400 Rev.1 (German layout) does the same. ROOL complete image or a new “self made” card makes no sence.
Status is 99% net and WPA2 ok.
It looks like a problem in the driversettings.
RODs Wifi (Netmanager) is working well with my Pi400.

I have exactly the same ‘Timed out while connecting’ error only when I switch off all security I can get a connection. So perhaps some error in the handshake. I use a vanilla RO 5.30 on a Pi400

when I switch off all security I can get a connection

+=1

The Wifi on my OS5.30 RPi400 only connects if security is turned off on the router.

I have exactly the same ‘Timed out while connecting’ error only when I switch off all security I can get a connection. So perhaps some error in the handshake. I use a vanilla RO 5.30 on a Pi400

The ‘Timed out while connecting’ seem to be returned for any failed connection. I certainly had that error thrown at me when I used the wrong user/password.

I have the same issue of not connecting with the time out error on my early Pi400 with the ROOL WiFi stack.

ROD’s stack and Network manager work.

Having the same problem with my Pi 400. Timeout errors. ROD’s stack only works for a bit until the hourglass starts going green intermittently and hanging the system each time it appears making it unusable.

Testing on Pi Model 3 Revision 1.2, onboard WiFi works fine. I think like everyone else that’s having problems with their Pi400 Wifi, is the very early revisions of the computer, as I got mine only a few days after it was released.

Just wanted to chime in – WiFi also not working here on a brand new Pi 400 with brand new vanilla 5.30 image.
(edit: only working if I turn off all security on the router. Which unfortunately is no option for me)