CB1
CB1 copied to clipboard
bigtreetech
v2.1.2 Wifi Issues
So I can get wifi connected with the 2.1.2 image over psu but it doesn't last. For me when it stops working the entire system stops working and requires a hard reset but cutting power. Sudo reboot now and shutdown now just send it into an endless splashscreen. I have not been able to determine how long wifi stays connected but it's less than 10 minutes. In my picture below I took it as soon as ssh became unresponsive so in that case it was 3 minutes.
Update: 30 minutes later and now it refuses to connect to wifi at all.
Yes, same here also the image will break if you try to update or write anything to it, the only way I can get it to connect again once it disconnects and refuses to connect is to reformat the SD card and reload the image then it will repeat again. I am puzzled how BTT keeps posting broken files.
Can't confirm wifi or update issues. Sources.list contains a bunch of chinese update servers, image seems to be synced with those servers (mirrors.tuna.tsinghua.edu.cn). I added the regular bullseye sources to my system and just did an apt-get update & upgrade. Also 0 Updates available. mirrors.tuna.tsinghua.edu.cn is also on the official debian mirrors list, so all good.
Wifi and ssh connected for over 20 minutes now, did the update process without issues and still working fine. I am also able to upload files via mainsail or create new files on the file system via ssh
Absolutely cannot get the CB1+M8p to connect at all. The M8P guide doesn't seem to help at all, and doesn't correct the problem. Anyone get this working?
Hello RcTomcat1, I changed the Chinese source list to the below and still same issues, deb http://deb.debian.org/debian bullseye main contrib non-free deb-src http://deb.debian.org/debian bullseye main contrib non-free
deb http://deb.debian.org/debian bullseye-updates main contrib non-free deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free
deb http://deb.debian.org/debian bullseye-backports main contrib non-free deb-src http://deb.debian.org/debian bullseye-backports main contrib non-free
deb http://security.debian.org/debian-security/ bullseye-security main contrib non-free deb-src http://security.debian.org/debian-security/ bullseye-security main contrib non-free
Here is what I just discovered, when I power on the CB1 (with the latest image) I get an IP address about 10 secs before the green LED by the power port starts flashing, as soon as the light starts flashing the CB1 is dropping out
@billru05 i used the following: deb http://deb.debian.org/debian bullseye main deb-src http://deb.debian.org/debian bullseye main
deb http://deb.debian.org/debian-security/ bullseye-security main deb-src http://deb.debian.org/debian-security/ bullseye-security main
deb http://deb.debian.org/debian bullseye-updates main deb-src http://deb.debian.org/debian bullseye-updates main
But as the chinese mirror is just that: a mirror there should be no need to update the sources.list The flashing green LED signals just a working system as far as I know. What does the router log and the system log of the CB1 say?
Update: 30 minutes later and now it refuses to connect to wifi at all.
There is something wrong with these boards I have my original 1 that works great no matter what I put on it, but the last 2 I received do not work connect for few minutes and stop. I can run this image on my board that works and get all the features https://github.com/stas2z/orangepi-build-cb1/releases/
Update: 30 minutes later and now it refuses to connect to wifi at all.
There is something wrong with these boards I have my original 1 that works great no matter what I put on it, but the last 2 I received do not work connect for few minutes and stop. I can run this image on my board that works and get all the features https://github.com/stas2z/orangepi-build-cb1/releases/
Which one of the 4 are you using?
Update: 30 minutes later and now it refuses to connect to wifi at all.
There is something wrong with these boards I have my original 1 that works great no matter what I put on it, but the last 2 I received do not work connect for few minutes and stop. I can run this image on my board that works and get all the features https://github.com/stas2z/orangepi-build-cb1/releases/
I also think it's a hardware issue on some of the boards. Both of my CB1s (ordered the day of launch) have stable wifi with the 2.1.2 image, without any problems. The same image does not work for other people.
Update: 30 minutes later and now it refuses to connect to wifi at all.
There is something wrong with these boards I have my original 1 that works great no matter what I put on it, but the last 2 I received do not work connect for few minutes and stop. I can run this image on my board that works and get all the features https://github.com/stas2z/orangepi-build-cb1/releases/
Which one of the 4 are you using?
I've tried both images this morning. The Bullseye image kernel panics once it boots and the Bookworm image boots, but Wifi appears completely non functional.
So I can get wifi connected with the 2.1.2 image over psu but it doesn't last. For me when it stops working the entire system stops working and requires a hard reset but cutting power. Sudo reboot now and shutdown now just send it into an endless splashscreen. I have not been able to determine how long wifi stays connected but it's less than 10 minutes. In my picture below I took it as soon as ssh became unresponsive so in that case it was 3 minutes.
This is just appalling - how could they possibly have thought this works well enough to release?
Update: 30 minutes later and now it refuses to connect to wifi at all.
There is something wrong with these boards I have my original 1 that works great no matter what I put on it, but the last 2 I received do not work connect for few minutes and stop. I can run this image on my board that works and get all the features https://github.com/stas2z/orangepi-build-cb1/releases/
Which one of the 4 are you using?
On the board that works I am using the bullseye minimal image and it works great. This image or any other image fails to work properly on my later boards. The key with this image is it loads all there proper kernel modules and if you watch it boot up with a monitor connected it has no red errors.
Update: 30 minutes later and now it refuses to connect to wifi at all.
There is something wrong with these boards I have my original 1 that works great no matter what I put on it, but the last 2 I received do not work connect for few minutes and stop. I can run this image on my board that works and get all the features https://github.com/stas2z/orangepi-build-cb1/releases/
Which one of the 4 are you using?
I've tried both images this morning. The Bullseye image kernel panics once it boots and the Bookworm image boots, but Wifi appears completely non functional.
I only have one this works on. I am positive they have a manufacturing issue and there 2.1.2 image still is lacking the Image I reposted above is great if your have a good board.
I brought six at one time (I ordered them 1 month ago) I just got them last week and I have played with two of them and I get the same results on any image or tweaking I load, they may get wifi for about 2 mins then they drop wifi, I can not get it back until I. clean & reformat the SD card reload image and again it may or may not get wifi but if it dose get wifi if drops within 2 - 3 mins. I can reboot, I can let it set still dose not get the wifi back.
I brought six at one time (I ordered them 1 month ago) I just got them last week and I have played with two of them and I get the same results on any image or tweaking I load, they may get wifi for about 2 mins then they drop wifi, I can not get it back until I. clean & reformat the SD card reload image and again it may or may not get wifi but if it dose get wifi if drops within 2 - 3 mins. I can reboot, I can let it set still dose not get the wifi back.
Yeah this is a batch or manufacturing issue I am sure of it. No way this can be software because like I said the one good board I have can run all of the images with wifi. 2 later ones do not work.
I have installed 2.1.2 on one of the two boards received from KB-3D.com (US Vendor) and wifi has been running well for about 4hrs thus far. I have been playing with gpiod and sunxi-pio and those seem to be working correctly as well.
Hello shawnchr , I just loaded the image from the link you posted (https://github.com/stas2z/orangepi-build-cb1/releases/), and both LED on board are solid green and I have no wifi, so there is differently something of a mystery on this board
Hello shawnchr , I just loaded the image from the link you posted (https://github.com/stas2z/orangepi-build-cb1/releases/), and both LED on board are solid green and I have no wifi, so there is differently something of a mystery on this board
With that image you need to go into nmtui and setup wlan0 it not configured automagically and the lights do stay solid on the board I have working so it could still crappy design.
Hello shawnchr, there are no lan lights on board so I do not think I can connect, I will try but the Lan looks dead on board
Hello shawnchr, there are no lan lights on board so I do not think I can connect, I will try but the Lan looks dead on board
No no networking of any kind initially you will need a monitor and keyboard
Has anyone found a way to read what version the hardware is with software? Also the scripts used at startup log cleartext credentials for SSID/password to /etc/scripts/wifi.log. Take a look at the mess in /etc/scripts. init.sh sets the timezone to HK :-(
logs should be in /var/logs (especially system related ones). No credentials should ever be logged. No assumption should be made of timezone or wifi country code.
So using the orangepi bullseye is getting me farther than btt did. The wifi is working but still seems to want to drop every now and then. While ssh putty will hang while trying to install something, in this case it was klipper. When I sudo reboot it hangs on "A stop job is running for" and lists three things (it's hard to see on the monitor). I'm going to try the other image because why not.
So using the orangepi bullseye is getting me farther than btt did. The wifi is working but still seems to want to drop every now and then. While ssh putty will hang while trying to install something, in this case it was klipper. When I sudo reboot it hangs on "A stop job is running for" and lists three things (it's hard to see on the monitor). I'm going to try the other image because why not.
So this the stop job takes forever to stop but it will eventually stop and reboot. The issue with the wifi dropping I am telling this is a hardware issue. the one board I have the works never drops so something happened with the later boards.
Has anyone found a way to read what version the hardware is with software? Also the scripts used at startup log cleartext credentials for SSID/password to /etc/scripts/wifi.log. Take a look at the mess in /etc/scripts. init.sh sets the timezone to HK :-(
logs should be in /var/logs (especially system related ones). No credentials should ever be logged. No assumption should be made of timezone or wifi country code.
As a follow-on, I am running fine on wifi on one board while the other absolutely refused. I finally commented out /etc/rc.local and installed a USB networking dongle and now both hardware and wifi work on that board. IMHO they are shooting themselves in the foot trying to do the dynamic flop/flip of ap and wireless via the rc.local (which kills wpa_supplicant and does all sorts of non-standard shinanigans. ) I also set my locale, my wifi country, and timezone. Now it feels almost workable!
Okay, so using the orangepi bullseye WITH a wifi dongle I am connected via PSU power, been able to install klipper, moonraker, fluidd, etc and so far it's been over an hour and I'm still connected via ssh! I'm not sure if this would work on the btt 2.1.2 image they just released but it is, so far, definitely working on this one. I shouldn't have to use an external piece of hardware to get their board working but considering they'll probably not make this right, I'll take what I can get. I'll update in the morning if anything changes
I tried both images now and I cannot connect wheter it's LAN or WiFi. This is the only stability I notice Nothing is working! Even after hours waiting for a sign of life. What I see is the Power is on and a blinking LED below WiFi module. The PiAdapter is powered via PSU or directly on my Laptop. Ethernet was connected in my office and powered by PSU or Router. LED's on LAN were dark. No lights or blinking... Great Job Guys! The same results as promises from german government. Thumb's up!!!
So i installed 2.1.2 this morning and everything went great. used the minimal image , connected to the CB1 via SSH right away and started to configure everything. I updated everything, installed KIAUH, then Klipper, moonraker and mainsail and connected to the web interface. Modified the config file for my printer and decided to take a break. At this point, the system was on for over an hour. A few hours later i turn the system back and and surprise... its not connecting to wifi. In the meantime i did found a workaround by reediting the config with the guest network. Now i am connected to the guest network and got access to the board again. Aparently using a new SSID gives you access once again. might not be a hardware issue after all and just bad software
Apparently they broke the network driver in 2.1.2. If you comment out everything in /etc/rc.local, their scripts will stop killing the wifi every 5 seconds (and will stop the blinking led). For those of you not familiar, rc.local gets executed every time you login. From my limited testing the "check interval" in the system.cfg seems to cause severe severe thrashing of the network stack as it kills wpa_supplicant and reconfigures the wifi for AP mode. In 2.1.2 they changed the value from 30 sec to 5 sec. It appears that the first reconfigure takes a while (as the system comes up) and second invocation starts before the first one finishes. I've been running two boards successfully for 24 hours now by dropping the pile of scripts from rc.local that instigate the rtl crashes. A usb network dongle works around these issues (wireless or wired).
I've also found that nmtui is a fairly useful tool in this exercise. It is a text-based network manager client.
The one good thing I've found is the script /etc/scripts/pwr_status, which it what blinks the power LED. So at a minimum we know that gpio229 is the LED! LOL