2011/10/8 Adam Williamson <awilliam@xxxxxxxxxx>
Works fine here. If the device isn't showing up at all I'd hazard aOn Sat, 2011-10-08 at 15:22 +0300, cornel panceac wrote:
> it doesn't work here, on f16 beta with latest updates. i get in
> 'messages' things like:
>
> Oct 8 15:11:42 localhost bluetoothd[1812]:
> Parsing /etc/bluetooth/input.conf failed: No such file or directory
> Oct 8 15:11:42 localhost bluetoothd[1812]:
> Parsing /etc/bluetooth/audio.conf failed: No such file or directory
>
> and
>
> Oct 8 15:11:42 localhost NetworkManager[921]: <warn> bluez error
> getting default adapter: No such adapter
>
> the same bluetooth stick works fine in f14.
>
> on the visible side of things, no bluetooth applet showsup in panel
> and if bluetooth-wizard is started manually, it never finds any
> device.
guess that the problem's at the kernel level...what do the lower level
console tools show?
--
the device seems to be recognized, but some files are missing:
Oct 9 13:44:33 localhost kernel: [ 189.908041] usb 2-4: new full speed USB device number 4 using ohci_hcd
Oct 9 13:44:33 localhost kernel: [ 190.108144] usb 2-4: New USB device found, idVendor=1131, idProduct=1004
Oct 9 13:44:33 localhost kernel: [ 190.108155] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 9 13:44:33 localhost kernel: [ 190.108162] usb 2-4: Product: ISSCEDRBTA
Oct 9 13:44:33 localhost kernel: [ 190.108168] usb 2-4: Manufacturer: ISSC
Oct 9 13:44:33 localhost kernel: [ 190.273170] Bluetooth: Core ver 2.16
Oct 9 13:44:33 localhost kernel: [ 190.273514] NET: Registered protocol family 31
Oct 9 13:44:33 localhost kernel: [ 190.273520] Bluetooth: HCI device and connection manager initialized
Oct 9 13:44:33 localhost kernel: [ 190.273530] Bluetooth: HCI socket layer initialized
Oct 9 13:44:33 localhost kernel: [ 190.273536] Bluetooth: L2CAP socket layer initialized
Oct 9 13:44:33 localhost kernel: [ 190.274263] Bluetooth: SCO socket layer initialized
Oct 9 13:44:33 localhost kernel: [ 190.292591] Bluetooth: Generic Bluetooth USB driver ver 0.6
Oct 9 13:44:33 localhost kernel: [ 190.310280] usbcore: registered new interface driver btusb
Oct 9 13:44:33 localhost bluetoothd[1925]: Bluetooth daemon 4.96
Oct 9 13:44:33 localhost bluetoothd[1925]: bluetoothd[1925]: Bluetooth daemon 4.96
Oct 9 13:44:33 localhost bluetoothd[1925]: Starting SDP server
Oct 9 13:44:33 localhost bluetoothd[1925]: bluetoothd[1925]: Starting SDP server
Oct 9 13:44:33 localhost kernel: [ 190.472746] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Oct 9 13:44:33 localhost kernel: [ 190.472760] Bluetooth: BNEP filters: protocol multicast
Oct 9 13:44:33 localhost bluetoothd[1925]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Oct 9 13:44:33 localhost bluetoothd[1925]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
...
and yum says:
Warning: No matches found for: /etc/bluetooth/input.conf
The file does not exist in f14 either.
Copying main.conf into input.conf got rid of the 'file not found' messages but still timeouts trying to connect to the device.
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
