2025-02-05.log

+ aloo_shu_ (~aloo_shu@85.51.18.12)00:00
- bkeys (QUIT: Ping timeout: 260 seconds) (~Thunderbi@h167.248.96.50.static.ip.windstream.net)00:00
- aloo_shu (QUIT: Ping timeout: 260 seconds) (~aloo_shu@90.166.193.108)00:02
* aloo_shu_ -> aloo_shu00:02
+ bkeys (~Thunderbi@h167.248.96.50.static.ip.windstream.net)00:03
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@h167.248.96.50.static.ip.windstream.net)00:17
+ bkeys (~Thunderbi@h167.248.96.50.static.ip.windstream.net)00:26
+ robin_ (~robin@user/terpri)00:46
- robin__ (QUIT: Ping timeout: 248 seconds) (~robin@user/terpri)00:49
joschfrickler: the most glaring problem should be fixed now. Please flash the correct system image from here on an sd-card to start over: https://source.mnt.re/reform/reform-system-image/-/jobs/7640/artifacts/browse00:49
- mtm (QUIT: Ping timeout: 248 seconds) (~textual@47.202.75.129)01:04
+ mtm (~textual@47.202.75.129)01:05
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@h167.248.96.50.static.ip.windstream.net)01:11
+ bkeys (~Thunderbi@h167.248.96.50.static.ip.windstream.net)01:24
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)01:34
- Bertl (QUIT: Ping timeout: 252 seconds) (herbert@IRC.13thfloor.at)01:34
+ Bertl (herbert@IRC.13thfloor.at)01:36
- Bertl (QUIT: Ping timeout: 252 seconds) (herbert@IRC.13thfloor.at)01:42
+ Bertl (herbert@IRC.13thfloor.at)01:42
- Bertl (QUIT: Ping timeout: 252 seconds) (herbert@IRC.13thfloor.at)01:48
+ Bertl (herbert@IRC.13thfloor.at)01:48
- mjw (QUIT: Ping timeout: 260 seconds) (~mjw@gnu.wildebeest.org)02:03
+ mjw (~mjw@gnu.wildebeest.org)02:12
+ _justin_kelly718 (~justinkel@user/justin-kelly/x-6011154)03:08
- _justin_kelly71 (QUIT: Ping timeout: 260 seconds) (~justinkel@user/justin-kelly/x-6011154)03:11
* _justin_kelly718 -> _justin_kelly7103:11
- MyNetAz (QUIT: Remote host closed the connection) (~MyNetAz@user/MyNetAz)03:37
+ MyNetAz (~MyNetAz@user/MyNetAz)03:48
- Bertl (QUIT: Ping timeout: 252 seconds) (herbert@IRC.13thfloor.at)03:54
- L29Ah (QUIT: Read error: Connection timed out) (~L29Ah@wikipedia/L29Ah)03:57
+ Bertl (herbert@IRC.13thfloor.at)04:01
- Bertl (QUIT: Ping timeout: 252 seconds) (herbert@IRC.13thfloor.at)04:07
+ Bertl (herbert@IRC.13thfloor.at)04:15
+ aloo_shu_ (~aloo_shu@90.166.99.110)04:17
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.18.12)04:20
* aloo_shu_ -> aloo_shu04:20
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@h167.248.96.50.static.ip.windstream.net)04:35
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)05:06
fricklerjosch: thx, will try that. do you have a procedure to update the emmc installation, too? can I simply overwrite that with the new system image, too?05:44
joschfrickler: yes, there is a script doing that called reform-flash-rescue which downloads the latest system image from the internet and puts it onto your emmc05:47
+ kfx (~kfx@wopr.sciops.net)06:08
kfxanyone got an imx8mq u-boot build that supports bootmenu?06:08
- Bertl (QUIT: Ping timeout: 252 seconds) (herbert@IRC.13thfloor.at)06:24
- mjw (QUIT: Ping timeout: 265 seconds) (~mjw@gnu.wildebeest.org)06:24
+ Bertl (herbert@IRC.13thfloor.at)06:59
+ aloo_shu_ (~aloo_shu@90.166.193.52)07:05
- Bertl (QUIT: Ping timeout: 252 seconds) (herbert@IRC.13thfloor.at)07:05
+ Bertl (herbert@IRC.13thfloor.at)07:07
- aloo_shu (QUIT: Ping timeout: 248 seconds) (~aloo_shu@90.166.99.110)07:07
* aloo_shu_ -> aloo_shu07:07
- Bertl (QUIT: Ping timeout: 252 seconds) (herbert@IRC.13thfloor.at)07:14
+ Bertl (herbert@IRC.13thfloor.at)07:14
fricklerjosch: ok, so ... I booted from sdcard with your new image, overwrote the emmc boot and system image (three times "y" as answer to reform-flash-rescue iirc, despite the offputting warnings). now retrying my actions from yesterday07:36
joschfrickler: well for you the warnings mean nothing because you have no important data on that system07:39
joschfrickler: but imagine you have been using the device for 2+ years: the reform-flash-rescue script will *still* be there and if you answer "y" three times it will allow you to delete everything07:40
fricklerjosch: well the warnings are more about bricking the system than loosing data, but yes, I do understand that those should be there07:40
fricklerbtw. the reason I did the apt stuff in the first place was that there is no openssh-server on the image, would it be an option to include it? you could still disable running the service by default. also should I rather open gitlab issues for questions like this?07:41
joschfrickler: i appreciate all your feedback. For simple things i think chat is okay. As things become more complex in the sense that i cannot fix them today, it starts making sense to use gitlab issues or email. But in general: please use the way to report issues that is most comfortable for you. I rather receive your problems in a less optimal way than not at all. :)07:43
joschabout openssh-server: this has been a topic in the past07:43
joschproblems is of course that it would have a service running by default but as you say, that could be disabled07:43
joschanother problem is, how to generate the key because it would be counterproductive to create the system image where everybody shares the same private key :)07:44
fricklerjosch: ah, good point about the system keys. I can look into that. I think I'm going to build my own custom image anyway with some tunings like skipping the initial installer07:48
joschcool!07:49
joschkfx: yes, the latest default imx8mq u-boot does support distro boot and thus u-boot-menu07:50
fricklernew warning during running reform-migrate btw.: WARNING: Unknown X keysym "dead_greek" (repeated 4 times)07:50
joschthat's normal07:51
joschi get this several thousand times07:51
joschit's an issue of keyboard configuration when creating an initramfs07:51
joschit bakes your chosen default system keyboard layout into the initramfs so that you have it available, for example when you want to open a luks device07:51
fricklerwell it wasn't in my log yesterday, so I thought I mention it. likely this means that it didn't get to create the new initramfs then07:52
joschfrickler: yes, that was the problem with more than one kernel having been present07:52
joschwhich is a different problem from the one i fixed now07:52
joschi'm in the process of fixing that one too but not done yet07:52
fricklerso I'm likely not getting that issue right now since the image has been rebuilt, so running with the latest kernel right from the start07:53
joschyes07:53
fricklerbut if it's not fixed yet, no use testing it anyway ;)07:53
fricklerhmm, now the system booted fine from ssd, but the display stayed black. I've seen that multiple times now during some of the reboots I did. typing in the passphrase blindly worked however and I can access via ssh. is this also a known issue or how can I debug it?07:57
joschthis is something i cannot answer because i do not have a pocket reform, so i don't remember issues with it that well07:58
joschfeel free to repeat the question later in case nobody answers or search the forum07:58
kfxjosch: this is great news, thank you -- when you say default do you mean upstream or the mnt gitlab?07:59
frickleralso I'd like to fix the kernel settings for the font size, the initial size is fine, then it switches to unreadable. iiuc that should also make the greeter more useable. any pointers how to do that?08:00
frickleroh, theres "fbcon=font:TER16x32" in cmdline08:00
fricklernow just to find out where that is defined08:01
joschkfx: mnt gitlab. You can use reform-flash-uboot to update your u-boot08:07
joschfrickler: that setting is part of latest u-boot for the imx8mplus pocket reform -- you might still be on an older u-boot version?08:08
kfxoh I see, this supports the debian u-boot-menu thing where it uses extlinux configuration?  as opposed to the bootmenu directives in the boot script?08:10
fricklerjosch: I didn't touch u-boot so far afaict. how can I check that?08:10
joschfrickler: you can run sudo reform-check08:12
joschkfx: correct, it supports extlinux.conf08:12
joschkfx: the default is still boot.scr (dispite all u-boot that are downloadable supporting extlinux.conf) because there are very old imx8mq systems with an u-boot version that does not support it. If we'd no longer ship boot.scr, that would make these systems unbootable with newer system images.08:13
kfxI understand08:14
kfxbut bootmenu directives in the boot.scr are not working08:14
kfxI'll try to rework what I'm doing to use the extlinux.conf approach08:14
joschah i never tried getting a boot menu via boot.scr08:14
kfxbootmenu is disabled in the build config, however it still doesn't work if you enable it and rebuild.  I've been advised that I would need a newer u-boot to get that working08:15
joschah i see08:16
joschright, imx8mq u-boot is still the ancient vendor fork...08:16
kfxmodern u-boot has diverged far enough that porting cinap's patches is beyond my capability08:17
kfxso I'll try to get extlinux.conf working08:18
fricklerjosch: https://paste.opendev.org/show/bMpQEV1Gt58v2pURBoBJ/ but where is that font override getting defined?08:31
- jacobk (QUIT: Quit: No Ping reply in 180 seconds.) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)08:59
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)09:01
+ reform26269 (~goutham@p200300e9ff3dceaf7b80146ddfdf7a8c.dip0.t-ipconnect.de)09:13
- reform26269 (QUIT: Client Quit) (~goutham@p200300e9ff3dceaf7b80146ddfdf7a8c.dip0.t-ipconnect.de)09:13
joschfrickler: ooooh you are on rk3588 pocket reform!09:18
joschsorry, in that case disregard what i said09:19
joschfrickler: could you please paste me your output of cat /proc/cmdline09:19
fricklerjosch: ro no_console_suspend cryptomgr.notests loglevel=3  clk_ignore_unused cma=256M swiotlb=65535 fbcon=rotate:3 fbcon=font:TER16x32  console=tty109:36
joschperfect, that was indeed missing fbcon=font:TER16x3209:38
joschi'll fix that in the next reform-tools release, thank you!09:39
josch(i don't have a rk3588, so i cannot test this myself :D)09:40
+ robin__ (~robin@user/terpri)09:48
- robin_ (QUIT: Ping timeout: 252 seconds) (~robin@user/terpri)09:50
- MyNetAz (QUIT: Remote host closed the connection) (~MyNetAz@user/MyNetAz)09:51
hramrachit does have the kernel commandline setting but changing the console setup or whatever settings seems ineffective09:57
hramrachjosch: on some distributions sshd is installed as disabled and without keys, and the keys are generated when the service is first started. perhaps changing the settings in the image would work but seeing the struggle to get the font settings right it might not be such a great idea09:58
hramrachbut at least seleting the keys should get them regenerated on next sshd start even on Debian, iirc09:59
- jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)10:04
+ jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net)10:05
+ MyNetAz (~MyNetAz@user/MyNetAz)10:06
- Ar|stote|is (QUIT: Ping timeout: 260 seconds) (~linx@149.210.13.214)10:29
+ Ar|stote|is (~linx@149.210.12.110)10:33
+ BoostisBetter (4a410829d7@irc.cheogram.com)10:36
joschhramrach: thank you, that's good to know! I have the openssh-server issue on my todo list :)11:05
chidk about sshd making new keys, we ship a dropin to make it happen https://github.com/grml/grml-live/blob/master/config/files/etc/systemd/system/ssh.service.d/keygen.conf/GRMLBASE11:09
joschch: but this will run on *every* boot, no?11:13
joschsystemd has some facility to detect a "first boot"11:13
chjosch: possible, we're a livecd :D11:13
- MyNetAz (QUIT: Remote host closed the connection) (~MyNetAz@user/MyNetAz)11:13
chjosch: i think a conditionpathexists on the key files might be useful too11:13
joschah indeed, that's even better than "first boot"11:14
chand/or maybe the file should delete itself afterwards, idk11:14
+ MyNetAz (~MyNetAz@user/MyNetAz)11:28
+ L29Ah (~L29Ah@wikipedia/L29Ah)11:36
+ aloo_shu_ (~aloo_shu@90.166.99.97)12:08
- aloo_shu (QUIT: Ping timeout: 246 seconds) (~aloo_shu@90.166.193.52)12:10
* aloo_shu_ -> aloo_shu12:10
+ andreas-e (~Andreas@2001:861:c4:f2f0::c64)12:43
- Bertl (QUIT: Ping timeout: 252 seconds) (herbert@IRC.13thfloor.at)12:57
+ Bertl (herbert@IRC.13thfloor.at)12:57
+ mjw (~mjw@gnu.wildebeest.org)12:59
+ gustav28 (~gustav@c-92-32-81-6.bbcust.telenor.se)13:02
- mtm (QUIT: Ping timeout: 265 seconds) (~textual@47.202.75.129)13:03
+ mtm (~textual@47.202.75.129)13:06
- MyNetAz (QUIT: Ping timeout: 252 seconds) (~MyNetAz@user/MyNetAz)13:21
+ aloo_shu_ (~aloo_shu@90.166.98.248)13:40
- aloo_shu (QUIT: Ping timeout: 248 seconds) (~aloo_shu@90.166.99.97)13:43
* aloo_shu_ -> aloo_shu13:43
+ Gooberpatrol_66 (~Gooberpat@user/gooberpatrol66)14:07
- Gooberpatrol66 (QUIT: Ping timeout: 248 seconds) (~Gooberpat@user/gooberpatrol66)14:08
- cobra (QUIT: Quit: ZNC 1.8.2 - https://znc.in) (~cobra@user/Cobra)14:21
+ MyNetAz (~MyNetAz@user/MyNetAz)14:21
+ cobra (~cobra@user/Cobra)14:27
+ aloo_shu_ (~aloo_shu@85.51.17.8)14:28
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@90.166.98.248)14:31
* aloo_shu_ -> aloo_shu14:31
- amospalla (QUIT: Quit: WeeChat 4.5.1) (~jordi@user/amospalla)14:40
+ amospalla (~jordi@user/amospalla)14:40
+ anzu (~anzu@melkki.cs.helsinki.fi)14:57
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)15:02
- qbit (QUIT: Remote host closed the connection) (~qbit@user/qbit)15:38
+ qbit (~qbit@user/qbit)16:06
irimi1frickler: i just checked, and i get one Wireless Adapter: MediaTek Inc. MT7612U16:33
irimi1i’m on my way to comparing with the MNTRE shop whether that’s the one i bought, but i’m getting a 504 instead :/16:33
irimi1is that the one it should be detecting?16:34
irimi1ah, i can answer that myself (thanks, WBM). yes, that’s the one it should be detecting16:38
irimi1what’s the next things i should check for troubleshooting?16:38
minuteirimi1: sorry, what's the issue? pocket reform and asiarf wifi card not detected?16:41
irimi1i had another look into dmesg knowing what card to look for, and i found 'probe with driver mt76x2u failed with error -2', says it’s 'mt76xu2 1-1.4:1.0'16:41
irimi1bad wifi reception, if i even manage to connect to my home wifi16:42
minuteirimi1: which cpu module? imx8mp?16:42
irimi1yes16:42
minuteirimi1: ok and you installed the mediatek card now as a workaround but it doesn't work or...?16:43
minuteirimi1: did you disable the built-in wifi in network manager?16:43
irimi1well, it looks like it gets detected, but reception-wise it even feels like it got a little bit worse16:43
minuteirimi1: are you using one or two antennas on the mt card?16:44
irimi1using both, as pictured in the handbook16:44
minuteirimi1: ok. can you confirm that the built-in wifi is disabled?16:45
irimi1i have not modified any configuretion. where would i disable it in the networkmanager?16:45
irimi1*configuration16:45
minutebecause now the two wifis will probably interfere16:45
irimi1oh, that doesn’t sound good16:45
+ aloo_shu_ (~aloo_shu@85.51.16.12)16:46
fricklerthat reminds me that I should put my wifi to the test, too ;)16:48
- aloo_shu (QUIT: Ping timeout: 246 seconds) (~aloo_shu@85.51.17.8)16:48
* aloo_shu_ -> aloo_shu16:48
minuteirimi1: it might be the easiest to block loading the driver for the internal card (qcacld2) by adding a line "blacklist qcacld2" to /etc/modprobe.d/reform-qcacld2.conf16:49
minute(and then reboot)16:49
irimi1sweet, i’m gonna try that. thank you so much <316:50
fricklerjosch: two questions regarding mkimage.sh: a) would you accept a patch to allow it to use a dedicated build directory? I don't like cluttering up the git root. b) with the --quick option, is there some preconfigured login or is that just to test the boot process?16:50
minuteirimi1: also you can try disconnecting one of the two antennas. i found that it works better with a single antenna sometimes16:50
irimi1minute: a fallback-option seems to be to put an 'unmanaged-devices' entry into the NetworkManager.conf if i see that right16:50
irimi1oh that’s interesting, too16:51
irimi1does it matter which one?16:51
minuteirimi1: not sure by heart... you can experiment16:51
irimi1i will :)16:51
joschfrickler: a) yes16:54
joschfrickler: b) the preconfigured login is root without a password16:54
irimi1minute: hm, i’m still having trouble with the reception and getting disconnected, but if NetworkManager can find my wifi for a minute it’s connecting immediately17:00
irimi1so looks like those drivers/devices competing was indeed an issue17:00
irimi1i’m gonna try disconnecting one antenna now :)17:00
- bkeys (QUIT: Ping timeout: 245 seconds) (~Thunderbi@38-146-94-247.echocast.zone)17:11
fricklerjosch: oh, I'd never guessed the latter, but on second thought that's likely a good default in that scenario17:13
fricklerthx17:13
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)17:15
irimi1hm.. should there be a wpa_supplicant running, minute?17:16
hramrachyes, NM should start it17:17
irimi1hm okay. because that’s giving me errors17:17
minuteirimi1: what did you try to do?17:17
irimi1nl80211: kernel reports: Unsupported attribute17:18
irimi1eeh, connecting to my wifi? ^^17:18
minutei think that doesn't matter...17:18
irimi1hm..ok17:18
hramrachit might be trying multiple ways to talk to the kernel, there are so many diffeernt revisions of the WiFi API it's not funny anymore17:19
minutejosch: pico-sdk-source not installable atm because libstdc++-arm-none-eabi-dev dependency issue...17:20
joschminute: is the mnt tooling not using a git submodule of pico-sdk instead of relying on the debian package?17:21
minutejosch: no longer17:21
minuteor maybe it depends17:21
+ mark_ (~mjw@gnu.wildebeest.org)17:21
minutei'm just setting up a pocket reform here for in-office use 17:21
minute(mainly for flashing/testing pocket reform fw stuff)17:22
minutejosch: for example pocket-reform-keyboard-fw uses /usr/src/pico-sdk17:22
joschminute: the problem is known. I'll put it at the top of my todo list to fix this.17:22
joschthe problem comes down to gcc-riscv64-unknown-elf17:23
minuteoh wow17:23
minutejosch: thanks!!17:23
minute(pocket sysctl fw also wants to use /usr/src/pico-sdk nowadays)17:23
joschokay, i see17:23
irimi1hm, i’m gonna try figure that out another time. gotta run now. either way, thanks for y’all’s help so far :)17:23
minuteirimi1: cya!17:23
- mjw (QUIT: Ping timeout: 248 seconds) (~mjw@gnu.wildebeest.org)17:23
joschthe problem with gcc-riscv64-unknown-elf was this one, if anybody is curious: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=108646217:24
joschthe last upload should've solved it. i'll investigate tonight what makes it still uninstallable17:25
joschthis is also why pico-sdk and packages around it got removed from testing17:25
minuteoh17:25
joschit's unstable... once Trixie is out, pico-sdk in there will not randomly stop being installable17:26
hramrachCan't say if I have that message or not, looks like the only logs are in journal17:26
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@38-146-94-247.echocast.zone)17:29
hramrachso I do, and I get ping times up to 3s for unknown reason with some external dongle17:30
chah pico-sdk needs the riscv gcc because theres now riscv stuff in the sdk?17:32
chif so, ... 'meh' (:17:32
hramrachyes, the new pico has riscv cores17:32
joschch: i see you understand why i didn't feel motivated to look into it even though it triggered the testing removal? ;)17:33
chyeah, annoying17:33
chand gcc-riscv64-unknown-elf is pseudo-orphaned?17:34
chhas an O: bug but maintainer != qa group17:34
joschyes, but keith seems to find time for it every once in a while17:34
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)17:37
hramrachI have a packet black hole somewhere. When a ping takes over 100s it can only be because the packet got too close to the event horizon, right?17:38
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)17:45
- bkeys (QUIT: Ping timeout: 276 seconds) (~Thunderbi@38-146-94-247.echocast.zone)18:00
- jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net)18:13
joschminute: the bug is actually this one: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105516018:18
joschminute: if there is no maintainer activity i think i am allowed to take care of this in 2 days18:18
ch.oO( just nmu it now )18:24
minutejosch: wow ok18:24
chInstalled Size 2,058,077.0kB blush18:26
minutemuch kB18:27
joschch: if you think doing the nmu *now* you can also do that ;)18:31
joschi think it's a bit unfair to bump severity to RC and then immediately nmu because technically, the bug has been RC for a long while, just not marked as such18:31
joschi also wonder why the maintainers do this as source-ful uploads and not a binNMU...18:32
chnah i'm in some other deep magic18:35
chbecause the -dev package is arch:all i guess?18:35
chwell, all binary packages there are arch:all18:35
chcant binNMU them18:35
joschah true, that's why18:36
- Gooberpatrol_66 (QUIT: Read error: Connection reset by peer) (~Gooberpat@user/gooberpatrol66)18:37
- nsc (QUIT: Ping timeout: 276 seconds) (~nicolas@i5C74DF26.versanet.de)18:45
- exark (QUIT: Quit: quit) (~exark@user/exark)18:51
joschi had a chat with keith. A new picolibc release is in the works, after that libstdc++ for arm and riscv will be uploaded18:52
+ exark (~exark@user/exark)18:53
+ jacobk (~quassel@utdpat241106.utdallas.edu)19:57
joschminute: estimated timeline is "less than a week, probably only a few days"20:27
- andreas-e (QUIT: Quit: Leaving) (~Andreas@2001:861:c4:f2f0::c64)20:31
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)20:35
+ reform21282 (~ryan@bras-base-toroon0964w-grc-08-142-198-81-33.dsl.bell.ca)20:43
reform21282hello20:43
reform21282just got my reform pocket booting20:43
reform21282how do you configure the charge controller¿20:44
reform21282my battery never seems to charge above 17%20:44
reform21282anyone here?20:44
kfxyes, folks are here!20:45
kfxsometimes it takes a while for people to respond; people are here but not necessarily looking at irc at the moment, so it's best if you can stick around for a while20:46
reform21282thanks, that is very u7nderstandable20:46
- reform21282 (QUIT: Quit: reform21282) (~ryan@bras-base-toroon0964w-grc-08-142-198-81-33.dsl.bell.ca)21:02
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@38-146-94-247.echocast.zone)21:03
+ bkeys (~Thunderbi@38-146-94-247.echocast.zone)21:04
+ pocketenjoyer (~pocketenj@142.198.81.33)21:12
fricklerdo I need to contact someone after signing up on source.mnt.re or just wait a bit?21:35
- pocketenjoyer (QUIT: Ping timeout: 240 seconds) (~pocketenj@142.198.81.33)21:56
- jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@utdpat241106.utdallas.edu)22:02
+ spew_ (~spew@135.233.119.40)22:14
- gustav28 (QUIT: Quit: Quit) (~gustav@c-92-32-81-6.bbcust.telenor.se)22:15
+ natalie- (~natalie@user/natalie)22:15
+ anuejn_ (~quassel@46.101.193.235)22:16
+ BAndiT1983_ (~quassel@46.101.193.235)22:16
- L29Ah (QUIT: Ping timeout: 252 seconds) (~L29Ah@wikipedia/L29Ah)22:18
- eery (QUIT: Ping timeout: 252 seconds) (~eery@192.150.253.237)22:18
- anzu (QUIT: Ping timeout: 252 seconds) (~anzu@melkki.cs.helsinki.fi)22:18
- MyNetAz (QUIT: Ping timeout: 252 seconds) (~MyNetAz@user/MyNetAz)22:18
- Bertl (QUIT: Ping timeout: 252 seconds) (herbert@IRC.13thfloor.at)22:18
- BAndiT1983 (QUIT: Ping timeout: 252 seconds) (~quassel@46.101.193.235)22:18
- anuejn (QUIT: Ping timeout: 252 seconds) (~quassel@46.101.193.235)22:18
- natalie (QUIT: Ping timeout: 252 seconds) (~natalie@user/natalie)22:18
- brennen (QUIT: Ping timeout: 252 seconds) (~brennen@user/brennen)22:18
- spew (QUIT: Ping timeout: 252 seconds) (~spew@135.233.119.40)22:18
* spew_ -> spew22:18
+ eery (~eery@2605:800:10:13:216:3eff:fe90:5237)22:21
+ brennen (~brennen@user/brennen)22:30
+ anzu (~anzu@melkki.cs.helsinki.fi)22:30
+ Bertl (herbert@IRC.13thfloor.at)22:31
joschfrickler: yes, minute needs to click a button to activate your accout on source.mnt.re22:31
+ pocketenjoyer (~pocketenj@bras-base-toroon0964w-grc-08-142-198-81-33.dsl.bell.ca)22:40
+ L29Ah (~L29Ah@wikipedia/L29Ah)22:43
minutefrickler: account approved23:12
+ LainExperiments (~LainExper@user/LainExperiments)23:15
pocketenjoyerHow does one control charging rates / parameters on the Pocket?23:15
minutepocketenjoyer: currently there's no software control over that, it's coded in the system controller firmware23:17
minutepocketenjoyer: https://source.mnt.re/reform/pocket-reform/-/tree/main/pocket-reform-sysctl-fw/src?ref_type=heads23:17
+ MyNetAz (~MyNetAz@user/MyNetAz)23:18
pocketenjoyerminute so if I have charging issues, am I right in thinking step 1 is updating the system controller firmware?23:22
chyes23:22
pocketenjoyerAre there instructions somewhere for that, please?23:25
kfxhttps://source.mnt.re/reform/pocket-reform/-/releases23:29
- mark_ (QUIT: Ping timeout: 260 seconds) (~mjw@gnu.wildebeest.org)23:33

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