| sigrid | minute: heya! I am reading lpc firmware code and wonder how "capacity_min_ampsecs" is supposed to be treated by the OS, ie whether it's "give a warning to the user" or "system has to be shut down to save the batteries from getting destroyed" | 00:08 |
|---|---|---|
| minute | sigrid: give a warning, because that's only a best guess fuel count | 00:08 |
| sigrid | acpi defines both of these separately and I want to map this value somehow | 00:08 |
| sigrid | ok, thanks :) | 00:08 |
| minute | sigrid: it's like, how many amp seconds (amp hours * 3600) do we think are left in the tank | 00:09 |
| sigrid | the "accu" value is only a somewhat rough estimation, right? | 00:10 |
| sigrid | I can see that cells with different (from the original) capacities would need to have a different value set in the firmware too, is my understanding correct? | 00:11 |
| minute | that is correct | 00:13 |
| minute | originally i wanted to make some tool that would let you set this up | 00:13 |
| sigrid | guess now with spi it could be more feasible | 00:13 |
| minute | yeah | 00:14 |
| + arminweigl_ (~arminweig@sourcehut/user/arminweigl) | 01:21 | |
| - arminweigl (QUIT: Ping timeout: 268 seconds) (~arminweig@sourcehut/user/arminweigl) | 01:22 | |
| + arminweigl (~arminweig@sourcehut/user/arminweigl) | 01:24 | |
| - arminweigl_ (QUIT: Ping timeout: 252 seconds) (~arminweig@sourcehut/user/arminweigl) | 01:25 | |
| + dustfing` (~user@d75-159-228-218.abhsia.telus.net) | 01:50 | |
| - dustfinger (QUIT: Ping timeout: 252 seconds) (~user@d75-159-228-218.abhsia.telus.net) | 01:51 | |
| - mtm (QUIT: Ping timeout: 252 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 02:04 | |
| smj | my 4th mnt reform arrived. This one required import duty to be paid of $37.73. | 03:09 |
| smj | the fun part is putting it together | 03:12 |
| smj | very good design and instructions | 03:12 |
| josch | When I put together mine, I was surprised how much was already put together. I wouldn't have minded if there were more parts that needed assembly. But of course that is a trade-off. :) | 03:36 |
| smj | me too! | 03:37 |
| smj | a decent savings, plus you get more familiar with the reform doing this | 03:38 |
| smj | oh, it needs a firmware update. | 04:04 |
| smj | sigrid has an update for the plan9front LPC stuff and needs newer firmware | 04:05 |
| + mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 04:10 | |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149-210-4-123.mobile.nym.cosmote.net) | 05:22 | |
| + Ar|stote|is (~linx@149-210-4-123.mobile.nym.cosmote.net) | 05:23 | |
| - Ar|stote|is (QUIT: Client Quit) (~linx@149-210-4-123.mobile.nym.cosmote.net) | 05:24 | |
| + Ar|stote|is (~linx@149-210-4-123.mobile.nym.cosmote.net) | 05:24 | |
| - Ar|stote|is (QUIT: Client Quit) (~linx@149-210-4-123.mobile.nym.cosmote.net) | 05:24 | |
| Boostisbetter | minute: wayfire seems to work well on the Reform. I was surprised at how snappy it seemed in your video. What are your thoughts? Are you switching to it from Sway? | 05:24 |
| + Ar|stote|is (~linx@149-210-4-123.mobile.nym.cosmote.net) | 05:24 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 06:03 | |
| + ajr_ (~ajr@user/ajr) | 06:31 | |
| - ajr (QUIT: Ping timeout: 255 seconds) (~ajr@user/ajr) | 06:34 | |
| josch | minute: you mentioned that you are interested in opinions for market research reasons. Here another datapoint. I showed my wife the pocket reform today. What impressed her most was the design. She finds the pocket reform extremely cute, especially with the mini trackball and the purple aluminium case. | 07:36 |
| - ajr_ (QUIT: Quit: WeeChat 3.6) (~ajr@user/ajr) | 09:06 | |
| + Smith42 (~Smith42__@147.197.221.58) | 09:54 | |
| + qwer (~qwer@37-48-17-181.nat.epc.tmcz.cz) | 10:10 | |
| eery | oh nice, chromium no longer stutters on startup with the etnaviv out-of-memory errors on the 5.19 kernel | 11:26 |
| minute | nice | 11:34 |
| + oomono (uid328183@id-328183.tinside.irccloud.com) | 11:37 | |
| eery | I wonder if it'd solve some of the issues with the TS buffer sharing patchset | 11:40 |
| eery | it's really cool how far the software work has gone, and your efforts to upstream the patches -- with the sysimage kernel/initrd I can boot into an unmodified copy of Fedora, open a wayland compositor, and run "chromium-browser" and get an accelerated, wayland-native chromium window with no artifacting now | 11:46 |
| josch | wow, that's awesome! :) | 11:49 |
| josch | eery: but now you are stuck with the initrd you have, no? As far as I remember Fedora uses completely different tooling to build their own initramfs. | 11:49 |
| eery | well, yeah, although I know enough about dracut I think I could generate one if I really wanted to | 11:52 |
| eery | to be honest since nothing is broken I'm pretty content with the arrangement | 11:53 |
| eery | I know that it probably shouldn't work and will probably eventually break, but I'll happily abuse it until it does ;) | 11:53 |
| minute | eery: could you write a little recipe on how to try this? fedora i mean | 11:54 |
| josch | eery: it would help a lot of other people if you'd invest some time to set it up properly :) | 11:54 |
| josch | It would probably even be possible to patch reform-system-image to output an image based on Fedora instead of Debian. | 11:55 |
| eery | I probably will once I'm back in the US and get a proper nvme, I've been running off the 32GB card this whole time haha | 11:55 |
| eery | minute: I can, it's very straightforward actually | 11:55 |
| minute | great | 11:56 |
| eery | It basically boils down to just creating two ext4 partitions (like in debian), copying the boot partition verbatim, and copying the aarch64 raw image from fedora into the second partition | 11:56 |
| eery | then just changing the UUIDs in /etc/fstab | 11:56 |
| eery | (and copying /lib/modules/<x> from the debian image) | 11:56 |
| josch | But the initramfs encodes the knowledge where to boot from -- how do you obtain an initramfs that has the correct options set? | 11:57 |
| eery | I have no explanation for why it works, just that I copy the files from the sysimage /boot partition and it does work :P | 11:58 |
| eery | no modifications | 11:58 |
| eery | how does the default initrd encode the rootfs? By UUID or does it use /dev/ paths? | 12:01 |
| josch | eery: wait, you are booting Fedora from SD-Card? | 12:03 |
| eery | yes, because I am being lazy and haven't gotten an nvme drive yet :| | 12:03 |
| josch | eery: that's why it works :) | 12:04 |
| josch | the initramfs of the sysimage-v3 is meant to be written to an SD-Card, so the initramfs of the sysimage-v3 is set up such that it expects the rootfs on your SD-Card | 12:04 |
| eery | Makes sense | 12:05 |
| josch | This works because the sysimage-v3 uses /dev entries in /etc/fstab: https://source.mnt.re/reform/reform-system-image/-/blob/main/reform2-imx8mq/mkuserland.sh#L28 | 12:05 |
| josch | It doesn't use UUID because at the time that /etc/fstab is created, the filesystems have not been created yet. | 12:05 |
| eery | Before I was just copying the sysimage /boot partition, I just used a really simple boot.scr I adapted from the gentoo page on reform and manually specified a root in the bootargs, e.g. "root=PARTUUID="8b868269-02" rootfstype=ext4 rootflags=rw" | 12:05 |
| eery | no idea if that'd override the config inside an initrd, but it worked with whatever image I was using then | 12:06 |
| josch | yes, arguments by the bootloader override settings in the initramfs | 12:07 |
| josch | this is by design, so that you can still change stuff without having booted and created a new initramfs first | 12:07 |
| eery | I got my reform in the mail the night before traveling internationally for 6 months so it's been a real hack'n'slash adventure in IT | 12:07 |
| josch | oh wow XD | 12:07 |
| eery | I was running void linux for a while but I decided I'd had enough pain and suffering, so I switched to Fedora - I probably should have just switched to the v3 sysimage but I've been running lots of fedora/rhel-clones at work, so it's "in my fingers" | 12:10 |
| - qwer (QUIT: Ping timeout: 252 seconds) (~qwer@37-48-17-181.nat.epc.tmcz.cz) | 12:39 | |
| + qwer (~qwer@89-24-41-218.nat.epc.tmcz.cz) | 12:40 | |
| - mjw (QUIT: Killed (NickServ (GHOST command used by wielaard!~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440))) (~mark@gnu.wildebeest.org) | 13:05 | |
| * wielaard -> mjw | 13:05 | |
| + mark__ (~mark@gnu.wildebeest.org) | 13:06 | |
| Smith42 | eery, what do you think of fedora? I'm wondering if it is worth switching from debian for new hardware compatibility... | 13:47 |
| josch | Smith42: which component in Debian is outdated such that your hardware isn't working with it? | 13:49 |
| eery | I like it, it's not perfect, but for me it's a very practical compromise in terms of getting regular stable releases with lots of packages in the repos | 13:57 |
| minute | at the moment we're on the latest released kernel, so i don't know if there's much more hardware support to gain | 13:58 |
| eery | josch: I'm assuming the problem is if you want to use a stable release, then on Debian you're stuck with increasingly outdated versions of e.g. the kernel and mesa | 13:58 |
| eery | I'm also assuming Smith42 is talking about debian on non-reform hardware haha | 13:58 |
| josch | Ah yes, that is of course correct. If you want a stable OS then of course versions will become outdated. Unfortunately we never managed to do any rolling releases in Debian. The best we have is to just use "testing" but that's also not ideal during the times when we freeze the archive to prepare for the next stable release. | 14:01 |
| eery | I like debian, but I'm a little allergic to Sid, and in my experience I tend to prefer it either in containers or in VMs | 14:02 |
| josch | That is a very sensible approach. :) | 14:02 |
| eery | When you need both stable release engineering and "relatively bleeding edge" is where Fedora shines IMO | 14:02 |
| josch | eery: I don't know much about Fedora. How do they do it? | 14:03 |
| - mtm (QUIT: Ping timeout: 244 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 14:03 | |
| eery | (note that fedora does lean into the bleeding part of bleeding edge, and has sharp edges, so...) | 14:03 |
| eery | Combination of a greater tolerance for "dramatic changes" than Debian (not always a good thing) and a bi-annual release cycle, I think | 14:04 |
| eery | That, and Fedora is basically RedHat's version of Sid for RHEL, so it gets all their work pumped into it | 14:05 |
| eery | I'm not intimate with the details, but RHEL releases are basically forks of a given Fedora release that gets support for 5-7 years or however long it is | 14:05 |
| Smith42 | eery, sorry I misread the chat; thought this was the "linux" chat! | 14:08 |
| Smith42 | yes I was asking about different hardware (framework laptop) | 14:09 |
| eery | well, it's still relatively on-topic here anyway ;) lol | 14:09 |
| josch | :D | 14:10 |
| eery | My biggest complaint about fedora (which kind of applies to debian, though more out of ignorance) is how ... black-magic the build system is | 14:13 |
| eery | the tooling around rpm and dpkg is really ... enormous and, uh, hacked together | 14:14 |
| eery | compared to a more "modern" distro, like say Void, where it takes about an afternoon to figure out how the package manager works and how releases/images are created | 14:14 |
| josch | the problem in Debian is, that people cannot agree on a single way to do things. So instead maintainers have 20 different options how they want to package their stuff and there is literally no Debian Developer who knows all of the ways how stuff can be packaged. Modern distros have a single way to do things and that's really nice. | 14:17 |
| eery | It's definitely a problem, but it's also really hard to beat the sheer inertia of dpkg and rpm (and apt-get and yum/dnf and whatever else) | 14:19 |
| eery | I've not looked too deeply into it, but I think fedora tries to "solve" the problem through aggressive usage of (really) heavy containers and really exhaustive scripts for setting up build environments :| | 14:19 |
| eery | something something Mock | 14:19 |
| sigrid | void linux gave me the least amount of pain and suffering | 14:40 |
| - qwer (QUIT: Remote host closed the connection) (~qwer@89-24-41-218.nat.epc.tmcz.cz) | 14:52 | |
| + qwer (~qwer@89-24-41-218.nat.epc.tmcz.cz) | 15:05 | |
| Boostisbetter | hello everyone from a Purism Librem 5. Hope my fellow Reformers are doing well. | 15:45 |
| minute | Boostisbetter: hello from a Pocket Reform with the same SoC. | 15:46 |
| bkeys | What is the estimated price of a pocket reform going to be? | 15:47 |
| Boostisbetter | minute: want to trade? 🤣️ | 15:47 |
| bkeys | Apparently the stuff to repair my reform came in a few days ago; hopefully I get it back in my hands soon | 15:48 |
| minute | Boostisbetter: no :D | 15:48 |
| Boostisbetter | minute: i'm super pumped for the Pocket. | 15:49 |
| Boostisbetter | and i understand wanting to trade. if i was you i wouldn't want to either. | 15:49 |
| Smith42 | The pocket reform looks so cool! Do we have an estimated release date? | 15:57 |
| minute | not yet | 16:06 |
| + mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 16:10 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 16:30 | |
| vagrantc | curious how feasible it would be to use the mnt reform2 CPU module on the pocket reform ... | 17:09 |
| vagrantc | or if it is fundamentally incompatible in some way... | 17:09 |
| vagrantc | guess the crowdfunding page says it's possible | 17:10 |
| josch | in that sense it would also be interesting if it will be possible to buy the pocket reform (or even the big reform) without any CPU module? | 17:19 |
| vagrantc | i was most interested in a ram upgrade :) | 17:22 |
| vagrantc | would be curious to see how the pockey keyboard layouy works ... might like that better than the mnt reform2 layout | 17:26 |
| minute | vagrantc: i am using that module in this very moment | 17:42 |
| vagrantc | i presume some fiddling with device-tree or whatnot? | 17:43 |
| minute | yeah, it has a different dts than reform | 17:48 |
| minute | for example, it uses a mipi dsi display directly | 17:48 |
| minute | and a different audio chip | 17:49 |
| - Smith42 (QUIT: Ping timeout: 244 seconds) (~Smith42__@147.197.221.58) | 18:23 | |
| sigrid | have anyone using the trackball started experiencing any kind of strain in your wrist/fingers at any point? | 18:46 |
| sigrid | not sure it's related in my case but just trying to find the reason :) | 18:47 |
| minute | sigrid: hmm for me it was more like the opposite... i.e. strain from mouse and less from the trackball. but probably everyone is different | 18:48 |
| sigrid | my desk situation sucks (it's a bit higher than I would like it) so who knows, many variables | 18:50 |
| sigrid | I used mnt for months with a better desk before moving to a new place, did not experience any problems | 18:50 |
| Boostisbetter | sigrid: it could just be the front of the reform case and your wrists and the angle that you are using it. | 19:06 |
| + monkeybusiness (~monkbusy@user/monkeybusiness) | 19:43 | |
| Boostisbetter | I know that with me, when I am using the laptop when I am angled as coming down on it with my arms, that I can use it for much longer. I love the design of the case though. It almost single handed brought me to buying the Reform. | 20:14 |
| Boostisbetter | Now that being said, as I just got my Librem 5 phone, I have to say that while Purism has really done alot of great work on the phone, that I really think the SoC shines in the Reform. I find that I am just trying to use the phone in the same way that I use the Reform, and I think this is why I am so looking forward to the Pocket Reform. | 20:15 |
| jfred | sigrid: Are you using the original stock trackball cup without metal bearings or the newer one with them? The older one would have given me arm pain (I have RSI, many things do) but the newer one mostly does not | 20:51 |
| sigrid | I think it's a new one | 20:55 |
| swivel | fwiw i used to get some RSI-like pains ages ago but everything along those lines disappeared once I started doing pushups daily, i suspect having any strenuous activity mixing it up a bit would help | 21:00 |
| - oomono (QUIT: Quit: Connection closed for inactivity) (uid328183@id-328183.tinside.irccloud.com) | 21:06 | |
| Boostisbetter | yep, strength training is the surprising answer to a great many questions / problems. | 21:14 |
| + ajr (~ajr@user/ajr) | 21:16 | |
| - mjw (QUIT: Killed (NickServ (GHOST command used by mark__!~mark@gnu.wildebeest.org))) (~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440) | 21:43 | |
| * mark__ -> mjw | 21:43 | |
| + wielaard (~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440) | 21:44 | |
| + Smith42 (~Smith42__@2a02:c7c:3899:a300:26ec:99ff:fe5b:dfb6) | 22:00 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 22:06 | |
| + bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 22:07 | |
| minute | sigrid: maybe you could use an external mouse with it for a while to test if there's a difference | 22:11 |
| sigrid | hmm, that's a good idea | 22:11 |
| sigrid | I'll do that | 22:11 |
| - Smith42 (QUIT: Ping timeout: 268 seconds) (~Smith42__@2a02:c7c:3899:a300:26ec:99ff:fe5b:dfb6) | 22:20 | |
| - monkeybusiness (QUIT: Ping timeout: 252 seconds) (~monkbusy@user/monkeybusiness) | 23:28 | |
| + monkeybusiness (~monkbusy@103.87.94.35) | 23:34 | |
| - monkeybusiness (QUIT: Changing host) (~monkbusy@103.87.94.35) | 23:34 | |
| + monkeybusiness (~monkbusy@user/monkeybusiness) | 23:34 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!