[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#812885: marked as done (general: Bluetooth doesn't work)



Your message dated Tue, 28 Jul 2020 15:35:32 +0200
with message-id <2b39b33da255da2462627227962e4ffa4b0e2656.camel@43-1.org>
and subject line Re: general: Bluetooth doesn't work
has caused the Debian Bug report #812885,
regarding general: Bluetooth doesn't work
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
812885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812885
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: general
Severity: normal

Dear Maintainer,

Hello!
	I was trying to make bluetooth work properly,
but I couldn't find a way to do it.
So I hope You will help me, plese.
this appears when system starts up:
[12.695075] bluetooth hci0: firmware: failed to load brcm/BCM43142A0-4ca-2009.hcd (-2)
Please help me fix it.
Best regards,
Justysia

-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

--- End Message ---
--- Begin Message ---
On Wed, 27 Jan 2016 16:49:38 +0100 justysia wrote:
>       I was trying to make bluetooth work properly,
> but I couldn't find a way to do it.
> So I hope You will help me, plese.
> this appears when system starts up:
> [12.695075] bluetooth hci0: firmware: failed to load brcm/BCM43142A0-4ca-2009.hcd (-2)

I'm closing this report as it doesn't look like anyone will investigate
the problem further; it is unclear if this is still a problem in the
current release.

Ansgar

--- End Message ---

Reply to: