2022-06-29.log

- bkeys (QUIT: Ping timeout: 264 seconds) (~Thunderbi@static-198-54-135-69.cust.tzulo.com)00:32
- S0rin (QUIT: Ping timeout: 246 seconds) (~S0rin@user/s0rin)00:44
- aliosablack (QUIT: Ping timeout: 255 seconds) (~chomwitt@2a02:587:dc1c:800:5c71:ba1b:727c:3afe)00:45
+ S0rin (~S0rin@user/s0rin)00:49
cinap_lenrekminute: btw, is here a switch to detect if the lid is closed?01:03
minutecinap_lenrek: nope01:05
minuteBoostisbetter: http://dump.mntmn.com/screenshot-2022-06-29-01-05-37.png01:06
cinap_lenrekminute: ok :)01:06
minuteBoostisbetter: games do not work yet though as the ones i tried are 64 bit, and i'm running this in box86 (32 bit)01:45
- mtm (QUIT: Ping timeout: 260 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net)02:04
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20)02:20
+ klardotsh (~klardotsh@172.56.105.158)03:15
+ bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com)03:22
flowyminute: masochism. that's all i can say.03:27
+ mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net)03:40
+ Major_Biscuit (~MajorBisc@c-001-032-040.client.tudelft.eduvpn.nl)07:48
+ aliosablack (~chomwitt@2a02:587:dc1c:800:6edf:8c3:2be1:2ef9)08:18
NanoCodeBugOpen On-Chip Debugger 0.11.0 (2021-03-07-12:52)09:29
NanoCodeBugLicensed under GNU GPL v209:29
NanoCodeBugFor bug reports, read09:29
NanoCodeBug        http://openocd.org/doc/doxygen/bugs.html09:29
NanoCodeBugInfo : Listening on port 6666 for tcl connections09:29
NanoCodeBugInfo : Listening on port 4444 for telnet connections09:29
NanoCodeBugInfo : J-Link V11 compiled Mar  3 2022 10:16:1409:29
NanoCodeBugInfo : Hardware version: 11.0009:29
NanoCodeBugInfo : VTarget = 3.306 V09:29
NanoCodeBugInfo : clock speed 1000 kHz09:29
NanoCodeBugInfo : JTAG tap: imx8mq.cpu tap/device found: 0x5ba00477 (mfg: 0x23b (ARM Ltd), part: 0xba00, ver: 0x5)09:29
NanoCodeBugInfo : imx8mq.a53.0: hardware has 6 breakpoints, 4 watchpoints09:29
NanoCodeBugInfo : starting gdb server for imx8mq.a53.0 on 333309:29
NanoCodeBugInfo : Listening on port 3333 for gdb connections09:29
NanoCodeBugInfo : starting gdb server for imx8mq.m4 on 333409:29
NanoCodeBugInfo : Listening on port 3334 for gdb connections09:29
NanoCodeBugoh god sorry09:29
NanoCodeBugmean to just include a few lines of that09:29
NanoCodeBugi have j-link connecting to the a53 cores now09:29
NanoCodeBugnow just to get debug symbols09:48
minuteNanoCodeBug: that's amazing!!10:27
minuteNanoCodeBug: great to see that jtag actually works10:29
NanoCodeBugthe soldering was rough, the som dissipates heat way too well for my hot air station10:31
NanoCodeBughad to use an iron to remove the net, and some dust must have got in the edge connector, i had to reseat it a few times before it would post all the way10:31
NanoCodeBugi just finished building the kernel with dbg info, but its late here now10:33
- aliosablack (QUIT: Remote host closed the connection) (~chomwitt@2a02:587:dc1c:800:6edf:8c3:2be1:2ef9)10:33
minuteNanoCodeBug: good work!10:34
Boostisbetterminute: really impressive that you got the client running. I guess finding x86 games to run is going to be the next challenge. 10:59
Boostisbetterminute: there is probably no way to hook box64 in when trying to start a 64 bit game.11:00
minuteBoostisbetter: i'm not sure. it might be possible but really tricky11:01
+ qwer (~qwer@89-24-50-198.nat.epc.tmcz.cz)11:01
Boostisbetterminute: exactly. Still would be a cool thing, just not for the faint of heart. 11:01
BoostisbetterI do very little gaming today, even though I love it, so this isn't isn't super crucial to me. 11:02
Boostisbetterbut it would be cool to say that you could get it running11:02
Boostisbetterand getting the client already working is very cool11:02
- Major_Biscuit (QUIT: Ping timeout: 264 seconds) (~MajorBisc@c-001-032-040.client.tudelft.eduvpn.nl)12:45
- mjw (QUIT: Killed (NickServ (GHOST command used by wielaard!~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440))) (~mark@gnu.wildebeest.org)13:04
* wielaard -> mjw13:04
+ mark_ (~mark@gnu.wildebeest.org)13:04
- mtm (QUIT: Ping timeout: 268 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net)14:04
nockooof, why do businesses use UPS? Are the rates really good? Is there service not shitty to some locations?15:02
nockoEverytime I order something and see it's shipped UPS I audibly groan. This rant brought to you by some mnt store purchases in UPS limbo...15:03
nockoMaybe Canadian UPS is uniquely shitty?15:04
+ Christoph_ (~Christoph@p54bf60e6.dip0.t-ipconnect.de)15:22
+ mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net)15:34
+ MajorBiscuit (~MajorBisc@wlan-145-94-167-213.wlan.tudelft.nl)15:36
dodomeine güte.. crowd supply wird jetzt erst klar dass ich den zoll selbst bezahlen muss, da wegen der batterien nur mit dhl oder ups verschickt werden kann15:54
dodoaber immerhin, es ist so weit \o/15:55
- qbit (QUIT: Quit: WeeChat 3.5) (~qbit@h.suah.dev)16:34
- Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p54bf60e6.dip0.t-ipconnect.de)16:37
+ reform29230 (~laszlo@g223.219-121-89.ppp.wakwak.ne.jp)16:45
- reform29230 (QUIT: Client Quit) (~laszlo@g223.219-121-89.ppp.wakwak.ne.jp)16:45
+ qbit (~qbit@h.suah.dev)16:47
+ Christoph_ (~Christoph@p54bf60e6.dip0.t-ipconnect.de)17:13
- qwer (QUIT: Remote host closed the connection) (~qwer@89-24-50-198.nat.epc.tmcz.cz)17:34
+ qwer (~qwer@89-24-50-198.nat.epc.tmcz.cz)17:37
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20)18:09
- MajorBiscuit (QUIT: Ping timeout: 264 seconds) (~MajorBisc@wlan-145-94-167-213.wlan.tudelft.nl)18:52
- mjw (QUIT: Quit: Leaving) (~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440)19:07
minutedodo: yep, it's because they found out that they can't ship the batteries with fedex, so the vat preclearing doesn't work... they will refund the vat to you 19:22
minutenocko: i've had pretty good experience with UPS shipping stuff from germany19:22
minutebetter than DHL, so we use UPS exclusively 19:22
+ MajorBiscuit (~MajorBisc@2a02-a461-129d-1-193d-75d8-745d-e91e.fixed6.kpn.net)19:51
+ Guest33 (~Guest33@g223.219-121-89.ppp.wakwak.ne.jp)19:55
Guest33Hi everyone! I have an issue with moving the OS to ssd. Getting the following error when running reform-migrate script at the point when reform-boot-config is started:19:59
Guest33chroot: failed to run command ‘update-initramfs’: No such file or directory19:59
Guest33Does anyone know how to deal with this problem? Thanks19:59
kfxdo you have the initramfs-tools package installed?  20:01
kfxor, I guess, that package would need to be installed in the chroot20:01
kfxwere there any previous error messages?20:01
minutehuh. Guest33 which system image version did you start this from?20:02
Guest33Seems like this package wasn't installed, I will now try again when it's there.20:03
Guest33No, there were no any other errors or warnings20:03
Guest33or, I guess, that package would need to be installed in the chroot20:04
Guest33> how do you install a package in chroot?20:04
Guest33minute I am not sure which version it is20:04
Guest33how can I check the image version?20:05
minuteGuest33: did you download it or was it shipped with the machine?20:05
Guest33it was shipped with the machine20:05
minuteGuest33: /etc/motd has something i think20:05
Guest33System Image v3: 2022-01-2620:06
minuteGuest33: if it's v3, you can probably update by doing apt update && apt upgrade first... or did you do that already?20:06
Guest33yes, I have done it, but may do once more just in case20:07
minuteand i recommend to reboot also after upgrading20:07
Guest33You don't have enough free space in /var/cache/apt/archives/. is what I get20:08
minuteugh20:09
minutei probably forgot to grow your filesystem ;)20:09
Guest33you mean moving /root to nvme?20:10
minuteno, the partition on the sd card is probably too small, smaller than the sd card20:10
minuteGuest33: you can see that with `lsblk`20:10
Guest33ooh, I see what you mean.20:10
minuteif you have another computer, you can grow it20:10
minutegrowpart -u auto /dev/$1 220:10
minutee2fsck -f /dev/${1}220:10
minuteresize2fs /dev/${1}220:11
minutewhere $1 is the sd card device20:11
minute(or i think gnome-disks can do it graphically)20:11
Guest33I just resized it with gnome-disks to take the whole remaining space of the sd card20:12
minutegreat20:12
Guest33In the long run, I want to have the main system to boot directly from the ssd, but with an option to boot from an sd card for some alternative OS(es). How would you go about making this work?20:15
minuteyou can't boot from ssd, but you can boot via emmc20:16
minuteBoostisbetter: according to a person on twitter, steam 32+64 bit is possible. there's a guide (i haven't had time for it though) https://github.com/Heasterian/Box86-64-on-SD845-mobian20:17
Boostisbetterthat is awesome, I'll see if I can find the time, but if you do find some it would be awesome if you could look into it. 20:18
Guest33you can't boot from ssd, but you can boot via emmc> right, I kinda forgot about it . It will be the next step of experimentation once I deal with the first task of using the ssd for /root20:18
BoostisbetterFor what it is worth I switched to an SSD but left the boot device the SD card. You only need it at boot, and can remove it while the system is up, so I just went that route. Plus if you SSD ever dies it seems like it would be easier to move back to running it off the sd card. 20:19
Guest33but once you boot from emmc, is there still a possibility to run an alternative OS from an sd card?20:19
kfxGuest33: you can hack up u-boot to work that way20:20
kfxGuest33: I'm running sigrid's u-boot, and that's how it works for me -- it boots from emmc, then looks for a boot script in the sd slot, then on nvme, and finally on emmc20:20
Guest33kfx right, hacking up u-boot is something I have never done yet, but it sounds like a fun thing to try20:22
Guest33 I'm running sigrid's u-boot, and that's how it works for me -- it boots from emmc, then looks for a boot script in the sd slot, then on nvme, and finally on emmc20:23
Guest33> this sounds exactly like I would try to achieve. do you have any links that would help me with making such set up?20:23
- MajorBiscuit (QUIT: Ping timeout: 272 seconds) (~MajorBisc@2a02-a461-129d-1-193d-75d8-745d-e91e.fixed6.kpn.net)20:24
Guest33sigrid's u-boot20:25
Guest33> what/who is sigrid20:25
Guest33oh I see, it's a person in this chat20:25
kfxI don't have sources or anything, sorry, maybe sigrid will see this and speak up20:26
Guest33no worries, thanks anyways20:29
minuteBoostisbetter: i have the same setup in regards to sd+ssd for the same reason yep.20:29
Guest33I have another question, and it's about running guix os on the reform and if anyone had any success making it work. I have read in the thread on the community forum and the gnu mailing list linked there, although all the messages are from last year and I assume there were some changes to the approach taken20:32
minutei don't know this20:35
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@static-198-54-135-69.cust.tzulo.com)20:40
+ bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com)20:41
- bkeys (QUIT: Ping timeout: 268 seconds) (~Thunderbi@static-198-54-135-69.cust.tzulo.com)20:45
+ bkeys (~Thunderbi@253.236-24.gp.ptn.tftn.static.friendlycity.net)20:59
- Guest33 (QUIT: Quit: Client closed) (~Guest33@g223.219-121-89.ppp.wakwak.ne.jp)21:05
flowyminute: fyi i was having really terrible screen interference problems since using sysimagev3 associated with stronger wifi signals. it was really quite painful at times. i guess it just depends on the particular internal cable layout and antenna placement.21:13
flowya very nice person in the forums sent me some of their emi shielding tame and first try the problems have disappeared21:13
flowy*shielding tape21:14
flowyaround the display connector and some of the cable.21:14
+ Guest33 (~Guest33@g223.219-121-89.ppp.wakwak.ne.jp)21:14
* mark_ -> mjw21:14
flowymaybe you should consider using some kind of shielded connector for future designs21:15
Guest33after running reform-migrate successfully and rebooting the machine I get an error [ end Kernel panic - not syncing: Requested init /sbin/reform-init failed (error -2). ]21:17
Guest33is there a way to resolve this?21:17
minuteah, reform-init does not exist anymore21:19
minuteflowy: thanks, i've seen it and was surprised by it21:19
minuteGuest33: it sounds like you have an older version of u-boot on the sd card :/21:20
minutestrange because `apt upgrade` should have refreshed that21:20
minuteGuest33: sorry for all the trouble. if you don't mind, could you flash the reform-system.img.gz from here on your sd card: https://source.mnt.re/reform/reform-system-image/-/jobs/833/artifacts/browse/reform2-imx8mq/21:21
minute(gunzip first)21:22
Guest33hmm, I see21:22
Guest33will try to flash this image now21:22
minuteGuest33: then it should boot again21:22
minuteGuest33: and then you can try `sudo reform-boot-config nvme`21:23
minuteGuest33: it might be cleaner to do `reform-migrate` again with that fresh sd card though21:23
Guest33thank you for your help. I will go through these steps and let you know if it worked21:24
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@253.236-24.gp.ptn.tftn.static.friendlycity.net)21:27
+ bkeys (~Thunderbi@253.236-24.gp.ptn.tftn.static.friendlycity.net)21:27
vagrantchmmm... i should go dig out my mnt/reform ... it's been stuck in a box for a while ... we'll see how the batteries are holding up :)21:30
minutevagrantc: uh oh!21:31
vagrantcthe firmware upgrades i did seemed to dramatically reduce the powered off drain ... it's been a few weeks21:33
vagrantcand have spare sunshine to top them off21:33
vagrantcso are the batteries for the pocket-reform not lifepo4 ?21:34
vagrantcit say liion if i recall21:34
vagrantcreally love that the mnt/reform takes a wide voltage range ... perfect for solar21:34
+ bkeys1 (~Thunderbi@static-198-54-135-69.cust.tzulo.com)21:42
vagrantchrm. circle key does nothing...21:42
vagrantcoh dear, the cells are very, very drained21:43
- bkeys (QUIT: Ping timeout: 246 seconds) (~Thunderbi@253.236-24.gp.ptn.tftn.static.friendlycity.net)21:44
* bkeys1 -> bkeys21:44
vagrantcsome as low as 0.8v ...21:44
vagrantcthey seem to be recovering ...21:45
vagrantcnegative amperage in the circle-b display means charging?21:51
Boostisbetteryrp21:51
Boostisbetter*yep21:51
vagrantctwo cells really seem to be struggling at 1.4v ... others seem to be doing ok21:52
Guest33vagrantc if I am not mistaken, you must be familiar with guix os. have you tried installing it on the reform?21:53
vagrantci thought the firmware improvements would have allowed leaving it unpowered for longer...21:53
vagrantcGuest33: it's on my eventual agenda ... since it still requires a few kernel patches, it might actually be easier to get supported21:53
Boostisbetteryes it should. But 1.4v is not good for a cell. I make it a habit to leave my reform on power when I'm not using it for more than 6 hours. 21:54
vagrantcalthough the bootloader won't be supportable due to the ddr timing blobs (if i recall correctly)21:54
vagrantci packed it but ended up leaving it packed longer than i had expected21:55
vagrantcnot 100% sure it was fully charged and balanced at the time ... but i *thought* it was pretty high (e.g. ~90+% and balanced)21:55
minutevagrantc: i have a new battery board in testing that will protect the cells. i'm not 100% happy with it yet because 1 cell can still die21:56
minutethat's why it's not yet released21:56
minutealso the next motherboard rev will fix the fundamental issue21:57
Guest33vagrantc do you mean it requires kernel patches for running with libre-kernel or with what's available in the channels too?21:57
vagrantcGuest33: could make a channel to support the bits that aren't appropriate for upstream guix to finish out the rest21:57
vagrantcGuest33: not all the patches for the mnt/reform are upstream21:57
vagrantcmost of the functionlity other than hdmi *should* work with linux-libre21:58
minutethe biggest patch, hdmi, is on the way to upstream by lucas stach21:58
vagrantcminute: look forward to board updates21:58
vagrantcminute: that's good to hear!21:58
vagrantcminute: there's a fundamental issue with the hardware? hrm. ah well, it's probably the most hardware-upgradable-fixable system i have for a reason :)21:59
minutevagrantc: yeah, it can be fixed with a new battery board or a new motherboard22:00
minutevagrantc: i actually used a ADI reference design for the battery monitor which has this bug already22:00
minutelike, in the official design22:00
Guest33vagrantc I see. I've checked all information available on this topic, seems like Christine Lemmer-Webber got some success with making it work, but I am not so certain about it. The blob for DDR4 was mentioned as an obstacle for running fully libre guix22:01
minutewell, the problem is multi-layered22:01
minuteanyway, i understand fully what is going on and it will be fixed22:01
minuteGuest33: what if u-boot incl the blob was added outside of guix?22:02
vagrantcGuest33: yeah, but it should be able to boot guix if you bring-your-own-bootloader22:02
minuteyeah that's what i mean22:02
vagrantcminute: then guix would have to patch out the blob ...22:02
vagrantcoh, you mean, you provide u-boot, yeah, that works22:02
minutevagrantc: yeah.22:02
minuteor u-boot could load it from disk22:03
minuteas a separate file22:03
minutedon't know what's less hassle22:03
vagrantci think the latest u-boot for the mnt/reform supports extlinux.conf ... and it's possible to get guix to generate an appropriate extlinux.conf even if it doesn't install the bootloader22:03
vagrantci don't suppose u-boot supports loading off of nvme?22:03
minutevagrantc: thought experiment: what if the ddrc blob lived on an i2c rom on the motherboard?22:04
sigridGuest33: https://github.com/ftrvxmtrx/void-packages/releases/tag/mntreform2-20220214 shows how to update u-boot on emmc, and the binary in question is at https://ftrv.se/_/mntreform2-u-boot.bin22:04
vagrantcthat's another slight gotcha for guix ... it doesn't support a split /boot partition22:04
sigridand https://github.com/ftrvxmtrx/void-packages/blob/mntreform2/srcpkgs/mntreform2-uboot/files/kernel.d/uboot is how boot.scr is generated in my case22:05
vagrantcminute: it's a somewhat arbitrary GNU Free Software Distribution distinction, but if it's "burned in" to a non-writeable space, it's ok... but if it's writeable ... it's kind of not ok.22:05
vagrantcthere are plenty of holes in that argument, but ... welp, there it is.22:05
minutevagrantc: i see. so i would need to produce a mask rom somehow :D22:06
Guest33sigrid thank you very much for the references22:06
minutevagrantc: i guess EPROMs are illegal?22:06
joschGuest33: you don't need another u-boot -- the u-boot from sysimage-v3 also first looks at the sd-card and then on the emmc22:06
joschvagrantc: the latest u-boot does support extlinux.conf but that's not the one included in sysimage-v322:07
joschGuest33: to flash the latest u-boot version to emmc you can use the reform-flash-rescue script22:07
vagrantcjosch: oh, curious.22:07
minutevagrantc: i know the whole thing is illogical, but it'd be interesting for me to understand what is allowed and what not... so what kind of ROMs are acceptable22:07
vagrantcminute: i'm not an expert on it, that's just what i've gleaned over time22:07
minutevagrantc: and, are you allowed to copy stuff from a ROM into MCU memory (it's not main memory!)22:07
Guest33josch thanks for the tip22:08
minutevagrantc: ok!22:08
vagrantci've fallen behind on mnt/reform stuff (obviously, given the status of my battery pack!)22:08
vagrantcwhich, seems to be at 3.2-3.4 range already ... that feels much better.22:09
minuteinteresting: https://ryf.fsf.org/about/criteria22:09
minute> However, there is one exception for secondary embedded processors. The exception applies to software delivered inside auxiliary and low-level processors and FPGAs, within which software installation is not intended after the user obtains the product. This can include, for instance, microcode inside a processor, firmware built into an I/O device, or the gate pattern of an FPGA. The software in22:09
minutesuch secondary processors does not count as product software22:09
minuteso, if we store the DDRC blob in LPC, it is ok?22:10
vagrantcmaybe!22:10
minuteand then u-boot would just copy it via SPI from LPC to the DDRC22:10
minutelol22:10
vagrantci wonder if you could get the baseboard certified without the cpu board22:11
minute> Some device manufacturers include a CD-ROM with their product that has proprietary Windows drivers for the device. This is unacceptable22:11
minutegood that we don't have a cd-rom22:11
vagrantcif you released a model without an hdmi port, maybe you coudl get that certified too22:12
Guest33so means it's technically possible to run fully libre guix on mnt/reform?22:13
vagrantchave mixed feelings about all that though ... exactly where to draw the line with blobs22:13
minute> Specifically, the seller must use the term "GNU/Linux" for any reference to an entire operating system which includes GNU and Linux, not "Linux"22:13
minutelet me interject for a moment22:13
minutevagrantc: i guess only the FSF committee can decide this 22:13
vagrantci've known people who were doing FSF respects-your-freedom evaluation in the past ... not sure if i know anyone recently connected22:14
* Guest33 -> lszl22:15
vagrantcyay, 3.4-3.6v ... that's approaching pretty normal22:16
minutevagrantc: cool22:17
minutevagrantc: how many days exactly was the thing in a box?22:17
vagrantcACTION rummages around old notes on dates ...22:18
vagrantcminute: i remember the FSF surprisingly endorsing (with caveats) the librem5, which has basically all the same issues, i think, being a very similar SoC22:20
minutelibrem5 was endorsed?22:21
vagrantcnot formally through the RYF thing, but ... some sort of holiday gifty giving thing22:22
vagrantchttps://www.fsf.org/givingguide/v11/22:23
minuteoh, interesting22:23
vagrantcmight be worth working with the purism folks who are vested in getting the full RYF thing ... to see what ways you could comply with the imx8* chips22:25
sknebelThey did that thing where they put the DRAM training firmware on a separate flash chip and used the embedded M4 cores as "secondary processors" right?22:26
vagrantcmaybe22:26
sknebelI guess I was remembering this post and later discussions around it: https://puri.sm/posts/librem5-solving-the-first-fsf-ryf-hurdle/22:27
minutei don't think it was actually done like that in the end22:29
minutehttps://source.puri.sm/Librem5/uboot-imx/-/issues/922:31
- Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p54bf60e6.dip0.t-ipconnect.de)22:32
minuteyeah https://source.puri.sm/Librem5/uboot-imx/-/blob/librem5/debian/bin/fetch-imx-firmware22:33
kfxis there any actual benefit to this or is it just bureacuratic gamesmanship so they can brag about their copyright purity22:34
kfxI'm skeptical of efforts like this where it's just a bunch of extra work to wind up in the same state the reform already sits22:35
vagrantcyeah, it's sometimes a bit dubious22:35
vagrantcthere is something to be said for being clear and transparent about what parts of your system are buildable from source and what are just ... stuff we hope works22:36
kfxno amount of wget juggling and hot patching will un-blackbox the ddr timings, it will just make copyright enthusiasts feel better about their thousand-dollar phones22:36
vagrantcbut a lot of hoop-jumping ... starts to get questionable22:36
kfxmeanwhile the Reform docs just say "here are the parts we don't have source for, and here is why we need them"22:36
sigridGNU/Loophole22:36
minutekfx: there is no benefit22:38
minutealso, we have the ls1082a module, it does not have a ddrc blob (still has a display controller blob for edp... so if that's more important to you than opengl, you could pair it with a 2d thing like sm750 and have a blob-free cortex-a72) 22:39
minutei'm not sure about the cost of producing a small batch of the ls1028a module at the moment though (chip shortages and all)22:39
lszlvagrantc how about running guix with nonguix channel on mnt/reform? to at least be able to use the distro for it's practical benefits22:47
vagrantcminute: regarding how long i neglected my mnt/reform in a box ... my current estimate is 5-8 weeks22:48
vagrantclszl: should be possible ... all it takes is doing the work :)22:49
minutevagrantc: oh, that's great then22:49
lszlvagrantc that's true. I don't have so much expertise in all of this yet, but it will be a fun journey to dig deep and learn how to do it22:52
vagrantcminute: i definitely get nervous seeing lifepo4 cells dropping that far below 2 volts ... but even the 0.8v cells seem to have recovered ok-ish22:55
minutevagrantc: it's not super healthy but they can take a beating22:55
vagrantcit's still charging a little over an amp ... but hasn't yet figured out what the percentage is22:56
minutevagrantc: normal, it will only switch to 100% when it decides that it can squeeze in no more charge22:59
- qwer (QUIT: Ping timeout: 268 seconds) (~qwer@89-24-50-198.nat.epc.tmcz.cz)23:10
+ qwer (~qwer@78-80-106-79.customers.tmcz.cz)23:20
- fsx (QUIT: Remote host closed the connection) (~fsx@durian.61924.nl)23:30
NanoCodeBughmm, in kde the sensor widgets don't work. I wonder whats up with that, they ui for them shows no available data sources23:58

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