| minute | cinap_lenrek: what's up | 00:00 |
|---|---|---|
| minute | cinap_lenrek: i've read "megamix" before and wondered what that is | 00:00 |
| - mjw (QUIT: Quit: Leaving) (~mark@gnu.wildebeest.org) | 00:02 | |
| cinap_lenrek | sounds like a dj set ;) | 00:30 |
| cinap_lenrek | just found it funny | 00:31 |
| cinap_lenrek | its in the imx8mqrm | 00:31 |
| cinap_lenrek | in the gpc_pgc controls | 00:31 |
| minute | haha yeah | 00:33 |
| cinap_lenrek | damn, doesnt seem to work | 00:38 |
| minute | whatcha trying? | 00:38 |
| cinap_lenrek | so i'm having issues reseting the dphy | 00:38 |
| cinap_lenrek | as soon as i touch dphy regs the machine freezes | 00:38 |
| cinap_lenrek | so i thought, well, must be some clock not enabled | 00:39 |
| cinap_lenrek | then i found the gpc controller which has a power-up bit for the mipi dphy | 00:39 |
| cinap_lenrek | so tried that | 00:39 |
| cinap_lenrek | but still, thats not it | 00:39 |
| minute | oh. but that's a common issue yeah, freeze if something's bus clock is not on | 00:41 |
| cinap_lenrek | no dice | 01:01 |
| cinap_lenrek | i mean, theres only a single clock gate | 01:01 |
| cinap_lenrek | CCGR93 | 01:01 |
| cinap_lenrek | and then there are MIPI_DSI_PHY_REF_CLK_ROOT, MIPI_DSI_ESC_RX_CLK_ROOT, MIPI_DSI_ESC_CLK_ROOT | 01:02 |
| cinap_lenrek | DISPLAY_APB_CLK_ROOT, DISPLAY_AXI_CLK_ROOT< DISPLAY_RTRM_CLK_ROOT, DISPLAYDC8000_CLK_ROOT, DISPLAY_DTRC_CLK_ROOT | 01:03 |
| cinap_lenrek | from the docs, CCGR93 only coveres the DISPLAY_* clocks | 01:03 |
| cinap_lenrek | but i'v basically ensured that all the root clocks are configured properly | 01:04 |
| cinap_lenrek | theres also a MIPI_CORE_CLK_ROOT | 01:05 |
| cinap_lenrek | but its nowhere documented what the frequency should be | 01:05 |
| cinap_lenrek | ah | 01:05 |
| - Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p54bf6423.dip0.t-ipconnect.de) | 01:09 | |
| cinap_lenrek | does the dphy need the pixel clock running for register access? | 01:09 |
| cinap_lenrek | it seems strange | 01:09 |
| cinap_lenrek | afaik, for lcdif, the pixelclock would only run once i configure the lcdif in DOTCLK mode | 01:10 |
| minute | i don't think so | 01:19 |
| minute | the linux driver needs IMX8MQ_CLK_DSI_PHY_REF | 01:20 |
| minute | what's phy_write(phy, 0x00, DPHY_LOCK_BYP); | 01:22 |
| minute | also, there's a bunch of resets https://source.mnt.re/reform/reform-boundary-uboot/-/blob/variant-emmc-nvme-boot/drivers/video/mipi_dsi_northwest.c#L248 | 01:27 |
| cinap_lenrek | oh | 01:31 |
| cinap_lenrek | its using a different set of registers for the resets | 01:31 |
| cinap_lenrek | i thought these where done by the SRC | 01:31 |
| cinap_lenrek | ok | 01:39 |
| cinap_lenrek | but whats sim_base? | 01:39 |
| cinap_lenrek | its passed in to the setup function, but it appears nowhere to be used | 01:39 |
| cinap_lenrek | the only reference to "sim" is in the ccm section | 01:42 |
| - q66 (QUIT: ) (~q66@q66.moe) | 01:56 | |
| + reform121 (~gus@35.139.130.53) | 01:57 | |
| - reform121 (QUIT: Client Quit) (~gus@35.139.130.53) | 01:58 | |
| minute | ah hm possibly imx7 | 01:58 |
| minute | lol https://community.nxp.com/t5/i-MX-Processors/IMX8MQ-Uboot-cannot-read-or-write-the-MIPI-DSI-register/m-p/1278855/highlight/true | 01:59 |
| minute | cinap_lenrek: sorry, i sent you down the wrong path | 02:00 |
| cinap_lenrek | no, thank you for helping | 02:02 |
| - mtm (QUIT: Ping timeout: 276 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 02:03 | |
| minute | that driver is (at least in part) for imx7 which has something called SIM/SIM0 | 02:04 |
| + q66 (~q66@q66.moe) | 02:05 | |
| minute | interesting https://github.com/boundarydevices/u-boot/blob/boundary-v2020.10/drivers/video/imx/nwl-drv.c#L856 | 02:06 |
| minute | * Usually, we don't need this clock here, but due to a design issue, | 02:06 |
| minute | * the MIPI Reset Synchronizer block depends on this clock. | 02:06 |
| minute | also * Usually, we don't need this clock here, but due to a design issue, | 02:07 |
| minute | * the MIPI Reset Synchronizer block depends on this clock. | 02:07 |
| minute | sorry, c/p fail | 02:07 |
| minute | also https://github.com/boundarydevices/u-boot/blob/boundary-v2020.10/drivers/video/imx/nwl-drv.c#L890 | 02:07 |
| minute | * We need to manage individual resets, since the order of their usage | 02:08 |
| minute | * really matters to DSI Host Controller. The order of operation, | 02:08 |
| minute | * should be like this: | 02:08 |
| cinap_lenrek | bingo | 02:14 |
| cinap_lenrek | it was the PCLK reset | 02:14 |
| cinap_lenrek | the god damn manual doesnt mention it | 02:15 |
| minute | nice! | 02:15 |
| cinap_lenrek | all they say is | 02:16 |
| cinap_lenrek | "reset_dpi_n" | 02:16 |
| cinap_lenrek | "reset_byte_n" | 02:16 |
| cinap_lenrek | "reset_esc_n" | 02:16 |
| cinap_lenrek | 2) Setup related clocks.... | 02:16 |
| cinap_lenrek | 3) Setup MIPI DSI application by programming DSI Host Controller *AND* DSI PHY required parameters... | 02:16 |
| - q66 (QUIT: Ping timeout: 260 seconds) (~q66@q66.moe) | 02:16 | |
| cinap_lenrek | 4) deassert all the resets | 02:16 |
| cinap_lenrek | like fuckers | 02:17 |
| minute | lol | 02:17 |
| + q66 (~q66@q66.moe) | 02:17 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 03:14 | |
| cinap_lenrek | hm | 03:29 |
| cinap_lenrek | dphy pll doesnt lock :/ | 03:29 |
| cinap_lenrek | maybe only works with the videopll as input? | 03:31 |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 03:32 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 03:32 | |
| + littlebo1eep (~alMalsamo@gateway/tor-sasl/almalsamo) | 03:38 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 03:39 | |
| + bkeys (~Thunderbi@static-198-54-135-37.cust.tzulo.com) | 03:43 | |
| - littlebo1eep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 03:47 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 03:48 | |
| - bkeys (QUIT: Ping timeout: 246 seconds) (~Thunderbi@static-198-54-135-37.cust.tzulo.com) | 04:02 | |
| + mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 04:08 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 04:58 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 05:07 | |
| + littlebo1eep (~alMalsamo@gateway/tor-sasl/almalsamo) | 05:18 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 05:22 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 05:26 | |
| - littlebo1eep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 05:28 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 05:29 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 05:59 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 06:08 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 07:04 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 07:05 | |
| + chomwitt (~chomwitt@2a02:587:dc0e:3e00:bc0d:a683:e7e9:901) | 07:23 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 07:49 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 07:59 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 08:12 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 08:15 | |
| + littlebo1eep (~alMalsamo@gateway/tor-sasl/almalsamo) | 08:55 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 08:56 | |
| - littlebo1eep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 09:06 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 09:06 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 09:12 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 09:19 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 09:53 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 10:01 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 10:16 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 10:17 | |
| + littlebo1eep (~alMalsamo@gateway/tor-sasl/almalsamo) | 10:22 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 10:23 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 10:27 | |
| - littlebo1eep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 10:29 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 10:34 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 10:38 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 10:46 | |
| - q66 (QUIT: Ping timeout: 258 seconds) (~q66@q66.moe) | 10:48 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 10:54 | |
| + mjw (~mark@gnu.wildebeest.org) | 11:04 | |
| bluerise | minute: did you get a chance to try the UEFI thing? | 11:08 |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 11:11 | |
| + Christoph_ (~Christoph@p4fe73f15.dip0.t-ipconnect.de) | 11:16 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 11:18 | |
| minute | bluerise: unfortunately not yet | 11:33 |
| minute | bluerise: it appears to work https://twitter.com/cooljqln/status/1532200743083851776?t=XvB00RE6DWGZVLNcf1b-VQ&s=19 | 11:43 |
| bluerise | Great, I'm jealous | 11:43 |
| minute | i wonder if it shouldn't also output stuff on hdmi by default? or no? | 11:46 |
| bluerise | Yup, it should | 11:48 |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 12:20 | |
| + mark (~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440) | 12:35 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 12:46 | |
| + littlebo1eep (~alMalsamo@gateway/tor-sasl/almalsamo) | 12:52 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 12:53 | |
| - sturles (QUIT: Remote host closed the connection) (~sturles@sauron.uio.no) | 13:00 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 13:10 | |
| - littlebo1eep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 13:13 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 13:36 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 13:44 | |
| + q66 (~q66@q66.moe) | 13:57 | |
| - GNUmoon (QUIT: Ping timeout: 240 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon) | 14:02 | |
| - mtm (QUIT: Ping timeout: 240 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 14:03 | |
| + littlebo1eep (~alMalsamo@gateway/tor-sasl/almalsamo) | 14:03 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 14:07 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 14:11 | |
| - littlebo1eep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 14:13 | |
| - q66 (QUIT: Quit: No Ping reply in 180 seconds.) (~q66@q66.moe) | 14:21 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 14:22 | |
| + q66 (~q66@q66.moe) | 14:23 | |
| + bkeys (~Thunderbi@static-198-54-135-37.cust.tzulo.com) | 14:27 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 14:28 | |
| bkeys | minute: I got my Reform yesterday, the experience of building it was pretty good | 14:28 |
| bkeys | Thanks for such an awesome project | 14:29 |
| bkeys | Is there a known list of operating systems other than the default debian install that is known to work with the Reform | 14:31 |
| + littlebo1eep (~alMalsamo@gateway/tor-sasl/almalsamo) | 14:35 | |
| minute | awesome bkeys! | 14:35 |
| minute | there's no list but you can find some stuff on community.mnt.re | 14:35 |
| minute | bkeys: so far only linux and genode work well, BSDs and plan9 don't have a solution for internal display yet | 14:36 |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 14:37 | |
| bkeys | Yeah I found some stuff, was wondering if there was something comprehensive | 14:37 |
| bkeys | I'm okay with Linux; I really like rpm based distros so getting Fedora to work would be nice | 14:37 |
| bkeys | https://community.mnt.re/t/death-by-fedora/912/4 | 14:37 |
| bkeys | This guy seems to have had a rough time getting it working | 14:38 |
| bkeys | How much of the kernel is mainlined for the Reform? | 14:39 |
| - littlebo1eep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 14:40 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 14:40 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 14:49 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 14:52 | |
| minute | bkeys: a lot, except for some small patches and hdmi... check our reform-system-image and reform-debian-packages repos | 14:55 |
| minute | i see no apparent reason why fedora should be hard to get working | 14:55 |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 14:59 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 15:00 | |
| bkeys | Are those small bits going to ever be mainlined? | 15:02 |
| bkeys | I will look at those repos; I don't mind having to use a custom kernel on something like the reform | 15:03 |
| bkeys | If I can build it and make it redistributable with a .rpm that'd be helpful for others | 15:08 |
| - Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p4fe73f15.dip0.t-ipconnect.de) | 15:10 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 15:21 | |
| josch | bkeys: all the patches are here: https://source.mnt.re/reform/reform-debian-packages/-/tree/main/linux/patches | 15:41 |
| josch | it would be great if somebody could work on getting them included into the kernel proper | 15:42 |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 15:52 | |
| - erle (QUIT: Ping timeout: 258 seconds) (~erle@ip5f5af7a3.dynamic.kabel-deutschland.de) | 16:00 | |
| * mark -> Guest4412 | 16:02 | |
| - Guest4412 (QUIT: Killed (calcium.libera.chat (Nickname regained by services))) (~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440) | 16:02 | |
| + Guest4412 (~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440) | 16:02 | |
| + mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 16:09 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 16:30 | |
| + bkeys1 (~Thunderbi@253.236-24.gp.ptn.tftn.static.friendlycity.net) | 16:47 | |
| - bkeys (QUIT: Ping timeout: 258 seconds) (~Thunderbi@static-198-54-135-37.cust.tzulo.com) | 16:50 | |
| * bkeys1 -> bkeys | 16:51 | |
| + erle (~erle@95.90.247.163) | 17:06 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 17:07 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 17:14 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 17:37 | |
| bkeys | I logged into the debian on my reform, ran a update, upgrade and now I get a kernel panic when I reboot | 17:41 |
| bkeys | Admittedly I didn't read any instructions about this; it's just something I do with a new install of any linux distro. Is this expected behavior minute? | 17:42 |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 17:42 | |
| josch | bkeys: what kind of debian installation did you have before? | 17:43 |
| bkeys | The one that came on the SD card in the box | 17:43 |
| minute | bkeys: huh... can you download and flash this system image and try again: https://source.mnt.re/reform/reform-system-image/-/jobs/793/artifacts/browse/reform2-imx8mq/ | 17:43 |
| minute | bkeys: it's possible that the version on the sd card that shipped with you reform is outdated | 17:44 |
| minute | there was a lot of work on clean debian integration in the meantime | 17:44 |
| vkoskiv | How does the img v3 feel at the moment? Ready to daily use yet? | 17:44 |
| bkeys | Yeah, my end goal is to put Fedora on it; and the main guy who maintains Fedora for ARM says that Fedora already runs well on I.MX8 so hopefully it will just be a matter of running a custom kernel | 17:46 |
| bkeys | I gotta say minute I am really impressed with the craftsmanship you put into this laptop; you can never find laptops this small anymore and the keyboard is awesome | 17:47 |
| bkeys | It's somewhat reminiscent of my old thinkpad x220 | 17:47 |
| bkeys | The little OLED screen above the keyboard tickles me for some reason. My father had an old dell XPS desktop that was our family computer growing up and I remember it had this little screen that had solitaire and some other stuff on it | 17:49 |
| - mjw (QUIT: Killed (NickServ (GHOST command used by Guest4412!~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440))) (~mark@gnu.wildebeest.org) | 17:50 | |
| * Guest4412 -> mjw | 17:50 | |
| + mark_ (~mark@gnu.wildebeest.org) | 17:51 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 17:57 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 17:59 | |
| + bkeys1 (~Thunderbi@static-198-54-135-37.cust.tzulo.com) | 18:04 | |
| minute | vkoskiv: yes, ready for daily | 18:04 |
| minute | bkeys1: ha, thanks you!! i like to hear these kind of impressions | 18:05 |
| - bkeys (QUIT: Ping timeout: 256 seconds) (~Thunderbi@253.236-24.gp.ptn.tftn.static.friendlycity.net) | 18:07 | |
| * bkeys1 -> bkeys | 18:07 | |
| josch | minute: could we add a sysimage-v3 generated for Debian testing instead of unstable? I'd not really agree with "ready for daily use" as long as we use Debian unstable as the base because unstable (as the same suggests) can contain horrible bugs that could thrash your whole system. Using testing is not 100% safe from that either but I'd rather recommend people to use Debian testing as a "rolling release" | 18:14 |
| josch | than unstable which can break your whole machine at any point. | 18:15 |
| vkoskiv | If my system gets trashed, I'll just restore from a backup! | 18:15 |
| vkoskiv | And all my code is on a git server somewhere anyway | 18:16 |
| josch | Sure, for experienced users, unstable is much less of a problem. :) | 18:16 |
| josch | Or maybe we can at least install apt-listbugs into the sysimage-v3 so that for every "apt-get upgrade" the user is presented with all the release critical bugs in the packages that they would upgrade to. | 18:17 |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 18:17 | |
| josch | Just recently we had a dpkg upload that led to systems becoming unbootable... | 18:18 |
| minute | josch: sure, how could we do it? | 18:19 |
| minute | josch: apt-listbugs sounds better tbh | 18:19 |
| josch | Okay, that's easy. I'll file a MR. | 18:19 |
| minute | our complexity will increase soon as we will add more device form factors (at least 1 ^^) and processors | 18:20 |
| josch | I'm a bit afraid that the current CI setup will not scale that well with that in mind because it stores all the artifacts in a tmpfs permanently. | 18:20 |
| vkoskiv | If one were to upgrade to the RCM4 variant, would the expectation bet to run raspbian on there or are there plans to support all the platforms in the reform system image? | 18:21 |
| minute | vkoskiv: the latter. i don't think stock raspian is an adequate user experience, it doesn't even use wayland | 18:21 |
| vkoskiv | From the little I've seen of the reform image, it is very obvious that it is very detail-oriented | 18:22 |
| minute | yeah | 18:22 |
| vkoskiv | The utility scripts and the initial setup looks so lovely :D | 18:22 |
| minute | thanks, the goal is to be welcoming ^^ and i want to improve that even more | 18:22 |
| vkoskiv | My unit is estimated to arrive on monday. Though it's shipping to my parents' house, so I'll see when I'm able to go there to play with it. | 18:22 |
| vkoskiv | Hopefully on monday, but I'm feeling a cold coming on possibly :S | 18:23 |
| minute | ugh | 18:23 |
| vkoskiv | Regardless, the start of my MNT journey is imminent. | 18:23 |
| bkeys | Okay booting the new image now | 18:24 |
| vkoskiv | Over the last few months I've switched completely over to Linux from macOS, and I've got a development setup that is quite productive now. | 18:24 |
| vkoskiv | I've also larped using the reform by just using my old 2005 Fujitsu laptop which is similar in size | 18:24 |
| vkoskiv | But much worse in performance | 18:24 |
| vkoskiv | So the reform will be a nice upgrade. | 18:24 |
| vkoskiv | And I know that my workflow will run well on there, because it works fine on the old 2005 machine. | 18:25 |
| minute | nice | 18:25 |
| josch | minute: speaking about "being welcoming" what are your thoughts on https://source.mnt.re/reform/reform-system-image/-/merge_requests/43 | 18:26 |
| minute | josch: yes, i want this, but a bit more refined | 18:26 |
| minute | josch: i'll get back to this after my short holiday that's from tomorrow till monday ^^ | 18:27 |
| josch | cool! :) | 18:27 |
| vkoskiv | Have a fun holiday! | 18:27 |
| + Christoph_ (~Christoph@p4fe73f15.dip0.t-ipconnect.de) | 18:28 | |
| minute | thanks! | 18:29 |
| minute | i also noted 3 lpc/boot todos: | 18:30 |
| minute | - [ ] reform LPC: detected balancing/charging loop and stop after 10x | 18:30 |
| minute | - [ ] reform uboot: print to OLED during boot | 18:30 |
| minute | - [ ] reform LPC: integrate battery status via SPI | 18:30 |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 18:31 | |
| josch | those would be great improvements :) | 18:31 |
| minute | they all shouldn't be too hard but would make reform life better | 18:32 |
| josch | I'm also happy to hear, that you plan to offer a sysimage for RCM4 instead of raspbian. I'm ready to contribute to that as well but acquiring a RCM4 is kinda impossible atm. XD | 18:32 |
| minute | ah, awesome | 18:33 |
| minute | alternatively we can focus on soquartz as long as cm4s are still so unavailable | 18:34 |
| minute | jacqueline just got it too boot in reform with edk2/uefi and at least sees serial output ;) | 18:34 |
| minute | (RK3566) | 18:34 |
| josch | jacqueline is so awsome -- very impressive stuff she's doing | 18:35 |
| bkeys | Where in the manual does it explain how to hook up to wifi? | 18:35 |
| minute | bkeys: do you mean in software? | 18:35 |
| bkeys | Yeah I didn't order a wifi card from you but I have a wifi card that works | 18:35 |
| minute | bkeys: that part of the manual is outdated unfortunately as with v3 we switched to networkmanager. so you can use `nmtui` for example | 18:35 |
| bkeys | I'll just do it in gnome | 18:35 |
| minute | ah | 18:35 |
| minute | gnome is easy yes | 18:35 |
| bkeys | I like KDE, so if it can run gnome I should be able to run KDE | 18:36 |
| minute | not sure if KDE works nowadays | 18:36 |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 18:36 | |
| minute | last time i checked (longer time ago) it didn't | 18:36 |
| bkeys | on wayland or x11? | 18:36 |
| minute | wayland | 18:36 |
| bkeys | It's terrible on wayland | 18:36 |
| minute | xserver does not work in general | 18:36 |
| minute | only via the trick in reform-windowmaker | 18:36 |
| minute | (it uses cage and xwayland) | 18:36 |
| minute | so kde could work with that too | 18:37 |
| bkeys | I have not used gnome3 in forever | 18:37 |
| bkeys | But I don't see my cursor | 18:37 |
| minute | huh | 18:37 |
| minute | with stock v3 image from the link above? | 18:37 |
| bkeys | Yes | 18:37 |
| minute | i tested it a few days ago | 18:37 |
| minute | how did you start it, just `gnome`? | 18:37 |
| bkeys | Yes | 18:37 |
| bkeys | Nothing special | 18:37 |
| bkeys | I hope my trackball is fine | 18:38 |
| minute | do you have a DIY kit? | 18:38 |
| bkeys | Yes | 18:38 |
| minute | ah, so maybe trackball is not hooked up properly? what if you connect a USB mouse? | 18:38 |
| minute | also, the trackball already works in the console | 18:38 |
| minute | normally | 18:38 |
| bkeys | It goes into Ul2 | 18:38 |
| minute | maybe it's programming switch is still on? | 18:39 |
| minute | (trackball's) | 18:39 |
| bkeys | I never flipped a switch on it | 18:39 |
| minute | yeah, but maybe from the factory (us) | 18:39 |
| minute | `lsusb` should show `Bus 001 Device 004: ID 03eb:2041 Atmel Corp. LUFA Mouse Demo Application` | 18:40 |
| bkeys | Is it sw7 that needs to be flipped on? | 18:41 |
| minute | bkeys: off | 18:42 |
| minute | there's only one switch on the trackball | 18:42 |
| bkeys | sw is off | 18:42 |
| minute | ok | 18:42 |
| minute | if it is on or no firmware flashed, you would see DFU bootloader in lsusb | 18:42 |
| minute | it's possible that the sensor cable is loose, that is a common issue | 18:43 |
| minute | so you could replug that | 18:43 |
| bkeys | Let me turn it back on and run lsusb | 18:43 |
| bkeys | minute: I see "LUFA Mouse Demo Application" | 18:44 |
| bkeys | In lsusb | 18:44 |
| bkeys | I run windowmaker, I see the cursor but it doesn't move with the trackball | 18:44 |
| bkeys | Moves fine with USB mouse though | 18:45 |
| minute | bkeys: lufa mouse demo application is good though | 18:46 |
| minute | bkeys: maybe the sensor is dirty/smudged? when pressing reset button on the trackball, does it flash once? (through the trackball keys) | 18:46 |
| bkeys | Im taking the bottom off | 18:47 |
| minute | yeah | 18:48 |
| bkeys | Yep the cable wasn't on there good | 18:49 |
| bkeys | That explains that | 18:49 |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 18:50 | |
| bkeys | Oh no | 18:50 |
| bkeys | I saw a bit of smoke come out; hopefully nothing got fried... | 18:50 |
| minute | smoke? :O | 18:51 |
| bkeys | It looks like it came from the som | 18:51 |
| bkeys | I unplugged the Ul2 line from the trackball | 18:51 |
| bkeys | I thought I was fine | 18:51 |
| minute | loose screw or other particle somewhere shorting something? | 18:52 |
| bkeys | 1 cell is showing up as ??? | 18:52 |
| bkeys | Am I safe to unplug the power cables to the carrier board? | 18:52 |
| bkeys | And can I still turn it on with 1 battery on ??? | 18:53 |
| bkeys | Dang it... | 18:54 |
| bkeys | Well I am booting up | 18:55 |
| bkeys | I can boot fine at least | 18:55 |
| bkeys | Trackball works | 18:55 |
| bkeys | minute: Well, how do I know which battery to pull out? | 18:56 |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 18:56 | |
| bkeys | minute: So my guess as to what happened is something got fried because I have one battery that is gone and a few others are reporting 2.2V; the computer boots up fine. I hope it's just a matter of replacing some 18650s but I suspect it's that the board is damaged | 19:05 |
| bkeys | I don't think the battery discharged in a fraction of a second | 19:06 |
| bkeys | Well I put it on the charger and all of the ones that said 2.2V are now back at 3.3V with all of the other ones. So that is a relief, maybe it is just a ruined battery in which case no problem | 19:08 |
| - mjw (QUIT: Quit: Leaving) (~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440) | 19:14 | |
| bkeys | Okay, so I unplugged the battery board and removed the 4; I still get a flashing ??? on the one battery. I see what happened | 19:16 |
| bkeys | I tried to unscrew the trackball and it shorted something out | 19:16 |
| bkeys | The battery itself is fine. I suspect since I unplugged the battery board and still get a flashing ??? that something is fried on my main board which is where the spark and smoke came from | 19:17 |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 19:18 | |
| bkeys | Is it possible to buy just a new carrier board for the Reform? I am not seeing an option for it in the shop | 19:19 |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 19:20 | |
| minute | bkeys: flashing "???"? | 19:27 |
| minute | bkeys: hmm maybe you have very old lpc/keyboard firmware? | 19:27 |
| minute | bkeys: check that you update lpc and keyboard firmware, pointers are in the forum. carriers currently hard to replace (chip shortage) | 19:28 |
| minute | i am now in holiday mode till monday | 19:28 |
| bkeys | will do; i just took it apart and I see no visible burns. Not that that is very indicative of much | 19:31 |
| bkeys | I mean its 1 battery so I can live with it for a while; I'd still want to fix it somehow either way. But I will try what you said | 19:32 |
| bkeys | Just a flashing ??? and battery icon is unsettling | 19:32 |
| minute | bkeys: that is old firmware | 19:33 |
| minute | bkeys: ??? means charge status in general is not known, it does not mean 1 battery is bad | 19:33 |
| minute | bkeys: the current firmware does not show this. | 19:33 |
| minute | i mean, it doesn't have blinking things | 19:33 |
| minute | your unit must have been sitting at mouser for a long time | 19:34 |
| minute | :D | 19:34 |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 19:41 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@static-198-54-135-37.cust.tzulo.com) | 19:43 | |
| + bkeys (~Thunderbi@static-198-54-135-37.cust.tzulo.com) | 19:43 | |
| bkeys | minute: No the battery itself is fine | 19:44 |
| bkeys | But I can remove the battery from where it shorted and the voltage stays the same regardless of it's being there | 19:44 |
| bkeys | So something must have gotten burnt when I shorted it. I think it looked like the spark and puff of smoke were under the heat sink | 19:45 |
| bkeys | But I even took the SoM off and I didn't see any scorch marks. You don't think this is possible for a person to fix with a soldering iron? I imagine what got burnt is a lot smaller than that | 19:45 |
| minute | bkeys: till next week, just remove all batteries and run on the power brick and update all firmware. then i can help you debug further | 19:46 |
| bkeys | Okay; is it your guess as well that something got physically damaged? | 19:48 |
| bkeys | And according to your sticker, mine is #204 | 19:51 |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 19:52 | |
| josch | bkeys: your problem reminds me of https://community.mnt.re/t/battery-issues-damaged-board/468 with this solution: https://community.mnt.re/t/isolating-battery-clips/962 | 20:03 |
| minute | bkeys: yeah, maybe a trace on battery board got burnt, that is easy to replace | 20:05 |
| - bkeys (QUIT: Ping timeout: 240 seconds) (~Thunderbi@static-198-54-135-37.cust.tzulo.com) | 20:08 | |
| + bkeys (~Thunderbi@253.236-24.gp.ptn.tftn.static.friendlycity.net) | 20:08 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 20:11 | |
| bkeys | Yeah I got the new firmware on there and the battery still shows up as missing. But at least it's not blinking at me anymore | 20:14 |
| bkeys | josch: Yeah if I had this fix this wouldn't have happened | 20:14 |
| bkeys | Except he was lucky, his battery board got broke; my carrier board is what is damaged I am pretty sure | 20:16 |
| bkeys | Cause I can swap the cables from each battery board around and the error is still there | 20:16 |
| josch | oh no... i really should apply this fix to my unit as well | 20:17 |
| bkeys | I'd suggest it. I should have unplugged the battery boards but for some reason I was concerned | 20:24 |
| bkeys | I flipped my carrier board over and I see no scorch marks there either | 20:24 |
| bkeys | ACTION shrugs | 20:24 |
| * mark_ -> mjw | 20:27 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@253.236-24.gp.ptn.tftn.static.friendlycity.net) | 20:38 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 20:38 | |
| + bkeys (~Thunderbi@253.236-24.gp.ptn.tftn.static.friendlycity.net) | 20:40 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 20:46 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 20:49 | |
| - bkeys (QUIT: Ping timeout: 246 seconds) (~Thunderbi@253.236-24.gp.ptn.tftn.static.friendlycity.net) | 20:52 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 21:01 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 21:17 | |
| + bkeys (~Thunderbi@253.236-24.gp.ptn.tftn.static.friendlycity.net) | 21:20 | |
| + aliosablack (~chomwitt@2a02:587:dc0e:3e00:bc0d:a683:e7e9:901) | 21:20 | |
| - chomwitt (QUIT: Ping timeout: 258 seconds) (~chomwitt@2a02:587:dc0e:3e00:bc0d:a683:e7e9:901) | 21:21 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 21:28 | |
| - bkeys (QUIT: Ping timeout: 246 seconds) (~Thunderbi@253.236-24.gp.ptn.tftn.static.friendlycity.net) | 21:35 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 21:39 | |
| + bkeys (~Thunderbi@253.236-24.gp.ptn.tftn.static.friendlycity.net) | 21:42 | |
| + bkeys1 (~Thunderbi@static-198-54-135-37.cust.tzulo.com) | 21:43 | |
| - bkeys (QUIT: Ping timeout: 258 seconds) (~Thunderbi@253.236-24.gp.ptn.tftn.static.friendlycity.net) | 21:46 | |
| * bkeys1 -> bkeys | 21:46 | |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 21:51 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 21:51 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@static-198-54-135-37.cust.tzulo.com) | 21:55 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 21:58 | |
| + bkeys (~Thunderbi@static-198-54-135-37.cust.tzulo.com) | 21:58 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 22:03 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 22:08 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 22:14 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 22:24 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 22:30 | |
| - littlebobeep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 23:01 | |
| - GNUmoon (QUIT: Ping timeout: 240 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon) | 23:20 | |
| + littlebobeep (~alMalsamo@gateway/tor-sasl/almalsamo) | 23:38 | |
| - aliosablack (QUIT: Ping timeout: 272 seconds) (~chomwitt@2a02:587:dc0e:3e00:bc0d:a683:e7e9:901) | 23:57 | |
| + chomwitt (~chomwitt@2a02:587:dc0e:3e00:bc0d:a683:e7e9:901) | 23:57 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!