libera/#maemo-leste/ Wednesday, 2021-06-16

mighty17[m]Sudo in x term doesnt ask for password, is there no root pass (toor acc to wiki)08:32
parazydThere is a root password08:39
parazydTry "su"08:39
parazydsudo currently just doesn't ask for a password.08:39
mighty17[m]Ah okay sudo not asking pass was concerning08:40
mighty17[m]Also what matric client do u suggest to use08:41
parazydYeah there's a NOPASSWD entry in /etc/sudoers08:41
parazydI don't know, not a matrix user.08:41
mighty17[m]I tried nheko but virtual keyboard didn't pop up08:41
parazydYou'll want gtk2 for automatic vkb.08:41
parazydAlso we should try to set up shortcuts so you can open the vkb anywhere.08:42
mighty17[m]Which we don't have?08:42
mighty17[m]Yeah like phosh has08:42
mighty17[m]also what sets the mAh in battery? dts? rootfs?08:43
parazydThere is a shortcuts config file like this: https://github.com/maemo-leste/leste-config/blob/master/leste-config-mapphone/usr/share/hildon-desktop/shortcuts.ini.leste08:44
parazydSo, RaiseVkb=XF86Search08:45
parazydYou could try setting this to some key.08:45
parazydFor the battery, it can be different from device to device, so I can't give you a correct answer.08:45
mighty17[m]yeah, my battery is 4000mah but inidcator says its 200008:46
parazydMight need calibration?08:47
parazydUsually that's done by making a full charge, and then a full discharge.08:47
mighty17[m]didnt know that, thanks08:48
parazydBut also the battery applet in Leste could have issues. Wizzup worked on the upower setup so he knows more than I do.08:48
mighty17[m]RaiseVkb=XF86Search > umm i dont have any extra keys08:48
mighty17[m]just pure screen :D08:48
parazydYou could use a volume key08:49
parazydOr you have no buttons at all?08:49
mighty17[m]vol key is broken08:49
parazyd:o08:50
siceloupower uses /sys/class/power_supply/* ... so 1st, does /sys have correct capacity?09:09
lelparazyd created a repository: https://github.com/maemo-leste/ui-fonts09:10
lelparazyd edited a repository: https://github.com/maemo-leste/ui-fonts09:11
mighty17[m]sicelo ig u need power supply info from maemo as well? :p09:45
parazydmighty17[m]: Yeah that's what he's asking09:49
mighty17[m]parazyd my question is different iirc he wanted pm comparison of Tab2 and droid4 as Tab2 has old uboot so dmesg says pm isn't available (pm = power management)09:55
uvos__no he wanted to kown if cat /sys/class/power_supply/*/charge_full_design  has the right mAh value09:58
uvos__as this is your responsability to set in the battery driver09:58
uvos__either by dts bindings or the driver autodetecting it via nvram09:59
parazydfreemangordon, Wizzup: Is also wpa_supplicant from devel supposed to go to stable?10:01
Wizzupno no no10:01
parazydlol ok10:02
parazydJust asking10:02
parazydI'm going to promote what I can today10:03
uvos__btw parazyd we should maybe flip on charge-mode for devel10:03
parazyduvos__: ok, let me clean devel up first and then do further tweaks10:03
uvos__ok10:03
parazydI don't like it when there's too many packages there.10:03
Wizzupparazyd: also do not promote icd stuff10:03
uvos__also not mce10:04
parazydWizzup: ACK, fmg told me about connui10:04
parazydNothing else10:04
parazyduvos__: ok10:04
parazydsec10:04
parazydhttp://sprunge.us/jdyZUt10:04
parazydThis is what we have there atm10:05
uvos__imo we can promote mapphone-kexecboot-*10:05
uvos__fbkeyboard is fine too10:05
uvos__whats the change in hildon-desktop10:06
uvos__?10:06
parazydSo I'm thinking: connui (without cellular), kexecboot configs, hildon-meta, fbkeyboard, gtk2, matchbox+hd10:07
uvos__ah its a code style change10:07
uvos__you can promote that10:07
parazyduvos__: it's built because of matchbox also, your 49fbe681b34794cc6501d2a024870143abe41b21 patch10:07
parazyd>    Fix fullscreen handling for fullscreen override redirect windows10:07
uvos__oh that10:07
uvos__yeah we can promote it10:07
parazydWizzup, uvos__: What about osso-systemui powerkeymenu/splashscreen/tklock ?10:08
Wizzupsorry, I can do this later but not right now10:08
WizzupI think those are probably fine, though10:08
uvos__parazyd: yes those are needed bugfixes10:08
uvos__related to the machbox change10:08
uvos__you must promote togehter10:08
parazyduvos__: You mean systemui+matchbox?10:09
uvos__yes10:09
parazydACK10:09
parazydThanks10:09
parazyduvos__: Are you using dsme on your devel device?10:11
uvos__parazyd: yes no10:11
parazydok, I mean, you haven't noticed any problems or something?10:11
* parazyd hasn't10:12
uvos__parazyd: no10:12
parazydok10:12
uvos__parazyd: but i changed several init scripts to remove dsmetool10:12
uvos__and i dont load the dsme mce module10:12
uvos__so dsme is pretty impotent on my device10:12
parazydok, this is unrelated10:12
uvos__idk if id notice if it breaks10:12
uvos__ok10:12
uvos__the kerecv change also looks fine10:13
parazyd*nod*10:14
uvos__byw  you might want to keep osso-systemui-splashscreen in devel10:15
uvos__no one has tested this yet10:15
uvos__and its unfinished afaik10:16
parazydTrue10:16
uvos__but we also dont use it10:16
uvos__hildon-input-method is fine10:16
uvos__this was just the utf8 change10:17
uvos__i thnk thats it10:17
parazydmhm10:17
mighty17[m]either by dts bindings or the driver autodetecting it via nvram > okay, i will try a full charge and discharge first to get it calibrated10:24
uvosmighty17[m]: this wont help if dts is wrong10:25
uvosprobubly10:25
uvosany sane driver will reject a cal value so different from charge_full_design10:25
mighty17[m]i havent put any info in dts about battery size10:31
uvosyour driver might not have dts bindigns for this10:32
uvoscpcap dosent for instance10:32
uvosisntead you might have to add your battery to the driver10:32
mighty17[m]max17042 fuel gauge ig10:32
mighty17[m]and my charger isnt in mainline :P10:32
uvosits about the fule gage10:32
uvosmax17042 has some way to detect or gain the capacity10:33
uvosyou have to figure out what it is and add your battery10:33
mighty17[m]yeah afaik https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/power/supply/maxim,max17042.yaml no battery10:33
uvosyeah well read the driver source10:34
mighty17[m]`cat charge_full_design > 5333500`10:39
mighty17[m]idk what unit that is in10:40
uvosdriver sets it writable then10:40
uvoscpcap dose this too but its not nesscarly the right way to do it10:40
uvos(might also be the only way .. read the driver)10:41
uvosnothing in leste dose this btw10:41
uvos2000000 is likely simply the default10:41
uvoson the drivers side10:41
mighty17[m]oh so most likely i have to specify it somewhere10:43
liohhi all. I am facing the issue that Maemo Leste boots fine on my N900 (I can see the boot messages) but I don't get a graphical interface.10:49
liohIt was working already but currently the screen just stays blank after boot10:50
parazydDo you wait enough time? I tried a fresh flash yesterday and it took me a minute to show up.10:50
parazydLike, actual 60-70 seconds10:51
liohI have waited that time, but battery level is already in the lower part, so maybe it's related to that. I am going to charge now and try again.10:53
parazydIt might be. You can also boot to Fremantle and charge it normally.10:54
liohI have flashed uboot so no fermantle anymore I guess10:55
liohalso I always have to type run sdboot after startup.10:55
liohOne time I got a selection Menu from uboot, but since then I have never seen it again and I don't know how to trigger it10:56
parazydBoot with the keyboard opened10:56
parazydThis'll get you to u-boot10:56
parazydIf it's closed then it automatically boots to fremantle iirc10:56
liohWhich does not seem to be available anymore after running sudo ./0xFFFF -m u-boot-2013.04-2.bin -f10:57
liohIs there a way to flash both? on the internal storage fermantle and leste on the sd-card?10:57
liohMaybe even using 0xFFFF?10:57
parazydPali: Maybe you know? ^10:59
parazydOn mine I installed u-boot through fremantle, not with 0xffff so I'm not sure.10:59
parazydIn any case, you might also be able to charge it while it's powered off. It's just that sometimes when you plug in, the phone powers on.10:59
uvosits just the appended kernel missing11:00
parazydI don't know if charging works in u-boot11:00
uvosso you should be able to somehow append the kernel11:00
uvosidk why we dont just have a image for people to install11:00
uvosthat has the freemantle kernel appended11:00
parazydBecause there are different kernels for fremantle11:00
uvossure but the latest/last one should work fine with anything right?11:01
uvosor dose pvr get in the way?11:01
uvosits static anyhow no?11:01
liohso you thing fermantle is still on the emmc and should still be bootable?11:04
liohhmm if i select internal emmc on uboot menu it is unable to find the relevant partitions11:07
Wizzupparazyd: this is the second report of this happening recently I think11:08
WizzupI can test the latest image on mine and see what hapens11:08
Wizzupalso, we should probably figure out what log files are most relevant11:08
parazydmtg now, bbl11:08
Wizzupopenrc can also log11:08
Wizzup:p11:08
Wizzuplioh: I'll try to reproduce this today or tomorrow at latest (also in mtg atm)11:30
liohis there a way to increase screen brightness on boot?11:55
parazydIn u-boot? Don't think so.12:17
parazydBooting normally with the power button should enable backlight12:17
mighty17[m]`PVRMMapRemoveRegisteredArea: psOffsetStruct 0xdb27724a for memory area 0x0x6051b23f is still mapped; psOffsetStruct->ui32Mapped 1 [1754, rivers/gpu/drm/pvrsgx/1.9.2253347/services4/srvkm/env/linux/mmap.c` hm?12:57
mighty17[m]also also `iptables/1.8.2 Failed to initialize nft: Protocol not supported` happened when i installed anbox, ig we need CONFIG_NFT_COMPAT in defconfig13:05
uvosthe prv problem is known13:07
uvosthe pvr driver is just broken in 5.1113:07
uvosanbox wont work on your device13:07
parazydmighty17[m]: This should be useful: https://github.com/maemo-leste/droid4-linux/blob/maemo/beowulf/debian/patches/anbox-support.patch13:07
uvosits broken on 32bit13:07
parazydhttps://github.com/maemo-leste/droid4-linux/blob/maemo/beowulf/debian/patches/0006-defconfig-enable-netfilter-masquerading.patch13:07
uvosand its bronken on pvr13:07
parazyduvos: I think it does work on 32bit, it's just pvr that is the issue.13:08
parazydCould try on Raspberry13:08
uvosparazyd: input is broken13:09
uvosparazyd: according to the guy who integrated it for pmos13:09
parazydoh13:10
uvosalso the bugreport on anbox github13:10
parazydYeah I remember, it was quite a while ago13:10
parazydDidn't check if things changed.13:10
uvosi think we should just silence that pvr warning for now13:26
mighty17[m]uvos: so anbox will work or not? i can go back to 5.10 or smth13:28
uvosno anbox dosent and will likey never work on your device13:29
uvosand even if it did13:29
uvosit really needs more than 1gb ram13:29
mighty17[m]i can give it swap/zram13:31
mighty17[m]i dont have a 16gb sd card for nothing :P13:31
parazydIt's not a magic bullet13:31
mighty17[m]also yeah u have a point with 32 bit so yeah13:34
uvosthe 32 bit bug can be fixed13:34
uvospvr is the problem13:34
liohwhat is the default screen lock code?13:43
mighty17[m]123413:44
sicelolioh: flashing u-boot does not touch fremantle rootfs or emmc13:44
mighty17[m]1234513:44
liohmighty17[m], does not work for changing the code (complains it's wrong)13:44
mighty17[m]That's the default keycode ^^13:44
liohahhh13:44
mighty17[m]Lockcode can only be changed if your hardware has CAL. QEMU does not have CAL. Droid 4 also not.13:45
mighty17[m]https://leste.maemo.org/Getting_Started13:45
liohn90013:45
parazydIf your device is locked, this might be the reason desktop isn't showing up13:46
parazydWizzup knows the intricacies of this on Leste13:46
liohdesktop is showing again after putting it to charge13:46
siceloIf you have lock code issues, you might have easier time if you first fix your Fremantle ... there are ways to recover it. Search tmo (talk.maemo.org)13:46
liohdevice lock is currently disabled13:46
siceloAh, ok13:46
liohyes, but if i understood you right, i should only need to add fermantle to the bootloader right?13:47
liohOr does it chain-boot?13:47
liohLoading the Fermantle bootloader from the emmc using u-boot?13:47
liohBecause just selecting 'boot from emmc' in the uboot menu does not work as mentioned13:48
liohand reflashing Fermantle is really a mess. At least on a recent x86_64 system. I have already found an old debian live image containing flasher. maybe I could give this one a try13:49
Wizzuplioh: so did you manage to make leste rende rok on boot, or is there still a problem with the image?14:34
uvos"[13:46] <lioh> desktop is showing again after putting it to charge"14:35
uvosnot sure why the device would hang somewhere before hildon when the battery is low14:37
uvosinstead of eg. powering back off14:37
parazydtbh it might be powering off14:37
siceloI don't think reflashing Fremantle is really a big mess :-)18:08
siceloAnyway, since lock code isn't active, you don't have a big need to get into Fremantle18:08
WizzupI think getting an upgraded fremantle with cssu is painful18:09
Wizzuptbh18:09
* uvos tried that and failed18:10
uvosor gave up anyhow18:11
siceloYou don't need cssu to fix lock code though. Anyhow,18:14
siceloAnyone knows if N9 & N950 use cal?18:15
siceloOr it's only N900?18:16
Palilioh: parazyd: you need to generate combined.bin image, not to flash u-boot.bin only18:57
Paliuse script u-boot-gen-combined to generate combined.bin binary from u-boot.bin and uImage kernel18:57
Paliand flash this combined.bin binary18:57
Palilook into u-boot/doc/README.nokia file18:58
Palihttps://source.denx.de/u-boot/u-boot/-/blob/master/doc/README.nokia_rx5119:04
Palihttps://github.com/pali/u-boot-maemo19:04
Palihttps://lists.denx.de/pipermail/u-boot/2021-May/450266.html19:05
Pali$ sh u-boot-gen-combined u-boot.bin uImage combined.bin19:06
Paliand to generate zImage from uImage use:19:07
Pali$ mkimage -A arm -O linux -T kernel -C none -a 80008000 -e 80008000 -n zImage-2.6.28-omap1 -d zImage-2.6.28-omap1 uImage19:07
PalizImage-2.6.28-omap1 kernel take from fremantle kernel19:08
PalizImage packed in fiasco archive packed in deb archive is at: http://repository.maemo.org/pool/maemo5.0/free/k/kernel/kernel_2.6.28-20103103+0m5_armel.deb19:10
Palito unpack deb, use: dpkg -x19:10
Palito unpack fiasco, use: 0xFFFF -M zimage.fiasco -u19:11
Paliparazyd: u-boot does not support battery charging19:12
freemangordonPali: do I get it right, that this guy wants me to post an one-liner patch?19:14
Palifreemangordon: seems to19:14
freemangordonok :)19:14
Paliput it into reply to that email19:15
freemangordonsure19:15
Palithx!19:24
tmlinduvos: hey cool, looks like on mz609 this works now: sudo fastboot flash utags utags-mz609-32-mmcblk1p6-boots-mmcblk1p18-kexecboot.bin19:25
freemangordonPali: sent19:25
tmlinduvos: that is after flashing the allow-mbmloader-flashing-mbm.bin from the "Xoom2 ME.rar" package like you suggested19:26
uvostmlind: yaay :)19:26
freemangordonoh, seems I don;t need moderator approval anymore :)19:26
uvostmlind: great now we can avoid to bricking the things19:26
tmlinduvos: maybe you forgot to do fastboot reboot bootloader, or your writes were not working19:26
uvosmy wirtes where not working19:27
tmlinduvos: ok19:27
uvosi rebooted multiple times after that19:27
uvosand its still at the version number from honycomb19:27
uvos(fastboot version)19:27
tmlinduvos: we can also probably now use some other partition other than cache partition for kexecboot19:27
uvosdepends on what mbm cares about19:28
uvosbut now you can expierament without accedentaly bricking the thing19:28
tmlindhmm we should try to find the allow-mbmloader-flashing-mbm.bin also for the 10" tablets19:28
uvostmlind: yeah19:28
uvostmlind: btw have a cdt.bin for mz609 or dose it not use that?19:29
uvoslooks like motoboot.img mentions it19:31
uvoslooks kinda like motoboot maybe contains a bunch of stuff compressed or soemthing19:32
tmlinduvos: did not flash that one, i think that's really only used for boot time checks19:32
uvosright but it  includes cdt.bin in its header19:32
uvosbut no cdt.bin19:33
tmlinduvos: i believe cdt.bin does not matter for allow-mbmloader-flashing-mbm.bin, it might make a difference after flashing something and rebooting though19:34
uvosok19:34
tmlindwell that's just my gut feeling based on experiments19:34
tmlindso maybe mz615 european model had a different number and we need to search for that firmware?19:35
uvostmlind: maybe19:35
uvosits mz61619:35
uvoshttps://www.ebay.de/itm/233958288980?epid=114527473&hash=item3679002e54:g:hSwAAOSw3MFgbU9919:35
tmlindoh ok19:37
Wizzupfreemangordon: Pali: looks like tom didn't respond to the point about having to port to dts19:43
Wizzupnot sure if he got that or not19:43
PaliWizzup: I really do not know... if you think that you can re-phrase freemangordon's email that there is missing response to dts, please do it19:45
PaliI'm really lost now :-(19:45
Wizzuphe wrote an email 7 minutes ago which I think is a bit more clear19:45
PaliI see "provide a linkable but not runnable"19:46
Paliso just provide fake stubs for those functions which are missing at linker time?19:46
Paliso linking step passes?19:46
PaliI do not know19:46
freemangordonWizzup: could you please step in as it seems for some reason my explanations about DTS are not clear to Tom.20:02
Wizzupok20:04
freemangordonand no, his last mail is not clear to me, in terms that I don;t understand how can I create linkable binary without enabling OF_CONTROL20:04
freemangordonwell, I can tweak Makefiles here and there, but is it what he wants me to do20:05
Palicreateing empty stubs in rx51 board code for "missing" of functions may produce linkable binary21:11
Palithis is probably the easiest way21:11
Wizzupfreemangordon: ping22:33
freemangordonWizzup: pong22:34
Wizzupfreemangordon: just one second, I'd like you to read the email I will send to u-boot ml and confirm22:34
freemangordonok22:35
freemangordonin the meanwhile, I was just able to hack uboot to link without OF_CONTROL enabled22:36
Wizzuphttps://paste.villavu.com/raw/erpkqsCqrW4BRjTSEiuE3IM46WnsjMJ10wDoqhfT/22:37
Wizzupbut that is just with stubs, as I mention in my proposed email, right22:37
freemangordonnot really, I #ifdef-ed some code and linked to the missing lib functions22:38
freemangordonlemme try it it will boot22:38
WizzupI see no reason to change my email for it, btw, so I think I'll send it momentarily22:38
Wizzupor would you like me to hold off?22:39
freemangordonyes, just a sec, I'll read it22:39
freemangordonyep, boots, not sure how to check if USB boots22:41
freemangordon*USB works22:41
freemangordonWizzup: looks ok, please sent22:41
freemangordonI'll do immediate follow-up with what I have so far22:42
Wizzupok22:42
Wizzupfreemangordon: done22:43
Wizzupit's awaiting approval though22:43
Wizzup(for the list)22:43
freemangordonok22:44
freemangordonyou have it (I see the mail)22:44
Wizzupyou're on cc22:45
freemangordonah, right :)22:45
freemangordonPali: https://pastebin.com/LgizurGs - it compiles with those changes22:51
freemangordonany idea what compatible shall I use in the board file?22:51
freemangordonfor  U_BOOT_DRVINFOS() that is22:52
freemangordonPali: also, how to test if USB works?22:57
freemangordonoh:22:57
freemangordonttyACM0: USB ACM device22:57
freemangordonI guess this means it works?22:58
Wizzupfreemangordon: try using screen23:03
Wizzupfreemangordon: like here: https://www.youtube.com/embed/tGGXvguyXWk23:04
freemangordonwhat are the parameters?23:05
freemangordonscreen -m /dev/ttyACM0 ?23:05
freemangordonnever used screen, sorry23:06
Wizzupscreen /dev/ttyACM0 11520023:06
freemangordonoh, it needs sudo23:07
Wizzupprobably, or some unix group membership23:07
freemangordonNokia RX-51 # version23:07
freemangordonU-Boot 2021.07-rc4-00026-gc4737cd594-dirty (Jun 16 2021 - 23:46:45 +0300)23:07
freemangordon:)23:07
Wizzup\o/23:07
Palieither screen, minicom or kermit23:07
freemangordonscreen works23:07
freemangordonand usb works it seems23:07
Palievery tool should work :-) just choose your favorite23:08
freemangordonalready did23:08
Paliperfect so it works?23:10
freemangordonNokia RX-51 # version23:10
freemangordonU-Boot 2021.07-rc4-00026-gc4737cd594-dirty (Jun 16 2021 - 23:46:45 +0300)23:10
freemangordonarm-linux-gnueabi-gcc (Debian 8.3.0-2) 8.3.023:10
freemangordonGNU ld (GNU Binutils for Debian) 2.31.123:10
Paliok, so works!23:10
freemangordonyes, it does23:10
Paliand is u-boot still showing that deprecation warning during 'make'?23:11
freemangordonyes, but this is a matter of changing one script23:11
freemangordonin Makefile,   CONFIG_OF_CONTROL shall be removed23:11
freemangordonthe one next to CONFIG_DM_USB23:12
freemangordondiff --git a/Makefile b/Makefile23:13
freemangordonindex a73481d18c..e1cf0200b7 10064423:13
freemangordon--- a/Makefile23:13
freemangordon+++ b/Makefile23:13
freemangordon@@ -1114,8 +1114,7 @@ ifneq ($(CONFIG_DM),y)23:13
freemangordon        @echo >&2 "See doc/driver-model/migration.rst for more info."23:13
freemangordon        @echo >&2 "===================================================="23:13
freemangordon endif23:13
freemangordon-       $(call deprecated,CONFIG_DM_USB CONFIG_OF_CONTROL CONFIG_BLK,\23:13
freemangordon-               USB,v2019.07,$(CONFIG_USB))23:13
freemangordon+       $(call deprecated,CONFIG_DM_USB CONFIG_BLK,USB,v2019.07,$(CONFIG_USB))23:13
freemangordon        $(call deprecated,CONFIG_DM_PCI,PCI,v2019.07,$(CONFIG_PCI))23:13
freemangordonheh23:13
freemangordonmy messages were throttled :)23:14
freemangordonanyway, have to do some RL work, night, see ya23:15
Wizzupgn23:15
WizzupTom responded btw23:15

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