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

Keine Verbindung zur FRITZ!Box #93

Closed
Eddy1972N opened this issue Jul 28, 2024 · 14 comments
Closed

Keine Verbindung zur FRITZ!Box #93

Eddy1972N opened this issue Jul 28, 2024 · 14 comments

Comments

@Eddy1972N
Copy link

Eddy1972N commented Jul 28, 2024

Seit dem letzten Update kann ich keine w-lan Verbindung zur Fritz Box herstellen! Mit der vorherigen Version funktioniert das sehr gut was ist bei euch passiert??

Bitte bug Fixing image

@Eddy1972N
Copy link
Author

No conect on wlan0 bevor the Update nativ v1.9 is conect the wlan 0 on raspberry pi4 !!! Please kill the bug ! I'm Not amused about that ! Please bugfix!!

@MattBlack85
Copy link
Collaborator

MattBlack85 commented Jul 29, 2024

@Eddy1972N I may have a look but the screenshot you sent is a bit unclear. It seems you made a lot of networks and you seem to run a WiFi adapter in addition to the raspberry WiFi, is this correct?

@Eddy1972N
Copy link
Author

Eddy1972N commented Jul 29, 2024

Yes i made an Access Point 3of them! But i Cant the Main w-lan From RPI 4 (wlan0 ) Not conect on the router at Home ! On the nativ 1.9 was it Connect !

Pleasanton try it make 3 Access Point on the Software! On the 1.9 and than past of the Update From the Server! Any Protokoll is broken ! I think so!

@MattBlack85
Copy link
Collaborator

@Eddy1972N not sure I understand you, are you saying it was working and then you updated the system and it doesn't work anymore?

@Eddy1972N
Copy link
Author

Eddy1972N commented Jul 29, 2024

@Eddy1972N not sure I understand you, are you saying it was working and then you updated the system and it doesn't work anymore?

That right! Please Control the Kernel

@Eddy1972N
Copy link
Author

Eddy1972N commented Jul 29, 2024

Thats all i put my Passwort in it but nothing! Its Kick me out
And now change From w0 to w1 but nothing change!

image

@mistertroy
Copy link

I've had the same problem. I did an update prior to imaging on Friday night, lost wifi, could only connect to the hotspot, so did it that way friday night. Sat down and tried to sort it out on saturday but couldn't, so reflashed the card. It was able to connect to wifi, so i did another update - then it couldn't. Was having issues with Kstars crashing when ending Ekos anyway, so probably needed a reflash anyway! Am able to look into it again today, so am currently reflashing the SD card.

I'm using a Pi4, running AA1.9. No problems before, kept it mostly bleeding edge. won't be doing that anymore!

@mistertroy
Copy link

And after reflashing it all works. I'm not going to update though until it gets cloudy again and I've backed everything up!

@MattBlack85
Copy link
Collaborator

I will look for any NetowrkManager updates lately, I am not sure at the moment if was any of its updates or simply a kernel that broke it

@Eddy1972N
Copy link
Author

And where is the Bug ???

@MattBlack85
Copy link
Collaborator

I have no idea, that is not something I wrote, use or mantain. That is a package released from KDE and distributed by the ArchLinuxARM team

@Eddy1972N
Copy link
Author

I will look for any NetowrkManager updates lately, I am not sure at the moment if was any of its updates or simply a kernel that broke it

Ist nothing change With the last Update at 02.08.24 !!!!

Please Bug fix

@sc74
Copy link
Contributor

sc74 commented Aug 7, 2024

Hi. It seems that the pis are affected by a problem for the brcmfmac driver. View your logs with dmesg -w. If you have something like this

brcmfmac: brcmf_set_channel: set chanspec 0xd0...fail, reason -52

So, try to apply the solution found for this issue

home-assistant/operating-system#3367 (comment)

create a file /etc/modprobe.d/brcmfmac.conf containing this line:

options brcmfmac feature_disable=0x82000

and reboot.

Another thing, if you are using openssh please read the archlinux page

https://archlinux.org/news/the-sshd-service-needs-to-be-restarted-after-upgrading-to-openssh-98p1/

@MattBlack85
Copy link
Collaborator

closed as fixed in 1.9.2

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

4 participants