Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. INTEL NUC Kit NUC8i5BEK Proxmox+Debian VM kein Onboard BT

    NEWS

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    • Save The Date: ioBroker@Smart Living Forum Solingen, 14.06.

    INTEL NUC Kit NUC8i5BEK Proxmox+Debian VM kein Onboard BT

    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Superdad last edited by

      Nicht auf der VM sondern in Proxmox auf dem Host.

      1 Reply Last reply Reply Quote 0
      • S
        Superdad last edited by

        In der VM:

        root@iOBrokerNUC:~# hcitool -i hci0 scan
        Invalid device: No such device
        
        crunchip 1 Reply Last reply Reply Quote 0
        • crunchip
          crunchip Forum Testing Most Active @Superdad last edited by

          @Superdad geb mal ein, auf deiner VM

          hciconfig auth
          
          1 Reply Last reply Reply Quote 0
          • S
            Superdad last edited by

            Sorry, war gerade was essen.

            root@iOBrokerNUC:~# hciconfig auth
            Can't get device info: No such device
            
            
            crunchip 1 Reply Last reply Reply Quote 0
            • unltdnetworx
              unltdnetworx Developer last edited by

              Reine Vermutung, aber evtl. müssen die Treiber auch in der VM hinzugefügt werden. Bei Ubuntu ging es sofort. Möglicherweise bei Debian nicht enthalten.

              1 Reply Last reply Reply Quote 0
              • crunchip
                crunchip Forum Testing Most Active @Superdad last edited by

                @Superdad laangsam Blick ich nimmer ganz durch
                Du hast jetzt die "fehlenden" iwlwifi Dateien reinkopiert, Rechner neu gestartet, auf dem Host findet er nun das Gerät, aber nicht in der VM bzw
                ein Gerät wird angezeigt, was aber nicht funktioniert.

                Der Adapter ist installiert.

                hast du ein

                sudo apt-get install bluetooth bluez libbluetooth-dev libudev-dev
                sudo apt-get install libcap2-bin
                sudo setcap cap_net_raw+eip $(eval readlink -f `which node`)
                
                

                im IoBroker ausgeführt?

                desweiteren
                was ergibt

                systemctl status bluetooth.service
                

                dieses muss du eingeben, das bluetooth gestartet wird und auch bei einem neustart wieder startet

                systemctl enable bluetooth.service
                systemctl start bluetooth.service
                

                ein

                hciconfig hci0 up
                

                schaltet dein Bluetooth Gerät ein

                1 Reply Last reply Reply Quote 0
                • S
                  Superdad last edited by

                  Erstmal das:

                  root@iOBrokerNUC:~# systemctl status bluetooth.service
                  ● bluetooth.service - Bluetooth service
                     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
                     Active: active (running) since Thu 2019-06-20 20:55:52 CEST; 4s ago
                       Docs: man:bluetoothd(8)
                   Main PID: 16799 (bluetoothd)
                     Status: "Running"
                      Tasks: 1 (limit: 4915)
                     CGroup: /system.slice/bluetooth.service
                             └─16799 /usr/lib/bluetooth/bluetoothd
                  
                  Jun 20 20:55:52 iOBrokerNUC systemd[1]: Starting Bluetooth service...
                  Jun 20 20:55:52 iOBrokerNUC bluetoothd[16799]: Bluetooth daemon 5.43
                  Jun 20 20:55:52 iOBrokerNUC systemd[1]: Started Bluetooth service.
                  Jun 20 20:55:52 iOBrokerNUC bluetoothd[16799]: Starting SDP server
                  Jun 20 20:55:52 iOBrokerNUC bluetoothd[16799]: Bluetooth management interface 1.14 initialized
                  
                  
                  1 Reply Last reply Reply Quote 0
                  • S
                    Superdad last edited by

                    Dann das:

                    root@iOBrokerNUC:~# hciconfig hci0 up
                    Can't get device info: No such device
                    
                    crunchip 1 Reply Last reply Reply Quote 0
                    • crunchip
                      crunchip Forum Testing Most Active @Superdad last edited by

                      @Superdad auf deiner VM
                      kannst noch Soft/Hard blocked no prüfen mit folgendem Befehl

                      rfkill list
                      

                      funktionieren jetzt eigendlich nun deine Treiber in Proxmox?
                      hast keine Ausgabe mehr gezeigt von

                      dmesg | grep tooth
                      
                      1 Reply Last reply Reply Quote 0
                      • S
                        Superdad last edited by

                        Also ich habe alle 17er Dateien drin und ucode 9000-34 und 9260-34.

                        1 Reply Last reply Reply Quote 0
                        • S
                          Superdad last edited by

                          Ausgabe von dmesg in Proxmox.

                          root@pve:~# dmesg | grep tooth
                          [    5.428947] Bluetooth: Core ver 2.22
                          [    5.428965] Bluetooth: HCI device and connection manager initialized
                          [    5.428995] Bluetooth: HCI socket layer initialized
                          [    5.428999] Bluetooth: L2CAP socket layer initialized
                          [    5.429003] Bluetooth: SCO socket layer initialized
                          [    5.433876] Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
                          [    8.031647] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
                          [    8.031649] Bluetooth: BNEP filters: protocol multicast
                          [    8.031652] Bluetooth: BNEP socket layer initialized
                          [   12.070350] Bluetooth: hci0: urb 000000008df1e450 failed to resubmit (2)
                          [  164.403866] Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
                          [  256.967089] Bluetooth: hci0: urb 000000003ff3f2ed failed to resubmit (2)
                          [  930.768975] Modules linked in: tcp_diag inet_diag nfsv3 nfs_acl nfs lockd grace fscache veth ip_set ip6table_filter ip6_tables iptable_filter cmac bnep softdog nfnetlink_log nfnetlink nls_iso8859_1 dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi i915 snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt drm_kms_helper drm intel_cstate i2c_algo_bit fb_sys_fops btusb btrtl btbcm btintel iwlmvm bluetooth mac80211 rtsx_pci_ms
                          [ 2094.425954] Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
                          [ 2195.809396] Bluetooth: hci0: urb 00000000f2205b5e failed to resubmit (2)
                          [ 4613.078873] Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
                          [ 4616.769724] Bluetooth: hci0: urb 000000001b52b7b8 failed to resubmit (2)
                          [ 4767.795902] Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
                          [ 9174.243886] Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
                          [ 9177.776850] Bluetooth: hci0: urb 00000000dc56a48b failed to resubmit (2)
                          [ 9262.249870] Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
                          [ 9290.733310] Bluetooth: hci0: urb 000000002a962bfd failed to resubmit (2)
                          [ 9586.752868] Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
                          [ 9607.213728] Bluetooth: hci0: urb 00000000c3d97bb3 failed to resubmit (2)
                          [10153.768841] Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
                          [10253.982889] Bluetooth: hci0: urb 00000000fc0a1aee failed to resubmit (2)
                          [11506.075844] Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
                          [11561.341543] Bluetooth: hci0: urb 000000006e2e8cd1 failed to resubmit (2)
                          [12533.847878] Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
                          [12536.773457] Bluetooth: hci0: urb 000000006e2719f4 failed to resubmit (2)
                          
                          unltdnetworx 1 Reply Last reply Reply Quote 0
                          • S
                            Superdad last edited by

                            root@iOBrokerNUC:~# rfkill list
                            -bash: rfkill: Kommando nicht gefunden.
                            
                            1 Reply Last reply Reply Quote 0
                            • unltdnetworx
                              unltdnetworx Developer @Superdad last edited by

                              @Superdad
                              Ich hoffe ohne die 17-2??!

                              1 Reply Last reply Reply Quote 0
                              • S
                                Superdad last edited by Superdad

                                Muss ich schauen.

                                Ups! Die waren drin.
                                Habs sie jetzt rausgenommen und neu rebootet.

                                crunchip 1 Reply Last reply Reply Quote 0
                                • crunchip
                                  crunchip Forum Testing Most Active @Superdad last edited by

                                  @Superdad na sieht nicht so aus, da stimmt was nicht mit deiner Firmware...so kann auch nix in IoBroker laufen

                                  1 Reply Last reply Reply Quote 0
                                  • unltdnetworx
                                    unltdnetworx Developer last edited by

                                    Ich tippe darauf, dass die 17-2 Version drin ist. Die hat wie bereits geschrieben nicht funktioniert.

                                    1 Reply Last reply Reply Quote 0
                                    • S
                                      Superdad last edited by

                                      Habe jetzt alle 17er drin gelassen, außer die 17-2er.
                                      Rebootet und ble bleibt trotzdem gelb.

                                      crunchip 1 Reply Last reply Reply Quote 0
                                      • S
                                        Superdad last edited by

                                        Das kommt bei gestoppter VM:

                                        root@pve:~# dmesg |grep iwlwifi
                                        [    5.096398] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
                                        [    5.120563] iwlwifi 0000:00:14.3: loaded firmware version 34.3125811985.0 op_mode iwlmvm
                                        [    5.183248] iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9560, REV=0x318
                                        [    5.349523] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
                                        [    5.349531] iwlwifi 0000:00:14.3: Not valid error log pointer 0x00000000 for Init uCode
                                        [    5.349568] iwlwifi 0000:00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 0x2458
                                        [    5.349571] iwlwifi 0000:00:14.3: Failed to start INIT ucode: -5
                                        [    5.361808] iwlwifi 0000:00:14.3: Failed to run INIT ucode: -5
                                        [  405.231295]  fb_sys_fops zavl(PO) iwlwifi snd_hda_codec syscopyarea intel_rapl_perf memstick ecdh_generic sysfillrect icp(PO) sysimgblt snd_hda_core wmi_bmof mei_me intel_wmi_thunderbolt snd_hwdep mei snd_pcm snd_timer snd cfg80211 soundcore pcspkr intel_pch_thermal shpchp wmi video mac_hid acpi_pad zcommon(PO) znvpair(PO) spl(O) vhost_net vhost tap ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi sunrpc ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq rtsx_pci_sdmmc e1000e(O) ptp pps_core i2c_i801 rtsx_pci ahci libahci
                                        

                                        und

                                        root@pve:~# lsusb -t
                                        /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 10000M
                                        /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
                                            |__ Port 10: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
                                            |__ Port 10: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
                                        
                                        crunchip 1 Reply Last reply Reply Quote 0
                                        • crunchip
                                          crunchip Forum Testing Most Active @Superdad last edited by

                                          @Superdad lösch mal dein durchgereichtes Bluetooth Gerät in der VM und beende diese
                                          dann schaust auf deinem Host

                                          hciconfig -a
                                          

                                          und dann

                                          hciconfig hci0 up
                                          
                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            Superdad last edited by

                                            root@pve:~# hciconfig -a
                                            hci0:   Type: Primary  Bus: USB
                                                    BD Address: D8:F2:CA:31:D5:2A  ACL MTU: 1021:4  SCO MTU: 96:6
                                                    UP RUNNING 
                                                    RX bytes:745 acl:0 sco:0 events:51 errors:0
                                                    TX bytes:2187 acl:0 sco:0 commands:51 errors:0
                                                    Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
                                                    Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
                                                    Link policy: RSWITCH SNIFF 
                                                    Link mode: SLAVE ACCEPT 
                                                    Name: 'pve'
                                                    Class: 0x000104
                                                    Service Classes: Unspecified
                                                    Device Class: Computer, Desktop workstation
                                                    HCI Version:  (0x9)  Revision: 0x100
                                                    LMP Version:  (0x9)  Subversion: 0x100
                                                    Manufacturer: Intel Corp. (2)
                                            
                                            root@pve:~# hciconfig hci0 up
                                            root@pve:~# 
                                            
                                            unltdnetworx 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            1.0k
                                            Online

                                            31.6k
                                            Users

                                            79.4k
                                            Topics

                                            1.3m
                                            Posts

                                            18
                                            189
                                            15662
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo