libera/#maemo-leste/ Friday, 2025-03-21

siceloWizzup: so in arm-sdk, i see a function for building the kernel for a device. and i also see the kernel exists as a standalone package. how does this work? or the function in arm-sdk is not used?11:01
siceloat least n900 in arm-sdk looks like it would build old kernel ... so i guess that's not used?11:03
Wizzupsicelo: we don't use arm-sdk way to build kernel11:13
Wizzupthat's a devuan-only thing11:13
Wizzupew just build a package and install/depend on it during out bootstrap11:13
siceloah, ok11:16
Wizzupdo you need help with l5 things?11:18
halftuxWizzup: what is the helper command to use with the arm-sdk is it build_image_dist or build_arm_dist?11:42
sicelobuild_arm_dist11:43
halftuxis the arm64-generic build already fixed?11:44
Wizzuphalftux: let me check @ generic11:55
Wizzuphttps://phoenix.maemo.org/view/Images/job/leste-image-arm64generic/6/11:55
Wizzuplooksl ike it's not set to auto build, heh11:55
Wizzupwe can also make a daedalus one if this passes11:58
halftuxsure fine with me11:58
halftuxso the kernel needs a device specific package. Is there also a package for the device tree files?12:00
sicelothe dts is generally part of the kernel package12:03
Wizzupyes, this is leste-config-xyz12:04
Wizzupoh, the device tree is part of the kernel12:04
Wizzuphonestly when it comes to specific kernel stuff I'm hoping we could just merge the support into a single kernel package since they are a pain to maintain, do you have a link to a kernel tree and config somewhere?12:04
sicelowhat do you mean by single kernel package?12:06
Wizzupnot to have a kernel per device, but a kernel for multiple devices12:07
Wizzuplike we have a single one for all our omap devices, ideally we'd also have a single one for arm64 devices12:07
Wizzupand we could extend the omap kernel to other 32 bit devices12:07
Wizzupwe modify builddeb scripts in kernel, so it's not a bunch of extra work12:08
sicelounfortunately that can clash. even within omap, for some reason d4 doesn't want kernel with THUMB, and we would like to have it for N900. as a result, we currently have it disabled for N90012:08
siceloanyway, for L5 i prefer this kernel, https://salsa.debian.org/Mobian-team/devices/kernels/librem5-linux, and it's the one I've been testing with so far ... unless halftux prefers something else12:09
Wizzupfor things that need their own kernel we will do it of course12:10
WizzupI don't know what halftux is working on, I assumed (maybe wrong) raspi12:10
siceloL5 as well, afaik :-)12:13
Wizzupok12:17
halftuxI only wanted to know how everything works in general to add maybe new devices by myself. I have odroid c4 in mind and yes I have L5 and raspi2-5 at home12:46
halftuxwhen I tried to build the raspi 3 and 4 it arm-sdk builds an old kernel from raspi git so I guess I need to remove this custom build and provide a package12:48
halftuxfor odroid c4 I am looking atm at armbian how they build the kernel, many patches are involved12:54
halftuxhttps://github.com/armbian/build/tree/main/patch/kernel/archive/meson-6.1212:59
Wizzuphalftux: yes, it would be great to get a proper kernel for the raspis13:08
Wizzupideally just mainline13:09
WizzupI would suggest to start with raspi over odroid-c4, since it is hopefully easier and more impactful13:10
halftuxok checkout daedalus image-builder and running arm64-generic then trying to get raspi4 mainline kernel running on it13:51
Wizzupcool :)13:58
Wizzupfreemangordon: this is not something we'd want to work on now, but nlnet is asking if I know what it would take to move us to gtk314:33
Wizzupas far as I know we got quite far, even have the input module working, but we don't have the theming working yet, which I think in turn made us not move forward, we might be missing some fremantle specific widgets too.14:34
arno11Wizzup: AI could help a lot imo14:54
Wizzuparno11: with what, themes?14:56
arno11idk exactly for theming but i asked leste assistant, seems able to directly convert gtk2 code to gtk3.14:58
arno11if you have specific example to provide and test, i can try14:59
Wizzupthe challenge isn't really porting gtk2 to gtk3, it's the fact that we have themes, widgets, etc that need to be ported14:59
Wizzupto a different plugin architecture at that14:59
Wizzupsome of this work was done already, but it's not like 'port this gui application from gtk2 to gtk3'14:59
arno11i understand that15:00
arno11i just mean: gtk2 to gtk3 sounds like a monumental work for just few devs with not a lot of spare time.15:08
Wizzupyup, hence not a now thing, but having an idea of how much work it would be is helpful15:09
Wizzupand nlnet might offer to fund some of the work15:10
arno11i see.15:10
inkyWizzup, i guess no hope for rafael to do that in close time, i think if you pull the pinephone kernel and send to phoenix, updated one will work, i can test, my pp is on devel.15:20
Wizzupjust a test15:50
Wizzuphttps://git.maemo.org/merlijn/test-bugtracker15:50
Wizzupoh, ha, it didn't copy the issues15:50
Wizzuplet me retry xD15:50
halftuxerror in: strapdir to image no space left on device15:54
halftux/dev/loop0p2 2.7G used 2.7G15:55
halftuxwhen trying to build generic arm64 with daedalus15:55
Wizzuphalftux: I have a fix for this, let me see15:57
Wizzuphalftux: edit arm-sdk/boards/arm64-generic.sh and change size=300015:57
halftuxyour bugtracker is brewing me a green coffee15:57
Wizzupmake it size=400015:57
halftuxok15:58
Wizzuphalftux: yeah it's still migrating15:58
Wizzupit's supposed to be a copy of the github bugtracker15:58
halftuxor better it is a green tea15:58
Wizzupgitea15:58
Wizzuplooks like the chimaera arm64 generic 64 build passed16:00
arno11yes indeed16:00
Wizzupshall I build a daedalus image on ci as well (try to?)16:00
Wizzuphttps://phoenix.maemo.org/view/Images/job/leste-image-arm64generic-daedalus/16:02
halftuxhmm now I am getting failure resolving maedevu.maemo.org but in another terminal I could ping the server16:04
halftuxchroot-script-intern fourthstage16:06
Wizzupcould be a temporary issue?16:06
Wizzupoh, there is one part where that does happen, but it should not be fatal16:06
Wizzupthat gitea migration is surely taking a while16:07
Wizzuplol, just as I said that it finished16:08
Wizzuphttps://git.maemo.org/merlijn/test-bugtracker/issues/75116:08
Wizzuphttps://git.maemo.org/merlijn/test-bugtracker/issues/76616:09
Wizzup(some examples)16:09
Wizzupthe milestones are there too: https://git.maemo.org/merlijn/test-bugtracker/issues?type=all&state=open&milestone=10&project=0&assignee=016:10
arno11cool, really similar to github16:11
arno11i mean, the ui16:12
Wizzupyeah16:12
WizzupI will see if folks can use their github account to log in too, at least for say reporting issues and such16:12
arno11ok16:13
WizzupI guess maybe the next step is to migrate some repos en masse16:14
Wizzupjust to see what it looks like16:14
arno11yeah16:15
freemangordonWizzup: we will have to port libhildon to gtk316:17
freemangordonporting hildon-desktop should be trivial, AFAIK16:19
freemangordonhowever, this port cannot be done as a one-shot task16:20
freemangordonwe shall do on phases16:20
Wizzupyes, but what would the phases look like I am wondering16:30
freemangordonlibhildon3 is the first one16:31
WizzupI think we already have that building16:31
freemangordonthen themes16:31
freemangordonbut no idea how complete it is16:31
Wizzupwell16:37
Wizzupthat depends on how we do it16:37
WizzupI don't think we should try to parse gtk2 themes and make them work in gtk316:37
WizzupI think we just need to make themes thegtk3 way16:37
Wizzupwhich is html/css style, rather than small bit maps16:38
Wizzupin which case we just need to ... make them16:38
Wizzupor we have to write code to parse/understand gtk2 pixmap themes and somehow render them in gtk316:38
Wizzupbtw, random example repo: https://git.maemo.org/merlijn/alarmd16:38
Wizzupoh it's private,sec16:39
Wizzupfixed16:40
arno11works fine16:41
WizzupI think some migrations are not ok16:45
Wizzuphttps://git.maemo.org/merlijn/hildon-status-menu16:45
Wizzupthis seems to have used whatever we forked it from16:45
Wizzupnot https://github.com/maemo-leste/hildon-status-menu16:46
arno11lot of branches are missing16:46
arno11ah yeah even master is wrong16:48
Wizzupsame here16:49
Wizzuphttps://github.com/maemo-leste/libconic16:49
Wizzuphttps://git.maemo.org/merlijn/libconic16:49
Wizzup'original_url': 'https://github.com/fremantle-gtk2/libconic.git'16:49
Wizzupthe problem is that our repos seem to be 'forked' from fremantle-gtk216:49
arno11same for h-s-m16:50
Wizzupyeah a bunch I bet16:51
WizzupI stopped the mass test import for now16:51
dsc_does it import users too16:54
dsc_and issues16:54
dsc_well, mock users16:54
dsc_else nobody can ever register, unless gitea can merge that16:55
dsc_btw Gitea has this really annoying 'archiving' feature (that I dont really understand) that loves to fill your HDD until it is full16:56
dsc_it has a job for that16:56
dsc_please look into `cron.archive_cleanup` and `cron.delete_repo_archives` config options16:57
dsc_because it will 100% kill the instance lol16:58
dsc_(speaking from experience)16:58
Wizzuphold up16:58
WizzupI already linked some examples and the test-bugtracker clearly shows the comments/issues imported from github16:58
Wizzupbut that is not the issue here16:59
Wizzupthe issue is that gitea seems to 'follow' github's fork network16:59
Wizzupso it's not cloning say github.com/maemo-leste/libconic16:59
Wizzupbut rather github.com/fremantle-gtk2/libconic16:59
Wizzupor even fremantle-gtk3/libconic in this case17:00
dsc_strange17:00
dsc_why would it follow17:00
Wizzupno idea, but that's what it seems to do, at least with the script that I used17:00
Wizzuplet me try manually for libconic17:00
Wizzupwhen I do it manually it seems better https://git.maemo.org/merlijn/libconic17:01
arno11indeed, better17:03
arno11at least, all branches seem there17:03
Wizzupmabye the github api returns the wrong urls17:03
Wizzupyeah I see it17:07
WizzupI'll fix it in a bit17:07
arno11able to see history commits but just from a folder or a file. no way to see full history17:10
Wizzupcan you share a link17:13
arno11*from the website, works from command line17:16
arno11a link about what ?17:19
arno11ah you mean showing commits history ?17:20
Wizzuphttps://git.maemo.org/merlijn/libhildonfm/commits/branch/master/configure.ac17:22
Wizzuphttps://git.maemo.org/merlijn/libhildonfm/commits/branch/master17:22
arno11ah yes :)17:26
WizzupI added a few more repos, they look better now17:26
arno11cool17:27
Wizzup(ofc we wouldn't have this under /merlijn/, just testing)17:27
arno11yes ofc17:27
Wizzuptrying hildon-desktop now to see if it migrates both open and closed prs17:28
arno11can't see any prs17:31
arno11*in /merlijn/hildon-desktop/issues17:32
arno11scratch that17:33
arno11/merlijn/hildon-desktop/pulls is ok17:33
arno11similar to github17:34
Wizzupcool17:34
Wizzupit's impressive, really17:34
Wizzuphttps://git.maemo.org/merlijn/hildon-desktop/pulls?type=all&state=closed&milestone=0&project=0&assignee=017:34
mkfhello.17:37
mkfi've (finally) managed to get that android tablet running once again17:37
mkfit's touch rougly works now, albeit it's still bit off.17:37
mkfis there any way to calibrate it? i'm using firmware from android, but it's flakey.17:38
freemangordonhmm, are you sure you use the correct FW?17:40
freemangordonplease check in fex17:40
freemangordon(or whatever that strange format was called)17:41
mkfyes, sys_config.fex apperently uses that fw17:42
freemangordondoes it work properly under android?17:42
mkfand for all fws inside that rom, this one behaves works best17:42
mkfyes, this works fine in android.17:42
freemangordonhmm, could be driver issue then17:42
mkftho, it's not the stock rom this device shipped with, but touch works fine in this rom dump.17:43
freemangordonsorry, can;t help with calib17:43
mkfno problem. would xinput_calib work? i've tried it but not sure if it worked17:43
WizzupI think xinput calibrator doesn't work if libinput is used (IIRC), but should work for other things17:44
Wizzuparno11: btw, jfyi (since you're watching this), it looks like the mass importer still doesn't actually properly import MRs and such17:45
Wizzupbut when I do it through the UI it does :D17:45
mkfi see. do beowulf images use libinput?17:45
mkf(i'm using old sunxi image until i manage to get usb and touch running, it's a bit easier to debug with those.)17:46
arno11Wizzup: ah ok17:47
sicelomkf: i saw this some weeks ago, https://github.com/kreijack/xlibinput_calibrator ... worth a try17:49
mkfsicelo: thanks. compiling it atm :D17:49
mkfgod bless qemu authors, they surely made lives easier.17:49
Wizzupmkf: no they should not, beowulf is also really old fwiw17:52
WizzupI know you know, but like, we might not remember the status of things on beowulf17:52
mkfhow can i check? also, how can i upgrade?17:55
mkfit says using input driver libinput for silead_ts17:56
mkf(Xorg.0.log)17:56
halftuxmaybe input_set_abs_params could help for ts problem17:58
Wizzuparno11: ok, found the issue, the script I am using does not pass along my token to gh so it can't pull in the other stuff, will test fix17:58
arno11ok cool18:00
mkfsicelo: xlibinput_calibrator fixed it. \o/18:03
sicelolovely18:19
Wizzuparno11: k, fixed, will continue with this later, let me see if I can figure out a fix to the fstab thing now18:55
arno11Wizzup: oh great19:32
arno11i think there is a commit to revert19:32
arno11commit 621d8ca in arm-sdk, no ?19:34
mkfis gconf problem solved?19:37
Wizzupmkf: in daeadalus, yes19:37
Wizzupand maybe in chimaera19:39
Wizzupdefinitely not in beowulf19:39
Wizzup(but you can work around it)19:39
Wizzuparno11: hm... maybre19:39
mkfi'm upgrading to chimaera.19:42
mkfdid the workaround tho.19:42
Wizzupbtw, here's the gtk3 issue we had: https://git.maemo.org/merlijn/test-bugtracker/issues/26119:50
Wizzupor milestone I guess19:50
Wizzuparno11: I think that is one part of the puzzle19:50
Wizzuparno11: we can certainly remove it and see if things just work19:51
Wizzuprevert it19:51
arno11ok, at least, from jenkins console, that seems to be the last thing which overrides fstab before the end of the build19:52
arno11but maybe i'm wrong19:52
mkfis gittea a mirror of github or complete replacement?20:10
mkfErr:1 https://maedevu.maemo.org/leste chimaera InRelease20:23
mkf  The following signatures were invalid: EXPKEYSIG 545FEC4E0927F6FD spam1@wizzup.org20:23
mkf^ any ideas?20:23
mkfinstalling maemo-keyring manually fixed it \o/20:29
arno11mkf: ATM gitea stuff is just a test20:33
arno11*with leste20:33
mkfwow, chimaera update was sure worth it, got battery indicator. :D21:30
arno11Wizzup: before building a new img, maybe we should add transitions, no ?21:54
arno11ah cool, daedalus arm64 is ok22:12
Wizzuparno11: well ... ok we don't know, but it built :)22:32
Wizzuparno11: yeah we should fix fstab and add a few more things22:32
arno11yep22:41
arno11renice xorg, mce, H-D and systemui could be useful but it works only with sudo so i've been only able to renice mce on boot22:47
arno11hmm not renice, nice sorry22:48
arno11so the problem is not sudo22:49
arno11ah now i remember22:50
arno11indeed even with nice we need sudo22:50
arno11to get prio @-8 or -922:51
arno11that's the problem22:51
arno11so atm it works on boot only with mce22:52

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!