Can’t make bluetooth service to start

Forum Forums Official Releases antiX-21/22 “Grup Yorum” Can’t make bluetooth service to start

  • This topic has 9 replies, 5 voices, and was last updated Feb 5-3:26 am by caprea.
Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #76706
    Member
    skz-

      Hello,

      Maybe someone could help me to identify and fix the issue I’m having here,
      For some reason bluetooth (bluesz) service does not start, as a result (I assume), Bluetooth doesn’t work.
      (not sure how to check the logs for this)

      
      $ sudo service bluetooth status
      bluetooth is not running ... failed!
      skz@linux:~
      $ sudo service bluetooth start
      Starting bluetooth: bluetoothd.
      skz@linux:~
      $ sudo service bluetooth status
      bluetooth is not running ... failed!
      skz@linux:~
      $ sudo service bluetooth restart
      Stopping bluetooth: /usr/sbin/bluetoothd.
      Starting bluetooth: bluetoothd.
      skz@linux:~
      $ sudo service bluetooth status
      bluetooth is not running ... failed!
      skz@linux:~
      $ 
      

      I’ve installed following packages:

      bluez blueman pulseaudio bluetooth pulseaudio-module-bluetooth pavucontrol

      I’ve edit the file: ~/.desktop-session/startup and uncommented: “pulseaudio -D &”

      Running “sudo rfkill”, outputs:

      
      ID TYPE      DEVICE      SOFT      HARD
       0 wlan      phy0   unblocked unblocked
       1 bluetooth hci0   unblocked unblocked
      

      Running “lsusb”, outputs:

      
      Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
      Bus 001 Device 005: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
      Bus 001 Device 004: ID 05e3:0610 Genesys Logic, Inc. Hub
      Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
      Bus 001 Device 002: ID 03f0:034a HP, Inc Elite Keyboard
      Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
      

      Wifi Connection (Conman) – Status – Bluetooth is enabled

      Running Bluetooth manager shows “BlueZ” service is not started.

      • This topic was modified 2 years, 2 months ago by skz-.
      #76709
      Moderator
      caprea

        You have really well prepared already.Might gives hints
        dmesg | grep bluetooth
        inxi --bluetooth

        #76710
        Moderator
        Brian Masinick

          Frankly I think some of the Bluetooth tools or the libraries they use have defects.

          On some distributions they work fine and others are temperamental.

          I got tired of fooling around with it and had difficulty isolating the source of the problems so if someone knows definitively what the typical problems are, I’d still be interested, but meanwhile it’s been working on at least one system so I use that when I need it quickly.

          --
          Brian Masinick

          #76794
          Member
          skz-

            inxi -bluetooth outputs something, but not sure how to proceed with this information, dmesg shows empty output.

            
            $ sudo dmesg | grep bluetooth
            skz@linux:~
            $ inxi --bluetooth
            Bluetooth:
              Device-1: Intel Bluetooth wireless interface type: USB driver: btusb 
              Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: stopped 
              rfk-block: hardware: no software: no address: 58:FB:84:70:19:F7 
            
            #76802
            Forum Admin
            anticapitalista

              Are you using runit or sysVinit version of antiX? Full or base or other?

              Philosophers have interpreted the world in many ways; the point is to change it.

              antiX with runit - leaner and meaner.

              #76804
              Member
              skz-

                Hey,

                antiX-base.
                EDIT: Sorry, forgot to add, SysV.

                
                $ /sbin/init --version
                SysV init version: 2.96
                
                • This reply was modified 2 years, 2 months ago by skz-.
                #76805
                Forum Admin
                anticapitalista

                  sysVinit or runit?

                  Philosophers have interpreted the world in many ways; the point is to change it.

                  antiX with runit - leaner and meaner.

                  #76808
                  Member
                  skz-

                    Sorry, forgot to add,
                    SysV.

                    #76820
                    Anonymous

                      > USB driver: btusb
                      As a troubleshooting step, if you have been booting with the ModernKernel… instead, try booting with LegacyKernel and recheck the result. (or other way ’round)

                      Also, you might try installing bluez-firmware package version from the debian bullseye-backports repository, then [reboot and] retest.

                      Additionally, installing these 2 packages may provide some useful troubleshooting tools//scripts
                      (I’ve never used these; I’m just reporting what I found to be available.)
                      packages.debian.org/bullseye/bluez-test-tools
                      packages.debian.org/bullseye/bluez-test-scripts

                      • This reply was modified 2 years, 2 months ago by Brian Masinick. Reason: From skidoo
                      #76844
                      Moderator
                      caprea

                        And one more thing. It can be ruled out that the bluetooth is switched off in the bios or that there is a hardware defect, yes?
                        Edit: Just seen it’s base. Base only provides one kernel, so you have to install another one for trying.

                      Viewing 10 posts - 1 through 10 (of 10 total)
                      • You must be logged in to reply to this topic.