You are not logged in.
Hello,
I just bought a PS3 navigation controller (model CECH-ZCS1M) and I can't seem
to be able to connect it to my laptop Lenovo T400. Please, I will apprecity any help.
I've tried both ASUS USB-BT400 bluetooth dongle and Lenovo T400's integrated bluetooth module.
0.) Formerly the firmware for ASUS dongle was failing to load, complaining about a non-existent "BCM20702A1-0b05-17cb.hcd" file:
[ 2720.574183] Bluetooth: hci0: BCM: chip id 63
[ 2720.606187] Bluetooth: hci0: BCM20702A
[ 2720.608190] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 2720.608230] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0b05-17cb.hcd failed with error -2
[ 2720.608235] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cb.hcd not found
So I copied the BCM20702A1-0b05-17cb.hcd file to "/lib/firmware/brcm/" and now the dmesg seems to be happy:
[ 2277.016550] usb 6-1: new full-speed USB device number 6 using uhci_hcd
[ 2277.206548] Bluetooth: hci0: BCM: chip id 63
[ 2277.238543] Bluetooth: hci0: BCM20702A
[ 2277.240527] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 2277.897599] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1467
[ 2277.928585] Bluetooth: hci0: Broadcom Bluetooth Device
However while the dmesg was complaining, the bluetoothctl command listed the dongle as being ok.
1.) Bluetooth daemon is active:
systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2017-03-02 22:55:03 CET; 29min ago
Docs: man:bluetoothd(8)
Main PID: 310 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 4915)
CGroup: /system.slice/bluetooth.service
└─310 /usr/lib/bluetooth/bluetoothd
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
2.) I always invoke the bluetoothctl command as a user that belongs to the lp group.
A.) I installed bluez-plugins and bluez-utils packages as described in the
PS 3/4 controller section on wiki.
B.) Then I invoked the bluetoothctl command and after connecting my PS3 controller via USB cable,
the command listed it as a device.
C.) Now the blietoothctl output looks like this (at the beginning, my PS3 controller is turned off):
bluetoothctl
[NEW] Controller 50:63:13:C7:8F:FF inferno #2 [default]
[NEW] Device 00:07:04:EF:38:C3 Navigation Controller
[NEW] Controller 5C:F3:70:6C:2E:8B inferno #1
[NEW] Device 00:07:04:EF:38:C3 Navigation Controller
[bluetooth]# select 5C:F3:70:6C:2E:8B
Controller 5C:F3:70:6C:2E:8B inferno #1 [default]
[bluetooth]# show 5C:F3:70:6C:2E:8B
Controller 5C:F3:70:6C:2E:8B
Name: inferno #1
Alias: inferno #1
Class: 0x00010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d052C
Discovering: no
[bluetooth]# info 00:07:04:EF:38:C3
Device 00:07:04:EF:38:C3
Name: Navigation Controller
Alias: Navigation Controller
Class: 0x000508
Icon: input-gaming
Paired: no
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Human Interface Device... (00001124-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: usb:v054Cp0268d0100
[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller 5C:F3:70:6C:2E:8B Discovering: yes
[bluetooth]# pair 00:07:04:EF:38:C3
Attempting to pair with 00:07:04:EF:38:C3
Failed to pair: org.bluez.Error.ConnectionAttemptFailed
[bluetooth]#
I turn the PS3 controller on right before invoking "scan on" and again before pairing.
The current problem seems to be that the PS3 controller's "connected" status stays always "off".
However some time before I was already able to see its "connected" status "on"
(right after turning the PS3 controller on, bluetoothctl printed some sentence about the new device being available).
However at that time I was not able to pair the PS3 controller with bluetooth dongle anyway.
It asked about a PIN code and then some "time out" error occured (tried "0000", "1234" and "9999" PIN codes).
I admit I do not understand to bluetoothctl command very much (lacks documentation)
and also it is quite hard to figure out what the PS3 controller is actually doing (hard to decode the de facto undocumented red LED blinking).
1.) why the PS3 controller device does not appear in the "bluetoothctl" output anymore,
2.) why the pairing was failing
Thank you very much for any help!
P.S.: I also fail to install hciconfig and hcitool commands.
When i invoke
pkgfile hciconfig
#or
pkgfile hcitool
it returns "extra/bash-completion". Is't it a bug?
Arch user since 2010.
Offline
OK, so I managed to get it working. I will write where the problem was within a comple of days.
Arch user since 2010.
Offline
Congratulations.
pkgfile looks for any files with the given name, not only binaries. bash-completion probably has a file that contains autocomplete information for this command. If you want to find only binaries, then use the -b switch.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline