| [crisos] Bluetooth USB dongle (key) Problem |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/crisos Archives
]
- To: crisos@xxxxxxxxxxxxxxxxxxx
- Subject: [crisos] Bluetooth USB dongle (key) Problem
- From: "Matteo Carnevali" <rekstorm@xxxxxxxx>
- Date: Wed, 24 Dec 2008 11:03:23 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:mime-version:content-type:x-google-sender-auth; bh=TsWrIaRhV5Kfk3u4R3tRG7hr6bUjXE8ovhkFpKgYntI=; b=QyKbbqV/mCNJN4lZqyXlSl2Ljcokhslbqt8snY0NKQ2ofiqRRA5n6HL0Q/IkGECBmu Qke/iBWoPHFMdNfL4N6S2gTKxDXRP93B3LYU+B4CTdnyDH0S+nBz1BduKLTgmkEE/70l f09JmhqNrc/5IEjQkbuksmhQyw5xF6dQzGegE=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :x-google-sender-auth; b=dtVQLYH4CvuKexriWI/mqT1cX7EGoT4JgDnbqqHxeieGB0ACLq2KJK6hQ7KFTOO5/8 RbyKxOvGWF2cSUan/aiODDghr5cincZxAGnlcdID9kI9ICAQ6H2d1Yq2Hc7ZzSlleLOe STwgcrvgRGtQYozkR6dU83IrC1Vx0HDMFQjvU=
Hi,
I'm using CrisOS on an ACME System Fox Board, I installed bluez-utils and kmod-bluetooth (as explained here: http://crisos.org/dokuwiki/doku.php?id=documentation:wiki:bluez_play), I've a Broadcom chip based usb bluetooth dongle (labelled DIKOM) that works very well on Ubuntu 8.10 but it gives me problems with CrisOs.
When booting crisos I get the following output which shows that bluez is corectly installed.
Please press Enter to activate this console. PPP generic driver version 2.4.2
ip_tables: (C) 2000-2006 Netfilter Core Team
nf_conntrack version 0.5.0 (2048 buckets, 8192 max)
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.9
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.5
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: BNEP (Ethernet Emulation) ver 1.2
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Bluetooth: HCI USB driver ver 2.9
usbcore: registered new interface driver hci_usb
As soon as I insert the USB Bluetooth dongle I get the following:
root@CrisOs:/# crisv10_irq dbg: ctr_status_irq, controller status: host_mode started
crisv10_irq dbg: ctr_status_irq, controller status: host_mode started running
usb 1-2: new full speed USB device using hc-crisv10 and address 2
usb 1-2: configuration #1 chosen from 1 choice
Unable to handle kernel access at virtual address 20c1a000
Oops: 0002
IRP: d00fe95e SRP: c00e4812 DCCR: 00000428 USP: 00000000 MOF: ffffff5d
r0: c1f53115 r1: c1f53080 r2: 20c1b075 r3: c1f530d0
r4: 00000004 r5: c1f530a0 r6: c1f53119 r7: c1f530d4
r8: c1f530a1 r9: fffffffd r10: c1f53080 r11: 00000000
r12: 00000001 r13: ff000008 oR10: c1f53080 sp: c1f75cb0
R_MMU_CAUSE: d0075012
Process khubd (pid: 28, stackpage=c1fda060)
Stack from c1f75bc0:
c000e36c c1f75cb0 c0004348 c00056ae c1f75cb0 ffffff5d c1f75cb0 c1fda060
20c1a000 00000000 c1f75cb0 c0004418 20c1a000 c000509a 00989680 c1f53119
c1f530a0 00000004 b000022d c1b26000 20c1b112 20c1a000 00000000 00000000
Call Trace: [<c000e36c>] [<c0004348>] [<c00056ae>] [<c0004418>] [<c000509a>] [<c0096aba>] [<d010053c>]
[<c0008fea>] [<c00054b0>] [<c00e4812>] [<d00fe95e>] [<d00fea10>] [<c001ed4a>] [<d010b6e0>] [<c001ed9a>]
[<c001edae>] [<d00faab4>] [<d00fb812>] [<d010b0a6>] [<d010b604>] [<d010b634>] [<c00ca8da>] [<d010b634>]
[<c00ab186>] [<c00ab200>] [<c00ab20a>] [<c00aa5cc>] [<c00ab28e>] [<c00a9630>] [<c00aa55a>] [<c00a9630>]
[<c00a983e>] [<c00c9a82>] [<c00cf356>] [<c00ab042>] [<c00ca7d8>] [<c00ab186>] [<c00ab200>] [<c00ab20a>]
[<c00aa5cc>] [<c00ab28e>] [<c00a9630>] [<c00aa55a>] [<c00a9630>] [<c00a983e>] [<c0092c36>] [<c00c5c0a>]
[<c00c6b2e>] [<c000a456>] [<c00c6534>] [<c001bf22>] [<c001bd2e>] [<c00062ea>]
Code: 42 b2 3f bd b4 35 0e c0 7d 92 c2 9f (44) 96 02 92 c2 9b 64 b6 02 b2 a7 0b
And typing standard commands to work with bluetooth I get:
root@CrisOs:/# hciconfig
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
or
root@CrisOs:/# hcitool dev
Devices:
root@CrisOs:/# hcitool scan
Device is not available: No such device
The same happen booting crisos with the USB BT dongle in!
I also did some trials removing hci_usb module, then inserting the USB BT dongle, and then re-inserting the hci_usb module but when I do insmod I get "Segmentation fault"!
The same happens if I remove hci_usb ant all the dependent modules: hci_uart, rfcomm, sco, bnep, l2cap, bluetooth, then isert the USB BT dongle and then reload the modules.
Anybody experienced the same situation or has suggestions?
Thank you in advance!
Matteo