2026-06-23.log

- bkeys (QUIT: Ping timeout: 264 seconds) (~Thunderbi@134.22.115.162)01:04
- gianmarcogg03 (QUIT: Ping timeout: 244 seconds) (~quassel@user/gianmarcogg03)01:26
- mjw (QUIT: Ping timeout: 272 seconds) (~mjw@gnu.wildebeest.org)01:26
+ gianmarcogg03 (~quassel@user/gianmarcogg03)01:31
+ oliverD (~Thunderbi@user/oliverd)01:41
- oliverD (QUIT: Ping timeout: 245 seconds) (~Thunderbi@user/oliverd)01:45
+ oliverD (~Thunderbi@user/oliverd)01:51
- oliverD (QUIT: Read error: Connection reset by peer) (~Thunderbi@user/oliverd)01:52
+ robin (~robin@user/terpri)01:52
- Svp (QUIT: Ping timeout: 248 seconds) (~svp@host-79-57-105-252.business.telecomitalia.it)02:52
+ aloo_shu_ (~aloo_shu@90.166.98.10)03:04
- aloo_shu (QUIT: Read error: Connection reset by peer) (~aloo_shu@90.166.98.10)03:04
* aloo_shu_ -> aloo_shu03:05
+ Svp (~svp@host-79-57-105-252.business.telecomitalia.it)03:11
murphnjSeems my keyboard has stopped being an intermittent problem.  I just opened it up, re-seated the cables, and it worked just long enough to get the decryption password in, but not long enough to log in.  I guess it has to be plugged into a hub with an external keyboard now.03:13
murphnjI'm up for suggestions.  Has anyone had luck resolvng this?03:13
minutemurphnj: i don't think this has been properly root caused. but we could send you the new rev keyboard under warranty.03:15
minutemurphnj: it can be the cable, or the rp2040 on the keyboard, or it's crystal for example03:15
murphnjIs there more information I can provide to help diagnose?  Also, I have a ticket in for the video output not working, but I haven't heard back in a while.03:18
minutemurphnj: uff, sorry for that. it's 3am here and i can barely keep my eyes open, can you ping me again here tomorrow between like 1pm and 8pm cest?03:19
murphnjI can try, email might be better though.  You can use mnt@murph.info and let me know when I can check.    I'll look in the morning.03:20
murphnjGet some sleep though.  Not worth endangering your health.  Seriously.03:21
murphnjI'm heading off myself, have to get up early in the morning)03:21
minuteunfortunately i won't remember this tomorrow. but we'll find your ticket in the support system03:24
- paperManu_ (QUIT: Ping timeout: 245 seconds) (~paperManu@173.206.172.163)03:43
- paperManu (QUIT: Ping timeout: 245 seconds) (~paperManu@173.206.172.163)03:43
- kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de)03:57
+ kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de)03:57
- kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de)04:05
- murphnj (QUIT: Quit: murphnj) (~murphnj@user/murphnj)04:10
+ kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de)04:10
+ jn_ (~quassel@user/jn/x-3390946)04:46
- jn (QUIT: Ping timeout: 268 seconds) (~quassel@user/jn/x-3390946)04:46
- mesaoptimizer (QUIT: Remote host closed the connection) (~user@user/PapuaHardyNet)05:09
+ reform10800 (~heiko@2a11:fb80:3c4:8801:709c:eb84:ccec:a4bb)05:29
- reform10800 (PART: !!unknown attribute: msg!!) (~heiko@2a11:fb80:3c4:8801:709c:eb84:ccec:a4bb)05:29
- schalken (QUIT: Quit: Leaving) (~schalken@117-118-178-69.gci.net)07:34
+ schalken (~schalken@117-118-178-69.gci.net)07:54
- chrcav (QUIT: Ping timeout: 249 seconds) (~chrcav@user/chrcav)08:02
+ chrcav (~chrcav@user/chrcav)08:02
- marty (QUIT: Ping timeout: 248 seconds) (~marty@static-23-234-100-60.cust.tzulo.com)09:02
+ marty (~marty@146.70.166.206)09:04
- robin (QUIT: Read error: Connection reset by peer) (~robin@user/terpri)09:07
+ robin_ (~robin@user/terpri)09:07
+ robin__ (~robin@user/terpri)09:12
- robin_ (QUIT: Ping timeout: 256 seconds) (~robin@user/terpri)09:14
- lidstah (QUIT: Ping timeout: 245 seconds) (~lidstah@gateway/tor-sasl/lidstah)09:56
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)09:57
- robin__ (QUIT: Quit: Leaving) (~robin@user/terpri)10:03
+ mesaoptimizer (~user@user/PapuaHardyNet)10:12
- mesaoptimizer (QUIT: Client Quit) (~user@user/PapuaHardyNet)10:12
+ mesaoptimizer (~user@user/PapuaHardyNet)10:13
+ mjw (~mjw@gnu.wildebeest.org)10:51
+ Guest14 (~Guest14@141.115.76.13)11:12
- Guest14 (QUIT: Client Quit) (~Guest14@141.115.76.13)11:13
- mjw (QUIT: Ping timeout: 256 seconds) (~mjw@gnu.wildebeest.org)12:11
* Guest5077 -> mjw12:19
+ paperManu (~paperManu@173.206.172.163)12:20
- paperManu (QUIT: Ping timeout: 267 seconds) (~paperManu@173.206.172.163)12:36
+ paperManu (~paperManu@204.48.0.160)12:36
- kensanata (QUIT: Quit: OK) (~alex@user/kensanata)12:47
+ kensanata (~alex@user/kensanata)12:49
- marty (QUIT: Ping timeout: 276 seconds) (~marty@146.70.166.206)12:57
+ marty (~marty@146.70.168.173)12:58
- paperManu (QUIT: Ping timeout: 252 seconds) (~paperManu@204.48.0.160)14:26
- Chwoka (QUIT: Read error: Connection reset by peer) (~Chwoka@216.73.127.21)14:32
+ paperManu (~paperManu@modemcable141.205-200-24.mc.videotron.ca)14:38
+ Chwoka (~Chwoka@216.73.127.21)14:47
- cwebber (QUIT: Ping timeout: 256 seconds) (~Christine@user/cwebber)16:23
+ cwebber (~Christine@user/cwebber)16:26
- paperManu (QUIT: Ping timeout: 272 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca)17:15
+ paperManu (~paperManu@modemcable141.205-200-24.mc.videotron.ca)17:16
+ vkoskiv (~vkoskiv@109-204-186-7.cust.valoonet.fi)17:42
- vkoskiv (QUIT: Changing host) (~vkoskiv@109-204-186-7.cust.valoonet.fi)17:43
+ vkoskiv (~vkoskiv@user/vkoskiv)17:43
+ wielaard (~mjw@2001:1c06:2486:4600:6fcb:4b0e:fedd:fb4d)17:53
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)18:10
- Gooberpatrol66 (QUIT: Quit: Konversation terminated!) (~Gooberpat@user/gooberpatrol66)18:37
- cli (QUIT: Ping timeout: 256 seconds) (~m-vsauiy@user/cli)18:40
+ cli (~m-vsauiy@user/cli)19:17
- GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon)19:19
- RandyK (QUIT: Remote host closed the connection) (~RandyK@user/randyk)19:19
+ RandyK (~RandyK@user/randyk)19:19
+ GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon)19:20
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)19:23
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)19:23
- wielaard (QUIT: Ping timeout: 245 seconds) (~mjw@2001:1c06:2486:4600:6fcb:4b0e:fedd:fb4d)19:38
+ wielaard (~mjw@gnu.wildebeest.org)19:58
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66)20:12
- mjw (QUIT: Killed (gallium.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:4600:5952:3a9:6e0e:555a)20:56
* wielaard -> mjw20:56
+ Guest452 (~mjw@2001:1c06:2486:4600:5952:3a9:6e0e:555a)20:56
minutech: as the resident mp2650 otg 5v expert, any insight on why that feature _wouldn't_ work? :D21:42
chminute: huh. you built the fw with OTG_AS_5V?21:43
minutech: yeah i wanted to officially support that on mb2.021:44
chhm. it should just work21:44
minutech: and i'm pretty sure i've seen it work once but now on 2 devices it doesn't, the charger only present like 2v (looks a bit like a probing voltage) that collapses to 0.8v when plugging something in21:44
chis there anything else on the same pin? i can check in a bit what voltage my charger presents21:46
minuteah the 2v aren't coming from the charger21:51
chok21:51
chi think it pretty much always emits 5V, but it's been a while ago21:51
minutebehind the charger protector (on chg v2, U3) it's 0.28v21:52
minutesorry i mean 0.0221:56
chcan you confirm if the otg_en bit is set?21:59
chare you on the sysctl 'main' branch firmware or a v2 branch?22:01
chrereading the datasheet, "obviously" no otg output if battery is <1V22:01
chah and NTC_GCOMP_SEL has to be 1 (default)22:02
minutech: i'm on a very umm... evolved branch22:02
minuteok let me check22:02
chdunno if you added some NTC stuff?22:03
minutenot consciously, but checking22:03
minuteoh > mps_reg_config.config0.ntc_gcomp_sel = 0;  // disable OTG pin22:03
chhm22:04
chthis is also on main22:04
chlet me think about this22:04
minutei think that's actually correct like that22:04
minuteiirc if you enable the OTG _pin_ then that's a separate pin that controls otg on/off versus doing it by register?22:05
minutechg_en has to be on perhaps?22:05
chfor otg you need both otg_en and ntc_gcomp_sel22:05
chchg_en is ignored when otg_en22:05
minuteright22:06
minute(my WIP branch is sysctl-mb20)22:07
choh wow22:08
chthis datasheet is really hard to parse22:08
chi should be wrong about ntc_gcomp_sel needing to be 122:09
chi will verify once my apt install finished22:09
chjosch: how do i get the arm-none-eabi toolchain now?22:10
minuteoh i got it to work22:14
minutentc_gcomp_sel needs to be 0 in any case22:14
minutebut i think it works only when chg_en = 122:14
minutehmm no, now it also works with chg_en = 022:14
minuteah looks like it just can't pass backwards through NX20P509022:18
minute> The NX20P5090 is an advanced 5 A unidirectional power switch22:18
minute> unidirectional22:18
minuteahaha22:18
minutewell. so it can't work with charger board v222:18
minute*chapter closed*22:19
joschch: what's the problem with gcc-arm-none-eabi?22:30
chjosch: pocket-reform.git needs to use the reform pico-sdk i guess, given it fails otherwise22:40
chminute: ugh :(22:40
chminute: so we need a charger v3? :(22:41
chjosch: forget what i said, its fixed in 421add3189016b05ad52aa9eba45f8f06a904a93 but my git history didnt see that22:42
+ DuArz (~DuArz@78.198.109.169)22:55
- paperManu (QUIT: Ping timeout: 246 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca)22:55
- DuArz (QUIT: Client Quit) (~DuArz@78.198.109.169)22:58
chi should sit down and fix the usb2 parts23:10
ch:\23:10

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