| *** alin has quit IRC | 00:30 | |
| *** alin has joined #sailfishos-porters | 08:16 | |
| *** lbt has quit IRC | 09:24 | |
| *** lbt has joined #sailfishos-porters | 09:24 | |
| *** lbt has quit IRC | 09:24 | |
| *** lbt has joined #sailfishos-porters | 09:24 | |
| *** alterego_ has joined #sailfishos-porters | 11:27 | |
| *** alin has quit IRC | 11:35 | |
| *** alterego_ has quit IRC | 11:36 | |
| *** alin has joined #sailfishos-porters | 11:37 | |
| * situ is still wondering about permission error with rtc | 11:54 | |
| situ | Could someone check if this condtion is true on mako https://github.com/mer-hybris/lge-kernel-mako/blob/hybris-10.1/drivers/rtc/qpnp-rtc.c#L524 ? | 12:01 |
|---|---|---|
| stephg | situ: how do you mean? | 12:13 |
| situ | stephg: Modify the kernel source to put debug statement to check value of rtc_dd->rtc_write_enable, recompile the kernel and boot with it.Then check the dmesg logs. | 12:14 |
| stephg | ah | 12:14 |
| situ | It may be possible dsme lacks CAP_SYS_TIME capability. | 12:15 |
| stephg | that sounds plausible | 12:17 |
| *** lbt has quit IRC | 12:22 | |
| *** s5pik3 has joined #sailfishos-porters | 12:23 | |
| situ | dsme is run as root. Does root user need to have capabilities to set time ? | 12:33 |
| sledges | situ: i'll rebuild the kernel | 12:36 |
| situ | sledges: It might be possible that time is being set through https://github.com/mer-hybris/android_kernel_lge_hammerhead/blob/hybris-11.0/drivers/rtc/interface.c#L67 | 12:38 |
| situ | on mako | 12:38 |
| situ | If rtc->ops->set_time is not set. | 12:39 |
| *** lbt has joined #sailfishos-porters | 12:49 | |
| *** lbt has quit IRC | 12:49 | |
| *** lbt has joined #sailfishos-porters | 12:49 | |
| sledges | will see | 12:53 |
| *** ernesti has joined #sailfishos-porters | 13:15 | |
| s5pik3 | The question was probably ask before but, is there anybody who knows how to build or send me a link to build the nexus 5 image of sailfish ? :) | 13:33 |
| sledges | situ: none of those codepaths are taken: https://pastee.org/5fbdx (pardon the puns :P) | 13:40 |
| situ | sledges: dmesg output ? | 13:46 |
| sledges | at the bottom | 13:47 |
| situ | It's using other driver. | 13:47 |
| sledges | s5pik3: hadk will be out soon and you will be able to join this crew of ours full time :) | 13:47 |
| sledges | situ: right | 13:48 |
| sledges | not rtc? | 13:48 |
| sledges | or not qpnp | 13:48 |
| sledges | (interface does not output anything too mind) | 13:48 |
| sledges | interface.c | 13:48 |
| situ | https://github.com/mer-hybris/android_kernel_lge_hammerhead/blob/hybris-11.0/drivers/rtc/rtc-pm8xxx.c | 13:48 |
| sledges | you gave me drivers/rtc/qpnp-rtc.c#L524 | 13:48 |
| situ | sledges: That's what is used on hammerhead | 13:48 |
| sledges | ? and rtc-pm8xxx.c | 13:49 |
| situ | sledges: I thought same is being used on mako. | 13:49 |
| sledges | but i put code into interface.c - i thought that was pretty driver-independent | 13:50 |
| situ | sledges: fulll dmesg output ? | 13:51 |
| sledges | sec | 13:51 |
| situ | sledges: wait are you sure dev_info will work ? I think I used dev_err | 13:51 |
| sledges | i used dev_err too - same | 13:52 |
| sledges | then saw dev_info is used for the visible lines | 13:52 |
| sledges | (see the "setting system c*..." line :D) | 13:52 |
| sledges | situ: https://pastee.org/9x2jh | 13:54 |
| sledges | full dmesg ^ | 13:54 |
| s5pik3 | sledges: I know and I'm very impatient to see this hadk, but there some ressources on the repos (https://github.com/mer-hybris) for the n5 and I want to try to build the image from there but the instructions I found was not clear ^^ | 13:54 |
| s5pik3 | sledges: but thanks :) | 13:54 |
| sledges | s5pik3: understandable :) | 13:55 |
| situ | s5pik3: You will be able to run Sailfish on N5 soon. Please bear with us, everybody who is working on it wants a public release ASAP. | 13:56 |
| sledges | s5pik3: trust me, not long now | 13:56 |
| s5pik3 | sledges: well on xda there is an image for the n5 but it's an older version of sailfish and nobody has build a newer so I want to do this myself for my personal knowledge :) | 13:56 |
| sledges | s5pik3: completely understandable, and your eagerness is just helping to get people's asses kicked ;) | 13:58 |
| s5pik3 | sledges: thanks you man, I know that the persons who's working on it do their best. I'm just want to understand for my personnal knowledge, but you guys doing a impressive work :) | 14:00 |
| sledges | cheers, and don't forget, we "do it together" ;) | 14:01 |
| situ | sledges: Those double quotes looks fishy, let's remove them :P | 14:02 |
| s5pik3 | ahah right ! | 14:02 |
| sledges | situ: yes, very -fishy- :D | 14:03 |
| situ | sledges: May rtc_set_time is never excuted | 14:04 |
| situ | where you had put debug statements | 14:04 |
| situ | Let's trying putting some debug statements in https://github.com/mer-hybris/lge-kernel-mako/blob/hybris-10.1/drivers/rtc/rtc-pm8xxx.c | 14:05 |
| situ | sledges: This line https://github.com/mer-hybris/lge-kernel-mako/blob/hybris-10.1/drivers/rtc/rtc-pm8xxx.c#L475 | 14:06 |
| sledges | ah, you pasted rtc-pm8xxx from hammerhead repo earlier and i got baffled a bit ;p | 14:10 |
| situ | sledges: I get confused while browsing between both repositories :P | 14:11 |
| sledges | ofc now it's obvious why none of rtc*.o files got rebuilt :D | 14:12 |
| sledges | good to undust kernel dev every so often ^_^ | 14:12 |
| *** kimmoli has joined #sailfishos-porters | 14:24 | |
| *** kimmoli has left #sailfishos-porters | 14:24 | |
| situ | sledges: Would it be possible for you to test again ? | 14:29 |
| *** ernesti has quit IRC | 14:33 | |
| sledges | <6>[ 1.391088] rtc-pm8xxx rtc-pm8xxx: !!! rtc_write_enable: 1 | 14:35 |
| sledges | situ: ^ | 14:35 |
| *** Nightmare__ has joined #sailfishos-porters | 14:36 | |
| *** Nightmare__ has left #sailfishos-porters | 14:36 | |
| situ | sledges: This means https://github.com/mer-hybris/lge-kernel-mako/blob/hybris-10.1/drivers/rtc/rtc-pm8xxx.c#L104 is execute and is succesful. | 14:41 |
| situ | sledges: Do applications running as root need capabilities too ? | 14:43 |
| * sledges shrugs | 14:45 | |
| situ | " To set the RTC's time the process must be privileged (i.e., have the CAP_SYS_TIME capability)." | 14:48 |
| situ | Stskeeps: ^ | 14:48 |
| sledges | why wouldn't dsme have those? (as they work on mako) | 15:10 |
| situ | sledges: probably the driver never checks for capabilities. | 15:10 |
| sledges | whereas n5 does? | 15:10 |
| situ | Could be, just guessing. | 15:11 |
| situ | sledges: Here is the irony, I disabled dsme on my device and it shows correct time now. | 15:14 |
| sledges | yh | 15:14 |
| sledges | :) | 15:14 |
| sledges | the original problem was that it fails intermittently? | 15:14 |
| sledges | also, no output on mako for sh-3.2# getcap /usr/sbin/dsme-server | 15:15 |
| situ | same here | 15:15 |
| situ | sledges: See this http://pastie.org/9396668 | 15:16 |
| situ | Probably dsme shows time in rtc if ioctl fails. | 15:16 |
| sledges | do you get error in dmesg when running hwclock ? | 15:20 |
| situ | sledges: No. | 15:21 |
| situ | strace -s 2048 hwclock --systohc --utc http://pastie.org/9396691 | 15:27 |
| situ | Right now running on kernel which has rtc_write_enable = false. | 15:29 |
| sledges | ok, means i could try to disable dsme on mako too | 15:34 |
| situ | From where system clock picks up time ? | 15:40 |
| *** s5pik3 has quit IRC | 16:29 | |
| *** alin has quit IRC | 19:29 | |
| *** alin has joined #sailfishos-porters | 20:34 | |
| *** alin has joined #sailfishos-porters | 20:34 | |
| *** alin has quit IRC | 22:45 | |
| *** alin has joined #sailfishos-porters | 22:46 | |
| *** alin has joined #sailfishos-porters | 22:46 | |
| dwangoAC | window 15 | 23:16 |
| dwangoAC | Heh - well, didn't mean to do that, but yeah, I have at least 15 windows open :) | 23:16 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!