Wichtig ist jetzt heraus zu finden wer den Stick blockiert. Also
sudo modprobe -rfv btusb
sudo modprobe -rfv ath3k
dann nur
sudo modprobe -v btusb
sudo /etc/init.d/bluetooth restart
Bluetooth Problem
Anmeldungsdatum: Beiträge: 19617 Wohnort: Schleswig-Holstein |
|
|
(Themenstarter)
Anmeldungsdatum: Beiträge: Zähle... |
~$ sudo modprobe -rfv btusb rmmod btusb rmmod btintel rmmod btbcm rmmod btrtl ~$ sudo modprobe -rfv ath3k rmmod ath3k ~$ sudo modprobe -v btusb insmod /lib/modules/4.13.0-17-generic/kernel/drivers/bluetooth/btintel.ko insmod /lib/modules/4.13.0-17-generic/kernel/drivers/bluetooth/btbcm.ko insmod /lib/modules/4.13.0-17-generic/kernel/drivers/bluetooth/btrtl.ko insmod /lib/modules/4.13.0-17-generic/kernel/drivers/bluetooth/btusb.ko ~$ sudo /etc/init.d/bluetooth restart [ ok ] Restarting bluetooth (via systemctl): bluetooth.service. Leider keine Veränderung, Adapter scheint noch deaktiviert zu sein. ☹ |
|
Anmeldungsdatum: Beiträge: 19617 Wohnort: Schleswig-Holstein |
Zeige nun rfkill list und journalctl | grep -i bluetooth |
|
(Themenstarter)
Anmeldungsdatum: Beiträge: 13 |
~$ rfkill list 0: Toshiba Bluetooth: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no 5: hci0: Bluetooth Soft blocked: no Hard blocked: no :~$ journalctl | grep -i bluetooth Nov 29 18:37:22 kernel: usb 1-1.2: Product: Bluetooth USB Host Controller Nov 29 18:37:25 kernel: toshiba_bluetooth: Toshiba ACPI Bluetooth device driver Nov 29 18:37:28 kernel: Bluetooth: Core ver 2.22 Nov 29 18:37:28 kernel: Bluetooth: HCI device and connection manager initialized Nov 29 18:37:28 kernel: Bluetooth: HCI socket layer initialized Nov 29 18:37:28 kernel: Bluetooth: L2CAP socket layer initialized Nov 29 18:37:28 kernel: Bluetooth: SCO socket layer initialized Nov 29 18:37:42 NetworkManager[835]: <info> [1511977062.0485] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Nov 29 18:37:46 kernel: usb 1-1.2: Product: Bluetooth USB Host Controller Nov 29 18:37:46 systemd[1]: Starting Bluetooth service... Nov 29 18:37:46 bluetoothd[1127]: Bluetooth daemon 5.46 Nov 29 18:37:46 systemd[1]: Started Bluetooth service. Nov 29 18:37:46 systemd[1]: Reached target Bluetooth. Nov 29 18:37:46 bluetoothd[1127]: Starting SDP server Nov 29 18:37:48 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Nov 29 18:37:48 kernel: Bluetooth: BNEP filters: protocol multicast Nov 29 18:37:48 kernel: Bluetooth: BNEP socket layer initialized Nov 29 18:37:48 bluetoothd[1127]: Bluetooth management interface 1.14 initialized Nov 29 18:37:48 kernel: Bluetooth: hci0 command 0x1003 tx timeout Nov 29 18:37:50 kernel: Bluetooth: hci0 command 0x1001 tx timeout Nov 29 18:37:52 kernel: Bluetooth: hci0 command 0x1009 tx timeout Nov 29 18:38:28 systemd[1282]: Starting Bluetooth OBEX service... Nov 29 18:38:29 systemd[1282]: Started Bluetooth OBEX service. Nov 29 18:40:00 sudo[2469]: desktop : TTY=pts/0 ; PWD=/home/desktop ; USER=root ; COMMAND=/bin/systemctl status bluetooth Nov 29 19:09:32 kernel: Bluetooth: hci0 urb ffff9ce0cebaf540 failed to resubmit (2) Nov 29 19:26:31 sudo[3060]: desktop : TTY=pts/0 ; PWD=/home/desktop ; USER=root ; COMMAND=/etc/init.d/bluetooth restart Nov 29 19:26:31 bluetoothd[1127]: Terminating Nov 29 19:26:31 systemd[1]: Stopping Bluetooth service... Nov 29 19:26:31 bluetoothd[1127]: Stopping SDP server Nov 29 19:26:31 bluetoothd[1127]: Exit Nov 29 19:26:31 systemd[1]: Stopped Bluetooth service. Nov 29 19:26:31 systemd[1]: Starting Bluetooth service... Nov 29 19:26:31 bluetoothd[3071]: Bluetooth daemon 5.46 Nov 29 19:26:31 systemd[1]: Started Bluetooth service. Nov 29 19:26:31 bluetoothd[3071]: Starting SDP server Nov 29 19:26:31 bluetoothd[3071]: Bluetooth management interface 1.14 initialized Nov 29 19:26:35 sudo[3096]: desktop : TTY=pts/0 ; PWD=/home/desktop ; USER=root ; COMMAND=/bin/systemctl start bluetooth.service Nov 29 19:34:37 sudo[3238]: desktop : TTY=pts/1 ; PWD=/home/desktop ; USER=root ; COMMAND=/etc/init.d/bluetooth restart Nov 29 19:34:37 bluetoothd[3071]: Terminating Nov 29 19:34:37 systemd[1]: Stopping Bluetooth service... Nov 29 19:34:37 bluetoothd[3071]: Stopping SDP server Nov 29 19:34:37 bluetoothd[3071]: Exit Nov 29 19:34:37 systemd[1]: Stopped Bluetooth service. Nov 29 19:34:37 systemd[1]: Starting Bluetooth service... Nov 29 19:34:37 bluetoothd[3249]: Bluetooth daemon 5.46 Nov 29 19:34:37 systemd[1]: Started Bluetooth service. Nov 29 19:34:37 bluetoothd[3249]: Starting SDP server Nov 29 19:34:37 bluetoothd[3249]: Bluetooth management interface 1.14 initialized Hm, ist das normal dass bei dem "rfkill" zwei Bluetooth Geräte sichtbar sind? Der Zustand ist unverändert. |
|
Anmeldungsdatum: Beiträge: 19617 Wohnort: Schleswig-Holstein |
Die Frage ist gut 😉 Zeige mal lsmod |
|
(Themenstarter)
Anmeldungsdatum: Beiträge: 13 |
~$ lsmod Module Size Used by btusb 45056 0 btrtl 16384 1 btusb btbcm 16384 1 btusb btintel 16384 1 btusb ccm 20480 3 pci_stub 16384 1 vboxpci 24576 0 vboxnetadp 28672 0 vboxnetflt 28672 0 vboxdrv 466944 3 vboxnetadp,vboxnetflt,vboxpci bnep 20480 2 uvcvideo 90112 0 videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc bluetooth 540672 12 btrtl,btintel,bnep,btbcm,btusb snd_hda_codec_hdmi 49152 1 rtsx_usb_ms 20480 0 memstick 16384 1 rtsx_usb_ms videobuf2_v4l2 24576 1 uvcvideo snd_hda_codec_realtek 94208 1 snd_hda_codec_generic 73728 1 snd_hda_codec_realtek videobuf2_core 40960 2 uvcvideo,videobuf2_v4l2 snd_hda_intel 40960 7 videodev 176128 3 uvcvideo,videobuf2_core,videobuf2_v4l2 snd_hda_codec 126976 4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek media 40960 2 uvcvideo,videodev ecdh_generic 24576 1 bluetooth snd_hda_core 81920 5 snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek arc4 16384 2 snd_hwdep 20480 1 snd_hda_codec snd_pcm 98304 5 snd_hda_intel,snd_hda_codec,snd_hda_core,snd_hda_codec_hdmi ath9k 151552 0 snd_seq_midi 16384 0 ath9k_common 36864 1 ath9k ath9k_hw 462848 2 ath9k,ath9k_common ath 28672 3 ath9k_hw,ath9k,ath9k_common intel_rapl 20480 0 snd_seq_midi_event 16384 1 snd_seq_midi snd_rawmidi 32768 1 snd_seq_midi mei_me 40960 0 snd_seq 65536 2 snd_seq_midi_event,snd_seq_midi mac80211 778240 1 ath9k snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi joydev 20480 0 input_leds 16384 0 x86_pkg_temp_thermal 16384 0 intel_powerclamp 16384 0 cfg80211 610304 4 mac80211,ath9k,ath,ath9k_common snd_timer 32768 2 snd_seq,snd_pcm toshiba_acpi 45056 0 mei 98304 1 mei_me snd 81920 24 snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_seq_device,snd_hda_codec_realtek,snd_pcm sparse_keymap 16384 1 toshiba_acpi coretemp 16384 0 industrialio 69632 1 toshiba_acpi soundcore 16384 1 snd serio_raw 16384 0 wmi 24576 1 toshiba_acpi shpchp 36864 0 kvm_intel 200704 0 binfmt_misc 20480 1 mac_hid 16384 0 kvm 581632 1 kvm_intel irqbypass 16384 1 kvm crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 toshiba_bluetooth 16384 0 ghash_clmulni_intel 16384 0 lpc_ich 24576 0 pcbc 16384 0 aesni_intel 188416 2 aes_x86_64 20480 1 aesni_intel crypto_simd 16384 1 aesni_intel glue_helper 16384 1 aesni_intel cryptd 24576 3 crypto_simd,ghash_clmulni_intel,aesni_intel intel_cstate 20480 0 intel_rapl_perf 16384 0 parport_pc 32768 0 ppdev 20480 0 lp 20480 0 parport 49152 3 lp,parport_pc,ppdev ip_tables 24576 0 x_tables 40960 1 ip_tables autofs4 40960 2 rtsx_usb_sdmmc 28672 0 rtsx_usb 20480 2 rtsx_usb_sdmmc,rtsx_usb_ms hid_generic 16384 0 usbhid 49152 0 hid 118784 2 hid_generic,usbhid amdkfd 188416 1 amd_iommu_v2 20480 1 amdkfd radeon 1470464 3 i2c_algo_bit 16384 1 radeon ttm 94208 1 radeon drm_kms_helper 167936 1 radeon syscopyarea 16384 1 drm_kms_helper sysfillrect 16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops 16384 1 drm_kms_helper drm 356352 6 radeon,ttm,drm_kms_helper psmouse 147456 0 ahci 36864 1 alx 45056 0 libahci 32768 1 ahci mdio 16384 1 alx video 40960 1 toshiba_acpi |
|
Anmeldungsdatum: Beiträge: 19617 Wohnort: Schleswig-Holstein |
Werde mich mal Informieren was toshiba_acpi da so macht und ob man es mal abschalten kann. |
|
(Themenstarter)
Anmeldungsdatum: Beiträge: 13 |
Super, vielen Dank! 👍 |
|
Anmeldungsdatum: Beiträge: 19617 Wohnort: Schleswig-Holstein |
Daran sollten wir nicht "Schrauben" https://github.com/torvalds/linux/blob/master/drivers/platform/x86/toshiba_acpi.c Mal sehen was es noch für Möglichkeiten gibt. Teste mal folgendes.Neustart ohne Bluetooth Stick,erst einstecken wenn der PC ganz hochgefahren ist. |
|
(Themenstarter)
Anmeldungsdatum: Beiträge: 13 |
Vielen Dank für die Recherche! Ich verwende keinen Stick, das Bluetooth ist beim Laptop eingebaut. |
|
Anmeldungsdatum: Beiträge: 19617 Wohnort: Schleswig-Holstein |
Werden die Bluetooth-Module mal "Blacklisten" damit sie beim Systemstart noch nicht geladen werden.Dazu eine Datei anlegen sudo - H pluma /etc/modprobe.d/blacklist-bluetooth.conf eintrag blacklist btusb blacklist ath3k Speichern Neustart.Zeige dann dmesg | egrep -i 'blue|firm' sowie lsmod | grep blue
grep -i blue /var/log/kern.log
dpkg -l linux-firmware |