| - bkeys (QUIT: Remote host closed the connection) (~Thunderbi@134.22.115.162) | 00:43 | |
| - mjw (QUIT: Ping timeout: 272 seconds) (~mjw@gnu.wildebeest.org) | 01:42 | |
| - mtm (QUIT: Ping timeout: 260 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 02:02 | |
| - nsc (QUIT: Ping timeout: 240 seconds) (~nicolas@15-99-142-46.pool.kielnet.net) | 03:08 | |
| + nsc (~nicolas@94-48-142-46.pool.kielnet.net) | 03:10 | |
| - jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@64.189.201.150) | 03:48 | |
| + mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 04:08 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 04:49 | |
| - sigrid (QUIT: Quit: leaving) (~sigrid@ftrv.se) | 06:15 | |
| - klardotsh (QUIT: Ping timeout: 255 seconds) (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net) | 06:31 | |
| + chomwitt (~chomwitt@2a02:587:7a24:b000:1ac0:4dff:fedb:a3f1) | 07:24 | |
| - b0 (QUIT: Quit: Ping timeout (120 seconds)) (~b0@leo.uberspace.de) | 08:24 | |
| + b0 (~b0@leo.uberspace.de) | 08:24 | |
| + mjw (~mjw@gnu.wildebeest.org) | 11:09 | |
| - mjw (QUIT: Ping timeout: 255 seconds) (~mjw@gnu.wildebeest.org) | 11:42 | |
| - mark_ (QUIT: Quit: Leaving) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 11:51 | |
| + mjw (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 12:50 | |
| - stites (QUIT: Ping timeout: 240 seconds) (~stites@130.44.147.204) | 13:27 | |
| + stites (~stites@2607:fb90:ad62:9844:b792:bda4:37c7:7710) | 13:29 | |
| - mtm (QUIT: Ping timeout: 255 seconds) (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 14:04 | |
| + jacobk (~quassel@64.189.201.150) | 14:05 | |
| + bkeys (~Thunderbi@134.22.115.162) | 14:16 | |
| minute | i think a311d image is missing a usb hub reset for pre-2.5 motherboards | 14:44 |
|---|---|---|
| - bkeys (QUIT: Remote host closed the connection) (~Thunderbi@134.22.115.162) | 14:47 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 14:52 | |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@64.189.201.150) | 14:53 | |
| + bkeys (~Thunderbi@134.22.115.162) | 14:58 | |
| - stites (QUIT: Read error: Connection reset by peer) (~stites@2607:fb90:ad62:9844:b792:bda4:37c7:7710) | 15:05 | |
| + stites (~stites@130.44.147.204) | 15:06 | |
| + jacobk (~quassel@129.110.242.224) | 15:06 | |
| - abortretryfail (QUIT: Ping timeout: 260 seconds) (~arf@146.ip-149-56-132.net) | 15:11 | |
| - mark_ (QUIT: Ping timeout: 240 seconds) (~mjw@gnu.wildebeest.org) | 15:28 | |
| + abortretryfail (~arf@146.ip-149-56-132.net) | 15:30 | |
| + murphnj (~murph@user/murphnj) | 15:53 | |
| + mtm (~mtm@c-71-228-84-213.hsd1.fl.comcast.net) | 16:10 | |
| - jacobk (QUIT: Ping timeout: 255 seconds) (~quassel@129.110.242.224) | 16:19 | |
| + jacobk (~quassel@utdpat241106.utdallas.edu) | 16:24 | |
| josch | ls1028a is still in berlin according to ups tracking :( | 16:52 |
| josch | scheduled or arrival on thursday | 16:52 |
| josch | folks seems to be having a long weekend :) | 16:52 |
| josch | minute: could we quickly revisit the decision to not preserve ${bootargs} in ubootenv.d/00reform2_ubootenv? I've now come across a few forum posts like https://community.mnt.re/t/screen-goes-black-after-boot/1653/7 which suggest to add XY to ${bootargs} to see if it fixes the problem. grepping the IRC logs it happened a few times that you or others suggested to edit the cmdline this or that way to try | 16:55 |
| josch | something out. If ubootenv.d/00reform2_ubootenv does not respect ${bootargs}, then there is no good way anymore to do any of this other than editing ubootenv.d/00reform2_ubootenv itself which is bad advice as that file is not meant to be edited by the user (because it will be overwritten during the next upgrade). Stuf in /etc like /etc/default/flash-kernel is meant to be user-controlled configuration | 16:55 |
| josch | but now gets ignored. | 16:56 |
| josch | I understand the motivation to make sure that no bad kernel option ends up in the final cmdline but this also takes away quite a bit of flexibility and i think it would be surprising to some users why the value they set in u-boot env is not picked up by the kernel. This already happened a few days ago. | 16:56 |
| josch | The platforms that must not receive the default /etc/default/flash-kernel for imx8mq have their own system image that ships without /etc/default/flash-kernel anyways, right? So respecting ${bootargs} would only be a problem for people who migrate their system from one SoM to another without adjusting or deleting their /etc/default/flash-kernel. Is that enough of a reason? | 16:58 |
| josch | well, what i meant as "quickly" became a wall of text, sorry XD | 17:06 |
| sevan | it's just a case of having an up to date v3 system image & doing the hardware swap when the thing arrives? | 17:16 |
| josch | sevan: not quite because the hardware you swap contains your /boot partition on its emmc :) | 17:18 |
| josch | with sysimage-v4 though you can have the exact same rootfs and only have /boot differ | 17:18 |
| sevan | ah, right. | 17:23 |
| minute | josch: oooh true there is a holiday wedged in between | 17:25 |
| minute | josch: i can follow your reasoning, and agree... it is mainly a problem for existing installs. | 17:26 |
| minute | josch: i need to check if ls1028a and a311d don't have any "bad" default bootargs | 17:27 |
| josch | yes, if it is only a problem for people migrating to another SoM, removing or changing /etc/default/flash-kernel could just be one of the steps in the documentation that explains how to move from imx to a different SoM | 17:56 |
| - marty_mcfly88 (QUIT: Quit: No Ping reply in 180 seconds.) (~quassel@2603-6000-8c01-0f3e-7dac-14c7-19c1-fd5c.res6.spectrum.com) | 18:13 | |
| + marty_mcfly88 (~quassel@2603-6000-8c01-0f3e-7dac-14c7-19c1-fd5c.res6.spectrum.com) | 18:14 | |
| - jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@utdpat241106.utdallas.edu) | 18:17 | |
| + jacobk (~quassel@129.110.242.224) | 18:26 | |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@129.110.242.224) | 18:35 | |
| + klardotsh (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net) | 19:10 | |
| - stites (QUIT: Ping timeout: 240 seconds) (~stites@130.44.147.204) | 19:26 | |
| + stites (~stites@2607:fb91:dc1:c8a5:8789:bf98:6bc7:9cd4) | 19:27 | |
| - Boostisbetter (QUIT: Ping timeout: 258 seconds) (4a410829d7@irc.cheogram.com) | 19:44 | |
| - colinsane (QUIT: Quit: bye) (~colinunin@97-113-128-229.tukw.qwest.net) | 19:52 | |
| + jacobk (~quassel@utdpat242016.utdallas.edu) | 19:53 | |
| + colinsane (~colinunin@97-113-128-229.tukw.qwest.net) | 19:54 | |
| - stites (QUIT: Read error: Connection reset by peer) (~stites@2607:fb91:dc1:c8a5:8789:bf98:6bc7:9cd4) | 19:59 | |
| + stites (~stites@130.44.147.204) | 20:00 | |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@utdpat242016.utdallas.edu) | 20:02 | |
| - nsc (QUIT: Ping timeout: 240 seconds) (~nicolas@94-48-142-46.pool.kielnet.net) | 20:07 | |
| + nsc (~nicolas@84-97-142-46.pool.kielnet.net) | 20:09 | |
| + jacobk (~quassel@utdpat241040.utdallas.edu) | 20:15 | |
| + Boostisbetter (4a410829d7@irc.cheogram.com) | 20:32 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 20:32 | |
| - bkeys (QUIT: Remote host closed the connection) (~Thunderbi@134.22.115.162) | 20:33 | |
| - mjw (QUIT: Killed (NickServ (GHOST command used by mark_!~mjw@gnu.wildebeest.org))) (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 20:38 | |
| * mark_ -> mjw | 20:38 | |
| + mark_ (~mjw@2001:1c06:2488:1400:4fd:39a7:74ac:7bae) | 20:39 | |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.32.204) | 20:46 | |
| + Ar|stote|is (~linx@149.210.32.204) | 20:49 | |
| - jacobk (QUIT: Ping timeout: 255 seconds) (~quassel@utdpat241040.utdallas.edu) | 20:57 | |
| abortretryfail | woah, my Reform drained its batteries down to 1.6V yesterday... wtf | 21:00 |
| Boostisbetter | Oh really? DO you have the new battery save boards? | 21:01 |
| abortretryfail | no, it wasn't an option from CrowdSupply when I got it this spring | 21:02 |
| Boostisbetter | If you can I would recommend picking those up, they specifically prevent this kind of draining. | 21:02 |
| abortretryfail | I think I put it to sleep Sunday morning and went out. Then I grabbed it today just now to use it and it was totally dead. | 21:03 |
| Boostisbetter | yeah that really sucks. However, the Reform will run with no batteries in at well. | 21:04 |
| Boostisbetter | There is a chance you might be able to revive the cell though. | 21:04 |
| Boostisbetter | minute or josch would know better than me on the specifics there though. | 21:04 |
| abortretryfail | i'm familiar with the process. I rescue totally "dead" cells from salvage laptop packs all the time. It's just surprising to see them that low. | 21:05 |
| Boostisbetter | yeah | 21:06 |
| abortretryfail | It's charging right now with -1.47A so i don't think they need rescue | 21:06 |
| Boostisbetter | yeah that sounds good. | 21:06 |
| Boostisbetter | seems like you dodged a bullet on that one. | 21:06 |
| abortretryfail | I just wonder *why* it did it | 21:07 |
| Boostisbetter | there is no under voltage protection in the original battery boards. | 21:09 |
| Boostisbetter | hence the revision and upgrade. | 21:09 |
| Boostisbetter | the Reform has incrementally improved a lot, but with steady changes over a period of time. | 21:10 |
| abortretryfail | the lpc has low voltage shutoff stuff in the code, i wonder if it got stuck or hung somehow | 21:10 |
| Boostisbetter | Just be mindful that this is something that can happen in the future, until you get the new battery boards. | 21:11 |
| abortretryfail | yeah, not putting it to sleep again until i get those. | 21:13 |
| Boostisbetter | minute: the wifi card supplied with the Reform does not do Bluetooth right? | 21:14 |
| abortretryfail | mine doesn't | 21:14 |
| minute | Boostisbetter: it does not. | 21:14 |
| Boostisbetter | abortretryfail: it will do it when not in sleep as well. | 21:14 |
| Boostisbetter | just needs to be on a charger if not going to be used for a long period of time (read more than 8 hours) | 21:14 |
| Boostisbetter | or off | 21:15 |
| abortretryfail | Boostisbetter: so the undervoltage state in the lpc code doesn't turn off the SoM correctly then? | 21:15 |
| Boostisbetter | minute: any advice on what software I can install to control a BT plugable dongle? | 21:16 |
| Boostisbetter | abortretryfail: I am not sure of the specifics, I just know that undervoltage protection was not working correctly on the previous battery boards. | 21:16 |
| minute | abortretryfail: it normally does, but then the batteries are already at the edge, and there is some ongoing drain (although quite small) from LPC waking up periodically | 21:16 |
| minute | abortretryfail: there was also a design error which makes the system turn _on_ in a very low voltage situation | 21:17 |
| abortretryfail | I bet that's what happened. I doubt the LPC could have drained them that low on its own | 21:17 |
| minute | abortretryfail: i.e. there's a UVLO resistor on the LPC's power supply. but that's not good because the LPC keeps the main regulators _off_. if it doesn't run, they turn on | 21:17 |
| minute | abortretryfail: a workaround is to remove this uvlo circuit and make sure EN on 3v3 standby regulator is always pulled up | 21:18 |
| abortretryfail | Fixed in MB 2.5 like the headphone jack's decoupling caps? | 21:19 |
| minute | yep | 21:19 |
| minute | and also the protected battery boards are included in all new builds (since we launched them) | 21:20 |
| abortretryfail | I'll have to take a look at the schematic and see if i can fix that too. I was planning on tacking some extra capacitors on to fix the headphone bass anyway. | 21:21 |
| abortretryfail | Boostisbetter: re: bluetooth, I just use bluetoothctl | 21:22 |
| abortretryfail | never had great luck with the tray applets | 21:23 |
| Boostisbetter | doesn't seem to be in the Debian repo. Or is it under a different package name? | 21:23 |
| abortretryfail | part of bluez i think | 21:25 |
| minute | Boostisbetter: blueman-applet / blueman-tray / blueman-manager | 21:29 |
| minute | it also ships with the standard config of sys image v4. | 21:30 |
| Boostisbetter | thanks! bluetoothctl doesn't seem to support audio agents | 21:34 |
| Boostisbetter | minute: any idea what the package name for those are? Because trying to install it with blueman is using bluez components instead of blueman elements you mentioned. | 21:37 |
| Boostisbetter | minute: disrregard. was just blueman. | 21:44 |
| Boostisbetter | I was just getting thrown off that it was saying it was including bluez, but it turns out that blueman utlitzes that for the backend work. | 21:53 |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.32.204) | 21:54 | |
| + Ar|stote|is (~linx@149.210.32.204) | 21:56 | |
| minute | Boostisbetter: bluez is required for blueman. | 21:56 |
| - Ar|stote|is (QUIT: Client Quit) (~linx@149.210.32.204) | 21:59 | |
| + bkeys (~Thunderbi@134.22.115.162) | 22:00 | |
| - bkeys (QUIT: Client Quit) (~Thunderbi@134.22.115.162) | 22:00 | |
| + Ar|stote|is (~linx@149.210.32.204) | 22:01 | |
| + jacobk (~quassel@utdpat241106.utdallas.edu) | 22:18 | |
| josch | concerning the system switching off when volatage is too low i once had the funny situation that i had the system on and had forgotten to put the plug in | 22:23 |
| josch | when i came back it was off of course but i did not yet realize that it was off because i forgot to plug it in | 22:24 |
| josch | so i switched it on and it managed to boot, i entered my luks passphrase, then logged in | 22:24 |
| josch | then in sway i noticed the battery status | 22:24 |
| josch | i reached to the power cable and that's when it went off again | 22:24 |
| minute | eek | 22:26 |
| josch | my system switches off at around 9-10% according to the oled (which shows the identical value as sway) so when sway showed me 9% remaining after having booted i thought i had a few more seconds to get the cable than i actually did :D | 22:28 |
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.32.204) | 22:33 | |
| + Ar|stote|is (~linx@149.210.32.204) | 22:36 | |
| sevan | this doesn't affect the Reform but I'm mentioning it since it's for the standard SATA version of SSDs (not m.2) but the WD Green drives have a new firmware for critical issues, and I realised the only way to update it is with a machine running Windows, what a faff. https://support-en.wd.com/app/answers/detailweb/a_id/51127/h/p2 | 22:39 |
| sevan | I do have a WD Black installed in my reform however. No recent version of Windows, nor a PC with nvme slot onboard. | 22:40 |
| sevan | I think I'm complaining about WD's firmware update mechanism in the room for mnt-reform. ignore. ;) | 22:42 |
| josch | remember the days when you bought hardware and the firmware that came with it was just it forever? :) | 22:44 |
| sevan | need more EEPROMs! | 22:45 |
| minute | i personally use wd blue 2tb in my reform | 22:59 |
| sevan | I went for the black because it was on sale I think. there's some impressive heatsinks on some of these drives. very fashionable :) | 23:04 |
| sknebel | If you push them NVMe drives can use cooling, its not entirely pointless/for show | 23:06 |
| - stites (QUIT: Ping timeout: 240 seconds) (~stites@130.44.147.204) | 23:07 | |
| sevan | sknebel: joke: yes but the battle field 2042 logo does add armor to it, right? | 23:07 |
| + stites (~stites@2607:fb90:ad61:8dda:f76b:db35:422d:4ab8) | 23:07 | |
| sknebel | dont get me started on weird logos and slogans on hardware ... | 23:08 |
| sevan | :D | 23:08 |
| josch | honestly, i'd be happy to have the MNT on my reform a bit more visible than it is | 23:08 |
| sknebel | like I sort of get the entire thing with PCs with windows in them and cool looking hardware... except 90% of high-end stuff is plastered in what amounts to ads | 23:08 |
| josch | it annoys me to be a walking advertisement for IBM, Lenovo etc but having an MNT device makes me quite proud to show off | 23:09 |
| sknebel | you could line it with something | 23:09 |
| sknebel | been thinking about copper tape | 23:09 |
| Zaba | nobody ever got fired for buying MNT | 23:09 |
| minute | perhaps one could make a different screen back that has some perforation along the logo | 23:09 |
| minute | the innolux display at least is open at the back and provides a light to the back | 23:10 |
| sknebel | a PCB that snugly fits in it would also be fun, if you get a really thin one it could fit into the recess (without components of course) | 23:10 |
| sevan | Zaba: <3 | 23:11 |
| sevan | minute: will things eventually lead to an animated started up logo, just like in the laptop scene from hackers? I hope so :) | 23:14 |
| minute | sevan: hehe | 23:18 |
| Boostisbetter | I don't know team, I feel like the MNT logo on the Reform is perfect as is. I think the clear bottom is the biggest logo there could be for MNT. | 23:18 |
| Boostisbetter | I'm pumped about the pocket though, and I am happy that it doesn't have a see through something because we need durability even more on a mobile device. I think it is going to be awesome. | 23:19 |
| Boostisbetter | Really looking forward to getting my pocket all set up as well as I have the Reform. | 23:19 |
| josch | Boostisbetter: do you follow Lukas on mastodon? There were some new Pocket posts today. :) | 23:32 |
| Boostisbetter | you bet I do. Let me check them out. | 23:36 |
| Boostisbetter | aww yeah! | 23:37 |
| Boostisbetter | minute: hope the 3d fit tests all worked and things fit, and new PCB are ordered. Hahaha! | 23:37 |
| - chomwitt (QUIT: Ping timeout: 264 seconds) (~chomwitt@2a02:587:7a24:b000:1ac0:4dff:fedb:a3f1) | 23:50 | |
| - stites (QUIT: Read error: Connection reset by peer) (~stites@2607:fb90:ad61:8dda:f76b:db35:422d:4ab8) | 23:54 | |
| + stites (~stites@130.44.147.204) | 23:55 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!