Hilfe bei der Installation einer Bluetooth-Tastatur

    Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

    • Hilfe bei der Installation einer Bluetooth-Tastatur

      ich benötige bie der Installation und Inbetriebnahme der MS Wedge Mobile Tastatur Unterstützung. Da die Tastatur über keinen USB Bluetooth Dongle verfügt, habe ich den Mini Bluetooth USB Dongle Klasse I 2.1 von Gembird erworben. Die Kombination läuft unter Win7 Prof. An der Solo2 (Software aktualisiert) bekomme ich keinen Zugriff auf das Gerät. Bei eingestecktem Dongle bekomme nach dem dmesg-Befehl folgende Aussage:

      Spoiler anzeigen
      > ohci-brcm ohci-brcm.2: irq 76, io mem 0x10490400

      > hub 7-0:1.0: USB hub found

      > hub 7-0:1.0: 1 port detected

      > ohci-brcm ohci-brcm.3: Broadcom STB OHCI

      > ohci-brcm ohci-brcm.3: new USB bus registered, assigned bus number 8

      > ohci-brcm ohci-brcm.3: irq 77, io mem 0x10490600

      > hub 8-0:1.0: USB hub found

      > hub 8-0:1.0: 1 port detected

      > Initializing USB Mass Storage driver...

      > usbcore: registered new interface driver usb-storage

      > USB Mass Storage support registered.

      > mousedev: PS/2 mouse device common for all mice

      > i2c /dev entries driver

      > lirc_dev: IR Remote Control driver registered, major 254
      > IR NEC protocol handler initialized

      > IR RC5(x) protocol handler initialized

      > IR RC6 protocol handler initialized

      > IR JVC protocol handler initialized

      > IR Sony protocol handler initialized

      > IR RC5 (streamzap) protocol handler initialized

      > IR SANYO protocol handler initialized

      > IR MCE Keyboard/mouse protocol handler initialized

      > IR LIRC bridge handler initialized

      > Linux video capture interface: v2.00

      > sdhci: Secure Digital Host Controller Interface driver

      > sdhci: Copyright(c) Pierre Ossman

      > sdhci-pltfm: SDHCI platform and OF driver helper

      > usbcore: registered new interface driver usbhid

      > usbhid: USB HID core driver

      > ALSA device list:

      > No soundcards found.

      > TCP cubic registered
      > NET: Registered protocol family 17
      > lib80211: common routines for IEEE802.11 drivers
      > lib80211_crypt: registered algorithm 'NULL'
      > PM: CP0 COUNT/COMPARE frequency does not depend on divisor
      > EBI CS0: setting up NAND flash (primary)
      > NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-
      bit)
      > brcmnand brcmnand.0: 256MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit,
      Hamming ECC
      > Bad block table found at page 131008, version 0x01
      > Bad block table found at page 130944, version 0x01
      > nand_read_bbt: bad block at 0x000002580000
      > nand_read_bbt: bad block at 0x000008b20000
      > Creating 4 MTD partitions on "brcmnand.0":
      > 0x000001f00000-0x000010000000 : "rootfs"
      > 0x000001f00000-0x000010000000 : "rootfs(redundant)"
      > 0x000000200000-0x000000900000 : "kernel"
      > 0x000000900000-0x000000a00000 : "mac"
      > UBI: attaching mtd0 to ubi0
      > UBI: physical eraseblock size: 131072 bytes (128 KiB)
      > UBI: logical eraseblock size: 126976 bytes
      > UBI: smallest flash I/O unit: 2048
      > UBI: VID header offset: 2048 (aligned 2048)
      > UBI: data offset: 4096
      > usb 8-1: new full-speed USB device number 2 using ohci-brcm
      > UBI: max. sequence number: 4747
      > UBI: attached mtd0 to ubi0
      > UBI: MTD device name: "rootfs"
      > UBI: MTD device size: 225 MiB
      > UBI: number of good PEBs: 1794
      > UBI: number of bad PEBs: 6
      > UBI: number of corrupted PEBs: 0
      > UBI: max. allowed volumes: 128
      > UBI: wear-leveling threshold: 4096
      > UBI: number of internal volumes: 1
      > UBI: number of user volumes: 1
      > UBI: available PEBs: 0
      > UBI: total number of reserved PEBs: 1794
      > UBI: number of PEBs reserved for bad PEB handling: 17
      > UBI: max/mean erase counter: 70/5
      > UBI: image sequence number: 1920545126
      > UBI: background thread "ubi_bgt0d" started, PID 44
      > UBIFS: parse sync
      > UBIFS: mounted UBI device 0, volume 0, name "rootfs"
      > UBIFS: file system size: 223731712 bytes (218488 KiB, 213 MiB, 1762 LEBs)
      > UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
      > UBIFS: media format: w4/r0 (latest is w4/r0)
      > UBIFS: default compressor: lzo
      > UBIFS: reserved for root: 0 bytes (0 KiB)
      > VFS: Mounted root (ubifs filesystem) on device 0:14.
      > devtmpfs: mounted
      > Freeing unused kernel memory: 192k freed
      > NET: Registered protocol family 10
      > procmk_init
      > dvb_bcm7356: module license 'Proprietary' taints kernel.
      > Disabling lock debugging due to kernel taint
      > DVB: registering new adapter (vusolo2)
      > bcm7335: hotplug_callback():
      > Hotplug - status.connected 1
      > bcm7335: hotplug_callback():
      > Hotplug - connecting HDMI to display 0xe
      > [GP]:brcm_pwm_init
      >
      > brcm_demux_init: $Id: bcm7335_demux.c,v 0.6 $
      > DVB: registering adapter 0 frontend 0 (BCM7346 FE)...
      > DVB: registering adapter 0 frontend 0 (BC
      > [MPVR]: >> misc_pvr_init
      > BKN
      > BKNI_Malloc(linuxkernel) top users:
      >
      > 694, 33312, portinginterface/vdc/src/common/bvdc_bufferheap
      > 561, 127284, ../BSEAV/lib/utils/balloc.c
      > 536, 21440, ../ma
      > 366, 43920, magnum/
      > input: dreambox advanced remote control
      > [LCD]: registered
      > [CI]: registered ci0
      > [DFP]: registered dbox fp
      > [DF
      >
      > [SC]: registered sci0
      > [SC]: registered sci1
      > sys
      > system_time_set wakeup mod
      > fpga update driver loaded
      > ud
      > Bluetooth: Core ver 2.16
      > NET: Registere
      > Bluetooth: HCI device and connection manager initial
      > Bluetooth: HCI socket layer initiali
      > Bluetooth: L2CAP socket layer initialized
      > Bluet
      > usbcore: registered new
      > kjournald starting. Commit interval 5 seconds
      > EXT3-fs (sda1): warning: maximal mount count
      > EXT3-fs (sda1): using internal journal
      > EXT3-fs (sda1): mounted filesystem
      > __clk_enable: network [1]
      > __clk_ena
      > bcm40nm_pm_genet_enable 00
      > ADDRCONF(
      > eth0: Link up, 100 Mbps Full Duplex
      > ADDRCONF(NE
      > [LCD]: unknown cmd 0x1015
      > [CI]: CI in
      >
      > eth0: no IPv6 routers present
      > FE tune
      > dmxdev: buf
      > dmxdev: buffer overflow
      > FE tune
      > dm
      > !!!pes_cb idx<0
      > dmxdev: buffer overf
      > warning: `vsftpd' uses 32-bit capabilities (legacy sup
      -sh: syntax error: unexpected ";("
      root@vusolo2:~# dmxdev: buffer overflow
      -sh: dmxdev:: not found
      root@vusolo2:~# dmxdev: b
      -sh: dmxdev:: not found
      root@vusolo2:~# dmxdev: buffer overflow
      -sh: dmxdev:: not found
      root@vusolo2:~# usb 8-1: USB disconnect,
      -sh: usb: not found
      root@vusolo2:~# FE tune
      -sh: FE: not found
      root@vusolo2:~# FE tune
      -sh: FE: not found
      root@vusolo2:~# FE tune
      -sh: FE: not found
      root@vusolo2:~# FE tune
      -sh: FE: not found
      root@vusolo2:~# FE tune
      -sh: FE: not found
      root@vusolo2:~# FE tune
      -sh: FE: not found
      root@vusolo2:~# FE tune
      -sh: FE: not found
      root@vusolo2:~# FE tune
      -sh: FE: not found
      root@vusolo2:~# FE tune
      -sh: FE: not found
      root@vusolo2:~# FE
      -sh: FE: not found
      root@vusolo2:~# FE tune
      -sh: FE: not found
      root@vusolo2:~# FE tune
      -sh: FE: not found
      root@vusolo2:~# F
      -sh: F: not found
      root@vusolo2:~# FE tune
      -sh: FE: not found
      root@vusolo2:~# usb 8-1: new f
      -sh: usb: not found
      root@vusolo2:~# root@vusolo2:~#
      -sh: root@vusolo2:~#: not found
      root@vusolo2:~# root@vusolo2:~# FE tune
      -sh: root@vusolo2:~#: not found
      root@vusolo2:~#


      Im Protokoll finden sich Angabe zu Bluetooth, die mir allerdings nichts "sagen". Mir ist zudem nicht klar, welche Kernel-Module (es sind standardmäßig BT-Module) installiert werden müssen.
      Für Ratschläge und Hinweise wäre ich sehr dankbar.

      Tekki

      Dieser Beitrag wurde bereits 4 mal editiert, zuletzt von tekki ()

    • RE: Hilfe bei der Installation einer Bluetooth-Tastatur

      OT:
      Tip:

      füge doch bitte die spoiler Funktion ein, dann tut der Finger beim scrollen nicht so weh
      und man kann die Frage unten schneller lesen ;)

      Quellcode

      1. [spoiler]
      3. text
      5. [/spoiler]


      Danke
      Fragen in der Shoutbox?
      Goethe sagte mal: ... auch ist das Suchen und Irren gut, denn durch Suchen und Irren lernt man...
      give it a chance!