public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Ricky Soh <rickysoh@gmail.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Help needed (Fedora Core 2)
Date: Mon, 13 Sep 2004 12:40:18 +0200	[thread overview]
Message-ID: <1095072018.5695.35.camel@pegasus> (raw)
In-Reply-To: <db972f43040912183766fef4f9@mail.gmail.com>

Hi Ricky,

> If bluez is installed properly, i should be able to see bluez under
> lsmod right? And l2test and scotest command are bluez command too, why
> are they missing? Please help.

with a 2.6 kernel the core module is named bluetooth.ko and not bluez.o
and the l2test and scotest commands are never installed by default.

Regards

Marcel




-------------------------------------------------------
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

  reply	other threads:[~2004-09-13 10:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <db972f43040909203314e6825d@mail.gmail.com>
     [not found] ` <20040910034429.37672.qmail@web11605.mail.yahoo.com>
2004-09-10  5:36   ` [Bluez-users] Help needed (Fedora Core 2) Ricky Soh
2004-09-12 13:54     ` Marcel Holtmann
2004-09-13  1:37       ` Ricky Soh
2004-09-13 10:40         ` Marcel Holtmann [this message]
2004-09-10  0:59 Ricky Soh
2004-09-10  2:26 ` David Zhu
2004-09-10  2:52   ` Ricky Soh
2004-09-10  3:10     ` David Zhu

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=1095072018.5695.35.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=rickysoh@gmail.com \
    /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