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

Previous Message by Date: click to view message preview

Re: modprobe: FATAL: Error inserting hci_usb

Marcel Holtmann wrote: Hi Pander, I'm have build linux kernel 2.6.8.1 with Debian testing distro on a PowerPC (PowerBook G4). All went well and booted oke except for bleutooth support: ... modprobe: FATAL: Error inserting hci_usb (/lib/modules/2.6.8.1-pbg4/kernel/drivers/bluetooth/hci_usb.ko): Unknown symbol in module, or unknown parameter (see dmesg) 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? I have seen this too, but sometimes it still works. Check with lsmod if the module is loaded. Hi Marcel, it works althought the FATAL is being reported. Thanks, Pander 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

Next Message by Date: click to view message preview

Re: question about hci_usb endpoint selection...

Hi Lars, > I already asked this before, but I want to "nail down" this problem now, > so I'm asking again and hope that someone can give some suggestions that > even my stupid brain can understand. If this is the wrong list to ask, > just point me to the correct one, and I'll post again there. > > The problem is this: > when using sco and using different voice modes (0x0060 for 16bit/8kHz, > 0x0040 for 8bit/8kHz), different "alternate settings" have to be used on > hci_usb. > > The former answer was: > "Don't use this patch [changing the "alternate settings" selection > hardcodedly] and accept the default voice setting of 0x0060." > > We really don't want to. There are MANY people out there who want to use > 16 bit audio, and MANY who want to use 8bit MU_LAW. What has to be done > to make it possible to change this "alternate setting" when we actually > *need* not alternate setting "2" (16bit), but use alternate setting "1" > when needed? > > Marcel pointed out that: > "You can make use of the notify() callback and adjust the alternate > setting as needed. Maybe you have to unlink and re-submit the ISOC > URB's, but the best way is to start the ISOC URB's only when a SCO > connection is created." > > Uhm, sorry. What? Yes, I'm not firm in kernel hacking, yes, I did not > RTFM, please just push me into the right direction here. Either API > documentation href and/or "use this and that function", or just dump > some lines of pseudo code with "what function comes from what API" so > that I can get a basic understanding what's going on in hci_usb. What > notify callback? How to register? Where can I find an example of someone > else doing this? Where can I find out what an ISOC URB really is? look at the hci_usb driver and add the notify() callback function for it. This function gets called when you change the voice setting or a new connection is added or removed. I changed the connection hash to count the ACL and SCO links separatly and disabled the tasklet when calling this function so that the core stops processing TX packets and enable it after the driver finished anything it has to do. 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

Marcel Holtmann wrote: Hi Pander, I'm have build linux kernel 2.6.8.1 with Debian testing distro on a PowerPC (PowerBook G4). All went well and booted oke except for bleutooth support: ... modprobe: FATAL: Error inserting hci_usb (/lib/modules/2.6.8.1-pbg4/kernel/drivers/bluetooth/hci_usb.ko): Unknown symbol in module, or unknown parameter (see dmesg) 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? I have seen this too, but sometimes it still works. Check with lsmod if the module is loaded. Hi Marcel, it works althought the FATAL is being reported. Thanks, Pander 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

Next 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