Canada Goose Wifi Issue "No Wifi Networks Detected"

RG35XXPRO 2508.1

Had the stuck boot on 2508.0. Disabling Network on Boot resolved most of the hung boots.

I think this new 2508.1 issue is related to the fix implemented.

If “Start Network on Boot” is Enabled. It will connect to the saved network and the scan feature will see the networks in my area. It boots fine, and I can disconnect and reconnect with no issues.

When disabled, trying to connect to the known network freezes it up. I have to reset. Also, Scanning immediately kicks back a “No Networks found” message or something similar. No scanning time.

Only way to connect from this state is to Enable “Start Network on Boot” and then reboot the device. Then everything works but wifi will always be on by default.

It may not be a huge battery drain but I don’t feel like I need it automatically latching on every play session. Probably not a big deal for players that use retro achievements since they will always be connected.

Just an FYI.

Update: Wifi is not a significant source of battery drain so it’s not a major issue to leave it on during boot.

RG40XXV 2508.1

Ran into the same issue this morning. Wifi scanned and connected normally immediately after installing Canada Goose. I turned off “Start Network on Boot” and sent files over without issue. After restarting, I could no longer connect to my saved wifi profile. It would freeze while trying to connect, after about 45-60 seconds it would show an IP address, but when I exit out of the connection settings and go back in, it shows the network as being disconnected.

I haven’t tried to enable “Start Network on Boot” as I was worried it would cause the device to freeze up after booting, so I can’t comment if that works on the 40XXV. Instead I just went back to using my 2508.0 card.

Unrelated to this issue, but I also tried to install Scrappy on 2508.1, and it failed. It didn’t show up in the apps list, although I haven’t explored it further and this isn’t the thread for that, so i digress.

Scrappy was fixed. If you goto it’s page, the owner gave an update link.

Enabling wifi on boot does “fix” the issue for now. Hopefully an easy update/patch resolves it and i can turn off wifi on boot.

1 Like

I came across this as well, hope they fix it as I prefer to manually connect to networks

I ran the diagnostic task toolkit script and it seems the wlan io regulator isn’t being recognized when the auto connect on boot setting is disabled

2 Likes

Unfortunately it’s not going to save one iota of battery life. Please see, What happened to the Wi-Fi toggle?

1 Like

Great to know! Thanks!

1 Like

hey i found a workaround/manual fix for this, heres my message from the discord explaining what to do:

”Hey, for anyone experiencing the issue where your device won’t scan for/connect to networks with the “network on boot” setting disabled, I found a fix. With the setting enabled turn on your device so the wifi driver loads properly, then connect via ssh or open the on device terminal and type “lsmod” to list the loaded modules. Note down your wifi module (either 8821cs or 8188eu i think) and create a new .sh script in /MUOS/init/ and type the “#!/bin/bash” then new line and “insmod /path/to/your/network/module” (in my example: insmod /lib/modules/4.9.170/kernel/drivers/net/wireless/rtl8821cs/8821cs.ko) and save the file and reboot. Now you can disable the “network on boot” setting and your device will still load the network kernel module, so you’ll be able to connect at will without enabling the setting and rebooting”

This is fixed in the upcoming 2508.2 Silly Goose patch release.

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.