public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluez-utils on old kernel
Date: Thu, 07 Jun 2007 12:22:46 +0200	[thread overview]
Message-ID: <1181211767.13429.170.camel@violet> (raw)
In-Reply-To: <1831337479@web.de>

Hi Philipp,

> I'm still tring to get my bluetooth working.
> Then I plugin the stick it is correct show when I run lsusb.
> 
> Bus 001 Device 002: ID 0a5c:2101 Broadcom Corp.

include the content of /proc/bus/usb/devices.

> Next I start to load the modules:
> 
> insmod
>   bluetooth
>   sco
>   l2cap
>   rfcomm
>   hci_uart
>   hci_vhci
>   firmware_class
>   hidp
>   bcm203x
>   hci_usb
> 
> but when the last module is loaded I get a segmentation fault

>>From what? Include information about it.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2007-06-07 10:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-06 17:24 [Bluez-users] bluez-utils on old kernel 01flipstar
2007-06-07 10:22 ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-08 23:30 01flipstar
2007-06-09  8:25 ` Marcel Holtmann
2007-06-07 15:38 01flipstar
2007-06-04 21:19 01flipstar
2007-06-03 14:44 01flipstar
2007-06-04 15:23 ` Marcel Holtmann
2007-06-04 15:43 ` Voni Hakau

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=1181211767.13429.170.camel@violet \
    --to=marcel@holtmann.org \
    --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