From: Mick Semb Wever <mick@semb.wever.org>
To: linux-bluetooth@vger.kernel.org
Subject: Works in 2.6.26, broken in 2.6.27 & 2.6.28 [WAS: Re: bnep module in 2.6.27 fails to provide bnep0 device]
Date: Sat, 03 Jan 2009 16:06:09 +0100 [thread overview]
Message-ID: <1230995170.10252.7.camel@localhost> (raw)
In-Reply-To: <1230983567.6118.25.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
> I'm using the following combination on gentoo:
>
> linux-2.6.27 (64-bit)
> bluez-libs-3.36
> bluez-utils-3.36
The problem exists the same after an upgrade to kernel-2.6.28
Downgrading to 2.6.26 everything works well.
The same environment is being used so the userspace seems not at fault.
Working on 2.6.26 gives the kernel logging:
[pand] Bluetooth PAN daemon version 3.36
[pand] Connecting to 00:19:63:14:8C:6C
[hcid] link_key_request (sba=00:10:60:D1:7C:31, dba=00:19:63:14:8C:6C)
[pand] bnep0 connected
[ifplugd(bnep0)] ifplugd 0.28 initializing.
[ifplugd(bnep0)] Using interface bnep0/00:10:60:D1:7C:31
[ifplugd(bnep0)] Using detection mode: IFF_RUNNING
[ifplugd(bnep0)] Initialization complete, link beat detected.
[ifplugd(bnep0)] Executing '/etc/ifplugd/ifplugd.action bnep0 up'.
[dhcpcd] bnep0: dhcpcd 4.0.7 starting
[ifplugd(bnep0)] client: bnep0: dhcpcd 4.0.7 starting
[dhcpcd] bnep0: broadcasting for a lease
[ifplugd(bnep0)] client: bnep0: broadcasting for a lease
[dhcpcd] bnep0: offered 89.8.70.95 from 89.8.70.93
...etc etc from a working connection...
~mck
--
"Do or do not there is no try." Yoda
| semb.wever.org | sesat.no | sesam.no |
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-03 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 11:52 bnep module in 2.6.27 fails to provide bnep0 device Mick Semb Wever
2009-01-03 15:06 ` Mick Semb Wever [this message]
2009-06-28 18:40 ` [SOLUTION] Works in 2.6.26, broken in 2.6.27 & 2.6.28 [WAS: Re: bnep module in 2.6.27 fails to provide bnep0 device] Mck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1230995170.10252.7.camel@localhost \
--to=mick@semb.wever.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox