Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Astroberry Update Renders Wifi Inop #218

Open
costargazer opened this issue Apr 3, 2023 · 4 comments
Open

Astroberry Update Renders Wifi Inop #218

costargazer opened this issue Apr 3, 2023 · 4 comments

Comments

@costargazer
Copy link

I have tried this procedure twice to verify this is what is happening.

1st boot of Astroberry from SD card, run update then upgrade. Changed the display resolution and reboot after upgrade. Wifi will not connect to router/modem, unable to make direct connection with wifi hotspot.

Reload Astroberry using Raspberry Pi Imager on SD card, 1st boot with fresh Astroberry and wifi is back to normal.

@bbillp
Copy link

bbillp commented Apr 3, 2023 via email

@costargazer
Copy link
Author

I should have given more information. The Rpi wifi will try to connect to the router but times out and the two computer icon appears. Checking network settings and Rpi settings everything appears normal but the Rpi onboard wifi appears disabled.
Wifi hotspot is disabled also when I switch to that.

Also noticed with a fresh 1st boot and changing the screen resolution to 1024 X 768 60hz the wifi is disabled also even without updating the software. Change the resolution back to 1240 X 800 and the wifi is back to normal.
The only fix I know of is to do a fresh reload of Astroberry on the SD card. I haven't updated the software and I haven't had any problem since.

@bbillp
Copy link

bbillp commented Apr 5, 2023 via email

@costargazer
Copy link
Author

First of all, my Rpi wifi and direct connect is working normal now because I reflashed the SD card and booted with that.

If I don't do an update everything is working. Bill it is not the HDMI cable, otherwise it would happen all the time.

My intention for posting this was to inform the developer that there is a glitch in the update that causes this.

As long as I don't update I'm working fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants