bigtreetech / CB1

OS System image for CB1
369 stars 62 forks source link

Debian image CB1_Debian11_bullseye_minimal_kernel4.9_20220730.img #10

Open emesix opened 2 years ago

emesix commented 2 years ago

APT source list are still some local setting in the CB1 Debian image.

sudo nano /etc/apt/sources.list deb https://mirrors.tuna.tsinghua.edu.cn/debian bullseye main

But rest of the image is pretty clean!!! Thank you Biqu / BigTreeTech

emesix commented 2 years ago

Biqu - user home directoy has a folder: root root 4096 Jul 30 12:21 gcode_files Remove folder before installing or change owner. sudo chown -R biqu gcode_files/ sudo chgrp -R biqu gcode_files/

escvn54 commented 2 years ago

That's the same source used by the OrangePi debian build, so no surprise, as it seems like BTT has built their release on top of the OrangePi Zero 2 release of Debian or Ubuntu respectively.

escvn54 commented 2 years ago

If you would prefer non CN sources, as I do, you can edit your sources.list with the following sources:

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

emesix commented 2 years ago

Yes it has the same hardware as a Orange Pi Zero 2. But i just want to make clear that BTT should remove all there references in OS images.

Biggest problem i have now is that ALLWINNER H616 is supported in klipper to be used for the motion sensor adxl345 ? And i cant get /tmp/klipper_host_mcu working...

midicdj1000 commented 2 years ago

So far this has worked for me, well at least installing Klipper, Mainsail, Moonraker and Klipper Screen worked without issue, The firmware compiled and Klipper can see the MCU so this is progress over the first Image.

djscrubb commented 2 years ago

Yes it has the same hardware as a Orange Pi Zero 2. But i just want to make clear that BTT should remove all there references in OS images.

Biggest problem i have now is that ALLWINNER H616 is supported in klipper to be used for the motion sensor adxl345 ? And i cant get /tmp/klipper_host_mcu working...

Have fun enabling spi bricked my image

Aleks-MO commented 2 years ago

There is no Wi-Fi connection..... I can't configure it. (((((

frutabruta commented 2 years ago

There is no Wi-Fi connection..... I can't configure it. (((((

Did you enter the Wi-Fi SSID and password to the file on microSD card? It is on one of the partitions mounted on Windows after writing the image. I think the file is called system.cfg.

Aleks-MO commented 2 years ago

frutabruta. No. I don't see this disk as BOOT. So it was not possible to edit the system.cfg file ....(((( How to force it through an SSH connection? [biqu@CB1 ~]$ iw wlan0 link Not connected. [biqu@CB1 ~]$ sudo ip link set wlan0 up [biqu@CB1 ~]$ iw wlan0 link Not connected. [biqu@CB1 ~]$ sudo iwlist wlan0 scan | grep ESSID ESSID:"Taxi-GSM-VIP" ESSID:"TP-LINK_C5D2CC" ESSID:"DIRECT-JR-BRAVIA" ESSID:"DIRECT-UA-BRAVIA" [biqu@CB1 ~]$ nmcli d wifi connect Taxi-GSM-VIP password *** Error: Failed to add/activate new connection: Not authorized to control networking. ????????????????????

frutabruta commented 2 years ago

@Aleks-MO Not sure about this release, but I think it's mounted as /mnt/u-disk or /media/u-disk.

Aleks-MO commented 2 years ago

@frutabruta It doesn't matter anymore, this system is not visible on my computer and it is impossible to edit. I don't know how to start Wi-Fi now...

midicdj1000 commented 2 years ago

Hi @Aleks-MO what size SD card are you using ? I had problems with a brand new 64gb sd card, I had the same problem that it wouldn't show any valid partitions on my pc. I switched to a smaller 8gb and it worked first time I at the end the drive with the wifi config opened and I could edit it.

midicdj1000 commented 2 years ago

Over the weekend I was able to install everything I needed including klipper screen and make sure everything was the latest version. A big improvement over the previous image. Like I just said I did have a problem that it would never finish verifying the sd card, I think it was a few hours and then it ended, but I didn't have any valid partitions to edit the wifi. I went back to the smaller 8gb and it worked first time. I guess I could have a faulty sd card ! Next steps is to connect the Manta and CB1 to a printer and a screen.

Aleks-MO commented 2 years ago

Hi! @midicdj1000 SD 32/16/8gb sd card..

Aleks-MO commented 2 years ago

@midicdj1000 In the current state, is it possible to start WiFi somehow?

midicdj1000 commented 2 years ago

are you using the raspberry pi image tool ? I stopped it trying to write the wifi and ssh stored settings.

midicdj1000 commented 2 years ago

perhaps clean the 8gb sd first and try again.

Aleks-MO commented 2 years ago

Yes, raspberry pi image tool

djscrubb commented 2 years ago

I used belina etcher and had no problems. This image for what ever reason doesn't use the system.txt file

midicdj1000 commented 2 years ago

How would I setup HDMI screen sizes ?

Aleks-MO commented 2 years ago

@djscrubb Yes

Aleks-MO commented 2 years ago

You can use Win32DiskImager, the result is the same...

TxBillbr commented 2 years ago

BTT needs to comply with the license and post the sources. There are many people who could help quickly get the image into a better shape. They also need to contact Debian to get into their ARM program. (https://www.debian.org/ports/arm/) and (https://wiki.debian.org/InstallingDebianOn/Allwinner)

Just for the record, I was able to get the CB1 up and running with exception of SPI and the webcamd. Still working on that. For those not seeing the system.cfg file, the install creates several mapped drives on a windows system. After the imaging is completed take a look at each. Only one will be recognized by windows. You may also need to re-insert the SD card as most imagers now auto-eject after imaging.

As a temporary work-around for resonance tuning, I plan to take a real Pi, add it to the printer.cfg as mcu42 (or whatever), install the resonance software on it, run that, then the results will be in the printer.cfg and I can comment out the real pi section and remove the real pi. A bit of monkey engineering, but should work.