LinuxQuestions.org - Bluetooth Dongle Install

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Bluetooth Dongle Install (https://www.linuxquestions.org/questions/slackware-14/bluetooth-dongle-install-470870/)

blueAlien

08-04-2006 05:54 PM

Bluetooth Dongle Install

I just got a bluetooth capable phone, so I decided to purchase a usb bluetooth dongle so I could sync it with my laptop. I've done some research on getting it to work, but what I have found is vague and splotchy. I am very confused.

when it's plugged in /sbin/lsusb reports:

Code:

Bus 003 Device 001: ID 0000:0000

Bus 002 Device 001: ID 0000:0000

Bus 002 Device 002: ID 0a5c:4500 Broadcom Corp.

Bus 002 Device 003: ID 0a5c:2100 Broadcom Corp.

Bus 002 Device 004: ID 0a5c:4502 Broadcom Corp.

Bus 002 Device 005: ID 0a5c:4503 Broadcom Corp.

Bus 001 Device 001: ID 0000:0000

Also I read that I am supposed to have the /etc/rc.d/rc.bluetooth script, but it is not there.

Any help is appreciated.

drkstr

08-04-2006 06:52 PM

I wrote a howto for this:

http://www.linuxquestions.org/linux/...lackware_HOWTO

Let me know if you are still having trouble after this.

regards,
...drkstr

**edit**
although the guide on my half-ass web site is more up-to-date. http://www.drkstr.org

blueAlien

08-05-2006 10:35 AM

I got everything installed, and am at the "/etc/rc.d/rc.bluetooth start" step, but I get an error saying "no hid3hci in (/sbin:/bin:/usr/sbin:/usr/bin)".

I went back and looked in my compile dirs, and found that hid2hci never compiled, but I didn't get any errors when compiling. So, I tried to compile it, and got a bunch of errors about undefined references in 7 different usb functions.

At this point in time, I am stuck here.

drkstr

08-05-2006 11:24 AM

Quote:

I went back and looked in my compile dirs, and found that hid2hci never compiled, but I didn't get any errors when compiling. So, I tried to compile it, and got a bunch of errors about undefined references in 7 different usb functions.

What specifically did you try and compile, and how? What specific error did you get? I can't help you unless you provide more detailed information. Did you compile and install all the needed dependencies prior to compiling bluez-utils? Since you missed such a big step during the process, it makes me think you might have missed some of the needed steps before it. Try starting back from the beginning and follow each of the steps closely.

regards,
...drkstr

blueAlien

08-10-2006 07:27 PM

I got dbus to download and install just fine, but for some reason I could not download bluez over cvs, so I downloaded bluez-libs, bluez-utils from their site, and installed them seperately. I modified rc.bluetooth, and hcid.conf. I did not install any documentation though.

Now when I get to Part 2, Step 1 is where things get bumpy.
root@#/etc/rc.d/rc.bluetooth start

Code:

which: no hid2hci in (/sbin:/bin:/usr/sbin:/usr/bin)

Starting Bluetooth subsystem hcid sdpdCon't open HIDP control socket: No such file or directory

 hidd rfcom.

I looked in the same directory I ran the ./configure, make, and make install in,
(aka ./bluez-utils-3.2/) and went to the tools dir (./bluez-utils-3.2/tools/)

root@#ls

Code:

Makefile

    Makefile.am

    Makefile.in

    avctrl.8

    avctrl.c

    bccmd.8

    bccmd.c

    ciptool

    ciptool.1

    ciptool.c

    ciptool.o

    csr.c

    csr.h

    csr.o

    csr_3wire.c

    csr_bcsp.c

    csr_h4.c

    csr_hci.c

    csr_usb.c

    dfu.c

    dfu.h

    dfutool.1

    dfutool.c

    example.psr

    hciattach

    hciattach.8

    hciattach.c

    hciattach.o

    hciattach_st.c

    hciattach_st.o

    hciconfig

    hciconfig.8

    hciconfig.c

    hciconfig.o

    hcisecfilter

    hcisecfilter.c

    hcisecfilter.o

    hcitool

    hcitool.1

    hcitool.c

    hcitool.o

    hid2hci.8

    hid2hci.c

    l2ping

    l2ping.1

    l2ping.c

    l2ping.o

    listing

    ppporc

    ppporc.c

    ppporc.o

    sdptool

    sdptool.1

    sdptool.c

    sdptool.o

    ubcsp.c

    ubcsp.h

It looks like hid2hci did not compile, which explains why it is missing. So I try to compile it:

root@# gcc hid2hci.c

Code:

/tmp/ccyOZwHQ.o(.text+0xf): In function `switch_hidproxy':

: undefined reference to `usb_open'

/tmp/ccyOZwHQ.o(.text+0x48): In function `switch_hidproxy':

: undefined reference to `usb_control_msg'

/tmp/ccyOZwHQ.o(.text+0x84): In function `switch_hidproxy':

: undefined reference to `usb_close'

/tmp/ccyOZwHQ.o(.text+0x53d): In function `find_devices':

: undefined reference to `usb_find_buses'

/tmp/ccyOZwHQ.o(.text+0x542): In function `find_devices':

: undefined reference to `usb_find_devices'

/tmp/ccyOZwHQ.o(.text+0x547): In function `find_devices':

: undefined reference to `usb_get_buses'

/tmp/ccyOZwHQ.o(.text+0x72a): In function `main':

 : undefined reference to `usb_init'

So this is where I am stuck.

drkstr

08-11-2006 02:18 AM

Quote:

I'm not sure what the latest version of bluez is out, but I was unable to get the latest version (at the time of writing the guide) working on my Slackware system. The cvs version had a required patch that was not in the release version yet. cvs checkout is working fine, I just tried it. What is the exact command you tried and the exact error messege you got?

Quote:

which: no hid2hci in (/sbin:/bin:/usr/sbin:/usr/bin)
Starting Bluetooth subsystem hcid sdpdCon't open HIDP control socket: No such file or directory
hidd rfcom.

What are the contents of your bluez build directory? Did everything get installed to /usr/sbin like it should have?

Code:

drkstr@dsk:$ whereis hid2hci

hid2hci: /usr/sbin/hid2hci /usr/man/man8/hid2hci.8 /usr/share/man/man8/hid2hci.8

Quote:

It looks like hid2hci did not compile, which explains why it is missing. So I try to compile it:

root@# gcc hid2hci.c

This is not proper syntax. That's what make files are for. Shouldn't be necessary anyways. Did you --enable-all or if you don't want everything, make sure you--enable-hid2hci. I remember the compile options being a bit diffrent on the non cvs version though. You might want to ../configure --help to make sure.

Let me know if you are still stuck.

regards,
...drkstr

blueAlien

08-14-2006 03:05 AM

Ok, so I scraped the compiling from source, and found a website that had dbus, bluez-libs, and bluez-utils already in a slack package. Those installed with no problem using pkgtool, and this is what I get now.

/etc/rc.d/rc.bluetooth start

Code:

Starting Bluetooth subsystem: hcid sdpdCan't open HIDP control socket: No such file or directory

 hidd hid2hci rfcomm.

Also, after I installed the above packages I ran
/etc/rc.d/rc.messagebus start

Code:

Starting message bus: /usr/bin/dbus-daemon --system

This is where I am now. BTW, Thanks for all the help so far.

drkstr

08-14-2006 03:36 AM

hmmm, not really sure. I always prefer to build my own packages if they don't come default with Slackware. This gives you more control over what goes into your system and you never know what what dependencies the builder already has.

You might want to check out the start up script and search for the error message your getting. Hopefully it will indicate which file it can't find and you can go from there.

Maybe someone that had this same problem will be able to help you, but if you can get some more info, I would be happy to give it a try as well.

regards,
...drkstr

blueAlien

08-14-2006 06:13 AM

Ok, so I've narrowed it down to "/usr/bin/hidd --server || true"
which gives me:

Code:

Can't open HIDP control socket: No such file or directory

The same exact output from when I ran /etc/rc.d/rc.bluetooth.

drkstr

08-14-2006 08:20 AM

What kernel version are you running? Do you have a 2.6 kernel with hidp support compiled in? If it is modular, is the module loaded? 'lsmod' to see a list of modules, 'modprobe hidb' to load it (assuming it's enabled as a module).

This is my Kernel config for 2.6.16.5:

Code:

Networking-->

  Bluetooth subsystem support --->

    <M>  L2CAP protocol support

    < >  SCO links support 

    <M>  RFCOMM protocol support

    [ * ]    RFCOMM TTY support                                                                                

    < >  BNEP protocol support                                                                                                                                                                                                                                        

    <M>  HIDP protocol support                                                                                

    Bluetooth device drivers  --->  

      <M> HCI USB driver                                                                                        

      [ ]  SCO (voice) support                                                                                  

      < > HCI UART driver                                                                                        

      < > HCI BCM203x USB driver                                                                                

      < > HCI BPA10x USB driver                                                                                  

      < > HCI BlueFRITZ! USB driver                                                                              

      < > HCI VHCI (Virtual HCI device) driver

Hope this helps. Let me know if you're still having problems.

regards,
...drkstr

blueAlien

08-17-2006 03:37 AM

I am currently using the 2.4.31 kernel. I have tried upgrading my kernel to 2.6 before, but I always seem to do something wrong, so I always revert back to 2.4.31. I tried again to go to 2.6, but again something is messed up. I am currently researching what went wrong, and if I can't fix it, then I will post here to with error mesages.

Thanks for all the help so far!

drkstr

08-17-2006 08:59 AM

Quote:

I am currently using the 2.4.31 kernel.

Yup, that is most likley the problem. Let me know how it turns out. Feel free to ask if you still can't get 2.6 up and running.

regards,
...drkstr

blueAlien

08-17-2006 07:29 PM

I only found one readable site out of all the google searching, and wouldn't you know it's a linuxquestions.org thread:

http://www.linuxquestions.org/questi...hreadid=387349

From what I gather, this all has to do with the hd controller in my laptop, which is sata (even though my laptop has an ide hard drive). So, I am going to try the few things that I understood from that thread, and see if they work. Will report back later on progress.

btw, the error message I get is:

Code:

VFS: Cannot open root device "805" or unknown-block(8,5)

Please append a correct "root="boot option

Kernel panic: VFS: Unable to mount root fs on unknown-block(8,5)

drkstr

08-17-2006 11:30 PM

hehe, I thought that might be the problem, but I didn't want to make random guesses before you posted the error.

Try doing a 'make distclean' from within the kernel source before you do you configure/compile. I was unable to tweak the default Slackware kernel back to workable. This is probably my own fault, but I tried many times and failed with the default Slackware 2.6 config. Got it working perfect the first try when I started clean (IE: 'make distclean').

I agree, it's not very easy to find a solution on this. You would think it would appear more often since I got the same result on *every* computer I've tried it on. (sounds like you might have too)

regards,
...drkstr

blueAlien

08-20-2006 08:51 PM

I tried make distclean, and I am still having the same problem, with the same error message. Although, I forgot to make a backup of my old kernel, so now I have two copies of a non-functioning kernel (IE .old).

Maybe I am not doing something right. I am going to try a fresh install on another computer and see if I get the same results when changing the kernel on it.

drkstr

08-20-2006 10:26 PM

Maybe this will help you if your not allready aware of it.

The error message you getting is the result of not hard coding support for your root partition (as apposed to being modular)

regards,
...drkstr

**edit**
typo

blueAlien

08-20-2006 11:45 PM

I understand what you are saying about hard coded vs modular (ie Y, M, N). What I don't get is what I am supposed to hard code.

Here are some snippets from my .config

Code:

# SCSI low-level drivers

#

# CONFIG_BLK_DEV_3W_XXXX_RAID is not set

# CONFIG_SCSI_7000FASST is not set

# CONFIG_SCSI_ACARD is not set

# CONFIG_SCSI_AHA152X is not set

# CONFIG_SCSI_AHA1542 is not set

# CONFIG_SCSI_AACRAID is not set

# CONFIG_SCSI_AIC7XXX is not set

# CONFIG_SCSI_AIC7XXX_OLD is not set

# CONFIG_SCSI_AIC79XX is not set

# CONFIG_SCSI_ADVANSYS is not set

# CONFIG_SCSI_IN2000 is not set

# CONFIG_SCSI_MEGARAID is not set

CONFIG_SCSI_SATA=y



...



#

# File systems

#

CONFIG_EXT2_FS=y

# CONFIG_EXT2_FS_XATTR is not set

CONFIG_EXT3_FS=y

# CONFIG_EXT3_FS_XATTR is not set

CONFIG_JBD=y

# CONFIG_JBD_DEBUG is not set

CONFIG_REISERFS_FS=y

# CONFIG_REISERFS_CHECK is not set

# CONFIG_REISERFS_PROC_INFO is not set

# CONFIG_JFS_FS is not set

# CONFIG_XFS_FS is not set

# CONFIG_MINIX_FS is not set

# CONFIG_ROMFS_FS is not set

# CONFIG_QUOTA is not set

# CONFIG_AUTOFS_FS is not set

CONFIG_AUTOFS4_FS=y

and here is my fstab

Code:

/dev/sda4        swap            swap        defaults        0  0

/dev/sda5        /                ext3        defaults        1  1

/dev/sda1        /boot            ext3        defaults        1  1

/dev/sda2        /home            reiserfs    defaults        1  0

/dev/cdrom      /mnt/cdrom      auto        users,ro        0  0

/dev/fd0        /mnt/floppy      auto        noauto,owner    0  0

/dev/sdb1        /mnt/usb1        auto        users            0  0

/dev/sdc1        /mnt/usb2        auto        users            0  0

devpts          /dev/pts        devpts      gid=5,mode=620  0  0

proc            /proc            proc        defaults        0  0

and lilo.conf

Code:

# Linux bootable partition config begins

image = /boot/vmlinuz

  root = /dev/sda5

  label = Slackware-2.6.0

  read-only # Non-UMSDOS filesystems should be mounted read-only for checking

# Linux bootable partition config ends

# Old bootable image config begins

image = /boot/vmlinuz.old

  root = /dev/sda5

  label = Slackware-old

  read-only

# Old bootable image config ends

Is there something I am missing?

drkstr

08-22-2006 08:59 AM

I think you might need to turn on a few options in
Device Drivers-->SCSI Device Support-->SCSI Low Level Drivers

Try to find the options specific to your hardware, but if you're not sure, post your hardware specs. The kernel config to my generic Live CD kernel looks like this:

Code:

#

# SCSI low-level drivers

#

CONFIG_ISCSI_TCP=m

CONFIG_BLK_DEV_3W_XXXX_RAID=y

CONFIG_SCSI_3W_9XXX=y

CONFIG_SCSI_7000FASST=y

CONFIG_SCSI_ACARD=y

CONFIG_SCSI_AHA152X=y

CONFIG_SCSI_AHA1542=y

CONFIG_SCSI_AACRAID=y

CONFIG_SCSI_AIC7XXX=y

CONFIG_AIC7XXX_CMDS_PER_DEVICE=4

CONFIG_AIC7XXX_RESET_DELAY_MS=15000

# CONFIG_AIC7XXX_DEBUG_ENABLE is not set

CONFIG_AIC7XXX_DEBUG_MASK=0

# CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set

CONFIG_SCSI_AIC7XXX_OLD=m

CONFIG_SCSI_AIC79XX=y

CONFIG_AIC79XX_CMDS_PER_DEVICE=4

CONFIG_AIC79XX_RESET_DELAY_MS=15000

# CONFIG_AIC79XX_ENABLE_RD_STRM is not set

# CONFIG_AIC79XX_DEBUG_ENABLE is not set

CONFIG_AIC79XX_DEBUG_MASK=0

# CONFIG_AIC79XX_REG_PRETTY_PRINT is not set

CONFIG_SCSI_DPT_I2O=y

CONFIG_SCSI_IN2000=y

CONFIG_MEGARAID_NEWGEN=y

CONFIG_MEGARAID_MM=y

CONFIG_MEGARAID_MAILBOX=y

CONFIG_MEGARAID_LEGACY=y

CONFIG_MEGARAID_SAS=y

CONFIG_SCSI_SATA=y

CONFIG_SCSI_SATA_AHCI=y

CONFIG_SCSI_SATA_SVW=y

CONFIG_SCSI_ATA_PIIX=y

CONFIG_SCSI_SATA_MV=y

CONFIG_SCSI_SATA_NV=y

CONFIG_SCSI_PDC_ADMA=y

CONFIG_SCSI_SATA_QSTOR=y

CONFIG_SCSI_SATA_PROMISE=y

CONFIG_SCSI_SATA_SX4=y

CONFIG_SCSI_SATA_SIL=y

CONFIG_SCSI_SATA_SIL24=y

CONFIG_SCSI_SATA_SIS=y

CONFIG_SCSI_SATA_ULI=y

CONFIG_SCSI_SATA_VIA=y

CONFIG_SCSI_SATA_VITESSE=y

CONFIG_SCSI_SATA_INTEL_COMBINED=y

CONFIG_SCSI_BUSLOGIC=y

# CONFIG_SCSI_OMIT_FLASHPOINT is not set

CONFIG_SCSI_DMX3191D=y

CONFIG_SCSI_DTC3280=y

CONFIG_SCSI_EATA=y

# CONFIG_SCSI_EATA_TAGGED_QUEUE is not set

# CONFIG_SCSI_EATA_LINKED_COMMANDS is not set

CONFIG_SCSI_EATA_MAX_TAGS=16

CONFIG_SCSI_FUTURE_DOMAIN=y

CONFIG_SCSI_GDTH=y

CONFIG_SCSI_GENERIC_NCR5380=m

CONFIG_SCSI_GENERIC_NCR5380_MMIO=y

CONFIG_SCSI_GENERIC_NCR53C400=y

CONFIG_SCSI_IPS=y

CONFIG_SCSI_INITIO=y

CONFIG_SCSI_INIA100=y

CONFIG_SCSI_PPA=m

CONFIG_SCSI_IMM=m

# CONFIG_SCSI_IZIP_EPP16 is not set

# CONFIG_SCSI_IZIP_SLOW_CTR is not set

CONFIG_SCSI_NCR53C406A=m

CONFIG_SCSI_SYM53C8XX_2=y

CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=1

CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16

CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64

# CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set

CONFIG_SCSI_IPR=y

# CONFIG_SCSI_IPR_TRACE is not set

# CONFIG_SCSI_IPR_DUMP is not set

CONFIG_SCSI_PAS16=m

CONFIG_SCSI_PSI240I=y

CONFIG_SCSI_QLOGIC_FAS=y

CONFIG_SCSI_QLOGIC_FC=y

# CONFIG_SCSI_QLOGIC_FC_FIRMWARE is not set

CONFIG_SCSI_QLOGIC_1280=y

# CONFIG_SCSI_QLA_FC is not set

CONFIG_SCSI_LPFC=y

CONFIG_SCSI_SYM53C416=y

CONFIG_SCSI_DC395x=y

CONFIG_SCSI_DC390T=y

CONFIG_SCSI_T128=y

CONFIG_SCSI_U14_34F=m

# CONFIG_SCSI_U14_34F_TAGGED_QUEUE is not set

# CONFIG_SCSI_U14_34F_LINKED_COMMANDS is not set

CONFIG_SCSI_U14_34F_MAX_TAGS=8

CONFIG_SCSI_ULTRASTOR=m

CONFIG_SCSI_NSP32=y

CONFIG_SCSI_DEBUG=m

But this is for a generic kernel.

regards,
...drkstr

blueAlien

08-27-2006 05:08 PM

I took your advise and added every sata option I could. Low and behold it worked, so I am now running my new kernel with only a few small issues (such as sound and wireless). I ran the rc.bluetooth script and it executed without any errors. So now all I have to do is finished the tutorial by installing kdebluetooth, and figure out exactly which sata options I really need (not to mention fix my other problems).

Thanks for all your help with the bluetooth, and my first sucessfull kernel install.

Peace
blueAlien

drkstr

08-27-2006 09:19 PM

I'm glad you got it working!

Quote:

I am now running my new kernel with only a few small issues (such as sound and wireless).

For the 2.6 kernel to get along with Slackware, you need to uninstall the alsa-driver package, then enable sound support, alsa, and the driver for your card, all as modules. Then run 'alsaconf', 'alsamixer', 'alsactl store'.

Wireless depends on the hardware so you will have to do a bit of searching. I have a Atheros wifi card so I had to go download the madwifi driver.

regards,
...drkstr

All times are GMT -5. The time now is 11:29 PM.