Sunday, 2022-12-18

T42<elros34> if you have "this requirement cannot be provided" and nothing else then try changing package you are installing in ks file to that patterns-sailfish-device-adaptation-* and try again, this should print missing package01:38
T42<edp_17> @elros34 : I've managed to upgrade packages on device and also build an image. (I had to replace the bluetooth-rfkill-event-hciattach with  bluetooth-rfkill-event and build that on OBS.)01:42
T42<edp_17> But now BT still doesn't work and interferes with wifi. (when I turn bt on, it turns wifi off)01:43
T42<edp_17> brcm_patchram_plus is not started when turn BT on and I got the following in journal:01:44
T42<edp_17> bluetooth_rfkill_event[]: main(bluetooth_rfkill_event.c:1228): Unknown rfkill switch 001:44
T42<edp_17> Log when I restart bluetooth service :
T42<elros34> and you did remember to make device specific modification to bluetooth-rfkil-event?01:53
T42<edp_17> Yes, I did this :
T42<elros34> then check rfkill-event logs not bluetoothd01:58
T42<edp_17> When restarting bluetooth-rfkill-event service :
T42<edp_17> This name has lots of spaces. Isn't this a problem? 'bcm4335 Bluetooth02:04
T42<edp_17>                                                         '02:04
T42<elros34> for sure it doesn't match02:05
T42<edp_17> How do you mean?02:07
T42<elros34> this is false:
T42<elros34> do you see bcm4335 when running strings on bluetooth-rfkil-name?02:10
T42<elros34> on binary02:10
T42<edp_17> Sorry, I don't understand what you wrote.02:11
T42<elros34> run 'strings /usr/bin(or sbin?)/bluetooth-rfkill-name | grep bcm4335'02:12
T42<edp_17> Should I have a bluetooth-rfkill-name binary?02:14
T42<elros34> how can you not have it, you just restarted it? maybe tnhe name is slightly different I do not remember excatly02:15
T42<edp_17> This gives me a blank line: /usr/sbin/bluetooth_rfkill_event | grep bcm433502:16
T42<elros34> so most likely you do not have this change you linked. This issue keeps coming back so you should really make it configurable in some settings file instead in sources02:17
T42<edp_17> Okay. Do you have an example?02:18
T42<edp_17> I don't get it why it is not there if I have this change:
T42<elros34> no, \n at the and makes it little more complicated. Se if grep bcm43 returns old rfkill name02:19
T42<edp_17> This also gives me a blank line: /usr/sbin/bluetooth_rfkill_event | grep bcm4302:20
T42<elros34> hmm dod you add 'strings' at the beginning?02:20
T42<elros34> do*02:21
T42<edp_17> If I add stings to the beginning, I get : bash: srings: command not found02:22
T42<edp_17> Ok, typo02:23
T42<edp_17> my keyboard is crazy :(02:23
T42<edp_17> Yep, old name is defined still :
T42<edp_17> I need to sleep now. Thanks for your help and good night.02:27
T42<elros34> sure, bye02:28
*** amccarthy is now known as Guest9111:54
*** amccarthy_ is now known as amccarthy11:54
T42<edp_17> Good morning! I don't get it. I've just hardcoded the DEFAULT_CONFIG_FILE and HCIATTACH_TYPE_ID_DEFAULT in bluetooth-rfkill-event and the string still report the default bcm43xx value! 😳12:05
T42<edp_17> Okay, I've figured out why. Ages ago I built bluetooth-rfkill-event locally and there was old binaries that I accidentally pushed to github. In there, probably my change was not there and somehow OBS included that binaries instead of new one compiled from updated source.12:13
T42<edp_17> Now, I've removed the old binaries from github, triggered re-building bluetooth-rfkill-event and when I do a string on it, it reports my driver.12:14
T42<edp_17> However, bt still doesn't work. Turning it on doesn't start brcm_patchram_plus. Plus, when I turn bt off (toggle it twice) it disconnects wifi. :( Later, I'll play more with it.12:33

Generated by 2.17.1 by Marius Gedminas - find it at!