Subject: Re: modprobe: FATAL: Error inserting hci_usb - msg#00054

Previous Message by Date: click to view message preview

Re: modprobe: FATAL: Error inserting hci_usb

On Wed, 2004-10-13 at 20:30 +0200, Pander wrote: > I also patched the 2.6.8.1 kernel source with patch-2.6.8-mh2 but that > resulted in the same error. dmesg says the same as above. Does anyone > know how to fix this? The unknown symbols are from the core bluetooth.ko module. It looks like an attempt has been made to insmod the hci_usb.ko module _without_ first loading the bluetooth.ko modules. The modules are _also_ loaded correctly though, and then it works. I don't see this with Fedora on my PowerBook G4. I suspect it's a userspace problem. Check that the dependencies are correct -- has depmod been run? -- dwmw2 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl

Next Message by Date: click to view message preview

Re: question about hci_usb endpoint selection...

Hi Lars, > OK, I added hci_usb_notify(..) and it works as it should (get's the > notify when voice mode is changed). you also need some extra changes from my Bitkeeper repository, because I fixed some locking parts around the notify framework. The number of ACL and SCO links are now also counted separately. You need that for selecting the correct alternate setting. > Now for the "real stuff"... :) > > I think to handle the voice mode change correctly, I have to duplicate > the code from about line 874..922 that locates the "proper" alternate > setting; before this can happen, the notify function must close No, because the correct alternate setting is described in the Bluetooth HCI USB transport specification. > ((husb *)hdev->driver_data)->isoc_iface with > usb_driver_release_interface(...) Don't try to release and claim it again. You are not in the probe() function. > is there anything else to do? Must some buffers be dropped or free'd or > something? is it possible to simply re-set > isoc_iface, isoc_in_ep and isoc_out_ep? No simple reset. Change the alternate setting, but you maybe have to suspend the ISOC URBs first and then resume them. Check the USB API definition of it first. > Or is it in fact not neccesary to disconnect isoc_iface and only change > the values of isoc_in_ep and isoc_out_ep? Maybe you should look at the /proc/bus/usb/devices first, because the endpoint identifiers on the second interface are always the same. You must tell the USB core to switch the alternate setting. Regards Marcel ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl

Previous Message by Thread: click to view message preview

Re: modprobe: FATAL: Error inserting hci_usb

On Wed, 2004-10-13 at 20:30 +0200, Pander wrote: > I also patched the 2.6.8.1 kernel source with patch-2.6.8-mh2 but that > resulted in the same error. dmesg says the same as above. Does anyone > know how to fix this? The unknown symbols are from the core bluetooth.ko module. It looks like an attempt has been made to insmod the hci_usb.ko module _without_ first loading the bluetooth.ko modules. The modules are _also_ loaded correctly though, and then it works. I don't see this with Fedora on my PowerBook G4. I suspect it's a userspace problem. Check that the dependencies are correct -- has depmod been run? -- dwmw2 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl

Next Message by Thread: click to view message preview

(dtl1_cs) Problems with Socket CF card on HP Jornada

Hi everyone, I am trying to use a Socket CF card (revision F, model no "8510-00159 F") with Linux (2.6.8.1-hh0 kernel) and Bluez on an HP Jornada 568 PDA for a project for our lab. It seems that I am running into the same problem that was described here: http://sourceforge.net/mailarchive/message.php?msg_id=1427158 When I run: root@jornada56x:~# hciconfig hci0: Type: PCCARD BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN INIT RUNNING RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:0 However: root@jornada56x:~# hciconfig hci0 up Can't init device hci0. Connection timed out(110) And: root@jornada56x:~# hcidump -x HCIDump - HCI packet analyzer ver 1.10 device: hci0 snap_len: 1028 filter: 0xffffffff < HCI Command: Read Local Supported Features (0x04|0x0003) plen 0 At boot time I get this: Starting Bluetooth subsystem:Bluetooth: Core ver 2.6 NET: Registered protocol family 31 Bluetooth: HCI device and connection manager initialized Bluetooth: HCI socket layer initialized hcid sdpdCan't open HIDP control socket: Protocol not supported hiddCan't open RFCOMM control socket: Protocol not supported rfcomm. Starting PCMCIA services: cardmgr[879]: watching 1 socket done. cardmgr[880]: socket 0: Socket Bluetooth Card Bluetooth: Nokia control data = 07 00 Any ideas/help are most appreciated, thanks in advance, Catalin ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl