Power cable unplug saved my day too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859592
Title:
Bluetooth unavailable after updates - Reading Intel version
information failed (-110)
To manage
Power cable unplug also did the trick for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859592
Title:
Bluetooth unavailable after updates - Reading Intel version
information failed (-110)
Power cable unplug as comment #2
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/comments/2
did the trick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859592
Title:
Bluetooth
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: rashmitha 1751 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on
Also had an issue with Bluetooth (Fedora): GUI says it was off but
"systemctl status bluetooth" says it is enabled, active, and running.
Found this thread after running "dmesg" and finding that same error:
"Reading Intel version information failed".
Pulling out the power cable (while the machine
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu65.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gad1821 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.04
Lsusb:
Bus 002 Device 001: ID
Hi,
I am having the same issue, with a TP Link Archer Tx50e (which uses
Intel AX200). On boot logs:
[8.084096] Bluetooth: hci0: command 0xfc05 tx timeout
[8.084101] Bluetooth: hci0: Reading Intel version information failed (-110)
[8.084110] Bluetooth: hci0: Intel Read version failed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859592
Title:
Bluetooth unavailable after updates - Reading Intel version
This patch may help, please give it a try:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=8bf7111b4bda00ae82e2de0cd871af997c3f2e9b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Caio Brandolim Rovetta (caiorovetta)
** Changed in: linux (Ubuntu)
Status: Confirmed => New
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu50.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ravi 2111 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.10
HibernationDevice:
I've also had this issue - twice - caused by leaving my desktop in
standby for > 24hrs (can't say the exact duration). Cold booting after
ensuring residual current has been expelled from the system has fixed it
on both occasions.
It sounds like #1905214. My hardware is also
Network controller
I had the same problem after a suspend/resume cycle => bluetooth was not
working with the message `hci0: Reading Intel version information failed
(-110)` in the syslog.
For me the kernel parameter `btusb.enable_autosuspend=0` fixed this problem.
--
You received this bug notification because
Hi, can someone help... Cold boot is not working for me I am
getting Failed to send firmware data (-38)
$ dmesg | grep -i bluetooth
[5.985839] Bluetooth: Core ver 2.22
[5.985858] Bluetooth: HCI device and connection manager initialized
[5.985864] Bluetooth: HCI socket
Cold boot as in powering off from PC's source button worked (taking
electricity off the mother board) worked for me.
Just shutting down and having the motherboard LEDs on didn't work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If there is a need for additional debug info, this bug is currently
affecting me and I am free to provide any logs neccessary.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859592
Title:
Bluetooth
** Changed in: linux (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859592
Title:
Bluetooth unavailable after updates - Reading Intel version
information
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859592
Title:
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859592
I came here from this link
https://askubuntu.com/questions/1231074/ubuntu-20-04-bluetooth-not-
working/1237801 cold rebooting from windows then booting back into
Ubuntu fixed the problem. is there any update on fixing the switching in
between Windows and Ubuntu while using Bluetooth devices?
--
I'm happy to report that it seems to work with kernel mainline 5.7. I do
get the error, but it works without having to cold boot the system at
least.
5.7.14-050714-generic #202008070831 SMP Fri Aug 7 08:34:53 UTC 2020
[5.291451] nvidia-gpu :01:00.3: i2c timeout error e000
[
I also encountered this issue, with ubuntu 18.04 and intel AX200NGW
Bluetooth. Would be willing to help provide debugging logs if needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859592
Title:
For me as well, the power cable did the trick. Thank you!
As mentioned in this comment above:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/comments/2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc6/
** Changed in: linux (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@vicamo I'm experiencing this as well. Ie. only a cold boot will fix it.
Is there anything I can do to help debug this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859592
Title:
Bluetooth
@Redsandro, any cold boot and only cold boot will Intel reload fw and
print fw filename. We know it rarely happens, and that's why we're eager
to know what hardware variant do you have.
@Ian, you can modprobe btusb alone and it will also load btintel as
well. ~lazy engineer.
--
You received
I too am having this problem after a suspend/resume [deep].
Kubuntu 18.04 (nearly up to date patches (20200424)
dmesg:
[285163.220315] Bluetooth: hci0: command 0xfc05 tx timeout
[285163.220316] Bluetooth: hci0: Reading Intel version information failed (-110)
To restart the BT adapter a
@vicamo any cold boot, right? Not specifically after having this error?
For the moment I'm working at home because of reasons, but one of these
weeks I'll be at the office (computer) again. But the error itself is
pretty rare.
I'm also encouraging @mizzao to `apport-collect 1859592`
--
You
Please do run `apport-collect 1859592` after a cold boot to submit logs
because Intel bluetooth may only reload fwd after that, and only when it
probes fw we may know its hw variant.
** Tags added: bluetooth
** Tags removed: bluetooth
** Tags added: hwe-bluetooth
--
You received this bug
@mizzao that sounds a lot like my "solution" comments/2 indeed. However,
during hot reboots on my dual boot setup, the Bluetooth DID work in
Windows for me, but not in Linux. For Linux, a cold boot was required.
So I am inclined to believe that the Linux Bluetooth driver puts the
Bluetooth
I also had this issue, which first manifested by bluetoothd being
completely unresponsive and being unkillable, even with SIGKILL. The
whole system would lag at regular intervals.
After a hot reboot (no power cycle), the lag went away but it was
impossible to activate bluetooth and dmesg showed
Thank you Terry
Your soloution was perfect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859592
Title:
Bluetooth unavailable after updates - Reading Intel version
information failed (-110)
To
thanks for following up on this
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859592
Title:
Bluetooth unavailable after updates
I read from previous bugs and forums on the internet that people seem to
think this is BIOS _update_ related. Things don't just break from one
day to the next because you suddenly need a firmware update. I tried a
couple of things like going to BIOS and loading default settings. Save.
Reboot. No
34 matches
Mail list logo
