You are not logged in.

#1 2021-03-21 17:03:28

shoelesshunter
Member
Registered: 2014-05-18
Posts: 152

help with bluetooth

I am new to bluetooth.

I enabled and started the service, but bluetoothctl hangs waiting for bluetoothd.

'systemctl status bluetooth' says:

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: inactive (dead)
       Docs: man:bluetoothd(8)

Mar 21 08:28:33 kyzer systemd[1]: Condition check resulted in Bluetooth service being skipped.
Mar 21 09:00:36 kyzer systemd[1]: Condition check resulted in Bluetooth service being skipped.

Where do I start to troubleshoot this? I am using KDE if it makes a difference. bluedevil is installed.

It is not blocked by rfkill.

Offline

#2 2021-03-21 22:23:55

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 12,716

Re: help with bluetooth

Check kernel logs, is btusb properly loaded? Condition check result means that /sys/class/bluetooth is not present which it should be if the kernel detected and set up a working bluetooth device.

Offline

#3 2021-03-23 00:08:29

shoelesshunter
Member
Registered: 2014-05-18
Posts: 152

Re: help with bluetooth

 dmesg | grep btusb 

yielded no hits.

 modprobe btusb

says

 modprobe: FATAL: Module btusb not found in directory /lib/modules/5.11.7-zen1-1-zen

Offline

#4 2021-03-23 22:24:42

shoelesshunter
Member
Registered: 2014-05-18
Posts: 152

Re: help with bluetooth

'modprobe btusb' did the trick. it works fine after a reboot.

Offline

#5 2021-04-05 23:15:20

shoelesshunter
Member
Registered: 2014-05-18
Posts: 152

Re: help with bluetooth

I put

#bluetooth

btusb

in my /etc/modules-load.d/

but I still have to manually modprobe the driver. It's not auto-loading

Offline

#6 2021-04-06 04:29:37

jonno2002
Member
Registered: 2016-11-21
Posts: 162

Re: help with bluetooth

does it happen with the standard arch kernel as well ?

Offline

#7 2021-04-06 07:09:13

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 12,716

Re: help with bluetooth

Do you have TLP or some power-saving daemon enabled that's configured to disable/unload bluetooth ?

Moving to Kernel & HW since this appears to be lower level than applications.

Last edited by V1del (2021-04-06 16:24:22)

Offline

#8 2021-04-06 20:29:45

seth
Member
Registered: 2012-09-03
Posts: 20,480

Re: help with bluetooth

shoelesshunter wrote:

I put

#bluetooth

btusb

in my /etc/modules-load.d/

but I still have to manually modprobe the driver. It's not auto-loading

Where exactly did you add those lines?
/etc/modules-load.d is a directory and the file has to be named somethingsomething.conf

Offline

#9 2021-04-06 23:49:20

shoelesshunter
Member
Registered: 2014-05-18
Posts: 152

Re: help with bluetooth

sorry. I wasn't clear.

the lines are in a file named btusb.conf in the modules-load.d directory.

Offline

#10 2021-04-07 06:35:54

seth
Member
Registered: 2012-09-03
Posts: 20,480

Re: help with bluetooth

Please post the file (eg. to ix.io - don't copy and paste it) and your system journal.

Offline

#11 2021-04-07 17:46:55

shoelesshunter
Member
Registered: 2014-05-18
Posts: 152

Re: help with bluetooth

#bluetooth

btusb

that's my btusb.conf

my systemctl -xb

journalctl -xb
-- Journal begins at Tue 2021-03-09 18:16:56 CST, ends at Wed 2021-04-07 12:42:31 CDT. --
Apr 05 21:35:10 kyzer kernel: Linux version 5.11.11-zen1-1-zen (linux-zen@archlinux) (gcc (GCC) 10.2.0, GNU ld (G>
Apr 05 21:35:10 kyzer kernel: Command line: BOOT_IMAGE=/vmlinuz-linux-zen root=UUID=b2a5afa0-8145-426f-bae8-74d26>
Apr 05 21:35:10 kyzer kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Apr 05 21:35:10 kyzer kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Apr 05 21:35:10 kyzer kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Apr 05 21:35:10 kyzer kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Apr 05 21:35:10 kyzer kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Apr 05 21:35:10 kyzer kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Apr 05 21:35:10 kyzer kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Apr 05 21:35:10 kyzer kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Apr 05 21:35:10 kyzer kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted'>
Apr 05 21:35:10 kyzer kernel: BIOS-provided physical RAM map:
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000086e86fff] usable
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x0000000086e87000-0x0000000087786fff] reserved
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x0000000087787000-0x000000009d99dfff] usable
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x000000009d99e000-0x000000009db9dfff] type 20
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x000000009db9e000-0x000000009e59dfff] reserved
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x000000009e59e000-0x000000009ec8dfff] ACPI NVS
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x000000009ec8e000-0x000000009ed0dfff] ACPI data
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x000000009ed0e000-0x000000009ed0efff] usable
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x000000009ed0f000-0x000000009fffffff] reserved
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x00000000ff600000-0x00000000ffffffff] reserved
Apr 05 21:35:10 kyzer kernel: BIOS-e820: [mem 0x0000000100000000-0x000000045dffffff] usable
Apr 05 21:35:10 kyzer kernel: NX (Execute Disable) protection: active
Apr 05 21:35:10 kyzer kernel: efi: EFI v2.60 by INSYDE Corp.
Apr 05 21:35:10 kyzer kernel: efi: ACPI=0x9ed0d000 ACPI 2.0=0x9ed0d014 TPMFinalLog=0x9e575000 SMBIOS=0x9dd50000 S>
Apr 05 21:35:10 kyzer kernel: SMBIOS 3.0.1 present.
Apr 05 21:35:10 kyzer kernel: DMI: LENOVO 81LK/LNVNB161216, BIOS BGCN33WW 11/24/2020
Apr 05 21:35:10 kyzer kernel: tsc: Detected 2400.000 MHz processor
Apr 05 21:35:10 kyzer kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Apr 05 21:35:10 kyzer kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Apr 05 21:35:10 kyzer kernel: last_pfn = 0x45e000 max_arch_pfn = 0x400000000
Apr 05 21:35:10 kyzer kernel: MTRR default type: write-back
Apr 05 21:35:10 kyzer kernel: MTRR fixed ranges enabled:
Apr 05 21:35:10 kyzer kernel:   00000-9FFFF write-back
Apr 05 21:35:10 kyzer kernel:   A0000-BFFFF uncachable
Apr 05 21:35:10 kyzer kernel:   C0000-FFFFF write-protect
Apr 05 21:35:10 kyzer kernel: MTRR variable ranges enabled:
Apr 05 21:35:10 kyzer kernel:   0 base 00C0000000 mask 7FC0000000 uncachable
Apr 05 21:35:10 kyzer kernel:   1 base 00A0000000 mask 7FE0000000 uncachable
Apr 05 21:35:10 kyzer kernel:   2 base 2000000000 mask 6000000000 uncachable
Apr 05 21:35:10 kyzer kernel:   3 base 1000000000 mask 7000000000 uncachable
Apr 05 21:35:10 kyzer kernel:   4 base 0800000000 mask 7800000000 uncachable
Apr 05 21:35:10 kyzer kernel:   5 base 4000000000 mask 4000000000 uncachable
Apr 05 21:35:10 kyzer kernel:   6 disabled
Apr 05 21:35:10 kyzer kernel:   7 disabled
Apr 05 21:35:10 kyzer kernel:   8 disabled
Apr 05 21:35:10 kyzer kernel:   9 disabled
Apr 05 21:35:10 kyzer kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
Apr 05 21:35:10 kyzer kernel: last_pfn = 0x9ed0f max_arch_pfn = 0x400000000
Apr 05 21:35:10 kyzer kernel: esrt: Reserving ESRT space from 0x000000009dd4cb98 to 0x000000009dd4cc20.
Apr 05 21:35:10 kyzer kernel: check: Scanning 1 areas for low memory corruption
Apr 05 21:35:10 kyzer kernel: Using GB pages for direct mapping
Apr 05 21:35:10 kyzer kernel: Secure boot could not be determined
Apr 05 21:35:10 kyzer kernel: RAMDISK: [mem 0x3213b000-0x35094fff]

Offline

#12 2021-04-07 17:51:27

shoelesshunter
Member
Registered: 2014-05-18
Posts: 152

Re: help with bluetooth

V1del wrote:

Do you have TLP or some power-saving daemon enabled that's configured to disable/unload bluetooth ?

Moving to Kernel & HW since this appears to be lower level than applications.

I am not using tlp. This is a laptop however.

Offline

#13 2021-04-07 19:22:21

seth
Member
Registered: 2012-09-03
Posts: 20,480

Re: help with bluetooth

seth wrote:

Please post the file (eg. to ix.io - don't copy and paste it) and your system journal.

And that's at best the head of the system journal… (and useless)
Please see the tip in the first link in my signature.

Offline

#14 2021-04-14 02:52:21

shoelesshunter
Member
Registered: 2014-05-18
Posts: 152

Re: help with bluetooth

systemd says module btusb is deny-listed

https://pastebin.com/c2XzSndw

Offline

#15 2021-04-14 05:44:06

seth
Member
Registered: 2012-09-03
Posts: 20,480

Re: help with bluetooth

Well, why did you blacklist it?

Offline

#16 2021-04-15 20:11:43

shoelesshunter
Member
Registered: 2014-05-18
Posts: 152

Re: help with bluetooth

I didn't. In fact, it is listed in /etc/modules-load.d

Offline

#17 2021-04-15 20:15:05

seth
Member
Registered: 2012-09-03
Posts: 20,480

Re: help with bluetooth

systemd thinks you do…

ls /{etc,usr/lib}/modprobe.d /{etc,usr/lib}/modules-load.d
cat /{etc,usr/lib}/modprobe.d/*

Offline

#18 2021-04-28 21:24:55

shoelesshunter
Member
Registered: 2014-05-18
Posts: 152

Re: help with bluetooth

ls /{etc,usr/lib}/modprobe.d /{etc,usr/lib}/modules-load.d ls /{etc,usr/lib}/modprobe.d /{etc,usr/lib}/modules-load.d
/etc/modprobe.d:
rtl8761usb.conf

/etc/modules-load.d:
btusb.conf

/usr/lib/modprobe.d:
bluetooth-usb.conf  nvdimm-security.conf  nvidia.conf  nvidia-dkms.conf  README  systemd.conf  thinkpad_acpi.conf

/usr/lib/modules-load.d:
bluez.conf  cdemu.conf  cdrecord.conf  fwupd-msr.conf  virtualbox-host-dkms.conf

Offline

#19 2021-04-29 02:22:30

shoelesshunter
Member
Registered: 2014-05-18
Posts: 152

Re: help with bluetooth

any ideas? I am still loading the kernel module manually for bluetooth to start.

Offline

#20 2021-04-29 07:27:40

seth
Member
Registered: 2012-09-03
Posts: 20,480

Re: help with bluetooth

seth wrote:
cat /{etc,usr/lib}/modprobe.d/*

Offline

#21 2021-05-01 02:44:15

shoelesshunter
Member
Registered: 2014-05-18
Posts: 152

Re: help with bluetooth

seth wrote:
seth wrote:
cat /{etc,usr/lib}/modprobe.d/*

cat: '/etc/modprobe.d/*': No such file or directory

# use "reset=1" as default, since it should be safe for recent devices and
# solves all kind of problems.
options btusb reset=1
install libnvdimm /usr/bin/ndctl load-keys ; /sbin/modprobe --ignore-install libnvdimm $CMDLINE_OPTS
blacklist nouveau
blacklist nouveau
systemd System and Service Manager

DETAILS:
        http://0pointer.de/blog/projects/systemd.html

WEB SITE:
        https://www.freedesktop.org/wiki/Software/systemd

GIT:
        git@github.com:systemd/systemd.git
        https://github.com/systemd/systemd

MAILING LIST:
        https://lists.freedesktop.org/mailman/listinfo/systemd-devel

IRC:
        #systemd on irc.freenode.org

BUG REPORTS:
        https://github.com/systemd/systemd/issues

AUTHOR:
        Lennart Poettering
        Kay Sievers
        ...and many others

LICENSE:
        LGPLv2.1+ for all code
        - except src/basic/MurmurHash2.c which is Public Domain
        - except src/basic/siphash24.c which is CC0 Public Domain
        - except src/journal/lookup3.c which is Public Domain
        - except src/udev/* which is (currently still) GPLv2, GPLv2+
        - except tools/chromiumos/* which is BSD-style

REQUIREMENTS:
        Linux kernel >= 3.13
        Linux kernel >= 4.2 for unified cgroup hierarchy support
        Linux kernel >= 5.4 for signed Verity images support

        Kernel Config Options:
          CONFIG_DEVTMPFS
          CONFIG_CGROUPS (it is OK to disable all controllers)
          CONFIG_INOTIFY_USER
          CONFIG_SIGNALFD
          CONFIG_TIMERFD
          CONFIG_EPOLL
          CONFIG_UNIX (it requires CONFIG_NET, but every other flag in it is not necessary)
          CONFIG_SYSFS
          CONFIG_PROC_FS
          CONFIG_FHANDLE (libudev, mount and bind mount handling)

        Kernel crypto/hash API
          CONFIG_CRYPTO_USER_API_HASH
          CONFIG_CRYPTO_HMAC
          CONFIG_CRYPTO_SHA256

        udev will fail to work with the legacy sysfs layout:
          CONFIG_SYSFS_DEPRECATED=n

        Legacy hotplug slows down the system and confuses udev:
          CONFIG_UEVENT_HELPER_PATH=""

        Userspace firmware loading is not supported and should
        be disabled in the kernel:
          CONFIG_FW_LOADER_USER_HELPER=n

        Some udev rules and virtualization detection relies on it:
          CONFIG_DMIID

        Support for some SCSI devices serial number retrieval, to
        create additional symlinks in /dev/disk/ and /dev/tape:
          CONFIG_BLK_DEV_BSG

        Required for PrivateNetwork= in service units:
          CONFIG_NET_NS
        Note that systemd-localed.service and other systemd units use
        PrivateNetwork so this is effectively required.

        Required for PrivateUsers= in service units:
          CONFIG_USER_NS

        Optional but strongly recommended:
          CONFIG_IPV6
          CONFIG_AUTOFS4_FS
          CONFIG_TMPFS_XATTR
          CONFIG_{TMPFS,EXT4_FS,XFS,BTRFS_FS,...}_POSIX_ACL
          CONFIG_SECCOMP
          CONFIG_SECCOMP_FILTER (required for seccomp support)
          CONFIG_CHECKPOINT_RESTORE (for the kcmp() syscall)

        Required for CPUShares= in resource control unit settings
          CONFIG_CGROUP_SCHED
          CONFIG_FAIR_GROUP_SCHED

        Required for CPUQuota= in resource control unit settings
          CONFIG_CFS_BANDWIDTH

        Required for IPAddressDeny= and IPAddressAllow= in resource control
        unit settings
          CONFIG_CGROUP_BPF

        For UEFI systems:
          CONFIG_EFIVAR_FS
          CONFIG_EFI_PARTITION

        Required for signed Verity images support:
          CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG

        We recommend to turn off Real-Time group scheduling in the
        kernel when using systemd. RT group scheduling effectively
        makes RT scheduling unavailable for most userspace, since it
        requires explicit assignment of RT budgets to each unit whose
        processes making use of RT. As there's no sensible way to
        assign these budgets automatically this cannot really be
        fixed, and it's best to disable group scheduling hence.
           CONFIG_RT_GROUP_SCHED=n

        It's a good idea to disable the implicit creation of networking bonding
        devices by the kernel networking bonding module, so that the
        automatically created "bond0" interface doesn't conflict with any such
        device created by systemd-networkd (or other tools). Ideally there
        would be a kernel compile-time option for this, but there currently
        isn't. The next best thing is to make this change through a modprobe.d
        drop-in. This is shipped by default, see modprobe.d/systemd.conf.

        Required for systemd-nspawn:
          CONFIG_DEVPTS_MULTIPLE_INSTANCES or Linux kernel >= 4.7

        Required for systemd-oomd:
          CONFIG_PSI

        Note that kernel auditing is broken when used with systemd's
        container code. When using systemd in conjunction with
        containers, please make sure to either turn off auditing at
        runtime using the kernel command line option "audit=0", or
        turn it off at kernel compile time using:
          CONFIG_AUDIT=n
        If systemd is compiled with libseccomp support on
        architectures which do not use socketcall() and where seccomp
        is supported (this effectively means x86-64 and ARM, but
        excludes 32-bit x86!), then nspawn will now install a
        work-around seccomp filter that makes containers boot even
        with audit being enabled. This works correctly only on kernels
        3.14 and newer though. TL;DR: turn audit off, still.

        glibc >= 2.16
        libcap
        libmount >= 2.30 (from util-linux)
                (util-linux *must* be built without --enable-libmount-support-mtab)
        libseccomp >= 2.3.1 (optional)
        libblkid >= 2.24 (from util-linux) (optional)
        libkmod >= 15 (optional)
        PAM >= 1.1.2 (optional)
        libcryptsetup (optional), >= 2.3.0 required for signed Verity images support
        libaudit (optional)
        libacl (optional)
        libfdisk >= 2.33 (from util-linux) (optional)
        libselinux (optional)
        liblzma (optional)
        liblz4 >= 1.3.0 / 130 (optional)
        libzstd >= 1.4.0 (optional)
        libgcrypt (optional)
        libqrencode (optional)
        libmicrohttpd (optional)
        libpython (optional)
        libidn2 or libidn (optional)
        gnutls >= 3.1.4 (optional, >= 3.6.0 is required to support DNS-over-TLS with gnutls)
        openssl >= 1.1.0 (optional, required to support DNS-over-TLS with openssl)
        elfutils >= 158 (optional)
        polkit (optional)
        tzdata >= 2014f (optional)
        pkg-config
        gperf
        docbook-xsl (optional, required for documentation)
        xsltproc    (optional, required for documentation)
        python-lxml (optional, required to build the indices)
        python >= 3.5
        meson >= 0.46 (>= 0.49 is required to build position-independent executables)
        ninja
        gcc, awk, sed, grep, m4, and similar tools

        During runtime, you need the following additional
        dependencies:

        util-linux >= v2.27.1 required
        dbus >= 1.4.0 (strictly speaking optional, but recommended)
                NOTE: If using dbus < 1.9.18, you should override the default
                policy directory (--with-dbuspolicydir=/etc/dbus-1/system.d).
        dracut (optional)
        polkit (optional)

        To build in directory build/:
          meson setup build/ && meson compile -C build/

        Any configuration options can be specified as -Darg=value... arguments
        to meson. After the build directory is initially configured, meson will
        refuse to run again, and options must be changed with:
          meson configure -Darg=value build/
        meson configure without any arguments will print out available options and
        their current values.

        Useful commands:
          meson compile -v -C build/ some/target
          meson test -C build/
          sudo meson install -C build/
          DESTDIR=... meson install -C build/

        A tarball can be created with:
          git archive --format=tar --prefix=systemd-222/ v222 | xz > systemd-222.tar.xz

        When systemd-hostnamed is used, it is strongly recommended to
        install nss-myhostname to ensure that, in a world of
        dynamically changing hostnames, the hostname stays resolvable
        under all circumstances. In fact, systemd-hostnamed will warn
        if nss-myhostname is not installed.

        nss-systemd must be enabled on systemd systems, as that's required for
        DynamicUser= to work. Note that we ship services out-of-the-box that
        make use of DynamicUser= now, hence enabling nss-systemd is not
        optional.

        Note that the build prefix for systemd must be /usr. (Moreover,
        packages systemd relies on — such as D-Bus — really should use the same
        prefix, otherwise you are on your own.) -Dsplit-usr=false (which is the
        default and does not need to be specified) is the recommended setting.
        -Dsplit-usr=true can be used to give a semblance of support for systems
        with programs installed split between / and /usr. Moving everything
        under /usr is strongly encouraged.

        Additional packages are necessary to run some tests:
        - busybox            (used by test/TEST-13-NSPAWN-SMOKE)
        - nc                 (used by test/TEST-12-ISSUE-3171)
        - python3-pyparsing
        - python3-evdev      (used by hwdb parsing tests)
        - strace             (used by test/test-functions)
        - capsh              (optional, used by test-execute)

USERS AND GROUPS:
        Default udev rules use the following standard system group
        names, which need to be resolvable by getgrnam() at any time,
        even in the very early boot stages, where no other databases
        and network are available:

        audio, cdrom, dialout, disk, input, kmem, kvm, lp, render, tape, tty, video

        During runtime, the journal daemon requires the
        "systemd-journal" system group to exist. New journal files will
        be readable by this group (but not writable), which may be used
        to grant specific users read access. In addition, system
        groups "wheel" and "adm" will be given read-only access to
        journal files using systemd-tmpfiles.service.

        The journal remote daemon requires the
        "systemd-journal-remote" system user and group to
        exist. During execution this network facing service will drop
        privileges and assume this uid/gid for security reasons.

        Similarly, the network management daemon requires the
        "systemd-network" system user and group to exist.

        Similarly, the name resolution daemon requires the
        "systemd-resolve" system user and group to exist.

        Similarly, the coredump support requires the
        "systemd-coredump" system user and group to exist.

NSS:
        systemd ships with four glibc NSS modules:

        nss-myhostname resolves the local hostname to locally configured IP
        addresses, as well as "localhost" to 127.0.0.1/::1.

        nss-resolve enables DNS resolution via the systemd-resolved DNS/LLMNR
        caching stub resolver "systemd-resolved".

        nss-mymachines enables resolution of all local containers registered
        with machined to their respective IP addresses.

        nss-systemd enables resolution of users/group registered via the
        User/Group Record Lookup API (https://systemd.io/USER_GROUP_API),
        including all dynamically allocated service users. (See the
        DynamicUser= setting in unit files.)

        To make use of these NSS modules, please add them to the "hosts:",
        "passwd:" and "group:" lines in /etc/nsswitch.conf. The "resolve"
        module should replace the glibc "dns" module in this file (and don't
        worry, it chain-loads the "dns" module if it can't talk to resolved).

        The four modules should be used in the following order:

                passwd: compat systemd
                group: compat systemd
                hosts: files mymachines resolve [!UNAVAIL=return] dns myhostname

SYSV INIT.D SCRIPTS:
        When calling "systemctl enable/disable/is-enabled" on a unit which is a
        SysV init.d script, it calls /usr/lib/systemd/systemd-sysv-install;
        this needs to translate the action into the distribution specific
        mechanism such as chkconfig or update-rc.d. Packagers need to provide
        this script if you need this functionality (you don't if you disabled
        SysV init support).

        Please see src/systemctl/systemd-sysv-install.SKELETON for how this
        needs to look like, and provide an implementation at the marked places.

WARNINGS:
        systemd will warn during early boot if /usr is not already mounted at
        this point (that means: either located on the same file system as / or
        already mounted in the initrd). While in systemd itself very little
        will break if /usr is on a separate, late-mounted partition, many of
        its dependencies very likely will break sooner or later in one form or
        another. For example, udev rules tend to refer to binaries in /usr,
        binaries that link to libraries in /usr or binaries that refer to data
        files in /usr. Since these breakages are not always directly visible,
        systemd will warn about this, since this kind of file system setup is
        not really supported anymore by the basic set of Linux OS components.

        systemd requires that the /run mount point exists. systemd also
        requires that /var/run is a symlink to /run.

        For more information on this issue consult
        https://www.freedesktop.org/wiki/Software/systemd/separate-usr-is-broken

        To run systemd under valgrind, compile with meson option
        -Dvalgrind=true and have valgrind development headers installed
        (i.e. valgrind-devel or equivalent). Otherwise, false positives will be
        triggered by code which violates some rules but is actually safe. Note
        that valgrind generates nice output only on exit(), hence on shutdown
        we don't execve() systemd-shutdown.

STABLE BRANCHES AND BACKPORTS:
        Stable branches with backported patches are available in the
        systemd-stable repo at https://github.com/systemd/systemd-stable.

        Stable branches are started for certain releases of systemd and named
        after them, e.g. v238-stable. Stable branches are managed by
        distribution maintainers on an as needed basis. See
        https://www.freedesktop.org/wiki/Software/systemd/Backports/ for some
        more information and examples.

ENGINEERING AND CONSULTING SERVICES:
        Kinvolk (https://kinvolk.io) offers professional engineering
        and consulting services for systemd. Please contact Chris Kühl
        <chris@kinvolk.io> for more information.
#  SPDX-License-Identifier: LGPL-2.1-or-later
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# When bonding module is loaded, it creates bond0 by default due to max_bonds
# option default value 1. This interferes with the network configuration
# management / networkd, as it is not possible to detect whether this bond0 was
# intentionally configured by the user, or should be managed by
# networkd/NM/etc. Therefore disable bond0 creation.

options bonding max_bonds=0

# Do the same for dummy0.

options dummy numdummies=0
options thinkpad_acpi fan_control=1

Offline

#22 2021-05-01 06:27:03

seth
Member
Registered: 2012-09-03
Posts: 20,480

Re: help with bluetooth

What happened to "rtl8761usb.conf"?

What if you comment away "options btusb reset=1"?

Offline

Board footer

Powered by FluxBB