public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Hung Dang <hungptit@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Bluetooth problem
Date: Fri, 17 Sep 2010 14:25:24 -0600	[thread overview]
Message-ID: <4C93CEB4.3010809@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2526 bytes --]

 Hi all,

I have Logitech Dinovo Edge and it works fine before. I update my system
recently and my bluetooth is messed up. Every time I start Bluetooth
Manager in GNOME I receive this message "Bluez daemon is not running,
blueman-manager cannot continue.". I am using Bluez-4.7.1 and Linux
kernel 2.34 and 2.35. I also check the output of the lsmod command and
modules bnep, hcid and sco are not loaded when bluetooth service start.
Plus I get no device when scanning for devices using "hcitool scan" and
the utility hid2hci is not in the system path.

Any suggestion?

Thanks in advance
Hung

Output of lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 004: ID 046d:c714 Logitech, Inc.
Bus 008 Device 003: ID 046d:c713 Logitech, Inc.
Bus 008 Device 002: ID 046d:0b04 Logitech, Inc.
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 041e:4055 Creative Technology, Ltd Live! Cam
Video IM Pro
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 413c:3010 Dell Computer Corp. Optical Wheel Mouse
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub


Output of lsmod
Module                  Size  Used by
nvidia              11087655  28
coretemp                5654  0
rfcomm                 38363  1
l2cap                  33680  3 rfcomm
snd_seq_dummy           1678  0
snd_seq_oss            28171  0
snd_seq_midi_event      6939  1 snd_seq_oss
snd_seq                53057  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          6394  3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            37296  0
snd_mixer_oss          16313  1 snd_pcm_oss
snd_hda_codec_realtek   287298  1
snd_hda_intel          22483  1
snd_hda_codec          71101  2 snd_hda_codec_realtek,snd_hda_intel
snd_hwdep               6386  1 snd_hda_codec
snd_pcm                76889  3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
snd_timer              20930  2 snd_seq,snd_pcm
snd                    66779  13
snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore               7579  1 snd
snd_page_alloc          8428  2 snd_hda_intel,snd_pcm
i2c_i801                8249  0


[-- Attachment #2: Type: text/html, Size: 5013 bytes --]

                 reply	other threads:[~2010-09-17 20:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4C93CEB4.3010809@gmail.com \
    --to=hungptit@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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