Bluetooth MSI 6967 & Mandrake 9.2 - problem

[Giger]

Podla tohto postupu http://www.root.cz/clanek/1694 sa snazim rozchodit bluetooth adapter na MDK 9.2.
Cely postup som presne dodrzal ale vysledok je takyto:



A este par vypisov...

[root@localhost root]# afe
Unable to open cache for locking: /root/.bluetooth/devcache
Unable to open cache for locking: /root/.bluetooth/devcache
[root@localhost root]#

[root@localhost root]# btctl
bt0 00:00:00:00:00:00
Flags: DOWN
RX: acl:0 sco:0 event:0 bytes:0 errors:0 dropped:0
TX: acl:0 sco:0 cmd:1 bytes:3 errors:0 dropped:0
Security: [-auth, -encrypt]
Packets: DM1 DH1
Role: allow switch, remain slave

bt1 00:10:dc:ea:3d:4a
Flags: UP DISC CONN
RX: acl:0 sco:0 event:15 bytes:119 errors:0 dropped:0
TX: acl:0 sco:0 cmd:14 bytes:550 errors:0 dropped:0
Security: service pair [-auth, -encrypt]
Packets: DM1 DH1 DM3 DH3 DM5 DH5 HV1 HV2 HV3
Role: allow switch, remain slave

bt1 je moj USB Dongle MSI6967 ale AFE
ho nejak nechce inicializovat (vid. screenshot)
Viete niekto poradit ako to rozchodit?
Vdaka.

Linux Newbie

[lempour]

a neni treba jeste zavest nejaky modul?
pastni sem vypis dmesg, popr. lsmod

[Giger]

a neni treba jeste zavest nejaky modul?
pastni sem vypis dmesg, popr. lsmod

dmesg...

usb-uhci.c: $Revision: 1.275 $ time 23:12:00 Oct 24 2003
usb-uhci.c: High bandwidth mode enabled
PCI: Found IRQ 5 for device 00:07.2
PCI: Sharing IRQ 5 with 00:0b.0
PCI: Sharing IRQ 5 with 00:0d.1
usb-uhci.c: USB UHCI at I/O 0xa000, IRQ 5
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 11 for device 00:0d.0
PCI: Sharing IRQ 11 with 00:13.0
usb-uhci.c: USB UHCI at I/O 0xa800, IRQ 11
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
PCI: Found IRQ 5 for device 00:0d.1
PCI: Sharing IRQ 5 with 00:07.2
PCI: Sharing IRQ 5 with 00:0b.0
usb-uhci.c: USB UHCI at I/O 0xac00, IRQ 5
usb-uhci.c: Detected 2 ports
usb.c: new USB bus registered, assigned bus number 3
hub.c: USB hub found
hub.c: 2 ports detected
usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
PCI: Found IRQ 10 for device 00:0d.2
ehci_hcd 00:0d.2: VIA Technologies, Inc. USB 2.0
ehci_hcd 00:0d.2: irq 10, pci mem d0a94000
usb.c: new USB bus registered, assigned bus number 4
ehci_hcd 00:0d.2: USB 2.0 enabled, EHCI 0.95, driver 2003-Jun-19/2.4
hub.c: USB hub found
hub.c: 4 ports detected
usbdevfs: remount parameter error
hub.c: new USB device 00:07.2-2, assigned address 2
usb.c: USB device 2 (vend/prod 0xdb0/0x1967) is not claimed by any active driver.
EXT3 FS 2.4-0.9.19, 19 August 2002 on ide3(34,1), internal journal
Adding Swap: 506008k swap-space (priority -1)
BlueZ Core ver 2.3 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
BlueZ HCI USB driver ver 2.4 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <maxk@qualcomm.com>
usb.c: registered new driver hci_usb
hdc: attached ide-scsi driver.

[Gargamel]

Noooo... affix sem taky jednou zkousel doma na jakymsi USB BlueTooth adapteru (noname) a taky to neslapalo. Nevim jestli to oficialne MSI podporuje, ale zkus zabrowsit na tech jejich strankach a podivat se jestli to je vubec podporovany.

[lempour]

o bluetooth na linuxu toho moc nevim, ale podle informaci existuji 3 implementace bluetooth softwaroveho rozhrani: BlueZ, Affix a openBT. Podle vseho ty pouzivas BlueZ (viz dmesg), kterej byl driv v jadre a affixovy GUI s nim neumi pracovat. Ale nechci kecat, mozna vic napovi lsmod a pak modinfo nazev_modulu, kterej obsluhuje ten tvuj adapter. btw..ten btctl je soucast affixu a zda se mi divny ze by komunikoval se zarizenim pomoci Bluez driveru. snad to aspon neco napovi, nemam bohuzel zadny BT zarizeni abych to vyzkousel sam.

[Giger]

o bluetooth na linuxu toho moc nevim, ale podle informaci existuji 3 implementace bluetooth softwaroveho rozhrani: BlueZ, Affix a openBT. Podle vseho ty pouzivas BlueZ (viz dmesg), kterej byl driv v jadre a affixovy GUI s nim neumi pracovat. Ale nechci kecat, mozna vic napovi lsmod a pak modinfo nazev_modulu, kterej obsluhuje ten tvuj adapter. btw..ten btctl je soucast affixu a zda se mi divny ze by komunikoval se zarizenim pomoci Bluez driveru. snad to aspon neco napovi, nemam bohuzel zadny BT zarizeni abych to vyzkousel sam.

Vies z tohoto nieco zistit...?

...
hci_usb 9560 0 (unused)
bluez 38276 1 [hci_usb]
ehci-hcd 19212 0 (unused)
usb-uhci 25136 0 (unused)
usbcore 74988 1 [hci_usb ehci-hcd usb-uhci]
rtc 9004 0 (autoclean)
...
[root@localhost home]# modinfo bluez
filename: /lib/modules/2.4.22-21mdk/kernel/net/bluetooth/bluez.o.gz
description: "BlueZ Core ver 2.3"
author: "Maxim Krasnyansky <maxk@qualcomm.com>"
license: "GPL"
...
[root@localhost home]# modinfo hci_usb
filename: /lib/modules/2.4.22-21mdk/kernel/drivers/bluetooth/hci_usb.o.gz
description: "BlueZ HCI USB driver ver 2.4"
author: "Maxim Krasnyansky <maxk@qualcomm.com>"
license: "GPL"

Uz mi nejde spustit ani to Afe:
[root@localhost home]# afe
Unable to open cache for locking: /root/.bluetooth/devcache
Segmentation fault

[lempour]

tak...podle navodu by ses mel napred zbavit BlueZ driveru (pokud jsou napevno zakompilovane v jadre, je treba je napred vyhodit a prekompilovat jadro, moduly staci smazat a spustit "depmod -a", + zakomentovat prislusne radky v /etc/modules.conf)a utilit a mas zkompilovane affix moduly. Mely by to byt tyto: affix, affix_pan, affix_rfcomm,affix_uart, affix_usb.

btw..to s tim btctl jsem zrejme kecal, bude to nejspis takova obecna utilita pro vsechny spolecne s btsrv

pak se zavedou ty moduly standardne prikazem modprobe, pripadne nejaky polozky v /etc/modules.conf aby se zavedly automaticky pokud bude jadro pozadovat pristup na bluetooth, melo by to byt popsane tu:
http://affix.sourceforge.net/affix-doc/index.html

[Gargamel]

Co treba tohle
http://www.abclinuxu.cz/hardware/ViewRelation?rid=50431

[lempour]

ja sem myslel ze Giger chce ten affix. Nebo ti to je jedno, gigere?

[Giger]

ja sem myslel ze Giger chce ten affix. Nebo ti to je jedno, gigere?

Tak nakoniec som to rozchodil cez BlueZ podla toho ABCLinuxu.
Ale az na jednu vec: nejak mi nefunguje rfcomm. Scan,inq,
ping - vsetko funguje, mobil najde comp, comp najde mobil ale neviem
presne ako pouzivat ten rfcomm.
Ten Affix ma sice graf. nadstavbu ale s BlueZ to slapalo hned.

[Giger]

Ten rfcoom mi stale nefunguje:

[root@localhost /]# rfcomm 0 00:10C:EA:3D:4A
Can't open RFCOMM control socket: No such file or directory

Kernel mam 2.4.22.
Utility pre BlueZ som stiahol z http://www.bluez.org/
Vsetky ostatne prikazy funguju.
Heeeelp...