balbes150

Moderators
  • Posts

    3759
  • Joined

  • Last visited

Recent Profile Visitors

85729 profile views

balbes150's Achievements

  1. Maybe I'm doing something wrong, but after switching to the right branch, it still helps me : ./compile.sh LIB_TAG="v22.05" without this key, the system itself switches back to the master branch ps I would suggest for future discussion, get rid of this parameter in scripts and use a "dumb branch switching system" (i.e., do not check which branch the system is on and use the current one, without auto-switching, or just issue a message, but do not switch without "user permission").
  2. I checked BT on M1 with the latest kernel version 5.18. Externally it looks like BT appears, but not completely and does not work. Perhaps the reason is the wrong firmware, but I do not know how to check it (I have never used BT and am not familiar with its operation). root@station-m1:~# rfkill list 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no root@station-m1:~# hcitool dev Devices: root@station-m1:~# dmesg | grep tty [ 0.000000] Kernel command line: root=UUID=2ffc1c83-6aec-4615-9cdb-9d1d06520324 console=tty0 rootflags=data=writeback rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian [ 0.002113] printk: console [tty0] enabled [ 1.944133] ff130000.serial: ttyS2 at MMIO 0xff130000 (irq = 20, base_baud = 1500000) is a 16550A [ 1.944527] serial serial0: tty port ttyS2 registered [ 8.556574] systemd[1]: Created slice Slice /system/getty. [ 8.848242] systemd[1]: Created slice Slice /system/serial-getty. [ 12.618612] systemd[1]: Found device /dev/ttyS0. root@station-m1:~# dmesg | grep Blu [ 12.294469] Bluetooth: Core ver 2.22 [ 12.294495] Bluetooth: Starting self testing [ 12.317128] Bluetooth: ECDH test passed in 22095 usecs [ 12.324887] Bluetooth: SMP test passed in 7481 usecs [ 12.324993] Bluetooth: Finished self testing [ 12.325637] Bluetooth: HCI device and connection manager initialized [ 12.325657] Bluetooth: HCI socket layer initialized [ 12.325665] Bluetooth: L2CAP socket layer initialized [ 12.325699] Bluetooth: SCO socket layer initialized [ 12.511015] Bluetooth: HCI UART driver ver 2.3 [ 12.511040] Bluetooth: HCI UART protocol H4 registered [ 12.511045] Bluetooth: HCI UART protocol BCSP registered [ 12.511202] Bluetooth: HCI UART protocol LL registered [ 12.511215] Bluetooth: HCI UART protocol ATH3K registered [ 12.511323] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 12.511817] Bluetooth: HCI UART protocol Intel registered [ 12.512291] Bluetooth: HCI UART protocol Broadcom registered [ 12.512373] Bluetooth: HCI UART protocol QCA registered [ 12.512387] Bluetooth: HCI UART protocol AG6XX registered [ 12.512436] Bluetooth: HCI UART protocol Marvell registered [ 13.377850] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000d lmp_ver=08 lmp_subver=8723 [ 13.382102] Bluetooth: hci0: RTL: rom_version status=0 version=2 [ 13.382132] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723ds_fw.bin [ 13.477842] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723ds_config.bin [ 13.501454] Bluetooth: hci0: RTL: cfg_sz 47, total sz 30147 [ 15.525293] Bluetooth: hci0: command 0xfc20 tx timeout [ 23.525310] Bluetooth: hci0: RTL: download fw command failed (-110) [ 42.372608] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 42.372629] Bluetooth: BNEP filters: protocol multicast [ 42.372646] Bluetooth: BNEP socket layer initialized
  3. Do I understand correctly that this is a message from a script lib/distributions.sh ? Only in it I found such a message Perhaps this PR will solve problem ? #3793
  4. If something is missing or is not working properly in the Armbian system, contact the hardware manufacturer to provide the necessary information or patches, or use the official versions from the manufacturer.
  5. I checked the latest version with kernel 5.18, Wi-Fi works without problems.
  6. What exactly does not work from the equipment on M1 ?
  7. SPI is not supported in this version. To use an SSD, choose the installation option "boot emmc - system SATA USB"
  8. Tnx I will check this parameter.
  9. Where is the image taken from (link) ? Where did such an old log come from ?
  10. All the work on adding the necessary to the main core has almost been done by Frank (all patches have been sent to the core and are waiting for acceptance), I only slightly added the missing elements
  11. https://forum.banana-pi.org/t/armbian-and-libreelec-for-bpi-r2-pro-rk3568/13308/2
  12. version 20220428 with kernel 5.18-rc4 (edge) and 5.17.5 (current)
  13. version 20220428 with kernel 5.18-rc4 (edge) and 5.17.5 (current)
  14. version 20220428 with kernel 5.18-rc4 (edge) and 5.17.5 (current)
  15. I believe that there is already support for the CSC level (in the near future I will send the necessary PR to the official build system). To get the status of "official" support, I recommend that you contact @Igor to discuss the details of obtaining such a level of support.