davidjharder when running then opening bluetooth option it is showing
03:06:27.1641 cc-bluetooth-panel[ 2815]: MESSAGE: BluetoothHardwareAirplaneMode: 0

my laptop is acer Swift SFX14-41G.

    CommonUser pretty sure that message is normal, I see the same thing.

    what about running dmesg | grep -i blue ?

    Also, was bluetooth working for you before the sync?

      davidjharder when i run dmesg | grep -i blue it is resulting

      [    4.770018] Bluetooth: Core ver 2.22
      [    4.770054] NET: Registered PF_BLUETOOTH protocol family
      [    4.770055] Bluetooth: HCI device and connection manager initialized
      [    4.770059] Bluetooth: HCI socket layer initialized
      [    4.770061] Bluetooth: L2CAP socket layer initialized
      [    4.770065] Bluetooth: SCO socket layer initialized
      [    5.598014] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
      [    5.598029] Bluetooth: BNEP socket layer initialized
      [    6.851558] Bluetooth: hci0: Opcode 0x c03 failed: -110

      for the problem i'm not remember if it occurred from when i using solus 4.3 before, but i sure that after i reinstalling to solus 4.4 it is the bluetooth is not working. is my hardware not supported ? but when i using opensuse timbleweed it is working fine.

        First: Thanks for this awesome distro. It is definitely currently one of the greatest desktop distros out there.

        Updated my packages yesterday and one of the packages was the nvidia driver. Now it doesn't start X anymore. Kernel and Nvidia driver are out of the sync. The kernel module has a different version than the nvidia driver package.

        Please correct that asap. Thanx a lot!

          m1h43l you're going to have to be more specific than that, we have multiple Nvidia drivers and they were all rebuilt after the kernel upgrade

            ReillyBrogan

            From dmsg

            API mismatch: the client has the version 535.86.05, but this kernel module has the version 535.54.03

            uname -a

            Linux mymachine 6.3.12-244.current #1 SMP PREEMPT_DYNAMIC Sat Jul 15 23:23:42 UTC 2023 x86_64 GNU/Linux

              Axios here is my bluetooth device

              checking with lsusb

              Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
              Bus 003 Device 002: ID 1c7a:0575 LighTuning Technology Inc. EgisTec EH575
              Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
              Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
              Bus 001 Device 003: ID 04ca:3802 Lite-On Technology Corp. Wireless_Device
              Bus 001 Device 002: ID 04f2:b6dd Chicony Electronics Co., Ltd HD User Facing
              Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

              checking with command inxi -Eaz

              Bluetooth:
                Device-1: Lite-On Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
                  speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-4:3 chip-ID: 04ca:3802
                  class-ID: e001 serial: <filter>
                Report: rfkill ID: hci0 rfk-id: 2 state: up address: see --recommends

                ReillyBrogan

                ... cannot edit my own post ... wtf...

                eopkg list-installed | grep vidia :

                nvidia-470-glx-driver-modaliases
                nvidia-glx-driver-32bit
                nvidia-glx-driver-common
                nvidia-glx-driver-current
                nvidia-glx-driver-modaliases

                m1h43l Seems like you're booted into the old kernel. The new one is 6.4.8-247. Either your update wasn't complete or something prevents the kernel update from being applied (like a too small ESP partition).

                eopkg remove linux-current
                eopkg install linux-current

                Now it works. Don't know why.

                  m1h43l probably because the package triggers happened again when you installed the package again. You could have achieved the same effect with sudo usysconf run -f

                  CommonUser Acer specs on that show mediatek mt7921
                  How did we get to lite-on are you using external adapter or replaced mt7921?

                  On that note another user had mediatek issues we could not seem to resolve dont know if he ever got it working.
                  I cant find much about lite-on.

                    Axios nope, i didn't using any external bluetooth adapter or replacing it.

                      CommonUser Do from terminal sudo LC_ALL=en-US.UTF8 lspci -vnn
                      and see what it says for network controller.

                        Axios it is showing

                        03:00.0 Network controller [0280]: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter [14c3:7961]
                        	Subsystem: Lite-On Communications Inc MT7921 802.11ax PCI Express Wireless Network Adapter [11ad:3802]
                        	Flags: bus master, fast devsel, latency 0, IRQ 89, IOMMU group 10
                        	Memory at fc02000000 (64-bit, prefetchable) [size=1M]
                        	Memory at fc02100000 (64-bit, prefetchable) [size=16K]
                        	Memory at fc02104000 (64-bit, prefetchable) [size=4K]
                        	Capabilities: [80] Express Endpoint, MSI 00
                        	Capabilities: [e0] MSI: Enable+ Count=1/32 Maskable+ 64bit+
                        	Capabilities: [f8] Power Management version 3
                        	Capabilities: [100] Vendor Specific Information: ID=1556 Rev=1 Len=008 <?>
                        	Capabilities: [108] Latency Tolerance Reporting
                        	Capabilities: [110] L1 PM Substates
                        	Capabilities: [200] Advanced Error Reporting
                        	Kernel driver in use: mt7921e

                          CommonUser Ok it is mediatek not sure bluetooth is going to work like I said earlier
                          Unless somebody knows something I dont.
                          There was a long thread we had about this dont remb the name tho.
                          The users wifi worked fine but his bluetooth wasnt your error code looks similiar to his and it crashed
                          at about the same point if memory is right.
                          Sorry I wasnt of more help we were hopeing kernal updates would fix it.

                          On a note I looked your computer up and that module is easy to replace I would recommend the intel
                          If bluetooth is needed its supported good.

                            Axios aaahh okay got it, thankyou for the information it is helpful, if you not pointed out about that i have no idea what's going on. For the usage of bluetooth it is not that urgent so maybe i can wait till next kernel update available.

                            But one thing i got curious, when i using opensuse tumbleweed i am using the kernel 6.4.3-current if i'm not mistake, and i can use the bluetooth as usual.

                              CommonUser Alright I think I see the issue. Kernel needs some more enablement around that, I'll get it added to the next Solus kernel. Can you please run the following command on your system?

                              eopkg info linux-current

                              And then respond with the output. I can give you early access to the next kernel when I build it. I also need to know whether or not you're using secure boot.

                                ReillyBrogan for the secure boot yes i enable the secure boot from the bios when i'm installing solus 4.4, running eopkg info linux-current resulting

                                Installed package:
                                Name                : linux-current, version: 6.4.8, release: 247
                                Summary             : Linux kernel image and modules (current)
                                Description         : The Linux kernel and modules, the core of the operating
                                                      system
                                Licenses            : GPL-2.0-only
                                Component           : kernel.image
                                Dependencies        : 
                                Distribution        : Solus, Dist. Release: 1
                                Architecture        : x86_64, Installed Size: 150.72 MB
                                Reverse Dependencies: 
                                
                                Package found in Solus repository:
                                Name                : linux-current, version: 6.4.8, release: 247
                                Summary             : Linux kernel image and modules (current)
                                Description         : The Linux kernel and modules, the core of the operating
                                                      system
                                Licenses            : GPL-2.0-only
                                Component           : kernel.image
                                Dependencies        : 
                                Distribution        : Solus, Dist. Release: 1
                                Architecture        : x86_64, Installed Size: 150.72 MB, Package Size: 134.15
                                                      MB
                                Reverse Dependencies: virtualbox-current linux-current-dbginfo
                                                      broadcom-sta-current