pabs3 has quit [Read error: Connection reset by peer]
pabs3 has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
irssitestser has joined #maemo-leste
irssitestser has quit [Client Quit]
joerg has quit [Ping timeout: 265 seconds]
joerg has joined #maemo-leste
_fab has joined #maemo-leste
ceene has joined #maemo-leste
Twig has joined #maemo-leste
pere has quit [Ping timeout: 276 seconds]
_fab has quit [Quit: _fab]
mkfx has joined #maemo-leste
Twig has quit [Read error: Connection reset by peer]
Twig has joined #maemo-leste
_fab has joined #maemo-leste
LeePen has quit [Ping timeout: 252 seconds]
akossh has joined #maemo-leste
Twig has quit [Ping timeout: 252 seconds]
Anasko has joined #maemo-leste
mkfx has left #maemo-leste [#maemo-leste]
Twig has joined #maemo-leste
mkfx has joined #maemo-leste
_fab has quit [Quit: _fab]
ceene has quit [Ping timeout: 246 seconds]
_fab has joined #maemo-leste
Livio has joined #maemo-leste
arno11 has joined #maemo-leste
<donihalim>
I still doesn't understand what happen when the system boot, the system often freeze after booting to the desktop that i had to force shutdown by removing the battery
<donihalim>
This makes rebooting the device quiete frustating
<arno11>
oh
<arno11>
donihalim: please elaborate
<arno11>
with chimaera and kernel 6.6 and sd swap ?
<arno11>
*chimaera -devel
<donihalim>
Ah sorry, so this is what happen: i powered on the phone and it boot normally, since i have display timeout set to 30s, after the phone boot to the hildon desktop the display will turned of after 30s
<donihalim>
After that the system often freeze, touching the screen or using the lock button doesnt not turned on the display
<donihalim>
This often happen everytime i reboot the phone or powered on the phone from shutdown state
<donihalim>
Yes im using chimaera -devel and kernel 6.6
<donihalim>
To workaround this i had to touch the screen after the initial 30s display timeout
<arno11>
hmm yeah the screen time out could be a problem
<arno11>
i usually disable it btw
<arno11>
or set it to 2min
<arno11>
when you say 'reboot', you mean you reboot the device from command line ?
<donihalim>
Either rebooting from cli org poweroff the phone via power menu
<arno11>
ok
<arno11>
did you disable trackers or ?
<donihalim>
Yes i disable tracker and apt worker, following the wiki
<arno11>
ok
<arno11>
and sure your fstab is ok ?
<arno11>
and do you use some custom scripts on boot ?
lyubov has quit [Read error: Connection reset by peer]
<arno11>
anyway, worth a try to set screen time out to 0 or 2 min
<Wizzup>
I don't think it makes sense to disable apt worker
<arno11>
it is just useful for first boots, need to update wiki
<donihalim>
/swap is being created when dist-upgrade to -devel
<arno11>
ok
<donihalim>
Wizzup: should i activate it again? How?
<arno11>
so as i said try to set time out to 0 or 2 min
<arno11>
for apt worker, same command but with different value
<arno11>
let me check
<donihalim>
I've set backlight timeout to 2min, see if still causing freeze
<arno11>
ok
<arno11>
for apt worker you can set check_interval to 10080 (once a week)
<arno11>
or 1440 for every day (original value)
<arno11>
*using the command from wiki
<donihalim>
Will try that, thanks
<arno11>
np
<arno11>
Wizzup: on daedalus, no need to deactivate ap worker for sure
<arno11>
*apt
<arno11>
but from chimaera img it is useful as many important optimisations are only in devel
<arno11>
and device is very slooow and absolutely not usable if apt worker start
<arno11>
anyway, no need now with new imgs
<sicelo>
i still haven't got my libseat problem resolved, so still have never got a successful boot of daedalus.
<sicelo>
Wizzup: any ideas?
<sicelo>
i haven't been able to spend any time on it tbh ... maybe if i do, i can figure it out
<donihalim>
arno11: setting backlight timeout to 2min doesnt solve the issue, i've tried rebooting several time, now the phon freeze again
<donihalim>
Time doesnt change, display not turned off even after 2 min
<arno11>
weird
<arno11>
btw you didn't encounter same issue on daedalus, right ?
<sicelo>
i've chrooted to it now... doing apt-upgrade. maybe it'll do a miracle
<donihalim>
arno11: it happen on daedalus aswell
<arno11>
oh
<donihalim>
Maybe hardware problem?
<arno11>
really don't know tbh
<arno11>
checking your Xorg log could be useful
<arno11>
sicelo: i doubt apt-upgrade could be useful as the img is almost up to date with chimaera -devel
<sicelo>
The following packages will be upgraded: conversations hildon-application-manager hildon-application-manager-settings-standard hildon-input-method hildon-meta hildon-meta-core hildon-meta-n900 libclockcore0-0 libgnutls30 libhildon-im-ui3 libjavascriptcoregtk-4.1-0 libopenh264-7 libtasn1-6 libwebkit2gtk-4.1-0 ofono ofono-scripts openssh-client openssh-server openssh-sftp-server qt-input-maemo
<sicelo>
The following packages will be DOWNGRADED: gtk2-engines-pixbuf libcal1 libcityinfo0-0 libclutter-0.8-0 libgail-common libgail18 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libiphb0 maemo-keyring
<sicelo>
20 upgraded, 0 newly installed, 11 downgraded, 0 to remove and 0 not upgraded.
<sicelo>
that downgrade is fine/acceptable?
<arno11>
yes
<arno11>
(versioning was wrong, that's why it says downgrade)
<arno11>
donihalim: ah, i forgot something...let me check
Livio has quit [Ping timeout: 264 seconds]
<arno11>
donihalim: ls /etc/sysctl.d
<arno11>
do you see n900-perf.conf in red ?
<donihalim>
Let me check
pere has joined #maemo-leste
<Wizzup>
arno11: did we not push the no parallel apt change to chimaera?
<Wizzup>
sicelo: I think there's more problems going on there
<Wizzup>
it looks to be loading swrast
<Wizzup>
[ 72.767] (EE) AIGLX error: dlopen of /usr/lib/arm-linux-gnueabihf/dri/omap_dri.so failed (/usr/lib/arm-linux-gnueabihf/dri/omap_dri.so: cannot open shared object file: No such file or directory)
<sicelo>
having chrooted into the sd card, got an excuse to also build upstream iio-sensor-proxy already. so i can now spare my N900 ;-)
<arno11>
but i supposed it is pvr_dri.so instead, or ?
<arno11>
donihalim: oh
<arno11>
so there is a real problem lol
<arno11>
Wizzup: some important commits are missing in -devel for n900
<donihalim>
whats the content supposed to be?
<arno11>
donihalim: i think you should comment all lines in this file and reboot :)
<Wizzup>
arno11: -devel being chimaera-devel yeah
<Wizzup>
sicelo: let me check my n900
<arno11>
this file is supposed to be removed or empty
<arno11>
Wizzup: yep, old vm tweaks are still there
<donihalim>
Should remove the link or?
<arno11>
so no surprise if donihalim device is freezing after boot
<arno11>
donihalim: just comment all lines
<arno11>
*#
<Wizzup>
sicelo: yes, ok, I see, the omap error I also have but it seems to be ok
<Wizzup>
I don't have this libseat issue, I wonder if it is a race condition somehow
<Wizzup>
I guess I should flash the latest n900 image
<donihalim>
Glad it's not hardware issue :)
<arno11>
yes indeed :)
<donihalim>
I'll rebooting several time, i'll report back
<arno11>
i need to check one more thing because maybe another file is problematic
<arno11>
donihalim: do you have 'leste-config-n900' in /etc/init.d/ ?
<arno11>
if yes, delete it or move it to $HOME
<donihalim>
Yes it present in /etc/init.d
<donihalim>
I'll move it to home
<arno11>
ok so that is the real culprit
<arno11>
ok
<arno11>
it should work fine now on next reboot
<donihalim>
Nice, many thanks arno11 :)
<arno11>
Wizzup: commits eaf6d22 is missing in chimaera, don't know why
<sicelo>
chimaera, or daedalus? also what repo?
<arno11>
(it reverts problematic nr_request and vm stuff on boot)
<arno11>
for daedalus it seems ok
<arno11>
so that's weird
ashley has quit [Ping timeout: 268 seconds]
<arno11>
leste-config repo
<Wizzup>
arno11: ok, I can fix that today, so I just need to check what is missing in chimaera?
<arno11>
yes, in leste config
<arno11>
seems ok in daedalus as i've never seen those files
<arno11>
donihalim: np, but many thx to YOU for the feedback
<sicelo>
i asked about my libseat issue in the libseat room, and they said it's failing during shutdown ... but i'm booting :-p
<sicelo>
so that suggests that the libseat errors are not the real culprit. i need to find who/what initiates a shutdown
<sicelo>
oh i'm dumb ... i think it's upower :-D
<arno11>
oh
<Wizzup>
that's quite possible
<Wizzup>
I dist-upgraded so I still have the old upower
<Wizzup>
you can -x upowerd and see if it works
<arno11>
but why no issue on my device ? (daedalus same img)
<sicelo>
arno11: my device has broken USB, so % readout in /sys/class is always 0%
<arno11>
ah ok
<sicelo>
it can happen to you as well if you remove the battery for a long time, since the fuel gauge will get reset. if you try and boot again, i'm sure you'll have same experience as i, assuming you don't connect to a charger
<arno11>
ok i see
apac has quit [Ping timeout: 248 seconds]
<sicelo>
upower from leste/chimaera made some estimations based on voltage
<sicelo>
and yay, i'm in Hildon now
<Wizzup>
great
<arno11>
yeah cool
<arno11>
welcome in daedalus !
<sicelo>
with my subpar SD card, can't do anything yet.
<sicelo>
arno11: so (1) swap, (2) that /etc/init.d/leste-config-n900, what else?
<arno11>
you have also leste-config-n900 in daedalus ?
<sicelo>
no idea. haven't looked yet. i'm just asking for what fixes i need to make in order to be able to use this ...
<sicelo>
my card isn't of the best quality, so yeah
<Wizzup>
I think it's just swap
<arno11>
ok, so you should not have troubles with leste config files but yes you need sd swap
<arno11>
if your sd is slow, you should block tracker3 or at least add .nomedia in $HOME
<arno11>
and use 500MHz min freq
<arno11>
that's it
<Wizzup>
I don't block tracer3 on my n900 fwiw
<arno11>
yes i know but your card is fast :)
<sicelo>
i didn't have it blocked in chimaera, nor played with frequencies
<arno11>
that's just suggestions
<sicelo>
still struggling to get to terminal to even do expandcard :-D
<arno11>
that's normal
<arno11>
first boot is a pita with slow sd
<arno11>
should work fine on next reboot
<sicelo>
oh wait ... maybe it's so dogslow because it's still trying to show that first boot thing ... still hasn't shown btw, and that's 14 min after :-D
<arno11>
omg
<arno11>
yeah that's the problem
<Wizzup>
top should probably show what it is doing
<arno11>
btw on next boots the only very slow thing should be apt and ham (if the card is not fast enough)
<sicelo>
thank God for lp5523 ... at least the white LED gives consolation
<Wizzup>
:)
<arno11>
lol
arno11 has left #maemo-leste [#maemo-leste]
Livio has joined #maemo-leste
Livio has quit [Ping timeout: 264 seconds]
<sicelo>
I'm more excited to see my iio-sensor-proxy working in Leste ... so screen will now get blanked during a phone call
<sicelo>
I'll submit MR later today hopefully
<sicelo>
if time permits, next stop should be upower ... we need to fix our stack
<Wizzup>
thank you for all the energy/efforts :)
pere has quit [Ping timeout: 248 seconds]
Livio has joined #maemo-leste
arno11 has joined #maemo-leste
hm has quit [Remote host closed the connection]
<arno11>
cool @iio-sensor, will save at least 50mA
<arno11>
during calls
<arno11>
70mA saved in fact with brightness @50
<arno11>
(on n900 calls actually burn around 350mA !)
<sicelo>
oh wow! didn't realize that
<Wizzup>
the cpu routing part of it probably causes a bunch of that
<Wizzup>
pipewire might make some of that a bit better
<sicelo>
i have given pipewire some thought for sure ... but i guest we will need to write a pipewire component for cmtspeech :-/
<sicelo>
unless we go cmtspeech -> pulse -> pipewire
mkfx has left #maemo-leste [Error from remote client]
nela7 has quit [Quit: bye]
nela7 has joined #maemo-leste
LeePen has joined #maemo-leste
<arno11>
cmtspeech -> pulse -> pipewire should be easy, there is module for that iirc
<arno11>
but anyway, i doubt we can improve cpu usage, just my opinion
<arno11>
unless we find a way to use dsp chip...
ashley has joined #maemo-leste
ashley is now known as Guest1863
pere has joined #maemo-leste
<sicelo>
i really wish so too (dsp)
<arno11>
oh now i remember what fmg said about cmt_pulse cpu usage: some neon code is missing for resampling 8000 -> 48000Hz iirc
<arno11>
and 48000 to 8000 in the other way
<arno11>
sicelo: yeah definitely @dsp
<sicelo>
@ neon code ... i think it's in one of the repositories. have never looked at it closely though
<arno11>
yes indeed iirc. the answer is probably in irc logs
<arno11>
if nobody has spare time for that, maybe AI could help
<arno11>
i mean for neon code
<sicelo>
dsc_: have you ever used the calendar in Leste? any idea where one can look if they wanted to fix the layout/display issue, namely, the week display on the left is 6 rows, but the actual days/dates are 5 rows..
Livio has quit [Ping timeout: 264 seconds]
a_fantom has joined #maemo-leste
fantom has quit [Ping timeout: 244 seconds]
<dsc_>
sicelo: my life is so boring I dont need a calendar