smoky crypt
I'm new and got WiFi to work by installing drivers. But the Bluetooth doesn't work after doing so as instructed in the wiki. This is what it says in lspci -v:
Subsystem: Dell Wireless 1704 802.11n + BT 4.0 Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at f7d00000 (64-bit, non-prefetchable) [size=32K] Capabilities: <access denied> Kernel driver in use: wl Kernel modules: bcma, wl
Any help would be gladly appreciated.
woven kelp
run rfkill, does bluetooth say unblocked or blocked? also you will need to install bluez to connect to bluetooth devices, or blueman for a gui
north gorge
@smoky crypt 
smoky crypt
run `rfkill`, does bluetooth say unblocked or blocked? also you will need to ins...
[kuroshite@kajukatli ~]$ rfkill ID TYPE DEVICE SOFT HARD 1 wlan dell-wifi unblocked unblocked 2 wlan phy0 unblocked unblocked 4 nfc nfc0 unblocked unblocked
north gorge
.aw Bluetooth
trim quartzBOT
smoky crypt
.aw Bluetooth
i cannot figure out the problem
fair wagon
you might need some firmware.
check the web for "1704 bluetooth"
can also check the journal for clues:
journalctl -x -b -p 4
smoky crypt
you might need some firmware.
check the web for "1704 bluetooth"
can also check...
i can't find a driver for linux
can you help me
north gorge
i cannot figure out the problem
Send system specs. You may be missing Linux-firmware and Bluetooth related packages
Nice pfp btw
smoky crypt
Nice pfp btw
thanks
flat wolfBOT
Sam✦ 🌙 received a thank you cookie!
fair wagon
you might need some firmware.
check the web for "1704 bluetooth"
can also check...
@smoky crypt can you send the output of journal?
smoky crypt
<@457081170908151818> can you send the output of journal?
[kuroshite@kajukatli ~]$ journalctl -x -b -p 4 May 08 14:32:04 kajukatli kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: > May 08 14:32:04 kajukatli kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/l> May 08 14:32:04 kajukatli kernel: #3 May 08 14:32:04 kajukatli kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance' May 08 14:32:04 kajukatli kernel: hpet_acpi_add: no address or irqs in _CRS May 08 14:32:04 kajukatli kernel: usb 1-1.5: config 0 descriptor?? May 08 14:32:04 kajukatli kernel: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found May 08 14:32:04 kajukatli kernel: i8042: Warning: Keylock active May 08 14:32:04 kajukatli kernel: memfd_create() without MFD_EXEC nor MFD_NOEXEC_SEAL, pid=1 'systemd' May 08 14:32:04 kajukatli systemd-gpt-auto-generator[201]: Refusing to automatically mount uncommon file system 'LVM2_membe> May 08 14:32:04 kajukatli (sd-execu[194]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator failed with exit st> May 08 14:32:05 kajukatli systemd-udevd[244]: Configuration file /usr/lib/udev/rules.d/60-libfprint-2-device-broadcom.rules> May 08 14:32:05 kajukatli lvm[307]: PV /dev/sda4 online, VG archlinux is complete. May 08 14:32:05 kajukatli lvm[307]: VG archlinux finished May 08 14:32:05 kajukatli lvm[306]: PV /dev/sda5 online, VG archlinux is complete. May 08 14:32:05 kajukatli lvm[306]: VG archlinux finished
fair wagon
the firmware seems fine.
but if you do not have the linux-firmware package installed, get it.
smoky crypt
the firmware seems fine.
but if you do not have the linux-firmware package insta...
Okay
blueman isn't opening now
fair wagon
`[kuroshite@kajukatli ~]$ journalctl -x -b -p 4
May 08 14:32:04 kajukatli kernel...
doesn't seem to be any related errrors.
do you have the ucode package?
intel or amd cpu?
fair wagon
blueman isn't opening now
systemctl status bluetooth.service
smoky crypt
`systemctl status bluetooth.service`
`[kuroshite@kajukatli ~]$ systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
Active: active (running) since Mon 2023-05-08 16:58:52 IST; 1 day 3h ago
Docs: man:bluetoothd(8)
Main PID: 15009 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 9394)
Memory: 816.0K
CPU: 58ms
CGroup: /system.slice/bluetooth.service
└─15009 /usr/lib/bluetooth/bluetoothd
May 08 16:58:52 kajukatli systemd[1]: Starting Bluetooth service...
May 08 16:58:52 kajukatli bluetoothd[15009]: Bluetooth daemon 5.66
May 08 16:58:52 kajukatli systemd[1]: Started Bluetooth service.
May 08 16:58:52 kajukatli bluetoothd[15009]: Starting SDP server`
fair wagon
ok, make sure you have intel-ucode too
fair wagon
blueman isn't opening now
does bluetoothctl run?
smoky crypt
ok, make sure you have intel-ucode too
installed it just now
smoky crypt
does `bluetoothctl` run?
yes
smoky crypt
does `bluetoothctl` run?
but sadly
[kuroshite@kajukatli ~]$ bluetoothctl Agent registered [bluetooth]# scan on No default controller available
fair wagon
list in bluetoothctl?
fair wagon
ok, there is indeed no bluetooth device detected on your system
smoky crypt
ok, there is indeed no bluetooth device detected on your system
how to make it detect it
02:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43142 802.11b/g/n (rev 01) Subsystem: Dell Wireless 1704 802.11n + BT 4.0 Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at f7d00000 (64-bit, non-prefetchable) [size=32K] Capabilities: <access denied> Kernel driver in use: wl Kernel modules: bcma, wl
it says BT 4.0 here
and it is also turned on in the bios
i believe it was working in windows
fair wagon
can you make sure your /boot is mounted and do mkinitcpio -p linux (if you are using the default linux kernel)
let's see if there are "missing firmware" listed there
searching for your device name, this is in the only relevant issue i found:
I have found the problem. bluetooth-mesh.service was also enabled and running and that created a conflict.
smoky crypt
can you make sure your /boot is mounted and do `mkinitcpio -p linux` (if you are...
ok i'm running it
it says generation successful 🙂
fair wagon
any warnings for missing firmware?
smoky crypt
any warnings for missing firmware?
yes
fair wagon
list the names of the missing firmware modules, so we keep that in mind
smoky crypt
==> WARNING: Possibly missing firmware for module: 'ast' ==> WARNING: Possibly missing firmware for module: 'xhci_pci' ==> WARNING: consolefont: no font found in configuration ==> WARNING: Possibly missing firmware for module: 'aic94xx' ==> WARNING: Possibly missing firmware for module: 'bfa' ==> WARNING: Possibly missing firmware for module: 'qed' ==> WARNING: Possibly missing firmware for module: 'qla1280' ==> WARNING: Possibly missing firmware for module: 'qla2xxx' ==> WARNING: Possibly missing firmware for module: 'wd719x'
fair wagon
ok.
now like that other issue, let's see if there could be conflicting services:
pstree -T | grep -i blu
smoky crypt
ok.
now like that other issue, let's see if there could be conflicting services:...
[kuroshite@kajukatli ~]$ pstree -T | grep -i blu |-bluetoothd | |-blueman-applet | |-blueman-tray | |-kitty---bash-+-bluetoothctl
fair wagon
that seems fine too
smoky crypt
;-;
fair wagon
`==> WARNING: Possibly missing firmware for module: 'ast'
==> WARNING: Possibly ...
and these seem unrelated
:(
smoky crypt
and these seem unrelated
:(
oh
where to look for the culprit
i stopped the bluetooth-mesh service you were talking about.
nothing really happened.
smoky crypt
nope
fair wagon
but in any case, the device would be seen in bluetoothctl (and rfkill for that matter)
sudo dmesg | grep -i blue
trying to find some clue
smoky crypt
`sudo dmesg | grep -i blue`
do i send the output?
fair wagon
please, if not too long
smoky crypt
please, if not too long
eh
[kuroshite@kajukatli ~]$ sudo dmesg | grep -i blue [ 2044.733051] Bluetooth: Core ver 2.22 [ 2044.733077] NET: Registered PF_BLUETOOTH protocol family [ 2044.733089] Bluetooth: HCI device and connection manager initialized [ 2044.733093] Bluetooth: HCI socket layer initialized [ 2044.733095] Bluetooth: L2CAP socket layer initialized [ 2044.733098] Bluetooth: SCO socket layer initialized [ 2090.795331] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 2090.795338] Bluetooth: BNEP filters: protocol multicast [ 2090.795344] Bluetooth: BNEP socket layer initialized [20088.999482] Modules linked in: snd_hrtimer cdc_mbim cdc_wdm cdc_ncm cdc_ether usbnet mii bnep btusb btrtl btbcm btintel btmtk bluetooth ecdh_generic crc16 snd_seq_dummy snd_seq snd_seq_device intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_ctl_led snd_hda_codec_realtek irqbypass snd_hda_codec_generic snd_hda_codec_hdmi crct10dif_pclmul uvcvideo crc32_pclmul snd_hda_intel polyval_clmulni pn544_mei polyval_generic mei_phy gf128mul snd_intel_dspcfg videobuf2_vmalloc pn544 ghash_clmulni_intel uvc snd_intel_sdw_acpi sha512_ssse3 spi_nor hci aesni_intel videobuf2_memops crypto_simd snd_hda_codec mtd mei_pxp videobuf2_v4l2 cryptd dell_laptop wl(POE) nfc mei_wdt mei_hdcp 8021q garp rapl mrp snd_hda_core stp spi_intel_platform iTCO_wdt llc dell_wmi intel_cstate snd_hwdep dell_smm_hwmon intel_pmc_bxt dell_smbios ppdev at24 spi_intel iTCO_vendor_support mei_me cfg80211 snd_pcm videodev ledtrig_audio dcdbas snd_timer i2c_i801 wmi_bmof pcspkr sparse_keymap mei intel_uncore e1000e
fair wagon
it is not even showing in rfkill...
but there seems to not be a firmware issue.
smoky crypt
ok
fair wagon
can you try this:
lsmod | grep -i dell-laptop
smoky crypt
can you try this:
`lsmod | grep -i dell-laptop`
it returns nothing
fair wagon
there seems to be an issue with dual booting windows making the device un-seen in linux
sudo modprobe dell-laptop
any messages?
smoky crypt
ok
smoky crypt
`sudo modprobe dell-laptop`
any messages?
none (just asked for a pw)
fair wagon
rfkill what does it show now?
smoky crypt
`rfkill` what does it show now?
[kuroshite@kajukatli ~]$ rfkill ID TYPE DEVICE SOFT HARD 1 wlan dell-wifi unblocked unblocked 2 wlan phy0 unblocked unblocked 8 nfc nfc0 unblocked unblocked
fair wagon
what's the laptop model? let's check if any info specific to it exists
smoky crypt
what's the laptop model? let's check if any info specific to it exists
Latitude E7240 01
smoky crypt
what's the laptop model? let's check if any info specific to it exists
were you able to find any
fair wagon
not really, specific to the device.
but there seems to be an AUR package with bluetooth drivers for the card:
https://aur.archlinux.org/packages/broadcom-bt-firmware-git
want to try installing that?
smoky crypt
i have actually
smoky crypt
💀
fair wagon
maybe a BIOS update?
fair wagon
check bios updates for your laptop, do it (will need to do from Windows probably)
i can't think of anything else, the device does not exist at all for your linux system
smoky crypt
check bios updates for your laptop, do it (will need to do from Windows probably...
i have pirated windows
the native one, it was replaced
fair wagon
i have pirated windows
only good way to get windows (:
fair wagon
why? sometimes it is important to update BIOS
upto you though.
not sure it will help anyway
smoky crypt
are there any other possibilities
maybe it broke? how to check
oh then it shouldn't work on windows
let me try just in case
fair wagon
you can check if it still runs in windows.
then maybe try disabling / powering off the device in windows, then booting linux again.
fair wagon
maybe the disabling in windows does something proper to the device, alleviating the issue
smoky crypt
no signs in windows xO
bios shows it tho
smoky crypt
no signs in windows xO
bios shows it tho
@fair wagon
fair wagon
are you still averse to a bios update? :D
also, is secure boot enabled in bios?
smoky crypt
are you still averse to a bios update? :D
also, is secure boot enabled in bios?
uhm i don't want to do it for nothing
nor do i want to break anything. i can't afford it.
and no, secure boot is disabled.
fair wagon
try fixing it in windows first then.
a bluetooth driver update from dell website?
is your wifi working flawlessly btw?
smoky crypt
yes
fair wagon
you could also try turning it off and on again in bios.
smoky crypt
ok
fair wagon
turn it off. save and exit bios. pc power off. pc power on. turn it on.
smoky crypt
ok
smoky crypt
turn it off. save and exit bios. pc power off. pc power on. turn it on.
still nothing
i checked both on arch and win
i ran the bt troubleshooter and it shows this:
fair wagon
has it worked before?
