Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Bluetooth can't receive files from phone
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
jhon987
Apprentice
Apprentice


Joined: 18 Nov 2013
Posts: 229

PostPosted: Tue Dec 04, 2018 8:38 pm    Post subject: Bluetooth can't receive files from phone Reply with quote

Hi,
As the title says I can't get files transferred from my phone to this computer, the motherboard is TUF H370-pro gaming (wi-fi) and according to its specs it comes with Bluetooth® 5.0.
I followed Gentoo's Bluetooth guide to the letter and also even enabled a couple more kernel options just in case (e.g. RFCOMM TTY support=y) and yet files aren't being transferred.

syslog shows the following, possibly related, problems:
Code:
Dec  4 22:12:28 gentoo obexd[3239]: OBEX daemon 5.50
Dec  4 22:12:28 gentoo bluetoothd[2711]: RFCOMM server failed for Message Notification: socket(STREAM, RFCOMM): Protocol not supported (93)
Dec  4 22:12:28 gentoo bluetoothd[2711]: RFCOMM server failed for Message Access: socket(STREAM, RFCOMM): Protocol not supported (93)
Dec  4 22:12:28 gentoo bluetoothd[2711]: RFCOMM server failed for Phone Book Access: socket(STREAM, RFCOMM): Protocol not supported (93)
Dec  4 22:12:28 gentoo bluetoothd[2711]: RFCOMM server failed for Synchronization: socket(STREAM, RFCOMM): Protocol not supported (93)
Dec  4 22:12:28 gentoo bluetoothd[2711]: RFCOMM server failed for File Transfer: socket(STREAM, RFCOMM): Protocol not supported (93)
Dec  4 22:12:28 gentoo bluetoothd[2711]: RFCOMM server failed for Object Push: socket(STREAM, RFCOMM): Protocol not supported (93)


I've installed KDE's bluedevil too.

As I understand rfcomm is a specific protocol - RFCOMM (Protocol used to emulate serial port connections) - wikipedia, and so I have enabled whatever seem relevant to both bluetooth and rfcomm:
Code:
cat /usr/src/linux/.config | grep -i "^config.*\(rfcomm\|bluetooth\|hcid\|sdpd\)"
CONFIG_BT_RFCOMM=y
CONFIG_BT_RFCOMM_TTY=y


Code:
dmesg | grep Bluetooth
[    1.867894] Bluetooth: Core ver 2.22
[    1.867905] Bluetooth: HCI device and connection manager initialized
[    1.867908] Bluetooth: HCI socket layer initialized
[    1.867910] Bluetooth: L2CAP socket layer initialized
[    1.867914] Bluetooth: SCO socket layer initialized
[    1.871966] Bluetooth: hci0: Firmware revision 0.1 build 251 week 16 2018


One thing I noticed by googling is that other people also get this in their boot up:
Code:
dmesg | grep 'Bluetooth'
[ 9.651122] Bluetooth: Core ver 2.15
[ 9.651375] Bluetooth: HCI device and connection manager initialized
[ 9.651378] Bluetooth: HCI socket layer initialized
[ 9.692237] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 502.891750] Bluetooth: L2CAP ver 2.14
[ 502.891755] Bluetooth: L2CAP socket layer initialized
[ 503.021223] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 503.021228] Bluetooth: BNEP filters: protocol multicast
[ 503.170048] Bluetooth: SCO (Voice Link) ver 0.6
[ 503.170054] Bluetooth: SCO socket layer initialized
[ 503.400998] Bluetooth: RFCOMM TTY layer initialized <---
[ 503.401006] Bluetooth: RFCOMM socket layer initialized  <---
[ 503.401009] Bluetooth: RFCOMM ver 1.11   <---


modprobing:
Code:
modprobe rfcomm
modprobe: FATAL: Module rfcomm not found in directory /lib/modules/4.14.83-gentoo

however, both rfcomm settings are compiled straight to the "Bluetooth subsystem support" module and so I assume that's why modprobe finds nothing but I don't understand why it doesn't show in dmesg and whether the protocol is actually relevant for the file transfer?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum