Bluetooth&&Bluez

[mehaj]

Hi,I'm trying to install bluez lib on my openbsd without success.
I get the following error

# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89..........................
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... yes
checking dynamic linker characteristics... openbsd4.9 ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for ppoll... no
checking for dlopen in -ldl... no
configure: error: dynamic linking loader is required

pleaase help

[jggimi]

There is a port of bluez-hcidump in the ports tree. You might start there, as $LDFLAGS are set in the Makefile. Look in sysutils/hcidump.

[mehaj]

Please it is normal that my bluetooth key(Broadcom BCM2045B2) is not reconized as bluetooth device by "OBSD 4.9"?
with 4.7 the same key was reconized without problem.

OpenBSD 4.9 (GENERIC) #671: Wed Mar  2 07:09:00 MST 2011
    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class) 500 MHz
cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX
real mem  = 536440832 (511MB)
avail mem = 517533696 (493MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 20/71/05, BIOS32 rev. 0 @ 0xfac40
pcibios0 at bios0: rev 2.0 @ 0xf0000/0x10000
pcibios0: pcibios_get_intr_routing - function not supported
pcibios0: PCI IRQ Routing information unavailable.
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc8000/0xa800
cpu0 at mainbus0: (uniprocessor)
amdmsr0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
io address conflict 0x6100/0x100
io address conflict 0x6200/0x200
pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x31
glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES
vr0 at pci0 dev 6 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11, address 00:00:24:c9:5a:d0
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034
vr1 at pci0 dev 7 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 5, address 00:00:24:c9:5a:d1
ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034
vr2 at pci0 dev 8 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 9, address 00:00:24:c9:5a:d2
ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034
vr3 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 12, address 00:00:24:c9:5a:d3
ukphy3 at vr3 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034
athn0 at pci0 dev 14 function 0 "Atheros AR9280" rev 0x01: irq 10
athn0: AR9280 rev 2 (2T2R), ROM rev 18, address 1c:bd:b9:da:16:2a
glxpcib0 at pci0 dev 20 function 0 "AMD CS5536 ISA" rev 0x03: rev 3, 32-bit 3579545Hz timer, watchdog, gpio
gpio0 at glxpcib0: 32 pins
pciide0 at pci0 dev 20 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 0 drive 1: <TRANSCEND>
wd0: 1-sector PIO, LBA, 1911MB, 3915072 sectors
wd0(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 2
pciide0: channel 1 ignored (disabled)
ohci0 at pci0 dev 21 function 0 "AMD CS5536 USB" rev 0x02: irq 15, version 1.0, legacy support
ehci0 at pci0 dev 21 function 1 "AMD CS5536 USB" rev 0x02: irq 15
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "AMD EHCI root hub" rev 2.00/1.00 addr 1
isa0 at glxpcib0
isadma0 at isa0
com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
com0: console
com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
nsclpcsio0 at isa0 port 0x2e/2: NSC PC87366 rev 10: GPIO VLM TMS
gpio1 at nsclpcsio0: 29 pins
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
usb1 at ohci0: USB revision 1.0
uhub1 at usb1 "AMD OHCI root hub" rev 1.00/1.00 addr 1
biomask e1c5 netmask ffe5 ttymask ffff
mtrr: K6-family MTRR support (2 registers)
uhub2 at uhub1 port 1 "Broadcom BCM2045B2" rev 2.00/1.00 addr 2
ugen0 at uhub2 port 1 "Broadcom Corp BCM2045A" rev 2.00/1.12 addr 3
uhidev0 at uhub2 port 2 configuration 1 interface 0 "Broadcom product 0x4502" rev 2.00/1.00 addr 4
uhidev0: iclass 3/1
ukbd0 at uhidev0: 8 modifier keys, 6 key codes
wskbd1 at ukbd0 mux 1
uhidev1 at uhub2 port 3 configuration 1 interface 0 "Broadcom product 0x4503" rev 2.00/1.00 addr 5
uhidev1: iclass 3/1
ums0 at uhidev1: 3 buttons
wsmouse0 at ums0 mux 0
vscsi0 at root
scsibus0 at vscsi0: 256 targets
softraid0 at root
root on wd0a swap on wd0b dump on wd0b

[mehaj]

yes i saw it but i'm interested by bluez for apply this code "http://search.cpan.org/~iguthrie/Net-Bluetooth-0.40/Bluetooth.pm"

[ocicat]

Originally Posted by mehaj

...i'm interested by bluez for apply this code...

BlueZ is Linux specific. To port this application to OpenBSD will potentially take significant time & understanding of OpenBSD's network stack (which is different than Linux). Because porting can be a very time-consuming activitiy, this site does not generally provide this level of support.

Recognize that both the libraries available on OpenBSD can be different than those available on Linux. OpenBSD's filesystem layout as described in hier(7) is also different. You should exhaustively check whether the existing applications already ported will take care of your needs before embarking on porting yourself.

[mehaj]

OK thank's i will try to work with bluez-hcidump
What about the other tread Bletooth&&BSD4.9

[jggimi]

1. I pointed you to sysutils/hcidump to suggest you look at the port framework, since it is a port of a bluez application. I do not know if the application itself would be of any value to you. As Ocicat eloquently stated, porting of Linux-specific applications requires knowledge of both Linux and OpenBSD software infrastructures. While looking the Makefile, I noticed the port does not have a $MAINTAINER, so questions about it (or other questions specific to bluez software porting efforts) are best taken to the ports@ mailing list.
2. I can't answer why your device now appears as a ugen(4) device rather than ubt(4) device without digging through driver source code, and related CVS logs, which I do not have the time to do today. And, even if I did have the time, I might not be able to find the change that affects your specific device.

[BSDfan666]

The bluetooth stack in OpenBSD currently lacks a maintainer, so it's suffering from some bit rot these days.. it's kind of broken, nobody cares enough about it to bring it back into shape.

The bluetooth host controllers are disabled in the kernel configuration, but still compiled in, for now you must enable them using UKC.

http://marc.info/?l=openbsd-cvs&m=129797369529495&w=2

[jggimi]

Thank you, BSDfan66. I don't use bluetooth with OpenBSD, so I've not paid any attention to applications, libraries, or associated kernel changes.

[BSDfan666]

Me neither, I don't own any bluetooth gear.. and quite frankly I don't see much need for support on OpenBSD, it's really not that more difficult to bring the USB data cable or use 802.11 wireless instead.

[Pjoter]

Originally Posted by BSDfan666

Me neither, I don't own any bluetooth gear.. and quite frankly I don't see much need for support on OpenBSD, it's really not that more difficult to bring the USB data cable or use 802.11 wireless instead.

Bluetooth is very common used nowdays. I don't get that approach...

[BSDfan666]

If it's important to you, then fix it.

[Pjoter]

Hello,

yes it is- I have bluetooth keyboard and mouse. And I won't fix it as I don't use OpenBSD

[BSDfan666]

Then it's not important to you, as you're using a different operating system.

[mehaj]

I've changed the kernel configuration and it works but how can i let the bluetooth device connected to openbsd identifiable by the others bluetooth devices " phone...."

[ocicat]

Originally Posted by mehaj

I've changed the kernel configuration and it works

You might help others by mentioning what you did to resolve your problem.

[mehaj]

Originally Posted by mehaj

how can i let the bluetooth device connected to openbsd identifiable by the others bluetooth devices " phone...."

oups all is in the help of btconfig.

btconfig ubt0 pscan

btconfig ubt0 iscan

thank you all for your help

[mehaj]

i've changed the configuration using UKC wich is invoked by the -c option when OpenBSD prompts for a kernel to boot:

>> OpenBSD/i386 BOOT 3.15
switching console to com0
>> OpenBSD/i386 BOOT 3.15
boot> -c
booting hd0a:/bsd: 8254588+1100008 [61+372432+358069]=0x99e4c8
entry point at 0x200120
[ using 730980 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.
Copyright (c) 1995-2011 OpenBSD. All rights reserved.  http://www.OpenBSD.org
OpenBSD 4.9 (GENERIC) #671: Wed Mar  2 07:09:00 MST 2011
deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class) 500 M	Hz
cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX
real mem  = 536440832 (511MB)
avail mem = 517533696 (493MB)
User Kernel Config
UKC> find ubt
423 ubt* at uhub*|uhub* disable port -1 configuration -1 interface -1 endor -1product -1 release -1 flags 0x0
UKC> enable ubt
423 ubt* enabled
UKC> find ubt
423 ubt* at uhub*|uhub* port -1 configuration -1 interface -1 vendor -1 product -1 release -1 flags 0x0
UKC> quit
.............................

[ocicat]

Your two threads on this subject have been merged into one. One is all that is necessary.