linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: mail+bluetooth@m-reimer.de
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Problems with Bluetooth built into BCM4313 WLAN card
Date: Tue, 16 Oct 2018 09:48:57 +0200 (CEST)	[thread overview]
Message-ID: <1681973667.42596.1539676137500@office.mailbox.org> (raw)
In-Reply-To: <50691311-913F-4AB0-AF3A-DD280EC0ECB9@holtmann.org>

Hello,

my acpidump output doesn't seem to have anything about "bluetooth" and I even don't see anything about my BCM4313 card.

About the Wifi chipset, I think it should be Broadcom (BCM4313)

I've tried to load the "thinkpad-acpi" module, but sadly it doesn't detect my ideapad laptop. No way to configure Bluetooth there. I also don't have bluetooth in the BIOS setup to enable it there.

If I'm right, then ACPI/BIOS can somehow block Bluetooth and so even if I get my new card, Bluetooth could still be disabled?

Is there any other way to enable Bluetooth besides booting Windows on this machine to do it there?

Manuel

> Marcel Holtmann <marcel@holtmann.org> hat am 15. Oktober 2018 um 19:25 geschrieben:
> 
> 
> Hi Manuel,
> 
> > I've tried with unblocked bluetooth but don't get anyting in lsusb:
> > 
> > # rfkill list
> > 0: ideapad_wlan: Wireless LAN
> > 	Soft blocked: no
> > 	Hard blocked: no
> > 1: ideapad_bluetooth: Bluetooth
> > 	Soft blocked: no
> > 	Hard blocked: no
> > 3: phy0: Wireless LAN
> > 	Soft blocked: no
> > 	Hard blocked: no
> > [root@manuelslaptop ~]# lsusb
> > Bus 002 Device 003: ID 04f2:b2e2 Chicony Electronics Co., Ltd 
> > Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
> > Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
> > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> > 
> > 
> > The WLAN part is also not the greatest (open source driver).
> > 
> > I've ordered a new card with Atheros chipset some days ago and will try if this solves this issue.
> 
> Then use acpidump etc to look at your ACPI tables and see if a Bluetooth UART device is described there. There is sadly no simple lsacpi to list your devices.
> 
> What is the WiFi chipset anyway? Is this Realtek based or what?
> 
> Regards
> 
> Marcel
>

  reply	other threads:[~2018-10-16  7:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 14:34 Problems with Bluetooth built into BCM4313 WLAN card mail+bluetooth
2018-10-14  8:30 ` Marcel Holtmann
2018-10-15 16:00   ` mail+bluetooth
2018-10-15 17:25     ` Marcel Holtmann
2018-10-16  7:48       ` mail+bluetooth [this message]
2018-10-20  9:29         ` Manuel Reimer
2018-10-20  9:37           ` Manuel Reimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1681973667.42596.1539676137500@office.mailbox.org \
    --to=mail+bluetooth@m-reimer.de \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).