System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
<donihalim>
So, after installing wireguard from ham and reboot the phone, now i cannot boot to leste. After loading the kernel, the display just blank for a moment then powering off
<donihalim>
I can boot to fremantle tho
<donihalim>
Is it known issue with wireguard on daedalus?
<freemangordon>
Wizzup: I will split hildon-meta to base and device-specific source packages, ok?
<freemangordon>
that way we can leave hildon-meta-core to be no system-upgrade
<freemangordon>
or rather, there will be no need to upgrade hildon-meta-core/device hildon-meta is upgraded
<freemangordon>
*if hildon-meta is upgraded
arno11 has joined #maemo-leste
<arno11>
donihalim: no issue like that afaik
<arno11>
did it work in chimaera btw ?
<arno11>
you should check boot logs imo
<donihalim>
arno11: i've never tried wg on chimaera
<arno11>
ok
lyubov has quit [Read error: Connection reset by peer]
lyubov has joined #maemo-leste
akossh has joined #maemo-leste
<Wizzup>
freemangordon: I am not quite sure what you mean
<Wizzup>
I guess it sounds fine to me
<sicelo>
donihalim: wg shouldn't cause that. maybe just your ongoing power issues
<donihalim>
Battery's fine, i tried using another sdcard that has leste on it and it boot normally
<freemangordon>
Wizzup: will see, will push later today
<arno11>
donihalim: did you check /var/log/boot ?
<arno11>
(maybe just tmp files corruption)
<freemangordon>
sicelo: I wonder what's going on with ZDI, that behaviour does not look normal
<sicelo>
I'm totally annoyed too. when I started with chasing the CVEs, some people mentioned that sometimes the people/organizations behind CVE reports mostly only care about the bounties/money. what's happening here seems to validate that
Anasko has joined #maemo-leste
<dsc_>
donihalim: i was using wg on chimaera just fine
Twig has joined #maemo-leste
udder has quit [Quit: die in fire]
udder has joined #maemo-leste
Twig has quit [Ping timeout: 252 seconds]
Twig has joined #maemo-leste
_fab has joined #maemo-leste
<donihalim>
arno11: donihalim: did you check /var/log/boot < can i mount the partition from fremantle? Or i should take out the sdcard and use my pc?
<donihalim>
Step to reproduce, fresh install daedalus from the latest available img, do the initial setup(including fixing swap), upgrade package, install wireguard from ham, reboot/poweroff
<arno11>
donihalim: you can easely mount the card in fremantle and check
<donihalim>
It's /var/log/boot right?
<arno11>
yes
<arno11>
and maybe syslog
<arno11>
*if there is nothing relevant
<arno11>
in boot log
<donihalim>
i dont see anything relevant, last log is regarding mafw-tracker-source
<donihalim>
In boot log
<arno11>
hmm no errors ?
<donihalim>
No
<arno11>
ok and syslog ?
<arno11>
/var/log/syslog
<donihalim>
syslog also only showing rtkit-daemon
<donihalim>
Do you have wg installed?
<arno11>
nope
<donihalim>
mind to test install wireguard on your exisiting daedalus? But please make backup first, since i cannot boot to the system after installing wg
<arno11>
sorry, but i can't do a backup now. no pc around
<arno11>
but something is unclear to me
<arno11>
when you boot, the devive shutdowns itself ?
<arno11>
*device
<donihalim>
arno11: sorry, but i can't do a backup now. no pc around < np
<donihalim>
Yes, after the kernel is loaded, screen then blank for a while, and then just shutting down
<sicelo>
no message ever shows?
<donihalim>
nope
<donihalim>
i'll post a video
<sicelo>
it's a power issue then
<arno11>
how wireguard starts on boot btw ? init script, xsession or ?
<sicelo>
unless the installation got borked in some other way (unrelated to wg)
<freemangordon>
upower
<freemangordon>
donihalim: try to boot with charger connected
<sicelo>
unlikely to be upower, since this is dying too early. charger may help indeed
<freemangordon>
hmm, right
<donihalim>
booting while connected to a charger also doenst make difference
<freemangordon>
but still seems power lelated, indeed
<donihalim>
warn: vid size are over 100mb
<freemangordon>
I see no charger connected
<freemangordon>
also, do you have wall charger (d+/d- short)?
<arno11>
yeah, from the video, seems power related
<freemangordon>
what battery is that?
<donihalim>
freemangordon: i've test it using wall charger, still wont boot
<donihalim>
Its the original battery
<donihalim>
I can boot fine to fremantle
<freemangordon>
weird
<freemangordon>
maybe put uSD card in PC and to fsck on it
<freemangordon>
*do fsck
<donihalim>
i could try, last time i do fsck on pc it just destroy the partition, whats the correct command?
<freemangordon>
sudo fsck.ext4 /dev/sdX2
<freemangordon>
where X depends on SD device
<freemangordon>
could bre /dev/sdc2 etc
<freemangordon>
*be
<donihalim>
The root partition right?
<sicelo>
so the thing is ... as mentioned before, we are using up way more power than fremantle, so comparing with it doesn't always hold true
<sicelo>
you might be having a contact issue. that's likey why industry decided to switch to screw on (like d4) or clip-on (most phones today) contacts
<donihalim>
sicelo: so it's my battery then?
<donihalim>
It's interesting to me that wireguard could cause such issue
<sicelo>
it's not WG
<donihalim>
sorry i dont understand, but why is it happen only after installing wg?
<arno11>
it is possible if it uses too much cpu with a weak battery
<sicelo>
donihalim: just pure coincidence :-)
<arno11>
on boot
<donihalim>
sicelo: i've tried doing fresh install and then installing wg, then this happen
hm has quit [Remote host closed the connection]
<donihalim>
Now, if i do fresh install again, it would boot normally
<freemangordon>
donihalim: A side note - daedalus is yet not released
<donihalim>
But to make sure, hopefully someone could try installing wg on daedalus
<freemangordon>
I mean maemo-daedalus
<freemangordon>
so for now better stick to chimaera
<sicelo>
I could try it tomorrow
<donihalim>
freemangordon: yes i probably should stick with chimaera
<freemangordon>
as we speak I am trying to iron out some lesta metapackages issues
<freemangordon>
*leste
<donihalim>
sicelo: thanks
<freemangordon>
and Wizzup said he will be back to whatever needs to be done
<sicelo>
but I'm 100% sure it's not WG because your system dies too early, to the point nothing ever shows on screen
<freemangordon>
so holpefully in 2-3 weeks we'll have a release
<arno11>
sicelo: it doesn't show anything anyway on daedalus: logs on screen are deactivated
<sicelo>
oh
<sicelo>
wasn't aware
<arno11>
freemangordon: we have a daedalus img working fine on n900 btw
<arno11>
that's what i sue daily now and what donihalim is currently testing
<arno11>
*use
<sicelo>
maybe we should enable those logs
<arno11>
yes but donihalim said there is nothing relevant in boot log
<sicelo>
which log?
<arno11>
/var/log/boot
<sicelo>
maybe what he can do is tar up all of /var/log and share it privately
<arno11>
yep
<donihalim>
i could say that the only log showed in boot and varlog are logs from previous working system(probably before reboot after installing wg)
<arno11>
ah
<donihalim>
I cloud see from the timestamp
<donihalim>
*could
<sicelo>
there are many other log files there, and off hand I can't think which one would be relevant
<sicelo>
for example, there's a daemon.log which might also be helpful
<arno11>
can't find it on my device
<freemangordon>
arno11: I am not sure extras are compiled for daedalus
<arno11>
only few pkgs
<arno11>
atm
<freemangordon>
right, and that might bring problems
<arno11>
yes indeed
<sicelo>
arno11: wait, no /var/log/daemon.log ?
<arno11>
nope
<sicelo>
wow, I should shut up then since I'm clearly outdated
<Wizzup>
yup, I'm back finally :)
<arno11>
Wizzup: :)
k1r1t0 has joined #maemo-leste
<freemangordon>
in the meanwhile, please, everyone who does not feel brave, disable -devel repos
<arno11>
sicelo: at least boot and syslog are relevant for boot
<freemangordon>
I am pushing things there that might potentially broke stuff
<freemangordon>
*break
<arno11>
we are all brave and adventurous :P
<freemangordon>
ok :)
<donihalim>
agree wirh arno11 :)
<sicelo>
arno11: donihalim: but then again, having nothing relevant in those logs more strongly suggests the power issue I'm on about... i.e. the system is dying before syslog itself is up
<arno11>
and full working stuff is boring
<arno11>
agree
<donihalim>
Another reason to get a new polarcell battery then :)
<freemangordon>
that way HAM can upgrade hildon-meta, without having to upgrade -core or device specific package and vice versa
<arno11>
hmm wireguard currently installs linux-image-6.1.0-31-armmp on 6.6 kernel. not sure it is harmless
<Wizzup>
freemangordon: sounds good
<arno11>
*with 6.6 kernel
<freemangordon>
I doubt :D
<Wizzup>
freemangordon: you will have to change the changelog entries
<freemangordon>
why?
<Wizzup>
arno11: that's bad, we have wireguard module in our kernel
<Wizzup>
freemangordon: it says hildon-meta, not hildon-meta-core
<freemangordon>
well...
<Wizzup>
freemangordon: in hildon-meta-core pkg
<Wizzup>
our CI will complain and not allow it
<freemangordon>
it was true back then, no?
<freemangordon>
ah, I see
<freemangordon>
ok, will do
<Wizzup>
as far as I am concerned you can empty the changelog
Twiggy has joined #maemo-leste
<freemangordon>
ok
<arno11>
donihalim: seems your install is broken :(
<Wizzup>
arno11: not sure why this would happen
<Wizzup>
I think we provide the right meta pkgs
<Wizzup>
is this daedalus?
<arno11>
daedalus yes
Twig has quit [Ping timeout: 248 seconds]
<sicelo>
if it's an installation that must be recovered at all costs, it can be done by chrooting into the card and installing correct kernel. I'd guess this armmp kernel didn't modify the uImage in /boot
<donihalim>
Ah i've already overwite the sdcard with new img...
<sicelo>
here might be your first contribution opportunity 😃
<Wizzup>
daedalus is experimental at this point
<Wizzup>
I'm not surprised there might be these kind of pitfalls
<freemangordon>
hmm, seems you deleted more than needed
<freemangordon>
lemme rebuild gconf for -devel
<Wizzup>
I just removed everything part of gconf from -devel, -experimental and stable
<Wizzup>
in chimaera
<freemangordon>
right
<freemangordon>
but now repos seem inconsistent, so I am rebuilding gconf for -devel
<freemangordon>
that should fix it, hopefully
<Wizzup>
ok
<Wizzup>
I suspect you'll see an error with the same soruce tag
<freemangordon>
lets see
_fab has quit [Quit: _fab]
<freemangordon>
Wizzup: going to try dist-upgrade
<Wizzup>
ok
<freemangordon>
hmm:
<freemangordon>
WARNING: The following essential packages will be removed.
<freemangordon>
This should NOT be done unless you know exactly what you are doing!
<freemangordon>
hildon-meta hildon-connectivity-rtcom (due to hildon-meta) osso-calculator (due to hildon-meta) qalendar (due to hildon-meta) clock-ui (due to hildon-meta)
<freemangordon>
Wizzup: any idea?
<Wizzup>
do you have the pins files?
<Wizzup>
pin files
<freemangordon>
yes
<freemangordon>
hmm, maybe I should have changed HAM catalogues as well
<freemangordon>
lemme see
<freemangordon>
hmm, yeah, that was it
<Wizzup>
cool
<freemangordon>
Wizzup: qt-input-maemo must be rebuild, there is some mess in the repos