Bluez drivers compilation: 90% done

[hugo]

You must use participate to a local area network profile on your Pocket PC to connect. It is the PAN profile. Rfcomm profile won't work (ie connect as modem). But if you get a working setup on this, i'll glad to hear. Problem is to get a working rfcomm.o with tty support. Even user mode rfcomm doesn't work with this

[xlephant]

hi hugo,

thanks for the reply and help. i've a MDA Compact (Imate Jam) with the MS bluetooth stack. and that is bad. because it is not supporting PAN profile. i tried with an other stuck from here:
http://forum.xda-developers.com/viewtopic.php?t=18537

but doesn't work with headsets ;-). so i need (i think) the DUN profile. do you know how to integred it? i'm not sure about the DUN profile but i hope it will be work. if you understand german. see here:
http://www.ppc-welt.info/community/s...30&postcount=9

hope you can help me. thx a lot.

[hugo]

I know what you want, and I tryed also as wel, even on stuff not present here. DUN is not possible ATM with bluez. You might have more chance with affix stack.

You might try also the cab file with the widcomm stack, if oyu are not afraid of a hard reset to go back to the previous one (do a full backup before installing so you can go back quickly).

You can activate headset profile with a registry setting if you need.

For DUN, you need a working rfcomm program. If you try the one from my distrib, it won't work, because rfcomm.o doesn't include tty.o, and it must be included in kernel to work, not as module.

You also need chat program (from the compilation source of pppd) to establish the communication. But it won't work before we get a valid rfcomm.o

[xlephant]

You might try also the cab file with the widcomm stack,

a lot of people tried already the widcomm stack from toshiba, see here:

http://forum.xda-developers.com/viewtopic.php?t=15604

but not with success. :-(

You can activate headset profile with a registry setting if you need.

what do you mean with that? in context to the widcomm stack or the Bluesoleil stack? do YOU know how?

anyway, maybe i have to try the affix stack again. i tried before but it didn't run who knows why?

thx hugo maybe we can get the rfcomm running

[hugo]

On widcomm stack, there is a registry setting to activate headset profile. I know this for sure on my Ipaqs. The widcomm stack you can install is probably not different. I can search the registry setting for you, but it is heavily posted on brighthand forum. This is if you want to go on the PAN road. For the DUN, I've given up the rfcomm way, but I can post my finding if somebody want's to go further.

[m.scholze]

Hi there,

in accordance with this Hugo&Dex's how-to thread I've been trying to get BT dongle (MSI MS-6967) to work on the Asus WL-500gx with Oleg's firmware 1.9.2.7-CR6b.

Everything works well until the last line of this script:

insmod /tmp/harddisk/bluetooth/lib/modules/bluez.o
insmod /tmp/harddisk/bluetooth/lib/modules/hci_usb.o
insmod /tmp/harddisk/bluetooth/lib/modules/l2cap.o
insmod /tmp/harddisk/bluetooth/lib/modules/bnep.o
export LD_LIBRARY_PATH='/tmp/harddisk/bluetooth/lib'
/tmp/harddisk/bluetooth/sbin/sdpd
/tmp/harddisk/bluetooth/sbin/hcid
/tmp/harddisk/bluetooth/bin/sdptool add NAP
/tmp/harddisk/bluetooth/bin/sdptool add DUN
/tmp/harddisk/bluetooth/bin/pand --listen --role NAP

When I start pand, there are a lot of these lines in syslog:

Jul 24 10:48:06 pand[2590]: Accept failed. Resource temporarily unavailable(11)

and their amount rapidly increases (aprox. 100 lines per second) until I kill pand.

Can someone tell me what's wrong and how to set it right?

Thank you.

[remixme]

Yep, I am definitely having the same problem as m.scholze on 1.9.2.7-5a using an Acer BT500.

My script is setup the same as m.scholzes with all the files in the appropriate places. I have also copied the correct files to /etc/bluetooth/

My script is slightly different to m.scholze as it has the -M

/tmp/harddisk/bluetooth/bin/pand --listen --role NAP -M

But I just get that same error:
Jan 1 00:17:17 pand[549]: Bluetooth PAN daemon
Jan 1 00:17:17 pand[549]: Accept failed. Resource temporarily unavailable(11)
Jan 1 00:17:17 pand[549]: Accept failed. Resource temporarily unavailable(11)
Jan 1 00:17:17 pand[549]: Accept failed. Resource temporarily unavailable(11)
Jan 1 00:17:18 pand[549]: Accept failed. Resource temporarily unavailable(11)

Any ideas?

[hugo]

Don't forget the drivers are usually compiled using one version of the system, and there has been one major evolution in Oleg's firmware since then. I guess there is some incompatibility, but I haven't tested. I don't want to go back to this, because there is already a bluez project available as a package, and it should be this one to be maintained from now on.

[remixme]

Okay, I understand, I'm willing to have a go at getting this working again in any case......

Ironically I am in a similar situation to xlephant in that I have an mda compact.
I got the bluesoleil stack detailed forums.xda-developers.com working for PAN on my device, and I managed to get good internet access over bluetooth and ran SkyPE on my pocketpc! Now I just want the bluetooth intregrated with the router!

I mean I even had to install a hacked stack to get my dongle working under XP SP2, as mine is no longer supported, I guess since I've come this far, I may as well carry on.

Xlephant judging my his log entries managed to get pand running using 1.9.2.7-3b, so I may try downgrading to that to see if I get the same result.

I can also try another bluetooth dongle, failing these options I presume I'd have to go and recompile the modules against the lastest source.

[hugo]

You can try an older version, if you have PAN profile on your XDA compact. I've been testing this also for a pocket pc, but lost interest because all my pocket pc have wi-fi. Actually, you can get a full network connection using the firmware version that was up to date at the date of my first post in the thread, but I wanted to make DUN working to automaticaly connect. PAN was perfectly operational for me, but needed to be activated by hand, and also needed a fixed IP on pocket pc side (on the bluetooth network card).
Your dongle should be working because you don't have any error message in the loading of the modules ( .o files)

[remixme]

Well it works with 1.9.2.7-3b, so at least now I have an option.

Basically under 3b it doesnt display the behaviour mentioned above, furthermore if I do a bluetooth discovery on my mda compact it appears as 'bluez'

I can find and join the PAN service, and a ping from the router to 10.0.0.2 brings back results in the 100-200ms range, I couldn't quite get internet to work under pocket IE but I suspect there is a setting wrong on pocket pc.

btw Hugo, thank's for all the hard work you have put into this thread!

I understand the fact that you have to wish to return to this stuff as it is quite time consuming! But I appreciate the fact that you took the time to reply!

Maybe if I can figure out which exact revision that has broke bluez, a fix can be found, as compiling from different sources seems like a bit of a stab in the dark without knowing the exact cause.

[remixme]

Well I can confirm one thing and that is that the upgrade to 1.9.2.7-4 is the one that breaks bluez 1.9.2.7-3c works fine.

All firmwares beyond this point exhibit the resource unavailable problem. Now to figure out what has changed between these two points that could have broken pand support?

I guess I could always try compiling from scratch with certain patches removed to try and find out more. But I suspect it is the fact that the uclibc chain has been updated?
http://wl500g.info/showthread.php?t=1917

[hugo]

have you tryed using a mix between my bluez version, and the 2 packages available as ipkg? I remember compiling the pan drive separatly by recompiling this with kernel from the source. I think somebody can try to just select then bluez PAN support in kernel and compile the module from one of the latest working environment. I cannot do it as I don't have a proper compiling setup anymore. The basic would be to setup the firmware compile environment as described by oleg, and to test it without any change. Then you have to modufy the kernel .config file to add the BNEP line (you have to search for this one cause my memory is too far away). You will end up with the bnep.o module that should make the trick. Hope this work.

[remixme]

Thanks for the tip,

I have gentoo linux almost setup on another partition, just need to get around to sorting a networking problem and then I can do the recompile. May take me a while but I shall report back results.

[remixme]

Right, after getting my linux install back on my computer.
I went and recompiled the modules using the lastest 1.9.2.7-6b sources.
Basically I went and compiled the firmware normally, I just changed the option for bluez in kernel.config to =m

And then got the newly compiled files, they are present in the attached file.

I had some success with the new files in that, when I replaced all four of the module files with my new ones, the script runs succesfully and pand doesn't panic.

My device detects the pan network and I can connect to it.
The router log shows my device connecting, so then I run

ifconfig bnep0 10.0.0.1
brctl addif br0 bnep0

I can then ping 10.0.0.1 but the problem is that I cannot ping 10.0.0.2!

My device is setup as before when I had it working with -3c, so I am doubtful that it is a device problem.

Here's my (edited) log:

Oct 22 20:18:30 login[131]: root login  on `pts/0' 
Oct 22 20:18:50 kernel: BlueZ Core ver 2.2 Copyright (C) 2000,2001 Qualcomm Inc
Oct 22 20:18:50 kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Oct 22 20:18:50 kernel: BlueZ HCI USB driver ver 2.1 Copyright (C) 2000,2001 Qualcomm Inc
Oct 22 20:18:50 kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Oct 22 20:18:50 kernel: usb.c: registered new driver hci_usb
Oct 22 20:18:50 kernel: BlueZ L2CAP ver 2.1 Copyright (C) 2000,2001 Qualcomm Inc
Oct 22 20:18:50 kernel: Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
Oct 22 20:18:51 kernel: BNEP: BNEP2 ver 1.0
Oct 22 20:18:51 kernel: BNEP: Copyright (C) 2002 Inventel
Oct 22 20:18:51 kernel: BNEP: Written 2001,2002 by
Oct 22 20:18:51 kernel: BNEP: ^IClement Moreau <clement.moreau@inventel.fr> David Libault <david.libault@inventel.fr>
Oct 22 20:18:51 kernel: BNEP: Copyright (C) 2002 Maxim Krasnyanskiy <maxk@qualcomm.com>
Oct 22 20:18:51 sdpd[161]: Bluetooth SDP daemon 
Oct 22 20:18:51 hcid[164]: Bluetooth HCI daemon
Oct 22 20:18:51 hcid[164]: HCI dev 0 up
Oct 22 20:18:51 hcid[164]: Starting security manager 0
Oct 22 20:18:51 pand[170]: Bluetooth PAN daemon
Oct 22 20:19:33 pand[188]: New connection from 00:02:5B:00:A1:A1 bnep0 		// Connection from the device
Oct 22 20:19:57 kernel: device bnep0 entered promiscuous mode
Oct 22 20:20:07 kernel: br0: port 3(bnep0) entering listening state
Oct 22 20:20:07 kernel: br0: port 3(bnep0) entering learning state
Oct 22 20:20:07 kernel: br0: port 3(bnep0) entering forwarding state
Oct 22 20:20:07 kernel: br0: topology change detected, propagating
Oct 22 20:20:29 kernel: br0: port 3(bnep0) entering disabled state		// I manually disconnect the device
Oct 22 20:20:29 kernel: br0: port 3(bnep0) entering disabled state
Oct 22 20:20:29 kernel: device bnep0 left promiscuous mode