|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Hardware Questions about drivers, peripheral cabling, configuration |
![]() |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Yes, to tell the truth, I cannot get the device to be trusted either. I have got to run the "dbus-send" command upon every reboot. I need to eventually put together a BASH script that will pull the device path from /var/log/messages and run the "dbus-send" command automatically, but I have been procrastinating, in hopes this issue will be resolved with an official openSUSE patch. For now, my wired keyboard remains connected in order to run the command every morning!
|
|
|||
|
Arrghhh.. this is too much pain for a tiny mouse...
This why I love linux 80% of the time and hate it the other 20%. Simple hardware can be a pain in the arse!
|
|
|||
|
silalaval schrieb:
> Arrghhh.. this is too much pain for a tiny mouse... > > This why I love linux 80% of the time and hate it the other 20%. > > Simple hardware can be a pain in the arse! ![]() Bluetooth is not "simple hardware". It is extremely complex. Small surprise it isn't working every time. More of a surprise it works as often as it does. |
|
|||
|
It may be complex, but it is not a new technology (formally specified in 1998), it is an open standard, and it is very popular. A functional Bluetooth implementation is a requirement for a modern desktop operating system.
|
|
|||
|
matthewcraig schrieb:
> Tilman Schmidt;1918738 Wrote: >> Bluetooth is not "simple hardware". It is extremely complex > > It may be complex, but it is not a new technology (formally specified > in 1998), it is an open standard, and it is very popular. A functional > Bluetooth implementation is a requirement for a modern desktop operating > system. Absolutely agree. I was just responding to silalaval's rant about "simple hardware" not working. Happy new year T. |
|
|||
|
Code:
nelsonlye@linux-s0ab:~/Desktop> ./simple-agent hci0 00:07:61:D4:B4:DE Creating device failed: org.bluez.Error.AlreadyExists: Bonding already exists Hi I have this problem. After I had restart my PC....... |
|
|||
|
I'd like to use the steps from "HOWTO Bluetooth Apple Keyboard (aluminum model)" with an other bluetooth device, i.e. with a mobile internet connection. With some older SuSe I used
pand --connect <address> --service NAP to pair with my mobile and then was asked by kbluetooth (?) for the PIN. How can I do this with above descritption (or any other way with SuSe 11.1)? I think at least the "org.bluez.Input.Connect" in the dbus-send command has to be changed? |
|
|||
|
openSUSE 10.x thru 11.0 never failed to detect and set up my Kensington Bluetooth Mouse on a Thinkpad T43. The combo worked so well I guess it is time to do a retrograde back to 11.0 or maybe try out that new shiny sidux 2008-4 DVD that's working so well on my main box.
This is a big disappointment! |
|
|||
|
Hi all, I have some problem...is for the TRUST part...
Code:
linux-0wpl:/home/nelsonlye/Documents # ./test-device.pl trusted 00:07:61:D4:B4:DE yes bash: ./test-device.pl: No such file or directory |
|
|||
|
Hi,
I'm using the simple-agent script and it asks for a PIN. But what is it??? I'm trying to connect a Microsoft (sorry, please don't ban me) Intellimouse Explorer for Bluetooth and it does not have any PIN's or passkeys... What am I supposed to enter? Please help... Thanks! |
![]() |
|
| Bookmarks |
| Tags |
| 11.1, apple keyboard bluetooth, bluetooth, kde, solution |
| Thread Tools | |
| Display Modes | |
|
|