<sicelo>
are you sure you made the verbosity changes Wizzup had shared? at least we don't seem to get the LL_DEBUG output. luckily for us, the LL_INFO is good enough. i.e. you don't necessarily have to redo this verbosity stuff
Anasko has quit [Remote host closed the connection]
Anasko has joined #maemo-leste
hm has joined #maemo-leste
ungeskriptet has joined #maemo-leste
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #maemo-leste
System_Error has quit [Ping timeout: 244 seconds]
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #maemo-leste
System_Error has joined #maemo-leste
<Wizzup>
sicelo: hm.. I think chmod -x on upowerd did solve the problem
<sicelo>
for your friend, you mean?
<Wizzup>
yeah
<sicelo>
could be the d4 has different problem from saeed 's
<Wizzup>
but I will check the mz617 as well
<sicelo>
please do. we need to fully resolve the issue if it's in our stack
<Wizzup>
yeah I think it's the main release blocker :p
<sicelo>
🤦 really? then yeah, let's get all the data and just squash the bug once and for all.
_fab has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
Daanct12 has quit [Quit: WeeChat 4.6.3]
System_Error has joined #maemo-leste
moparisthebest has quit [Ping timeout: 260 seconds]
_fab has quit [Ping timeout: 260 seconds]
ceene has quit [Ping timeout: 276 seconds]
moparisthebest has joined #maemo-leste
erebion has quit [Quit: Disconnected by admin]
erebion has joined #maemo-leste
erebion has quit [Changing host]
erebion has joined #maemo-leste
<buZz>
sicelo: i wonder if maybe their thermistor pin is poorly connected or something
<buZz>
and whatever chip is first talking to battery just switches it off because of temps
<sicelo>
i wouldn't rule that out, although, at least in the case of N900, i doubt a battery like that would make it past NOLO so easy
<buZz>
ah yeah perhaps
<buZz>
a poor connection could change the resistance though
<buZz>
halftorn flexpcb or something
System_Error has quit [Remote host closed the connection]
_fab has joined #maemo-leste
System_Error has joined #maemo-leste
uvos__ has joined #maemo-leste
<uvos__>
the mapphones dont care about the presence of the thermistors
<uvos__>
nor the rom
<uvos__>
I dont have a thermistor or rom in mine and it works fine
<uvos__>
the only side effect is that android refuses to charge the battery without the rom
<uvos__>
but even android perfetcly happy running with just the voltage present
<uvos__>
so on n900 maybe, but not on mz617/d4
uvos__ has quit [Remote host closed the connection]
<buZz>
for droid4 i needed to 'ignore' the thermistor when i hooked up something weird
<buZz>
to prevent something freaking out
<buZz>
but that might be removed from driver now? i dont know
uvos__ has joined #maemo-leste
<uvos__>
buZz: your right
<buZz>
it could be they are hitting that too, and disabling it could help?
<uvos__>
i forgot about that. I added a kernel modul parameter to ignore it since battery presence is based on the thermistor
<uvos__>
so if you dont have the thermistor and dont set this parameter upower will think there is no batterz
<uvos__>
no idea how it reacts to that
<buZz>
or if the thermistor is poorly connected ;)
<mkf>
sicelo: i did tried upower, didn't worked.
<sicelo>
mkf: in your case upower is definitely not the problem. your battery reports >3.7V, which is fine. and your logs do not show the poweroff as coming from mce, which in our stack is the only responsible component for battery-related poweroff (via battery-upower -> battery-guard).
<mkf>
Any ideas?
<sicelo>
your system is powering off for something else ... not sure what. in fact that's why removing `battery-guard` from modules did not make any difference
<sicelo>
unfortunately for now i'm not fully sure what it could be. maybe Wizzup might have a better idea looking at your logs ...
<sicelo>
does Fremantle run without an issue?
<sicelo>
maybe try downloading a new image, try different SD card, etc.? could even try postmarketOS just for comparison.
<mkf>
Yes. It did ran leste well few months ago with the same sd.
<mkf>
It doesn't run fremantle atm since i broke it's boot
<uvos__>
The kernel will also power off for low battery, as its poweroff is triggered from a low irq from cpcap if the battery is not well connected it could concevably power off on a short voltage sag (due to poor connection) before userspace gets the chance to react
<uvos__>
i gues
<uvos__>
at least on mapphones
<uvos__>
mkf: your problem is on n900 right?
<sicelo>
N900 doesn't have poweroff at kernel driver
<mkf>
Yes
<uvos__>
right ok
<uvos__>
yeah then idk
<uvos__>
strange
<uvos__>
we are talking an oderly power off here right?
<uvos__>
not a hard power cut
<uvos__>
a clue is also the white led
<uvos__>
if you see a the white led during the power off, mce was told about the shutdown
<uvos__>
which means it was triggered by or via dsme
<uvos__>
if you have an orderly shutdown without the white led then something triggered via init
<mkf>
I can see white led for few moments, returns to the tty with seatd errors and shuts down
<uvos__>
ok
<uvos__>
is lifeguard enabled on your machine?
<uvos__>
it dosent reboot after this right?
<mkf>
lifewhat?
<mkf>
It turns off. No reboots.
<uvos__>
dsme will reboot the system when a deamon crashes to often
<uvos__>
this part of dsme is called lifeguard
<uvos__>
its disabled by haveing a file in /etc/ i dont remmeber of hand what it is
<uvos__>
we should be creating that file in the images
<uvos__>
but maybe it whent missing
<uvos__>
but if its a shutdown, not reboot its not that
<mkf>
There are mad daemons i can see
<uvos__>
anyhow if you see the white led then its dsme doing the shutdown (possibly told by something else)
<sicelo>
what i see a lot in the dsme.log (towards the end) is a number of processes stopping and restarting with different PIDs.
<sicelo>
and at least i can see mce shutting down. but the shutdown doesn't appear to be from mce itself
<uvos__>
only dsme tells mce to enter shutdown state
<uvos__>
(other than mce itself)
<mkf>
I guess i can sort that log
<mkf>
To have a more clear timestamps?
<sicelo>
at least on the mce side, you can triple-check that you added the arguments/switches Wizzup shared, which hopefully should cause the LL_DEBUG prints to show in the log as well
<sicelo>
but i really don't think this came from mce ... at least the logs don't indicate it.
<sicelo>
also, you already neutered upower, so it's not upower (which i, of course, expect).
<uvos__>
could his power button be stuck?
<uvos__>
on power longpress we shutdown
<uvos__>
so mce starts longpress timer expires shortly after -> shutdown
<uvos__>
the power button debug prints are LL_DEBUG i think
narodnik has quit [Ping timeout: 260 seconds]
<uvos__>
mkf: maybe remove all the power button actions in /etc/mce.ini and /etc/mce.ini.d/--memo.ini
mkf has left #maemo-leste [Disconnected: Replaced by new connection]
mkf has joined #maemo-leste
_fab has quit [Quit: _fab]
<mkf>
Unlikely because fremntle was fine
<sicelo>
mkf: a lot could have changed :-) ...
<sicelo>
that's why it really won't hurt to try a new image, new card, etc., after trying uvos__ latest suggestion
<sicelo>
SD cards wear out 'quietly', and the device itself (they're really old now, and yours is already a bit unhealthy)
<mkf>
Let me try a known good image
_fab has joined #maemo-leste
_fab has quit [Client Quit]
uvos__ has quit [Ping timeout: 276 seconds]
uvos__ has joined #maemo-leste
vectis has joined #maemo-leste
Twig has joined #maemo-leste
vectis has quit [Ping timeout: 240 seconds]
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #maemo-leste
_fab has joined #maemo-leste
vectis has joined #maemo-leste
mkf has left #maemo-leste [Disconnected: Replaced by new connection]
mkf has joined #maemo-leste
mkf has left #maemo-leste [#maemo-leste]
mkf has joined #maemo-leste
mkf has left #maemo-leste [Disconnected: Replaced by new connection]
mkf has joined #maemo-leste
g4rrgl3n0m4d has joined #maemo-leste
Anasko has quit [Ping timeout: 272 seconds]
pabs3 has quit [Ping timeout: 245 seconds]
narodnik has joined #maemo-leste
pabs3 has joined #maemo-leste
mkf has left #maemo-leste [Disconnected: Replaced by new connection]
mkf has joined #maemo-leste
xinomilo has joined #maemo-leste
mkf has left #maemo-leste [Disconnected: Replaced by new connection]
mkf has joined #maemo-leste
mkf has left #maemo-leste [#maemo-leste]
mkf has joined #maemo-leste
pere has quit [Ping timeout: 265 seconds]
narodnik has quit [Ping timeout: 240 seconds]
narodnik has joined #maemo-leste
<saeed>
hi leste people
<saeed>
installed an image from 2024
<saeed>
boots.
<saeed>
sicelo, uvos__, Wizzup: ^
<saeed>
by the way the modem of this phone is busted.
<saeed>
i don't know why, but it might be related
_fab has quit [Quit: _fab]
<sicelo>
broken modem shouldn't cause an issue (i did see from your log that yours is broken)
<saeed>
how does framtle mounts its file system?
<saeed>
i edited a file there and the system doesnt boot anymore
<saeed>
it was in /etc, i've mounted mmcblk1p1 and i can see no standard heir of files (i.e, there is no /etc)
<saeed>
neither an fstab
<saeed>
o7
<sicelo>
fremantle?
<saeed>
yeah.
<saeed>
i have booted leste to rescue the fremantle
<freemangordon>
saeed: fremantle rootfs is on onenand
narodnik has quit [Ping timeout: 240 seconds]
<freemangordon>
mtdblock0 IIRC
<saeed>
on nand?
<saeed>
ah
<freemangordon>
onenand, yes
<freemangordon>
ther is 256 MiB onenand split into several mtdblock devices
<saeed>
uh
<freemangordon>
oh, it is not mtdblock0, but the last block
<saeed>
wrong fs type, bad option, bad superblock, etc
<saeed>
ok
<freemangordon>
lemme connecto to my device to check
<saeed>
unkown fs type ubi
<saeed>
i recall ubifs.
narodnik has joined #maemo-leste
<freemangordon>
ubi0:rootfs on / type ubifs (rw,bulk_read,no_chk_data_crc)
xinomilo has quit [Quit: Leaving]
<saeed>
can i mount it in leste?
<freemangordon>
you should be able to, unless we didn't enable ubifs in kerne;l
<saeed>
it seems it wasnt enabled. :(
<freemangordon>
why don;t you just boot rescueos if you want to recover your fremantle?
<saeed>
never tried it. let me see.
<saeed>
so i just should dd that 5mb image?
<freemangordon>
no
<freemangordon>
you boot it with flasher
<sicelo>
iirc ubi is enabled in our kernel. what you might be missing is the userspace tools for mounting it (mtd-tools or something like that)
<freemangordon>
still, weird that recent images shut doen
<freemangordon>
*down
<freemangordon>
Wizzup: sorry, didn't have time to push ofono fixes yet, will do my best to do it tomorrow
pere has joined #maemo-leste
<sicelo>
saeed: try a new image again. if you still have a problem with it, let me know the exact image so i can also download it and hopefully debug. my N900 has working USB port at least
_fab has joined #maemo-leste
gnarface has quit [Remote host closed the connection]
<saeed>
a new build has been issued or i should reuse last image?
<sicelo>
tbh i don't know what's the latest state of images :p
<sicelo>
if you have the bandwidth, i would suggest downloading a fresh copy, and verifying the checksums afterwards
_fab has quit [Ping timeout: 260 seconds]
<saeed>
its back!
<saeed>
thanks again
<sicelo>
meaning?
arno11 has joined #maemo-leste
<saeed>
old framantle setup was fixed with rescueos
<saeed>
i'll redownload leste image again tomrrow to retry
<sicelo>
oh nice
gnarface has joined #maemo-leste
_fab has joined #maemo-leste
_fab has quit [Remote host closed the connection]
gnarface has quit [Remote host closed the connection]
apac has joined #maemo-leste
vectis has quit [Ping timeout: 240 seconds]
gnarface has joined #maemo-leste
vectis has joined #maemo-leste
vectis has quit [Ping timeout: 240 seconds]
thatretrocattt has joined #maemo-leste
thatretrocattt has left #maemo-leste [#maemo-leste]
thatretrocattt has joined #maemo-leste
<thatretrocattt>
pluh
<thatretrocattt>
no one on here ey?
thatretrocattt has left #maemo-leste [#maemo-leste]