Failed to start discovery org bluez error notready

The problem

• I was able to create the bluetooth integration via UI
• on startup, the integration crashes
  
• restarting HA or rebooting the host (Raspberry Pi 4) does not change anything

What version of Home Assistant Core has the issue?

core-2022.12.1

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

bluetooth

Link to integration documentation on our website

https://www.home-assistant.io/integrations/bluetooth/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

2022-12-09 16:49:08.473 DEBUG (MainThread) [homeassistant.components.bluetooth.scanner] Initializing bluetooth scanner with {'detection_callback': <bound method HaScanner._async_detection_callback of <homeassistant.components.bluetooth.scanner.HaScanner object at 0x7f808f2440>>, 'scanning_mode': 'active', 'adapter': 'hci0'}
2022-12-09 16:49:08.476 DEBUG (MainThread) [homeassistant.components.bluetooth.scanner] hci0 (DC:A6:32:F6:AB:EC): Starting bluetooth discovery attempt: (1/3)
2022-12-09 16:49:08.482 DEBUG (MainThread) [homeassistant.components.bluetooth.scanner] hci0 (DC:A6:32:F6:AB:EC): adapter stopped responding; executing reset
2022-12-09 16:49:08.483 DEBUG (MainThread) [bluetooth_auto_recovery.recover] Power cycling Bluetooth adapter hci0
2022-12-09 16:49:08.489 DEBUG (MainThread) [btsocket.btmgmt_protocol] Encoding cmd_code as type CmdCode
2022-12-09 16:49:08.489 DEBUG (MainThread) [btsocket.btmgmt_protocol] Encoding controller_idx as type Controller
2022-12-09 16:49:08.493 DEBUG (MainThread) [btsocket.btmgmt_protocol] Encoding param_len as type ParamLen
2022-12-09 16:49:08.495 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding event_code as type EvtCode
2022-12-09 16:49:08.497 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding controller_idx as type Controller
2022-12-09 16:49:08.500 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding param_len as type ParamLen
2022-12-09 16:49:08.502 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding command_opcode as type CmdCode
2022-12-09 16:49:08.503 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding status as type Status
2022-12-09 16:49:08.504 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding num_controllers as type IntUL
2022-12-09 16:49:08.506 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding controller_index[i] as type IntUL
2022-12-09 16:49:08.507 DEBUG (MainThread) [btsocket.btmgmt_protocol] Socket Read: <event_code=CommandCompleteEvent, controller_idx=65535, param_len=7> <command_opcode=ReadControllerIndexList, status=Success> <num_controllers=1, controller_index[i]=[0]>
2022-12-09 16:49:08.508 DEBUG (MainThread) [btsocket.btmgmt_protocol] Encoding cmd_code as type CmdCode
2022-12-09 16:49:08.510 DEBUG (MainThread) [btsocket.btmgmt_protocol] Encoding controller_idx as type Controller
2022-12-09 16:49:08.512 DEBUG (MainThread) [btsocket.btmgmt_protocol] Encoding param_len as type ParamLen
2022-12-09 16:49:08.514 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding event_code as type EvtCode
2022-12-09 16:49:08.515 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding controller_idx as type Controller
2022-12-09 16:49:08.516 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding param_len as type ParamLen
2022-12-09 16:49:08.517 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding command_opcode as type CmdCode
2022-12-09 16:49:08.519 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding status as type Status
2022-12-09 16:49:08.520 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding address as type Address
2022-12-09 16:49:08.522 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding bluetooth_version as type IntUL
2022-12-09 16:49:08.523 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding manufacturer as type IntUL
2022-12-09 16:49:08.524 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding supported_settings as type IntUL
2022-12-09 16:49:08.525 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding current_settings as type CurrentSettings
2022-12-09 16:49:08.525 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding class_of_device as type IntUL
2022-12-09 16:49:08.526 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding name as type Name
2022-12-09 16:49:08.527 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding short_name as type IntUL
2022-12-09 16:49:08.527 DEBUG (MainThread) [btsocket.btmgmt_protocol] Socket Read: <event_code=CommandCompleteEvent, controller_idx=0, param_len=283> <command_opcode=ReadControllerInformation, status=Success> <address=DC:A6:32:F6:AB:EC, bluetooth_version=9, manufacturer=305, supported_settings=114431, current_settings={Powered: False, Connectable: False, FastConnectable: False, Discoverable: False, Bondable: False, LinkLevelSecurity: False, SecureSimplePairing: True, BREDR: True, HighSpeed: False, LowEnergy: True, Advertising: False, SecureConnections: True, DebugKeys: False, Privacy: False, ControllerConfiguration: False, StaticAddress: False, PHYConfiguration: False, WidebandSpeech: False}, class_of_device=0, name=b'homeassistant', short_name=0>
2022-12-09 16:49:08.529 DEBUG (MainThread) [bluetooth_auto_recovery.recover] Response(header=<event_code=CommandCompleteEvent, controller_idx=0, param_len=283>, event_frame=<command_opcode=ReadControllerInformation, status=Success>, cmd_response_frame=<address=DC:A6:32:F6:AB:EC, bluetooth_version=9, manufacturer=305, supported_settings=114431, current_settings={Powered: False, Connectable: False, FastConnectable: False, Discoverable: False, Bondable: False, LinkLevelSecurity: False, SecureSimplePairing: True, BREDR: True, HighSpeed: False, LowEnergy: True, Advertising: False, SecureConnections: True, DebugKeys: False, Privacy: False, ControllerConfiguration: False, StaticAddress: False, PHYConfiguration: False, WidebandSpeech: False}, class_of_device=0, name=b'homeassistant', short_name=0>)
2022-12-09 16:49:08.530 DEBUG (MainThread) [btsocket.btmgmt_protocol] Encoding cmd_code as type CmdCode
2022-12-09 16:49:08.531 DEBUG (MainThread) [btsocket.btmgmt_protocol] Encoding controller_idx as type Controller
2022-12-09 16:49:08.532 DEBUG (MainThread) [btsocket.btmgmt_protocol] Encoding param_len as type ParamLen
2022-12-09 16:49:08.536 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding event_code as type EvtCode
2022-12-09 16:49:08.536 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding controller_idx as type Controller
2022-12-09 16:49:08.538 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding param_len as type ParamLen
2022-12-09 16:49:08.539 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding command_opcode as type CmdCode
2022-12-09 16:49:08.540 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding status as type Status
2022-12-09 16:49:08.540 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding address as type Address
2022-12-09 16:49:08.541 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding bluetooth_version as type IntUL
2022-12-09 16:49:08.541 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding manufacturer as type IntUL
2022-12-09 16:49:08.541 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding supported_settings as type IntUL
2022-12-09 16:49:08.541 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding current_settings as type CurrentSettings
2022-12-09 16:49:08.542 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding class_of_device as type IntUL
2022-12-09 16:49:08.542 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding name as type Name
2022-12-09 16:49:08.543 DEBUG (MainThread) [btsocket.btmgmt_protocol] Decoding short_name as type IntUL
2022-12-09 16:49:08.545 DEBUG (MainThread) [btsocket.btmgmt_protocol] Socket Read: <event_code=CommandCompleteEvent, controller_idx=0, param_len=283> <command_opcode=ReadControllerInformation, status=Success> <address=DC:A6:32:F6:AB:EC, bluetooth_version=9, manufacturer=305, supported_settings=114431, current_settings={Powered: False, Connectable: False, FastConnectable: False, Discoverable: False, Bondable: False, LinkLevelSecurity: False, SecureSimplePairing: True, BREDR: True, HighSpeed: False, LowEnergy: True, Advertising: False, SecureConnections: True, DebugKeys: False, Privacy: False, ControllerConfiguration: False, StaticAddress: False, PHYConfiguration: False, WidebandSpeech: False}, class_of_device=0, name=b'homeassistant', short_name=0>
2022-12-09 16:49:08.547 DEBUG (MainThread) [bluetooth_auto_recovery.recover] Current power state of bluetooth adapter hci0 is OFF, trying to turn it back ON
2022-12-09 16:49:08.547 DEBUG (MainThread) [btsocket.btmgmt_protocol] Encoding powered as type IntUL
2022-12-09 16:49:08.548 DEBUG (MainThread) [btsocket.btmgmt_protocol] Encoding cmd_code as type CmdCode
2022-12-09 16:49:08.549 DEBUG (MainThread) [btsocket.btmgmt_protocol] Encoding controller_idx as type Controller
2022-12-09 16:49:08.551 DEBUG (MainThread) [btsocket.btmgmt_protocol] Encoding param_len as type ParamLen
2022-12-09 16:49:13.556 WARNING (MainThread) [bluetooth_auto_recovery.recover] Bluetooth adapter hci0 could not be reset due to timeout
2022-12-09 16:49:13.560 DEBUG (MainThread) [bluetooth_auto_recovery.recover] Executing USB reset for Bluetooth adapter hci0
2022-12-09 16:49:13.565 DEBUG (MainThread) [bluetooth_auto_recovery.recover] hci0 is not a USB devices while attempting USB reset: ttyS0 is not a USB device
2022-12-09 16:49:13.565 DEBUG (MainThread) [homeassistant.components.bluetooth.scanner] hci0 (DC:A6:32:F6:AB:EC): adapter reset result: False
2022-12-09 16:49:13.565 DEBUG (MainThread) [homeassistant.components.bluetooth.scanner] hci0 (DC:A6:32:F6:AB:EC): Starting bluetooth discovery attempt: (2/3)
2022-12-09 16:49:13.568 DEBUG (MainThread) [homeassistant.components.bluetooth.scanner] hci0 (DC:A6:32:F6:AB:EC): BleakError while starting bluetooth; attempt: (2/3): [org.bluez.Error.NotReady] Resource Not Ready
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/bluetooth/scanner.py", line 228, in _async_start
    await self.scanner.start()  # type: ignore[no-untyped-call]
  File "/usr/local/lib/python3.10/site-packages/bleak/__init__.py", line 156, in start
    await self._backend.start()
  File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/scanner.py", line 191, in start
    self._stop = await manager.active_scan(
  File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/manager.py", line 357, in active_scan
    assert_reply(reply)
  File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/utils.py", line 20, in assert_reply
    raise BleakDBusError(reply.error_name, reply.body)

Additional information

Environment:
Raspberry 4 (64 bit) with Home Assistant Operating System 9.3 (Supervisor 2022.11.2)

Linux Mint Forums

Welcome to the Linux Mint forums!

Failed to connect: org.bluez.Error.NotReady (Bluetooth)

Failed to connect: org.bluez.Error.NotReady (Bluetooth)

Post by Tropical » Mon Feb 08, 2021 12:30 am

While trying to connect a Bluetooth speaker, I played with Bluetooth related installation/uninstallation (tray icon, bluez, blueman).

As a result:
— the Bluetooth tray icon disappeared;
— when trying to connect bluetooth via bluetoothctl to other devices (phone in this case), I get this kind of error:

User details:
non-native English speaker

System details:
Linux Mint 20.2 Cinnamon
Kernel 5.11.0-36-generic

Re: Failed to connect: org.bluez.Error.NotReady (Bluetooth)

Post by mikeflan » Tue Feb 16, 2021 5:55 pm

Re: Failed to connect: org.bluez.Error.NotReady (Bluetooth)

Post by Tropical » Tue Feb 23, 2021 11:33 pm

Installed Blueman, Bluetooth works now,

Blueman icon appears only when I launch it.

I would like to understand how to make the original Bluetooth icon to appear on startup (either Blueman or the original installed app).
I remember clicking on the status icon and uninstalling it, but I don’t know its program name.

I did this mistake because I was trying to make a Bluetooth speaker work. That is another thread:
(Excuse me the dirt typing. What language/syntax should I use in the Insert link button?)
viewtopic.php?f=49&t=342092&p=1967589#p1967589

User details:
non-native English speaker

System details:
Linux Mint 20.2 Cinnamon
Kernel 5.11.0-36-generic

Re: Failed to connect: org.bluez.Error.NotReady (Bluetooth)

Post by hglee » Wed Feb 24, 2021 12:45 am

Open a Terminal (Ctrl-Alt-T), then copy-and-paste these three command-lines, one at a time.

Источник

Arch Linux

You are not logged in.

#1 2015-07-30 03:14:03

Bluetooth not connecting with blutoothctl

I am having trouble connecting to a bluetooth->serial adapter (HC05) even though I can see the device and pair with it.

.. and when I try to connect:

I have made sure I am part of the «lp» group.
Any idea’s welcome. Thanks.

journlctl shows this error on restarting the bluetooth service ..

Last edited by bmentink (2015-07-30 03:17:53)

#2 2015-07-30 03:49:08

Re: Bluetooth not connecting with blutoothctl

Did you power up the host’s carrier?

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#3 2015-07-30 04:12:27

Re: Bluetooth not connecting with blutoothctl

Yes, it says : Failed to connect: org.bluez.Error.NotReady if you don’t power on, my message is different.

Last edited by bmentink (2015-07-30 04:13:19)

#4 2015-07-30 04:24:59

Re: Bluetooth not connecting with blutoothctl

You’re right. Can you connect to other (non-serial) classes of Bluetooth devices?
Did the rfcomm kernel module load?

Nothing is too wonderful to be true, if it be consistent with the laws of nature — Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. — Alan Turing
—
How to Ask Questions the Smart Way

#5 2015-07-30 04:57:04

Re: Bluetooth not connecting with blutoothctl

You’re right. Can you connect to other (non-serial) classes of Bluetooth devices?
Did the rfcomm kernel module load?

I tried connecting to my TV:

It seems to have connected even though it says not. (I am guessing the prompt reflects connection?)
However, If I pair with the device and then connect, I get the same as the oroginal error ..

Источник

Org bluez error notready

I’m having problems with a Bluetooth keyboard, and BT in general, on an up-to-date Retropie installation where it previously worked fine. No changes of note have been made. Hardware is a Raspberry Pi 3 (original model)

Within EmulationStation, in the RetroPie | Bluetooth configuration tool, the bluetooth keyboard which previously worked is still registered, but will no longer pair.

‘Register and Connect to Bluetooth device’ returns:

A previously working Xbone One S controller (which I unpaired a while ago) is not detected by this process.

It is not possible to remove the existing entry via
‘Remove Bluetooth device’ (no error is shown, but the entry persists).

Bluetooth is not disabled in /boot/config.txt

At the command line, after exiting ES, I uninstalled and reinstalled bluetooth, then rebooted. This made no difference:

Via ssh, using bluetoothctl , a similar error is returned:
org.bluez.Error.NotReady

Discovery via scan on
and removal of the existing entry, both fail:

The hcitool cannot be used, however the hciuart.service is enabled and active:

[Edit: added test for bluetooth.service]

Returns that the bluetooth service is active, however there are ‘Failed to obtain ha. ‘ and ‘failed to set mode’ entries listed

systemctl status bluetooth.target appears okay:

I’m at a loss here. I cannot recall any recent changes or updates to my installation that could begin to account for the problem, and cannot find the core error mentioned anywhere on retropie.org.uk’s forum.

Can anybody help?

If a post has helped you, please encourage the author by up-voting via the ^ icon located in the bottom-right corner.

RetroResolution.com — Adventures in retro gaming on original hardware and via emulation with RetroPie on the Raspberry Pi.

I’ve now solved the problem. After all the low-level diagnostics, as is often the case, the solution came whilst I was nowhere near the system, and was simple.

I recalled I’d disabled Bluetooth via the lxde Desktop (accessible from the EmulationStation Ports menu, after installation via retropie setup) quite some time ago. The Bluetooth icon on the desktop menu bar was grey; right-clicking allowed me to enable the stack fully.

I’ve no idea why I disabled Bluetooth via the desktop, as I’ve not actively used it since the full reinstall of the current RetroPie on this RPi 3.

I also have no idea exactly what subsystem or service was disabled by this action.

Regardless, after a reboot, the Bluetooth configuration tool, accessed via EmulationStation | RetroPie, then worked exactly as it should. I was able to remove and add the keyboard, connect, and use it with no problems.

Unlikely as it is, maybe these posts will help somebody in the future.

If a post has helped you, please encourage the author by up-voting via the ^ icon located in the bottom-right corner.

RetroResolution.com — Adventures in retro gaming on original hardware and via emulation with RetroPie on the Raspberry Pi.

To auto reconnect Bluetooth device on reboot, the following may be required

create a udev rule for each device, if required

via EmulationStation | RetroPie,
Bluetooth Configuration
select option:
‘Setup udev rule for joypad (required for. 8bitdo. )’

Added
SUBSYSTEM==»input», ATTRS==»Bluetooth 3.0 Keyboard», MODE=»0666″, ENV=»1″
to /etc/udev/rules.d/99-bluetooth.rules

Testing
Reboot, with keyboard powered on and left in connected mode (no led showing): works

reboot, with keyboard powered off; wait for EmulationStation to load; power on keyboard (green led): works

If a post has helped you, please encourage the author by up-voting via the ^ icon located in the bottom-right corner.

RetroResolution.com — Adventures in retro gaming on original hardware and via emulation with RetroPie on the Raspberry Pi.

Hi RR, I had the exact same problem and it was driving me insane. thanks for figuring this out and sharing your solution!

Источник

Bluetooth Integration Fails to Setup/Start Bluetooth Adapter #77992

The problem

This issue was previously reported and marked as closed for 2022.8, but still exists in 2022.9. The Bluetooth adapter fails to initialize with message:

What version of Home Assistant Core has the issue?

What was the last working version of Home Assistant Core?

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Link to integration documentation on our website

Diagnostics information

The option to download diagnostic information did not appear until after running bluetoothctl power off, power on, and scan on in the command line
config_entry-bluetooth-f77680e969acca3b9ab7d010a0f19ff4.json.txt

Example YAML snippet

Anything in the logs that might be useful for us?

The text was updated successfully, but these errors were encountered:

Hey there @bdraco, mind taking a look at this issue as it has been labeled with an integration ( bluetooth ) you are listed as a code owner for? Thanks!
_{(message by CodeOwnersMention)}

I was able to find VMWare’s virtual bluetooth adapter. Someone in the other thread mentioned having trouble with passthrough via VMWare and I wonder if it’s related.

I also have a similar issue, running HA (2022.9) supervised on a Raspberry PI 4. #76544 does not appear fixed yet, but is still giving troubles.

Same for me, a lot of BT devices dead.

same for me 🙁 after updating to 2022.09

I wasn’t able to get it to work before updating to 2022.9, so it’s not a new issue as much as the old one isn’t truly fixed. According to this comment from the previous bug thread, running the commands bluetoothctl power off, power on, and scan on may fix it in some cases. But for me while it made the integration look like it was fixed in the devices & services / integrations page, it is still not working and the same errors keep repeating in the log. BUT doing so did give me the option to download diagnosistics, which I have attached here and in the original post.
config_entry-bluetooth-f77680e969acca3b9ab7d010a0f19ff4.json.txt

Can you use bluetoothctl to connect and pair with a device in range?

Can you use bluetoothctl to connect and pair with a device in range?

Nope. The first time ran bluetoothctl it said «Discovery started», a line with the controller, and two devices. It logged the RSSI’s of those two devices for several lines with the tag [CHG] until it logged the tag [DEL] instead.

Every attempt to run bluetoothctl scan on resulted in just the «Discovery started» line with no additional logging.

I am able to discover and pair devices via the host Windows device, but they do not seem to get shared with Home Assistant. Which makes sense as Home Assistant is still struggling to stably stay connected to the controller according to the logs.

I have the same issue,
interestingly,
after playing with bluetoothctl and refreshing my ‘ha devices GUI, the error state has cleared.
(I’m running 2022.9.2)

@grouts112 but are you still getting errors in the logs? While Home Assistant’s GUI says Bluetooth is working after messing with bluetoothctl, it actually isn’t and I’m still getting the same errors in the log, repeating due to retries.

@Nerwyn I hadn’t looked at logs at all, is there a specific log you see it in ?
I looked at superviser od Core logs and dont see anything
Maybe I am one of the lucky ones that playing with the cli fixed it.

@grouts112 It’s under Settings > System > Logs > Load Full Logs. I get these errors repeating infinitely:

@Nerwyn Hi, no I dont get anything logging there other than a few SyncWorker messages. Nothing todo with Bluetooth.
From your message, your bluetooth adapter doesnt support BLE.
In bluetoothctl,
What do you get when you
‘scan off’
And then ‘scan le’ ?
then ‘scan off’. And
‘scan bredr’

i get no errors at all doing that and it finds my phone on the scan le.

If you get errors,might be worth trying a different Bluetooth dongle?

@grouts112 I’m using this adapter, which both supports Bluetooth LE and is on the Home Assistant Bluetooth list of known working adapters. All of those commands just say «Discovery started/stopped» with no additional logging. I only got additional logging the first time I turned scan on. Every subsequent time just had the discovery message.

I think I figured it out! This seems to be an issue with VMWare’s Bluetooth settings. By disabling Share Bluetooth devices with the virtual machine , under USB Controller in Virtual Machine Settings, I was able to attach the Bluetooth device to the VM like my Zwave dongle, and it just worked! Deleted and reconfigured the Bluetooth integration, and the August/Yale Bluetooth lock was immediately found!

© 2023 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Источник

Failed to start discovery: org.bluez.Error.NotReady #289

Symptom data

1. Does the problem occur on battery or AC or both?
2. Attach the full output of tlp-stat via https://gist.github.com/ for all cases of 1.

Expected behavior

Actual behavior

Steps to reproduce the problem

this is not a laptop its a shuttle pc with assembled parts so on ac always. tlc stat output below
— TLP 1.0 ———————————————

+++ Configured Settings: /etc/default/tlp
TLP_ENABLE=1
TLP_DEFAULT_MODE=AC
TLP_PERSISTENT_DEFAULT=0
DISK_IDLE_SECS_ON_AC=0
DISK_IDLE_SECS_ON_BAT=2
MAX_LOST_WORK_SECS_ON_AC=15
MAX_LOST_WORK_SECS_ON_BAT=60
CPU_HWP_ON_AC=balance_performance
CPU_HWP_ON_BAT=balance_power
SCHED_POWERSAVE_ON_AC=0
SCHED_POWERSAVE_ON_BAT=1
NMI_WATCHDOG=0
ENERGY_PERF_POLICY_ON_AC=performance
ENERGY_PERF_POLICY_ON_BAT=powersave
DISK_DEVICES=»sda sdb»
DISK_APM_LEVEL_ON_AC=»254 254″
DISK_APM_LEVEL_ON_BAT=»128 128″
SATA_LINKPWR_ON_AC=max_performance
SATA_LINKPWR_ON_BAT=min_power
AHCI_RUNTIME_PM_TIMEOUT=15
PCIE_ASPM_ON_AC=performance
PCIE_ASPM_ON_BAT=powersave
RADEON_POWER_PROFILE_ON_AC=high
RADEON_POWER_PROFILE_ON_BAT=low
RADEON_DPM_STATE_ON_AC=performance
RADEON_DPM_STATE_ON_BAT=battery
RADEON_DPM_PERF_LEVEL_ON_AC=auto
RADEON_DPM_PERF_LEVEL_ON_BAT=auto
WIFI_PWR_ON_AC=off
WIFI_PWR_ON_BAT=on
WOL_DISABLE=Y
SOUND_POWER_SAVE_ON_AC=0
SOUND_POWER_SAVE_ON_BAT=1
SOUND_POWER_SAVE_CONTROLLER=Y
BAY_POWEROFF_ON_AC=0
BAY_POWEROFF_ON_BAT=0
BAY_DEVICE=»sr0″
RUNTIME_PM_ON_AC=on
RUNTIME_PM_ON_BAT=auto
USB_AUTOSUSPEND=1
USB_BLACKLIST_BTUSB=0
USB_BLACKLIST_PHONE=0
USB_BLACKLIST_WWAN=1
RESTORE_DEVICE_STATE_ON_STARTUP=0

+++ System Info
System = Shuttle Inc. V1.0 XH170
BIOS = 1.12
Kernel = 4.12.6-1-ARCH #1 SMP PREEMPT Sat Aug 12 09:16:22 CEST 2017 x86_64
/proc/cmdline = BOOT_IMAGE=/vmlinuz-linux root=UUID=cba2b4a0-3663-4522-8ee5-8575a7b96d5a rw quiet resume=UUID=d580a3f7-5548-46fd-98d1-b99e5c42e51c
Init system = systemd
Boot mode = BIOS (CSM, Legacy)

+++ TLP Status
State = enabled
Last run = unknown
Mode = unknown
Power source = unknown

Notice: tlp.service is not enabled — invoke «systemctl enable tlp.service» to correct this!
Notice: tlp-sleep.service is not enabled — invoke «systemctl enable tlp-sleep.service» to correct this!
Notice: systemd-rfkill.service is not masked — invoke «systemctl mask systemd-rfkill.service» to correct this!

+++ Processor
CPU model = Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz

/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver = intel_pstate
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor = powersave
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors = performance powersave
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq = 800000 [kHz]
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq = 3900000 [kHz]
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_preference = balance_power
/sys/devices/system/cpu/cpu0/cpufreq/energy_performance_available_preferences = default performance balance_performance balance_power power

/sys/devices/system/cpu/cpu1/cpufreq/scaling_driver = intel_pstate
/sys/devices/system/cpu/cpu1/cpufreq/scaling_governor = powersave
/sys/devices/system/cpu/cpu1/cpufreq/scaling_available_governors = performance powersave
/sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq = 800000 [kHz]
/sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq = 3900000 [kHz]
/sys/devices/system/cpu/cpu1/cpufreq/energy_performance_preference = balance_power
/sys/devices/system/cpu/cpu1/cpufreq/energy_performance_available_preferences = default performance balance_performance balance_power power

/sys/devices/system/cpu/cpu2/cpufreq/scaling_driver = intel_pstate
/sys/devices/system/cpu/cpu2/cpufreq/scaling_governor = powersave
/sys/devices/system/cpu/cpu2/cpufreq/scaling_available_governors = performance powersave
/sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq = 800000 [kHz]
/sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq = 3900000 [kHz]
/sys/devices/system/cpu/cpu2/cpufreq/energy_performance_preference = balance_power
/sys/devices/system/cpu/cpu2/cpufreq/energy_performance_available_preferences = default performance balance_performance balance_power power

/sys/devices/system/cpu/cpu3/cpufreq/scaling_driver = intel_pstate
/sys/devices/system/cpu/cpu3/cpufreq/scaling_governor = powersave
/sys/devices/system/cpu/cpu3/cpufreq/scaling_available_governors = performance powersave
/sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq = 800000 [kHz]
/sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq = 3900000 [kHz]
/sys/devices/system/cpu/cpu3/cpufreq/energy_performance_preference = balance_power
/sys/devices/system/cpu/cpu3/cpufreq/energy_performance_available_preferences = default performance balance_performance balance_power power

/sys/devices/system/cpu/intel_pstate/min_perf_pct = 21 [%]
/sys/devices/system/cpu/intel_pstate/max_perf_pct = 100 [%]
/sys/devices/system/cpu/intel_pstate/no_turbo = 0
/sys/devices/system/cpu/intel_pstate/turbo_pct = 13 [%]
/sys/devices/system/cpu/intel_pstate/num_pstates = 32

x86_energy_perf_policy: program not installed.

/sys/module/workqueue/parameters/power_efficient = Y
/proc/sys/kernel/nmi_watchdog = 1

+++ Undervolting
PHC kernel not available.

+++ Temperatures
CPU temp = 51 [°C]
Fan speed = (not available)

+++ File System
/proc/sys/vm/laptop_mode = 0
/proc/sys/vm/dirty_writeback_centisecs = 500
/proc/sys/vm/dirty_expire_centisecs = 3000
/proc/sys/vm/dirty_ratio = 20
/proc/sys/vm/dirty_background_ratio = 10

+++ Storage Devices
/dev/sda:
Model = SanDisk Ultra II 480GB
Firmware = X41200RL
APM Level = 128
Status = active/idle
TRIM = supported
Scheduler = deadline

Runtime PM: control = on, autosuspend_delay = -1

+++ SATA Aggressive Link Power Management
/sys/class/scsi_host/host0/link_power_management_policy = max_performance
/sys/class/scsi_host/host1/link_power_management_policy = max_performance
/sys/class/scsi_host/host2/link_power_management_policy = max_performance
/sys/class/scsi_host/host3/link_power_management_policy = max_performance
/sys/class/scsi_host/host4/link_power_management_policy = max_performance
/sys/class/scsi_host/host5/link_power_management_policy = max_performance

+++ AHCI Host Controller Runtime Power Management
/sys/bus/pci/devices/0000:00:17.0/ata1/power/control = on
/sys/bus/pci/devices/0000:00:17.0/ata2/power/control = on
/sys/bus/pci/devices/0000:00:17.0/ata3/power/control = on
/sys/bus/pci/devices/0000:00:17.0/ata4/power/control = on
/sys/bus/pci/devices/0000:00:17.0/ata5/power/control = on
/sys/bus/pci/devices/0000:00:17.0/ata6/power/control = on

+++ PCIe Active State Power Management
/sys/module/pcie_aspm/parameters/policy = default (using bios preferences)

+++ Intel Graphics
/sys/module/i915/parameters/enable_rc6 = 1 (enabled)
/sys/module/i915/parameters/enable_dc = -1 (use per-chip default)
/sys/module/i915/parameters/enable_fbc = 1 (enabled)
/sys/module/i915/parameters/enable_psr = 0 (disabled)
/sys/module/i915/parameters/modeset = 1 (enabled)
/sys/module/i915/parameters/semaphores = 0 (disabled)

+++ Wireless
bluetooth = on
wifi = on
wwan = none (no device)

hci0(btusb) : bluetooth, not connected
wlp1s0(rtl8821ae) : wifi, connected, power management = off

+++ Audio
/sys/module/snd_hda_intel/parameters/power_save = 0
/sys/module/snd_hda_intel/parameters/power_save_controller = Y

+++ Runtime Power Management
Device blacklist = (not configured)
Driver blacklist = amdgpu nouveau nvidia radeon (default)

/sys/bus/pci/devices/0000:00:00.0/power/control = on (0x060000, Host bridge, skl_uncore)
/sys/bus/pci/devices/0000:00:02.0/power/control = on (0x030000, VGA compatible controller, i915)
/sys/bus/pci/devices/0000:00:14.0/power/control = on (0x0c0330, USB controller, xhci_hcd)
/sys/bus/pci/devices/0000:00:16.0/power/control = on (0x078000, Communication controller, mei_me)
/sys/bus/pci/devices/0000:00:17.0/power/control = on (0x010601, SATA controller, ahci)
/sys/bus/pci/devices/0000:00:1c.0/power/control = auto (0x060400, PCI bridge, pcieport)
/sys/bus/pci/devices/0000:00:1f.0/power/control = on (0x060100, ISA bridge, no driver)
/sys/bus/pci/devices/0000:00:1f.2/power/control = on (0x058000, Memory controller, no driver)
/sys/bus/pci/devices/0000:00:1f.3/power/control = on (0x040300, Audio device, snd_hda_intel)
/sys/bus/pci/devices/0000:00:1f.4/power/control = auto (0x0c0500, SMBus, i801_smbus)
/sys/bus/pci/devices/0000:00:1f.6/power/control = on (0x020000, Ethernet controller, e1000e)
/sys/bus/pci/devices/0000:01:00.0/power/control = on (0x028000, Network controller, rtl8821ae)

+++ USB
Autosuspend = enabled
Device whitelist = (not configured)
Device blacklist = (not configured)
Bluetooth blacklist = disabled
Phone blacklist = disabled
WWAN blacklist = enabled

Bus 002 Device 002 ID 2109:0812 control = auto, autosuspend_delay_ms = 0 — VIA Labs, Inc. VL812 Hub (hub)
Bus 002 Device 001 ID 1d6b:0003 control = auto, autosuspend_delay_ms = 0 — Linux Foundation 3.0 root hub (hub)
Bus 001 Device 004 ID 045e:0745 control = on, autosuspend_delay_ms = 2000 — Microsoft Corp. Nano Transceiver v1.0 for Bluetooth (usbhid)
Bus 001 Device 003 ID 13d3:3458 control = auto, autosuspend_delay_ms = 2000 — IMC Networks (btusb)
Bus 001 Device 002 ID 2109:2812 control = auto, autosuspend_delay_ms = 0 — VIA Labs, Inc. VL812 Hub (hub)
Bus 001 Device 001 ID 1d6b:0002 control = auto, autosuspend_delay_ms = 0 — Linux Foundation 2.0 root hub (hub)

+++ Battery Status
No batteries detected.

• Install ethtool to disable Wake On LAN (WOL)
• Install smartmontools for disk drive health info

The text was updated successfully, but these errors were encountered:

Источник

Hi,

[EDIT]

I’m having problems with a Bluetooth keyboard, and BT in general, on an up-to-date Retropie installation where it previously worked fine. No changes of note have been made. Hardware is a Raspberry Pi 3 (original model)

sudo uname -a

returns:

Linux retropie 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux

Within EmulationStation, in the RetroPie | Bluetooth configuration tool, the bluetooth keyboard which previously worked is still registered, but will no longer pair.

‘Register and Connect to Bluetooth device’ returns:

(Creating device failed: org.bluez.Error.AlreadyExists)

A previously working Xbone One S controller (which I unpaired a while ago) is not detected by this process.

It is not possible to remove the existing entry via
‘Remove Bluetooth device’ (no error is shown, but the entry persists).

Bluetooth is not disabled in /boot/config.txt

#disable onboard bluetooth
#dtoverlay=pi3-disable-bt

At the command line, after exiting ES, I uninstalled and reinstalled bluetooth, then rebooted. This made no difference:

sudo apt-get remove pi-bluetooth

sudo apt-get install pi-bluetooth

Via ssh, using bluetoothctl, a similar error is returned:
org.bluez.Error.NotReady

Discovery via scan on
and removal of the existing entry, both fail:

pi@retropie:~ $ bluetoothctl
[NEW] Controller B8:27:EB:AD:FC:96 retropie [default]
[NEW] Device 70:73:00:13:9E:03 Bluetooth 3.0 Keyboard
[bluetooth]# scan on
Failed to start discovery: org.bluez.Error.NotReady

The hcitool cannot be used, however the hciuart.service is enabled and active:

pi@retropie:~ $ hcitool scan
Device is not available: No such device

pi@retropie:~ $ systemctl status hciuart.service
● hciuart.service - Configure Bluetooth Modems connected by U   
Loaded: loaded (/lib/systemd/system/hciuart.service; enabl   
Active: active (running) since Fri 2019-01-11 00:35:21 GMT  
Process: 324 ExecStart=/usr/bin/btuart (code=exited, status 
Main PID: 442 (hciattach)
   CGroup: /system.slice/hciuart.service
           └─442 /usr/bin/hciattach /dev/serial1 bcm43xx 9216
Jan 11 00:35:16 retropie systemd[1]: Starting Configure Bluet
Jan 11 00:35:21 retropie btuart[324]: bcm43xx_init
Jan 11 00:35:21 retropie btuart[324]: Flash firmware /lib/fir
Jan 11 00:35:21 retropie btuart[324]: Set BDADDR UART: b8:27:
Jan 11 00:35:21 retropie btuart[324]: Set Controller UART spe
Jan 11 00:35:21 retropie btuart[324]: Device setup complete
Jan 11 00:35:21 retropie systemd[1]: Started Configure Blueto
lines 1-15/15 (END)

[Edit: added test for bluetooth.service]

systemctl status bluetooth.service

Returns that the bluetooth service is active, however there are ‘Failed to obtain ha…’ and ‘failed to set mode’ entries listed

● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; ena   
Active: active (running) since Fri 2019-01-11 00:35:21 GMT     Docs: man:bluetoothd(8)
 Main PID: 447 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─447 /usr/lib/bluetooth/bluetoothd

Jan 11 00:35:21 retropie systemd[1]: Starting Bluetooth servi
Jan 11 00:35:21 retropie bluetoothd[447]: Bluetooth daemon 5.
Jan 11 00:35:21 retropie systemd[1]: Started Bluetooth servic
Jan 11 00:35:21 retropie bluetoothd[447]: Starting SDP server
Jan 11 00:35:21 retropie bluetoothd[447]: Bluetooth managemen
Jan 11 00:35:21 retropie bluetoothd[447]: Failed to obtain ha
Jan 11 00:35:21 retropie bluetoothd[447]: Sap driver initiali
Jan 11 00:35:21 retropie bluetoothd[447]: sap-server: Operati
Jan 11 00:35:21 retropie bluetoothd[447]: Failed to set mode:
Jan 11 00:35:21 retropie bluetoothd[447]: Endpoint registeredlines 1-19/19 (END)

systemctl status bluetooth.target appears okay:

● bluetooth.target - Bluetooth
   Loaded: loaded (/lib/systemd/system/bluetooth.target; stat   
Active: active since Fri 2019-01-11 00:35:21 GMT; 56min ag     
Docs: man:systemd.special(7)

Jan 11 00:35:21 retropie systemd[1]: Reached target Bluetoothlines 1-6/6 (END)...skipping...
● bluetooth.target - Bluetooth
   Loaded: loaded (/lib/systemd/system/bluetooth.target; stat   
Active: active since Fri 2019-01-11 00:35:21 GMT; 56min ag    
 Docs: man:systemd.special(7)

Jan 11 00:35:21 retropie systemd[1]: Reached target Bluetooth~

I’m at a loss here. I cannot recall any recent changes or updates to my installation that could begin to account for the problem, and cannot find the core error mentioned anywhere on retropie.org.uk’s forum.

Can anybody help?