From: Ricky Soh <rickysoh@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Help needed (Fedora Core 2)
Date: Fri, 10 Sep 2004 08:59:34 +0800 [thread overview]
Message-ID: <db972f43040909175946b8d17a@mail.gmail.com> (raw)
Dear all,
Sorry, i have a noob's question. I am using fedora core2.
1. When i plug in my usb BT dongle, /dev/bluetooth/ directory is not
created. Under lsmod, there is no bluez but only bluetooth. The
command l2ping but not l2test is working only. For l2test, command not
found. Scotest is not found too.
Based on the above symptons, i suspect fedora core 2 does not have the
full version of bluez installed. Am i right to say that or bluez is
not even installed? I tot bluez is the official linux bt protocol,
thus bluetooth in fedora core 2 should be bluez right? Please
enlighten me and advise me how do i get bluez working... thanks.
Sincerely
Ricky
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2004-09-10 0:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 0:59 Ricky Soh [this message]
2004-09-10 2:26 ` [Bluez-users] Help needed (Fedora Core 2) David Zhu
2004-09-10 2:52 ` Ricky Soh
2004-09-10 3:10 ` David Zhu
[not found] <db972f43040909203314e6825d@mail.gmail.com>
[not found] ` <20040910034429.37672.qmail@web11605.mail.yahoo.com>
2004-09-10 5:36 ` Ricky Soh
2004-09-12 13:54 ` Marcel Holtmann
2004-09-13 1:37 ` Ricky Soh
2004-09-13 10:40 ` 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=db972f43040909175946b8d17a@mail.gmail.com \
--to=rickysoh@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