Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Maybe you are missing the correct firmware package as your dmesg is saying "failed to load firmware". Do you know what device you have? Can you see it in lspci for example? Did you check the firmware folder if the config file is there or anywhere else?
The firmware package you mention does seems to say it supports the card seen by the kernel.
This is probably new hardware? Perhaps you need a newer version of the package.
Head_on_a_Stick wrote:Have you tried a newer kernel?
Is it not dangerous? I need a stable system.
if you use the backported one, it is relatively safe, since the backporting team attempts to make newer packages that are compatible with the old packages on Debian 9. Your alternative is to wait for Debian 10 to come out (in a few months). You can also have both the old kernel from Debian 9 and the the backported one installed at the same time (in Debian 9). Then you can select which one to use from grub on boot (if you test it and see that it works but are not willing to go fully with the new kernel).
bluetoothctl
[NEW] Controller 30:D1:6B:4B:5C:95 sos [default]
[NEW] Device DB:F4:69:58:DB:CE DJ1200BT
[bluetooth]# help
Available commands:
list List available controllers
show [ctrl] Controller information
select <ctrl> Select default controller
devices List available devices
paired-devices List paired devices
power <on/off> Set controller power
pairable <on/off> Set controller pairable mode
discoverable <on/off> Set controller discoverable mode
agent <on/off/capability> Enable/disable agent with given capability
default-agent Set agent as the default one
advertise <on/off/type> Enable/disable advertising with given type
set-advertise-uuids [uuid1 uuid2 ...] Set advertise uuids
set-advertise-service [uuid][data=[xx xx ...] Set advertise service data
set-advertise-manufacturer [id][data=[xx xx ...] Set advertise manufacturer data
set-advertise-tx-power <on/off> Enable/disable TX power to be advertised
set-scan-filter-uuids [uuid1 uuid2 ...] Set scan filter uuids
set-scan-filter-rssi [rssi] Set scan filter rssi, and clears pathloss
set-scan-filter-pathloss [pathloss] Set scan filter pathloss, and clears rssi
set-scan-filter-transport [transport] Set scan filter transport
set-scan-filter-clear Clears discovery filter.
scan <on/off> Scan for devices
info [dev] Device information
pair [dev] Pair with device
trust [dev] Trust device
untrust [dev] Untrust device
block [dev] Block device
unblock [dev] Unblock device
remove <dev> Remove device
connect <dev> Connect device
disconnect [dev] Disconnect device
list-attributes [dev] List attributes
set-alias <alias> Set device alias
select-attribute <attribute> Select attribute
attribute-info [attribute] Select attribute
read Read attribute value
write <data=[xx xx ...]> Write attribute value
notify <on/off> Notify attribute value
register-profile <UUID ...> Register profile to connect
unregister-profile Unregister profile
version Display version
quit Quit program
[bluetooth]# exit
[DEL] Controller 30:D1:6B:4B:5C:95 sos [default]
/etc/init.d/bluetooth status
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2019-02-01 08:06:18 CET; 5h 35min ago
Docs: man:bluetoothd(8)
Main PID: 521 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CGroup: /system.slice/bluetooth.service
└─521 /usr/lib/bluetooth/bluetoothd
febr 01 08:06:18 sos bluetoothd[521]: Starting SDP server
febr 01 08:06:19 sos bluetoothd[521]: Bluetooth management interface 1.14 i…ized
febr 01 08:06:19 sos bluetoothd[521]: Failed to obtain handles for "Service…stic
febr 01 08:06:19 sos bluetoothd[521]: Sap driver initialization failed.
febr 01 08:06:19 sos bluetoothd[521]: sap-server: Operation not permitted (1)
febr 01 08:06:34 sos bluetoothd[521]: Endpoint registered: sender=:1.44 pat…urce
febr 01 08:06:34 sos bluetoothd[521]: Endpoint registered: sender=:1.44 pat…Sink
febr 01 08:06:59 sos bluetoothd[521]: Endpoint registered: sender=:1.66 pat…urce
febr 01 08:06:59 sos bluetoothd[521]: Endpoint registered: sender=:1.66 pat…Sink
febr 01 08:06:59 sos bluetoothd[521]: RFCOMM server failed for Headset Voic…(98)
Hint: Some lines were ellipsized, use -l to show in full.
pylkko wrote:Yes. The kernel in Debian 9 is 4.9, so if you have 4.19 then it is a 'new kernel'. And notice also the "bpo" in your output which stands for backport.
When will it come out Debian 10? Can this be known?
pylkko wrote:Yes. The kernel in Debian 9 is 4.9, so if you have 4.19 then it is a 'new kernel'. And notice also the "bpo" in your output which stands for backport.
I have update the new kernel my debian-9.7.0-amd64-netinst.iso system. The new debian-9.9.0-amd64-netinst.iso kernel is real both debian-9.7.0-amd64-netinst.iso kernel? The new kernel is only for Debian 10? I would like reinstall my system if be published the new kernel, but if the 9.9 is old kernel, i not reinstall my system. Thanks your answer. Have a nice day!
