Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Elimar Riesebieter <riesebie@lxtec.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Re: Apple bluetooth mouse
Date: Tue, 30 Dec 2003 20:49:26 +0100	[thread overview]
Message-ID: <1072813766.2542.28.camel@pegasus> (raw)
In-Reply-To: <20031230182456.GA3035@samweis.home.lxtec.de>

Hi Elimar,

> I try to get an Apple bt mouse to work with my 2.6.0 Debian system on
> powerpc G4 1Ghz laptop.
> 
> I`ve 
> download the deb sources,
> updated bluez-libs to 2.5 and bluez-utils to 2.4,
> and patched the kernel with
> http://www.holtmann.org/linux/kernel/patch-2.6.0-mh1.gz.
> 
> I didn't found a bluez module so I changed bluez to bluetooth in
> /etc/modutils/bluez.
> 
> After restarting the hid daemon there is no device hci0. create_dev
> fom Marcel Holtmann didn't help. Anyway the devices rfcomm* and vhci
> where still there. Following modules where loaded from the hid and
> sdp daemons:
> $ /sbin/lsmod | head -4
> Module                  Size  Used by
> rfcomm                 34200  0
> l2cap                  25028  5 rfcomm
> bluetooth              54912  6 rfcomm,l2cap
> 
> $ hcitool inq
> Inquiry failed.: No such device
> Inquiring ...
> 
> ls-pci -vv doesn't list me a something like bluetooth controller but
> unknown devices. Maybe the kernel does not recognize the responsible
> controller?
> 
> $ lspci | grep -i unknown
> 00:10.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4e50
> 01:0b.0 Host bridge: Apple Computer Inc.: Unknown device 0035
> 01:17.0 Class ff00: Apple Computer Inc.: Unknown device 003e
> 01:18.0 USB Controller: Apple Computer Inc.: Unknown device 003f
> 01:19.0 USB Controller: Apple Computer Inc.: Unknown device 003f
> 01:1a.0 USB Controller: Apple Computer Inc.: Unknown device 003f
> 06:0b.0 Host bridge: Apple Computer Inc.: Unknown device 0036
> 06:0d.0 Class ff00: Apple Computer Inc.: Unknown device 003b

send us "lspci -vvv" (as root) and the content of /proc/bus/usb/devices.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2003-12-30 19:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031228012502.GA16798@samweis.home.lxtec.de>
     [not found] ` <20031228170349.GA1460@samweis.home.lxtec.de>
     [not found]   ` <m3fzf47oa3.fsf@neo.loria>
2003-12-30 18:24     ` [Bluez-users] Re: Apple bluetooth mouse Elimar Riesebieter
2003-12-30 19:49       ` Marcel Holtmann [this message]
     [not found]         ` <20031229175358.GA801@samweis.home.lxtec.de>
2003-12-30 20:59           ` [Bluez-users] " Elimar Riesebieter
2003-12-30 21:06             ` Marcel Holtmann
2003-12-30 22:15               ` Elimar Riesebieter
2003-12-31  8:04                 ` 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=1072813766.2542.28.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=riesebie@lxtec.de \
    /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