| - glu (QUIT: Ping timeout: 252 seconds) (~glu@user/glu) | 00:12 | |
| + glu (~glu@user/glu) | 00:12 | |
| sevan | created a new merge request to address the jitter issue caused by the hint about powering on with the v4 keyboard when the system is up. It doesn't cover when the systems is off and a keyboard reset is issued but I'll dig in when my cable has turned up. | 00:34 |
|---|---|---|
| - Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.4.16) | 01:00 | |
| + Ar|stote|is (~linx@149.210.4.16) | 01:00 | |
| - mtm (QUIT: Ping timeout: 265 seconds) (~textual@47.202.75.129) | 01:04 | |
| + mtm (~textual@47.202.75.129) | 01:06 | |
| - aloo_shu (QUIT: Ping timeout: 246 seconds) (~aloo_shu@90.166.99.246) | 02:01 | |
| - pandora (QUIT: Quit: Connection closed for inactivity) (uid585533@id-585533.ilkley.irccloud.com) | 02:10 | |
| + cobra_ (~cobra@user/Cobra) | 02:32 | |
| - cobra (QUIT: Ping timeout: 248 seconds) (~cobra@user/Cobra) | 02:32 | |
| - mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org) | 03:08 | |
| - paperManu (QUIT: Ping timeout: 252 seconds) (~paperManu@107.159.243.8) | 03:11 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 04:35 | |
| - glu (QUIT: Read error: Connection reset by peer) (~glu@user/glu) | 05:44 | |
| + glu (~glu@user/glu) | 05:44 | |
| + chomwitt (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 07:37 | |
| - mtm (QUIT: Read error: Connection reset by peer) (~textual@47.202.75.129) | 08:18 | |
| + mtm (~textual@47.202.75.129) | 08:22 | |
| BoostisBetter | minute: what does the T in the upper left hand corner of the OLED LPC display mean? | 09:08 |
| BoostisBetter | minute: and the follow up questiomn to that would be: what is the procedure that should be done when seeing it? Can you just ignore it? | 09:23 |
| BoostisBetter | I didn't see it mentioned in any of the manuals for the pocket or Reform | 09:26 |
| minute | BoostisBetter: T means timeout. i.e. system controller did not respond to a command | 09:47 |
| minute | BoostisBetter: it can be ignored | 09:47 |
| BoostisBetter | minute: what is the best way to get rid of it? just activate the menu? | 09:50 |
| minute | BoostisBetter: yeah | 09:51 |
| BoostisBetter | minute: vielen Dank! | 09:52 |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 10:04 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 10:04 | |
| + aloo_shu (~aloo_shu@85.51.17.85) | 10:08 | |
| - chomwitt (QUIT: Ping timeout: 252 seconds) (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 11:47 | |
| minute | josch: i'm disabling imx8mq hdmi until it is investigated and fixed, and will merge 6.12+pocket multi panel driver | 11:53 |
| minute | josch: i'm doing that by copying the normal imx8mq dts over the imx8mq hdmi dts in reform-debian-packages so that they're identical | 11:53 |
| minute | josch: i have also deleted my revert commit of your hdmi driver bump so we can work from the latest version, later | 11:54 |
| josch | minute: yes, makes sense :) | 11:55 |
| - iank (QUIT: Ping timeout: 265 seconds) (~iank@fsf/staff/iank) | 12:05 | |
| + iank (~iank@fsf/staff/iank) | 12:12 | |
| + paperManu (~paperManu@107.159.243.8) | 12:38 | |
| minute | pipeline passed, did a manual rollout and will test upgrade on a device with display v2 now (and on my other systems) | 12:44 |
| BoostisBetter | minute: is there any advantage to the v2 display, such that if you had a v1 display, you would want the v2? Shouldn't be any right? This is just a supply chain change right? | 12:45 |
| minute | BoostisBetter: i think you already asked me this question in the past. | 12:45 |
| BoostisBetter | minute; Most likely. I got ADD issues, so my bad. | 12:46 |
| BoostisBetter | minute: do you think a touchscreen is something that could possibly be a future upgrade? | 12:46 |
| BoostisBetter | Or is there not enough room for the aditional display layer that would be needed? | 12:47 |
| minute | BoostisBetter: no worries. so, we moved to this display due to supply chain issues. i don't think it has other benefits. except that these are supposed to be newly made, and a lot of the display v1 was refurbished stock | 12:47 |
| minute | idk about touchscreen. should be possible | 12:48 |
| BoostisBetter | minute: the touch display would be next level improvement for the Pocket. | 12:48 |
| BoostisBetter | but no stress, I think you have more than enough on your plate right now | 12:48 |
| BoostisBetter | The Reform Next is looking amazing! | 12:49 |
| minute | thanks, i'm working on the campaign video this week | 12:51 |
| + mjw (~mjw@gnu.wildebeest.org) | 13:01 | |
| + gustav28 (~gustav@c-78-82-53-236.bbcust.telenor.se) | 13:02 | |
| - mtm (QUIT: Ping timeout: 252 seconds) (~textual@47.202.75.129) | 13:03 | |
| + mtm (~textual@47.202.75.129) | 13:06 | |
| BoostisBetter | very awesome. I am definantely planning on picking up the Next. | 13:08 |
| minute | nice! | 13:16 |
| minute | ah, getting bitten on old production system with " trying to overwrite '/usr/share/doc/reform-handbook/html/_static/logo.svg', which is also in package reform-handbook 2.0" | 13:23 |
| minute | probably need to uninstall reform-handbook before upgrading? | 13:23 |
| josch | minute: you might need to upgrade reform-handbook to the latest version which does not ship this file anymore but references it from the reform-branding package | 13:25 |
| josch | admittedly, this error is because i forgot to set the correctly versioned conflicts/breaks/replaces in reform-branding and reform-handbook | 13:26 |
| josch | i was somehow hoping that both packages would not spend as much time in Debian NEW so that i can fix these things with the next upload | 13:27 |
| minute | uff during this install, update-initramfs is run several times | 13:27 |
| minute | it would be probably faster to re-image the complete system image | 13:27 |
| josch | but we are now waiting for nearly 2 months... | 13:27 |
| minute | uff | 13:28 |
| josch | have been waiting for ezurio-qca-firmware since July :D | 13:29 |
| minute | meeh | 13:29 |
| josch | so long that it is now the third entry in this list: https://ftp-master.debian.org/new.html | 13:29 |
| minute | btw, looks like we'll be having another nice out of tree wifi driver for next ;/ | 13:29 |
| sevan | away | 13:29 |
| sevan | derp | 13:29 |
| minute | because the mainline driver for that chip also doesn't work, basically same as qcacld2 | 13:29 |
| josch | oh no... | 13:29 |
| minute | the state of wifi mainline drivers is really concerning | 13:30 |
| minute | but we'll see. so far i tested the USB version only, there's also sdio/uart (which i dread much more though) | 13:30 |
| minute | usb is nicely plug and play with no dts nonsense | 13:31 |
| sevan | minute: where's the part which runs the initramfs initiation thing twice, it adds a delay with ZFS as it had to do the DKMS dance twice. | 13:31 |
| minute | uff | 13:31 |
| minute | we'll re-image the devies freshly, this will also bring in the latest wofi fix etc | 13:38 |
| josch | sevan: these debian bugs are relevant: #1063162 and #1079509 | 13:42 |
| josch | sevan: there is a MR for initramfs-tools adding the solution of the second bug: https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/137 | 13:43 |
| minute | nice | 13:43 |
| josch | the maintainers see the problem that if installation is interrupted, you now have an unbootable system because only a stub was created | 13:43 |
| minute | cool that this is being improved | 13:44 |
| + glu_ (~glu@user/glu) | 13:45 | |
| - glu (QUIT: Ping timeout: 252 seconds) (~glu@user/glu) | 13:45 | |
| * glu_ -> glu | 13:45 | |
| sevan | josch: thanks for the link, I'll have a read through. Just as an initial thought, there is an irony that regardless of what they're trying to address there you do end up getting clobbered regardless. When there's a breaking change introduced on the kernel side & the module build fails during DKMS & if you didn't realise it (happened to me several time), you reboot & wonder where your zpool has gone :) | 13:56 |
| sevan | that's a breaking change introduced upstream in the kernel that is (nothing to do with Debian / their kernel team) | 13:58 |
| josch | right, that's super annoying | 13:58 |
| minute | i'm wondering if, during production imaging, if i could recycle an initramfs from a first successful run instead of mounting the image and running update-initramfs -u | 14:20 |
| josch | minute: i asked something similar in the MR | 14:21 |
| josch | i was wondering whether maybe the scripting could process an environment variable saying: please be unsafe, i know what i'm doing | 14:21 |
| minute | that could save almost 5 hours of install time i think, for 300 boards | 14:22 |
| minute | (update-initramfs takes around 50 seconds) | 14:22 |
| josch | you do not install them by just dd-ing the image onto the board? | 14:22 |
| minute | josch: no because we don't have an emmc image | 14:22 |
| josch | right, you have to adjust /boot | 14:23 |
| minute | i need to change the partition labels and then chroot, change the fstab und run update-initramfs -u | 14:23 |
| minute | exactly | 14:23 |
| minute | but instead of the last step i could cp the initramfs i think | 14:23 |
| minute | that should be much quicker | 14:23 |
| josch | maybe a new option could be added to mkimage.sh which produces images with a /boot that will have an fstab entry making it load from eMMC instead of sd-card? | 14:23 |
| minute | josch: yeah, that would be useful also | 14:24 |
| minute | also for rk3588 install later | 14:24 |
| minute | where we don't ship an sd card anymore | 14:24 |
| josch | okay, i can see if i can cook something up tonight | 14:24 |
| minute | awesome! | 14:25 |
| minute | rk3588s are ready for pickup at dhl :3 | 14:25 |
| josch | \o/ | 14:25 |
| + reform23305 (~pip@178.238.173.7) | 14:32 | |
| reform23305 | q | 14:34 |
| - reform23305 (QUIT: Client Quit) (~pip@178.238.173.7) | 14:34 | |
| - mjw (QUIT: Ping timeout: 245 seconds) (~mjw@gnu.wildebeest.org) | 14:34 | |
| + mjw (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 14:35 | |
| josch | for what it's worth, i pinged some people and got the dpkg maintainer to reply to the initramfs-tools merge request... | 14:35 |
| josch | maybe this moves things forward a bit | 14:35 |
| minute | weird, why does lolcat package install to /usr/games... | 14:39 |
| - MyNetAz (QUIT: Remote host closed the connection) (~MyNetAz@user/MyNetAz) | 14:56 | |
| josch | its maintainer put it into section "games" which is probably why | 14:56 |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:56 | |
| minute | ugh, on the test production install, reform-setup was not able to launch greetd and ends in a shell | 15:00 |
| minute | maybe i could put a "systemctl restart greetd" at the end of the initial setup script as a workaround | 15:01 |
| minute | default foot font size is a bit big :D | 15:03 |
| minute | but happy that wayfire works fine | 15:03 |
| minute | pocket-reform-handbook also | 15:04 |
| minute | other than this greetd glitch, the image is in good shape | 15:05 |
| ch | i think the fontsize in foot was always big? | 15:05 |
| ch | at least it was always too big for me :D | 15:05 |
| + MyNetAz (~MyNetAz@user/MyNetAz) | 15:07 | |
| + chomwitt (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 15:10 | |
| + bkeys1 (~Thunderbi@254.sub-97-150-246.myvzw.com) | 15:19 | |
| - bkeys (QUIT: Ping timeout: 244 seconds) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 15:20 | |
| * bkeys1 -> bkeys | 15:20 | |
| minute | ch: yeah. just something i could address soon :D | 15:32 |
| - chomwitt (QUIT: Ping timeout: 260 seconds) (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 15:40 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 15:41 | |
| + Twodisbetter (2cc0e4ea1c@irc.cheogram.com) | 16:03 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 16:10 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 16:44 | |
| sevan | so, ZFS users, is it safe to upgrade to the 6.12 kernel? | 16:47 |
| minute | sevan: would it be possible for you to test that on a SD card with the new image? | 16:49 |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 16:54 | |
| + bkeys1 (~Thunderbi@254.sub-97-150-246.myvzw.com) | 16:59 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 16:59 | |
| * bkeys1 -> bkeys | 16:59 | |
| sevan | minute: hmm, good point. I could :) | 17:04 |
| + chomwitt (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 17:17 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:18 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:18 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:34 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:34 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:49 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:50 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:05 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:05 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 18:07 | |
| * mjw -> Guest1555 | 18:07 | |
| - Guest1555 (QUIT: Killed (molybdenum.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 18:07 | |
| * mark_ -> mjw | 18:07 | |
| + Guest1555 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 18:07 | |
| - bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:14 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:21 | |
| - brennen (QUIT: Quit: WeeChat 2.8) (~brennen@user/brennen) | 18:23 | |
| + brennen (~brennen@user/brennen) | 18:24 | |
| - jjbliss (QUIT: Ping timeout: 276 seconds) (jjbliss@infinity.garden) | 18:34 | |
| josch | minute: currently, the system image knows that it has to boot from sd-card because it creates filesystem with labels reformsdboot and reformsdroot and adds LABEL= entries into /etc/fstab. This means you *could* flash the sd-card image to emmc and it would work out-of-the-box except that it would fail to work as intended as soon as you add another rescue sd-card because then you have the same label for | 18:37 |
| josch | different partitions, correct? | 18:37 |
| josch | minute: because then, all that mkimage.sh has to do differently is to create system images with reformmmcboot and reformmmcroot (or whatever other labels), right? | 18:38 |
| + leonardo- (~leonardo@li1800-6.members.linode.com) | 18:47 | |
| + sterni_ (~quassel@user/sterni) | 18:47 | |
| + n_to_ (~n_to@2a03:4000:6:3662:24b1:57ff:fec6:76c1) | 18:48 | |
| + edenist_ (edenist@rdns.robotprofessor.net) | 18:52 | |
| + patsavoura (~linx@149.210.4.16) | 18:52 | |
| - Ar|stote|is (QUIT: *.net *.split) (~linx@149.210.4.16) | 18:53 | |
| - n_to (QUIT: *.net *.split) (~n_to@2a03:4000:6:3662:24b1:57ff:fec6:76c1) | 18:53 | |
| - sterni (QUIT: *.net *.split) (~quassel@user/sterni) | 18:54 | |
| - leonardo (QUIT: *.net *.split) (~leonardo@li1800-6.members.linode.com) | 18:54 | |
| - edenist (QUIT: *.net *.split) (~edenist@rdns.robotprofessor.net) | 18:54 | |
| * edenist_ -> edenist | 18:54 | |
| * edenist -> edenist_ | 18:54 | |
| + TwoDIsBooster (~committed@user/TwoDIsBooster) | 19:09 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:18 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:18 | |
| ch | i was wondering if linux can still know where it got booted from. but i guess that requires uboot to pass in some arg :( | 19:18 |
| sevan | ch: is there nothing in sysfs? | 19:19 |
| josch | ch: you can perfectly hide where it booted from without a problem, no? | 19:21 |
| josch | it's easy to let the /boot partition that u-boot reads the image and initramfs from be a different one that linux mounts later | 19:21 |
| - glu (QUIT: Read error: Connection reset by peer) (~glu@user/glu) | 19:24 | |
| + glu (~glu@user/glu) | 19:24 | |
| - TwoDIsBooster (QUIT: Ping timeout: 252 seconds) (~committed@user/TwoDIsBooster) | 19:29 | |
| ch | josch: yeah it would need sth like passing $boot(dev?) from uboot. but meh | 19:37 |
| sevan | "100%Original 3.2V 3000mAh 18650 Lithium Iron Phosphate Rechargeable Battery 1C-3C 21700 LiFePO4 Battery for Flashlight Mini Fan" hmm | 19:44 |
| sevan | I suspect those are 3.7V | 19:45 |
| sevan | based an all the other 3000mAh batteries being 3.7V :) | 19:46 |
| - MyNetAz (QUIT: Read error: Connection reset by peer) (~MyNetAz@user/MyNetAz) | 19:47 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:48 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:49 | |
| + MyNetAz (~MyNetAz@user/MyNetAz) | 19:58 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:04 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:04 | |
| sevan | alright, batteries ordered | 20:08 |
| sevan | went for 8 of these https://www.batteriesplus.co.uk/acatalog/3.2V-18650-Li-Ion---LiFePO4---Lithium-Phosphate---1800mAh-rechargeable-batteries-for-Solar-Garden-Lights-2255.html | 20:08 |
| josch | o0 | 20:08 |
| sevan | Now to see which shows up first the cable or the batteries. :) | 20:08 |
| josch | which solar garden lights use 18650 lifepo4? | 20:08 |
| sevan | josch: the ones in the advert! (fooling around, I have no idea) | 20:09 |
| josch | i wish there were some | 20:09 |
| josch | i'm looking for options for a second life of my old 18650ies :) | 20:10 |
| sevan | how come you replaced your old batteries? | 20:11 |
| josch | jeff geerling measured only 2.5 hours of runtime for his a311d reform | 20:12 |
| josch | to debunk this, i had to get some fresh cells and redo the same test setup | 20:12 |
| josch | https://floss.social/@josch/112098284536607191 | 20:13 |
| sevan | oh, I saw your issue report on the reform repo last night. | 20:14 |
| sevan | Interesting stuff, I've never played around with power management before. | 20:14 |
| sevan | got me curious what is possible in an amateur setting without fancy expensive measurement tools. | 20:15 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:20 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:20 | |
| sevan | btw, how come the LPC baud rate is so crazy high on the RK3588 :D | 20:21 |
| sevan | just amused as there's only one or 2 characters sent to it over the wire. | 20:22 |
| sevan | josch: this https://source.mnt.re/reform/reform/-/issues/18 | 20:23 |
| - bkeys (QUIT: Ping timeout: 265 seconds) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:29 | |
| - n_to_ (QUIT: Quit: quitidiquit) (~n_to@2a03:4000:6:3662:24b1:57ff:fec6:76c1) | 20:33 | |
| + n_to (~n_to@2a03:4000:6:3662:24b1:57ff:fec6:76c1) | 20:33 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:35 | |
| minute | sevan: that's not the lpc baud rate. | 20:38 |
| minute | sevan: what is high is the SoC's baud rate for serial console | 20:38 |
| sevan | minute: aaaahhhh | 20:38 |
| sevan | minute: thanks again. :) | 20:39 |
| - bkeys (QUIT: Ping timeout: 265 seconds) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:51 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:51 | |
| - bkeys (QUIT: Client Quit) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:54 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:54 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 21:10 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 21:10 | |
| - mtm (QUIT: Remote host closed the connection) (~textual@47.202.75.129) | 21:16 | |
| + mtm (~textual@47.202.75.129) | 21:17 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 21:25 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 21:25 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 21:45 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 21:45 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 22:01 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 22:01 | |
| josch | minute: can you confirm my theory regarding the system image? | 22:05 |
| josch | minute: it will still be a few days until i'm in the position where i can flash a SoM myself to test this without destorying my setup :D | 22:05 |
| minute | josch: sorry, which theory? | 22:09 |
| minute | ah, checking | 22:09 |
| minute | josch: yes, labels + fstab | 22:09 |
| josch | minute: there is one wrinkle which is auto-resizing. The image includes a first-boot script which currently only auto-resizes the partition on sd-card. Would you expect the changed image to auto-resize the partition on emmc? | 22:11 |
| minute | josch: oh right... currently we resize the emmc partition in the pocket-factory script after imaging | 22:12 |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-53-236.bbcust.telenor.se) | 22:15 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 22:27 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 22:27 | |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 22:35 | |
| josch | minute: disk image for you to flash directly to emmc and see what happens: https://source.mnt.re/reform/reform-system-image/-/jobs/7108/artifacts/browse | 22:36 |
| josch | this one uses different disk labels reformemmcboot and reformemmcroot | 22:37 |
| josch | if that worked i will turn it from a POC to something that can get merged | 22:37 |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 22:38 | |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 22:42 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 22:58 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 22:58 | |
| + colinsane (~colinunin@97-113-71-244.tukw.qwest.net) | 23:00 | |
| + jacobk (~quassel@2603:8080:b200:7b02:77cb:6304:f9db:dda1) | 23:01 | |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@2603:8080:b200:7b02:77cb:6304:f9db:dda1) | 23:10 | |
| - chomwitt (QUIT: Quit: WeeChat 3.8) (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 23:12 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 23:13 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 23:14 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 23:29 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 23:30 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 23:42 | |
| - mjw (QUIT: Ping timeout: 276 seconds) (~mjw@gnu.wildebeest.org) | 23:45 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 23:45 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 23:46 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 23:58 | |
| + bkeys1 (~Thunderbi@254.sub-97-150-246.myvzw.com) | 23:58 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!