Hi @mts,
Well, the chroot can help because there you can find out why it’s not working. That’s what the logs are for, after all. So please provide the output of the following, when tun in the chroot environment:
journalctl --priority=warning..crit --no-pager --boot=-1
Where:
- The
--priority=warning..errargument limits the output to warnings and errors only; - and the
--no-pagerformats the output nicely for use here, on the forum; - the
--boot=-1argument limits the output to log messages from the previous boot. This can be adjusted to-2for the boot before that,-3to the boot before that, and so on and so forth.
Tip 
When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:
```
pasted text
```
Or three (3) tilde signs, like this:
~~~
pasted text
~~~
This will just cause it to be rendered like this:
Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.
Instead of like this:
Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.
Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.
Thereby increasing legibility thus making it easier for those trying to provide assistance.
For more information, please see:
![]()
Additionally
If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:
LC_ALL=C bluetoothctl
This will just cause the terminal output to be in English, making it easier to understand and debug.