Notices


Reply
Thread Tools
Posts: 669 | Thanked: 433 times | Joined on May 2010
#201
Originally Posted by freemangordon View Post
I was redirected to windows live, have no idea why. Anyway thanks.

One more think:

Please confirm that you were able to connect sixaxis controler in case of .noem logs, and not able to connect in case of .em logs, as I see no difference between contents of those files.
yes - at the first time it worked (and there was no dialog popping up), second time it didn't and the dialog popped up - i pressed yes the first time and no in the second and third.
 

The Following User Says Thank You to impeham For This Useful Post:
Posts: 3,074 | Thanked: 12,960 times | Joined on Mar 2010 @ Sofia,Bulgaria
#202
Just one more thing - could you please :

1. execute step 1 and 2 from previous instructions
2. open terminal and write:
lshal > lshal.log.noem

3. execute steps 4,5,6 from previous instructions
4. repeat step 2, but instead of typing .noem type .em at the end of the filename

5. now you should have 2 files in /home/user directory

lshal.noem
lshal.em

6. find a way to put them in a .zip archive
7. attach zip file here
 
Posts: 669 | Thanked: 433 times | Joined on May 2010
#203
Attached - all previous logs are here too.
Attached Files
File Type: zip dmseg_logs.zip (23.0 KB, 93 views)
 

The Following User Says Thank You to impeham For This Useful Post:
Posts: 3,074 | Thanked: 12,960 times | Joined on Mar 2010 @ Sofia,Bulgaria
#204
Originally Posted by impeham View Post
Attached - all previous logs are here too.
First, thanks for all your effort till now.

Could you please execute (as root) following commands in terminal

/opt/usr/bin/btinputplugin disable
stop bluetoothd
start bluetoothd

and check whether you are able to use your DS3 after that. Also check if keyboard/mouse work and report.
 
Posts: 669 | Thanked: 433 times | Joined on May 2010
#205
Originally Posted by freemangordon View Post
First, thanks for all your effort till now.

Could you please execute (as root) following commands in terminal

/opt/usr/bin/btinputplugin disable
stop bluetoothd
start bluetoothd

and check whether you are able to use your DS3 after that. Also check if keyboard/mouse work and report.
After doing this i am able to connect with both the DS3 and the keyboard and they are working very good, but i cannot connect to the mouse - i get connection failed message (the pairing worked but i can't connect to it).
 
Posts: 669 | Thanked: 433 times | Joined on May 2010
#206
i made a test - i removed my keyboard from the bluetooth devices and tried to add it again and couldn't (pairing is ok but connection rejected).
it seems that the stop start made the joystick work only with already paired devices. if i try to add one as new (keyboard or mouse) it fails.
 
Posts: 669 | Thanked: 433 times | Joined on May 2010
#207
Originally Posted by impeham View Post
i made a test - i removed my keyboard from the bluetooth devices and tried to add it again and couldn't (pairing is ok but connection rejected).
it seems that the stop start made the joystick work only with already paired devices. if i try to add one as new (keyboard or mouse) it fails.
ok - next thing i did was to remove extkbd, extmou and the bluetooth package and reinstall extkbd and extmou.
now i was able to pair & connect to both keyboard and mouse.
i executed:
/opt/usr/bin/btinputplugin disable
stop bluetoothd
start bluetoothd

and afterwards i was still able to connect with the keyboard (and the joystick), but not with the mouse (i did not do the pairing again)

I hope this helps

Last edited by impeham; 2011-03-12 at 00:39.
 

The Following User Says Thank You to impeham For This Useful Post:
Posts: 3,074 | Thanked: 12,960 times | Joined on Mar 2010 @ Sofia,Bulgaria
#208
Originally Posted by impeham View Post
ok - next thing i did was to remove extkbd, extmou and the bluetooth package and reinstall extkbd and extmou.
now i was able to pair & connect to both keyboard and mouse.
i executed:
/opt/usr/bin/btinputplugin disable
stop bluetoothd
start bluetoothd

and afterwards i was still able to connect with the keyboard (and the joystick), but not with the mouse (i did not do the pairing again)

I hope this helps
OK, think that I am close, but to confirm that will you please (with extkbd and extmou installed and input plugin enabled, so you can connect mouse and keyboard)

in xterm as root:

1. unzip attached file to /root
2. chmod 755 /root/bluetoothd
3. stop bluetoothd
4. /root/bluetoothd -n
5. try to connect sixaxis

NOTE TO ALL OTHERS - this will not work for you, attached bluetoothd has impeham's sixaxis controller MAC address hardcoded, so it is only for him
Attached Files
File Type: zip bluetoothd.zip (160.1 KB, 90 views)
 
Posts: 669 | Thanked: 433 times | Joined on May 2010
#209
Just tried with your instructions - it doesn't work. the behavior now is exactly as it was at start:
mouse and keyboard can connect, and when joystick tries to, i get the playstation controller found dialog with yes and no which neither works...

i exited from the bluetoothd with Ctrl-C afterwards.

Thanks for the effort
 
Posts: 3,074 | Thanked: 12,960 times | Joined on Mar 2010 @ Sofia,Bulgaria
#210
Can you confirm that BT address of your sixaxis controller is 00:06:F7:08:8E:08
 
Reply

Tags
bluetooth, keyboard

Thread Tools

 
Forum Jump


All times are GMT. The time now is 00:46.