Debian Bug report logs - #359003
bluez-utils: udev script missing

version graph

Package: bluez-utils; Maintainer for bluez-utils is Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>; Source for bluez-utils is src:bluez.

Reported by: Hadmut Danisch <hadmut@danisch.de>

Date: Sat, 25 Mar 2006 20:33:10 UTC

Severity: normal

Tags: moreinfo

Found in version bluez-utils/2.25-1

Done: Filippo Giunchedi <filippo@debian.org>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to debian-bugs-dist@lists.debian.org, Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>:
Bug#359003; Package bluez-utils. Full text and rfc822 format available.

Acknowledgement sent to Hadmut Danisch <hadmut@danisch.de>:
New Bug report received and forwarded. Copy sent to Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>. Full text and rfc822 format available.

Message #5 received at submit@bugs.debian.org (full text, mbox):

From: Hadmut Danisch <hadmut@danisch.de>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: bluez-utils: udev script missing
Date: Sat, 25 Mar 2006 21:04:42 +0100
Package: bluez-utils
Version: 2.25-1
Severity: normal

Hi,

when plugging in a USB bluetooth dongle in a running linux system the
bluetooth drivers do not recognize the dongle. I need to call
/etc/init.d/bluez-utils restart to make the dongle work.

bluez-utils should come with an appropriate udev script which
automatically restarts the bluetooth utils (or does whatever needs to
be done) automatically when a USB dongle is inserted or removed. 


regards
Hadmut


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-danisch-p4-intel
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)

Versions of packages bluez-utils depends on:
ii  libbluetooth1                2.25-1      Library to use the BlueZ Linux Blu
ii  libc6                        2.3.6-3     GNU C Library: Shared libraries an
ii  libdbus-1-2                  0.61-4      simple interprocess messaging syst
ii  libusb-0.1-4                 2:0.1.11-5  userspace USB programming library
ii  lsb-base                     3.0-16      Linux Standard Base 3.0 init scrip
ii  makedev                      2.3.1-80    creates device files in /dev
ii  module-init-tools            3.2.2-2     tools for managing Linux kernel mo
ii  modutils                     2.4.27.0-5  Linux module utilities
ii  sysvinit                     2.86.ds1-12 System-V-like init utilities

bluez-utils recommends no packages.

-- no debconf information



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>:
Bug#359003; Package bluez-utils. Full text and rfc822 format available.

Acknowledgement sent to Edd Dumbill <edd@usefulinc.com>:
Extra info received and forwarded to list. Copy sent to Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>. Full text and rfc822 format available.

Message #10 received at 359003@bugs.debian.org (full text, mbox):

From: Edd Dumbill <edd@usefulinc.com>
To: Hadmut Danisch <hadmut@danisch.de>, 359003@bugs.debian.org
Subject: Re: [Pkg-bluetooth-maintainers] Bug#359003: bluez-utils: udev script missing
Date: Sun, 26 Mar 2006 08:42:56 +0100
Please include the output of lsusb -v so we can see the make and model
of your dongle

On Sat, 2006-03-25 at 21:04 +0100, Hadmut Danisch wrote:
> Package: bluez-utils
> Version: 2.25-1
> Severity: normal
> 
> Hi,
> 
> when plugging in a USB bluetooth dongle in a running linux system the
> bluetooth drivers do not recognize the dongle. I need to call
> /etc/init.d/bluez-utils restart to make the dongle work.
> 
> bluez-utils should come with an appropriate udev script which
> automatically restarts the bluetooth utils (or does whatever needs to
> be done) automatically when a USB dongle is inserted or removed. 
> 





Information forwarded to debian-bugs-dist@lists.debian.org, Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>:
Bug#359003; Package bluez-utils. Full text and rfc822 format available.

Acknowledgement sent to Hadmut Danisch <hadmut@danisch.de>:
Extra info received and forwarded to list. Copy sent to Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>. Full text and rfc822 format available.

Message #15 received at 359003@bugs.debian.org (full text, mbox):

From: Hadmut Danisch <hadmut@danisch.de>
To: Edd Dumbill <edd@usefulinc.com>
Cc: 359003@bugs.debian.org
Subject: Re: [Pkg-bluetooth-maintainers] Bug#359003: bluez-utils: udev script missing
Date: Sun, 26 Mar 2006 10:10:43 +0200
Edd Dumbill wrote:
> Please include the output of lsusb -v so we can see the make and model
> of your dongle


Bus 002 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass          224 Wireless
  bDeviceSubClass         1 Radio Frequency
  bDeviceProtocol         1 Bluetooth
  bMaxPacketSize0        64
  idVendor           0x0a12 Cambridge Silicon Radio, Ltd
  idProduct          0x0001 Bluetooth Dongle (HCI mode)
  bcdDevice            4.43
  iManufacturer           0
  iProduct                0
  iSerial                 0
  bNumConfigurations      1


It is a D-Link Bluetooth DBT-120.

I have another notebook at work with builtin bluetooth. When switching 
radio on (WLAN+Bluetooth) with the radio switch at the front this has 
the effect as if a Bluetooth USB dongle had been inserted. I'll send 
those USB data tomorrow.

However, wouldn't it be easier to just take the Vendor/Product id list 
from the driver software? If the dongle driver can use it, there must be 
a list of recognized dongles (or Vendor/Product ids). Why not use that 
already existing list?


regards
Hadmut








Information forwarded to debian-bugs-dist@lists.debian.org, Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>:
Bug#359003; Package bluez-utils. Full text and rfc822 format available.

Acknowledgement sent to Edd Dumbill <edd@usefulinc.com>:
Extra info received and forwarded to list. Copy sent to Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>. Full text and rfc822 format available.

Message #20 received at 359003@bugs.debian.org (full text, mbox):

From: Edd Dumbill <edd@usefulinc.com>
To: Hadmut Danisch <hadmut@danisch.de>
Cc: 359003@bugs.debian.org
Subject: Re: [Pkg-bluetooth-maintainers] Bug#359003: bluez-utils: udev script missing
Date: Sun, 26 Mar 2006 12:39:17 +0100
On Sun, 2006-03-26 at 10:10 +0200, Hadmut Danisch wrote:
> 
> However, wouldn't it be easier to just take the Vendor/Product id
> list 
> from the driver software? If the dongle driver can use it, there must
> be 
> a list of recognized dongles (or Vendor/Product ids). Why not use
> that 
> already existing list? 

You're seeing some new bug, I think.  For years the dongle will be
initialised without the need for a restart.  It's not a udev issue, it's
hcid in all likelihood.

-- Edd





Information forwarded to debian-bugs-dist@lists.debian.org, Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>:
Bug#359003; Package bluez-utils. Full text and rfc822 format available.

Acknowledgement sent to hadmut@danisch.de (Hadmut Danisch):
Extra info received and forwarded to list. Copy sent to Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>. Full text and rfc822 format available.

Message #25 received at 359003@bugs.debian.org (full text, mbox):

From: hadmut@danisch.de (Hadmut Danisch)
To: 359003@bugs.debian.org
Subject: More debugging
Date: Mon, 27 Mar 2006 22:17:39 +0200
Hi,

I did some more testing. Maybe the problem I was reporting is gone. 
It does not take a reboot, it takes *time*. 

I am pretty sure that at least about a year ago I did intensive
testing and verified that it took a restart, even after waiting for
more than an hour. Now it works without restart, but takes some
time. When trying to connect to a device within about 3-4 seconds
after plugging in the dongle, it just appears as if the dongle has not
been detected, and if the problem still existed. That's why I was
assuming that the problem is not yet solved.

When waiting long enough, it works without restarting the daemons. 

Sorry for the bug report.

regards
Hadmut



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>:
Bug#359003; Package bluez-utils. Full text and rfc822 format available.

Acknowledgement sent to Filippo Giunchedi <filippo@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>. Full text and rfc822 format available.

Message #30 received at 359003@bugs.debian.org (full text, mbox):

From: Filippo Giunchedi <filippo@debian.org>
To: 359003@bugs.debian.org, 359003-submitter@bugs.debian.org
Subject: elaboration on this
Date: Tue, 16 May 2006 19:54:22 -0500
[Message part 1 (text/plain, inline)]
Hi,
thanks for your report, what kernel version are you using? and bluez-utils? (I
guess 2.25, right?)

filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:

How do you feel about women's rights? I like either side of them.
-- Groucho Marx
[signature.asc (application/pgp-signature, inline)]

Message sent on to Hadmut Danisch <hadmut@danisch.de>:
Bug#359003. Full text and rfc822 format available.

Tags added: moreinfo Request was from Filippo Giunchedi <filippo@debian.org> to control@bugs.debian.org. Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>:
Bug#359003; Package bluez-utils. Full text and rfc822 format available.

Acknowledgement sent to Rainer Dorsch <rdorsch@web.de>:
Extra info received and forwarded to list. Copy sent to Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>. Full text and rfc822 format available.

Message #40 received at 359003@bugs.debian.org (full text, mbox):

From: Rainer Dorsch <rdorsch@web.de>
To: 359003@bugs.debian.org
Subject: udev script missing (?)
Date: Sun, 8 Oct 2006 00:27:12 +0200
Hello,

I just upgraded a sarge system to etch and since hotplug is gone in etch, 
attaching my bluetooth usb dongle 

topsi:~# lsusb -v -s 001:006

Bus 001 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle 
(HCI mode)
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass          224 Wireless
  bDeviceSubClass         1 Radio Frequency
  bDeviceProtocol         1 Bluetooth
  bMaxPacketSize0        64
  idVendor           0x0a12 Cambridge Silicon Radio, Ltd
  idProduct          0x0001 Bluetooth Dongle (HCI mode)
  bcdDevice            5.25
  iManufacturer           0
  iProduct                0
  iSerial                 0
  bNumConfigurations      1


did not start pand as it was with my hotplug script:
topsi:~# cat /etc/hotplug.d/usb/epox-bluetooth.hotplug
#!/bin/sh

# Hotplug script for the Epox BT-DG02A bluetooth dongle for Debian Linux 3.1
#
# The dongle reports several attachments. Therefore we filter for the VERSION.
# pand is started with /etc/init.d/bluez-utils, we restart bluez-utils when a
# dongle is plugged in. On a coldplug (usb dongle is in the system on boot),
# this hotplug script fails (called by rcS.d/S40hotplug), but the regular
# bluez-utils start script rc2.d/S25bluez-utils starts pand in this case

# The direct start-stop-daemon calls are legacy code and should be
# removed if this setup is solid.

pidfile=/var/run/pand.pid
DAEMON=/usr/bin/pand

CHARS=`echo $DEVPATH| wc -c`
VERSION=`echo $DEVPATH|cut -c $((CHARS-3))-$CHARS`

(date
echo $DEVPATH
echo $PRODUCT
echo $TYPE
echo $ACTION
echo $CHARS
echo $VERSION) >> /tmp/epox.log


case `echo $PRODUCT|cut -d / -f 1-2` in
        # a12/1/525 and a12/1/828 have been seen for the Epox BT DB02A
        a12/1) break ;;
        *) exit ;;
esac
case $TYPE in
        224/1/1) break ;;
        *) exit ;;
esac
case $ACTION in
        add)
            if [ ! -z VERSION ]; then
              if [ $VERSION = 1.0 ]; then
                # restart bluez-utils because it might not started up 
correctly
                sleep 2 # required for some reason
                echo Restart bluez-utils >> /tmp/epox.log
                /etc/init.d/bluez-utils restart >> /tmp/epox.log 
2>/tmp/epox.err
#                start-stop-daemon --start --exec $DAEMON -- --nodetach --role 
PANU --search --encrypt --pidfile $pidfile >> /tmp/pand.log
              fi
            fi
            ;;
        remove)
            ifdown bnep0
#            start-stop-daemon --stop --exec $DAEMON --pidfile $pidfile
            /etc/init.d/bluez-utils stop
            ;;
esac
topsi:~# 


Now I thought I have to migrate this script to udev.


But this bug report seems to imply that there should be a build in mechanism, 
which does that for me already. I have bnep0 in my allow-hotplugable 
interface in /etc/network/interface such that after plugging in the dongle, 
an /etc/init.d/bluetooth restart is currently enough to get the connection 
working.

Many thanks,
Rainer





Information forwarded to debian-bugs-dist@lists.debian.org, Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>:
Bug#359003; Package bluez-utils. Full text and rfc822 format available.

Acknowledgement sent to Filippo Giunchedi <filippo@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>. Full text and rfc822 format available.

Message #45 received at 359003@bugs.debian.org (full text, mbox):

From: Filippo Giunchedi <filippo@debian.org>
To: Rainer Dorsch <rdorsch@web.de>, 359003@bugs.debian.org
Subject: Re: [Pkg-bluetooth-maintainers] Bug#359003: udev script missing (?)
Date: Mon, 9 Oct 2006 13:01:17 +0200
[Message part 1 (text/plain, inline)]
On Sun, Oct 08, 2006 at 12:27:12AM +0200, Rainer Dorsch wrote:
> Hello,
> 
> I just upgraded a sarge system to etch and since hotplug is gone in etch, 
> attaching my bluetooth usb dongle 

have a look at udev rules in /etc/udev, you might want to see
bluez-pcmcia-support as it contains some udev rules and the bluetooth_serial
script. You want to match your usb dongle via udev and then use a RUN target
running your modified script.

By the way, this seems a non-bug to me, can I close it or it needs more
attention?

thanks,
filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:

The only way to get rid of a temptation is to yield to it.
-- Oscar Wilde
[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>:
Bug#359003; Package bluez-utils. Full text and rfc822 format available.

Acknowledgement sent to Rainer Dorsch <rdorsch@web.de>:
Extra info received and forwarded to list. Copy sent to Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>. Full text and rfc822 format available.

Message #50 received at 359003@bugs.debian.org (full text, mbox):

From: Rainer Dorsch <rdorsch@web.de>
To: Filippo Giunchedi <filippo@debian.org>
Cc: 359003@bugs.debian.org
Subject: Re: [Pkg-bluetooth-maintainers] Bug#359003: udev script missing (?)
Date: Mon, 9 Oct 2006 16:08:29 +0200
Fillippo,

many thanks for your quick reply. I did not open the original bug, I just 
commented, since my problem was at least similar.

It would have helped me to find some documentation how to attach my own usb 
bluetooth stick to the usb port and get the network up automatically 
in /usr/share/doc/bluez-utils.

I will try your suggestion and if I succeed, I am happy to send you a few 
lines (or if you want to can go ahead and write the lines and I will "test" 
them).

Many thanks,
Rainer

Am Montag, 9. Oktober 2006 13:01 schrieb Filippo Giunchedi:
> On Sun, Oct 08, 2006 at 12:27:12AM +0200, Rainer Dorsch wrote:
> > Hello,
> >
> > I just upgraded a sarge system to etch and since hotplug is gone in etch,
> > attaching my bluetooth usb dongle
>
> have a look at udev rules in /etc/udev, you might want to see
> bluez-pcmcia-support as it contains some udev rules and the
> bluetooth_serial script. You want to match your usb dongle via udev and
> then use a RUN target running your modified script.
>
> By the way, this seems a non-bug to me, can I close it or it needs more
> attention?
>
> thanks,
> filippo
> --
> Filippo Giunchedi - http://esaurito.net
> PGP key: 0x6B79D401
> random quote follows:
>
> The only way to get rid of a temptation is to yield to it.
> -- Oscar Wilde

-- 
Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
jabber: rdorsch@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>:
Bug#359003; Package bluez-utils. Full text and rfc822 format available.

Acknowledgement sent to Rainer Dorsch <rdorsch@web.de>:
Extra info received and forwarded to list. Copy sent to Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>. Full text and rfc822 format available.

Message #55 received at 359003@bugs.debian.org (full text, mbox):

From: Rainer Dorsch <rdorsch@web.de>
To: Filippo Giunchedi <filippo@debian.org>
Cc: 359003@bugs.debian.org
Subject: Re: [Pkg-bluetooth-maintainers] Bug#359003: udev script missing (?)
Date: Fri, 8 Dec 2006 15:11:30 +0100
Hi Filippo,

(I added the bug on cc, that people have a chance to find my setup using 
google)

I added an udev rule and an udev script for bluetooth usb dongles on my 
system. The rule and script are pasted at the end of the mail. 

I think it is not yet enough to be a starting point for bluetooth usb dongles 
in the Debian bluez packages. 

Essentially, what I want to do is:

When an usb dongle is plugged:
-> bring up the bnep0 interface
-> ifplugd triggers
-> get an IP address using dhclient

ifplugd and dhclient work well, I have a three minor issues with the bnep0 
interface:

1) The udev script is only called for "add" actions not for "remove" actions. 
Why?

2) I have a sleep statement in the udev script. Not sure why it is needed (and 
I would like to get rid of it, because it is a source of a race condition)
        sleep 2
        /etc/init.d/bluetooth restart

Without the sleep statement, I see in syslog

Dec  8 13:22:18 topsi kernel: usb 1-2: new full speed USB device using 
uhci_hcd and address 6
Dec  8 13:22:19 topsi kernel: usb 1-2: configuration #1 chosen from 1 choice
Dec  8 13:22:19 topsi hcid[5171]: HCI dev 0 registered
Dec  8 13:22:19 topsi hcid[5171]: Register path:/org/bluez/hci0 fallback:0
Dec  8 13:22:19 topsi hcid[5171]: HCI dev 0 up
Dec  8 13:22:19 topsi hcid[5171]: Device hci0 has been added
Dec  8 13:22:19 topsi hcid[5171]: Starting security manager 0
Dec  8 13:22:19 topsi hcid[5171]: Device hci0 has been activated
Dec  8 13:22:19 topsi sdpd[5173]: terminating...
Dec  8 13:22:19 topsi hcid[5171]: Unregister path:/org/bluez/hci0
Dec  8 13:22:19 topsi hcid[5171]: Unregister path:/org/bluez
Dec  8 13:22:19 topsi hcid[5171]: Exit
Dec  8 13:22:20 topsi hcid[5351]: Bluetooth HCI daemon
Dec  8 13:22:20 topsi sdpd[5353]: Bluetooth SDP daemon
Dec  8 13:22:20 topsi pand[5354]: Bluetooth PAN daemon version 3.7
Dec  8 13:22:20 topsi pand[5354]: Inquiring
Dec  8 13:22:20 topsi hcid[5351]: Register path:/org/bluez fallback:1
Dec  8 13:22:20 topsi hcid[5351]: HCI dev 0 registered
Dec  8 13:22:20 topsi hcid[5351]: Register path:/org/bluez/hci0 fallback:0
Dec  8 13:22:20 topsi hcid[5351]: HCI dev 0 already up
Dec  8 13:22:20 topsi hcid[5351]: Device hci0 has been added
Dec  8 13:22:20 topsi hcid[5351]: Starting security manager 0
Dec  8 13:22:20 topsi hcid[5351]: Device hci0 has been activated
Dec  8 13:22:21 topsi pand[5354]: Inquiry failed. Device or resource busy(16)

With the sleep statement everything works fine:
Dec  8 13:24:08 topsi kernel: usb 1-2: new full speed USB device using 
uhci_hcd and address 9
Dec  8 13:24:08 topsi kernel: usb 1-2: configuration #1 chosen from 1 choice
Dec  8 13:24:08 topsi hcid[5415]: HCI dev 0 registered
Dec  8 13:24:08 topsi hcid[5415]: Register path:/org/bluez/hci0 fallback:0
Dec  8 13:24:08 topsi hcid[5415]: HCI dev 0 up
Dec  8 13:24:08 topsi hcid[5415]: Device hci0 has been added
Dec  8 13:24:08 topsi hcid[5415]: Starting security manager 0
Dec  8 13:24:09 topsi hcid[5415]: Device hci0 has been activated
Dec  8 13:24:11 topsi sdpd[5417]: terminating...
Dec  8 13:24:11 topsi hcid[5415]: Unregister path:/org/bluez/hci0
Dec  8 13:24:11 topsi hcid[5415]: Unregister path:/org/bluez
Dec  8 13:24:11 topsi hcid[5415]: Exit
Dec  8 13:24:12 topsi hcid[5457]: Bluetooth HCI daemon
Dec  8 13:24:12 topsi sdpd[5459]: Bluetooth SDP daemon
Dec  8 13:24:12 topsi pand[5460]: Bluetooth PAN daemon version 3.7
Dec  8 13:24:12 topsi pand[5460]: Inquiring
Dec  8 13:24:12 topsi pand[5460]: Searching for NAP on 00:04:61:82:24:9F
Dec  8 13:24:12 topsi hcid[5457]: Register path:/org/bluez fallback:1
Dec  8 13:24:12 topsi hcid[5457]: HCI dev 0 registered
Dec  8 13:24:12 topsi hcid[5457]: Register path:/org/bluez/hci0 fallback:0
Dec  8 13:24:12 topsi hcid[5457]: HCI dev 0 already up
Dec  8 13:24:12 topsi hcid[5457]: Device hci0 has been added
Dec  8 13:24:12 topsi hcid[5457]: Starting security manager 0
Dec  8 13:24:12 topsi hcid[5457]: Device hci0 has been activated
Dec  8 13:24:12 topsi pand[5460]: Connecting to 00:04:61:82:24:9F
Dec  8 13:24:12 topsi hcid[5457]: link_key_request (sba=00:04:61:81:10:DA, 
dba=00:04:61:82:24:9F)
Dec  8 13:24:12 topsi pand[5460]: bnep0 connected

Then ifplugd and dhclient come up:

Dec  8 13:24:13 topsi ifplugd.agent[5469]: Invoking ifplugd for bnep0
Dec  8 13:24:13 topsi ifplugd(bnep0)[5479]: ifplugd 0.28 initializing.
Dec  8 13:24:13 topsi ifplugd(bnep0)[5479]: Using interface 
bnep0/00:04:61:81:10:DA
Dec  8 13:24:13 topsi ifplugd(bnep0)[5479]: Using detection mode: IFF_RUNNING
Dec  8 13:24:13 topsi ifplugd(bnep0)[5479]: Initialization complete, link beat 
detected.
Dec  8 13:24:13 topsi dhclient: Internet Software Consortium DHCP Client 
2.0pl5

3) At startup the bluetooth network does not come up. I need to replug the usb 
dongle to get it working.


This is the rule file:

topsi:~# cat /etc/udev/bluez-usb-support.rules
# USB adapters
SUBSYSTEM=="usb", BUS=="usb", ENV{MANF_ID}="$sysfs{idVendor}", 
ENV{PROD_ID}="$sysfs{idProduct}"

#topsi:/sys/bus/usb/devices/usb1/1-2# cat idProduct
#0001
#topsi:/sys/bus/usb/devices/usb1/1-2# cat idVendor
#0a12
#topsi:/sys/bus/usb/devices/usb1/1-2#

# Epox BT-DG02A
BUS=="usb", SYSFS{idProduct}=="0001", SYSFS{idVendor}=="0a12", 
SYSFS{bInterfaceNumber}=="00", RUN+="bluetooth_usb"

topsi:~#

Register the udev script:

topsi:/etc/udev/rules.d# ls -l z60_bluez-usb-support.rules
lrwxrwxrwx 1 root root 26 2006-12-07 09:05 z60_bluez-usb-support.rules 
-> ../bluez-usb-support.rules
topsi:/etc/udev/rules.d#

The RUN scripts in /lib/udev

topsi:/etc/udev/rules.d# cat /lib/udev/bluetooth_usb
#!/bin/sh
#
# bluetooth_usb
#
# Bluetooth usb dongle startup
#

echo $* > /tmp/bluetooth_usb.log
echo MANF_ID: $MANF_ID >> /tmp/bluetooth_usb.log
echo ACTION: $ACTION >> /tmp/bluetooth_usb.log

start_bluetooth()
{
#       if [ ! -x /bin/setserial -o ! -x /usr/sbin/hciattach ]; then
#               logger "$0: setserial or hciattach not executable, cannot 
start $DEVNAME"
#               return 1
#       fi

#       IRQ=`/bin/setserial $DEVNAME | sed -e 's/.*IRQ: //'`
#       /bin/setserial $DEVNAME irq 0 ; /bin/setserial $DEVNAME irq $IRQ

        MANF_CARD_ID="${MANF_ID},${CARD_ID}"
        sleep 2
        /etc/init.d/bluetooth restart
}

stop_bluetooth()
{
#       [ -x /bin/fuser ] || return 1

#        /bin/fuser -k -HUP $DEVNAME > /dev/null
}

case "$ACTION" in
   add)
        start_bluetooth
        ;;
   remove)
        stop_bluetooth
        ;;
   *)
        logger "Unknown action received $0: $ACTION"
        ;;
esac
topsi:/etc/udev/rules.d#



Many thanks,
Rainer


Am Montag, 9. Oktober 2006 13:01 schrieben Sie:
> On Sun, Oct 08, 2006 at 12:27:12AM +0200, Rainer Dorsch wrote:
> > Hello,
> >
> > I just upgraded a sarge system to etch and since hotplug is gone in etch,
> > attaching my bluetooth usb dongle
>
> have a look at udev rules in /etc/udev, you might want to see
> bluez-pcmcia-support as it contains some udev rules and the
> bluetooth_serial script. You want to match your usb dongle via udev and
> then use a RUN target running your modified script.
>
> By the way, this seems a non-bug to me, can I close it or it needs more
> attention?
>
> thanks,
> filippo
> --
> Filippo Giunchedi - http://esaurito.net
> PGP key: 0x6B79D401
> random quote follows:
>
> The only way to get rid of a temptation is to yield to it.
> -- Oscar Wilde

-- 
Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
jabber: rdorsch@jabber.org
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/



Information forwarded to debian-bugs-dist@lists.debian.org, Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>:
Bug#359003; Package bluez-utils. Full text and rfc822 format available.

Acknowledgement sent to Filippo Giunchedi <filippo@esaurito.net>:
Extra info received and forwarded to list. Copy sent to Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>. Full text and rfc822 format available.

Message #60 received at 359003@bugs.debian.org (full text, mbox):

From: Filippo Giunchedi <filippo@esaurito.net>
To: Rainer Dorsch <rdorsch@web.de>
Cc: 359003@bugs.debian.org, 359003-submitter@bugs.debian.org
Subject: closing this old bug
Date: Sat, 7 Jul 2007 18:42:58 +0200
Hi,
thanks Rainer for your feedback on the bug.

Hadmut: can you reproduce this bug with bluez-utils 3.7 which is etch?

filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:

I always keep the Titanic in mind when I talk about security or
safety, meaning that nothing is fully secure.
-- Anonymous (?)



Message sent on to Hadmut Danisch <hadmut@danisch.de>:
Bug#359003. Full text and rfc822 format available.

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>:
Bug#359003; Package bluez-utils. Full text and rfc822 format available.

Acknowledgement sent to Hadmut Danisch <hadmut@danisch.de>:
Extra info received and forwarded to list. Copy sent to Debian Bluetooth Maintainers <pkg-bluetooth-maintainers@lists.alioth.debian.org>. Full text and rfc822 format available.

Message #68 received at 359003@bugs.debian.org (full text, mbox):

From: Hadmut Danisch <hadmut@danisch.de>
To: Filippo Giunchedi <filippo@esaurito.net>, 359003-quiet@bugs.debian.org
Cc: Rainer Dorsch <rdorsch@web.de>, 359003@bugs.debian.org, 359003-submitter@bugs.debian.org
Subject: Re: Bug#359003: closing this old bug
Date: Sat, 07 Jul 2007 21:25:29 +0200
Filippo Giunchedi wrote:
> Hi,
> thanks Rainer for your feedback on the bug.
> 
> Hadmut: can you reproduce this bug with bluez-utils 3.7 which is etch?


No, sorry, I am not using this bluetooth mobile anymore. My new mobile
phone uses a USB cable.


regards
Hadmut



Information stored:
Bug#359003; Package bluez-utils. Full text and rfc822 format available.

Acknowledgement sent to Hadmut Danisch <hadmut@danisch.de>:
Extra info received and filed, but not forwarded. Full text and rfc822 format available.

Message sent on to Hadmut Danisch <hadmut@danisch.de>:
Bug#359003. Full text and rfc822 format available.

Reply sent to Filippo Giunchedi <filippo@debian.org>:
You have taken responsibility. Full text and rfc822 format available.

Notification sent to Hadmut Danisch <hadmut@danisch.de>:
Bug acknowledged by developer. Full text and rfc822 format available.

Message #81 received at 359003-done@bugs.debian.org (full text, mbox):

From: Filippo Giunchedi <filippo@debian.org>
To: Hadmut Danisch <hadmut@danisch.de>
Cc: 359003-done@bugs.debian.org, Rainer Dorsch <rdorsch@web.de>
Subject: Re: Bug#359003: closing this old bug
Date: Sun, 8 Jul 2007 09:37:07 +0200
On Sat, Jul 07, 2007 at 09:25:29PM +0200, Hadmut Danisch wrote:
> Filippo Giunchedi wrote:
> > Hi,
> > thanks Rainer for your feedback on the bug.
> > 
> > Hadmut: can you reproduce this bug with bluez-utils 3.7 which is etch?
> 
> 
> No, sorry, I am not using this bluetooth mobile anymore. My new mobile
> phone uses a USB cable.

allright, I'm therefore closing this bug, reopen if appropriate

filippo
--
Filippo Giunchedi - http://esaurito.net
PGP key: 0x6B79D401
random quote follows:

Computer Science is no more about computers than astronomy is about telescopes.
-- Edsger Dijkstra



Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Mon, 06 Aug 2007 07:25:22 GMT) Full text and rfc822 format available.

Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Mon Apr 21 06:02:35 2014; Machine Name: buxtehude.debian.org

Debian Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.