Hi,
I work with 2.6.10-1.766_FC3 kernel.
I rebuilt bluetooth.ko and hci_usb.ko using using
those makefile:
---------------------------------
#
# Makefile for bluetooth.ko
#
obj-m += bluetooth.o
bluetooth-objs := af_bluetooth.o hci_core.o hci_conn.o
hci_event.o hci_sock.o hci_sysfs.o lib.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
default:
$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
----------------------------------
#
# Makefile for the Linux Bluetooth HCI device drivers.
#
obj-m := hci_usb.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
default:
$(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
-------------------------------------
but with this I used bluetooth files of 2.6.8 kernel.
and before building modules I changed in
/lib/modules/2.6.10-1.766_FC3/build/include/net
the bluetooth directory by the 2.6.8 kernel one.
until know everyting is okay and is not blutooth
specific.
The copilation is okay, and I put my too modules in
the specific directories in
/lib/modules/2.6.10-1.766_FC3/kernel
Any bluez module at this time is loaded.
and when I run
#modprobe bluetooth.ko
i can see my module with lsmod.
but when I run
#modprobe hci_usb.ko
I had:
FATAL: Error inserting hci_usb
(/lib/modules/2.6.10-1.766_FC3/kernel/drivers/bluetooth/hci_usb.ko):
Unknown symbol in module, or unknown parameter (see
dmesg)
and I see with dmesg:
Bluetooth: Core ver 2.6
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager
initialized
Bluetooth: HCI socket layer initialized
hci_usb: disagrees about version of symbol
hci_free_dev
hci_usb: Unknown symbol hci_free_dev
hci_usb: disagrees about version of symbol
hci_alloc_dev
hci_usb: Unknown symbol hci_alloc_dev
hci_usb: disagrees about version of symbol
hci_unregister_dev
hci_usb: Unknown symbol hci_unregister_dev
hci_usb: disagrees about version of symbol
hci_register_dev
hci_usb: Unknown symbol hci_register_dev
hci_free_dev,...etc are defined in hci_core.h
bluetooth.ko use hci_core.c and hci_usb.c includes
hci_core.h
and If review what I deed I use thes same version of
Hci_core for my too modulues.
so I don't undersand why there is a misunderstanding
between the too modules?
regards
D?couvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails !
Cr?ez votre Yahoo! Mail sur http://fr.mail.yahoo.com/
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi!
> hci_usb: no version for "struct_module" found: kernel
> tainted.
> hci_usb: no version magic, tainting kernel.
Try google or some other great magic tool ;-)
Seems to me that the kernel image was not compiled from
exactly the same sources.
IMHO it's better to compile a complete new kernel and not
only some modules and try to load them into the
distribution kernel (this is just my guess about what might
be the problem so please complain if I'm wrong)
Best regards,
Sebastian
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi,
> when I tape
> #modprobe -f hci_usb
> it works, I can do an hciconfig hci0 up an using
> hcitool etc...
>
>
> dmesg tells:
> hci_usb: no version for "struct_module" found: kernel
> tainted.
> hci_usb: no version magic, tainting kernel.
> Bluetooth: HCI USB driver ver 2.7
> usbcore: registered new driver hci_usb
>
> I don't understand where is the matter. But is it
> possible that HCI USB driver is a ver 2.7 and the
> Bluetooth: Core ver 2.6 in the same kernel?
this is no problem. All modules have there own version number.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
when I tape
#modprobe -f hci_usb
it works, I can do an hciconfig hci0 up an using
hcitool etc...
dmesg tells:
hci_usb: no version for "struct_module" found: kernel
tainted.
hci_usb: no version magic, tainting kernel.
Bluetooth: HCI USB driver ver 2.7
usbcore: registered new driver hci_usb
I don't understand where is the matter. But is it
possible that HCI USB driver is a ver 2.7 and the
Bluetooth: Core ver 2.6 in the same kernel?
--- benbouzid imad <[email protected]> a ?crit :
> Hi,
>
> I work with 2.6.10-1.766_FC3 kernel.
> I rebuilt bluetooth.ko and hci_usb.ko using using
> those makefile:
> ---------------------------------
> #
> # Makefile for bluetooth.ko
> #
>
> obj-m += bluetooth.o
> bluetooth-objs := af_bluetooth.o hci_core.o
> hci_conn.o
> hci_event.o hci_sock.o hci_sysfs.o lib.o
>
> KDIR := /lib/modules/$(shell uname -r)/build
> PWD := $(shell pwd)
> default:
> $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
> ----------------------------------
> #
> # Makefile for the Linux Bluetooth HCI device
> drivers.
> #
>
> obj-m := hci_usb.o
>
> KDIR := /lib/modules/$(shell uname -r)/build
> PWD := $(shell pwd)
>
> default:
> $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
> -------------------------------------
>
>
> but with this I used bluetooth files of 2.6.8
> kernel.
> and before building modules I changed in
> /lib/modules/2.6.10-1.766_FC3/build/include/net
> the bluetooth directory by the 2.6.8 kernel one.
>
> until know everyting is okay and is not blutooth
> specific.
>
> The copilation is okay, and I put my too modules in
> the specific directories in
> /lib/modules/2.6.10-1.766_FC3/kernel
>
> Any bluez module at this time is loaded.
> and when I run
> #modprobe bluetooth.ko
> i can see my module with lsmod.
> but when I run
> #modprobe hci_usb.ko
> I had:
>
> FATAL: Error inserting hci_usb
>
(/lib/modules/2.6.10-1.766_FC3/kernel/drivers/bluetooth/hci_usb.ko):
> Unknown symbol in module, or unknown parameter (see
> dmesg)
>
> and I see with dmesg:
> Bluetooth: Core ver 2.6
> NET: Registered protocol family 31
> Bluetooth: HCI device and connection manager
> initialized
> Bluetooth: HCI socket layer initialized
> hci_usb: disagrees about version of symbol
> hci_free_dev
> hci_usb: Unknown symbol hci_free_dev
> hci_usb: disagrees about version of symbol
> hci_alloc_dev
> hci_usb: Unknown symbol hci_alloc_dev
> hci_usb: disagrees about version of symbol
> hci_unregister_dev
> hci_usb: Unknown symbol hci_unregister_dev
> hci_usb: disagrees about version of symbol
> hci_register_dev
> hci_usb: Unknown symbol hci_register_dev
>
> hci_free_dev,...etc are defined in hci_core.h
>
> bluetooth.ko use hci_core.c and hci_usb.c includes
> hci_core.h
> and If review what I deed I use thes same version of
> Hci_core for my too modulues.
> so I don't undersand why there is a misunderstanding
> between the too modules?
>
> regards
>
>
>
>
>
>
>
> D?couvrez le nouveau Yahoo! Mail : 250 Mo d'espace
> de stockage pour vos mails !
> Cr?ez votre Yahoo! Mail sur
> http://fr.mail.yahoo.com/
>
>
>
-------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT
> Products from real users.
> Discover which products truly live up to the hype.
> Start reading now.
>
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Bluez-users mailing list
> [email protected]
>
https://lists.sourceforge.net/lists/listinfo/bluez-users
>
D?couvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails !
Cr?ez votre Yahoo! Mail sur http://fr.mail.yahoo.com/
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi,
> I work with 2.6.10-1.766_FC3 kernel.
> I rebuilt bluetooth.ko and hci_usb.ko using using
> those makefile:
> ---------------------------------
> #
> # Makefile for bluetooth.ko
> #
>
> obj-m += bluetooth.o
> bluetooth-objs := af_bluetooth.o hci_core.o hci_conn.o
> hci_event.o hci_sock.o hci_sysfs.o lib.o
>
> KDIR := /lib/modules/$(shell uname -r)/build
> PWD := $(shell pwd)
> default:
> $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
> ----------------------------------
> #
> # Makefile for the Linux Bluetooth HCI device drivers.
> #
>
> obj-m := hci_usb.o
>
> KDIR := /lib/modules/$(shell uname -r)/build
> PWD := $(shell pwd)
>
> default:
> $(MAKE) -C $(KDIR) SUBDIRS=$(PWD) modules
> -------------------------------------
>
>
> but with this I used bluetooth files of 2.6.8 kernel.
> and before building modules I changed in
> /lib/modules/2.6.10-1.766_FC3/build/include/net
> the bluetooth directory by the 2.6.8 kernel one.
>
> until know everyting is okay and is not blutooth
> specific.
>
> The copilation is okay, and I put my too modules in
> the specific directories in
> /lib/modules/2.6.10-1.766_FC3/kernel
>
> Any bluez module at this time is loaded.
> and when I run
> #modprobe bluetooth.ko
> i can see my module with lsmod.
> but when I run
> #modprobe hci_usb.ko
> I had:
>
> FATAL: Error inserting hci_usb
> (/lib/modules/2.6.10-1.766_FC3/kernel/drivers/bluetooth/hci_usb.ko):
> Unknown symbol in module, or unknown parameter (see
> dmesg)
>
> and I see with dmesg:
> Bluetooth: Core ver 2.6
> NET: Registered protocol family 31
> Bluetooth: HCI device and connection manager
> initialized
> Bluetooth: HCI socket layer initialized
> hci_usb: disagrees about version of symbol
> hci_free_dev
> hci_usb: Unknown symbol hci_free_dev
> hci_usb: disagrees about version of symbol
> hci_alloc_dev
> hci_usb: Unknown symbol hci_alloc_dev
> hci_usb: disagrees about version of symbol
> hci_unregister_dev
> hci_usb: Unknown symbol hci_unregister_dev
> hci_usb: disagrees about version of symbol
> hci_register_dev
> hci_usb: Unknown symbol hci_register_dev
>
> hci_free_dev,...etc are defined in hci_core.h
>
> bluetooth.ko use hci_core.c and hci_usb.c includes
> hci_core.h
> and If review what I deed I use thes same version of
> Hci_core for my too modulues.
> so I don't undersand why there is a misunderstanding
> between the too modules?
use either the Fedora Core kernel or the vanilla one. Don't try to play
tricks and then complain that it does not work.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users