Bluetooth мышка
darvin11 23 июля, 2009 - 17:11
Читал howto, никак не могу настроить
hcitool мышку находит, но не подключает
hcitool info 00:07:61:81:3D:56 |16:06| Requesting information ... BD Address: 00:07:61:81:3D:56 Device Name: Bluetooth Travel Mouse LMP Version: 1.2 (0x2) LMP Subversion: 0x545 Manufacturer: Cambridge Silicon Radio (10) Features: 0xfc 0xff 0x0f 0x00 0x08 0x08 0x00 0x00 <encryption> <slot offset> <timing accuracy> <role switch> <hold mode> <sniff mode> <park state> <RSSI> <channel quality> <SCO link> <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme> <power control> <transparent SCO> ~:$sudo hcitool cc 00:07:61:81:3D:56 |16:06| ~:$sudo hcitool con |16:08| Connections: <AFH cap. slave> <AFH cap. master>
соответственно, в ядре видимо все включено
не нашел описания конфигов, попробовал такой написать файлик:
~:$cat /etc/bluetooth/input.conf |16:08| # Configuration file for the input service # This section contains options which are not specific to any # particular interface [General] # Set idle timeout (in minutes) before the connection will # be disconnect (defaults to 0 for no timeout) #IdleTimeout=30 Bind=yes Device=00:07:61:81:3D:56 ~:$cat /etc/bluetooth/main.conf |16:09| [General] # List of plugins that should not be loaded on bluetoothd startup #DisablePlugins = network,input # Default adaper name # %h - substituted for hostname # %d - substituted for adapter id Name = %h-%d # Default device class. Only the major and minor device class bits are # considered. Class = 0x000100 # How long to stay in discoverable mode before going back to non-discoverable # The value is in seconds. Default is 180, i.e. 3 minutes. # 0 = disable timer, i.e. stay discoverable forever DiscoverableTimeout = 0 # How long to stay in pairable mode before going back to non-discoverable # The value is in seconds. Default is 0. # 0 = disable timer, i.e. stay pairable forever PairableTimeout = 0 # Use some other page timeout than the controller default one # which is 16384 (10 seconds). PageTimeout = 8192 # Discover scheduler interval used in Adapter.DiscoverDevices # The value is in seconds. Defaults is 0 to use controller scheduler. DiscoverSchedulerInterval = 0 # What value should be assumed for the adapter Powered property when # SetProperty(Powered, ...) hasn't been called yet. Defaults to true InitiallyPowered = true # Remember the previously stored Powered state when initializing adapters RememberPowered = true # Use vendor, product and version information for DID profile support. # The values are separated by ":" and VID, PID and version. #DeviceID = 1234:5678:abcd # Do reverse service discovery for previously unknown devices that connect to # us. This option is really only needed for qualification since the BITE tester # doesn't like us doing reverse SDP for some test cases (though there could in # theory be other useful purposes for this too). Defaults to true. ReverseServiceDiscovery = true ~:$cat /etc/conf.d/bluetooth |16:10| # Bluetooth configuraton file # Run hid2hci (allowed values are "true" and "false") HID2HCI_ENABLE=false # Bind rfcomm devices (allowed values are "true" and "false") RFCOMM_ENABLE=false # Config file for rfcomm RFCOMM_CONFIG="/etc/bluetooth/rfcomm.conf"
зы, в иксах какой протокол к ней указывать и устройство, если все-таки подключу?
»
- Для комментирования войдите или зарегистрируйтесь
подключил я значит мышку, в
подключил я значит мышку, в cat /dev/input/mouse1 выдает когда ее дергаешь... как ее дальше под хорг через hal?
Покури тему evdev.
Покури тему evdev. http://209.85.129.132/search?q=cache:AEprcBPXU08J:ru.gentoo-wiki.com/wiki/Xorg_%D1%83%D1%81%D1%82%D1%80%D0%BE%D0%B9%D1%81%D1%82%D0%B2%D0%B0_%D0%B2%D0%B2%D0%BE%D0%B4%D0%B0_%D1%87%D0%B5%D1%80%D0%B5%D0%B7_hal+gentoo+mouse+evdev+hal&hl=ru&gl=ru&strip=1
Секта Черных Пингвинов
http://blackpenguins.ru
настроил я как там написанно,
настроил я как там написанно, клавиатура и тачпад работают как надо теперь (в xorg.conf не прописанны, прописанны в хале)
теперь снова проблема в bluetooth
поставил я значит перед этим kbluetooth4, он у меня заработал. перезагрузился - перестал работать, выдает такую ошибку:
PS. проблема была в том что /etc/init.d/bluetooth не был запущен ) исправил