You are not logged in.

Pages: 1

#1 2012-02-17 10:55:21

darquandier
Member
Registered: 2011-09-26
Posts: 10

Bluetooth adapter not working

Hello,

I've been having problem with my bluetooth adapter.
I have a Sony Vaio VPCF2.

The bluetooth exists, is detected by hcitool, but I cannot use it at all...
Even in Gnome3, the button to activate it is greyed out.

Here are a few result of my experimentations :

^.^11:52:08-pilot@moya:~$ rfkill list
0: sony-wifi: Wireless LAN
	Soft blocked: no
	Hard blocked: no
1: sony-bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
2: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no
3: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
¤.¤11:54:09-pilot@moya:~$ sudo hciconfig hci0
hci0:	Type: BR/EDR  Bus: USB
	BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
	DOWN 
	RX bytes:0 acl:0 sco:0 events:0 errors:0
	TX bytes:12 acl:0 sco:0 commands:4 errors:0

^.^11:54:25-pilot@moya:~$ sudo hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

¤.¤11:54:05-pilot@moya:~$ sudo hciconfig hci0 piscan
Can't set scan mode on hci0: Network is down (100)


And some info on the configuration: 

^.^11:50:27-pilot@moya:~$ uname -a
Linux moya 3.2.6-2-ARCH #1 SMP PREEMPT Thu Feb 16 10:10:02 CET 2012 x86_64 Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz GenuineIntel GNU/Linux

^.^11:48:42-pilot@moya:~$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 05ca:18c0 Ricoh Co., Ltd 
[ins]Bus 001 Device 004: ID 0489:e027 Foxconn / Hon Hai [/ins]

If anyone has any idea as to how I could make it work ?
I reckon this is a kernel problem, if so, where should I report it, I'm sure other people would benefit from having this resolved.

Offline

#2 2012-02-17 12:26:02

marxav
Member
From: Gatineau, PQ, Canada
Registered: 2006-09-24
Posts: 386

Re: Bluetooth adapter not working

I am having a similar situation which you could have found in the forum : https://bbs.archlinux.org/viewtopic.php?id=135723.  Maybe what's there might help you.

Offline

#3 2012-02-17 13:43:31

darquandier
Member
Registered: 2011-09-26
Posts: 10

Re: Bluetooth adapter not working

Similar but different I guess. Firstly, "rfkill list" shows that there is no hard of soft block.
Actually, if I change the physical switch I can see it going from on to off with rfkill so that detects normally.

Secondly, my card is shown as DOWN, never as UP with hciconfig.

Offline

#4 2012-02-17 14:03:13

marxav
Member
From: Gatineau, PQ, Canada
Registered: 2006-09-24
Posts: 386

Re: Bluetooth adapter not working

darquandier wrote:

Secondly, my card is shown as DOWN, never as UP with hciconfig.

Even if you  do hciconfig hci0 up

Offline

#5 2012-02-17 14:16:09

darquandier
Member
Registered: 2011-09-26
Posts: 10

Re: Bluetooth adapter not working

As stated in the first post :

^.^11:54:25-pilot@moya:~$ sudo hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

Offline

#6 2012-02-17 19:48:59

pigiron
Member
From: USA
Registered: 2009-07-14
Posts: 150

Re: Bluetooth adapter not working

Bus 001 Device 004: ID 0489:e027 Foxconn / Hon Hai

EDIT: Ignore my dribble... probably a red herring.

Is this one of those goofy chips that Foxconn created that combined USB bluetooth with Atheros AR9285 Wireless PCI-Express?

If so, it has a troubled history that I poked around in last year for the sad clown:

https://bbs.archlinux.org/viewtopic.php … 48#p990948

If my google fu was any good back then, it lead me to the thread that I mentioned last year... where when the chip was first brought up, the bluetooth adapter advertised itself with a particular VendorID:DeviceID, but after the firmware was loaded it morphed itself into a different ID.

Anyway, that was history... But if you do have that chip, you don't appear to be recently alone with your problem... just google "0489:e027" (with the quotes).

Also, you might want to see if there's anything in the system logs... and when I'm shooting Bluez bugs, I trying kill all the bluetooth daemons and then fire up a terminal and enter (as root):

bluetoothd -d -n

But interpreting all the debug messages that spew out is an entirely different kettle of fish.

Last edited by pigiron (2012-02-17 20:40:37)

Offline

#7 2012-02-18 00:41:40

Hyugga
Member
From: Santiago, Chile
Registered: 2010-03-26
Posts: 335

Re: Bluetooth adapter not working

i'm having problems with bluetooth too, but in bluedevil. I opened a thread some time ago but with no responses... I hope we can solve this.

Offline

#8 2012-02-20 13:56:17

darquandier
Member
Registered: 2011-09-26
Posts: 10

Re: Bluetooth adapter not working

Here is my try with "bluetoothd -d -n"

^.^14:51:34-pilot@moya:~$ sudo /etc/rc.d/bluetooth stop
:: Stopping bluetooth subsystem:  pand dund rfcomm hidd  bluetoothd                                                                                                                                                                      [DONE] 
¤.¤14:51:59-pilot@moya:~$ sudo bluetoothd -n -d
bluetoothd[2748]: Bluetooth daemon 4.98
bluetoothd[2748]: src/main.c:parse_config() parsing main.conf
bluetoothd[2748]: src/main.c:parse_config() discovto=0
bluetoothd[2748]: src/main.c:parse_config() pairto=0
bluetoothd[2748]: src/main.c:parse_config() pageto=8192
bluetoothd[2748]: src/main.c:parse_config() auto_to=60
bluetoothd[2748]: src/main.c:parse_config() name=%h-%d
bluetoothd[2748]: src/main.c:parse_config() class=0x000100
bluetoothd[2748]: src/main.c:parse_config() discov_interval=30
bluetoothd[2748]: src/main.c:parse_config() Key file does not have key 'DeviceID'
bluetoothd[2748]: Starting SDP server
bluetoothd[2748]: src/plugin.c:plugin_init() Loading builtin plugins
bluetoothd[2748]: src/plugin.c:add_plugin() Loading audio plugin
bluetoothd[2748]: src/plugin.c:add_plugin() Loading input plugin
bluetoothd[2748]: src/plugin.c:add_plugin() Loading serial plugin
bluetoothd[2748]: src/plugin.c:add_plugin() Loading network plugin
bluetoothd[2748]: src/plugin.c:add_plugin() Loading service plugin
bluetoothd[2748]: src/plugin.c:add_plugin() Loading hciops plugin
bluetoothd[2748]: src/plugin.c:add_plugin() Loading mgmtops plugin
bluetoothd[2748]: src/plugin.c:add_plugin() Loading formfactor plugin
bluetoothd[2748]: src/plugin.c:add_plugin() Loading storage plugin
bluetoothd[2748]: src/plugin.c:add_plugin() Loading adaptername plugin
bluetoothd[2748]: src/plugin.c:add_plugin() Loading wiimote plugin
bluetoothd[2748]: src/plugin.c:plugin_init() Loading plugins /usr/lib/bluetooth/plugins
bluetoothd[2748]: plugins/service.c:register_interface() path /org/bluez/2748/any
bluetoothd[2748]: plugins/service.c:register_interface() Registered interface org.bluez.Service on path /org/bluez/2748/any
bluetoothd[2748]: network/manager.c:read_config() /etc/bluetooth/network.conf: Key file does not have key 'DisableSecurity'
bluetoothd[2748]: network/manager.c:read_config() Config options: Security=true
bluetoothd[2748]: input/manager.c:input_manager_init() input.conf: Key file does not have key 'IdleTimeout'
bluetoothd[2748]: audio/manager.c:audio_manager_init() audio.conf: Key file does not have key 'AutoConnect'
bluetoothd[2748]: plugins/hciops.c:hciops_init() 
bluetoothd[2748]: plugins/hciops.c:hciops_setup() 
bluetoothd[2748]: src/main.c:main() Entering main loop
bluetoothd[2748]: src/rfkill.c:rfkill_event() RFKILL event idx 0 type 1 op 0 soft 0 hard 0
bluetoothd[2748]: src/rfkill.c:rfkill_event() RFKILL event idx 1 type 2 op 0 soft 0 hard 0
bluetoothd[2748]: src/rfkill.c:rfkill_event() RFKILL event idx 2 type 1 op 0 soft 0 hard 0
bluetoothd[2748]: src/rfkill.c:rfkill_event() RFKILL event idx 3 type 2 op 0 soft 0 hard 0
bluetoothd[2748]: plugins/hciops.c:init_known_adapters() 
bluetoothd[2748]: plugins/hciops.c:init_device() hci0
bluetoothd[2748]: Listening for HCI events on hci0
bluetoothd[2748]: plugins/hciops.c:init_device() child 2751 forked
bluetoothd[2751]: Can't init device hci0: Connection timed out (110)
bluetoothd[2748]: plugins/hciops.c:child_exit() child 2751 exited

So yeah, anything new, except it times out.
I tried doing some "hciconfig up" on the side, nothing appears in the log nevertheless.

Offline

Pages: 1

Board footer

Powered by FluxBB