From: Wu Jason <superht001@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Can't init device hci0. Connection timed out(110)
Date: Tue, 9 Aug 2005 00:39:59 +0800 [thread overview]
Message-ID: <8eddf07b05080809396f5d3c1@mail.gmail.com> (raw)
Dear All,
I'm a newbie to use bluez in my school final project on Fedora Core 3.
But I encounter the problem as the Subject "Can't init device hci0.
Connection timed out(110)".
I had search the older mail list, and try many methods to cover the
problem but it still didn't work.
Finally, I still need your help, thanks.
My environment (I had updated the kernal to the lastest version and patch)
[root@localhost ~]# uname -a
Linux localhost.localdomain 2.6.12-mh2 #1 Sat Aug 6 00:25:51 CST 2005
i686 i686 i386 GNU/Linux
[root@localhost ~]# rpm -qa | grep ^bluez
bluez-libs-2.10-2
bluez-hcidump-1.11-1
bluez-bluefw-1.0-6
bluez-utils-2.10-2
Status
[root@localhost ~]# modprobe hci_usb
[root@localhost ~]# modprobe l2cap
[root@localhost ~]# lsmod
Module Size Used by
l2cap 29700 0
hci_usb 17288 0
bluetooth 51972 2 l2cap,hci_usb
md5 4096 1
ipv6 267264 10
parport_pc 26948 1
lp 11272 0
parport 38984 2 parport_pc,lp
autofs4 27652 0
sunrpc 158916 1
ipt_REJECT 4736 1
ipt_state 1792 2
ip_conntrack 39128 1 ipt_state
iptable_filter 2560 1
ip_tables 19200 3 ipt_REJECT,ipt_state,iptable_filter
dm_mod 57396 0
button 5264 0
battery 7940 0
ac 3716 0
uhci_hcd 34192 0
i2c_piix4 8080 0
i2c_core 18816 1 i2c_piix4
pcnet32 33028 0
mii 5248 1 pcnet32
floppy 63028 0
BusLogic 79380 0
sd_mod 17920 0
scsi_mod 138312 2 BusLogic,sd_mod
[root@localhost ~]# hciconfig -a
hci0: Type: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:0 acl:0 sco:0 commands:0 errors:0
Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DH1 HV1
Link policy:
Link mode: SLAVE ACCEPT
[root@localhost ~]# hciconfig hci0 up
Can't init device hci0. Connection timed out(110)
The method I tried (remove the bluetooth.ko)
[root@localhost bluetooth]# pwd
/lib/modules/2.6.12-mh2/kernel/net/bluetooth
[root@localhost bluetooth]# mv bluetooth.ko bluetooth.ko.old
[root@localhost bluetooth]# modprobe hci_usb
WARNING: Could not open
'/lib/modules/2.6.12-mh2/kernel/net/bluetooth/bluetooth.ko': No such
file or directory
FATAL: Error inserting hci_usb
(/lib/modules/2.6.12-mh2/kernel/drivers/bluetooth/hci_usb.ko): Unknown
symbol in module, or unknown parameter (see dmesg)
If you need more information to help me, please let me know, thank for
your help again.
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-08-08 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 16:39 Wu Jason [this message]
2005-08-09 5:59 ` [Bluez-users] Can't init device hci0. Connection timed out(110) hariharan veerappan
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=8eddf07b05080809396f5d3c1@mail.gmail.com \
--to=superht001@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