<buZz>
apt install audacious works, needs a 'ctrl-p' to change the layout to 'winamp' and then a 'ctrl-d' to get pixeldoubling, although we might need pixeltripling :P
<tmlind>
yeah worth try pulling, hopefully no bad merge conflicts
<freemangordon>
tmlind: for the testing, shall I just do git merge?
<mighty17[m]>
<freemangordon> "OTOH, if I hack mesa - one..." <- Well right! Wlroots it is then, iirc I tried the patches from tmlinds tree but that crashes wlroots whenever i started an app
<mighty17[m]>
Broken bus error iirc
<freemangordon>
mighty17[m]: give me some time to finish what I am doing, I'll get back to meas
<freemangordon>
*mesa
<freemangordon>
uvos__ likes that patch too, so as I said, I may reconsider
Daanct12 has quit [Ping timeout: 268 seconds]
_uvos_ has joined #maemo-leste
<_uvos_>
freemangordon: i mostly maintain the mapphone kernel for us. so i remerge the kernel from feature branches for every major release and just merge in .y regularly
<_uvos_>
so yeah merging in .y is fine
<freemangordon>
I am doing it ATM
<_uvos_>
since thats what i do anyhpw
<_uvos_>
great
<freemangordon>
but, I do pull --rebase :p
<_uvos_>
i should probubly also rebase on 5.19 since 5.18 is eol
<_uvos_>
but at this point it might make sense just to wait for 6.0
<_uvos_>
also usually i wait for tmlind to rebase his stuff first
<freemangordon>
CONFLICT (content): Merge conflict in drivers/power/supply/cpcap-battery.c
<freemangordon>
:(
<mighty17[m]>
<freemangordon> "mighty17: give me some time to..." <- Coolio, till then I'll reapply the patch and get proper logs
<freemangordon>
uvos__: do we still need 7d58bfa7fbdb5e332d8aeb64723649ec78c25315?
<freemangordon>
the only difference I see compared to .y is that one time warning
<freemangordon>
I am going to drop that patch
<freemangordon>
tmlind: I guess we shall drop 4d3cc4fad55a53a879ae101079096ef0f3c6ff15 as well
<uvos>
but you can temporarly drop it for testing if you want (its not enabled on leste anyhow)
<freemangordon>
umm, the code it is already in linus tree
<uvos>
ok then sure, you can drop it
<freemangordon>
as I said, the only difference is missing one time warning logic
<uvos>
i often forget what i pushed upstream allready
<freemangordon>
no_nvmem_warned that is
<uvos>
thats fine
<uvos>
it just uses warn once function
<freemangordon>
ok, dropped
uvos__ has quit [Ping timeout: 260 seconds]
uvos__ has joined #maemo-leste
<freemangordon>
tmlind: I am going to drop d3ceddc76538c8b104ef1e751022a59e9db31ea4 as well
<freemangordon>
yay! rebased :)
Pali has quit [Quit: No Ping reply in 360 seconds.]
Pali has joined #maemo-leste
Pali has quit [Ping timeout: 252 seconds]
akossh has joined #maemo-leste
Livio has joined #maemo-leste
Livio has quit [Changing host]
Livio has joined #maemo-leste
<tmlind>
freemangordon: hmm isn't that commit needed for the serdev functions?
Daanct12 has joined #maemo-leste
<freemangordon>
yes, it is, forward-porting ATM
<tmlind>
ok
<freemangordon>
I kept your comments and sign-off, hope you don;t mind
Daanct12 has quit [Ping timeout: 252 seconds]
<tmlind>
np
<freemangordon>
does not boot :(
<freemangordon>
but is not dead either
<Wizzup>
I think we 'typically' only rebase when going to a new stable (non-point) release, although if you had any conflicts I guess they would have happened anyway
<Wizzup>
arg @ not boot
<freemangordon>
well. it boots...
<freemangordon>
still booting
Daanct12 has joined #maemo-leste
<uvos>
freemangordon: have serial?
<freemangordon>
no
<uvos>
:(
<freemangordon>
but display is inited
<uvos>
should i make and send you a serial adapter?
<freemangordon>
it waits for 6600 usb to initialize
<uvos>
its tirivall after all
<freemangordon>
I think I have dmesg
<freemangordon>
it is alive, just not booting
Daaanct12 has joined #maemo-leste
* Wizzup
mumbles something about merging in fixes when just trying to fix a specific issue
<freemangordon>
ok, I got shell
<uvos>
eh we should keep the kernel recent, for sec fixe if nothing else
<freemangordon>
seems udevd waits forever
<Wizzup>
freemangordon: maybe moddep wasn't run or something
<Wizzup>
maybe run moddep -a
<freemangordon>
no, it is anotehr issue
<Wizzup>
ok
pere has quit [Ping timeout: 268 seconds]
<freemangordon>
let it finish powering off
<freemangordon>
I'll post dmesg log
<Wizzup>
uvos: I agree we should, but I wouldn't mix it with fixing specific issues first
<Wizzup>
anyway w/e :)
Daanct12 is now known as Guest1343
Daaanct12 is now known as Daanct12
<Wizzup>
ps: I submitted two talks for the openfest2022 call for papers https://wizzup.org/sub.png - let's see if they accept one
<sicelo>
it happens when the command fails ... so check your current readout command. it doesn't return non-zero (fails)
<buZz>
it might have to do with calibration
<buZz>
that if i didnt hit 'fully charged' from that boot, the current readout doesnt work?
<buZz>
like battery percentage aswell, iirc
<uvos>
no
<sicelo>
yes current should always be there (even on bq27200 driver which is very fussy about calibration)
<buZz>
ahhh indeed, i was trying to | bc -l "" something , but without success thusfar :P
<buZz>
just 'battery percentage' is empty when not hit a fully charged mode
<buZz>
well, and 'battery charge'
<buZz>
hmmm, with last updates i now have 2G icon visible from ofono registration (i guess) , but cant get my iap to appear for gprs with my old methods
<buZz>
maybe i should delete the iap and have it be reprovisioned?
<uvos>
no idea i cant get it to work either
<uvos>
even when its provisioned in ofono
<buZz>
ah, i guess i dont have all the latest updates, lets see
<sicelo>
one droid 4 thing that i see often nowadays is 'sudden death'
<sicelo>
just now i was doing `apt update`, and while looking away, it just died and rebooted
<sicelo>
i see these kinds of reboots often
<buZz>
maybe a loose battery connection? i havent had that really
<sicelo>
not battery, of course. device was sitting on a table, securely
<buZz>
what was the room temp during that?
<buZz>
hmmf, nope, even last ofono updates dont give me the gprs iap back
<sicelo>
heh, this week is cold :-)
<sicelo>
let me look at logs and see if i can pinpoint something
eloy has quit [Changing host]
eloy has joined #maemo-leste
mardy has quit [Quit: WeeChat 3.5]
<freemangordon>
sicelo: sounds like a HW issue. you said you have a custom battery?
vagag has joined #maemo-leste
vagag has left #maemo-leste [#maemo-leste]
akossh has quit [Quit: Leaving.]
Livio has quit [Ping timeout: 255 seconds]
jr-logbot` has quit [Remote host closed the connection]