Re: ReMoKo and openSuSE 11
i have the same versions as Claus, and no i never tryed connecting bluetooth mouse or keyboard, thanx alot valerio for your help ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ReMoKo and openSuSE 11
2008/10/1 Claus Christmann <[EMAIL PROTECTED]> > On Wednesday 01 October 2008 07:51:48 am Valerio Valerio wrote: > > Hi, > > > > 2008/10/1 Flyin_bbb8 <[EMAIL PROTECTED]> > > > > > ok i don't know if this might be useful but the line "--> BlueZ input > > > service started" is only showin in the terminal through ssh after i > press > > > the X button > > > > this is the normal behavior, ReMoko stop the input service because use > the > > same channels to send information, on exit ReMoko restore the initial > > conditions of the system. > > The weird thing is that your system try to connect on the psm 1 ( > L2CAP(s): > > Connect req: psm 1 scid 0x0040), and the HID psm are the 17 and 19, which > > version of BlueZ do you have on your system ? > > > > Best regads, > > Sorry for beeing absent on this thread for so long... > > I run into the exact same issues as described so far. > > Here is the data on my bluez installation (standart setup for an openSuSE > 11.0 > install): > > bluez-libs: 3.32-3.2 (Tue 15 Jul 2008 12:36:04 PM EDT) > bluez-utils: 3.32-8.2 (Tue 15 Jul 2008 09:25:35 PM EDT) > > Thanks a lot for your help, Valerio. This should be a bug related to kdebluetooth or some custom changes made by openSuSE on the BlueZ packages. I test kdebluetooth (1.0~beta9~r769275) in my Ubuntu 8.04 and I can pair the device and connect to it without any problem, as you can see in the dump below (lines market with ***), the bluetooth system request connection on the correct psm (17 and 19). Any of you have tried to connect a bluetooth keyboard or a mouse to your system ? ## > HCI Event: Command Status (0x0f) plen 4 > HCI Event: Connect Complete (0x03) plen 11 < ACL data: handle 42 flags 0x02 dlen 10 L2CAP(s): Info req: type 2 < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2 > HCI Event: Number of Completed Packets (0x13) plen 5 > ACL data: handle 42 flags 0x02 dlen 10 L2CAP(s): Info req: type 2 < ACL data: handle 42 flags 0x02 dlen 16 L2CAP(s): Info rsp: type 2 result 0 Extended feature mask 0x > ACL data: handle 42 flags 0x02 dlen 16 L2CAP(s): Info rsp: type 2 result 0 Extended feature mask 0x < ACL data: handle 42 flags 0x02 dlen 12 L2CAP(s): Connect req: psm 17 scid 0x0040 > HCI Event: Number of Completed Packets (0x13) plen 5 > HCI Event: Number of Completed Packets (0x13) plen 5 > HCI Event: Command Status (0x0f) plen 4 > HCI Event: Max Slots Change (0x1b) plen 3 > ACL data: handle 42 flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0 Connection successful < ACL data: handle 42 flags 0x02 dlen 12 L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 0 > HCI Event: Number of Completed Packets (0x13) plen 5 > HCI Event: Command Status (0x0f) plen 4 < HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4 > ACL data: handle 42 flags 0x02 dlen 17 > ACL data: handle 42 flags 0x01 dlen 1 L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4 Success MTU 672 > ACL data: handle 42 flags 0x02 dlen 16 L2CAP(s): Config req: dcid 0x0040 flags 0x00 clen 4 MTU 48 < ACL data: handle 42 flags 0x02 dlen 18 L2CAP(s): Config rsp: scid 0x0040 flags 0x00 result 0 clen 4 Success MTU 48 < ACL data: handle 42 flags 0x02 dlen 12 L2CAP(s): Connect req: psm 19 scid 0x0041 > HCI Event: Number of Completed Packets (0x13) plen 5 > HCI Event: Number of Completed Packets (0x13) plen 5 > HCI Event: Read Remote Supported Features (0x0b) plen 11 > HCI Event: Command Complete (0x0e) plen 6 < HCI Command: Remote Name Request (0x01|0x0019) plen 10 > HCI Event: Command Status (0x0f) plen 4 > ACL data: handle 42 flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0041 result 0 status 0 Connection successful < ACL data: handle 42 flags 0x02 dlen 12 L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 0 > HCI Event: Number of Completed Packets (0x13) plen 5 > ACL data: handle 42 flags 0x02 dlen 18 L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4 Success MTU 672 > ACL data: handle 42 flags 0x02 dlen 16 L2CAP(s): Config req: dcid 0x0041 flags 0x00 clen 4 MTU 48 < ACL data: handle 42 flags 0x02 dlen 18 L2CAP(s): Config rsp: scid 0x0041 flags 0x00 result 0 clen 4 Success MTU 48 > HCI Event: Remote Name Req Complete (0x07) plen 255 > HCI Event: Number of Completed Packets (0x13) plen 5 < ACL data: handle 42 flags 0x02 dlen 14 L2CAP(d): cid 0x0041 len 10 [psm 19] HIDP: Data: Output report < ACL data: handle 42 flags 0x02 dlen 10 L2CAP(d): cid 0x0041 len 6 [psm 19] HIDP: Data: Output report > HCI Event: Number of Completed Packets (0x13) plen 5 > HCI Event: Number of Completed Packets (0x13) plen 5 # Best regards, -- Valério Valério http://
Re: ReMoKo and openSuSE 11
On Wednesday 01 October 2008 07:51:48 am Valerio Valerio wrote: > Hi, > > 2008/10/1 Flyin_bbb8 <[EMAIL PROTECTED]> > > > ok i don't know if this might be useful but the line "--> BlueZ input > > service started" is only showin in the terminal through ssh after i press > > the X button > > this is the normal behavior, ReMoko stop the input service because use the > same channels to send information, on exit ReMoko restore the initial > conditions of the system. > The weird thing is that your system try to connect on the psm 1 ( L2CAP(s): > Connect req: psm 1 scid 0x0040), and the HID psm are the 17 and 19, which > version of BlueZ do you have on your system ? > > Best regads, Sorry for beeing absent on this thread for so long... I run into the exact same issues as described so far. Here is the data on my bluez installation (standart setup for an openSuSE 11.0 install): bluez-libs: 3.32-3.2 (Tue 15 Jul 2008 12:36:04 PM EDT) bluez-utils: 3.32-8.2 (Tue 15 Jul 2008 09:25:35 PM EDT) Thanks a lot for your help, Valerio. Claus -- Claus Christmann Graduate Research Assistant Georgia Institute of Technology 270 Ferst Drive Atlanta, GA 30332-0150, USA http://uav.ae.gatech.edu ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ReMoKo and openSuSE 11
Hi, 2008/10/1 Flyin_bbb8 <[EMAIL PROTECTED]> > ok i don't know if this might be useful but the line "--> BlueZ input > service started" is only showin in the terminal through ssh after i press > the X button > this is the normal behavior, ReMoko stop the input service because use the same channels to send information, on exit ReMoko restore the initial conditions of the system. The weird thing is that your system try to connect on the psm 1 ( L2CAP(s): Connect req: psm 1 scid 0x0040), and the HID psm are the 17 and 19, which version of BlueZ do you have on your system ? Best regads, -- Valério Valério http://www.valeriovalerio.org > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ReMoKo and openSuSE 11
ok i don't know if this might be useful but the line "--> BlueZ input service started" is only showin in the terminal through ssh after i press the X button ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ReMoKo and openSuSE 11
On Sun, Sep 28, 2008 at 3:18 PM, Valerio Valerio <[EMAIL PROTECTED]> wrote: > Hi, > > Can you also provide me the output of ReMoko ? > Sure, here you go, sorry for the delay i was really busy for the last 3 days [EMAIL PROTECTED]:~# DISPLAY=:0 remoko dbus_objectInit... proxy ok interface ok failcount= 0 dbus_objectInit... could not create proxy for org.freesmartphone.ousaged:/org/freesmartphone/Usage org.freedesktop.DBus.Error.ServiceUnknown: The name org.freesmartphone.ousaged was not provided by any .service files failcount= 1 dbus_objectInit... could not create proxy for org.freesmartphone.ousaged:/org/freesmartphone/Usage org.freedesktop.DBus.Error.ServiceUnknown: The name org.freesmartphone.ousaged was not provided by any .service files failcount= 1 dbus_objectInit... off transition to bluetooth_off_alert You are using ASU finished transition to main finished --> BlueZ input service stopped initializing daemon ... initializing listener ... waiting connection ... waiting connection ... waiting connection ... waiting connection ... waiting connection ... 0x0005c0 0x0005c0 Device Class changed to: 0x0005c0 --> BlueZ input service started Connection terminated Killed Exception in thread Thread-2: Traceback (most recent call last): File "/usr/lib/python2.5/threading.py", line 486, in __bootstrap_inner self.run() File "/usr/share/remoko/remoko/remoko_server.py", line 174, in run reply = self.remoko.sock.recv(100) error: (104, 'Connection reset by peer') ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ReMoKo and openSuSE 11
Hi, Can you also provide me the output of ReMoko ? Best regards, -- Valério Valério http://www.valeriovalerio.org 2008/9/28 Flyin_bbb8 <[EMAIL PROTECTED]> > sorry for the third post, here's some hcidumps from both pc and freerunner > while havin remoko on > > # hcidump (from pc) > HCI sniffer - Bluetooth packet analyzer ver 1.41 > device: hci0 snap_len: 1028 filter: 0x > < HCI Command: Create Connection (0x01|0x0005) plen 13 > > HCI Event: Command Status (0x0f) plen 4 > > HCI Event: Connect Complete (0x03) plen 11 > < ACL data: handle 11 flags 0x02 dlen 10 > L2CAP(s): Info req: type 2 > < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2 > > HCI Event: Command Status (0x0f) plen 4 > < HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4 > > HCI Event: Read Remote Supported Features (0x0b) plen 11 > > HCI Event: Command Complete (0x0e) plen 6 > < HCI Command: Remote Name Request (0x01|0x0019) plen 10 > > HCI Event: Command Status (0x0f) plen 4 > > HCI Event: Page Scan Repetition Mode Change (0x20) plen 7 > > HCI Event: Max Slots Change (0x1b) plen 3 > > ACL data: handle 11 flags 0x02 dlen 10 > L2CAP(s): Info req: type 2 > < ACL data: handle 11 flags 0x02 dlen 16 > L2CAP(s): Info rsp: type 2 result 0 > Extended feature mask 0x > > HCI Event: Number of Completed Packets (0x13) plen 5 > > HCI Event: Remote Name Req Complete (0x07) plen 255 > > ACL data: handle 11 flags 0x02 dlen 16 > L2CAP(s): Info rsp: type 2 result 0 > Extended feature mask 0x > < ACL data: handle 11 flags 0x02 dlen 12 > L2CAP(s): Connect req: psm 1 scid 0x0040 > > ACL data: handle 11 flags 0x02 dlen 16 > L2CAP(s): Connect rsp: dcid 0x scid 0x0040 result 2 status 0 > Connection refused - PSM not supported > > HCI Event: Number of Completed Packets (0x13) plen 5 > < HCI Command: Disconnect (0x01|0x0006) plen 3 > > HCI Event: Command Status (0x0f) plen 4 > > HCI Event: Disconn Complete (0x05) plen 4 > > > > hcidump (from freerunner) > HCI sniffer - Bluetooth packet analyzer ver 1.38 > device: hci0 snap_len: 1028 filter: 0x > > HCI Event: Connect Request (0x04) plen 10 > < HCI Command: Accept Connection Request (0x01|0x0009) plen 7 > > HCI Event: Command Status (0x0f) plen 4 > > HCI Event: Connect Complete (0x03) plen 11 > < ACL data: handle 42 flags 0x02 dlen 10 > L2CAP(s): Info req: type 2 > < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2 > > HCI Event: Page Scan Repetition Mode Change (0x20) plen 7 > > HCI Event: Max Slots Change (0x1b) plen 3 > > HCI Event: Command Status (0x0f) plen 4 > > HCI Event: Number of Completed Packets (0x13) plen 5 > > HCI Event: Command Status (0x0f) plen 4 > < HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4 > > HCI Event: Command Complete (0x0e) plen 6 > < HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4 > > HCI Event: Command Status (0x0f) plen 4 > > HCI Event: Connection Packet Type Changed (0x1d) plen 5 > > ACL data: handle 42 flags 0x02 dlen 10 > L2CAP(s): Info req: type 2 > < ACL data: handle 42 flags 0x02 dlen 16 > L2CAP(s): Info rsp: type 2 result 0 > Extended feature mask 0x > > HCI Event: Read Remote Supported Features (0x0b) plen 11 > > ACL data: handle 42 flags 0x02 dlen 16 > L2CAP(s): Info rsp: type 2 result 0 > Extended feature mask 0x > > HCI Event: Number of Completed Packets (0x13) plen 5 > > ACL data: handle 42 flags 0x02 dlen 12 > L2CAP(s): Connect req: psm 1 scid 0x0040 > < ACL data: handle 42 flags 0x02 dlen 16 > L2CAP(s): Connect rsp: dcid 0x scid 0x0040 result 2 status 0 > Connection refused - PSM not supported > > HCI Event: Number of Completed Packets (0x13) plen 5 > > HCI Event: Disconn Complete (0x05) plen 4 > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ReMoKo and openSuSE 11
sorry for the third post, here's some hcidumps from both pc and freerunner while havin remoko on # hcidump (from pc) HCI sniffer - Bluetooth packet analyzer ver 1.41 device: hci0 snap_len: 1028 filter: 0x < HCI Command: Create Connection (0x01|0x0005) plen 13 > HCI Event: Command Status (0x0f) plen 4 > HCI Event: Connect Complete (0x03) plen 11 < ACL data: handle 11 flags 0x02 dlen 10 L2CAP(s): Info req: type 2 < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2 > HCI Event: Command Status (0x0f) plen 4 < HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4 > HCI Event: Read Remote Supported Features (0x0b) plen 11 > HCI Event: Command Complete (0x0e) plen 6 < HCI Command: Remote Name Request (0x01|0x0019) plen 10 > HCI Event: Command Status (0x0f) plen 4 > HCI Event: Page Scan Repetition Mode Change (0x20) plen 7 > HCI Event: Max Slots Change (0x1b) plen 3 > ACL data: handle 11 flags 0x02 dlen 10 L2CAP(s): Info req: type 2 < ACL data: handle 11 flags 0x02 dlen 16 L2CAP(s): Info rsp: type 2 result 0 Extended feature mask 0x > HCI Event: Number of Completed Packets (0x13) plen 5 > HCI Event: Remote Name Req Complete (0x07) plen 255 > ACL data: handle 11 flags 0x02 dlen 16 L2CAP(s): Info rsp: type 2 result 0 Extended feature mask 0x < ACL data: handle 11 flags 0x02 dlen 12 L2CAP(s): Connect req: psm 1 scid 0x0040 > ACL data: handle 11 flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x scid 0x0040 result 2 status 0 Connection refused - PSM not supported > HCI Event: Number of Completed Packets (0x13) plen 5 < HCI Command: Disconnect (0x01|0x0006) plen 3 > HCI Event: Command Status (0x0f) plen 4 > HCI Event: Disconn Complete (0x05) plen 4 hcidump (from freerunner) HCI sniffer - Bluetooth packet analyzer ver 1.38 device: hci0 snap_len: 1028 filter: 0x > HCI Event: Connect Request (0x04) plen 10 < HCI Command: Accept Connection Request (0x01|0x0009) plen 7 > HCI Event: Command Status (0x0f) plen 4 > HCI Event: Connect Complete (0x03) plen 11 < ACL data: handle 42 flags 0x02 dlen 10 L2CAP(s): Info req: type 2 < HCI Command: Read Remote Supported Features (0x01|0x001b) plen 2 > HCI Event: Page Scan Repetition Mode Change (0x20) plen 7 > HCI Event: Max Slots Change (0x1b) plen 3 > HCI Event: Command Status (0x0f) plen 4 > HCI Event: Number of Completed Packets (0x13) plen 5 > HCI Event: Command Status (0x0f) plen 4 < HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4 > HCI Event: Command Complete (0x0e) plen 6 < HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4 > HCI Event: Command Status (0x0f) plen 4 > HCI Event: Connection Packet Type Changed (0x1d) plen 5 > ACL data: handle 42 flags 0x02 dlen 10 L2CAP(s): Info req: type 2 < ACL data: handle 42 flags 0x02 dlen 16 L2CAP(s): Info rsp: type 2 result 0 Extended feature mask 0x > HCI Event: Read Remote Supported Features (0x0b) plen 11 > ACL data: handle 42 flags 0x02 dlen 16 L2CAP(s): Info rsp: type 2 result 0 Extended feature mask 0x > HCI Event: Number of Completed Packets (0x13) plen 5 > ACL data: handle 42 flags 0x02 dlen 12 L2CAP(s): Connect req: psm 1 scid 0x0040 < ACL data: handle 42 flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x scid 0x0040 result 2 status 0 Connection refused - PSM not supported > HCI Event: Number of Completed Packets (0x13) plen 5 > HCI Event: Disconn Complete (0x05) plen 4 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ReMoKo and openSuSE 11
and when i do " hcitool -cc 'mycomputermacadd' " it connects and shows connected on the pc for a second then drops it , not much experience here ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ReMoKo and openSuSE 11
problem is when we go to the this input devices wizard and say add new devices it finds the openmoko bluetooth then press the button setup and it says " Failed to Create input device for 'device' " ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ReMoKo and openSuSE 11
Hi, 2008/9/24 Claus Christmann <[EMAIL PROTECTED]> > Hi, > > I got very excited to learn about ReMoKo, but got frustrated even more that > hidd (the command necessary to bind the Neo to the desktop as a hid device, > see [1]) is not present on openSuSE [2]. > > Before I start looking into that matter I just wanted to check if anybody > got > ReMoKo to cooperate with kinputwizard (the part of kbluetooth in openSuSE > that should do the stuff hidd used to do [3] ...) > > So, anybody any hints? In exchange for answers I would opt in to update the > Wiki with my success story... if your problem is in the paring process, you can change the default pin of the neo in "/etc/bluetooth/hcid.conf" to a valid numeric pin (like or 1234 for e.g), after you pair the device once, you only need to hit connect in the wizard evertime you want to use ReMoko. Best regards, -- Valério Valério http://www.valeriovalerio.org > > Thanks, > > Claus > > [1]:http://wiki.openmoko.org/wiki/ReMoko#Install_Instructions > [2]: > http://forums.opensuse.org/hardware/392726-hidd-not-found-system-suse-11-a.html > [3]:http://en.opensuse.org/Bluetooth/kinputwizard > -- > Claus Christmann > Graduate Research Assistant > > Georgia Institute of Technology > 270 Ferst Drive > Atlanta, GA 30332-0150, USA > > http://uav.ae.gatech.edu > > ___ > Openmoko community mailing list > community@lists.openmoko.org > http://lists.openmoko.org/mailman/listinfo/community > ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
ReMoKo and openSuSE 11
Hi, I got very excited to learn about ReMoKo, but got frustrated even more that hidd (the command necessary to bind the Neo to the desktop as a hid device, see [1]) is not present on openSuSE [2]. Before I start looking into that matter I just wanted to check if anybody got ReMoKo to cooperate with kinputwizard (the part of kbluetooth in openSuSE that should do the stuff hidd used to do [3] ...) So, anybody any hints? In exchange for answers I would opt in to update the Wiki with my success story... Thanks, Claus [1]:http://wiki.openmoko.org/wiki/ReMoko#Install_Instructions [2]:http://forums.opensuse.org/hardware/392726-hidd-not-found-system-suse-11-a.html [3]:http://en.opensuse.org/Bluetooth/kinputwizard -- Claus Christmann Graduate Research Assistant Georgia Institute of Technology 270 Ferst Drive Atlanta, GA 30332-0150, USA http://uav.ae.gatech.edu ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
