[Bluez-users] Installing / get running bluez-3.1

[Bluez-users] Installing / get running bluez-3.1

[Andreas Fehr]

Hi

I run into a problem to install or get running bluez-3.1

Up to now, I used some version 2.x (can't remember what version as I 
uninstalled it to early). Compiling and installing the files was no 
problem, but I can't get it running.

I use:
- Kernel 2.6.17.4
- bluez-libs-3.1
- bluez-utils-3.1
- dbus-0.62

dmesg |grep blue -i -a1 shows:

 PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
 Bluetooth: Core ver 2.8
 NET: Registered protocol family 31
 Bluetooth: HCI device and connection manager initialized
 Bluetooth: HCI socket layer initialized
 PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
 --
 NET: Registered protocol family 17
 Bluetooth: L2CAP ver 2.8
 Bluetooth: L2CAP socket layer initialized
 Bluetooth: RFCOMM socket layer initialized
 Bluetooth: RFCOMM TTY layer initialized
 Bluetooth: RFCOMM ver 1.7
 Using IPI Shortcut mode
 --
 usb 2-1: configuration #1 chosen from 1 choice
 Bluetooth: HCI USB driver ver 2.9
 usbcore: registered new driver hci_usb

I have a Blue Fritz V2.0 USB dongle and lsmod tells me, that the usb 
module has been loaded:
 Module                  Size  Used by
 hci_usb                 9236  0 

With vmware and it's USB driver, I'm able to use the Bluetooth dongle, 
so the USB driver, the dongle and my hardware seem to be ok. So much for 
the good part.

Now, if I run rfcomm bind 0, the file /dev/rfcomm gets created:
 crw-rw-rw-  1 root dialout 216, 0 Jul  9 19:02 /dev/rfcomm0

rfcomm: (1)
 rfcomm0: 00:18:xx:xx:xx:xx channel 3 clean

But the old software that I used to use does not work.

minicom comes up with the message:
 minicom: cannot open /dev/rfcomm0: No route to host

hcitool scan prints:
 Device is not available: No such device


What might be the cause of this?


I suspect, it's the dbus subsystem, but I don't get any help there. Is 
there a way to have some verbose messages that tell me where I'm wrong?

dbus-daemon is running:
 /usr/bin/dbus-daemon --config-file=/etc/dbus-1/system.conf

and I started a session daemon:
 dbus-daemon --fork --print-pid 8 --print-address 6 --session


Now I'm stuck...

Any help out there?
Thanks, Andreas


(1)
the ID is my valid phone ID. I copied hcid.conf and rfcomm.conf to save 
my configuration from /etc/bluetooth. This might be an enhancement. Each 
time I install a new version of bluez, the get removed (with the 
uninstall of the old version). Just keep the config data on the system, 
it's easier to remove a configuration directory than to go to the 
server, dig up the backup drive, attach it to the system, search the 
correct backup version, copy the config files, and restore the backup 
drive in the server room... :-)


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Installing / get running bluez-3.1

[Marcel Holtmann]

Hi Andreas,

> I run into a problem to install or get running bluez-3.1
> 
> Up to now, I used some version 2.x (can't remember what version as I 
> uninstalled it to early). Compiling and installing the files was no 
> problem, but I can't get it running.
> 
> I use:
> - Kernel 2.6.17.4
> - bluez-libs-3.1
> - bluez-utils-3.1
> - dbus-0.62
> 
> dmesg |grep blue -i -a1 shows:
> 
>  PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
>  Bluetooth: Core ver 2.8
>  NET: Registered protocol family 31
>  Bluetooth: HCI device and connection manager initialized
>  Bluetooth: HCI socket layer initialized
>  PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
>  --
>  NET: Registered protocol family 17
>  Bluetooth: L2CAP ver 2.8
>  Bluetooth: L2CAP socket layer initialized
>  Bluetooth: RFCOMM socket layer initialized
>  Bluetooth: RFCOMM TTY layer initialized
>  Bluetooth: RFCOMM ver 1.7
>  Using IPI Shortcut mode
>  --
>  usb 2-1: configuration #1 chosen from 1 choice
>  Bluetooth: HCI USB driver ver 2.9
>  usbcore: registered new driver hci_usb
> 
> I have a Blue Fritz V2.0 USB dongle and lsmod tells me, that the usb 
> module has been loaded:
>  Module                  Size  Used by
>  hci_usb                 9236  0 
> 
> With vmware and it's USB driver, I'm able to use the Bluetooth dongle, 
> so the USB driver, the dongle and my hardware seem to be ok. So much for 
> the good part.
> 
> Now, if I run rfcomm bind 0, the file /dev/rfcomm gets created:
>  crw-rw-rw-  1 root dialout 216, 0 Jul  9 19:02 /dev/rfcomm0
> 
> rfcomm: (1)
>  rfcomm0: 00:18:xx:xx:xx:xx channel 3 clean
> 
> But the old software that I used to use does not work.
> 
> minicom comes up with the message:
>  minicom: cannot open /dev/rfcomm0: No route to host
> 
> hcitool scan prints:
>  Device is not available: No such device

call "hciconfig -a" and make sure "hcidump -X -V" is running in another
terminal to catch the setup.

You might also kill hcid and then start it with "hcid -n" to catch the
initialization of the adapter via hcidump.

Regards

Marcel




-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Installing / get running bluez-3.1

[Andreas Fehr]

On Sunday, 09. July 2006, 19:15, Andreas Fehr (as AF) wrote:

>AF: Up to now, I used some version 2.x (can't remember what version as 
>AF: I uninstalled it to early). Compiling and installing the files was 
>AF: no problem, but I can't get it running.
>AF: 
>AF: I use:
>AF: - Kernel 2.6.17.4
>AF: - bluez-libs-3.1
>AF: - bluez-utils-3.1
>AF: - dbus-0.62
>AF: 
>AF: dmesg |grep blue -i -a1 shows:
>AF: 
>AF:  PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
>AF:  Bluetooth: Core ver 2.8
>AF:  NET: Registered protocol family 31
>AF:  Bluetooth: HCI device and connection manager initialized
>AF:  Bluetooth: HCI socket layer initialized
>AF:  PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
>AF:  --
>AF:  NET: Registered protocol family 17
>AF:  Bluetooth: L2CAP ver 2.8
>AF:  Bluetooth: L2CAP socket layer initialized
>AF:  Bluetooth: RFCOMM socket layer initialized
>AF:  Bluetooth: RFCOMM TTY layer initialized
>AF:  Bluetooth: RFCOMM ver 1.7
>AF:  Using IPI Shortcut mode
>AF:  --
>AF:  usb 2-1: configuration #1 chosen from 1 choice
>AF:  Bluetooth: HCI USB driver ver 2.9
>AF:  usbcore: registered new driver hci_usb
>AF: 
>AF: I have a Blue Fritz V2.0 USB dongle and lsmod tells me, that the usb 
>AF: module has been loaded:
>AF:  Module                  Size  Used by
>AF:  hci_usb                 9236  0 
>AF: 
>AF: With vmware and it's USB driver, I'm able to use the Bluetooth dongle, 
>AF: so the USB driver, the dongle and my hardware seem to be ok. So much for 
>AF: the good part.
>AF: 
>AF: Now, if I run rfcomm bind 0, the file /dev/rfcomm gets created:
>AF:  crw-rw-rw-  1 root dialout 216, 0 Jul  9 19:02 /dev/rfcomm0
>AF: 
>AF: rfcomm: (1)
>AF:  rfcomm0: 00:18:xx:xx:xx:xx channel 3 clean
>AF: 
>AF: But the old software that I used to use does not work.
>AF: 
>AF: minicom comes up with the message:
>AF:  minicom: cannot open /dev/rfcomm0: No route to host
>AF: 
>AF: hcitool scan prints:
>AF:  Device is not available: No such device
>
> call "hciconfig -a" and make sure "hcidump -X -V" is running in 
> another terminal to catch the setup.

For me, both output look reasonable. Does it help to analyse the 
problem?


hciconfig -a (BD Address changed):

hci0:   Type: USB
        BD Address: 00:05:0F:99:06:04 ACL MTU: 120:20 SCO MTU: 64:0
        UP RUNNING PSCAN 
        RX bytes:407 acl:0 sco:0 events:18 errors:0
        TX bytes:320 acl:0 sco:0 commands:18 errors:0
        Features: 0xff 0xff 0x05 0x00 0x00 0x00 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: RSWITCH HOLD SNIFF PARK 
        Link mode: SLAVE ACCEPT 
        Name: 'mycomputer'
        Class: 0x3e0100
        Service Classes: Networking, Rendering, Capturing, Object Transfer, Audio
        Device Class: Computer, Uncategorized
        HCI Ver: 1.1 (0x1) HCI Rev: 0x2005 LMP Ver: 1.1 (0x1) LMP Subver: 0x1805
        Manufacturer: AVM Berlin (31)

hcidump -X -V:

HCI sniffer - Bluetooth packet analyzer ver 1.31
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Read Local Name (0x03|0x0014) plen 0
> HCI Event: Command Complete (0x0e) plen 252
    Read Local Name (0x03|0x0014) ncmd 1
    status 0x00 name 'mycomputer'
< HCI Command: Read Class of Device (0x03|0x0023) plen 0
> HCI Event: Command Complete (0x0e) plen 7
    Read Class of Device (0x03|0x0023) ncmd 1
    status 0x00 class 0x3e0100
< HCI Command: Read Local Version Information (0x04|0x0001) plen 0
> HCI Event: Command Complete (0x0e) plen 12
    Read Local Version Information (0x04|0x0001) ncmd 1
    status 0x00
    HCI Version: 1.1 (0x1) HCI Revision: 0x2005
    LMP Version: 1.1 (0x1) LMP Subversion: 0x1805
    Manufacturer: AVM Berlin (31)



> You might also kill hcid and then start it with "hcid -n" to catch the 
> initialization of the adapter via hcidump.

< HCI Command: Write Scan Enable (0x03|0x001a) plen 1
    enable 2
> HCI Event: Command Complete (0x0e) plen 4
    Write Scan Enable (0x03|0x001a) ncmd 1
    status 0x00
< HCI Command: Read Stored Link Key (0x03|0x000d) plen 7
    bdaddr 00:00:00:00:00:00 all 1
> HCI Event: Command Complete (0x0e) plen 8
    Read Stored Link Key (0x03|0x000d) ncmd 1
    status 0x00 max 8 num 0
< HCI Command: Read Local Version Information (0x04|0x0001) plen 0
> HCI Event: Command Complete (0x0e) plen 12
    Read Local Version Information (0x04|0x0001) ncmd 1
    status 0x00
    HCI Version: 1.1 (0x1) HCI Revision: 0x2005
    LMP Version: 1.1 (0x1) LMP Subversion: 0x1805
    Manufacturer: AVM Berlin (31)
< HCI Command: Write Local Name (0x03|0x0013) plen 248
    name 'mycomputer'
> HCI Event: Command Complete (0x0e) plen 4
    Write Local Name (0x03|0x0013) ncmd 1
    status 0x00
< HCI Command: Write Class of Device (0x03|0x0024) plen 3
    class 0x3e0100
> HCI Event: Command Complete (0x0e) plen 4
    Write Class of Device (0x03|0x0024) ncmd 1
    status 0x00
< HCI Command: Read Local Supported Features (0x04|0x0003) plen 0
> HCI Event: Command Complete (0x0e) plen 12
    Read Local Supported Features (0x04|0x0003) ncmd 1
    status 0x00
    Features: 0xff 0xff 0x05 0x00 0x00 0x00 0x00 0x00
< HCI Command: Write Inquiry Mode (0x03|0x0045) plen 1
    mode 0
> HCI Event: Command Complete (0x0e) plen 4
    Write Inquiry Mode (0x03|0x0045) ncmd 1
    status 0x00
< HCI Command: Read Scan Enable (0x03|0x0019) plen 0
> HCI Event: Command Complete (0x0e) plen 5
    Read Scan Enable (0x03|0x0019) ncmd 1
    status 0x00 enable 2
< HCI Command: Read Scan Enable (0x03|0x0019) plen 0
> HCI Event: Command Complete (0x0e) plen 5
    Read Scan Enable (0x03|0x0019) ncmd 1
    status 0x00 enable 2
< HCI Command: Read Local Name (0x03|0x0014) plen 0
> HCI Event: Command Complete (0x0e) plen 252
    Read Local Name (0x03|0x0014) ncmd 1
    status 0x00 name 'mycomputer'



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

Re: [Bluez-users] Installing / get running bluez-3.1

[Andreas Fehr]

On Tuesday, 11. July 2006, 19:18, Andreas Fehr (as AF) wrote:

>AF: On Sunday, 09. July 2006, 19:15, Andreas Fehr (as AF) wrote:
>AF: 
>AF: >AF: Up to now, I used some version 2.x (can't remember what version as 
>AF: >AF: I uninstalled it to early). Compiling and installing the files was 
>AF: >AF: no problem, but I can't get it running.
>AF: >AF: 
>AF: >AF: I use:
>AF: >AF: - Kernel 2.6.17.4
>AF: >AF: - bluez-libs-3.1
>AF: >AF: - bluez-utils-3.1
>AF: >AF: - dbus-0.62

<snip>

>AF: >AF: With vmware and it's USB driver, I'm able to use the Bluetooth dongle, 
>AF: >AF: so the USB driver, the dongle and my hardware seem to be ok. So much for 
>AF: >AF: the good part.
>AF: >AF: 
>AF: >AF: Now, if I run rfcomm bind 0, the file /dev/rfcomm gets created:
>AF: >AF:  crw-rw-rw-  1 root dialout 216, 0 Jul  9 19:02 /dev/rfcomm0
>AF: >AF: 
>AF: >AF: rfcomm: (1)
>AF: >AF:  rfcomm0: 00:18:xx:xx:xx:xx channel 3 clean
>AF: >AF: 
>AF: >AF: But the old software that I used to use does not work.
>AF: >AF: 
>AF: >AF: minicom comes up with the message:
>AF: >AF:  minicom: cannot open /dev/rfcomm0: No route to host
>AF: >AF: 
>AF: >AF: hcitool scan prints:
>AF: >AF:  Device is not available: No such device
>AF: >
>AF: > call "hciconfig -a" and make sure "hcidump -X -V" is running in 
>AF: > another terminal to catch the setup.
>AF: 
>AF: For me, both output look reasonable. Does it help to analyse the 
>AF: problem?

Ok, I'm one step further. It looks like it is a problem with my phone 
that I wont to connect to.

With vmware, i have the same BD address as with bluez (under Linux) but 
I use different device (computer) names. It looks like the phone got 
confused by that (no reaction on the phone on connection attempt). I 
removed the pairing from the phone.

Now, I get some message to enter the pine on the phone. But not long 
enough to enter any key in the phone. Bluetooth gets disconnected after 
about 2 seconds.

Is there any information about setting up pin or pin_helper with the new 
version 3.x of bluez? I grepped bluez-util with 'pin' and 'pin_helper' 
but there was no documentation for this new version. I did not change 
anything from the old version 2.xx that I used, but it looks like the 
old configuration doesn't work anymore.

Thanks,
Andreas


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users