| sicelo | Wizzup: https://github.com/maemo-leste/maemo-leste.github.io/pull/18 | 08:21 |
|---|---|---|
| Wizzup | sicelo: will merge, but won't push out yet | 11:33 |
| Wizzup | since it activates rss feeds from people | 11:34 |
| sicelo | sure :-) | 11:34 |
| buZz | hehe , droid4 bricked itself | 17:10 |
| buZz | as-in , that one superverbose log filled SD card | 17:10 |
| buZz | lets see if emergencyshell is enough to fix it :) | 17:11 |
| buZz | dangit, didnt config root pwd i think | 17:13 |
| buZz | but its not root:toor :/ | 17:13 |
| Wizzup | should be I think | 17:16 |
| buZz | yeah guess i changed it to something i cant remember dangit :P | 17:17 |
| buZz | cardreader time i guess | 17:17 |
| tmlind | buZz: let me know if you see "failed to enable" errors in the beginning of your error log.. | 17:37 |
| tmlind | or something else interesting, the theory right now is spi access fails and pmic access fails | 17:37 |
| Wizzup | tmlind: oh right let me dig my logs now :) | 17:38 |
| Wizzup | heh been almost two weeks since I was supposed to check: | 17:39 |
| Wizzup | # uptime 17:37:47 up 13 days, 17:34, 1 user, load average: 0,87, 0,23, 0,08 | 17:39 |
| Wizzup | tmlind: I don't seem to see these lines, I only have the panel disable/enable | 17:40 |
| Wizzup | I do sometimes see: | 17:42 |
| Wizzup | [1186414.293518] omap-mcbsp 40124000.mcbsp: CLKS: could not clk_get() prcm_fck | 17:42 |
| Wizzup | oh hey: | 17:42 |
| Wizzup | [1074080.898284] abe-clkctrl:0030:0: failed to disable | 17:42 |
| Wizzup | yup so I saw those too before: | 17:43 |
| Wizzup | May 28 09:30:16 localhost kernel: [1364651.545074] abe-clkctrl:0030:0: failed to disable | 17:43 |
| Wizzup | May 30 09:30:23 localhost kernel: [157271.035980] abe-clkctrl:0030:0: failed to disable | 17:43 |
| Wizzup | May 30 16:53:25 localhost kernel: [183853.249938] abe-clkctrl:0030:0: failed to disable | 17:43 |
| uvos | with the old kernel i gues | 17:44 |
| Wizzup | uvos: right | 17:48 |
| Wizzup | uvos: what do you think about n900 dts change for f7/f8 ? | 17:48 |
| Wizzup | to raise/lower volume | 17:49 |
| uvos | Wizzup: i allready mentioned ill implement it next kernel release | 17:49 |
| uvos | its allready in my tree | 17:49 |
| Wizzup | I missed that somehow, sry! | 17:49 |
| uvos | no problem :) | 17:49 |
| Wizzup | ah I see it now | 17:49 |
| uvos | do note that this has some down sides | 17:50 |
| uvos | like it will for instance make non-volume use of the buttons apply to external usb keyboards and bluetooth devices differently | 17:50 |
| uvos | (excepting bluetooth speakers headphones those will continue to work fine (volume only)) | 17:51 |
| Wizzup | are you talking about if/when we would change the hildon key? | 17:51 |
| uvos | yes | 17:51 |
| Wizzup | right | 17:52 |
| uvos | but right now too for xterm | 17:52 |
| uvos | since it reacts to xf86vol* | 17:52 |
| Wizzup | xterm already handles both I think | 17:52 |
| uvos | yes | 17:52 |
| uvos | then again f7 f8 being volume on an external keyboard is really random allready | 17:52 |
| uvos | so idk if this is worse | 17:52 |
| uvos | i really dislike how fremantle handles/ uses the volume buttons | 17:53 |
| uvos | but thats a different storry | 17:53 |
| tmlind | Wizzup: i think those abe-clkctrl errors are harmless, misconfigured source clock | 17:57 |
| tmlind | or device busy while trying to idle if it's a autoidle configured device | 17:58 |
| Wizzup | ok, then I am not sure if I can find the error you're talking about | 17:59 |
| tmlind | ok so nothing interesting in your logs sounds like | 17:59 |
| tmlind | those lcd messages are annoying | 17:59 |
| Wizzup | right | 17:59 |
| uvos | more annoying is the stuttering | 18:00 |
| uvos | :P | 18:00 |
| uvos | the kernel messages are easy to ignore | 18:00 |
| tmlind | which stuttering? | 18:00 |
| Wizzup | I was thinking of restarting for new kernel but maybe since I'm at 13 days I should wait | 18:00 |
| uvos | d4's lcd stutters, looses frames | 18:00 |
| tmlind | yeah and the ants | 18:00 |
| uvos | compeare a bionic side by side | 18:00 |
| uvos | its like butter compeared to d4 | 18:00 |
| tmlind | weird | 18:00 |
| uvos | tmlind: yeah but the pannel dropping frames happens on android too | 18:01 |
| uvos | its a hw bug | 18:01 |
| Wizzup | imo the ants are more strange and sometimes mess up the fonts in tricky ways | 18:01 |
| uvos | the ants are some sw bug | 18:01 |
| tmlind | uvos: oh ok, did not know that | 18:01 |
| tmlind | yeah the ants might be some kind of cache issue | 18:01 |
| buZz | tmlind: you mean in the overflowing log? afaik its icd2.log thats just configured 'extra verbose' by default | 18:02 |
| Wizzup | no that's different buZz | 18:02 |
| Wizzup | you're talking about different things | 18:02 |
| buZz | ah ok, didnt get the question | 18:02 |
| tmlind | buZz: if your device ended up hanging, maybe check your /var/log/messages or syslog | 18:03 |
| buZz | i'm quite sure its because icd2.log is full , which somehow prevents hildon from finishing to start | 18:04 |
| buZz | but i'll let you know | 18:04 |
| uvos | hmm really | 18:08 |
| uvos | when my disk is full i get a popup from xsession to that effect and hildon stars when i click ok | 18:08 |
| uvos | ah the reson is presumably because my /home is on a different partion | 18:10 |
| uvos | (and not full) | 18:10 |
| Wizzup | some parts of icd2 are very verbose every x seconds | 18:10 |
| Wizzup | currently | 18:10 |
| Wizzup | the ofono/modem part | 18:10 |
| uvos | btw | 18:10 |
| uvos | should roaming work | 18:10 |
| uvos | i was in italy recently and could not get mobile data to work via icd2 at all | 18:11 |
| uvos | had to use qmicli | 18:11 |
| uvos | maybe apn issues again? | 18:11 |
| uvos | might be good to know whats failing when root is read only | 18:11 |
| uvos | @buzz | 18:11 |
| buZz | i had functional 3G in luxembourgh on leste | 18:12 |
| buZz | with a dutch sim | 18:12 |
| Wizzup | uvos: well you need to tell ofono to allow roaming | 18:12 |
| uvos | Wizzup: sure yeah i treid that | 18:13 |
| uvos | its probubly the apn thing, ill be in austria soon and will try an repo it | 18:13 |
| uvos | and get logs this time | 18:13 |
| Wizzup | great | 18:16 |
| freemangordon | hi! | 18:31 |
| freemangordon | so, I am not sure I understand that 'volume keys' change | 18:31 |
| freemangordon | still, please, don't do changes that will make BT HF volume keys to change pages in book readers | 18:32 |
| buZz | tmlind: btw in my 'hanging' it doesnt really hang, holding powerbutton still starts powerdown | 18:41 |
| Wizzup | freemangordon: why would pages change in ebooks upon volume raise? | 19:09 |
| uvos | because bluetooth headphones have volume buttons | 19:10 |
| uvos | but they dont | 19:10 |
| uvos | not really | 19:10 |
| freemangordon | Wizzup: what device key would you use to turn pages? | 19:10 |
| uvos | the keys go over alsa | 19:10 |
| uvos | they do also go over evdev | 19:10 |
| uvos | but thats a legacy compat thing | 19:10 |
| uvos | we can just disable it | 19:10 |
| freemangordon | ok | 19:10 |
| Wizzup | freemangordon: I would swipe or press on-screen probably | 19:11 |
| uvos | (this is how pa mangaes to change the volume of the right stream when the vol buttons on bt headphones are pressed) | 19:11 |
| freemangordon | Wizzup: well, RN all book readers I used (on n900) use volume keys to turn pages | 19:11 |
| freemangordon | and that's really convenient | 19:11 |
| uvos | however on a bt keyboard the vol buttons will change the page | 19:12 |
| uvos | but then again on a bt keyboard as is f8 and f9 would change volume | 19:12 |
| uvos | witch is equally wierd | 19:12 |
| freemangordon | right | 19:12 |
| freemangordon | Wizzup: the similar stands for osso-xterm | 19:13 |
| freemangordon | anyway, I already got my answer :) | 19:13 |
| Wizzup | from my pov making n900 act the same as other devices improves the situation | 19:13 |
| Wizzup | this way it will work the same as other devices, volume applet will work, too | 19:13 |
| uvos | i men we could change the other devices to be f8 f9 too, (well except x86 tablets and the like, there it is impossible) | 19:14 |
| Wizzup | all other phones simply map these buttons to vol -/+. so I don't know why we would keep n900 different | 19:14 |
| uvos | *mean | 19:14 |
| Wizzup | it's f7/f8 btw, but yeah | 19:14 |
| freemangordon | Wizzup: I don;t really care if those are f7/f8 or volume keys or whatever | 19:16 |
| freemangordon | as long is we don;t break the UX | 19:16 |
| Wizzup | ok, so in that sense I think we can streamline it to be the volume keys for now | 19:16 |
| maxwelld | folks, my maemo xterm is crashing whe starting. i dont know what i did that started t cause that. restart does not help. | 19:32 |
| maxwelld | i have xterm luckily | 19:33 |
| maxwelld | imean normal xterm not maemo term | 19:33 |
| maxwelld | which runs | 19:33 |
| maxwelld | with very small letters | 19:33 |
| maxwelld | how can i start maemo terminal from xterm to see the prooblem? | 19:34 |
| uvos | osso-xterm | 19:34 |
| uvos | or osso_xterm | 19:34 |
| uvos | maybe | 19:34 |
| maxwelld | oh now it doesnt bring me eve debian app menu | 19:35 |
| maxwelld | very weird | 19:35 |
| uvos | smells hw failure | 19:38 |
| maemish_ | Is there still coming a new release. Have been checking twitter and maemo forum. Twitter the last post is from January promising more news next week. | 20:47 |
| maemish_ | I recall something similar on maemo forum. I don't mind there is not coming news often but if someone says there is coming then people wait. Maybe better not to promise next news soon when posting. | 20:48 |
| uvos | we dont do "releases" just install and update (optionally to devel) | 20:49 |
| uvos | we operate like a rolling distro like arch linux for our packages really | 20:50 |
| maxwelld | so it is a floating point exception | 22:09 |
| maxwelld | i am afraid it is indeed in hw, not just sdcard. | 22:09 |
| maxwelld | 😕 | 22:09 |
| Wizzup | or broken sd card | 22:09 |
| Wizzup | flash a new image to a new or different sd card and check :) | 22:09 |
| maxwelld | uhu, doing that. | 22:10 |
| maxwelld | so i found my old 'adata' sdcard, with it droid works well. | 22:52 |
| maxwelld | but with new sandisk - no. weird. | 22:52 |
| maxwelld | did fsck, but it didn't find anything. | 22:53 |
| maxwelld | so i am thinking what temporary files to delete. | 22:53 |
| maxwelld | i have strace of osso-xterm when it was dying. | 22:53 |
| Wizzup | fsck on ext4 won't show random data corruption | 22:53 |
| Wizzup | for integrity checks you would need a different file system | 22:53 |
| Wizzup | there can also be partial writes after some hang or power failure | 22:53 |
| Wizzup | I don't think it makes sense to try to figure out where the SIGFPE comes from per se | 22:54 |
| maxwelld | anyway this is strace https://bpa.st/WYRF2 | 22:54 |
| maxwelld | i am thinking of fixing the sdcard by removing some temporary files that can be corrupted. | 22:54 |
| maxwelld | some cache files | 22:54 |
| maxwelld | i wonder what can open osso-xterm that it fails to open. | 22:55 |
| Wizzup | from my experience, this is futile, data corruption can cause a million different kind of errors that make no sense | 22:56 |
| Wizzup | like if the instructions data is corrupted, how would you find out | 22:56 |
| Wizzup | you can checksum all the files manually, but again, how much time do you want to invest :) | 22:56 |
| maxwelld | what would you suggest? just to use a new image and migrate my files to it? | 22:57 |
| Wizzup | probably, yes | 22:57 |
| Wizzup | and throw away the broken sd card ;P | 22:57 |
| maxwelld | but... you think it is broken? i am in denial (: it is a new sdcard. (: | 22:58 |
| Wizzup | you can flash a new image to it and see if that works | 22:58 |
| maxwelld | heh, will do that. (: | 22:58 |
| Wizzup | then it might not be, but I've had sd cards fail on my pretty quickly at times | 22:58 |
| maxwelld | interesting that this 'adata' worked for me much more stable and much longer than this 'sandisk'. | 22:58 |
| maxwelld | and it still works. | 22:59 |
| Wizzup | there are also many fake sandisks | 23:01 |
| maxwelld | eh. | 23:02 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!