OESF Portables Forum
Everything Else => General Support and Discussion => Zaurus General Forums => Archived Forums => Security and Networking => Topic started by: Russ Palmer on September 12, 2005, 01:27:31 pm
-
Summary
I am having problems with the D-Link DCF-650BT CF card on SL-C3000 and would appreicate any assistance in debugging the problem.
Everything looks fine; however after a few pings, l2ping timeouts out and dmesg has the following entries:
bcsp_pkt_cull: Peer acked invalid packet
bcsp_handle_le_pkt: Found a LE sync pkt, card has reset
bcsp_pkt_cull: Peer acked invalid packet
bcsp_handle_le_pkt: Found a LE sync pkt, card has reset
bcsp_pkt_cull: Peer acked invalid packet
bcsp_handle_le_pkt: Found a LE sync pkt, card has reset
. . .
Detailed Description
1. Reboot the Zaurus w/ the D-Link CF card installed.
2. After the reboot, the card is recognized.
cardctl ident gives:
Socket 0:
product info: "Bluetooth BT0100M", "", ""
function: 2 (serial)
Socket 1:
product info: "HITACHI", "microdrive"
manfid: 0x0319, 0x0000
function: 4 (fixed disk)
3. hci also appears to be ok.
hciconfig -a gives:
hci0: Type: UART
BD Address: 00:40:05:D4:A4:6D ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:584 acl:0 sco:0 events:16 errors:0
TX bytes:500 acl:0 sco:0 commands:16 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'zaurus'
Class: 0x120104
Service Classes: Networking
Device Class: Computer, Desktop workstation
HCI Ver: 1.1 (0x1) HCI Rev: 0x110 LMP Ver: 1.1 (0x1) LMP Subver: 0x110
Manufacturer: Cambridge Silicon Radio (10)
hcitool dev gives:
Devices:
hci0 00:40:05:D4:A4:6D
4. Can successfully scan for neighboring devices:
hcitool scan gives:
Scanning ...
00:12:F3:00:51:8A BD2
5. However the l2ping fails after a few seconds:
Ping: 00:12:f3:00:51:8a from 00:40:05:D4:A4:6D (data size 20) ...
20 bytes from 00:12:f3:00:51:8a id 0 time 39.24ms
20 bytes from 00:12:f3:00:51:8a id 1 time 74.83ms
no response from 00:12:f3:00:51:8a: id 201
no response from 00:12:f3:00:51:8a: id 202
no response from 00:12:f3:00:51:8a: id 203
no response from 00:12:f3:00:51:8a: id 204
. . .
Configuration
I'm using the Sharp ROM and have the following packages installed:
sudo_0.1_arm.ipk
susp-resume_0.9-3.1.ipk
bluez-zaurus_2.12-2.4.20-alpha4_arm.ipk
susp-resume-bluez_0.9.3_arm.ipk
cat /etc/bluetooth/uart
"Bluetooth BT0100M", "", "":/dev/ttyS3 bcsp
. . .
cat /etc/bluetooth/hcid.conf
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.3 2002/07/18 18:12:46 maxk Exp $
#
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security auto;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# PIN helper
pin_helper /etc/bluetooth/givepin;
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h";
# Local device class
#class 0x120114;
class 0x120104;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
iscan enable; pscan enable;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
#
#lm accept,master;
#
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
#
#lp hold,sniff;
#
lp rswitch,hold,sniff,park;
# Authentication and Encryption
#auth enable;
#encrypt enable;
}
-
It works. . . but only if the USB cable is connected to my Windows PC.
If I try the steps to reproduce the described problem with the USB cable connected to my Windows box every thing works as it should. l2ping has been going for 15 minutes with response times right around 45 ms.
If I try the steps to reproduce the described problem without the USB cable connected then the problem occurs every time.
Does anyone have an idea why having the USB cable would make my bluetooth CF card work? This is a PDA, so I can't have this only working when my Zaurus is connected to a Windows PC via USB.