Problem with Logitech Mx900 again - psm strikes again - SOLVED

[Maksim Yevmenkin]

Vladimir,

[...]

>>so, could you please double check your /etc/bluetooth/bthidd.conf file 
>>and make sure bthidd(8) uses the correct config.
> 
> It strikes again. I was pretty sure, that bug was fixed last time. 
> Manual changing psm in bthidd.conf fix my problem.

good

> I remember I've tested code with your patch and even send you ok notice
> (PR misc/76107).
> 
> I was not touch bthidd.conf because I was pretty sure that it has valid
> values.
> I am sure that trying to make mouse work I've done
> # bthidcontrol -a mouse > /etc/bluetooth/bthidd.conf.tmp
> # diff /etc/bluetooth/bthidd.conf{,.tmp}
> 
> and got no difference.
> 
> But it strikes again.

no problem, dont worry about it :)

> Ok, I will try all cycle from scratch.
> 
> Just reconnect mouse to cradle - Ok
> Then reset mouse and run bthidcontrol query -> psm 0x13
> Then reconnect directly to bthidd - Ok

great

> I have only idea why it happens - I have used very old binary of
> bthidcontrol installed while compare/rebuild bthidd.conf (with bug,
> unfortunately it was just overwritten by fresh build).
> /probably one should attach build+install of bthid* binaries to world ?/

well, bthidd(8) is not complete yet. it missing support for 
keyboard/keypad. i'm working on the kbdmux now and when i'm done i will 
add missing support and connect it to the build. bthidcontrol(8) could 
be added to the build, but it is not very useful without bthidd(8).

> Looks like there was hardware glitch (when win and freebsd connection
> was broken over night, probably out of power in battaries, it was)
> After that I've tried to restore mouse and replace bthidd.conf with
> broken version and it stop working.

could be, but it still does not explain why it did not work with windows.

>>i suspect there might be another bug in bthidd(8), so if you could 
>>please try to run bthidd(8) under debugger and try to examine internal 
>>configuration structures after bthidd(8) parses the config file.
> 
> Looks like bthidd is ok in this case.

good

>>i also attached a patch that renames global variable to avoid name 
>>collision with the local variables. i do not expect it to fix your 
>>problem, but please try it anyway.
> 
> I have tried - it works ok (without it too), only issue - first chunk of patch - should be removed before apply.

thanks. i think i will commit it after freeze is over. this is something 
that needs to be fixed anyway.

>>>It looks like hardware problem for me (over one night both OSes stop
>>>stop seen mouse) no reset was initiated, cradle was far-far away from
>>>place where it happens. But, probably there is software solution.
>>
>>lets not blame the hardware just yet :)
> 
> Yes, it was software.

it usually is :)

> But still It is not clean for me two issues:
>  a) why mouse stops work under WinXP (it works before, and stop to work at the same night as under freebsd)
>  b) why it happens (no suspend/hibernate was initiated)

cant help you here, sorry :) must have been sun flare or something :)

thanks,
max