uvos has quit [Ping timeout: 256 seconds]
_inky has quit [Remote host closed the connection]
sunshavi has quit [Ping timeout: 260 seconds]
_inky has joined #maemo-leste
sunshavi has joined #maemo-leste
zhxt has joined #maemo-leste
inky has quit [Ping timeout: 240 seconds]
inky has joined #maemo-leste
_inky has quit [Ping timeout: 256 seconds]
_inky has joined #maemo-leste
Pali has quit [Ping timeout: 240 seconds]
<mighty17[m]> Any clues why this happens, when I cold boot my mmc5 node (ie sdio for wifi) doesn't show in dmesg, and wifi doesn't work as well, but if I boot from twrp into mainline (ie reboot to system option) mmc5 and wifi works
joerg has quit [Ping timeout: 240 seconds]
joerg has joined #maemo-leste
macros__ has joined #maemo-leste
macros_ has quit [Ping timeout: 268 seconds]
mardy has joined #maemo-leste
<tmlind> Wizzup, freemangordon: not sure if i understand the lima thing.. but noticed this commit is referenced also in a wlroots bug lima: fix xserver page flip fail for full screen client
<tmlind> mentioned in this bug: https://github.com/swaywm/wlroots/issues/2795
<freemangordon> tmlind: clutter was not updateing damaged areas correctly
<freemangordon> not related to xserver or lima
<freemangordon> but that's only part of the story
<freemangordon> lima still has issues
<tmlind> ok
<freemangordon> in the meanwhile something got broken on my d4 :(
<freemangordon> as soon as I try to init pvr device hangs
<tmlind> heh ok
<tmlind> hmm i don't think we have EGL_KHR_partial_update, do we? or is there something similar
<tmlind> freemangordon: maybe you're trying to init pvr for wrong hardware? check the pvr env variables
<freemangordon> tmlind: no matter, it should not hang the device
<freemangordon> and it was working since yesterday
<freemangordon> when I did dist-upgrade
<freemangordon> oh, maybe libs are broken?
<freemangordon> hmm, why such a big diff in dtb size between what I have here and repo kernel?
<freemangordon> this is the last resort, copying kernel and modules that I used didn;t help
<tmlind> you can decompile the dtb to check with dtc -I dtb -O dts your.dtb
<freemangordon> mhm
<freemangordon> but lets see first if using my dtb helps
<freemangordon> no!
<freemangordon> wtf?
<freemangordon> ok, sgx user libs then
<tmlind> hmm looks like EGL_KHR_partial_update is listed for series6 only in PowerVR.Supported+Extensions.OpenGL+ES.EGL.pdf
<freemangordon> why do you look at that?
<tmlind> just wondering if the wlroots bug above is related to the black rectangles
<tmlind> the missing flush bug
<freemangordon> yep, seems ddk blobs in -experimental are broken
<tmlind> wrong commit or wrong env?
<freemangordon> no idea
<freemangordon> but if I LD_LIBRARY_PATH to the local blobs dir I keep on device, init no longer hangs
<tmlind> ok
<freemangordon> ugh
<freemangordon> this is for wrong device
<freemangordon> -rw-rw-r-- 1 root root 99776 Oct 26 16:16 libsrv_init.so.1.17.4948957 is in my blobs dir
<freemangordon> -rw-r--r-- 1 root root 103736 Dec 15 01:36 /usr/lib/arm-linux-gnueabihf/libsrv_init.so.1.17.4948957 is installed with sgx-ddk-um-ti343x
<freemangordon> wait, what?!?
<freemangordon> sgx-ddk-um-ti343x
<tmlind> heh
<freemangordon> why is this installed on d4?!?
<freemangordon> Wizzup: xserver-xorg-video-omap most-probably is being held because of a wrong dependency to sgx-ddk-um-ti343x
<tmlind> freemangordon: so was the solution to the clutter issue to update clutter or some commit? just wondering..
<freemangordon> update clutter
<tmlind> ok nice
<freemangordon> update, like enable support for double-buffering
<tmlind> ok
<freemangordon> the code was there but disabled by Nokia, with a big fat warning to re-enable it when needed :)
<tmlind> heh ok :)
<tmlind> so did that fix the missing flush issue?
<freemangordon> umm... what issue?
<tmlind> the black squares on some frames issue
<freemangordon> this was fixed in ddx
<tmlind> oh, i've missed that, so what change fixed that?
<freemangordon> waiting sgx to finish rendering before doing flips
<freemangordon> lemme find the commit
<tmlind> ok thanks nice if it's fixed finally
<tmlind> yeah commit would be nice to see for longer term memory to revolve the issue :)
<tmlind> to resolve the issue
<tmlind> trauma therapy kind of thing..
<freemangordon> magic happens in waitForBlitsCompleteOnDeviceMem
<freemangordon> the only remaining issues are correct 3-buffer implmentation and tearing
<tmlind> hmm ok yeah i recall seeing this but never figured out where exactly it ends up waiting..
<tmlind> ok thanks, yup you already explained things for me earlier from there
<tmlind> looks like simple-dmabuf-egl.c in wait_for_buffer_release_fence() uses EGL_KHR_wait_sync, i guess that's how it ensures updates..
<freemangordon> yes
<freemangordon> well, I guess yes
<tmlind> oh but EGL_KHR_wait_sync is listed series6 only?
<freemangordon> no, why?
<freemangordon> our driver reports it supported, iirc
<freemangordon> lemme check
<freemangordon> (d4 boots...)
<tmlind> hmm so do we get "Warning: EGL_KHR_wait_sync not supported" with weston-simpel-dmabuf, let me check..
<tmlind> i'm only seeing explicit_synchronization warnings
<freemangordon> I see EGL_KHR_wait_sync as suported extension
<freemangordon> *supported
<tmlind> ok
<tmlind> hmm so is the conclusion that the client's responsibility to call EGL_KHR_wait_sync, basically the topmost app (or xserver related stuff) with black squares issue?
<tmlind> hmm i'm seeing also a maximized weston-terminal suffer from some areas not being updated when switching to it, so maybe there still is some driver issue too
<tmlind> not sure if i ever saw this issue with weston, not that i did much testing either
<freemangordon> tmlind: I am not sure I get it - do you still see issues with xserver applications?
* freemangordon wonders what is the difference between EGL_NOKIA_texture_from_pixmap and EGL_NOK_texture_from_pixmap
<freemangordon> TBH I am not sure how usable EGL_KHR_wait_sync is
<tmlind> freemangordon: so my test case is slow down pvr, then flip sway desktops with termite running.. but maybe that uses xwayland and i really should test that with weston-terminal for example. sounds like you got it fixed for xorg
<tmlind> freemangordon: so i presume things work now fine for you also with sgx clock slowed down with no black squares?
<freemangordon> mhm
<tmlind> ok great
<tmlind> hmm so for my test case, maybe "lima: fix xserver page flip fail for full screen client" is really the right fix if termite uses xwayland, or if switching from any xwayland app to let's say weston-terminal
<freemangordon> why lima?
<freemangordon> I mean - that should not affect pvr, IIUC
<tmlind> no idea.. but it sounds like it's the previous app that needs to wait for gpu render to complete before the switch to any other app happens
<freemangordon> sure
<freemangordon> well, actually it should wait before the flip
<tmlind> so i tried flipping between two desktops with a weston-terminal only in each desktop and so far have not been able to trigger the artifacts
<freemangordon> flip == "drm page flip"
* freemangordon tries EGL_NOK_texture_from_pixmap
<tmlind> ok so the wait before the flip may only be missing for my test case when switching from some xwayland app to some other app.. well at least i need to test that
<tmlind> hmm but then why do i see artifacts when switching from weston-terminal to termite? if it's up to weston-terminal to wait for gpu to complete before flip, and assuming it's doing the right thing..
<tmlind> sounds like i need to test with xwayland disabled at least
xmn has quit [Quit: ZZZzzz…]
<tmlind> seeing artifacts also between two weston-terminal windows as long as one is maximized so they look different, the artifacts seem very small though just maybe 10x20 pixels at the top left corner in portrait mode
<tmlind> mode like p shaped small artifact with about 10x10 pixels top part and 5x10 part bottom..
<tmlind> oh well so much for that theory
<freemangordon> ugh, we have a glmark fps regression
<freemangordon> with glmark2-es2-drm that is
<freemangordon> tmlind: how to check the clocks?
<freemangordon> glmark2 Score: 37
<freemangordon> on d4
<freemangordon> wtf?
<tmlind> freemangordon: the d4 sgx clock slow down trick is rwmem 0x4a008164=0x1f, let me check the value i have by default
<freemangordon> 225
<freemangordon> it is ok
<freemangordon> something else slows it down
<freemangordon> maybe mesa
<tmlind> yup 0x225 is the default value
<freemangordon> lemme try with my kernel first
Twig has joined #maemo-leste
<sicelo> tmlind: i *think* termite is not xwayland, nor is weston-terminal
<sicelo> yes, my d4 3d accel has been slow since last update (as well as that ti343x issue)
<tmlind> sicelo: right, but it occured to me that if termite was using xwayland then the issue should not happen with weston-terminal.. but the issue is there for sure too with weston-terminal
<tmlind> i think termite can use both xorg or wayland depending on the env
<sicelo> possible. when i used sway and weston on N900 (where i used termite), i was specifically disabling xwayland support ...
<sicelo> (i thought xwayland would add overhead for N900) ;-)
Twig has quit [Ping timeout: 256 seconds]
<freemangordon> ok, something in the kernel
<freemangordon> with 'my' kernel fps are back to normal
<freemangordon> it is kernel config though, not kernel as such
zhxt has quit [Quit: Leaving]
<sicelo> what's the offending config?
<freemangordon> no idea
<freemangordon> it is just that kernel in repos is build with different config
<tmlind> some debug option?
<freemangordon> no idea
<freemangordon> lemme compare
<tmlind> make savedefconfig for both, then diff -u
<freemangordon> umm... I will diff /proc/config.gz stuff
<freemangordon> I would bet on CONFIG_COMPACTION=y
<freemangordon> missing in repo kernel
<freemangordon> so device idles faster
<freemangordon> tmlind: what do you think^^^?
<freemangordon> hmm, this is crazy
<freemangordon> after a reboot fps is back to normal
<freemangordon> sicelo: how do you know 3d is slower for you?
<sicelo> e.g. switching between desktop is noticeably laggier than before
<sicelo> *desktops
<freemangordon> what desktops?
<sicelo> desktop 1, desktop 2, etc. not sure how to describe them :-)
<freemangordon> in hildon-desktop or where?
<sicelo> yes, h-d
<freemangordon> how do you "switch"?
<freemangordon> scroll?
<sicelo> desktop = where desktop widgets stay in h-d
<freemangordon> ok, but how do you "switch"?
<sicelo> so you switch by swiping desktop left or right
<freemangordon> ok, so you "scroll"
<freemangordon> :)
<sicelo> hehe,
<freemangordon> hmm, this is weird, this should render with 54 fps
<freemangordon> do you want to measure the fps?
<sicelo> i can test in a proper way, if you tell me how to
<freemangordon> ok
<sicelo> otherwise nearly every interaction definitely lags for me
<freemangordon> /usr/sbin/dsmetool -k /usr/bin/hildon-desktop
* sicelo boots leste
<freemangordon> CLUTTER_SHOW_FPS=1 maemo-summoner hildon-desktop.launch
<freemangordon> but before that, which xorg driver is in use?
<freemangordon> you said you had issues with pvr blobs package
<freemangordon> how did you solve that?
<sicelo> mmm, xorg not starting after my last tries :-P
<freemangordon> sicelo: sudo apt-get install xserver-xorg-video-omap=0.5.0+2m7.4
<freemangordon> ugh
<freemangordon> the one in -devel is broken
<freemangordon> lemme fix it
<tmlind> freemangordon: weird so if CONFIG_COMPACTION=y makes the fps go back to normal, we need to add some pmqos limit somewhere
<freemangordon> tmlind: no, it was a reboot that made them go back to normal
<freemangordon> no idea what was it
<freemangordon> the same kernel now gives glmark 62
<tmlind> oh ok even stranger
<freemangordon> yeah
<Wizzup> freemangordon: it should not pull ti343x for sure
<sicelo> freemangordon: heh, fps between 2 and 5. i guess my accel is completely broken then?
<freemangordon> yeah, the issue was that -experimental was not pulled in -devel
<freemangordon> sicelo: sure
<freemangordon> wait 5 minutes
Pali has joined #maemo-leste
<freemangordon> sicelo: CI is building it
<Wizzup> freemangordon: wait you need CONFIG_COMPACTION for higher fps??
<freemangordon> no
<freemangordon> I was thinking that was the case, but after a reboot fps is back to normal
<freemangordon> NFC what was that
<freemangordon> Wizzup: so, I got low fps with kernel in the repo
<freemangordon> then I boot my zImage which differs by only config options with the repo one
<freemangordon> and it performed just fine
<freemangordon> then I compared configs and the only suspicious one was CONFIG_COMPACTION
<freemangordon> then I boot repo kernel again, but this time fps were ok
<freemangordon> so false alarm
<Wizzup> freemangordon: maybe it's me enabling cma
<Wizzup> ok
<freemangordon> no, it works fine ever since
<Wizzup> ok
<Wizzup> freemangordon: do you have leste-config-droid4 and hildon-meta-droid4
<freemangordon> I think yes
<Wizzup> that is maybe why you got ti343x
<Wizzup> ok
<Wizzup> (if you don't have it)
<freemangordon> no, I get it because of omap xorg driver
<Wizzup> ok
<freemangordon> the version in -devel is higher than the version in -experimental
<freemangordon> but code-wise it is older
<Wizzup> I'll check it out, I'm trying to get rid of a headache this morning :D
<Wizzup> freemangordon: oh so I forgot to bump
<freemangordon> no need (to check out) I am already on it
<freemangordon> Wizzup: no, you forgot to pull
<Wizzup> ok
<Wizzup> weird
<freemangordon> experimental in devel
<Wizzup> the branches here all point to the same commit
<Wizzup> [maemo/beowulf-devel] [maemo/beowulf-experimental] {origin/maemo/beowulf-devel} {origin/maemo/beowulf-experimental} <0.5.0> PVREXA: add some more framebuffer flush points
<freemangordon> no idea, bu on github devel was 2 commits behind experimental
<Wizzup> hm
<freemangordon> maybe you didn;t push
<freemangordon> Wizzup: no, you didn;t pull
<freemangordon> your code lacks 2 commits
<Wizzup> ok
<Wizzup> pls fix :)
<freemangordon> already did
<freemangordon> building atm
<freemangordon> sicelo: do you have -experimental enabled?
<sicelo> yes
<freemangordon> apt update/upgrade then
<sicelo> on it
<sicelo> done. still getting 5fps. let me reboot perhaps
<freemangordon> sicelo: also, make sure you have meta installed
<freemangordon> leste-config-droid4 and hildon-meta-droid4 that is
<sicelo> right. hildon-meta-droid4 was missing
<freemangordon> sicelo: I would guess your xorg.conf is wrong or broken too, but lets see
<freemangordon> most-probably you use modesetting without glamor
<freemangordon> to have 2-5 fps
uvos has joined #maemo-leste
<sicelo> now seems snappy again :-)
<sicelo> let me try the fps readout
<freemangordon> :)
<freemangordon> should be 52-53
<sicelo> what's the current xorg.conf file? i recall there were some changes in location, etc.
<freemangordon> /usr/share/X11/xorg.conf.d
<freemangordon> 99-omap
<freemangordon> why do you need that?
<freemangordon> there is nothing in there realyl
<sicelo> wanted to check because you said it's possible my xorg.conf is wrong or broken wrt modesetting/glamor
<freemangordon> no need
<freemangordon> if it is snappy, then it is using the correct xorg.conf file
<sicelo> i got 67 once, but mostly i'm in the 40s. i guess this is correct
<sicelo> thanks for the help.
<Wizzup> freemangordon: is the tearing fixed?
<freemangordon> no :(
<freemangordon> sicelo: hmm, no
<freemangordon> not correct
<freemangordon> you should get > 50
<freemangordon> what version is xserver-xorg-video-omap ?
<sicelo> xserver-xorg-video-omap 0.5.1+2m7
<Wizzup> freemangordon: so regarding lima, what are the next steps, I see you want me to query for the swap behaviour, and I should file a bug report with the trace and video
<Wizzup> what else, should we try the partial update khr extensions?
<Wizzup> enunes hinted at that
louipc has left #maemo-leste [bye]
<Wizzup> also:
<Wizzup> If your UI application is compositing multiple uncompressed layers which make heavy use of transparencies, then using EGL_BUFFER_PRESERVED is probably a sensible thing to do.
<Wizzup> (from that mali blob)
<Wizzup> blog*
<Wizzup> it might make sense to use EGL_KHR_partial_update and EGL_KHR_swap_buffers_with_damage
<sicelo> i see it's offering me another update now, from devel, not experimental, https://paste.debian.net/1224713/
<Wizzup> yeah see 11:07 < freemangordon> Wizzup: no, you forgot to pull
<freemangordon> sicelo: yeah, I built for both
<freemangordon> Wizzup: I don;t really see what will we gain from using those extension
<freemangordon> lima guys should just fix their driver
<freemangordon> so, what I think are the next steps - capture another trace and a video of it and open an issue attaching those
<freemangordon> this is without setting EGL_BUFFER_PRESERVED
<freemangordon> not sure about TFP, either should work
<freemangordon> ah, you said with TFP issue is not visible while capturing a trace
<freemangordon> so no TFP then
<freemangordon> sicelo: if you do left-right-left-... swipe really fast (on same desktop) you should hit 53 fps
<freemangordon> unless somehow 3-buffer is disabled in xorg.conf
<uvos> a transition is still the better test tho
<uvos> since the swipe fps depens on how fast you swipe
<uvos> and how many icons you have
<uvos> and on ts event rate
<freemangordon> uvos: sure, but it requires ini changes
<freemangordon> otherwise I agree
<uvos> right
<uvos> sicelo's 40 fps might be entirely reasonable depending on the above factors
<freemangordon> hmm, ok
<uvos> 40 ish is about what it get on a full desktop
<freemangordon> I would expect more from pvr540 :)
<uvos> icons wise
<uvos> me too
<uvos> android is locked 60
<freemangordon> actually fps should not depend on the number of icons
<uvos> it dose tho
<freemangordon> or it does?
<freemangordon> ok
<sicelo> i think it's alright now. i just got 70 at some point
<freemangordon> that's weird as well
<sicelo> heh, what? the 70?
<freemangordon> mhm
<uvos> i get that too
<uvos> sometimes
<freemangordon> but how?
<uvos> no idea seams random
<freemangordon> I mean - it seems sometimes drm flip takes an instant
<freemangordon> instead of 6 ms
<uvos> right
<freemangordon> anyway
<sicelo> was scrolling between widget-less desktps. no idea
<uvos> but the scrolling dosent look 70 fps either way
<freemangordon> yes
<uvos> somewhere frames must be being discarded
<freemangordon> Wizzup: definitely there is some issue in lima and it has to be fixed, all devices I replay latest traces on show no issues
<freemangordon> uvos: mhm
<freemangordon> it is not smooth
<freemangordon> but I'll get back to it when we have the other issies fixed
<freemangordon> I would say it is related to tearing
<freemangordon> Wizzup: well, all devices are NV and Intel, but still
uvos has quit [Ping timeout: 250 seconds]
<tmlind> so is devel about to get updated then or a there still pending issues?
<tmlind> s/a/are/
<sicelo> it's updated. at least i have the xserver-xorg-video-omap from devel now, and it's running correctly
<tmlind> oh ok nice, i'll try to find my test device and update it then :)
* tmlind goes poking in a pile of cardboard boxes
<Wizzup> freemangordon: ok, will go, bbiab
<freemangordon> tmlind: make sure you have meta packages installed if you played with it a lot
<tmlind> heh bionic just shuts down now with no screens found after upgrade :)
<freemangordon> so, do you have leste-config-droid4 and hildon-meta-droid4 installed?
<freemangordon> or this is diifferent device?
<tmlind> need to check
<tmlind> trying to boot to m-l emergency shell
<tmlind> uvos: that worked nicely :)
<freemangordon> not for me, it should not try to start powervr service ;)
<tmlind> freemangordon: i have leste-config-bionic instead of leste-config-droid4
<freemangordon> I guess that's fine
<freemangordon> what about hildon-meta-droid4?
<freemangordon> or it should be hildon-meta-bionic?
<tmlind> yup i have hildon-meta-bionic
<freemangordon> that might be a problem
<freemangordon> uvos: Wizzup: is this updated?
<freemangordon> tmlind: so, Xorg does not start?
<freemangordon> may I have the log file
<freemangordon> or at least - what is the error there?
<tmlind> freemangordon: just a sec and i'll grep for EE
<tmlind> /var/log/Xorg.0.log or some other one?
<freemangordon> try to start Xorg
<freemangordon> and then provide /var/log/Xorg.0.log
<tmlind> just run Xorg manually in the emergency shell or some other way?
<freemangordon> yes, just run it
<freemangordon> tmlind: hmm, wait
<freemangordon> what is mesa version you have installed?
<freemangordon> d4 wants libegl-mesa0 (>= 21.2.5)
<freemangordon> and sgx-ddk-um-libs
<tmlind> dpkg -l | grep libgl only returns libegl1-sgx-omap4
<freemangordon> yeah, that's the issue
<freemangordon> tmlind: please install libegl-mesa0
<freemangordon> and sgx-ddk-um-libs
<tmlind> ok will do, need to start wpa_supplicant and wlan0 first
<Wizzup> tmlind: I did not test bionic yet with 5.15
<freemangordon> and libegl1 libgles1 libgles2
<Wizzup> maybe the pkg doesn't pull the sgx ddk stuff
<freemangordon> :nod:
<Wizzup> I kind of assumehoped that uvos tested it
<Wizzup> droid3 works with droid4 meta installed
<Wizzup> ... :)
<freemangordon> meta does not pull upgraded mesa/sgx libs
<Wizzup> yeah I installed the droid4 meta
<Wizzup> I can probably clean this up in ~20 mins or so
<freemangordon> please do when you have time, I am going on a walk
<freemangordon> ttyl
<tmlind> Wizzup: ok, any easy way to start wlan0 in emergency shell or just manually start wpa_supplicant and dhclient?
<freemangordon> maybe start icd2
<tmlind> ok
<freemangordon> if you have autoconnect enabled
<freemangordon> not sure it will start though
<tmlind> yup
<freemangordon> but you can try
<freemangordon> I think you need those https://pastebin.com/p2zqd6JY
<tmlind> heh tries to start xorg and shuts down
<freemangordon> :(
<sicelo> i was starting wpa_supplicant by hand, then using wpa_cli
<freemangordon> I do that too when I have to recover
<freemangordon> but, I have conf file with my AP and password :)
<freemangordon> so the only thing I need is ctrl-R :p
<sicelo> ;-)
<sicelo> iwd people will say switch
<freemangordon> what to? iwd?
<sicelo> yeah :p
<freemangordon> never used, is it better?
<freemangordon> or some NIH syndrome?
<sicelo> ymmv. i'm using it now on my laptop. its cli is definitely easier/friendlier than wpa_cli. other than that, personally don't see much benefit
<sicelo> but they say power savings, making it more suitable for mobiles
<freemangordon> I see
<freemangordon> anyway, I am going on a walk, bbl
<Wizzup> sicelo: what power savings
<Wizzup> tmlind: fwi with -D you can start services without starting dependecies
<Wizzup> tmlind: so /etc/init.d/dsme start
<Wizzup> and then
<Wizzup> /etc/init.d/icd2 start -D
<Wizzup> (or just icd2 -l0 &)
<tmlind> ok
<tmlind> icd2 fails to starat with /tmp/session_bus?address.user not there
<sicelo> Wizzup: https://wiki.gentoo.org/wiki/Iwd (fast network discovery, and better roaming definitely NOT what i've experienced so far ... unless it's debian or hw issues that affect me)
<sicelo> as for the battery/power savings, "battery life (kernel crypto framework is more efficient than wpa_supplicant)" from https://gitlab.com/postmarketOS/postmarketos/-/issues/45
<Wizzup> tmlind: /etc/init.d/dbus-user start
<tmlind> ok
<Wizzup> sicelo: seems mostly not relevant, that's only valid when actually doing lots of rx/tx
<Wizzup> tmlind: btw I assume your icd2 is set to automatically connect?
<Wizzup> tmlind: sorry for the pain btw, I'll try to fix the droid3 and bionic meta
<Wizzup> hm actually it looks like I did have the bionic3 already with some of these packages
<tmlind> no problem, just a pain to try to fix using the emergency shell
<tmlind> bad battery too, so uart is only somewhat usable..
<tmlind> i'll let the battery charge up, then retry
<tmlind> Wizzup: now /etc/init.d/icd2 start -D produces openrc error bad variable name
<Wizzup> huh
<Wizzup> that sounds like something is corrupted almost
<tmlind> 1: export: directory:: bad variable name
<Wizzup> huh yeah that's weird..
<tmlind> oh well i'll start it manually when i have a serial console and don't need to deal with the vkb
<Wizzup> mhm
<tmlind> uhh this xorg not working and shutdown when things go wrong is just annoying :(
<tmlind> can't even install packages without system shutting down automatically
<Wizzup> tmlind: can you check what sgx-ddk-um-ti is installed
<Wizzup> dpkg -l | grep sgx-ddk-um-
<Wizzup> tmlind: if you don't want it to reboot, just touch this file
<Wizzup> touch /etc/no_lg_reboots
<Wizzup> tmlind: ^^
<tmlind> ok
<Wizzup> I guess for 'end users' it is probably better than phone reboots if X crashes
<Wizzup> for developers it's mostly annoying :)
<Wizzup> sicelo: did you see there are N810 patches for pwm and led on linux-omap? fun
<sicelo> yeah, i love that work :-)
<sicelo> interesting - when my xorg wasn't starting, i didn't get system shutting down. instead it just dropped me to a shell after a short while
<sicelo> ah, i do have no_lg_reboots, although i don't remember when i set it :p
<tmlind> heh started getting battery low warnings while using serial console but got the charger in in time :)
<Wizzup> in dmesg or from ui?
<tmlind> dmesg
<Wizzup> mhm
<tmlind> still in emergency shell and installing the needed packages now
<Wizzup> which ones were missing for you
pere has quit [Ping timeout: 256 seconds]
inky has quit [Ping timeout: 256 seconds]
inky_ has joined #maemo-leste
<tmlind> it's pretty messed up right now, can't configure hildon-desktop because xorg still won't start, need to continue later, gotta go now ttyl
_inky has quit [Ping timeout: 256 seconds]
_inky has joined #maemo-leste
<Wizzup> tmlind: I'll check bionic, I just upgraded my droid3 and added the right meta and it works for me
<Wizzup> it seems to get stuck on reboot sometimes though (when shutting down)
<Wizzup> I bet this is related to the serial panics
pere has joined #maemo-leste
<Wizzup> s/panics/oopses/
<freemangordon> Wizzup: BTW, do we already support those tablets you gave me?
<freemangordon> what the? PP battery discharged while being out of the device
Danct12 has quit [Quit: Quitting]
inky has joined #maemo-leste
inky_ has quit [Ping timeout: 256 seconds]
freemangordon has quit [Remote host closed the connection]
freemangordon has joined #maemo-leste
<freemangordon> same black screen as yesterday, it turned out GPU cooling fan had been stuck :)
<freemangordon> hmm, pinephone image does not boot
<freemangordon> Wizzup: ^^^
<freemangordon> well, I get to login prompt, but can;t do much there
<freemangordon> hmmm
<freemangordon> false alarm
<freemangordon> I wrote the image for the second time and now it boots
<mighty17[m]> <mighty17[m]> "Any clues why this happens, when..." <- Bump :(
<freemangordon> hmm, very strange behaviour om PP with kernel from -devel
<freemangordon> brightness constantly changes
<freemangordon> and device seems to become very hot
<freemangordon> this is some 5.14-rc1
inky has quit [Read error: Connection reset by peer]
inky has joined #maemo-leste
inky has quit [Read error: Connection reset by peer]
inky has joined #maemo-leste
<Wizzup> freemangordon: rafael2k is working on new kernel
<Wizzup> freemangordon: no, those tablets do not have working panel (bridge) yet
Danct12 has joined #maemo-leste
<Wizzup> freemangordon: the kernel is ok for me
<Wizzup> idk about als/brightness
xmn has joined #maemo-leste
inky_ has joined #maemo-leste
amk has quit [Ping timeout: 256 seconds]
inky has quit [Ping timeout: 240 seconds]
amk has joined #maemo-leste
inky_ has quit [Remote host closed the connection]
inky_ has joined #maemo-leste
inky_ has quit [Client Quit]
inky_ has joined #maemo-leste
<freemangordon> Wizzup: it is not als, it does it even before h-d has started
pere has quit [Ping timeout: 240 seconds]
<freemangordon> at least that's my understanding
<Wizzup> freemangordon: als/mce runs before hd fwiw
<Wizzup> but yeah if it is before mce...
pere has joined #maemo-leste
<freemangordon> I stopped mce and it continues
<freemangordon> blinking that is
<freemangordon> kernel issue, I downgraded to 5.10.0-1+2m7.1 in it is gone
inky has joined #maemo-leste
inky_ has quit [Ping timeout: 268 seconds]
<Wizzup> freemangordon: ok
<rafael2k> ow yeah, kernel packages ready
<rafael2k> the repo should be fine
<rafael2k> I'll finish up ofono repo soon, I will just wrap a missing glib function and it will be ready for maemo upstreaming
<tmlind> Wizzup: getting closer to a working system, now missing XDG_RUNTIME_DIR /run/user/1000
<tmlind> rebooted, let's see, looks like desktop starts at least
<tmlind> ok updated, bbl
<rafael2k> btw, I realize the kernel is installed correctly, but the default initrd and Image.gz are not updated automagically - is this done somewhere else?
<freemangordon> "maemo upstreaming" yay!
<rafael2k> ; ))
inky_ has joined #maemo-leste
inky has quit [Ping timeout: 240 seconds]
<rafael2k> yaaay!
<rafael2k> I have my battery level back!
<rafael2k> ; ))
<rafael2k> for the first time since I don't remember when
<rafael2k> .dtb are not being copyed too... I need to check the debian/ ... I had to do some tweaks as default maemo pp debian dir did not work out-of-the-box
<rafael2k> Linux devuan-pinephone 5.15.10 #1 SMP Sat Dec 25 10:36:14 MSK 2021 aarch64 GNU/Linux
<rafael2k> now rebooting to see how X with accell is going on
<rafael2k> just need to sort out setting the default kernel, initrd and dtbs
<rafael2k> My eg25-manager patch to make it compile without mm also went upstream
inky has joined #maemo-leste
inky_ has quit [Ping timeout: 256 seconds]
DPA has quit [Ping timeout: 265 seconds]
<rafael2k> X is better, not perfect, but way much better... thanks for the all the work -
<Wizzup> rafael2k: we-ll fix the other bug soon
<Wizzup> :)
<rafael2k> there is some work to do kernel side in pp, especially some firmware (like https://github.com/dragan-simic/ov5640-autofocus-firmware/ for camera), audio needs other tweaks (now there is hdmi also and new stuff), but all in all, things are getting better
<rafael2k> Wizzup: yay!
DPA has joined #maemo-leste
Langoor has joined #maemo-leste
<rafael2k> alsa is working great through mplayer specifying the hw:0, but all ucm2 config is trashed in the new kernel, need to re-do the audio configs to match the new kernel audio feats
<rafael2k> not only ucm2, but standard alsa configs are not ok in the new kernel (it was not totally ok before... now they just do not work out-of-the-box)
<rafael2k> *with the new kernel
<rafael2k> ofono is ready to go production: https://github.com/rafael2k/ofono
<rafael2k> For people with pp, who want to test new ofono packages: http://173.255.215.196/pinephone/ofono-packaging/