From: Michal Semler <cijoml@volny.cz>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] BT3030
Date: Sun, 16 May 2004 18:07:38 +0200 [thread overview]
Message-ID: <200405161807.38658.cijoml@volny.cz> (raw)
In-Reply-To: <200405162253.38581.hedin@hiervard.ru>
On Sunday 16 of May 2004 17:53, =E8=C5=C4=C9=CE wrote:
> Saturday 15 May 2004 16:01, Marcel Holtmann =D0=C9=DB=C5=D4:
> > Hi Hedin,
> >
> > > Here is my `dmesg` log after I load my modules after connecting the
> > > dongle:
> > >
> > > usb 1-1: new full speed USB device using address 3
> > > Bluetooth: Core ver 2.4
> > > NET: Registered protocol family 31
> > > Bluetooth: HCI device and connection manager initialized
> > > Bluetooth: HCI socket layer initialized
> > > Bluetooth: L2CAP ver 2.1
> > > Bluetooth: L2CAP socket layer initialized
> > > Bluetooth: HCI USB driver ver 2.5
> > > usbcore: registered new driver hci_usb
> > > Bluetooth: Broadcom Blutonium firmware driver ver 1.0
> > > bcm203x_probe: Mini driver request failed
> > > bcm203x: probe of 1-1:1.0 failed with error -5
> > > usbcore: registered new driver bcm203x
> >
> > this means that the request for the mini driver file BCM2033-MD.hex
> > failed. You need /sys mounted, you need /etc/hotplug/firmware.agent and
> > you must put the two firmware files from Broadcom in the firmware
> > directory under /usr/lib/hotplug/firmware.
>
> Sorry for dumb questions. I got these two filfes into
> /usr/lib/hotplug/firware (I took them from bluez-blufw package).
> The error still remains.
>
> But how about another one? I can't find it and what is "/sys" ? (I'm not
> really experienced with Linux, sorry).
write:
mkdir /sys
edit /etc/fstab and add this line:
sysfs /sys sysfs defaults 0 0
save it and write:
mount -a as root
Michal
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-05-16 16:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 2:03 [Bluez-users] BT3030 Hedin
2004-05-15 9:01 ` Marcel Holtmann
[not found] ` <200405162253.38581.hedin@hiervard.ru>
2004-05-16 16:07 ` Michal Semler [this message]
[not found] ` <200405171448.23338.hedin@hiervard.ru>
2004-05-17 10:23 ` Michal Semler
-- strict thread matches above, loose matches on Subject: below --
2004-09-08 13:23 coser
2004-09-08 14:15 ` Marcel Holtmann
2004-09-08 14:34 ` coser
2004-09-08 15:09 ` Marcel Holtmann
2004-05-23 13:27 Хедин
2004-05-23 14:19 ` Marcel Holtmann
2004-05-19 14:02 Хедин
2004-05-19 14:10 ` Marcel Holtmann
2004-01-21 12:55 Nosve
2004-01-20 21:44 Igor Luiz Oliveira de Souza
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=200405161807.38658.cijoml@volny.cz \
--to=cijoml@volny.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox