DBUS Error with OpenWRT
Facultas
I'm trying to get Bluetooth working on the BB and I'm using OpenWRT,
I've installed dbus and (I think) all necessary packages but when I
try to run dbus-daemon I get this error...
root@OpenWrt:/# dbus-daemon --system
Failed to start message bus: Failed to open socket: Address family not
supported by protocol
root@OpenWrt:/#
Anyone have any ideas on what the problem could be? I think it could
be something to do with the system.conf file, in particular this
section...
<!-- Only listen on a local socket. (abstract=/path/to/socket
means use abstract namespace, don't really create filesystem
file; only Linux supports this. Use path=/whatever on other
systems.) -->
<listen>unix:path=/var/run/dbus/system_bus_socket</listen>
...but I'm not sure. Anything I can see on Google about this error
all seems to be general stuff and is decidedly unhelpful!
Andrew Scheller
bifferboard-slackware page might provide some useful pointers?
http://sites.google.com/site/bifferboard/Home/desktop-linux-distributions/slackware/bluetooth
Lurch
> --
> You received this because you are subscribed to the "Bifferboard" Google group - honest!
> To unsubscribe from this group, send email to bifferboard...@googlegroups.com
>
Facultas
that guide you mentioned) but the problem with that particular one is
that dhcpcd isn't working on it (but I can't remember offhand what the
error message was, whereas udhpc on the open WRT one does work). I
will find out over the weekend what exactly was wrong with that and
create a separate post for it. Also the Slackware filesystem is
huuuuuge. I'd prefer OpenWRT as it seems to be running much quicker
than Slackware.
.
On Feb 5, 3:40 pm, Andrew Scheller <ya...@loowis.durge.org> wrote:
> I've not got any bluetooth hardware, but I dunno if this
>
> Lurch
>
Andrew Scheller
> that guide you mentioned) but the problem with that particular one is
> that dhcpcd isn't working on it (but I can't remember offhand what the
> error message was,
I've only used the latest tarball-9 of slackware, and don't have any
problems with getting a dhcp lease . Sorry that's not very helpful!
> create a separate post for it. Also the Slackware filesystem is
> huuuuuge.
Huge? It's smaller than a CD iso image. How tiny is your USB stick? ;-)
> I'd prefer OpenWRT as it seems to be running much quicker
> than Slackware.
Yeah, OpenWRT is designed for limited-resources embedded systems,
whereas the slackware for bifferboard is the 'full' desktop version.
Much more flexibility (and compatibility) at the price of a bit of
speed. At least with Linux you get to make that choice :)
Lurch
d1savowed
Quick question, what are you trying to do with bluetooth? Dbus is
fairly heavy on a system and depending on what you are trying to do,
it may not be needed.
As for the "Address Family Not Supported", the first thing that
springs to mind is that your OS doesn't have support for Unix sockets
either compiled in or loaded as a module. Which version of OpenWRT do
you have installed, and what kernel for that matter.
If its an old release, it may well be that the socket module needs
loading. I believe in the later release of OpenWRT I built I enabled
it by default, but im not 100% sure.
Stu
Facultas
On Feb 6, 1:35 am, d1savowed <stu...@linux-depot.com> wrote:
> Hi Facultas,
> Quick question, what are you trying to do with bluetooth?Dbusis
> fairly heavy on a system and depending on what you are trying to do,
> it may not be needed.
I'm trying to get RSSI signals off it, got a C app doing that for me
using bluez. I've managed to get it working on Slackware now - the
problem with that was that dhcpcd wasn't detecting the proxy settings
after I'd set them (still no idea why) but I've set it up on a non-
proxy network now and it appears to be fine.
> As for the "Address Family Not Supported", the first thing that
> springs to mind is that your OS doesn't have support for Unix sockets
> either compiled in or loaded as a module. Which version of OpenWRT do
> you have installed, and what kernel for that matter.
Yeah that's what I was thinking too, but im not sure of the kernel
module or where to get it. I may try just recompiling a different
version of OpenWRT, I had been using the version in this guide on the
bifferboard website....
http://sites.google.com/site/bifferboard/Home/howto/compile-firmware
(sorry, not sure how to add that as a link)
So whatever version of OpenWRT that is (sorry I can't be more
helpful!)
I've noticed there is another page on the BB site about OpenWRT should
I be using the versions there?
> If its an old release, it may well be that the socket module needs
> loading. I believe in the later release of OpenWRT I built I enabled
> it by default, but im not 100% sure.
>
> Stu
Is it merely a compiler option then? Do you know what heading that
would be under?
Sorry for the late reply, it's been a bit of a busy weekend. I do
appreciate the help however.
Andrew Scheller
> problem with that was that dhcpcd wasn't detecting the proxy settings
Um, I thought dhcpd only detected IP settings? - you normally have to
still configure proxy settings manually (usually by setting an
environment variable).
> version of OpenWRT, I had been using the version in this guide on the
> bifferboard website....
> http://sites.google.com/site/bifferboard/Home/howto/compile-firmware
> So whatever version of OpenWRT that is (sorry I can't be more
> helpful!)
I think that's an 'old' guide, and I *believe* this is the latest guide
http://sites.google.com/site/bifferboard/openwrt-svn
Unfortunately this is all it says about the kernel: "Your rootfs has
been created, next you need to create a suitable kernel."
> I've noticed there is another page on the BB site about OpenWRT should
> I be using the versions there?
Yeah, there seem to be several different versions of openwrt floating
around (both on the wiki, on sourceforge, and in svn) - all seems a
bit confusing - which is why I'm personally sticking to Slackware (the
Biff-updated distro) for now.
Lurch
Facultas
On Feb 9, 3:07 pm, Andrew Scheller <ya...@loowis.durge.org> wrote:
> > using bluez. I've managed to get it working on Slackware now - the
> > problem with that was that dhcpcd wasn't detecting the proxy settings
>
> Um, I thought dhcpd only detected IP settings? - you normally have to
> still configure proxy settings manually (usually by setting an
> environment variable).
>
Ah sorry I explained myself poorly there, I have set the proxy
settings manually its just not picking them up for some reason. The
http_proxy variable has def. been set it's just not picking it up.
> > version of OpenWRT, I had been using the version in this guide on the
> > bifferboard website....
> >http://sites.google.com/site/bifferboard/Home/howto/compile-firmware
> > So whatever version of OpenWRT that is (sorry I can't be more
> > helpful!)
>
> I think that's an 'old' guide, and I *believe* this is the latest guidehttp://sites.google.com/site/bifferboard/openwrt-svn
Yeah I just compiled that today, will let you know how I get on.
Andrew Scheller
>> > problem with that was that dhcpcd wasn't detecting the proxy settings
>>
>> Um, I thought dhcpd only detected IP settings? - you normally have to
>> still configure proxy settings manually (usually by setting an
>> environment variable).
>
> Ah sorry I explained myself poorly there, I have set the proxy
> settings manually its just not picking them up for some reason. The
> http_proxy variable has def. been set it's just not picking it up.
Why are you expecting dhcpcd to work through an http proxy? ;)
Lurch
Facultas
> Why are you expecting dhcpcd to work through an http proxy? ;)
>
Is it not able to? Ah, am I just being a dufus here? When I googled it
it just said to ~$export http_proxy inserthttpproxyhere
Andrew Scheller
> Is it not able to? Ah, am I just being a dufus here?
I'm afraid so ;) HTTP and DHCP are *entirely* different protocols.
Without a specific DHCP-relay, DHCP will only work within one LAN segment.
> When I googled it
> it just said to ~$export http_proxy inserthttpproxyhere
Yeah, that works fine for programs that work over HTTP e.g. wget, curl or lynx.
Lurch
Facultas
described entirely the wrong problem. It is slapt-get that isnt
detecting the http_proxy env. variable, not (as I had said) dhcp.
Hopefully it's all a bit more clear now without me confusing things by
talking about problems that don't exist :P Interestingly enough on
the OpenWRT distribution I have on my other BB opkg is able to use the
proxy settings just fine.
On a side note I should have the newer OpenWRT version from this
guide
http://sites.google.com/site/bifferboard/openwrt-svn
on ANOTHER BB (I have 5 of them :P) later on today or by the latest
tomorrow. Will let you know if DBUS works on that.
-Facultas
Andrew Scheller
> described entirely the wrong problem.
:-D Happens to us all at some point.
> It is slapt-get that isnt
> detecting the http_proxy env. variable, not (as I had said) dhcp.
> Hopefully it's all a bit more clear now without me confusing things by
> talking about problems that don't exist :P
Ah, that makes more sense now!
According to the FAQ it should just work though...
http://software.jaos.org/git/slapt-get/plain/FAQ.html#slgFAQ24
> Interestingly enough on
> the OpenWRT distribution I have on my other BB opkg is able to use the
> proxy settings just fine.
That doesn't mean much, opkg != slapt-get
> on ANOTHER BB (I have 5 of them :P) later on today or by the latest
And I thought I was crazy for having 3 bifferboards ;)
Good luck with your experimentation...
Lurch