| 1 |
On 2021-07-03 13:59+0200 Tamer Higazi <th982a@××××××××××.com> wrote: |
| 2 |
|
| 3 |
> Hi |
| 4 |
> |
| 5 |
> The problem is that the bluetooth circuit seems to be damaged, as I |
| 6 |
> have recently the same result on Windows (not only on linux. |
| 7 |
> |
| 8 |
> At Windows, I can deactivate the hardware at the "device manager", I |
| 9 |
> want this the same to be done on Linux. |
| 10 |
> |
| 11 |
> Not the driver, just to ignore the hardware. |
| 12 |
> Why do I ask this ? |
| 13 |
> |
| 14 |
> I ordered now a new bluetooth 5 stick, what if it uses the same |
| 15 |
> driver ? So loading the driver should not be suppressed more the |
| 16 |
> hardware should be ignored.... |
| 17 |
|
| 18 |
If the broken bluetooth device is attached via USB (turns up in |
| 19 |
`lsusb`), you can disable it via udev: |
| 20 |
<https://projectgus.com/2014/09/blacklisting-a-single-usb-device-from-linux/>. |
| 21 |
|
| 22 |
Kind regards, tastytea |
| 23 |
|
| 24 |
-- |
| 25 |
Get my PGP key with `gpg --locate-keys tastytea@××××××××.de` or at |
| 26 |
<https://tastytea.de/tastytea.asc>. |
Archives