All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Holland <ah160@york.ac.uk>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] blue-fw not working for USB Belkin F8T001 in Gentoo Linux
Date: Wed, 07 Jan 2004 12:31:48 +0000	[thread overview]
Message-ID: <3FFBFC34.3050509@york.ac.uk> (raw)

I'm a Gentoo user, and my kernel and bluetooth modules are all compiled 
using the latest Gentoo Sources, 2.4.22-r2.

When I was using 2.4.20-r9, hci_usb wouldn't see my USB bluetooth dongle 
until after bluefw had run. Since I upgraded to 2.4.22-r2, my dongle is 
detected as part of the standard USB bus scan during boot, although it 
brings up a lot of insmod errors. Further on during the boot, bluefw 
always fails, saying that my device has timed out. This leaves my 
bluetooth device invisible to hciconfig.

Everything works fine if I boot into Windows XP and let the Belkin 
software load the firmware, then reboot into Linux without powering 
down. I still get the insmod errors, but bluefw brings up no error 
messages and all bluetooth things work wonderfully.

I realise this may look more like a Gentoo query than a bluez query, but 
there don't seem to be many bluetooth users on the Gentoo forums, so I 
thought this might be the best place to ask.

For reference, these are the errors I get during bootup:

  * Mounting proc at /proc...   [ ok ]
hub.c: new USB device 00:07.2-2, assigned address 3
usb.c: USB device 3 (vend/prod 0xa5c/0x200a) is not claimed by any 
active driver.
hub.c: new USB device 00:07.2-1.1, assigned address 4
input: USB HID v1.10 Keyboard [045e:001d] on usb1:4.0
input: USB HID v1.10 Device [045e:001d] on usb1:4.1
BlueZ Core ver 2.4 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
insmod: insmod: a module named bluez already exists
insmod: insmod: insmod 
/lib/modules/2.4.22-gentoo-r2/kernel/net/bluetooth/bluez.o failed
insmod: insmod: insmod hci_usb failed
insmod: insmod: a module named bluez already exists
insmod: insmod: insmod 
/lib/modules/2.4.22-gentoo-r2/kernel/net/bluetooth/bluez.o failed
insmod: insmod: insmod hci_usb failed
BlueZ HCI USB driver ver 2.4 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
usb.c: registered new driver hci_usb

Thanks.

Alex Holland



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2004-01-07 12:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 12:31 Alex Holland [this message]
2004-01-07 12:50 ` [Bluez-users] blue-fw not working for USB Belkin F8T001 in Gentoo Linux Marcel Holtmann
2004-01-07 13:03   ` Alex Holland
2004-01-07 16:12     ` Marcel Holtmann
2004-01-07 14:23   ` Marc Hansen
2004-01-07 14:49     ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3FFBFC34.3050509@york.ac.uk \
    --to=ah160@york.ac.uk \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.