All comments:13Replies

  1. lonewolf31 Elite member 2022-6-22 12:38:24

    Chris4arm Posted at 2022-6-20 18:00
    Hi lonewolf31,

    actually what i need is a Debian based server image, ideally ArmBian, with Bluetooth ...

    @Chris4arm
    OK, can build one.
    Ubuntu 22.04 or 20.04 I don't think will make a difference with bluetooth as it's perhaps a kernel or u-boot or even Armbian problem.
    Realtek bluetooth drivers are very complicated and even RTL8723cs support was only recently done for rk3229 devices for the 5.18 kernel.
    But I will look at rtl8723cs, rtl8723bs bluetooth and see if there isn't perhaps a setting missing that I can try with rtl8723ds bluetooth, but yes, it takes a lot of hours to test.
    There are only 3 Rockchip devices with rtl8723ds bluetooth over serial console and I also didn't see a solution yet for them.

    Kernel 5.20-5.21 will have better monitor resolution display.
    But I'm looking at LibreELEC and seeing if I can't perhaps port some of their unofficial kernel patches to Armbian but it's a lot since it supports multiple monitors.

    Station M2/ROC-RK3566-PC is similar to M1 size but an updated version and using Broadcom wifi + bluetooth. Bluetooth works correctly in latest kernel but they are still working on 4K resolution monitor support.

    Have you looked at USB splitters, it is like a USB hub but without extra cables?
    https://www.aliexpress.com/item/1005004084639980.html

  2. Chris4arm Member 2022-6-23 02:53:52

    lonewolf31 Posted at 2022-6-22 12:38
    @Chris4arm
    OK, can build one.
    Ubuntu 22.04 or 20.04 I don't think will make a difference with blue ...

    Hi lonewolf31,

    the screen resolution doesn't matter to me because I want to make a screenless server.
    By buying the M1 I thought that the BT was supported by recent kernels. It's disappointing.
    Realtek does not help with this support?
    Who else is working on this support ?

    Anyway thanks for your help.

    Chris

  3. Chris4arm Member 2022-7-12 21:32:19

    lonewolf31 Posted at 2022-6-30 12:19
    Ubuntu Server
    https://mega.nz/file/YvpViZrR#02xC7o3hv9MbOttlqjr1wHLrqLwKDwGwrp-NfoV_ZIo

    Hi lonewolf31 ,

    thanks and sorry for the delay but I was on vacation.
    I tried the Ubuntu Server image but got no success with bluetooth :
    Bluetooth: hci0: RTL: no UART config entry found
    The firmware files are there but something is missing
    see below for details.

    1. [    0.000000] Kernel command line: root=UUID=6521683e-34d0-4f6b-9b5f-e5f9fad5f5da console=ttyS0,1500000 console=tty0 rootflags=data=writeback rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian
    2. [    0.002225] printk: console [tty0] enabled
    3. [    0.008814] printk: console [tty0] printing thread started
    4. [    0.087366] Serial: AMBA PL011 UART driver
    5. [    3.158546] ff130000.serial: ttyS2 at MMIO 0xff130000 (irq = 25, base_baud = 1500000) is a 16550A
    6. [    3.158883] serial serial0: tty port ttyS2 registered
    7. [    3.384913] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    8. [    3.384974] ehci-pci: EHCI PCI platform driver
    9. [    3.385050] ehci-platform: EHCI generic platform driver
    10. [    3.385495] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    11. [    3.385526] ohci-pci: OHCI PCI platform driver
    12. [    3.385652] ohci-platform: OHCI generic platform driver
    13. [    3.387165] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
    14. [    3.387210] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
    15. [    3.387508] xhci-hcd xhci-hcd.0.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000000002010010
    16. [    3.387633] xhci-hcd xhci-hcd.0.auto: irq 31, io mem 0xff600000
    17. [    3.388236] ohci-platform ff5d0000.usb: Generic Platform OHCI controller
    18. [    3.388296] ohci-platform ff5d0000.usb: new USB bus registered, assigned bus number 3
    19. [    3.388299] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
    20. [    3.388322] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 4
    21. [    3.388349] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed
    22. [    3.388666] ohci-platform ff5d0000.usb: irq 34, io mem 0xff5d0000
    23. [    3.388713] ehci-platform ff5c0000.usb: EHCI Host Controller
    24. [    3.388738] usb usb2: Product: xHCI Host Controller
    25. [    3.388748] usb usb2: Manufacturer: Linux 5.19.0-rc3-media xhci-hcd
    26. [    3.388759] usb usb2: SerialNumber: xhci-hcd.0.auto
    27. [    3.391082] usb usb4: Product: xHCI Host Controller
    28. [    3.391095] usb usb4: Manufacturer: Linux 5.19.0-rc3-media xhci-hcd
    29. [    3.391107] usb usb4: SerialNumber: xhci-hcd.0.auto
    30. [    3.393082] ehci-platform ff5c0000.usb: new USB bus registered, assigned bus number 5
    31. [    3.393343] ehci-platform ff5c0000.usb: irq 33, io mem 0xff5c0000
    32. [    3.408090] ehci-platform ff5c0000.usb: USB 2.0 started, EHCI 1.00
    33. [    3.408695] usb usb5: Product: EHCI Host Controller
    34. [    3.408705] usb usb5: Manufacturer: Linux 5.19.0-rc3-media ehci_hcd
    35. [    3.452500] usb usb3: Product: Generic Platform OHCI controller
    36. [    3.452511] usb usb3: Manufacturer: Linux 5.19.0-rc3-media ohci_hcd
    37. [    3.471260] sdhci: Secure Digital Host Controller Interface driver
    38. [    3.471274] sdhci: Copyright(c) Pierre Ossman
    39. [    3.472775] sdhci-pltfm: SDHCI platform and OF driver helper
    40. [    3.936120] usb 3-1: new low-speed USB device number 2 using ohci-platform
    41. [   12.521081] systemd[1]: Created slice Slice /system/serial-getty.
    42. [   15.823219] Bluetooth: Core ver 2.22
    43. [   15.823270] Bluetooth: Starting self testing
    44. [   15.858318] Bluetooth: ECDH test passed in 34207 usecs
    45. [   15.865148] Bluetooth: SMP test passed in 6424 usecs
    46. [   15.865316] Bluetooth: Finished self testing
    47. [   15.865557] NET: Registered PF_BLUETOOTH protocol family
    48. [   15.865562] Bluetooth: HCI device and connection manager initialized
    49. [   15.865614] Bluetooth: HCI socket layer initialized
    50. [   15.865634] Bluetooth: L2CAP socket layer initialized
    51. [   15.865703] Bluetooth: SCO socket layer initialized
    52. [   16.208762] Bluetooth: HCI UART driver ver 2.3
    53. [   16.208815] Bluetooth: HCI UART protocol H4 registered
    54. [   16.208821] Bluetooth: HCI UART protocol BCSP registered
    55. [   16.209070] Bluetooth: HCI UART protocol LL registered
    56. [   16.209088] Bluetooth: HCI UART protocol ATH3K registered
    57. [   16.212504] Bluetooth: HCI UART protocol Three-wire (H5) registered
    58. [   16.213248] Bluetooth: HCI UART protocol Intel registered
    59. [   16.214139] Bluetooth: HCI UART protocol Broadcom registered
    60. [   16.214233] Bluetooth: HCI UART protocol QCA registered
    61. [   16.214239] Bluetooth: HCI UART protocol AG6XX registered
    62. [   16.214321] Bluetooth: HCI UART protocol Marvell registered
    63. [   16.686749] systemd[1]: Found device /dev/ttyS0.
    64. [   17.092743] Bluetooth: hci0: RTL: examining hci_ver=08 hci_rev=000d lmp_ver=08 lmp_subver=8723
    65. [   17.097170] Bluetooth: hci0: RTL: rom_version status=0 version=2
    66. [   17.097216] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723ds_fw.bin
    67. [   17.103479] Bluetooth: hci0: RTL: loading rtl_bt/rtl8723ds_config.bin
    68. [   17.104770] Bluetooth: hci0: RTL: no UART config entry found
    69. [   27.667198] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
    70. [   27.667234] Bluetooth: BNEP filters: protocol multicast
    71. [   27.667270] Bluetooth: BNEP socket layer initialized
    Copy the code


    Any hint ?

    Chris

12 Jump to Page

Reply

You need to log in before you can reply Login | Register