From: "Hamid MENOUAR" <menouar@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Module bluez not found
Date: Fri, 3 Aug 2007 08:27:45 +0200 [thread overview]
Message-ID: <d5920d1e0708022327v665d3c02gc8799485d896d459@mail.gmail.com> (raw)
In-Reply-To: <57c68ddc0708010345u73c7482esff100f76b20646fc@mail.gmail.com>
Thank you for your answer.
Even when doing that, still no devices is detected when scanning
(hcitool scan) !!
Regards,
Menouar
On 8/1/07, siddhant tewari <siddhant.tewari@gmail.com> wrote:
> u should try
> modprobe hci_usb
> modprobe rfcomm
>
> then run
> hciconfig hci0 up (only one dongle attached)
>
> then
> hcitool scan (if near by devices are scanned succesfully then part of
> bluetooth system is working fine)
>
> now for sending and recieving files you should try searching in mail
> archive.....
>
> regards
> siddhant
>
>
>
> On 8/1/07, Hamid MENOUAR < menouar@gmail.com> wrote:
> >
> > Dear all,
> >
> > In order to use Bluez to connect some bluetooth device on my computer,
> > I have installed on my Linux FC2 the four following packages
> > (bluez-libs, bluez-utils, bluez-firmware, bluez-hcidump).
> >
> > And, when trying to load the Bluez module manually by doing "modprobe
> > bluez" it says "FATAL: Module bluez not found."
> >
> > Could anyone help me to explain and solve this?
> >
> > Thank you in advance,
> > Menouar
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > Bluez-users mailing list
> > Bluez-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bluez-users
> >
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-08-03 6:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 8:51 [Bluez-users] Module bluez not found Hamid MENOUAR
2007-08-01 10:45 ` siddhant tewari
2007-08-03 6:27 ` Hamid MENOUAR [this message]
2007-08-03 6:30 ` siddhant tewari
2007-08-03 7:11 ` Hamid MENOUAR
2007-08-06 16:31 ` Hamid MENOUAR
2007-08-01 12:52 ` Timothy Murphy
2007-08-03 6:32 ` Hamid MENOUAR
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=d5920d1e0708022327v665d3c02gc8799485d896d459@mail.gmail.com \
--to=menouar@gmail.com \
--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