[Bluez-devel] Problems when inserting snd_bt

All of lore.kernel.org
 help / color / mirror / Atom feed

* [Bluez-devel] Problems when inserting snd_bt_sco module in the kernel
@ 2006-01-21 19:12 Dani Camps
  2006-01-21 21:13 ` Brad Midgley
  0 siblings, 1 reply; 3+ messages in thread
From: Dani Camps @ 2006-01-21 19:12 UTC (permalink / raw)
  To: BlueZ Devel

[-- Attachment #1: Type: text/plain, Size: 4871 bytes --]

  Hi all, 
   
   I have a Fedora Core 3 box with kernel  2.6.12-1.1372. I have a Logitech bluetooth headset and for my Linux box  a USB dongle with a bluetooth chipset from Broadcom Corp.
   
   The  bluetooth dongle is working fine and I can see my Logitech headset with  hcitool scan. I have compiled the btsco driver in order to use the  headset, but the problem comes when I try to insert the snd_bt_sco in  the kernel, by doing:
   -----------------------------------------------------------------------------------------------------------------
   #modprobe snd_bt_sco
 FATAL:  Error inserting snd_bt_sco  (/lib/modules/2.6.12-1.1372_FC3/extra/snd-bt-sco.ko): Unknown symbol in  module, or unknown parameter (see dmesg)
   -----------------------------------------------------------------------------------------------------------------
   This is the output from dmesg:
     -----------------------------------------------------------------------------------------------------------------
   snd_bt_sco: disagrees about version of symbol snd_pcm_new
   snd_bt_sco: Unknown symbol snd_pcm_new
   snd_bt_sco: disagrees about version of symbol snd_pcm_lib_ioctl
   snd_bt_sco: Unknown symbol snd_pcm_lib_ioctl
   snd_bt_sco: disagrees about version of symbol snd_hwdep_new
   snd_bt_sco: Unknown symbol snd_hwdep_new
   snd_bt_sco: disagrees about version of symbol snd_pcm_set_ops
   snd_bt_sco: Unknown symbol snd_pcm_set_ops
   snd_bt_sco: disagrees about version of symbol snd_pcm_period_elapsed
   snd_bt_sco: Unknown symbol snd_pcm_period_elapsed
   snd_bt_sco: disagrees about version of symbol snd_pcm_new
   snd_bt_sco: Unknown symbol snd_pcm_new
   snd_bt_sco: disagrees about version of symbol snd_pcm_lib_ioctl
   snd_bt_sco: Unknown symbol snd_pcm_lib_ioctl
   snd_bt_sco: disagrees about version of symbol snd_hwdep_new
   snd_bt_sco: Un   known   symbol snd_hwdep_new
   snd_bt_sco: disagrees about version of symbol snd_pcm_set_ops
   snd_bt_sco: Unknown symbol snd_pcm_set_ops
   snd_bt_sco: disagrees about version of symbol snd_pcm_period_elapsed
   snd_bt_sco: Unknown symbol snd_pcm_period_elapsed
   -----------------------------------------------------------------------------------------------------------------
   More output information that can be useful:
   -----------------------------------------------------------------------------------------------------------------
   #hciconfig -a
   hci0:   Type: USB
           BD Address: 00:80:5A:40:9E:72 ACL MTU: 377:10  SCO MTU: 16:0
           UP RUNNING PSCAN ISCAN
           RX bytes:1114 acl:6 sco:0 events:48 errors:0
           TX bytes:485 acl:6 sco:0 commands:23 errors:0
             Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
           Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
           Link policy: RSWITCH HOLD SNIFF PARK
           Link mode: SLAVE ACCEPT
           Name: 'dani-laptop-0'
           Class: 0x000000
           Service Classes: Unspecified
           Device Class: Miscellaneous,
           HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x309
           Manufacturer: Broadcom Corporation (15)
   -------------------------------------------------------------------------------------------------------------
   #hciconfig hci0 revision
   hci0:        Type: USB
           BD Address: 00:80:5A:40:9E:72 ACL MTU: 377:10  SCO MTU: 16:0
           Firmware 0.3.009
   -------------------------------------------------------------------------------------------------------------
   #hcitool info 00:0D:44:0C:11:4A (headset's address)
   Requesting information ...
           BD Address:  00:0D:44:0C:11:4A
           Device Name: Logitech HS01-V16
           LMP Version: 1.2 (0x2) LMP Subversion: 0x611
           Manufacturer: Cambridge Silicon Radio (10)
           Features: 0xfc 0xfe 0x0f 0x00 0x08 0x08 0x00 0x00
                   <encryption> <slot offset> <timing accuracy> <  ;role switch>
                   <hold mode> <sniff mode> <RSSI> <channel  quality> <SCO link>
                   <HV2 packets> <HV3 packets> <u-law log> <A-law  log> <CVSD>
                   <paging scheme> <power control> <transparent SCO>
                   <AFH cap. slave> <AFH cap. master>
   -------------------------------------------------------------------------------------------------------------------
   # btsco -v
   btsco v0.4c
   Error: control open (hw:2): No such file or directory
   Error: Can't find device. Bail
     ---------------------------------------------------------------------------------------------------------------------
   
   Any idea about what is wrong ? Maybe my USB dongle does not work with the btsco driver ?
   
   Thanks in advance
   
   Dani Camps
   
     


  

			
---------------------------------
Yahoo! Photos
 Got holiday prints? See all the ways to get quality prints in your hands ASAP.

[-- Attachment #2: Type: text/html, Size: 6647 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Bluez-devel] Problems when inserting snd_bt_sco module in the kernel
  2006-01-21 19:12 [Bluez-devel] Problems when inserting snd_bt_sco module in the kernel Dani Camps
@ 2006-01-21 21:13 ` Brad Midgley
  2006-01-22 12:25   ` Dani Camps
  0 siblings, 1 reply; 3+ messages in thread
From: Brad Midgley @ 2006-01-21 21:13 UTC (permalink / raw)
  To: bluez-devel

Dani

You need to build the snd_hwdep kernel module. iirc, it's something like:

make -C /usr/src/linux CONFIG_SND_HWDEP=m modules modules_install

you will also need to get a csr dongle unless you're helping with the
broadcom workaround.

brad

> I have a Fedora Core 3 box with kernel 2.6.12-1.1372. I have a Logitech
> bluetooth headset and for my Linux box a USB dongle with a bluetooth
> chipset from Broadcom Corp.
> 
> The bluetooth dongle is working fine and I can see my Logitech headset
> with hcitool scan. I have compiled the btsco driver in order to use the
> headset, but the problem comes when I try to insert the snd_bt_sco in
> the kernel, by doing:
> -----------------------------------------------------------------------------------------------------------------
> #modprobe snd_bt_sco
> FATAL: Error inserting snd_bt_sco
> (/lib/modules/2.6.12-1.1372_FC3/extra/snd-bt-sco.ko): Unknown symbol in
> module, or unknown parameter (see dmesg)
> -----------------------------------------------------------------------------------------------------------------
> This is the output from dmesg:
> -----------------------------------------------------------------------------------------------------------------
> snd_bt_sco: disagrees about version of symbol snd_pcm_new
> snd_bt_sco: Unknown symbol snd_pcm_new
> snd_bt_sco: disagrees about version of symbol snd_pcm_lib_ioctl
> snd_bt_sco: Unknown symbol snd_pcm_lib_ioctl
> snd_bt_sco: disagrees about version of symbol snd_hwdep_new
> snd_bt_sco: Unknown symbol snd_hwdep_new
> snd_bt_sco: disagrees about version of symbol snd_pcm_set_ops
> snd_bt_sco: Unknown symbol snd_pcm_set_ops
> snd_bt_sco: disagrees about version of symbol snd_pcm_period_elapsed
> snd_bt_sco: Unknown symbol snd_pcm_period_elapsed
> snd_bt_sco: disagrees about version of symbol snd_pcm_new
> snd_bt_sco: Unknown symbol snd_pcm_new
> snd_bt_sco: disagrees about version of symbol snd_pcm_lib_ioctl
> snd_bt_sco: Unknown symbol snd_pcm_lib_ioctl
> snd_bt_sco: disagrees about version of symbol snd_hwdep_new
> snd_bt_sco: Un known symbol snd_hwdep_new
> snd_bt_sco: disagrees about version of symbol snd_pcm_set_ops
> snd_bt_sco: Unknown symbol snd_pcm_set_ops
> snd_bt_sco: disagrees about version of symbol snd_pcm_period_elapsed
> snd_bt_sco: Unknown symbol snd_pcm_period_elapsed
> -----------------------------------------------------------------------------------------------------------------
> More output information that can be useful:
> -----------------------------------------------------------------------------------------------------------------
> #hciconfig -a
> hci0:   Type: USB
>         BD Address: 00:80:5A:40:9E:72 ACL MTU: 377:10  SCO MTU: 16:0
>         UP RUNNING PSCAN ISCAN
>         RX bytes:1114 acl:6 sco:0 events:48 errors:0
>         TX bytes:485 acl:6 sco:0 commands:23 errors:0
>         Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>         Link policy: RSWITCH HOLD SNIFF PARK
>         Link mode: SLAVE ACCEPT
>         Name: 'dani-laptop-0'
>         Class: 0x000000
>         Service Classes: Unspecified
>         Device Class: Miscellaneous,
>         HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x309
>         Manufacturer: Broadcom Corporation (15)
> -------------------------------------------------------------------------------------------------------------
> #hciconfig hci0 revision
> hci0:    Type: USB
>         BD Address: 00:80:5A:40:9E:72 ACL MTU: 377:10  SCO MTU: 16:0
>         Firmware 0.3.009
> -------------------------------------------------------------------------------------------------------------
> #hcitool info 00:0D:44:0C:11:4A (headset's address)
> Requesting information ...
>         BD Address:  00:0D:44:0C:11:4A
>         Device Name: Logitech HS01-V16
>         LMP Version: 1.2 (0x2) LMP Subversion: 0x611
>         Manufacturer: Cambridge Silicon Radio (10)
>         Features: 0xfc 0xfe 0x0f 0x00 0x08 0x08 0x00 0x00
>                 <encryption> <slot offset> <timing accuracy> < ;role switch>
>                 <hold mode> <sniff mode> <RSSI> <channel quality> <SCO link>
>                 <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD>
>                 <paging scheme> <power control> <transparent SCO>
>                 <AFH cap. slave> <AFH cap. master>
> -------------------------------------------------------------------------------------------------------------------
> # btsco -v
> btsco v0.4c
> Error: control open (hw:2): No such file or directory
> Error: Can't find device. Bail
> ---------------------------------------------------------------------------------------------------------------------
> 
> Any idea about what is wrong ? Maybe my USB dongle does not work with
> the btsco driver ?
> 
> Thanks in advance
> 
> Dani Camps
> 
> 
> ------------------------------------------------------------------------
> Yahoo! Photos
> Got holiday prints? See all the ways
> <http://us.rd.yahoo.com/mail_us/taglines/holidayprints/*http://pa.yahoo.com/*http://us.rd.yahoo.com/mail_us/taglines/photos/evt=38089/*http://pg.photos.yahoo.com/ph//print_splash>
> to get quality prints in your hands ASAP.



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [Bluez-devel] Problems when inserting snd_bt_sco module in the kernel
  2006-01-21 21:13 ` Brad Midgley
@ 2006-01-22 12:25   ` Dani Camps
  0 siblings, 0 replies; 3+ messages in thread
From: Dani Camps @ 2006-01-22 12:25 UTC (permalink / raw)
  To: bluez-devel

[-- Attachment #1: Type: text/plain, Size: 4223 bytes --]

 
Hi Brad, 
 
 Thanks for your quick reply.
 When I try to compile the snd_hwdep kernel module with:
 
---------------------------------------------------------------------------------------------------------------
 # make -C /usr/src/kernels/2.6.12-1.1372_FC3-i686/ CONFIG_SND_HWDEP=m 
modules modules_install
 
 make: Entering directory `/usr/src/kernels/2.6.12-1.1372_FC3-i686'
   CHK     include/linux/version.h
   CHK     include/asm-i386/asm_offsets.h
 make[1]: *** There is no rule to build the object `init/main.o', 
needed for `init/built-in.o'.  Stop.
 make: *** [init] Error 2
 make: Leaving directory `/usr/src/kernels/2.6.12-1.1372_FC3-i686'
 
 
---------------------------------------------------------------------------------------------------------------
 As you can see I get that error when trying to build snd_hwdep.
 Even though, I can insert snd_hwdep in the kernel by doing:
 #modprobe snd_hwdep
 
 After doing this, and having the Bluetooth dongle plugged in and the 
bluetooth service started, this is my output of lsmod:
 
---------------------------------------------------------------------------------------------------------------
 #lsmod
 Module                  Size  Used by
 snd_hwdep               9376  0
 rfcomm                 41565  0
 l2cap                  29509  5 rfcomm
 hci_usb                18121  2
 bluetooth              55237  7 rfcomm,l2cap,hci_usb
 i915                   18753  1
 drm                    68949  2 i915
 parport_pc             28293  1
 lp                     12873  0
 parport                40073  2 parport_pc,lp
 autofs4                28229  0
 wlan_wep                5504  1
 tun                    11329  0
 sunrpc                164229  1
 pcmcia                 28897  2
 microcode               7009  0
 nls_utf8                2113  1
 ntfs                  177808  1
 dm_mod                 57333  0
 video                  15685  0
 button                  6609  0
 battery                 9285  0
 ac                      4805  0
 md5                     4033  1
 ipv6                  262977  8
 ohci1394               39945  0
 ieee1394              303545  1 ohci1394
 yenta_socket           21449  2
 rsrc_nonstatic         12737  1 yenta_socket
 pcmcia_core            50013  3 pcmcia,yenta_socket,rsrc_nonstatic
 uhci_hcd               35025  0
 ehci_hcd               40013  0
 i2c_i801                8653  0
 i2c_core               21313  1 i2c_i801
 snd_intel8x0m          19780  5
 snd_intel8x0           34752  2
 snd_ac97_codec         78332  2 snd_intel8x0m,snd_intel8x0
 snd_pcm_oss            51360  0
 snd_mixer_oss          18432  3 snd_pcm_oss
 snd_pcm                99080  6 
snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_oss
 snd_timer              33412  1 snd_pcm
 snd                    58884  16 
snd_hwdep,snd_intel8x0m,snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
 soundcore              10785  3 snd
 snd_page_alloc         10244  3 snd_intel8x0m,snd_intel8x0,snd_pcm
 8139too                29505  0
 mii                     5569  1 8139too
 ath_pci                58788  0
 ath_rate_onoe           7816  1 ath_pci
 wlan                  108508  4 wlan_wep,ath_pci,ath_rate_onoe
 ath_hal               147536  2 ath_pci
 joydev                  9345  0
 ext3                  130633  1
 jbd                    83161  1 ext3
 
---------------------------------------------------------------------------------------------------------------
 
 Here is when I try to insert the snd_bt_sco, but it crashes like I 
decribed in my previous email.
 
 The enviroment where I am trying to insert snd_bt_sco is correct or do 
I need some extra other module, or snd_hwdep must be rebuilt and 
inserted again ? In that case any idea about the error that I get when trying 
to build snd_hwdep ?
 
 Regarding my bluetooth dongle, I am not trying to workaround any 
Broadcom problem, I just want to use my headset :), is then absolutely 
necessary that I get a USB dongle with a CSR bluetooth chipset? Which brands 
are shipping USB dongles with CSR bluetooth chipsets ?
 
 Thanks a lot
 
 Dani
 

		
---------------------------------
 
 What are the most popular cars?  Find out at Yahoo! Autos

[-- Attachment #2: Type: text/html, Size: 4740 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2006-01-22 12:25 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-01-21 19:12 [Bluez-devel] Problems when inserting snd_bt_sco module in the kernel Dani Camps
2006-01-21 21:13 ` Brad Midgley
2006-01-22 12:25   ` Dani Camps

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.