2023-07-04.log

+ mlarkin (~mlarkin@047-036-115-056.res.spectrum.com)00:33
bkeysjfred: A fellow ebike enjoyer I see01:01
- minute (QUIT: Server closed connection) (~mntirc@softboy.mntmn.com)01:55
+ minute (~mntirc@softboy.mntmn.com)01:55
- mtm (QUIT: Ping timeout: 246 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)02:04
jfredbkeys: that's right :P02:05
jfredThough I don't like that they tend to be very proprietary02:05
jfred(We need someone like MNT for e-bikes haha)02:06
- XYZ (QUIT: Ping timeout: 246 seconds) (~XYZ@78-80-114-131.customers.tmcz.cz)02:25
- scops (QUIT: Server closed connection) (~scopstchn@2001:470:69fc:105::8da)03:01
+ scops (~scopstchn@2001:470:69fc:105::8da)03:01
- robin (QUIT: Ping timeout: 246 seconds) (~robin@user/terpri)03:06
violetugh for real i got an e-bike once with an awful charge controller that deep discharged the battery while i had it in storage for like half a year or a year03:18
violetand then the battery was dead dead03:18
violetand they dont sell that battery anymore on their website they were like "email us if you need the old battery model"03:18
violeti did not email them and decided to get a different bike 03:19
- nsc (QUIT: Ping timeout: 250 seconds) (~nicolas@193-97-142-46.pool.kielnet.net)03:25
+ bluerise_ (~bluerise@pc19f889e.dip0.t-ipconnect.de)03:25
- bluerise (QUIT: Ping timeout: 260 seconds) (~bluerise@p5b0acd89.dip0.t-ipconnect.de)03:27
+ nsc (~nicolas@200-98-142-46.pool.kielnet.net)03:27
noamsigrid: silly question, how hot does your Reform get under 9front usually? e.g. cputemp03:35
noamI'm seeing e.g. CPU temp of 72 whilst idling, and the thing is _hot_03:36
sigrid56C iirc03:53
sigridmaybe your heatsink is a bit off03:54
sigridis that plain 9front or your mod?03:54
noamthe latter03:58
noamCPU base load is ~zero, but there's ~500 context switches / sysclals per second03:59
sigridmaybe see what that is04:03
sigridalthough why would it be that high (temp) anyway04:03
noamIf it's constantly waking up / going to sleep / waking up?04:09
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)04:10
noam...I have absolutely no idea what's causing those. Disconnected ethernet, killed bar+riow+reform/shortcuts, no impact04:12
sigridi don't think that's often enough04:12
sigridsee running time in ps or something04:12
noamI am, there's nothing there other than paqfs, usbd, kb, cwfs, rio, and stats04:12
sigridwhich one is highest?04:14
noamkb04:14
sigridok04:14
noam0:29 0:26; nothing else is even at 0:1004:14
sigridwhich chip is your trackball?04:14
noamThat's... also odd, I haven't exactly typed much into it, and IIRC that's minutes of CPU time...04:14
noamNo idea, I can check04:14
sigridor was it the keyboard... lemme remember04:15
noamI know nusb/kb's the HID driver, so... one of the two :P04:16
noamTrackball's an AVR chip, dunno which one04:17
sigridok, it was trackball, i remembered04:17
sigridok, you need to update its fw04:17
noamAh, okay, I've been meaning to do that anyways04:17
noamThanK!04:17
sigridjust do it for all devices there04:18
sigridthe bug was the fw would continuously send the same reports over and over04:19
noamahhh04:19
noamI need to do this so pmctl will work anyways :P04:19
noamdidn't realize there was a more urgent reason to do so04:19
noamCells are a bit warm, but they *were* just charging, sooooo probably fine?04:22
noamI flipped the LPCP switch on and plugged a microUSB cable into the board and it's not showing up :/04:56
noamHopefully it's just a bad cable04:57
noamyep! :)04:58
noamaannnnnnd now the LPC won't respond. Yikes05:13
noamneat, prebuilt 20_R3.bin works05:20
joschnoam: thank you for your feedback! You were faster than me in trying those. :D05:22
noam?05:23
noamjosch: whatcha talking about? :)05:23
joschnoam: when you do circle, s on your keyboard -- does it show the correct version in the OLD screen?05:25
noamsigrid: Also, hm, how do I update the trackball firmware?05:25
noamsilly me, there's probably a port if I just take the trackball out05:26
noamjosch: not going to check until after I've flashed the other firmwares05:27
noamthe handbook website is 404ing :/05:28
noamAnyone have a mirror?05:28
joschhttps://mntre.com/reform2/handbook/parts.html#trackball-firmware works for me?05:28
joschwhich url is 404 for you?05:28
noamAh, ddg gives shit results, noted.05:30
noamalso: I'm an idiot, the trackball is a USB DEVICE05:30
noamI don't need to disconnect it to flash it lol, glad I actually RTFMed first05:30
- jomo (QUIT: Server closed connection) (~jomo@user/jomo)05:31
+ jomo (~jomo@user/jomo)05:31
noamwait, do I have to press the reset button on the trackball WHILE THE REFORM IS RUNNING to falsh it??05:39
joschyes05:43
joschif you don't reset it, it will keep being a usb mouse05:43
joschbut you want it to be a "Atmel DFU bootloader"05:43
noamI didn't realize turning on the reform would reset the trackball, but of course it does, that's what powers it05:45
noamit wasn't on to *notice* the button press before05:45
noamfuck05:45
+ XYZ (~XYZ@37-48-50-214.nat.epc.tmcz.cz)05:55
noamjosch: nah, I don't want it to be an Atmel DFU bootloader :P06:00
noamI want it to be an ATmega32U2 DFU :P06:01
noammore seriously: dagnabbit, endpoint isn't showing up???06:02
noamOh, I need to boot linux to do this don't I06:04
noamfudge06:04
noamThat means no trackball updates for m06:04
noame06:04
noamGuess I have to implement nusb/dfu first :/06:05
- c-keen[m] (QUIT: Server closed connection) (~c-keenner@2001:470:69fc:105::2:8760)06:44
+ c-keen[m] (~c-keenner@2001:470:69fc:105::2:8760)06:44
+ robin (~robin@user/terpri)06:50
+ bgs (~bgs@212-85-160-171.dynamic.telemach.net)07:13
noamjosch: firmware version is indeed 20230703 :)07:32
joschawesome, thanks!07:38
- ec0 (QUIT: Ping timeout: 246 seconds) (~ec0@vps-446f4f39.vps.ovh.ca)07:58
- murph[m] (QUIT: Server closed connection) (~murphhope@2001:470:69fc:105::d564)09:22
+ murph[m] (~murphhope@2001:470:69fc:105::d564)09:22
- klardotsh (QUIT: Ping timeout: 246 seconds) (~klardotsh@98.97.35.74)09:31
- XYZ (QUIT: Ping timeout: 250 seconds) (~XYZ@37-48-50-214.nat.epc.tmcz.cz)09:33
+ MajorBiscuit (~MajorBisc@2001:1c00:31c:8400:f184:4168:559b:d91b)09:43
+ XYZ (~XYZ@78-80-113-63.customers.tmcz.cz)09:45
+ ec0 (~ec0@vps-446f4f39.vps.ovh.ca)10:12
- XYZ (QUIT: Remote host closed the connection) (~XYZ@78-80-113-63.customers.tmcz.cz)10:25
+ XYZ (~XYZ@78-80-113-63.customers.tmcz.cz)10:38
joschBoostisbetter: did you already flash your lpc?12:12
joschBoostisbetter: I created a script which helps you do that by giving you step by step instructions about what to do and also automatically chooses the right device, mounts and flashes it without you having to manually edit /dev/sdX in flash.sh: https://source.mnt.re/reform/reform/-/merge_requests/4512:12
- mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae))) (~mjw@gnu.wildebeest.org)12:23
* mark_ -> mjw12:23
- MajorBiscuit (QUIT: Ping timeout: 240 seconds) (~MajorBisc@2001:1c00:31c:8400:f184:4168:559b:d91b)12:37
+ MajorBiscuit (~MajorBisc@c-001-005-040.client.tudelft.eduvpn.nl)12:39
joschminute: I forgot what we agreed on for reform-boundary-uboot. Would you like me to send all my changes via MR or just the important ones and I do commits related to the buildsystem or CI for example directly to the main branch?12:52
joschSince the old artifacts are gone we need another tag and I could take care of that.12:53
joschbluerise_: the only thing still missing from mainline uboot is display support, right?12:54
minutejosch: for me it's fine if you send me only important changes via MR and otherwise commit directly12:55
joschokay!12:56
BoostisbetterJosch: thanks! I haven done it yet! Got busy last night! 13:26
bluerise_josch: yes, and my PCIe patch which depends on the power domain fixup that I didn't yet finish up because someone needs to do refcounting13:58
* bluerise_ -> bluerise13:58
bluerisehttps://github.com/bluerise/u-boot/commits/mnt13:59
bluerisehttps://github.com/bluerise/u-boot/commit/1b1e651e84321519fb703aaeda8f79f664ac5ceb13:59
bluerisetechnically that diff isn't great because a lot is hardcoded that should be done in proper drivers14:00
- mtm (QUIT: Ping timeout: 240 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)14:02
Ar|stote|isminute: will I get another email when items have shipped? will it have a tracking number? how much is ~2weeks most of the time?14:04
joschhuh... so I updated my LPC today with the binary from source.mnt.re and since then I get random bursts like this my dmesg14:33
joschhttps://paste.debian.net/1284910/14:33
joschand during those 2 minutes my internal reform keyboard stops working14:33
joschhas anybody seen this effect?14:34
+ mark_ (~mjw@gnu.wildebeest.org)14:37
minutejosch: huuuh... so sounds like a hiccup of the UART connection between keyboard and lpc 14:45
minuteAr|stote|is: hmm, AFAIK we shipped your order and you should have gotten a tracking code a while ago14:45
minuteAr|stote|is: yeah, your order should arrive tomorrow14:46
joschhrm... maybe my variable renaming broke something because i failed to find+replace properly in 064b49c2c34076cfa2f5ffe99a26559471b9d93414:55
joschi shall observe this further and go back to before that commit if this behaviour continues14:55
+ sva (~sva@vm-187.askja.de)15:00
- bgs (QUIT: Remote host closed the connection) (~bgs@212-85-160-171.dynamic.telemach.net)15:25
+ mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net)16:02
- Boostisbetter (QUIT: Ping timeout: 246 seconds) (4a410829d7@irc.cheogram.com)16:06
joschminute: i noticed that your gitlab is configured to create merge commits when merging merge requests. Is that behaviour intended by you in favor of fast-forward merges without additional merge commits? It can be changed under "Settings -> Merge requests -> Merge method" for each project.16:32
- [tj] (QUIT: Server closed connection) (~tj]@188.166.156.159)16:55
+ [tj] (~tj]@188.166.156.159)16:55
+ Boostisbetter (4a410829d7@irc.cheogram.com)17:24
minutejosch: would this make things easier?17:49
minutenow gonna continue working on a311d integration17:52
Boostisbetterminute: did you notice that Purism's Librem 5 was upgraded and is now using the 4gb variant of the SoC the Reform has been using all along. Feels like an Apple upgrade move to me. Surely it was possible to go with this chip out of the game, instead of the 3gb variant. 18:04
c-keen[m]How do I boot without using the boot script in U-Boot?18:07
c-keen[m]The boot script contains the wrong dtb filename which is missing a hdmi part in it's name18:07
c-keen[m]I don't have a MMC card at my disposal atm otherwise I would boot from there18:07
minuteBoostisbetter: i noticed that it was upgraded to a very interesting price and also USA flags :D18:08
minutemeanwhile, our products have always been assembled in our studio...18:08
minutec-keen[m]: how about using `sudo reform-display-config dual`?18:09
minutec-keen[m]: (with --emmc probably?)18:09
c-keen[m]How when I cannot get into Linux?18:10
minutec-keen[m]: ah, you mean it doesn't boot18:10
minutec-keen[m]: you can do `setenv fdtfile ...`18:10
c-keen[m]Yes18:10
minutec-keen[m]: and then `boot`18:10
minutec-keen[m]: where `...` would be the .dtb that you want18:11
c-keen[m]The first message has been lost I think18:11
minutec-keen[m]: my first message? it was > you can do `setenv fdtfile ...18:11
c-keen[m]What's before 'and then boot' ?18:11
minutec-keen[m]: setenv fdtfile my-favorite-dtb-file.dtb18:12
c-keen[m]Ah it is confusing as there is fdtfile, fdt_file and fdtpath in the environment18:13
c-keen[m]Yes that works18:13
minutecool18:13
minuteBoostisbetter: also yes. the 3gb was just the nxp reference design i think18:15
minuteat least the nxp imx8mq evk also had 3gb18:15
minutethe 4th GB was past the 32-bit address space. maybe they had problems with that at first18:16
minutethis was also the first 64-bit i.mx if i'm not mistaken18:16
minutei.mx8qm was arguably first, but had a lot of technical issues, so i.mx8mq was made as a stopgap18:17
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)18:19
c-keen[m]minute so to remedy the situation I should rerun he reform-display-config script?18:24
minutec-keen[m]: yep18:27
c-keen[m]ok, thanks for your patience18:27
minuteno problem!18:36
minutejosch: vagrantc: if i am in the process of building a new kernel package for debian, and testing it on the target... how can i also cross-rebuild the corresponding initramfs? for example, i might need it to load more modules than just those for imx8mq18:37
minutenow i have to compile in at least the MMC drivers to get a bootable system18:37
minutehmm, very strange failure when building the kernel package one more time, maybe i have to delete and remake the unshare-root-fs?18:41
minuteException: ('python3.11', '-c', 'import importlib; print(importlib.util.MAGIC_NUMBER)') failed with status code 118:41
minutedpkg: error processing package python3-minimal (--configure):18:41
c-keen[m]also something I noticed: In uboot the right shift key does not seem to work, it repeats keystrokes...19:02
minutec-keen[m]: funny19:04
c-keen[m]also: the reform-check script says, that it cannot download the raw/flash.bin from a u-boot pipeline due to hash mismatches19:06
minutec-keen[m]: yeah, i have to do some tag shenanigans on the gitlab19:07
c-keen[m]I see19:07
minuteah, we have to update these https://source.mnt.re/reform/reform-tools/-/blob/main/bin/reform-check#L10219:10
minutec-keen[m]: hmm, perhaps you need to update reform-tools? can you try that?19:12
joschminute: re git merge: which strategy to pick is personal preference i think. Personally, I see little point in cluttering the "git log" output with merge commits if though the commit applies directly on top of HEAD.19:12
c-keen[m]minute manually?19:12
joschc-keen[m]: there was a problem when source.mnt.re got moved to a different servers and some artifacts are now 404. I already created a new git tag for reform-boundary u-boot and now only need to make a new upload of reform-tools.19:13
joschc-keen[m]: i can ping you once i'm done -- maybe in a few hours?19:13
c-keen[m]sure! I am not going anywhere19:14
joschminute: the initramfs is built as part of reform-system-image. To build the initramfs you need a chroot environment that matches the final system (that's what the reform-debian-packages script does). So you can either do this natively on the reform (but i guess it doesn't even boot to a serial console?) or you have a chroot directory on your machine and (assuming that machine is not arm64) you use 19:15
joschqemu-user binfmt to emulate arm64 transparently.19:15
- MajorBiscuit (QUIT: Quit: WeeChat 3.6) (~MajorBisc@c-001-005-040.client.tudelft.eduvpn.nl)19:19
joschc-keen[m]: this should fix your problem https://source.mnt.re/reform/reform-tools/-/merge_requests/4019:20
joschc-keen[m]: once minute merges that, the reform-debian-packages pipeline has to get triggered by minute, then the pipeline has to pass and then the cronjob uploading the result to the mirror has to run19:21
c-keen[m]understood19:23
minutejosch: gotcha. glad you're back! maybe you have an idea why sbuild is broken right now (with unshare)19:28
minutejosch: it fails when it wants to setup python3-minimal19:28
minutei've tried to inspect this by extracting the mmdebstrap-made tarball, but when entering the chroot iwth mmdebstrap --unshare-helper, something is wrong with the permissions19:29
minutei.e. the root user in the chroot can't do root things (like apt update)19:29
joschminute: did you extract the tarball as root?19:30
minutejosch: tried that as well19:30
joschminute: is the error this: result = self._execute('import importlib; print(importlib.util.MAGIC_NUMBER)', version)19:31
minutejosch: yes19:31
joschminute: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=104031619:31
joschminute: python in unstable is broken right now19:31
minuteah weird, i was looking in the wrong package's or suites bug tracker i guess 19:32
minutejosch: is there anything i can do to continue working on the kernel stuff or do i have to work on another project today until it is fixed?19:33
joschminute: other than waiting for this to be fixed you could do s/unstable/testing/ everywhere19:34
joschit's a very common problem that anybody doing stuff with unstable has their stuff broken for multiple days sometimes19:34
minutejosch: ok, this selects another kernel version though, right?19:34
minuteso i have to be lucky that the patches work?19:34
joschyes19:35
minuteok, will try19:35
joschtesting has 6.3.7-1 and unstable has 6.3.11-119:35
minuteah, that's not so bad19:35
joschyes, it might just work :)19:35
josch(but i had the patches fail to apply even with just the minor version changing in the past)19:35
minute:019:36
minutelooks like i'm lucky with the patches19:40
minuteok, looks like the build process is working now, phew19:42
minutejosch: regarding the mmdebstrap chroot extraction, my guess is i'm missing some tar options like --owner, --numeric-owner or sth like that19:43
minutewhen extracting just like that, everything is owned by my normal user19:43
joschminute: yes, when you have a tarball with files owned by user X and you extract is as the non-root user, the files end up owned by your user19:46
vagrantcminute: regarding the initramfs ... unless the initramfs configuration has been tweaked, it should install most kernel modules out of the box ...19:46
joschbut you also likely never want to extract that tarball (i'm the author of both mmdebstrap and sbuild and never saw a need to extract it)19:46
joschminute: for the imx8mq we had to add several modules on top19:47
vagrantcminute: you can add more by adding some scripts in various places under /etc/initramfs-tools or /usr/share/initramfs-tools/19:47
joschit's /etc/initramfs-tools/modules19:49
joschthat's what mkuserland.sh in reform-system-image does19:49
- cmahns (QUIT: Changing host) (8fe824803c@2604:bf00:561:2000::10cd)19:55
+ cmahns (8fe824803c@user/cmahns)19:55
minuteok, i'm still trying to wrap my head around the moving parts. my development process is like this: 1. i'm rebuilding the kernel package. 2. i'm manually grafting the kernel package on top of an sd card with a release version of reform-system-image. (i.e. i am using dpkg -x on the root partition)19:56
minuteprobably i should rather somehow find a clean way to chroot into the sd card but also mount the /boot partition into it 19:56
minuteand then dpkg -i the kernel package and then rebuild the initramfs somehow? (update-initramfs?)19:57
minutealways recreating the whole reform-system-image and reflashing it would take too long for my dev process19:57
minuterebuilding the debian kernel also already takes much much longer than just rebuilding my development kernel. probably because it always have to start from zero19:58
joschminute: dpkg -x is not enough. That just extracts the kernel. What you want is to "dpkg -i linux-image*.deb" which installs the kernel *and* will rebuild your initramfs.20:07
joschah i should read the whole backlog :)20:07
joschso, you don't need "dpkg -x" but just "dpkg -i"20:08
joschif what you have is the sd-card with the arm64 system on it, don't forget to mount /boot into it before chrooting into it20:08
joschif you don't mount /boot, then the initramfs doesn't get placed into the correct location20:09
joschminute: when i bisected the kernel i did something similar and i also did not re-run the reform-system-image script as that would naturally take too long20:09
joschyes, rebuilding the debian kernel takes longer because it starts from zero, because it needs to install all dependencies first, because it builds way more modules than needed and because it builds more than the kernel itself (docs, tools etc...)20:10
minutejosch: ok, so we are on the same page regarding the kernel testing procedure. now for the rebuilding: it's not possible to cache a build step there, yes?20:18
joschminute: there are two main ways to speed up the build process20:23
joschminute: either, if you want to continue building in an isolated environment like sbuild to minimize interference from the outside there is ccache (but i've never used it when cross-building)20:23
joschminute: or you ditch sbuild and cross-build it straight from an unpacked source directory by invoking debian/rules targets manually20:24
joschbut the second option is highly depending on what source package you are building and i'm not familiar enough with the linux packaging to tell you what to run20:24
minutehmmm ok, so maybe ccache is an option for later20:26
minutenow trying to install the kernel package on chrooted sdcard20:26
joschi've often found answers to my Debian kernel building related questions here: https://kernel-team.pages.debian.net/kernel-handbook/index.html20:26
joschbut i didn't read the whole thing yet so i cannot tell you whether that document contains the answer to your questions20:27
minutejosch: this seems applicable https://wiki.debian.org/sbuild#Using_.22ccache.22_with_sbuild20:28
minuteanother little challenge: we'll need to adjust "bootargs" (kernel command line) for quirks of the different socs. for example, on a311d, the serial console is ttyAML0, not ttymxc0, and we need pci=pci_bus_perf. (this one might actually be interesting for imx as well)20:29
joschminute: the bootargs are set in /etc/default/flash-kernel20:35
joschthis is something that the reform-system-image script will have to do different depending on the SoM20:35
minuteok20:36
joschit already supplies the special values for imx8mq20:36
joschminute: until reform-system-image does the right thing, just edit your /etc/default/flash-kernel and the next time you install a kernel, flash-kernel will write out boot.scr with the updated bootargs20:38
minutejosch: cool, thanks20:48
minute> A start job is running for /dev/mmcblk1p120:48
minuteok, fstab will need to be tuned as well i think (?)20:49
joschif you are running from sd-card then no20:50
minutejosch: well, on a311d, sd card is /dev/mmcblk0 :D20:50
joschah then yes :)20:52
minuteit boots and i can log in, so progress20:53
josch\o/20:53
joschit's on my todo list to use a UUID in /etc/fstab instead of a path like /dev/mmcblk1p1 -- that way this will work independen on how the kernel names the sd-card or emmc20:54
minuteah nice20:54
- jacobk (QUIT: Ping timeout: 264 seconds) (~quassel@47-186-122-163.dlls.tx.frontiernet.net)20:54
minutejosch: is the fstab managed by a reform-tool nowadays? just wondering where i should patch when shipping this20:55
minuteor is it just created once during reform-system-image build?20:56
joschminute: nothing in /etc should be managed by reform-tools as everything in /etc should be admin maintained and not package maintained20:56
minuteah! interesting20:56
joschminute: the reform-system-image script fills /etc/fstab20:56
minuteok cool, so for now i can patch that for an initial a311d-reform-system-image20:57
- mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mjw@gnu.wildebeest.org))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)21:00
* mark_ -> mjw21:00
+ mark_ (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae)21:00
minuteon a311d, emmc and sd card device name are exactly swapped vs imx... whyyy21:05
minuteemmc is mmcblk121:05
joschmaybe a udev rule can be used to turn those around again?21:07
joschthis might also be a lesson to stop relying on /dev/sd* naming and to use /dev/disk/by-id/* instead21:08
josch(see my latest merge request for lpc flash.sh)21:08
joschor by using the filesystem UUID instead21:09
+ jacobk (~quassel@2600:100c:b25f:3b8a:42c5:a261:b8c5:2121)22:55
- jacobk (QUIT: Ping timeout: 246 seconds) (~quassel@2600:100c:b25f:3b8a:42c5:a261:b8c5:2121)23:13
+ jacobk (~quassel@52.128.53.110)23:16
- XYZ (QUIT: Ping timeout: 246 seconds) (~XYZ@78-80-113-63.customers.tmcz.cz)23:36
- jacobk (QUIT: Ping timeout: 264 seconds) (~quassel@52.128.53.110)23:56

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