| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 00:39 | |
| minute | why does debian turn on GPU Rasterization for chromium in /etc/chromium.d/default-flags? | 00:55 |
|---|---|---|
| sevan | is it because the chromium executable is a wrapper script which pulls that in for passing on as a flag to the actual chromium binary? | 00:58 |
| minute | yes but why force this setting | 00:59 |
| minute | it seems weirdly specific | 01:00 |
| minute | why not let chromium handle its own default settings | 01:00 |
| minute | also this setting makes a mess of all SVGs on a311d | 01:00 |
| sevan | ah, sorry, I thought you meant what going from a gui based browser to the /etc | 01:00 |
| sevan | s/what/why | 01:01 |
| minute | ah no, i meant why is debian messing with a gpu setting | 01:01 |
| minute | the other settings there are all more about privacy/phoning home stuff | 01:01 |
| sevan | got it, to the package history in its repo! :) | 01:02 |
| minute | it's not explained there why it's done... there's a comment but it says "Enable GPU rasterization." :D | 01:02 |
| minute | like if the person who did this was just a fan of this setting lol | 01:02 |
| sevan | :D | 01:03 |
| josch | the commit that introduced this is also not helpful: https://salsa.debian.org/chromium-team/chromium/-/commit/05ee00d9adc0cb37c756ead81db30c60d5f056e3 | 01:05 |
| NanoCodeBug | ch: i've noticed the waybar battery meter acting strangely recently, i see on both your and mine firmware forks, which makes me think its a regression in waybar. I don't see the battery uevent showing incorrect values, or upower showing incorrect values. | 01:15 |
| josch | NanoCodeBug: waybar changed behaviour, yes. The community forum has the commit that broke things. | 01:16 |
| NanoCodeBug | josch: i thought that was for it being stuck at 100%? the behavior i see is it toggling between 0% and the correct value. | 01:17 |
| + reform15947 (~georg@84-115-231-62.cable.dynamic.surfer.at) | 01:18 | |
| josch | ah okay | 01:18 |
| josch | yes, that's different then | 01:18 |
| * reform15947 -> g-man | 01:20 | |
| - g-man (QUIT: Quit: Leaving) (~georg@84-115-231-62.cable.dynamic.surfer.at) | 01:26 | |
| NanoCodeBug | does anyone else get slow download speeds for apt? speedtests say i should be getting 50/50 mbps, but my download speed for apt is 60 kB/s from the mnt servers | 01:43 |
| - mtm (QUIT: Ping timeout: 246 seconds) (~textual@c-71-228-84-213.hsd1.fl.comcast.net) | 02:02 | |
| + NanoCodeBug30 (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 02:03 | |
| minute | NanoCodeBug30: getting 726kB/sec over wifi when installing pocket-reform-handbook | 02:03 |
| - NanoCodeBug30 (QUIT: Client Quit) (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 02:04 | |
| + NanoCodeBug83 (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 02:04 | |
| minute | now getting 2MB/sec | 02:04 |
| + mtm (~textual@c-71-228-84-213.hsd1.fl.comcast.net) | 02:05 | |
| - NanoCodeBug (QUIT: Ping timeout: 256 seconds) (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 02:05 | |
| minute | josch: i'm very pleased that pocket-reform-handbook works fine now and is also correctly listed in reform-help | 02:09 |
| NanoCodeBug83 | minute: i can't get above 100, averaging around 50 kb/s, speed tests show higher | 02:10 |
| minute | NanoCodeBug83: maybe some weird throttled connection somewhere to our server? | 02:10 |
| minute | somewhere on the internet i mean | 02:10 |
| NanoCodeBug83 | minute: i think so, it doesn't seem to be a pocket-wifi thing. | 02:11 |
| minute | unfortunately (?) we don't have a CDN in place | 02:11 |
| NanoCodeBug83 | i'll poke at some traceroutes, but getting some data from other folks on the west coast of the US would be good too | 02:13 |
| - NanoCodeBug83 (QUIT: Quit: Client closed) (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 02:16 | |
| + NanoCodeBug (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 02:27 | |
| NanoCodeBug | minute: from my desktop - it starts out slow but eventually climbs to 500+ kb/s, but the pocket stays at 50 kb/s | 02:29 |
| minute | NanoCodeBug: hmm no idea... i don't have imx8mp with me. mtu issues? | 02:31 |
| NanoCodeBug | minute: a311d with a wifi card i bought from asiarf - its the same as the one in the shop but they didn't put a rf shield on it for some reason | 02:32 |
| NanoCodeBug | i don't think thats affecting it but i'll keep poking | 02:32 |
| NanoCodeBug | and see if something changes it | 02:32 |
| NanoCodeBug | minute: the shop page for the wifi kit doesn't show where the antennas were mounted - obv not a problem until people get their hands on it, but where did you place the antenna stickers? | 02:33 |
| minute | NanoCodeBug: ah, i've been testing with a311d and that card also, earlier | 02:49 |
| minute | NanoCodeBug: that's true! i place one in the middle of the headphone board (where the molex originally was), and the other one kind of facing it (offset a bit) on the inside of the non metallic part of the back panel | 02:50 |
| - nsc (QUIT: Ping timeout: 276 seconds) (~nicolas@i5C74DD8F.versanet.de) | 03:14 | |
| + nsc (~nicolas@28-96-142-46.pool.kielnet.net) | 03:15 | |
| + reform24929 (~nano@c-73-35-191-67.hsd1.wa.comcast.net) | 03:18 | |
| * reform24929 -> set | 03:19 | |
| * set -> nanocodebugpocke | 03:20 | |
| * nanocodebugpocke -> nanocodebug2 | 03:20 | |
| - nanocodebug2 (QUIT: Client Quit) (~nano@c-73-35-191-67.hsd1.wa.comcast.net) | 03:22 | |
| - NanoCodeBug (QUIT: Ping timeout: 256 seconds) (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 03:45 | |
| + NanoCodeBug (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 03:47 | |
| - paperManu (QUIT: Ping timeout: 252 seconds) (~paperManu@198.16.214.40) | 04:00 | |
| - mjw (QUIT: Ping timeout: 245 seconds) (~mjw@gnu.wildebeest.org) | 04:04 | |
| - aloo_shu (QUIT: Ping timeout: 255 seconds) (~aloo_shu@90.166.193.180) | 04:13 | |
| + aloo_shu (~aloo_shu@90.166.193.180) | 04:22 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 04:40 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 05:33 | |
| - staticbunny (QUIT: Ping timeout: 252 seconds) (~staticbun@76-223-253-78.lightspeed.frokca.sbcglobal.net) | 05:41 | |
| _hramrach | How do I tahe off the top panel? I suppose it does not come out when unscrewed because it's glued to the thermal pads? | 08:04 |
| - aloo_shu (QUIT: Ping timeout: 246 seconds) (~aloo_shu@90.166.193.180) | 09:19 | |
| + gustav28 (~gustav@c-4135524e.019-141-67626730.bbcust.telenor.se) | 10:02 | |
| Twodisbetter | No, it is not glued. But because of how tight the lid on the display is, it may feel like that. You just put a toothpick or something like that in one of the edges the display and lift gently. | 10:23 |
| Twodisbetter | No, it is not glued. But because of how tight the lid on the display is, it may feel like that. You just put a toothpick or something like that in one of the edges the display lid and lift gently. | 10:33 |
| Twodisbetter | minute: to be clear to update the firmware of the system and battery controller can be accomplished through apt right? The keyboard firmware requires external flashing of the firmware on the RP controller right? | 10:40 |
| Twodisbetter | minute: So when the PD logic has been redone to work with 5v sources, that should just be an easy matter of apt updating reform-tools or something right? | 10:41 |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-105-237.dlls.tx.frontiernet.net) | 11:04 | |
| + jacobk (~quassel@47-186-105-237.dlls.tx.frontiernet.net) | 11:04 | |
| josch | Twodisbetter: no, this is not yet how it works | 11:08 |
| josch | you still have to manually download and execute the appropriate scripts | 11:09 |
| josch | Twodisbetter: this is what we talked about yesterday with respect to fwupd | 11:09 |
| + aloo_shu (~aloo_shu@90.166.193.0) | 11:16 | |
| minute | _hramrach: yes, there is some resistance because of the thermal pad, but it is not super strong. check out the ifixit teardown video! | 11:29 |
| _hramrach | yes, once one of the sides gets off slightly it's possible to grab the edge to flip it open | 11:30 |
| _hramrach | is there some source for those bolts used for bolting down M.2 cards? Looks like non come neither with the machine nor with cards | 11:31 |
| minute | _hramrach: very good question. one can also use a washer and an m2 screw, or a threaded hex spacer | 11:33 |
| Twodisbetter | josch: with a second device right? No worries. It is possible so good. Just cumbersome. | 11:34 |
| + kensanata2 (~alex@user/kensanata) | 11:36 | |
| + dominicm_ (45ee0d70e9@2a03:6000:1812:100::3e6) | 11:36 | |
| + cobra_ (~cobra@user/Cobra) | 11:38 | |
| + chrcav_ (~chrcav@user/chrcav) | 11:39 | |
| + xktr_ (~xktr@user/xktr) | 11:40 | |
| minute | Twodisbetter: no, no second device needed | 11:42 |
| Twodisbetter | minute: ahh so you could download the firmware and the script and just run it on the machine to updated? | 11:43 |
| Twodisbetter | that is easy. Awesome! | 11:43 |
| Twodisbetter | minute: so when the system and keyboard firmware is ready they will be pushed out and we can just grab them and go? | 11:44 |
| _hramrach | so, after router reset som devices actually connect to 5ghz, maybe wifi will work better now | 11:44 |
| - chrcav (QUIT: *.net *.split) (~chrcav@user/chrcav) | 11:44 | |
| - cobra (QUIT: *.net *.split) (~cobra@user/Cobra) | 11:44 | |
| - xktr (QUIT: *.net *.split) (~xktr@user/xktr) | 11:44 | |
| - kensanata (QUIT: *.net *.split) (~alex@user/kensanata) | 11:44 | |
| - dominicm (QUIT: *.net *.split) (45ee0d70e9@2a03:6000:1812:100::3e6) | 11:44 | |
| * kensanata2 -> kensanata | 11:44 | |
| * dominicm_ -> dominicm | 11:44 | |
| _hramrach | FWIW https://www.tme.eu/de/en/details/09482612749003/usb-cables-and-adapters/harting/ the price looks good but they have no ready stock | 11:45 |
| minute | Twodisbetter: yes, see here https://community.mnt.re/t/mnt-pocket-reform-system-controller-firmware-update-2024-08-26/2434/12 | 11:47 |
| minute | _hramrach: ha. i'm sourcing these at the moment and we'll resell them https://ix.sinbon.eu/product/ix-type-a-to-rj45-jack/ | 11:48 |
| Twodisbetter | minute: that just confirms that these kinds of firmware updates are things we will have to manually pull down. Thank you! | 11:48 |
| minute | Twodisbetter: at the moment yes. at some point this will be more automated | 11:49 |
| Twodisbetter | BUT, this update, for example, didn't update the keyboard firmware with the led timeout right? | 11:49 |
| minute | Twodisbetter: no. the keyboard is separate but can be updated in a similar way. there isn't an official release yet though | 11:49 |
| Twodisbetter | also sorry for bugging ya on a Saturday. Thanks for the help! Have a rad day! | 11:50 |
| - colinsane (QUIT: Quit: bye) (~colinunin@97-113-148-88.tukw.qwest.net) | 11:50 | |
| minute | Twodisbetter: thank you! | 11:50 |
| minute | btw i also find it strange that the imx8mp is so hot nowadays even when idle. i'm sure it wasn't like this a few years ago when i explored that chip. i was able to work on it more with no heatsink | 11:51 |
| minute | the cpu freq seems to have no influence also | 11:52 |
| minute | so it might be the gpu or some other core | 11:52 |
| minute | might be worth to recheck all clocking options (there are a lot though) | 11:53 |
| _hramrach | hh, disconnected again, and when reconnected it's connected to 2.4GHz | 11:55 |
| ch | NanoCodeBug: it doesnt toggle between 0 and a value for me, but it does toggle between 'battery' and 'plugged' | 11:57 |
| ch | NanoCodeBug: not sure how that state is derived in the first place, afaict in the sysctl fw state is always 0? | 11:58 |
| _hramrach | but the wifi works much better now, the only thing changed is adding more heat transfer pads | 11:58 |
| ch | NanoCodeBug, minute: i was trying to make sense of transfer speeds yesterday, i really dont understand it yet. some things go fast, some stay slow. cant tell what makes a difference | 11:59 |
| _hramrach | I also had the state flip on the charger once so it might reflect reality, too | 11:59 |
| ch | hmm? | 12:00 |
| _hramrach | I have a carger which shows the carging state, and once it was flipping, reconnecting the cable fixed it | 12:01 |
| ch | i dont have a charger connected | 12:01 |
| + andypiper (~andypiper@5.80.119.21) | 12:22 | |
| - andypiper (QUIT: Remote host closed the connection) (~andypiper@5.80.119.21) | 12:22 | |
| + andypiper (~andypiper@5.80.119.21) | 12:24 | |
| ch | ok reform2_lpc has its own ideas on charging/plugged/... instead of using a state reported by the sysctl fw | 12:29 |
| _hramrach | so looks like thermal transfer pads is what fixes the WiFi. Cut up some M.2 thermal pad and put a piece over the RAM and another over WiFi, with that there is little left of the CPU board that does not have a pad over it. There is a problem that the WiFi chip is very close to some connectors that shold not be covered, a template would probably help if this were supposed to be done in | 12:40 |
| _hramrach | production. | 12:40 |
| - andypiper (QUIT: Remote host closed the connection) (~andypiper@5.80.119.21) | 12:51 | |
| + paperManu (~paperManu@198.16.214.40) | 12:53 | |
| Twodisbetter | minute: congrats on the ifixit coverage. The ONLY thing I very much disagree with in their video is that comment they made about the design. I think the pocket is beautifully designed and absolutely should win some awards for that. | 13:12 |
| minute | _hramrach: thanks for confirming that this helps! | 13:13 |
| mesaoptimizer | btw the Reform next is beautiful | 13:14 |
| mesaoptimizer | based on the prototype screenshots I mean | 13:14 |
| + mjw (~mjw@gnu.wildebeest.org) | 13:16 | |
| minute | mesaoptimizer: thank you! prepare for more drops next week :D | 13:20 |
| josch | Twodisbetter: if you are a doing a product review you have to find *something* negative or otherwise you'll sound biased, right? If the "design" was the worst they found about the pocket then so be it. :) | 13:28 |
| minute | rcore pic https://mastodon.social/@mntmn/113096029545564088 | 13:34 |
| josch | there is so much going on! | 13:37 |
| ch | woooo | 13:37 |
| minute | there's also a dsi connector on the back! (but nothing else) | 13:38 |
| - mtm (QUIT: Ping timeout: 252 seconds) (~textual@c-71-228-84-213.hsd1.fl.comcast.net) | 14:03 | |
| + mtm (~textual@c-71-228-84-213.hsd1.fl.comcast.net) | 14:06 | |
| ch | strange, rebooting the sysctl rpi without going through a flash confused it | 14:28 |
| - sir-photch (QUIT: Remote host closed the connection) (~m-hy5poy@static.93.70.235.167.clients.your-server.de) | 14:32 | |
| + sir-photch (~m-hy5poy@static.93.70.235.167.clients.your-server.de) | 14:34 | |
| ch | NanoCodeBug: fun new edge case: the type-c power meter i have plugged inline seems to prevent the apple30w charger from detecting a reset of the fusb. sending a soft-reset message then makes it work again. :( | 14:39 |
| - sir-photch (QUIT: Remote host closed the connection) (~m-hy5poy@static.93.70.235.167.clients.your-server.de) | 14:43 | |
| + sir-photch (~m-hy5poy@static.93.70.235.167.clients.your-server.de) | 14:45 | |
| ch | https://community.mnt.re/t/burn-in-on-display/2510/6 maybe sth like that can be put into the default config | 14:55 |
| ch | would be nice if the kbd backlight would turn off at the same time, but not sure how to pull that integration off | 14:56 |
| ch | minute: curious, how much power does the a311d you're using draw when idle? | 15:12 |
| - vkoskiv (QUIT: Ping timeout: 255 seconds) (~vkoskiv@87-100-167-110.bb.dnainternet.fi) | 15:18 | |
| Twodisbetter | ch: josch could tell you about that in the Reform itself. He has been using one for a long time now. | 15:22 |
| - chrcav_ (QUIT: Quit: leaving) (~chrcav@user/chrcav) | 15:45 | |
| + chrcav (~chrcav@user/chrcav) | 15:45 | |
| + vkoskiv (~vkoskiv@87-100-167-110.bb.dnainternet.fi) | 15:47 | |
| vkoskiv | One of these days I'll reconfigure irssi to not mess up everything when the server reboots | 16:01 |
| vkoskiv | Autolog makes the situation just about tolerable, but it's still lame whenever it happens | 16:02 |
| josch | ch: last time i tried "swaymsg output * power off" it looked up my machine when idle | 16:08 |
| josch | but maybe it is time to try this out again | 16:09 |
| - jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@47-186-105-237.dlls.tx.frontiernet.net) | 16:32 | |
| _hramrach | hm, firefox can't display extensions https://github.com/uBlockOrigin/uMatrix-issues/issues/14 | 16:56 |
| NanoCodeBug | ch: i've noticed my usb-c power meter messes with the port orientation detection as well | 17:08 |
| NanoCodeBug | ch: the reform2-lpc was written for the original reform2 system controller - it makes assumptions based on the capabilities of the data that controller sent. I don't think all those assumptions hold true for the pocket, the pocket doesn't send all the same information either - a future project (for me or whomever wants to have some fun) is to go | 17:08 |
| NanoCodeBug | back and revisit it and add a device tree option that specifies the controller host (or fork the driver for the pocket). so things like the battery technology, number of batteries, etc. all report correctly. | 17:08 |
| + andypiper (~andypiper@5.80.119.21) | 18:04 | |
| - NanoCodeBug (QUIT: Ping timeout: 256 seconds) (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 18:11 | |
| + NanoCodeBug (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 18:43 | |
| * plomlomp0m -> plomlompom | 18:48 | |
| - NanoCodeBug (QUIT: Quit: Client closed) (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 18:49 | |
| + NanoCodeBug (~NanoCodeB@c-73-35-191-67.hsd1.wa.comcast.net) | 18:49 | |
| - mjw (QUIT: Ping timeout: 245 seconds) (~mjw@gnu.wildebeest.org) | 19:06 | |
| + mjw (~mjw@gnu.wildebeest.org) | 19:07 | |
| - andreas-e (QUIT: Remote host closed the connection) (~Andreas@2001:861:c4:f2f0::c64) | 19:20 | |
| _hramrach | update-initramfs complains it's missing zstd and is using gzip insted. zstd has generelly better compression and better performance than gzip, especially decompression performance. Adding it to the image is likely to slightly shoten boot times. | 19:37 |
| andypiper | adding zstd is already in one of the issues I think as a proposal... https://source.mnt.re/reform/reform-system-image/-/issues/27 | 19:47 |
| - andypiper (QUIT: Remote host closed the connection) (~andypiper@5.80.119.21) | 19:58 | |
| + IchikaZou (~IchikaZou@36-231-102-217.dynamic-ip.hinet.net) | 19:59 | |
| - IchikaZou (QUIT: Remote host closed the connection) (~IchikaZou@36-231-102-217.dynamic-ip.hinet.net) | 20:04 | |
| + jacobk (~quassel@2603:8080:b200:7b02:77cb:6304:f9db:dda1) | 20:10 | |
| - mjw (QUIT: Ping timeout: 276 seconds) (~mjw@gnu.wildebeest.org) | 20:18 | |
| josch | _hramrach: i tested unpack times of the initramfs when packed as gzip versus packed with zstd on a311d and yes, zstd is faster: by half a second | 20:22 |
| josch | as a result i didn't bother yet but there is this issue about adding a few more utilities to the image: | 20:22 |
| _hramrach | by more if the kernel uncompression happens during some initial boot state when the CPU frequency is low | 20:22 |
| josch | right, but anything below 0.5 seconds is not noticable compared to how often you boot the system per day, no? | 20:23 |
| josch | like, lets say it uncompresses in 0 seconds -- that's still only 0.5 seconds faster | 20:23 |
| josch | here is the issue: https://source.mnt.re/reform/reform-system-image/-/issues/27 | 20:23 |
| josch | or in other words: the time i'm spending writing about this here is more than several hundred boots even assuming it would be zero :) | 20:24 |
| _hramrach | The gain is only noticable if you load from slow memory or using very slow driver in u-boot or if the decompression happens before the CPU frequency is set | 20:25 |
| - jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@2603:8080:b200:7b02:77cb:6304:f9db:dda1) | 20:26 | |
| _hramrach | doesn't sway have some fullscreen layout? | 20:31 |
| _hramrach | like on a 27" screen I can make use of more than one appllication at the same time, on a 7" hardly | 20:32 |
| ch | josch: seemed to work fine on the pocket. maybe cpu and/or dts specific. certainly would suck a lot if turning off hdmi hangs the machine | 20:39 |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-4135524e.019-141-67626730.bbcust.telenor.se) | 20:51 | |
| + gustav28 (~gustav@c-4135524e.019-141-67626730.bbcust.telenor.se) | 20:55 | |
| + mjw (~mjw@gnu.wildebeest.org) | 20:55 | |
| + staticbunny (~staticbun@76-223-253-78.lightspeed.frokca.sbcglobal.net) | 21:17 | |
| - staticbunny (QUIT: Ping timeout: 248 seconds) (~staticbun@76-223-253-78.lightspeed.frokca.sbcglobal.net) | 21:22 | |
| josch | ch: this is why (before the pocket) everybody was using brightnessctl instead | 21:46 |
| josch | search in the channel logs for "dpms" to find people reporting this | 21:46 |
| josch | and i saw it on imx8mq and on a311d | 21:46 |
| josch | ch: oh and maybe even more disturbing: people even saw the lock-up issues when not using wayland or xorg at all but just on the tty and console blanking enabled | 21:49 |
| ch | mh | 21:52 |
| ch | not good :) | 21:52 |
| - blast007 (QUIT: Remote host closed the connection) (~blast@user/blast007) | 22:09 | |
| + blast007 (~blast@user/blast007) | 22:09 | |
| + IchikaZou (~IchikaZou@36-231-102-217.dynamic-ip.hinet.net) | 22:11 | |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-4135524e.019-141-67626730.bbcust.telenor.se) | 22:15 | |
| + reform25593 (~sandspur@2604:2d80:c82:9b00:f867:92c3:f381:2832) | 22:26 | |
| - reform25593 (QUIT: Remote host closed the connection) (~sandspur@2604:2d80:c82:9b00:f867:92c3:f381:2832) | 22:27 | |
| ch | hmm, any tricks to be aware of for unbricking the sysctl rpi? | 22:35 |
| ch | it doesnt enumerate as a device on my other laptop | 22:36 |
| ^alex | how are you connecting to it? | 22:38 |
| ^alex | the jumpers need to go away from the port on the mainboard, the switch needs to be thrown, and the internal usb-c port should show up the boot-mode pico | 22:38 |
| ch | tried a usb-c<>usb-c cable and a usb-c<>a | 22:39 |
| ch | the battery pack stays connected, right? | 22:39 |
| ^alex | the battery stays connected | 22:39 |
| ^alex | to avoid having to unscrew the motherboard we use a right-angle adapter | 22:39 |
| ch | i'll try another computer. the handbook says sth about micro-usb, but that seems like a leftover? | 22:41 |
| ^alex | just to confirm, you've also moved the jumpers above the port, right? | 22:42 |
| ^alex | with the jumpers in their default position, the internal USB-C port goes to the SoC, not the rpi | 22:42 |
| ch | yeah i moved them | 22:43 |
| ch | do you know if c->a cables work or only c<>c? | 22:44 |
| ch | ah nevermind | 22:45 |
| ch | turning off the standby powerswitch doesn't help :) | 22:45 |
| ch | is there a harm leaving the jumpers in that way? | 22:49 |
| ch | ^alex: thanks! | 22:50 |
| ch | angled cable is ordered already :) | 22:50 |
| ^alex | yeah, if you leave them that way the mainboard can't communicate with the syscon | 22:51 |
| ch | ah. better put them back then | 22:57 |
| ch | ^alex: have you explored using a timer interrupt + __wfi() intead of sleep_us(...) for possibly better power consumption on the sysctl pi? | 22:58 |
| + ryuka (sid667511@id-667511.hampstead.irccloud.com) | 22:58 | |
| ^alex | we've been exploring Dormant Mode | 22:58 |
| ^alex | but have mostly been bricking the syscon instead | 22:59 |
| ^alex | we want to wait for NanoCodeBug's refactor to land | 22:59 |
| * ryuka -> Ryuka_Zou | 22:59 | |
| ^alex | before we get too far into making things more interrupt-driven | 23:02 |
| ch | i think i've also come to this conclusion | 23:08 |
| ch | with the som off, there a power draw of 0.5W if the reporting is correct | 23:09 |
| - IchikaZou (QUIT: Remote host closed the connection) (~IchikaZou@36-231-102-217.dynamic-ip.hinet.net) | 23:10 | |
| + IchikaZou (~IchikaZou@36-231-102-217.dynamic-ip.hinet.net) | 23:11 | |
| * IchikaZou -> ryukazou | 23:14 | |
| - ryukazou (QUIT: Remote host closed the connection) (~IchikaZou@36-231-102-217.dynamic-ip.hinet.net) | 23:24 | |
| + ryukazou (~ryukazou@36-231-102-217.dynamic-ip.hinet.net) | 23:24 | |
| - ryukazou (QUIT: Killed (molybdenum.libera.chat (Nickname regained by services))) (~ryukazou@36-231-102-217.dynamic-ip.hinet.net) | 23:34 | |
| * Ryuka_Zou -> ryukazou | 23:34 | |
| + ryukazou_ (~ryukazou@36-231-102-217.dynamic-ip.hinet.net) | 23:35 | |
| - ryukazou_ (QUIT: Remote host closed the connection) (~ryukazou@36-231-102-217.dynamic-ip.hinet.net) | 23:38 | |
| + ryukazou_ (~ryukazou@36-231-102-217.dynamic-ip.hinet.net) | 23:38 | |
| - ryukazou_ (QUIT: Remote host closed the connection) (~ryukazou@36-231-102-217.dynamic-ip.hinet.net) | 23:40 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!