Bluez 4.61 with GUI

[jemimah]

I did have some test runs where the installer would not create the /var/run/dbus and /var/lib/dbus directories. They are in the pet, but I guess it's a bug in the installer.

When I get a chance, I'll see if I can update the dbus pet to be more forceful about this.

[ttuuxxx]

all you have to is have a blank /var/lib/dbus/ directory
and have the user add
dbus-uuidgen --ensure &

to near the bottom of his/her /root/.xinitrc file:)
ttuuxxx

[jemimah]

It's already in the /etc/init.d/dbus script. Creating the directories that are missing should be good enough to get it going.

[aarf]

created blank directory /var/lib/dbus/

and did the modification

Code: Select all

dbus-uuidgen --ensure &

but still got errors and no gui until after adding the second directory at /var/run/dbus

however still not connected.

puppy sees mobile phone Sony-erricsonG502 but phone doesn't see puppy.
phone is using same settings that enable bluetooth connection in knoppix531 immediately before booting puppy431.
g502 connects via USB cable using pupdial and has modem detected as ttyACM0
gprs-connect detects ttyS0 but fails to connect.

sending via bluetooth stops at the image screen below and doesn't send and doesn't show as connected on the phone.
various code cut at various times most interesting is perhaps
bluetooth-wizar[12453]: segfault at 0 ip b7e5e980 sp bf908e60 error 4 in libdbus -1.so.3.4.0[b7e54000+35000]
see below for context

Code: Select all

  ath5k 0000:01:00.0: registered as 'phy0'
i801_smbus 0000:00:1f.3: PCI INT B -> Link[LNKD] -> GSI 7 (level, low) -> IRQ 7
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: Generic Bluetooth USB driver ver 0.5
usbcore: registered new interface driver btusb
phy0: Selected rate control algorithm 'minstrel'
ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
Clocksource tsc unstable (delta = -413442562 ns)
lp: driver loaded but no devices found
evdev.c(EVIOCGBIT): Suspicious buffer size 511, limiting output to 64 bytes. See                               http://userweb.kernel.org/~dtor/eviocgbit-bug.html
usb 1-2: USB disconnect, address 2
usb 1-2: new high speed USB device using ehci_hcd and address 7
usb 1-2: configuration #1 chosen from 1 choice
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 7
usb-storage: waiting for device to settle before scanning
usb 1-2: USB disconnect, address 7
usb 2-2: new full speed USB device using uhci_hcd and address 2
usb 2-2: configuration #3 chosen from 1 choice
cdc_acm 2-2:3.1: ttyACM0: USB ACM device
cdc_wdm 2-2:3.7: cdc-wdm0: USB WDM device
cdc_acm 2-2:3.3: ttyACM1: USB ACM device
usbcore: registered new interface driver cdc_wdm
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapter           s
usb0: register 'cdc_ether' at usb-0000:00:1d.0-2, CDC Ethernet Device, 02:80:37:                              0e:03:00
usbcore: registered new interface driver cdc_ether
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (8056 buckets, 32224 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: reset high speed USB device using ehci_hcd and address 5
usb 1-5: reset high speed USB device using ehci_hcd and address 5
# 

Code: Select all

# ./bluetooth
+ killall dbus-launch
+ killall bluetoothd
+ killall bluetooth-applet
killall: bluetooth-applet: no process killed
+ killall obexd
killall: obexd: no process killed
+ /etc/init.d/dbus restart
Stopping system message bus...
15518 ?        Zs     0:00 dbus-daemon <defunct>
+ sleep 1
+ mkdir /root/bluetooth-share
+ bluetoothd -n
bluetoothd[16041]: Bluetooth daemon 4.61
bluetoothd[16041]: Unable to get on D-Bus
+ /usr/libexec/obexd --ftp --opp -r /root/bluetooth-share -n
+ sleep 1
Failed to connect to socket /tmp/dbus-eJIZiklUb0: Connection refused
obexd[16042]: manager_init failed
+ bluetooth-applet
# Can't get session bus: Failed to connect to socket /tmp/dbus-eJIZiklUb0: Connection refused

Code: Select all

Bluetooth: Generic Bluetooth USB driver ver 0.5
i801_smbus 0000:00:1f.3: PCI INT B -> Link[LNKD] -> GSI 7 (level, low) -> IRQ 7
usbcore: registered new interface driver btusb
phy0: Selected rate control algorithm 'minstrel'
ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
Clocksource tsc unstable (delta = -300472249 ns)
lp: driver loaded but no devices found
evdev.c(EVIOCGBIT): Suspicious buffer size 511, limiting output to 64 bytes. See                               http://userweb.kernel.org/~dtor/eviocgbit-bug.html
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapter                              s
bluetooth-wizar[12453]: segfault at 0 ip b7e5e980 sp bf908e60 error 4 in libdbus                              -1.so.3.4.0[b7e54000+35000]
PPP generic driver version 2.4.2

[jemimah]

Dbus crashing again, weird since it's the same dbus package I used last time - just changed it to use a proper init script. Using the same script on Puppeee with no issues.

[paulski]

I think its something new with Puppy 4.31 or with the 2.6.30.5 Kernel and newer.
I've tried all the pets on a clean install - no go.
I've also tried older sets of bluez obex etc. that I successfully used on older puppies (e.g 4.12) without any problems -albeit at the command line/script level.
Now none of those things work anymore.

Common to both approaches - I can scan and find Bluetooth devices via my USB dongle. Shows up fine in the bluetooth-wizard.
Connecting in any form goes bad and no notification goes through to the device to punch in a pin number.

Common errors at the command line show things like:
From passkey-agent "Can't get on system bus"
or others like rfcomm connect :"Can't connect RFCOMM socket: No route to host"
Or hcid "Unable to get on D-Bus"

Curious.....

[Pro]

Hi jemimah,
You have a DEV part of GConf and GConf-dbus for compile bluez-gnome?
Please post it on forum.

[jemimah]

The dev pet can be downloaded here:
http://www.murga-linux.com/puppy/viewto ... 099#343099

[cklammer]

For which Puppy version is this post? Would this work on 4.10?

Just asking before I run waste time running against any walls ...

[jemimah]

I've only tested on 4.3. I'm doubtful about earlier versions, as the gtk version on 4.3 is even technically too old to run the gnome-bluetooth tools.

Something is screwy with the dbus install here too. I intend to take a look when I get a chance but I'm trying to get Puppeee to a releasable quality the moment and it's pretty much taking all my time.

[Volodya]

Hi!

I just wanted to thank the guy who put all this together.

I report these bluetooth dongles to be working:

ISSCEDRBTA 0x1131:0x1004 and
0xa12:0×1

Both generics

Worked fine for sending files from the computer to the telephone (not for receiving).

The computer is shown in the telephone's list for sending, but when I press send I get "sending failed".

Should I add the telephone's mac address to some kind of list for enabling the computer to receive files? Which one is the shared directory if I want to access to the computer from the telephone? Where to set it?

Thank you guys, you rock!

[pabloA]

Volodya.

Have you tried running this in a console -

obexfs -b [phone mac] ~/bluetooth-share

[aarf]

Volodya.

Have you tried running this in a console -

obexfs -b [phone mac] ~/bluetooth-share

success in a slow fashion.
clicked bluetooth analyser in menu>network not much able to be done there.

then in terminal did

Code: Select all

# bluetooth-browse

which after a while popped-up a rox window with a folder with what looked like a mac address for a name
so did

Code: Select all

# obexfs -b 00:27:F8:D6:93:F0 /root/bluetooth-share
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
# 

where 00:27:F8:D6:93:F0 is [phone mac]

(then at this point here i connected my usb cable to my phone because i though failure had occurred)

after a longish time and then more longish time for the folder
/root/bluetooth-share/phone memory
to be fully populated i was able to copy things slowly from my phone to my eeepc for the first time.
not sure yet which are the needed steps. above

[linuxgnuru]

In Fedora 14, I have tangoGPS working just fine using bluetooth rfcomm with my Nokia E75 phone's GPS, just wondered how to get the bluetooth rfcomm working under puppy and if this tango will be able to use serial ports not just usb?

[jemimah]

Fluppy011 comes with both bluetooth and tango. Probably it's easiest to start there.

[gary101]

Hi jemimah

Thanks for your work on this. I have long thought that the dbus and bluetooth infrastructure is a serious lack in puppy, especially with more and more devices and uses becoming available.

It seems the main problem is dbus and getting it to play nicely. I have had some serious trouble getting your script to run consistantly and have to manually kill processes and rerun the script to get dbus working.

I have found however that moving the script from startup and starting it manually from elsewhere seems to start the gui with no problems.

The only errors I now get are about missing conf files in /usr/etc/bluetooth, these are:
serial.conf
audio.conf
input.conf
network.conf

I have not looked into these to deeply but think I understand, with perhaps the exception of serial.conf, what services they configure. I have copied an audio.conf I found on the web so I can have a look at the options for it.

Personally the reason I want to get bluetooth working is to have a wireless headset set up for skype, but I cannot seem to find the btsco compiled for 413 kernel 2.6.30.5
If anyone has this compiled I would be really grateful.

Anyway, I will do some work on the missing config files and report if I have any success.

All the best

Gary

[jemimah]

Your documentation seems out of date. Unfortunately the bluez wiki seems to be MIA for quite some time now. You need to do something more like this: http://wiki.zenwalk.org/index.php?title ... th_headset

I still recommend using fluppy for the newer bluez (and working dbus). Bluez releases loads of bugfixes every couple weeks, so the newer the version, the better.

Plus I don't support running this version at all - it never really worked and I don't have much motivation to mess with it.

[jakfish]

For those of you who love the struggles of bluetooth in linux, I'm attaching both a pet and the actual directories/files of obexd 0.38, which is a considerable step up from 0.21.

With 0.21, I was unable to send files back-and-forth to my WinMo phone.

But 0.38 works with Puppeee 4.31 and an HTC Touch Pro 2 phone, with a custom 6.53 ROM.

This is my first compilation and jemimah was the driving force--she helped me in every way and any success of this is hers.

I think the pet works, but it was my first, too. So less-intrepid users could just copy over the files to their appropriate directories.

I'm posting it in this thread since my working bluetooth uses the pets that jemimah supplies on page one.

Jake

[Whitesnow]

[CUT] You need to do something more like this: http://wiki.zenwalk.org/index.php?title ... th_headset

No asound* files on Puppy (but *state one in /etc), where to put headset instructions wrote on that site?

I'm on the latest Puppy with Twinkle as softphone and a Nokia HS-26W headset.

Please, help...