From: Marcel Holtmann <marcel@holtmann.org>
To: "Joonas Hämäläinen" <kerberos@mbnet.fi>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluefw problem
Date: 28 Sep 2003 22:37:01 +0200 [thread overview]
Message-ID: <1064781427.5012.33.camel@pegasus> (raw)
In-Reply-To: <1064739488.4196.14.camel@Aielien>
Hi Joonas,
> thing is, I don't seem to have any bluetooth.o on my mandrake. I spent
> quite a while now searching for it, after I tried to get some usefull
> information from archive :)
> This is output from my lsmod, and thre it is also bluez not bluetooth at
> all.
you must have it, otherwise you don't these log entires. Try this:
find /lib/modules/ -name bluetooth.o
> As I told, it works if I first boot into windows, and then reboot to
> mandrake, then I get it working just fine. But if I do hard boot, or
> start right to mandrake, my lsmod looks just same, only difference is
> that my dongel isn't found.
>
> Also, if I unplug dongel when it has been working, and plug it back, it
> isn't found by hciconfig anymore. Same if I do hciconfig hci0 down and
> then try bring it up again.
This means that the firmware loading didn't succeded. The problem can be
bluetooth.o because it grabs the Broadcom device without firmware.
Regards
Marcel
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2003-09-28 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-27 22:57 [Bluez-users] Bluefw problem Joonas Hämäläinen
2003-09-28 7:04 ` Marcel Holtmann
2003-09-28 8:58 ` Joonas Hämäläinen
2003-09-28 20:37 ` Marcel Holtmann [this message]
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=1064781427.5012.33.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=kerberos@mbnet.fi \
/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.