I am just despairing regarding the R64 and WiFi with the image “bpi-r64_bullseye_newatf_5.15_incomplete.img” …
I installed this on my R-64 and I can’t activate the 2.4 GHz nor the 5 GHz module in any way. It takes hours until the “WLAN0” shows up under “ifconfig -a”. The 5 GHz module I could not see so far. What is possibly wrong here? What does not work here? Should I rather go to the older version of the image?
i’m not sure i have tested wifi in this image as the name contains “incomplete”, it was a start for having an acutal base. i guess wifi-firmware is missing…
i wonder why it “takes hours” instead of simply “not working”.
maybe wifi driver is unstable here as i used a very early 5.15 there. try upgrading kernel to a recent 5.15.
Question over Debian Bullseye image
The external WiFi - Card is installed on cn25, so like your informations…
Question over Debian Bullseye image
If I try “lspci” there are no output on my screen
Kernel - Version
At the moment, I had the following kernel installed: 5.15.0-bpi-r64-main
I don’t know, if this is a new 5.15 - Kernel or not…
takes hours instead of simply “not working”
Well, the reason is, that sometimes I´ve got the WLAN0 - Interface if I reboot the router. At the moment, it is not working.
NOW - my system is up since: 19:40:55 up 5:47, 2 users, load average: 0.14, 0.26, 0.31
AND now, I had the Interface: 14: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:0c:43:26:60:00 brd ff:ff:ff:ff:ff:ff inet6 fe80::20c:43ff:fe26:6000/64 scope link valid_lft forever preferred_lft forever
BUT! No IP - Adresses is bind to this Interface, etc. And I don’t know, what kind of problems that this is… Best regards
your dmesg above says you have enabled the mt7622 wmac-wifi which firmware gets loaded (which i guess is the wlan0). As it is same driver this is not missing. so basicly the card is not recognized.
if lspci shows nothing (no controllers too) i guess there is something with pcie wrong…maybe looks in dmesg about pcie mapping
As already briefly written, it happens that the system displays the WLAN0 after a very long time, before that it cannot be found.
Therefore, I do not know how to better narrow down this error… What is the reason why this is not visible immediately after restarting the router… AND! Why it does not want to bind an IP - address to it afterwards.
My kernel repo is at 5.15.33,you can get a compiled image on its releases page
Just download the tar.gz for r64, unpack the content of the folders into the right partition (maybe change name of uImage) and add a line pointing to the new kernel file in the uEnv.txt
no, uenv.txt is on BPI-BOOT-partition (where the uImage needs to be extracted),
if none exist just create one in same folder like the uImage or in the root of this partition
modules go to BPI-ROOT like the folder in the tar-file