Linux-Bluetooth Archive on
 help / color / Atom feed
Subject: [Bug 202515] Bluetooth LE Extended Connect returning Command Disallowed
Date: Fri, 08 Feb 2019 21:39:29 +0000
Message-ID: <> (raw)
In-Reply-To: <>

Mathias Tillman ( changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #17 from Mathias Tillman ( ---
To make a long story short, I've managed to figure it out: the latest firmware
actually fixes it, but for some reason it's not actually loaded on to the
controller until I shut down the computer and leave it off for around 10
seconds or so. A simple reboot isn't enough for it to load the new firmware.

I verified this by doing a cold boot with the distro firmware, copying over the
new firmware then rebooting several times. None of these times was the LE Set
Extended Scan Parameters reported as being supported. I then shut down the
computer and turned it on again after roughly 10 seconds, and after that the
command was reported. I then copied over the distro firmware, rebooted several
times and it was still working. Turned off the computer and on again, and it no
longer worked.

So aside from that odd firmware loading requiring a cold boot, it seems to be
working as expected without a patched kernel.

Thanks for the replies everyone, and sorry for all of the long-winded messages.
I will be marking this as resolved now.

You are receiving this mail because:
You are the assignee for the bug.

      parent reply index

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06  0:01 [Bug 202515] New: " bugzilla-daemon
2019-02-06  8:27 ` [Bug 202515] " bugzilla-daemon
2019-02-06  8:27 ` bugzilla-daemon
2019-02-06  9:07 ` bugzilla-daemon
2019-02-06  9:42 ` bugzilla-daemon
2019-02-06 11:11 ` bugzilla-daemon
2019-02-06 11:11 ` bugzilla-daemon
2019-02-06 11:19 ` bugzilla-daemon
2019-02-06 11:58 ` bugzilla-daemon
2019-02-06 12:18 ` bugzilla-daemon
2019-02-06 19:36 ` bugzilla-daemon
2019-02-07 12:59 ` bugzilla-daemon
2019-02-07 22:55 ` bugzilla-daemon
2019-02-07 23:05 ` bugzilla-daemon
2019-02-07 23:48 ` bugzilla-daemon
2019-02-08 16:16 ` bugzilla-daemon
2019-02-08 17:35 ` bugzilla-daemon
2019-02-08 21:39 ` bugzilla-daemon [this message]

Reply instructions:

You may reply publically 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:

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

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Bluetooth Archive on

Archives are clonable:
	git clone --mirror linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ \
	public-inbox-index linux-bluetooth

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox