INTEL NUC Kit NUC8i5BEK Proxmox+Debian VM kein Onboard BT
-
Also ich habe alle 17er Dateien drin und ucode 9000-34 und 9260-34.
-
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) -
root@iOBrokerNUC:~# rfkill list -bash: rfkill: Kommando nicht gefunden. -
@Superdad
Ich hoffe ohne die 17-2??! -
Muss ich schauen.
Ups! Die waren drin.
Habs sie jetzt rausgenommen und neu rebootet. -
@Superdad na sieht nicht so aus, da stimmt was nicht mit deiner Firmware...so kann auch nix in IoBroker laufen
-
Ich tippe darauf, dass die 17-2 Version drin ist. Die hat wie bereits geschrieben nicht funktioniert.
-
Habe jetzt alle 17er drin gelassen, außer die 17-2er.
Rebootet und ble bleibt trotzdem gelb. -
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 libahciund
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 -
@Superdad lösch mal dein durchgereichtes Bluetooth Gerät in der VM und beende diese
dann schaust auf deinem Hosthciconfig -aund dann
hciconfig hci0 up -
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:~# -
@Superdad
Auch im Host keine 17-2? -
@Superdad sagte in INTEL NUC Kit NUC8i5BEK Proxmox+Debian VM kein Onboard BT:
5.120563] iwlwifi 0000:00:14.3: loaded firmware version 34.3125811985.0 op_mode iwlmvm
im Netz hab ich was von einer
Firmware-Version 46.3gelesen
-
Ich habe die Dateien nur im Host.
Im iobroker (VM) gibt es ja keinen Firmware-Ordner. -
@unltdnetworx nein, raus damit
-
Die sind ja raus im Host.
-
Die Ordner mal erstellen?
-
-
@crunchip
War nur eine Idee. Wie gesagt, Ubuntu und grün -
Das kommt in der VM:
root@iOBrokerNUC:~# lsusb -t /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Wireless, Driver=, 12M |__ Port 1: Dev 2, If 1, Class=Wireless, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
