built-in Bluetooth on eee-pc not functioning, dongle also not

Asked by Heinvandijk on 2012-11-02

The build-in bluetooth of a ASUS eee-pc netbook does not function properly. I assume there is no appropriate driver.
I want to use a usb-bluetooth-dongle which functions well on my pc (10.04 and 12.04). But when I $ sudo hciconfig hci0 down
the GUI does not switch to hci1, the usb-bluetooth-dongle. The owner is not familiar with CLI so the solution must be simple for her.
Can I prevent loading hci0 so that the dongle will be used after connection?

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu bluez Edit question
Assignee:
No assignee Edit question
Last query:
2012-11-03
Last reply:
2012-11-03

Can you give the output of:

lsb_release -a; uname -a; lspci; lsusb; dmesg | grep -i blue

Thanks

Heinvandijk (dijkvan) said : #2

Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise

 uname -a
Linux eli-laptop 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:41:14 UTC 2012 i686 i686 i386 GNU/Linux

00:00.0 Host bridge: Intel Corporation N10 Family DMI Bridge
00:02.0 VGA compatible controller: Intel Corporation N10 Family Integrated Graphics Controller
00:02.1 Display controller: Intel Corporation N10 Family Integrated Graphics Controller
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 02)
00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 4 (rev 02)
00:1d.0 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation N10/ICH7 Family SATA Controller [AHCI mode] (rev 02)
01:00.0 Ethernet controller: Atheros Communications Inc. AR8132 Fast Ethernet (rev c0)
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 13d3:5702 IMC Networks UVC VGA Webcam
Bus 005 Device 002: ID 0b05:1788 ASUSTek Computer, Inc.

$ dmesg | grep -i blue
[ 21.535417] Bluetooth: Core ver 2.16
[ 21.535502] Bluetooth: HCI device and connection manager initialized
[ 21.535510] Bluetooth: HCI socket layer initialized
[ 21.535517] Bluetooth: L2CAP socket layer initialized
[ 21.535535] Bluetooth: SCO socket layer initialized
[ 21.584310] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 21.584320] Bluetooth: BNEP filters: protocol multicast
[ 21.610657] Bluetooth: RFCOMM TTY layer initialized
[ 21.610676] Bluetooth: RFCOMM socket layer initialized
[ 21.610683] Bluetooth: RFCOMM ver 1.11
[ 22.095374] Bluetooth: Generic Bluetooth USB driver ver 0.6

Great and the output of:

sudo dmidecode -t 1

Thanks

Heinvandijk (dijkvan) said : #4

# dmidecode 2.11
SMBIOS 2.6 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
 Manufacturer: ASUSTeK Computer INC.
 Product Name: 1015PE
 Version: x.x
 Serial Number: A5OAAS313142
 UUID: 33B7F600-5FCE-81DF-3DFD-485B397A3EE8
 Wake-up Type: Power Switch
 SKU Number: 1015PE
 Family: Eee PC

Try:

sudo rfkill unblock bluetooth

Source:
http://www.splitbrain.org/blog/2010-08/27-asus_eeepc_1015pe

If it works, we can add the command to the startup

Heinvandijk (dijkvan) said : #7

 hciconfig -a
hci0: Type: BR/EDR Bus: USB
 BD Address: 1C:4B:D6:12:50:82 ACL MTU: 1021:8 SCO MTU: 64:1
 UP RUNNING PSCAN ------------> no effect !!!!??
 RX bytes:822 acl:0 sco:0 events:33 errors:0
 TX bytes:637 acl:0 sco:0 commands:33 errors:0
 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x87
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 Link policy: RSWITCH HOLD SNIFF PARK
 Link mode: SLAVE ACCEPT
 Name: 'elisa-laptop-0'
 Class: 0x6e0100
 Service Classes: Networking, Rendering, Capturing, Audio, Telephony
 Device Class: Computer, Uncategorized
 HCI Version: 3.0 (0x5) Revision: 0x1c1
 LMP Version: 3.0 (0x5) Subversion: 0x4203
 Manufacturer: Broadcom Corporation (15)

Heinvandijk (dijkvan) said : #8

Now with dongle inserted:
sudo rfkill unblock bluetooth
lisa-laptop:~$ hciconfig -a
hci0: Type: BR/EDR Bus: USB
 BD Address: 1C:4B:D6:12:50:82 ACL MTU: 1021:8 SCO MTU: 64:1
 UP RUNNING PSCAN
 RX bytes:1099 acl:0 sco:0 events:36 errors:0
 TX bytes:646 acl:0 sco:0 commands:36 errors:0
 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x87
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 Link policy: RSWITCH HOLD SNIFF PARK
 Link mode: SLAVE ACCEPT
 Name: 'elisa-laptop-0'
 Class: 0x6e0100
 Service Classes: Networking, Rendering, Capturing, Audio, Telephony
 Device Class: Computer, Uncategorized
 HCI Version: 3.0 (0x5) Revision: 0x1c1
 LMP Version: 3.0 (0x5) Subversion: 0x4203
 Manufacturer: Broadcom Corporation (15)

hci1: Type: BR/EDR Bus: USB
 BD Address: 99:88:66:00:1D:19 ACL MTU: 384:8 SCO MTU: 64:8
 UP RUNNING PSCAN
 RX bytes:789 acl:0 sco:0 events:28 errors:0
 TX bytes:376 acl:0 sco:0 commands:27 errors:0
 Features: 0xff 0xff 0x8f 0xfe 0x9b 0xf9 0x00 0x80
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 Link policy: RSWITCH HOLD SNIFF PARK
 Link mode: SLAVE ACCEPT
 Name: 'elisa-laptop-0'
 Class: 0x6e0100
 Service Classes: Networking, Rendering, Capturing, Audio, Telephony
 Device Class: Computer, Uncategorized
 HCI Version: 2.0 (0x3) Revision: 0x7a6
 LMP Version: 2.0 (0x3) Subversion: 0x7a6
 Manufacturer: Cambridge Silicon Radio (10)

Heinvandijk (dijkvan) said : #9

I tryed:
 sudo mv /etc/init/bluetooth.conf bluetooth.conf
Bluetooth was disabled but also the dongle. Hence
 :~$ sudo mv bluetooth.conf /etc/init/bluetooth.conf

:~$ cat /etc/init/bluetooth.conf
# bluez - bluetooth daemon

description "bluetooth daemon"

start on started dbus
stop on stopping dbus

env UART_CONF=/etc/bluetooth/uart
env RFCOMM_CONF=/etc/bluetooth/rfcomm.conf

expect fork
respawn

exec /usr/sbin/bluetoothd

post-start script
 [ "$VERBOSE" = no ] && redirect='>/dev/null 2>&1' || redirect=

 # start_uarts()
 if [ -x /usr/sbin/hciattach ] && [ -f $UART_CONF ];
 then
  grep -v '^#' $UART_CONF | while read i; do
    eval "/usr/sbin/hciattach $i $redirect" || :
  done
 fi

 # start_rfcomm()
 if [ -x /usr/bin/rfcomm ] && [ -f $RFCOMM_CONF ] ;
 then
  # rfcomm must always succeed for now: users
  # may not yet have an rfcomm-enabled kernel
  eval "/usr/bin/rfcomm -f $RFCOMM_CONF bind all $redirect" || :
 fi
end script

post-stop script
 # stop_uarts()
 logger -t bluez "Stopping uarts"
 killall hciattach >/dev/null 2>&1 || :

 # stop_rfcomm()
 logger -t bluez "Stopping rfcomm"
 if [ -x /usr/bin/rfcomm ];
 then
  eval "/usr/bin/rfcomm unbind all $redirect" || :
 fi
end script

Did the command show a bluetooth icon on the panel?

Heinvandijk (dijkvan) said : #11

The icon stayed on te panel with command (no effect found), and with the mv-command of #9. In the latter case the menu was simpler; just item connect/disconnect and settings.

Heinvandijk (dijkvan) said : #12

tried:
sudo update-rc.d bluetooth remove
update-rc.d: /etc/init.d/bluetooth exists during rc.d purge (use -f to force)

Can this go wrong if I use -f ?

Heinvandijk (dijkvan) said : #13

tried 12; no result. Has to do with 12.04, earlier versions seem to work.
Next we I can not work on the problem.
Thanks for your help so far.

I suggest you report a bug. Make sure your BIOS is up to date too

Can you help with this problem?

Provide an answer of your own, or ask Heinvandijk for more information if necessary.

To post a message you must log in.