From: Mick Semb Wever <mick@semb.wever.org>
To: linux-bluetooth@vger.kernel.org
Subject: bnep module in 2.6.27 fails to provide bnep0 device
Date: Sat, 03 Jan 2009 12:52:47 +0100 [thread overview]
Message-ID: <1230983567.6118.25.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 2580 bytes --]
This used to work for me but after some system updates is now broken.
I'm using the following combination on gentoo:
linux-2.6.27 (64-bit)
bluez-libs-3.36
bluez-utils-3.36
Restarting bluetooth, with the usb bluetooth dongle in, gives in the
system log:
[hcid] Bluetooth HCI daemon
[hcid] Parsing /etc/bluetooth/main.conf failed: No such file or directory
[hcid] Starting SDP server
[hcid] Unix socket created: 11
[hcid] Registered manager path:/org/bluez/audio
[hcid] Registered input manager path:/org/bluez/input
[hcid] Starting experimental netlink support
[kernel] pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
[hcid] Failed to find Bluetooth netlink family
[hcid] Can't init plugin /usr/lib64/bluetooth/plugins/netlink.so
[hcid] bridge pan0 created
[hcid] Registered manager path:/org/bluez/network
[hcid] Registered server path:/org/bluez/network/nap
[hcid] Registered server path:/org/bluez/network/gn
[hcid] Registered server path:/org/bluez/network/panu
[hcid] Registered manager path:/org/bluez/serial
[hcid] HCI dev 0 registered
[hcid] HCI dev 0 already up
[hcid] Device hci0 has been added
[hcid] Starting security manager 0
[hcid] Device hci0 has been activated
Then running "pand -c XX" I get:
[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
[/etc/init.d/net.bnep0] ERROR: interface bnep0 does not exist
[/etc/init.d/net.bnep0] Ensure that you have loaded the correct kernel module for your hardware
[/etc/init.d/net.bnep0] ERROR: net.bnep0 failed to start
It seems pand connects through the bnep0 device, and indeed the mobile
phone i'm connecting to registers the connection and itself connects to
the 3g network, but the kernel complains and the connection is quickly dropped...
I have googled around without any luck at all.
The bnep module is definitely loaded, i have tried reloading it, and
restarting the system. And recompiling the kernel with modules built-in
instead.
I'm quite lost here and hoping anybody can help, or instruct what more
information is required.
~mck
ps this was original posted to http://gmane.linux.network which i
presumed, too late, is an advanced development list. I gather this is
the right list as it is the conglomeration of the previous bluez.users
and bluez.devel lists.
--
"Don't use Outlook. Outlook is really just a security hole with a small
e-mail client attached to it." Brian Trosko
| semb.wever.org | sesat.no | sesam.no |
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-01-03 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 11:52 Mick Semb Wever [this message]
2009-01-03 15:06 ` 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] Mick Semb Wever
2009-06-28 18:40 ` [SOLUTION] " 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=1230983567.6118.25.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