System_Error has quit [Remote host closed the connection]
joerg has quit [Ping timeout: 272 seconds]
joerg has joined #maemo-leste
Kryder has joined #maemo-leste
ceene has joined #maemo-leste
pere has joined #maemo-leste
Livio has joined #maemo-leste
akossh has joined #maemo-leste
Wikiwide has quit [Remote host closed the connection]
Wikiwide has joined #maemo-leste
pere has quit [Ping timeout: 252 seconds]
Livio has quit [Quit: leaving]
arno11 has joined #maemo-leste
xmn has quit [Ping timeout: 272 seconds]
Wizzup has quit [Ping timeout: 260 seconds]
Wizzup has joined #maemo-leste
arno11 has quit [Quit: Lost terminal]
arno11 has joined #maemo-leste
Wikiwide has quit [Remote host closed the connection]
Wikiwide has joined #maemo-leste
<Wizzup>
phoenix.maemo.org / leste.maemo.org is down for a few more hours today, and then they will be on UPS
narodnik2 has quit [Quit: WeeChat 4.3.4]
System_Error has joined #maemo-leste
<inky>
i don't know why is this, i assume you integrated all or almost all patches, so i guess this is more because of devuan vs alpine thing. maybe glibc vs musl also matter, i don't know.
<inky>
i want to also tell that i don't know why, but under maemo pinephone not only works longer than under postmarketos, but the handset itself is cold, under pmos it is always hot. even if on apps run.
<inky>
i hope it's not just the older versions of everything.
<Wizzup>
could be wayland vs X
<Wizzup>
or gtk4/qt6 vs gtk2, etc
uvos has joined #maemo-leste
Wikiwide has quit [Remote host closed the connection]
Wikiwide has joined #maemo-leste
<uvos>
inky: seams mutch more likely that you have something installed thats using cpu time on pmos rather than something we did, we dont hit any sleepstates on the pp as far as i am aware
<uvos>
inky: i gues running powertop and compearing would reveal who it is
<Wizzup>
we def. worked on pp power management
<uvos>
Wizzup: sure but we dont hit crust sleep at all
<uvos>
iirc
<uvos>
also on pmos you could have any interface installed or no interface installed so like Wizzup sais it might be heavy or not
<Wizzup>
right, the mode where you basically suspend and can't listen to music we don't hit
<uvos>
Wizzup: right i know but pmos can hit it depending on the installed de
Livio has joined #maemo-leste
Livio has quit [Ping timeout: 264 seconds]
Livio has joined #maemo-leste
Livio has quit [Ping timeout: 276 seconds]
pere has joined #maemo-leste
pere has quit [Ping timeout: 265 seconds]
xmn has joined #maemo-leste
udder has quit [Quit: die in fire]
udder has joined #maemo-leste
<arno11>
Wizzup: btw zram is still there in n900 just not launched on boot
<arno11>
i tried it and as expected, it is a bit slower than swapfile
<arno11>
but it works
<Wizzup>
yeah, so it is disabled as expected
<arno11>
yep
<buZz>
arno11: did you try those zram tweaks perhaps?
<uvos>
n900 is sortof short of both, space and speed
<uvos>
at least on d4 i find myself rarely in want of more ram but often in want of more speed so maybe there lzo is good as is?
<inky>
>also on pmos you could have any interface installed or no interface installed so like Wizzup sais it might be heavy or not
<inky>
with every interface, i usually use sxmo, it is the most lightweight. i don't turn on suspend.
<inky>
>could be wayland vs X
<inky>
in sxmo i use X. that's my usual there.
<inky>
>we def. worked on pp power management
<inky>
i guess you did something important and incredible.
<inky>
sincerely, without anything running, only bare sxmo which is dwm, it would be down in 3-4 hours, but it is up since the late morning and half of the battery is used.
<inky>
i'll try powertop.
<uvos>
i think mainly something is broken on your pmos install
<inky>
i understand, but sincerely, there's not much to be broken, that's a bare dwm with customizations.
<inky>
i'll try powertop.
<uvos>
the thing with pm is that it can break in a lot of ways
<uvos>
i think you should investigate it a bit and maybe file a bug with pmos against the difference
<uvos>
the kernel should be pretty mutch the same so the userspace you have installed must be misbehaveing somehow
<inky>
i'll try.
<Wizzup>
I thought zstd was faster and better, maybe I'm confused
<Wizzup>
uvos: I am not sure if the kernel is that exactly the same
<uvos>
Wizzup: im just going of those nummbers there, i have no futher knowlage in this area
<uvos>
but if those are correct then i think lzo may be the best tradeoff
Livio has joined #maemo-leste
<Wizzup>
they only measured cp time, which is compression only
<Wizzup>
not decompression
<Wizzup>
this would assume that most of the zram would then be written to more than read?
<uvos>
Wizzup: yeah
<uvos>
Wizzup: thats unlikely
<uvos>
Wizzup: but idk what the relavtive speed difference is during decompression
<uvos>
lzo is mainly very simple so i suspect its fast there too
<Wizzup>
I think zstd decompresses really fast
<Wizzup>
as you can see it's basically near gzip
<uvos>
well gzip uses deflate
<uvos>
and wikipedia claims lzo to be faster than deflate
<sicelo>
inky: pmos does run quite a few things that can be CPU-intensive. you won't believe it, but, for example, sxmo pegs N900 cpu at 100% non-stop (well disabling conky makes things better)
<Wizzup>
o.O
<uvos>
wow thats terrible
<uvos>
i mean thats your problem right there xD
Livio has quit [Ping timeout: 252 seconds]
Livio has joined #maemo-leste
<Wizzup>
ah etc/init.d/zram comes from arm-sdk... that's why it isn't in dpkg -S
<arno11>
Wizzup: btw how to check zram current algo ?
hexagonwin has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
<Wizzup>
zramctl
<arno11>
thx
<arno11>
currently trying zstd
<Wizzup>
you can probably increase the zram size too
<Wizzup>
(since it compresses better)
<arno11>
ah ok, yes seems to small
<Wizzup>
I'd say at least 30% more
<Wizzup>
maybe even 50% depending on your current size
<arno11>
actually 175MB
<Wizzup>
there's also the question of whether the zram backing is your ram or a loopback device, I think it could be either
<Wizzup>
maybe not..
* Wizzup
googles
<Wizzup>
I think that is zswap
<arno11>
ok
<Wizzup>
or was :)
<arno11>
ok :)
<Wizzup>
yes, so nevermind my above, zram is only in ram
<arno11>
so lzo seems definitely a bit faster on n900 compared to zstd
<arno11>
but slower than sd swapfile
<arno11>
ofc i suppose it is possible to tweak zram stuff a lot
<arno11>
on n900, the weak cpu seems the culprit bcs overclock improves things with both algos
<Wizzup>
faster how, startup times?
<arno11>
yep
<Wizzup>
is it possible to set zstd level?
<Wizzup>
looks like not
<arno11>
ok
<arno11>
bbl
n9001 has quit [Ping timeout: 260 seconds]
System_Error has quit [Remote host closed the connection]
Livio has quit [Ping timeout: 260 seconds]
Livio has joined #maemo-leste
uvos__ has joined #maemo-leste
<uvos>
"After the page has been decompressed into the swap cache, the compressed version in the pool can be freed."
<uvos>
dose zswap really work like that, seams pointless to decompress the page before writeing it to disk, why not decompress it when reading it back
Wikiwide has quit [Remote host closed the connection]
Wikiwide has joined #maemo-leste
Livio has quit [Quit: Reconnecting]
Livio has joined #maemo-leste
System_Error has joined #maemo-leste
<Wizzup>
yeah, that is odd
arno11 has quit [Ping timeout: 272 seconds]
Wikiwide has quit [Remote host closed the connection]
Wikiwide has joined #maemo-leste
<inky>
what was about that issue when whitespace rotated the screen? i experience it now with dino. every time i press whitespace with onscreen keyboard (not maemo keyboard), screen rotates. i remember diejuse had this issue.
Wikiwide has quit [Ping timeout: 252 seconds]
System_Error has quit [Remote host closed the connection]
akossh has quit [Quit: Leaving.]
arno11 has joined #maemo-leste
<arno11>
inky: also got it with proot
<arno11>
iirc the culprit is hildon-input-method
Livio has quit [Ping timeout: 260 seconds]
arno11 has left #maemo-leste [#maemo-leste]
uvos has quit [Remote host closed the connection]
KREYREN has joined #maemo-leste
System_Error has joined #maemo-leste
KREYREN has quit [Remote host closed the connection]