libera/#maemo-leste/ Sunday, 2024-10-06

Wizzupfreemangordon: ugh libosso uses __malloc_hook which is now deprecated/gone00:30
sicelofreemangordon: re bq2415x: it was the positioning :-)04:41
sicelooriginally i had https://paste.debian.net/1331047/ ... i.e. i was calling `power_supply_changed()` after the call to `...update_reported_mode()`. now i call it just before.04:42
siceloreported_mode actually processes data from isp170x, not bq2415x. so what was happening is that isp fires a notification, and at that time bq2415x starts the 2s internal timer, so at this time, it reports online 0.04:44
sicelomeanwhile, reported mode has already set its state to a charging mode. a couple of seconds later, isp170x fires another event with unchanged values. i absolutely don't know where this 2nd event comes from, but you can see it in https://paste.debian.net/1331046/04:50
sicelowhen that 2nd event arrives, reported_mode simply does nothing since it already updated the mode internally during the 1st isp170x event. calling `power_supply_changed()` before reported_mode causes the bq24 properties to be rechecked every time isp170x reports an event, and thus problem solved :-)04:54
siceloon that note, uvos thanks for merging the change. would appreciate a build so we can have testing06:09
tmlindWizzup, uvos: i may have a kexecboot patch to possibly fix that oops issue, needs testing though, not sure why/if i ever pushed it out..07:37
tmlindwell looking at the description, it seems like a workaround, but might be acceptable if it helps: http://muru.com/linux/0001-kexecboot-Only-umount-the-read-only-kernel-partition.patch07:40
uvostmlind: reading the commit i dont think it helps10:31
uvostmlind: since thats exactly what happened, the device failed to kexec because the dtb was missing and then the stock kernel crashed10:31
Wizzupuvos: do you need me to kick a build for droid4-linux ?10:32
uvosso your patch dosent help here because its no change10:32
uvosWizzup: have not done the changelog10:32
Wizzupuvos: I think he's saying it might prevent the oops that followed10:32
uvosWizzup: no look at the patch10:32
uvosWizzup: it moves the unmount behind the kexec so it dosent happen at all in the happy path10:32
Wizzupok10:33
uvosin unhappy path it still happens and stil crashes10:33
sicelommm, my leste vm just broke from apt upgrade. https://paste.debian.net/1331486/10:39
WizzupI had this too recently10:39
Wizzupsec10:40
* Wizzup starts mz61710:40
Wizzupfreemangordon: it doesn't look like this mem saw stuff is used a lot https://github.com/search?q=org%3Amaemo-leste%20osso_mem_saw_enable&type=code10:40
uvosWizzup: the tiny mz617 image has the wrong leste-config10:41
Wizzupuvos: huh really?10:41
uvosi have /lib/udev/rules.d/85-input-devices.rules which is breaking my ts10:41
uvosyeah10:41
Wizzupwhich one is installed10:42
uvossec just rebooted10:42
uvosyay working ts10:43
Wizzupsicelo: try dpkg --configure gconf210:43
Wizzupuvos: dpkg -l | grep leste-config10:44
Wizzup?10:44
uvosi deleted the offending file10:44
Wizzupsicelo: maybe also dpkg --configure dbus-x1110:44
Wizzupuvos: sure but dpkg -l will still tell you :D10:44
uvoshaha10:44
uvosleste-config-common/now 1.113-1+m7 all [installed,local]10:45
uvosleste-config-mapphone/now 1.113-1+m7 all [installed,local]10:45
uvosleste-config-mz617/now 1.113-1+m7 all [installed,local]10:45
uvosleste-config-droid4/now 1.113-1+m7 all [installed,local]10:45
Wizzuphuh10:45
uvosboth d4 and mz617 is installed10:45
Wizzupvery strange10:45
Wizzupuvos: do you also get an error probing the soundcard btw, on mz617?10:45
uvosWizzup: no10:45
uvosyes10:45
uvosi mean it dosent probe10:45
Wizzup[   41.545867] mot-mdm6600-codec 4806a000.serial:modem:audio-codec@2: ASoC: error at snd_soc_component_probe on 4806a000.serial:modem:audio-codec@2: -11010:45
Wizzup[   41.605468] asoc-audio-graph-card2 soundcard: ASoC: failed to instantiate card -11010:45
uvoses10:45
uvosyes10:45
Wizzup[   41.619659] asoc-audio-graph-card2 soundcard: error -ETIMEDOUT: parse error10:45
Wizzup[   41.632446] asoc-audio-graph-card2: probe of soundcard failed with error -11010:45
Wizzupthis10:46
Wizzupok10:46
Wizzupmy thinking was that this might be responsible for not hitting RET10:46
sicelothanks. that helped10:46
uvosWizzup: btw the samall image is also lacking h-i-m10:47
uvoswhich makes it pretty hard to start wifi10:47
Wizzupuvos: I thought him was on there specifically10:48
Wizzupmaybe it doesn't start properly, or it really doesn't exist?10:48
Wizzuphm you're right10:48
Wizzuphildon-input-meta is in hildon-meta, not in hildon-meta-core10:49
uvosyeah its there10:49
uvosbut it dose you no good bacause its disabled by default and the controll pannel applet to enable it is not there10:49
Wizzupok, but once you enable it, it works?10:49
uvosmybe i dont know the gconf call on hand10:50
Wizzupok10:50
WizzupI suppose you just plugged in a keyboard10:50
uvosnot yet10:50
uvosalso the power button dosent work10:50
uvoswhich is strange because it dose work10:50
Wizzupthe power menu might not be present perhaps10:51
Wizzuphildon-meta-core is pretty trimmed down10:51
uvosdoubleclick dosent work either10:51
uvosbut power key contributes to inactivity timeout10:51
uvosstrange10:51
Wizzupif you have a way to type btw, you can install the applet from apt10:51
Wizzupassuming there's any space left :D10:51
uvosi have 100mb10:52
uvosbut catch 22 i cant go online10:52
uvosto get the applet to go online :P10:52
Wizzuphildon-meta-core has the systemui for tklock, powerkey and mode change10:52
Wizzupso it -should- be ok10:52
uvosand i cant use usb-net since then i cant type via serial10:52
Wizzupdoes it show the usb dialog if you plug in usb?10:52
Wizzupah10:52
Wizzupwell, usb net should just work no?10:52
Wizzup(for ssh)10:53
Wizzupfreemangordon: I'm considering getting rid of the libosso/src/osso-mem.c stuff at laest for daedalus, it seems to try to do some userspace oom prevention by hooking malloc, but it's only used by 1 program (hildon thumbnailer iirc)10:56
Wizzupthere is the lowmem state check but I don't think that exists on any of the modern kernels10:57
Wizzupsee https://github.com/search?q=org%3Amaemo-leste+osso_mem&type=code10:57
Wizzupuvos: how did you make the img btw?10:58
uvosi copied the contents of both mz617-tiny-bootstrap partitions to a singe parition image10:59
uvosthen i manually installed a newer kernel11:00
uvosand fixed fstab and boot.cfg to point to p18 instead of p2011:00
Wizzupok11:01
uvoswhat was the flag again to create an ext4 partition that the stock kernel can mount?11:02
uvossomething with no 64bit file offsets11:02
Wizzupgoogling shows -O ^64bit but idk if that is right11:06
Wizzuphttps://serverfault.com/questions/950704/mkfs-o-64bit-metadata-csum-t-ext4-in-201911:06
Wizzupuvos: for the image we also want no partitions right, no partition table12:06
Wizzupmz617 tiny I mean12:06
uvosboth mz617 tiny and regular12:14
uvostiny gets installed on p18 "cache" via fastboot12:14
uvosand is then used to install the full image to p20 "userdata"12:14
uvosthere is no room to have a partition table anywhere on a mapphone emmc ofc12:14
uvossince that is part of mbm12:14
uvosidealy we would build single parition images for all mapphones12:15
uvossince then you would not need a sdcard to install leste to those devices12:15
uvosyou could just fastboot flash leste to userdata (on the lest resticitve bootloaders anyhow)12:15
Wizzupright, agreed12:16
WizzupI'm trying to make the changes to libdevuansdk now12:16
Wizzupit doesn't support not having a partition table but I'm adding that now12:16
uvosa problem with doing this atm is btw that kexecboot requires boot.cfg and the kernel to be in /boot12:16
uvoswhile we mount boot to /boot12:16
uvosso the packages install stuff to /boot/boot12:16
Wizzupyes12:16
uvoswe could just have the image builder link /boot/boot to boot for now i gues12:17
Wizzupor have a different /etc/fstab12:17
Wizzupwe can just not mount boot12:17
uvosno we cant12:17
uvosthe package installes to /boot/boot it will do that in the single partition12:17
uvosbut thats no use12:17
uvosbecause kexecboot will open that partition look at /boot not find /boot/boot.cfg and continue on12:18
uvosit only works atm because /boot on the root partition is a mount to a different partiton where /boot/boot.cfg dose exist12:18
uvosso kexecboot finds it there12:18
uvosso kexecboot finds it there12:19
Wizzupok12:29
Wizzupuvos: ok, think I'm mostly there with the image builder13:20
Wizzupyeah, got an image without partitions, size 747M13:33
Wizzupbtw, I think we should try to upgrade our raspi images to whatever debian does on raspi13:36
Wizzupuvos: what size should I make the image again for mz617?13:43
Wizzup23:09 < uvos> the only partition flashable via fastboot that is large enough is cache at 850 ish mb13:55
Wizzupok13:55
arno11Wizzup: nice @raspi. btw i tried several img's few weeks ago and that's totally broken iirc14:11
Wizzupyeah probably14:12
arno11back @home in 2 weeks, then i can try new img if needed on both pi3 and pi414:14
Wizzup/dev/loop0      800M  450M  319M  59% /mnt/extern14:20
Wizzupbtrfs zstd:15 compression :)14:20
Wizzupvs ext414:21
Wizzup/dev/loop1      771M  747M     0 100% /mnt/extern_114:21
uvos/dev/mmcblk1p18                                                1732608                         3694591                         1961984                         958M Microsoft basic data14:40
uvos    /dev/mmcblk1p19                                                3694592                         5128191                         1433600                         700M Microsoft basic data14:40
uvos    /dev/mmcblk1p20                                                5128192                        31047679                        25919488                        12.4G Microsoft basic data14:40
uvos(Device                                                           Start                             End                         Sectors                         Size Type)14:41
uvosWizzup: so netxt problem i have is that the locale is all wrong14:47
uvosWizzup: freemangordon: please kick the kernel15:32
Wizzupok15:37
Wizzupuvos: experimental or what15:37
uvosdevel15:37
Wizzupuvos: so shall I aim for 700M or 958M ?15:37
Wizzupwith btrfs compression 700M is easily doable15:37
Wizzupmerlijn@gentoo-x13 /mnt/extern $ sudo du -sh .15:37
Wizzup751M.15:37
Wizzupmerlijn@gentoo-x13 /mnt/extern $ df -h .15:38
WizzupFilesystem      Size  Used Avail Use% Mounted on15:38
Wizzup/dev/loop0      800M  450M  319M  59% /mnt/extern15:38
Wizzupseems like 700M might be better15:41
uvoscache is the 900MB parititon15:49
uvosp1815:49
Wizzupuvos: right, but I also saw a 700mb one16:18
Wizzupuvos: ok I will investigate why the droid4 leste-config was there and send oyu an image if you're up for it17:18
Wizzupissuing kernel build17:19
uvosthe 700mb is the other flashable partition: cdrom17:47
uvosobviously we want kexecboot on the smaller of 2 flashable partitions17:47
uvosWizzup: sure i have leste on p20 now so im open to trying things on p1817:47
sicelotysm @kernel build17:51
sicelothose mapphones (i assume mapphone?) don't have sd card slots?17:51
uvosno the mz61x variants either have sdcard or a modem but never both at the same time17:52
siceloi don't know much about mapphones ... they didn't really land in these parts. only motorola of those days that i think i ever saw was the photon q, or some other that looked similar17:53
siceloLeste's D4 that I have is probably the only D4 in all the 9 or 10 SADC countries :p17:54
siceloah yeah, it was Motorola RAZR. Not sure which variant specifically, since I see a few on gsmarena17:57
Wizzupuvos: doesn't my mz616 have both?17:58
uvosWizzup: nope17:59
uvosWizzup: mz615 has sdcard and mz616 has modem17:59
Wizzupwell this tablet has a sim slot and a (working) sd card slot\18:02
WizzupI haven't tested the sim slot I suppose18:02
uvoshmm18:03
uvosat18:03
uvosthe very least no lte version also has sdcard18:03
Wizzupright18:04
Wizzupuvos: so don't hit RET either on mz617 right?18:11
Wizzupyou don't*18:11
uvosno18:11
uvosit never has for me18:12
uvos(also minimal linux root)18:12
Wizzupok18:12
Wizzupmy suspicion is the audio but I'm not sure18:12
uvosWizzup: do you have any mz617-32 variants?18:32
uvosor any mz61x-3218:32
WizzupI will check18:45
Wizzup(after dinner)18:45
sicelofun, the charger uevent isn't working properly in the leste kernel, but works 100% in 6.10 that I was using while testing it.19:55
sicelouevent is generated alright, but here, isp170x is much faster ... and finishes everything before bq2415x finishes updating itself19:56
siceloi think our kernel is correct. anyway, no more time to play with this for a while. i will have a quick check to see what quickest solution is - probably blacklisting bq2415x again19:58
sicelowhat's a good, simple way that i can get myself setup to build leste kernel locally, as a deb?20:00
siceloi know how to build it the 'plain' way20:01
uvossicelo: in theory https://wiki.debian.org/Multiarch/HOWTO and then add the arch to the dpkg-buildpackage commend (not sure what flag use help)20:06
uvosi have never done this except to build i386 on amd6420:06
uvosbut should work, kernel has should be extra easy20:06
uvosor just build in armhf quemu20:07
uvosplease avoid submitting patches that you have not tested against the kernel in question20:08
WizzupI just use a normal cross compile fwiw20:13
Wizzupno need to build the .deb20:13
siceloWizzup: then moving modules manually between pc and device?20:15
WizzupuImage and all modules yes20:16
Wizzupjust run make modules_install with the var set so install the mods to some dir20:16
sicelouvos: sure. anyway, you won't need to revert the existing patch. it's already an improvement since we're getting an uevent when plugging in charger ... just not good enough yet20:19
uvosyou can also just directly install to the device by mounting it with sshfs20:19
uvoswhich is what i do20:19
Wizzupguys, shall I also make trixie setup now, or does that make no sense? I worry it will be hard to keep sw synced with three repos, but I can do it ofc20:27
WizzupI suppose it can't hurt to just make it work at least20:31
sicelothree? i'd say two at a time. i.e. bookworm, so we switch to it, and as soon as switch is complete, start with trixie.20:32
Wizzupok20:33
sicelos/so/until/20:33
siceloanyway maybe others have different idea :-)20:33
Wizzupuvos: so then shall I call these mz617-emmc-bootstrap, mz617-emmc en mc617-sd or something?20:35
Wizzups/ en / and /20:35
uvosmc617-sd?20:39
uvossure sounds sane otherwise20:39
Wizzupmz617-sd or mz617-sdcard20:41
Wizzupor just mmc I suppose20:41
uvosbut mz617 has no sdcard20:41
uvosand mz615 will probubly need a different dtb20:41
freemangordonWizzup: sorry, can't look at this ATM20:42
uvosso im not sure what you want with that20:42
uvoson mz617 the lack of hw video decoding really stinks20:42
uvossince its sutch a nice platform for viewing videos :(20:43
Wizzupfreemangordon: at what?20:44
freemangordonthat osso malloc stuff20:44
Wizzupuvos: you're right, sdcard makes no sense20:44
Wizzupfreemangordon: ok, I might just #if 0 it and continue for now20:44
Wizzupsince there's basically no users20:44
Wizzupthen we can discuss later20:44
freemangordonyes, please do, I'll have a look when I am back in BG20:44
Wizzuptake it easy :)20:44
freemangordonsure20:45
freemangordonarno11: so, that pastebin, there is no presence-ui button in h-s-m right? if that's the case, that means that by that time there are no telepathy accounts enabled/reported. I will prepare a version of the plugin with traces to see what exactly fails.20:46
freemangordonbut, it is not h-s-m to blame20:47
freemangordonIIUC20:47
Wizzupuvos: it's still with leste-config-droid4, but: https://wizzup.org/maemo-leste-1.0-armhf-mz617-20241006.img.xz21:00
uvosWizzup: ok cant test today21:09
arno11freemangordon: indeed, there is no presence ui btn in hsm21:11
Wizzupuvos: no worries21:12
arno11freemangordon: accounts seem not reported yet since it works if hsm starts later21:15
sicelofreemangordon: i suppose you read above that I'm back to my misery. but now i think i have better understanding of that charger driver, and at least some wq basics. i'm thinking that I need a second workqueue, specifically for running the `power_supply_changed()` function.  will schedule it with a 2s delay, to match the timing characteristics of the device.21:38
sicelothe existing workqueue is specifically for kicking the timer every so often. i could do the power_supply_changed() inside it, but that'll send excessive uevents.21:40
Wizzupsicelo: if it works on in 6.10 but not on 6.x, should that give you some hint too?21:40
sicelothere are no differences whatsoever in the isp170x and bq2415x drivers in all those versions ... actually that's why i just expected things to work the same21:41
Wizzupannoying..21:45
siceloyeah, it has taken time that i really didn't have. anyway reward is having learned something21:46
Wizzup:)21:57
Wizzupforgot that maemo-system-services uses python-gconf, will need to port it to calling gconftool-223:21

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