Nic
09.12.06, 17:28
Hallo zusammen,
nachdem ich hier schon mächtig (& erfolglos) rumgesucht habe, schreibe ich doch mal:
Ich habe einen AMD 64, SuSE 10.0, aktueller Stand, und einen ANYCOM USB-200-Adapter. Die üblichen verdächtigen Pakete sind per YAST installiert, der Stick wird auch erkannt:
localhost:/etc/bluetooth # hciconfig -a
hci0: Type: USB
BD Address: 00:16:38:C4:36:6B ACL MTU: 1017:8 SCO MTU: 64:1
UP RUNNING
RX bytes:105 acl:0 sco:0 events:14 errors:0
TX bytes:309 acl:0 sco:0 commands:14 errors:0
Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Can't read local name on hci0: Input/output error (5)
localhost:/etc/bluetooth #
Komisch ist, daß der Name angeblich nicht erkannt wird. Hier ist mal die hci.config:
ocalhost:/etc/bluetooth # more hcid.conf
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann 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
# if you want a interactiv query of your pin use /usr/bin/bluepin
# /bin/bluepincat is using the pin in the /etc/bluetooth/pin file
# pin_helper /usr/bin/bluepin;
#pin_helper /bin/bluepincat;
pin_helper /bin/bluepincat;
# D-Bus PIN helper
#dbus_pin_helper;
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "BlueZ %h %d";
# Local device class
# e.g.
# 0xsss100 = Computer
# 0xsss104 = Computer Desktop
# 0xsss108 = Computer Server
# 0xsss10c = Computer Laptop
# The 'sss' above defines the service-class (not quite, only the
# first 11 bits, the next 11 define the device-class, than 2 format bits
.)
# See https://www.bluetooth.org/foundry/assignnumb/document/baseband
# for more information.
# 0x100bbb stands for "Object Transfer (v-Inbox, v-Folder, ...)"
# 0x020bbb stands for "Networking (LAN, Ad hoc, ...)"
class 0x700100;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
# valid parameters: enable | disable
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;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
# Authentication and Encryption (Security Mode 3)
auth disable;
encrypt disable;
}
localhost:/etc/bluetooth #
Auf den Scan kommt folgendes:
ec 9 17:44:05 linux hcid[10725]: HCI dev 0 unregistered
Dec 9 17:44:15 linux kernel: usb 1-5.4: new full speed USB device using ehci_hcd and address 13
Dec 9 17:44:15 linux kernel: hub 1-5.4:1.0: USB hub found
Dec 9 17:44:15 linux kernel: hub 1-5.4:1.0: 3 ports detected
Dec 9 17:44:16 linux kernel: usb 1-5.4.1: new full speed USB device using ehci_hcd and address 14
Dec 9 17:44:16 linux hcid[10725]: HCI dev 0 registered
Dec 9 17:44:16 linux kernel: hci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb ffff810020f25228 err -28
Dec 9 17:44:16 linux kernel: hci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb ffff810020f25228 err -28
Dec 9 17:44:16 linux hcid[10725]: HCI dev 0 up
Dec 9 17:44:16 linux hcid[10725]: Starting security manager 0
Dec 9 17:44:16 linux hcid[12629]: Can't set scan mode on hci0: Device or resource busy (16)
Dec 9 17:44:16 linux hcid[12629]: Can't set auth on hci0: Device or resource busy (16)
Dec 9 17:44:16 linux hcid[12629]: Can't set encrypt on hci0: Device or resource busy (16)
Dec 9 17:44:16 linux kernel: usb 1-5.4.2: new full speed USB device using ehci_hcd and address 15
Dec 9 17:44:26 linux kernel: drivers/usb/input/hid-core.c: timeout initializing reports
Dec 9 17:44:26 linux kernel:
Dec 9 17:44:26 linux kernel: input: USB HID v1.11 Keyboard [Broadcom Corp ANYCOM Bluetooth USB-200 UHE] on usb-0000:00:02.2-5.4.2
Dec 9 17:44:26 linux kernel: usb 1-5.4.3: new full speed USB device using ehci_hcd and address 16
Dec 9 17:44:36 linux kernel: drivers/usb/input/hid-core.c: timeout initializing reports
Dec 9 17:44:36 linux kernel:
Dec 9 17:44:36 linux kernel: input: USB HID v1.11 Mouse [Broadcom Corp ANYCOM Bluetooth USB-200 UHE] on usb-0000:00:02.2-5.4.3
Dec 9 18:23:03 linux syslog-ng[5167]: STATS: dropped 0
localhost:/etc/bluetooth #
Das GUI für den Bluetooth OBEX Object push client erscheint erst, wenn ich den BT-USB-Stick abziehe, zusammen mit Fehlermeldungen, daß das Device fehlt...
Ich weiß hier nicht mehr weiter, die Treiber (Broadcom) sind mit dem YAST-Firmware-Paket geladen und soweit scheint sonst alles zu stimmen.
Danke & Gruß
Nic
nachdem ich hier schon mächtig (& erfolglos) rumgesucht habe, schreibe ich doch mal:
Ich habe einen AMD 64, SuSE 10.0, aktueller Stand, und einen ANYCOM USB-200-Adapter. Die üblichen verdächtigen Pakete sind per YAST installiert, der Stick wird auch erkannt:
localhost:/etc/bluetooth # hciconfig -a
hci0: Type: USB
BD Address: 00:16:38:C4:36:6B ACL MTU: 1017:8 SCO MTU: 64:1
UP RUNNING
RX bytes:105 acl:0 sco:0 events:14 errors:0
TX bytes:309 acl:0 sco:0 commands:14 errors:0
Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Can't read local name on hci0: Input/output error (5)
localhost:/etc/bluetooth #
Komisch ist, daß der Name angeblich nicht erkannt wird. Hier ist mal die hci.config:
ocalhost:/etc/bluetooth # more hcid.conf
#
# HCI daemon configuration file.
#
# $Id: hcid.conf,v 1.7 2004/12/13 14:16:03 holtmann 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
# if you want a interactiv query of your pin use /usr/bin/bluepin
# /bin/bluepincat is using the pin in the /etc/bluetooth/pin file
# pin_helper /usr/bin/bluepin;
#pin_helper /bin/bluepincat;
pin_helper /bin/bluepincat;
# D-Bus PIN helper
#dbus_pin_helper;
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "BlueZ %h %d";
# Local device class
# e.g.
# 0xsss100 = Computer
# 0xsss104 = Computer Desktop
# 0xsss108 = Computer Server
# 0xsss10c = Computer Laptop
# The 'sss' above defines the service-class (not quite, only the
# first 11 bits, the next 11 define the device-class, than 2 format bits
.)
# See https://www.bluetooth.org/foundry/assignnumb/document/baseband
# for more information.
# 0x100bbb stands for "Object Transfer (v-Inbox, v-Folder, ...)"
# 0x020bbb stands for "Networking (LAN, Ad hoc, ...)"
class 0x700100;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
# valid parameters: enable | disable
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;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
# Authentication and Encryption (Security Mode 3)
auth disable;
encrypt disable;
}
localhost:/etc/bluetooth #
Auf den Scan kommt folgendes:
ec 9 17:44:05 linux hcid[10725]: HCI dev 0 unregistered
Dec 9 17:44:15 linux kernel: usb 1-5.4: new full speed USB device using ehci_hcd and address 13
Dec 9 17:44:15 linux kernel: hub 1-5.4:1.0: USB hub found
Dec 9 17:44:15 linux kernel: hub 1-5.4:1.0: 3 ports detected
Dec 9 17:44:16 linux kernel: usb 1-5.4.1: new full speed USB device using ehci_hcd and address 14
Dec 9 17:44:16 linux hcid[10725]: HCI dev 0 registered
Dec 9 17:44:16 linux kernel: hci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb ffff810020f25228 err -28
Dec 9 17:44:16 linux kernel: hci_usb_isoc_rx_submit: hci0 isoc rx submit failed urb ffff810020f25228 err -28
Dec 9 17:44:16 linux hcid[10725]: HCI dev 0 up
Dec 9 17:44:16 linux hcid[10725]: Starting security manager 0
Dec 9 17:44:16 linux hcid[12629]: Can't set scan mode on hci0: Device or resource busy (16)
Dec 9 17:44:16 linux hcid[12629]: Can't set auth on hci0: Device or resource busy (16)
Dec 9 17:44:16 linux hcid[12629]: Can't set encrypt on hci0: Device or resource busy (16)
Dec 9 17:44:16 linux kernel: usb 1-5.4.2: new full speed USB device using ehci_hcd and address 15
Dec 9 17:44:26 linux kernel: drivers/usb/input/hid-core.c: timeout initializing reports
Dec 9 17:44:26 linux kernel:
Dec 9 17:44:26 linux kernel: input: USB HID v1.11 Keyboard [Broadcom Corp ANYCOM Bluetooth USB-200 UHE] on usb-0000:00:02.2-5.4.2
Dec 9 17:44:26 linux kernel: usb 1-5.4.3: new full speed USB device using ehci_hcd and address 16
Dec 9 17:44:36 linux kernel: drivers/usb/input/hid-core.c: timeout initializing reports
Dec 9 17:44:36 linux kernel:
Dec 9 17:44:36 linux kernel: input: USB HID v1.11 Mouse [Broadcom Corp ANYCOM Bluetooth USB-200 UHE] on usb-0000:00:02.2-5.4.3
Dec 9 18:23:03 linux syslog-ng[5167]: STATS: dropped 0
localhost:/etc/bluetooth #
Das GUI für den Bluetooth OBEX Object push client erscheint erst, wenn ich den BT-USB-Stick abziehe, zusammen mit Fehlermeldungen, daß das Device fehlt...
Ich weiß hier nicht mehr weiter, die Treiber (Broadcom) sind mit dem YAST-Firmware-Paket geladen und soweit scheint sonst alles zu stimmen.
Danke & Gruß
Nic