2.12 beta Bluetooth kernel modules

[the_spudster]

Just wondering if someone can help.
I have been testing the 2.12 beta with so far a great deal of success on two old thinkpads (A21m, A21e),

I have also been using it in conjunction with some kde apps (mostly for Amarok) and also because my daughter likes the kde desktop. Incidently I have not come across anything that can run kde as fast as puppy and always come back to it (got a huge pile of redundant disks!.......must buy some rewritables!)

One thing she requested was bluetooth so i included the bluez libs and utils plus dbus kdebluetooth and kmobiletools into Marks mkkde program....made the squash file and voila we are ready to rock and roll.................not.

The problem seems to lie with the omission of some parts of the kernel within the lib/modules/2.6.18.1/kernel/net/bluetooth folder
i.e: l2cap.ko, sco.ko, rfcomm.kp, cmtp.ko and bnep.ko

Please excuse my ignorance (I am still abit of a noob!) but I am wondering how I can add these extra modules (are they tucked away somewhere in the zdrv_212.sfs), or do I have to compile another kernel? if so how? or is there an easier way. i.e use a different puppy version. (need to use v2.** to run Kde (looked at the 'all modules for 202' and they are not included in there))

On a plus point Puppy 2.12 has the drivers for the Usb dongle I am using, and
works like dream, so I am sure I am close.

Thanks in advance to anyone who can help

Regards
Simon

Sorry for the essay but sometimes I cant help it! (O'level English and all!)

[the_spudster]

Just a quick update on the bluetooth modules.

It would seem that you can build part of the bluetooth kernel module by executing

[BarryK]

[quote]It would seem that you can build part of the bluetooth kernel module by executing

[Lobster]

I plugged in my USB Bluetooth dongle and ran the USB viewer in 2.12 Beta 2
This is what I got (it said unknown device and gave this info)
Hope it is helpful

Code: Select all

Unknown Device
Speed: 12Mb/s (full)
USB Version:  1.10
Device Class: e0(unk. )
Device Subclass: 01
Device Protocol: 01
Maximum Default Endpoint Size: 64
Number of Configurations: 1
Vendor Id: 0a12
Product Id: 0001
Revision Number:  5.25

Config Number: 1
	Number of Interfaces: 3
	Attributes: 80
	MaxPower Needed: 200mA

	Interface Number: 0
		Name: (none)
		Alternate Number: 0
		Class: e0(unk. ) 
		Sub Class: 1
		Protocol: 1
		Number of Endpoints: 3

			Endpoint Address: 81
			Direction: in
			Attribute: 3
			Type: Int.
			Max Packet Size: 16
			Interval: 1ms

			Endpoint Address: 02
			Direction: out
			Attribute: 2
			Type: Bulk
			Max Packet Size: 64
			Interval: 0ms

			Endpoint Address: 82
			Direction: in
			Attribute: 2
			Type: Bulk
			Max Packet Size: 64
			Interval: 0ms

	Interface Number: 1
		Name: (none)
		Alternate Number: 0
		Class: e0(unk. ) 
		Sub Class: 1
		Protocol: 1
		Number of Endpoints: 2

			Endpoint Address: 03
			Direction: out
			Attribute: 1
			Type: Isoc
			Max Packet Size: 0
			Interval: 1ms

			Endpoint Address: 83
			Direction: in
			Attribute: 1
			Type: Isoc
			Max Packet Size: 0
			Interval: 1ms

	Interface Number: 1
		Name: (none)
		Alternate Number: 1
		Class: e0(unk. ) 
		Sub Class: 1
		Protocol: 1
		Number of Endpoints: 2

			Endpoint Address: 03
			Direction: out
			Attribute: 1
			Type: Isoc
			Max Packet Size: 9
			Interval: 1ms

			Endpoint Address: 83
			Direction: in
			Attribute: 1
			Type: Isoc
			Max Packet Size: 9
			Interval: 1ms

	Interface Number: 1
		Name: (none)
		Alternate Number: 2
		Class: e0(unk. ) 
		Sub Class: 1
		Protocol: 1
		Number of Endpoints: 2

			Endpoint Address: 03
			Direction: out
			Attribute: 1
			Type: Isoc
			Max Packet Size: 17
			Interval: 1ms

			Endpoint Address: 83
			Direction: in
			Attribute: 1
			Type: Isoc
			Max Packet Size: 17
			Interval: 1ms

	Interface Number: 1
		Name: (none)
		Alternate Number: 3
		Class: e0(unk. ) 
		Sub Class: 1
		Protocol: 1
		Number of Endpoints: 2

			Endpoint Address: 03
			Direction: out
			Attribute: 1
			Type: Isoc
			Max Packet Size: 25
			Interval: 1ms

			Endpoint Address: 83
			Direction: in
			Attribute: 1
			Type: Isoc
			Max Packet Size: 25
			Interval: 1ms

	Interface Number: 1
		Name: (none)
		Alternate Number: 4
		Class: e0(unk. ) 
		Sub Class: 1
		Protocol: 1
		Number of Endpoints: 2

			Endpoint Address: 03
			Direction: out
			Attribute: 1
			Type: Isoc
			Max Packet Size: 33
			Interval: 1ms

			Endpoint Address: 83
			Direction: in
			Attribute: 1
			Type: Isoc
			Max Packet Size: 33
			Interval: 1ms

	Interface Number: 1
		Name: (none)
		Alternate Number: 5
		Class: e0(unk. ) 
		Sub Class: 1
		Protocol: 1
		Number of Endpoints: 2

			Endpoint Address: 03
			Direction: out
			Attribute: 1
			Type: Isoc
			Max Packet Size: 49
			Interval: 1ms

			Endpoint Address: 83
			Direction: in
			Attribute: 1
			Type: Isoc
			Max Packet Size: 49
			Interval: 1ms

	Interface Number: 2
		Name: (none)
		Alternate Number: 0
		Class: fe(app. ) 
		Sub Class: 1
		Protocol: 0
		Number of Endpoints: 0

[BarryK]

The problem seems to lie with the omission of some parts of the kernel within the lib/modules/2.6.18.1/kernel/net/bluetooth folder
i.e: l2cap.ko, sco.ko, rfcomm.kp, cmtp.ko and bnep.ko

The only thing in that folder is 'bluetooth.ko' module.

[the_spudster]

Hi Barry and Lobster.
Many thanks for your comments.

Please excuse my ignorance regarding terminology but I am kind of new to linux and still trying to learn! and as on one of the previous posts I am too 'blundering around!'

It seems that I might of jumped the gun in saying that rfcomm etc were located in the zdrv file. It does seem however that when you use the devx_212.sfs file, you can see the required files.

For Lobster, to load the drivers for his usb dongle you have to 'modprobe hci_usb' .
Then if you have bluez libs and bluez utils installed you should be able to run hciconfig' to show the dongle status.
If no mac address is shown type 'hciconfig hci0 up' to start the device then 'hciconfig' to show the status.

Run 'hcitool' for further interaction with your dongle.

My problem is when I try to run 'rc.bluetooth start' from the /etc/rc.d folder console tells me what is missing.

My summition is based on the fact that if I search on the slackware site for rfcomm, it tells me that it is within the kernel.
If I download the kernel and extract it it has the additional modules in the bluetooth folder.

As before any help is appreciated!

Best regards

Simon

Ps Still loving Puppy!

[Lobster]

can you upload / host the
bluez libs and bluez utils
you are using please

[BarryK]

Look in /lib/modules directory, you will find the kernel configuration file. search for "bluetooth" and you will see what it built-in, a module, or missing.
One thing I notice:
# CONFIG_BT_SCO is not set
so the "sco" module is not supported in this kernel.
(note: those letters "sco" make me cringe)

[the_spudster]

Made a little bit of progress last night by installing the bluez libs and utils and dbus directly into puppy, rather than installing in the mkkde kde_mini.sfs. The error message went away when I './rc.buetooth start' but there are other errors when I start the 'kbluetoothd' software. ( something about the file length being incorrect and suggests remaking the link.

I realise this sounds vague but I was doing this at about three in the morning with a cold and two small children also with colds, keeping me up all night, so the memory is a bit fuzzy!

Sorry for being a bit slow to get back, but I am at my parents at the moment until Friday using thier dial-up connection (forgotten how slowwwww it is!)

Will upload the files on Friday night, otherwise I think I found them at www.develia.org (not sure of the spelling...)

Oh and where do I upload files to?

Regards to all!
Simon

[the_spudster]

Hi all
These are the files that I have been using.
They are for slackware 11 files. So far I have found that they work better if you extract the files and copy them to the relevent directories rather than using the mkkde program (cant see the difference) but the 'rc.bluetooth start' command works without errors this way.
When you have done this you will have to change the rc.bluetooth.new file to rc.bluetooth and rc.messagebus.new to rc.messagebus (in etc/rc.d)

Lobster... It seems that I cannot upload .tgz files as an attatchment, but you can find the ones I have been using here:

http://www.develia.org/tarballs/network ... i686-1.tgz
http://www.develia.org/tarballs/network ... i686-1.tgz
http://www.develia.org/tarballs/network ... i686-1.tgz
http://www.develia.org/tarballs/librari ... i686-1.tgz

I guess that it is quite likely that I have not installed these .tgz's correctly, so please let me know the correct method, and also if you feel like, it tell me how stupid I am!

Barry.....I feel a little inadequate in your company! I just wish that I knew a bit more so to make a more healthy contribution!

Had a look at the kernel configuration file and found this:

CONFIG_BT=m
# CONFIG_BT_L2CAP is not set
# CONFIG_BT_SCO is not set

#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
# CONFIG_BT_HCIUSB_SCO is not set
CONFIG_BT_HCIUART=m
# CONFIG_BT_HCIUART_H4 is not set
# CONFIG_BT_HCIUART_BCSP is not set
CONFIG_BT_HCIBCM203X=m
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_BT_HCIVHCI=m

not sure what it means though.....

Did notice that there is a shortcut to 'build' in the 2.6.18.1 directory. in this there are some of the appropriate files in the include/net/bluetooth directory.

Hope this is of use

Regards
Simon

[IsleVegan]

i went through a great challenge a few months ago to get this working on ubuntu, but i'm not sure where to start on puppy.

[gop00]

Puppy 2.12 is missing some bluetooh kernel module. specifically rfcomm, bnep, cmtp, hidp and the files with the same name.ko files within, also the l2cap.ko and sco.ko files.

Please can anyone guide me where to ge this.

I've tried to add these modules from ubuntu (2.6.17.10), but no luck. When I try to load hidp.ko modules, "-1 Invalid module format" is returned.

Please help...SOS.

[tempestuous]

the_spudster and gop00 are right, Puppy has only SOME of the bluetooth modules.
I just enabled the extra modules in the kernel configuration, and compiled them.
I also compiled the latest BlueZ libs/utils/firmware. These should be better than those Slackware packages. If you have already installed the Slackware versions, start with a new pupfile, otherwise you might have some conflicting files.

Hope it all works. Please report your results. There have been a few other forum posts about unsuccessful attempts to get Bluetooth devices working.

EDIT March 2007: these bluetooth modules are now contained in Puppy as standard from version 2.14 onwards.
But the "BlueZ" bluetooth libraries, utilities (and sometimes firmware) still need to be added.

Forum member daemon reports that an older version of bluez-libs is necessary to get his gprs working.
He provided these libraries here -
http://www.murga-linux.com/puppy/viewto ... 6314#86314

And debernardis has set up a wiki page to explain setup, especially the all-important creation of the /dev/rfcomm0 device node.

UPDATE:
Now attached are openobex, obexftp, and obexfs, needed to transfer files via bluetooth.
These are older versions compatible with Puppy 2.x and debernardis' older bluetooth libraries.

[Browny]

I have tried with the above packages and installed the pup packages...i don't know how to proceed with this...

I have run the hciconfig through terminal but getting the output as

"Can't open HCI socket.: Address family not supported by protocol"

[debernardis]

Try http://puppylinux.org/wikka/ExperimentalBT/

[edoc]

And debernardis has set up a wiki page to explain setup, especially the all-important creation of the /dev/rfcomm0 device node.

I have all of these:

bluetooth-libs-utils-firmware.pup
bluetooth-modules-k2.6.18.1
bluez-libs-2.10.tar.gz
bluez-utils-2.10.tar.gz
bt2.sh.gz

I am not currently trying to connect a phone, I am trying to connect a
Bluetooth-USB dongle and then a Bluetooth GPS to that.

Can anyone recommend a specific Bluetooth-USB adapter & Bluetooth GPS
that is known to work with Puppy 2.14?