| vkoskiv_ | Any known issues at the moment or should I try to look for one? No repro steps yet. I think it has to do with me having it on a charger, turning it on and then leaving it for a while. Not sure. | 00:00 |
|---|---|---|
| vkoskiv_ | I'll try clicking the kbd reset with a toothpick | 00:00 |
| vkoskiv_ | I can see it in there from the gap | 00:00 |
| vkoskiv_ | reset button didn't do a thing. Last time pulling charger and batteries fixed it | 00:01 |
| vkoskiv_ | Just noticed - haven't looked at schematic yet, two legs on my LTC power measurement chip are bridget. On the not-pin-1 side. | 00:02 |
| + Gooberpatrol_66 (~Gooberpat@user/gooberpatrol66) | 00:03 | |
| + patrick_ (224fa09e8b@2604:bf00:561:2000::217) | 00:03 | |
| + conky_ (5fb0fe5593@2604:bf00:561:2000::10b) | 00:03 | |
| + yankcrim- (~nick@agrajag.dischord.org) | 00:04 | |
| + jfred_ (sid534649@libera/sponsor/jfred) | 00:04 | |
| + nocko_ (sid501219@id-501219.helmsley.irccloud.com) | 00:04 | |
| + eschaton_ (~eschaton@li541-49.members.linode.com) | 00:04 | |
| + jfred-linode_ (quassel@libera/sponsor/jfred) | 00:05 | |
| + Asmadeus_ (~asmadeus@240b:13:8c80:d300:e:98c:8000:d300) | 00:06 | |
| + sbp_ (~sbp@2001:19f0:6800:1102:5400:ff:fe11:39a1) | 00:06 | |
| + leonardo1 (~leonardo@user/leonardo) | 00:06 | |
| + sinedeo_ (~sinedeo@2a01:4f9:c010:2837::1) | 00:06 | |
| + jnerula_ (~jnerula@li1009-93.members.linode.com) | 00:07 | |
| + swivel_ (~swivel@shells.gnugeneration.com) | 00:07 | |
| - eschaton (QUIT: Ping timeout: 250 seconds) (eschaton@2600:3c01::f03c:91ff:fefd:5d92) | 00:07 | |
| - nocko (QUIT: Ping timeout: 250 seconds) (sid501219@user/nocko) | 00:07 | |
| - scops (QUIT: Ping timeout: 250 seconds) (~scopstchn@2001:470:69fc:105::8da) | 00:07 | |
| - patrick (QUIT: Ping timeout: 250 seconds) (224fa09e8b@fsf/member/patrick) | 00:07 | |
| - leonardo (QUIT: Ping timeout: 250 seconds) (~leonardo@user/leonardo) | 00:07 | |
| - Asmadeus (QUIT: Ping timeout: 250 seconds) (~asmadeus@240b:13:8c80:d300:e:98c:8000:d300) | 00:07 | |
| - swivel (QUIT: Ping timeout: 250 seconds) (~swivel@shells.gnugeneration.com) | 00:07 | |
| - jfred (QUIT: Ping timeout: 250 seconds) (sid534649@libera/sponsor/jfred) | 00:07 | |
| - conky (QUIT: Ping timeout: 250 seconds) (5fb0fe5593@2604:bf00:561:2000::10b) | 00:07 | |
| - sinedeo (QUIT: Ping timeout: 250 seconds) (~sinedeo@2a01:4f9:c010:2837::1) | 00:07 | |
| - jfred-linode (QUIT: Ping timeout: 250 seconds) (quassel@libera/sponsor/jfred) | 00:07 | |
| - jnerula (QUIT: Ping timeout: 250 seconds) (~jnerula@li1009-93.members.linode.com) | 00:07 | |
| - Gooberpatrol66 (QUIT: Ping timeout: 250 seconds) (~Gooberpat@user/gooberpatrol66) | 00:07 | |
| - sbp (QUIT: Ping timeout: 250 seconds) (~sbp@apache/doge/sbp) | 00:07 | |
| - yankcrime (QUIT: Ping timeout: 250 seconds) (~nick@agrajag.dischord.org) | 00:07 | |
| * conky_ -> conky | 00:07 | |
| * jfred_ -> jfred | 00:07 | |
| * leonardo1 -> leonardo | 00:07 | |
| + scops (~scopstchn@2001:470:69fc:105::8da) | 00:18 | |
| - mjw (QUIT: Quit: Leaving) (~mark@gnu.wildebeest.org) | 00:22 | |
| * Asmadeus_ -> Asmadeus | 00:23 | |
| - S0rin (QUIT: Ping timeout: 276 seconds) (~S0rin@user/s0rin) | 00:24 | |
| + S0rin (~S0rin@user/s0rin) | 00:28 | |
| - Gooberpatrol_66 (QUIT: Quit: Leaving) (~Gooberpat@user/gooberpatrol66) | 00:33 | |
| * sbp_ -> sbp | 00:36 | |
| - sbp (QUIT: Changing host) (~sbp@2001:19f0:6800:1102:5400:ff:fe11:39a1) | 00:36 | |
| + sbp (~sbp@apache/doge/sbp) | 00:36 | |
| josch | vkoskiv_: sounds like this: https://community.mnt.re/t/power-issues-and-lpc-wakeup/596 | 00:45 |
| josch | I've had the same effect two days ago for the first time -- only plugging the batteries fixed it | 00:45 |
| minute | one person had a proposed patch for it | 00:53 |
| * nocko_ -> nocko | 00:58 | |
| josch | since i don't understand https://source.mnt.re/reform/reform/-/merge_requests/26 and since this problem happened to me so rarely, i wanted to wait until it got official blessing by getting merged before trying this out -- i might change my mind in case this happens to me more often :) | 01:11 |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 01:13 | |
| - Gooberpatrol66 (QUIT: Ping timeout: 258 seconds) (~Gooberpat@user/gooberpatrol66) | 01:45 | |
| + Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 01:52 | |
| - GNUmoon (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 02:00 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 02:01 | |
| - mtm (QUIT: Ping timeout: 256 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 02:02 | |
| Asmadeus | I guess the warning to not fiddle with wdt from interrupt context sort of make sense, but that sleep being required (according to forum post) is quite weird... | 02:04 |
| - Christoph_ (QUIT: Remote host closed the connection) (~Christoph@p54bf616b.dip0.t-ipconnect.de) | 02:18 | |
| * swivel_ -> swivel | 03:16 | |
| - klardotsh (QUIT: Ping timeout: 240 seconds) (~klardotsh@172.56.104.60) | 03:39 | |
| + bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 03:44 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 03:57 | |
| + bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 03:57 | |
| + mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 04:08 | |
| flowy | minute: oh, that's cool. i would order a reform trad layout keyboard, for sure! i'm not a fan of the current stagger, however i am definitely a fan of making compromises so that we actually have nice things and they don't simply remain pipe dreams forever :) | 04:26 |
| flowy | i tried fps gaming with the standalone keyboard and the stagger actually causes finger pain on WASD keys (arrow formation...). it really illustrates the ergonomic compromise | 04:28 |
| flowy | direct diagonal combos can be painful basically | 04:29 |
| flowy | anyways i still like the reform keyboard | 04:50 |
| flowy | it's got character | 04:50 |
| - bkeys (QUIT: Ping timeout: 256 seconds) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 04:55 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 06:50 | |
| + littlebo1eep (~alMalsamo@gateway/tor-sasl/almalsamo) | 07:34 | |
| - littlebo1eep (QUIT: Ping timeout: 240 seconds) (~alMalsamo@gateway/tor-sasl/almalsamo) | 08:09 | |
| + MajorBiscuit (~MajorBisc@c-001-020-042.client.tudelft.eduvpn.nl) | 09:11 | |
| Boostisbetter | have you ever used and orthogonal layout keyboard? The Moonlander I use on my desktop is the most comfortable keyboard I have ever used. | 10:11 |
| Boostisbetter | I find the keyboard on the Reform to be very good though. | 10:11 |
| Boostisbetter | one of my favorite parts of the keyboards is the display. I love that you can check battery status and have an on and off switch that are all independent from the OS. | 10:14 |
| * mark -> mjw | 11:32 | |
| + Christoph_ (~Christoph@p54bf6030.dip0.t-ipconnect.de) | 12:24 | |
| - mjw (QUIT: Quit: Leaving) (~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440) | 12:48 | |
| - MajorBiscuit (QUIT: Ping timeout: 272 seconds) (~MajorBisc@c-001-020-042.client.tudelft.eduvpn.nl) | 13:01 | |
| + MajorBiscuit (~MajorBisc@2a02-a461-129d-1-193d-75d8-745d-e91e.fixed6.kpn.net) | 13:03 | |
| + mjw (~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440) | 13:06 | |
| flowy | i've only tried ortholinear layouts briefly. i appreciate the aesthetic, but i'm not sold yet on the ergonomics. i've only seen anecdotal claims that swing either way in regards to whether they help RSI. i'm wary of investing energy into learning another layout if the benefits are unclear | 13:35 |
| flowy | i suffer from light RSI and had a couple bad periods, fortunately i found various things that work for me before going deep into alternative keyboard layouts. | 13:39 |
| flowy | but moonlander and other keyboards from that company look very cool! | 13:41 |
| flowy | i'm not particularly interested in the pocket reform personally, again for ergonomics. i'm wary of devices that small, particularly for eye strain. but i guess i don't have a particular use for it. the reform's size is pretty good for me as a functional portable computer. could just be a bit slimmer | 13:44 |
| flowy | i'm a big fan of high DPI screens + big fonts :) | 13:45 |
| flowy | for me more pixels mean better type, not more space | 13:45 |
| flowy | the pocket reform sounds really cool though and i wish i did have some use for it heh | 13:47 |
| flowy | lots of time to think of a reason | 13:47 |
| - mtm (QUIT: Ping timeout: 240 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 14:02 | |
| - MajorBiscuit (QUIT: Ping timeout: 248 seconds) (~MajorBisc@2a02-a461-129d-1-193d-75d8-745d-e91e.fixed6.kpn.net) | 14:03 | |
| + MajorBiscuit (~MajorBisc@c-001-030-042.client.tudelft.eduvpn.nl) | 14:05 | |
| vkoskiv_ | I'm a fan of the stock reform keyboard. I didn't find it difficult to adjust to the layout. The only thing that still occasionally trips me up is hitting return when I meant to hit ', and hitting the up arrow when going for rshift. | 14:28 |
| vkoskiv_ | The first issue is just the ansi/horizontal return, which I'm not used to. All euro layouts I've used before have a vertical return. | 14:29 |
| vkoskiv_ | The only thing I don't like is the deck flex in the bottom centre of the board. I'm thinking about modeling a little bracket that would grab onto the edge of the PCB and brace against the acrylic bottom cover. Been a while since I've used CAD, though. | 14:29 |
| vkoskiv_ | Like an F-shape bracket, but with a wide base that then sits against the acrylic cover when closed. Possibly with some interface material to prevent scratching over time. | 14:30 |
| flowy | yeah that's a good idea | 14:38 |
| vkoskiv_ | I have... *a* 3D printer. It's a bit of a crusty one, I built it in 2016. | 14:46 |
| + bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 14:52 | |
| vkoskiv_ | Another firmware idea: When hitting circle+0, if the system is on, first send acpi shutdown signal to linux, and then only force shutdown after some timeout interval (tbd) | 15:44 |
| vkoskiv_ | Would that make sense? Seems more gentle than a forced shutdown. Then there could be a key combo to force the shutdown | 15:45 |
| vkoskiv_ | Alternatively, just a quick "you sure?" check for the shutdown cmd. Would be simpler. | 15:45 |
| vkoskiv_ | What is gsd-xsettings? Some gnome settings daemon? Do I need it? It's using up a bunch of ram. | 16:07 |
| + mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 16:09 | |
| sl | kfx: vkoskiv_: i eventually made my image board single user (me) after repeated and persistent invasions | 16:13 |
| vkoskiv_ | Yeah. Mine's just so unknown that I'm the only semi-active user | 16:15 |
| vkoskiv_ | I can disable registrations if I want. Or make them approve-only. | 16:16 |
| vkoskiv_ | I don't understand why anything from gnome-settings-daemon is running when I'm not using gnome. I'm just running sway. | 16:16 |
| vkoskiv_ | I'm comparing this to my arch setup, which had none of that stuff running. I'm used to it taking up <100MB of memory when booted up with no sway session running. | 16:17 |
| vkoskiv_ | 82MB of RAM seems like a ton for a single settings daemon to be using, IMO :D | 16:17 |
| vkoskiv_ | I'd love to know what it's doing with that memory. | 16:18 |
| * vkoskiv_ -> vkoskiv | 16:21 | |
| Boostisbetter | just had a weird wifi bug for the first time. When I resumed it came back up, but wifi did not. When looking through the connection wifi wasn't even an option. I slept the Reform again and woke it shortly thereafter and wifi was back. I guess the wifi card just took a little too long on resume and the kernel ignored it. | 16:42 |
| vkoskiv | Speaking of resume, it still fails 100% of the time for me | 16:44 |
| vkoskiv | I just get 'no response from lpc' every time | 16:44 |
| Boostisbetter | oh, since upgrading I have had really reliable standby and resume action. | 16:45 |
| Boostisbetter | It works REALLY well. | 16:45 |
| Boostisbetter | So much so that when it occasionally does not, I have no problem just quickly setting everything back up in my session. | 16:45 |
| vkoskiv | I don't think it's a software issue in my case, the firmware probably doesn't even send the wake up signal to the system | 16:51 |
| vkoskiv | I'm running the latest firmware on both kbd and lpc though, so not sure why my particular case doesn't work | 16:51 |
| vkoskiv | I'm also running that little patch I made, but that doesn't affect this. | 16:52 |
| - GNUmoon (QUIT: Ping timeout: 240 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon) | 17:04 | |
| + GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) | 17:18 | |
| - mjw (QUIT: Quit: Leaving) (~mjw_@2001:1c06:2488:1400:9e5c:8eff:fe8f:a440) | 17:21 | |
| + mjw (~mark@gnu.wildebeest.org) | 17:51 | |
| - MajorBiscuit (QUIT: Quit: WeeChat 3.5) (~MajorBisc@c-001-030-042.client.tudelft.eduvpn.nl) | 18:34 | |
| bkeys | josch: So something I have been thinking about is, it shouldn't matter that my Reform doesn't boot debian since I am trying to boot Fedora anyway. But I realized, that the image I am booting does not have any reference to distroboot, do you have any clue why that is? | 20:00 |
| bkeys | Does your image have your distroboot changes? | 20:01 |
| + klardotsh (~klardotsh@98.97.119.207) | 20:11 | |
| josch | bkeys: no, you have to build your own uboot from the main branch | 20:12 |
| josch | bkeys: the current sysimage-v3 uses the v3 tag of u-boot and the distroboot stuff came afterwards | 20:12 |
| josch | it might still matter that you cannot boot debian because this hints at that something doesn't work as you expect it to which will make booting fedora harder because you don't have a working setup to start from | 20:13 |
| josch | bkeys: I verified that this one works: wget -O flash.bin https://source.mnt.re/reform/reform-boundary-uboot/-/jobs/artifacts/master/raw/flash.bin\?job\=build | 20:39 |
| - TadeusTaD (QUIT: Quit: Stay Cheeki Breeki) (tadeustad@psifactor.pl) | 21:06 | |
| + TadeusTaD (tadeustad@2a01:4f8:13b:288c::2) | 21:28 | |
| bkeys | Okay well that at least makes sense then. | 21:40 |
| bkeys | josch: Do you have a full system image somewhere that does use the distroboot stuff? I agree, I'd like to at least have a working system. | 21:41 |
| josch | bkeys: you can just combine the latest working sysimage-v3 with more recent u-boot -- would you like me to do that for you or tell you how to do it? | 21:42 |
| josch | (the first version would have the advantage that i could test the exact same image to make sure that it boots for me) | 21:43 |
| bkeys | My guess is that it basically is that the first 8 megabytes (or so) already have the non-distroboot uboot on there, I flash this and the rest of the debian image should "just work" | 21:44 |
| bkeys | Basically I dd the flash.bin you just sent to the front of the SD card | 21:44 |
| bkeys | Hopefully it works... | 21:44 |
| josch | you have to dd it with the correct offset | 21:45 |
| josch | dd if=flash.bin of=/dev/mmcblk0 conv=notrunc bs=1k seek=33 | 21:45 |
| bkeys | Booting... | 21:51 |
| bkeys | Nothing on the screen so far. | 21:51 |
| josch | bkeys: did you manage to get hold of a serial adapter or a hdmi screen? | 21:53 |
| bkeys | No it's in the other room; let me go get it | 21:53 |
| bkeys | josch: Bad Linux ARM64 Image Magic! | 22:22 |
| bkeys | There is no reference to distroboot in the printenv either | 22:23 |
| josch | u-boot tells you that? | 22:23 |
| bkeys | Yes | 22:23 |
| josch | one sec, lets make sure we are both using the same thing -- i'll prepare something | 22:23 |
| bkeys | Oh wait... I am on emmc, I was on SD at the beginning of this convo | 22:24 |
| bkeys | I mean I didn't have it working then either | 22:24 |
| bkeys | Neither of them reference uboot cause I tried it on both | 22:25 |
| bkeys | *neither of them reference distroboot | 22:27 |
| josch | bkeys: you are printing your environment by accessing your u-boot via serial? | 22:30 |
| - erle (QUIT: Ping timeout: 240 seconds) (~erle@ip5f5af7b3.dynamic.kabel-deutschland.de) | 22:30 | |
| bkeys | Yes | 22:32 |
| bkeys | sudo minicom -D /dev/ttyUSB0 | 22:32 |
| bkeys | Then I run | 22:32 |
| bkeys | => printenv | 22:32 |
| bkeys | ERROR: invalid device tree | 22:33 |
| bkeys | ERROR: failed to install device tree | 22:33 |
| josch | nice, having serial will make this much easier :) | 22:33 |
| bkeys | That is the error I get when I boot | 22:33 |
| bkeys | From SD card | 22:33 |
| josch | can you show me the full log from u-boot? | 22:33 |
| bkeys | Which it's trying to read from mmc 0 and the SD card is mmc 1 so I see why it says that | 22:33 |
| bkeys | Sure | 22:33 |
| bkeys | I see what's happening but I have no clue how that is true | 22:35 |
| bkeys | https://paste.centos.org/view/a82a23f7 | 22:36 |
| bkeys | josch: It still has all my changes from when I tried to load Fedora on here a few days ago? | 22:36 |
| bkeys | But I have flashed this thing so many times | 22:36 |
| bkeys | And i know it is loading Uboot from the SD card, because if I remove the SD card I get no serial output | 22:36 |
| bkeys | I am gonna grab a totally fresh SD card | 22:37 |
| josch | bkeys: this is definitely the wrong uboot | 22:38 |
| josch | this is ancient uboot from before sysimage-v3 | 22:38 |
| kfx | don't uboot-shame bkeys | 22:40 |
| josch | sorry XD | 22:40 |
| bkeys | I agree haha | 22:42 |
| josch | here is what I do to produce a working sysimage-v3 sd-card with most recent u-boot including distro_bootcmd: | 22:43 |
| bkeys | But I don't know why it won't update no matter what | 22:43 |
| josch | wget https://source.mnt.re/reform/reform-system-image/-/jobs/793/artifacts/raw/reform2-imx8mq/reform-rescue-system.img.gz | 22:43 |
| josch | zcat reform-rescue-system.img.gz | sudo dd of=/dev/mmcblk0 bs=10M status=progress | 22:43 |
| josch | wget https://source.mnt.re/reform/reform-boundary-uboot/-/jobs/809/artifacts/raw/flash.bin | 22:43 |
| josch | sudo dd if=flash.bin of=/dev/mmcblk0 conv=notrunc bs=1k seek=33 | 22:43 |
| josch | I just did this for my sd-card and it boots from it as expected | 22:43 |
| josch | if that does not work for you, we really have to look elsewhere for the problem | 22:44 |
| bkeys | I will do those things exactly, and if it doesn't update i will just get a new SD card | 22:46 |
| josch | i assume you are still using the one that was shipped with your reform? | 22:46 |
| bkeys | Yes | 22:46 |
| josch | okay, good | 22:47 |
| josch | minute: recently I was talking about switching the CI backend now that creating a sysimage-v3 doesn't require root privileges anymore. To test my theory, I just attempted running mkimage.sh on the Debian gitlab CI and this failed because the docker CI runner doesn't support binfmt_misc to emulate arm64 via qemu. I have no idea about docker or gitlab CI but I guess this is something to keep in mind when | 22:56 |
| josch | choosing another CI runner. The internet says binfmt_misc can work with docker if run with --privileged. | 22:56 |
| bkeys | josch: Okay I did your list of commands, and if that doesn't work I will use a whole new SD card | 23:04 |
| bkeys | josch: Same stuff, no changes to printenv | 23:05 |
| bkeys | I'm gonna blame the SD card at the moment | 23:05 |
| klardotsh | josch: I've done GitLab CI to x-compile aarch64 docker images before (used binfmt_misc under the hood), worked great. some good reading in the space: https://blog.56k.cloud/building-docker-multi-arch-images-with-gitlab-cicd/ | 23:06 |
| + tadeus_brick (tadeustad@psifactor.pl) | 23:10 | |
| josch | klardotsh: as a noob in that area, this article confuses me. Is this article not suggesting to build a docker image for each architecture you need? | 23:11 |
| bkeys | Okay, I put in a totally new SD card and now my printenv is printing out nothing | 23:14 |
| bkeys | I wish this thing would just work... | 23:15 |
| josch | bkeys: this is super odd... if your cpu module would somehow get u-boot from emmc you would at least see some output on serial | 23:15 |
| bkeys | If I try to run something like ls mmc 0 it reboots | 23:15 |
| bkeys | Yes | 23:15 |
| bkeys | I get serial output on this new SD card | 23:16 |
| josch | how can you run something like ls mmc 0 if it prints nothing? | 23:16 |
| bkeys | printenv prints nothing | 23:16 |
| josch | ah so you are in uboot? | 23:16 |
| bkeys | Yes | 23:16 |
| bkeys | But if I run ls mmc 0 it resets | 23:16 |
| josch | your uboot output looks like it comes from emmc | 23:17 |
| josch | it cannot come from your sd-card | 23:17 |
| josch | how certain are you, that your dip-switch is indeed set to ON? | 23:17 |
| bkeys | Well if I remove the SD card I get no serial output at all | 23:17 |
| josch | i don't know why that happens but the u-boot output you see cannot come from the u-boot version i linked to above | 23:18 |
| josch | does your dip switch look like this: https://source.mnt.re/reform/reform-handbook/uploads/6e7a46b06df43e788f705b783bd46c15/17e7457e179e68e3c74ab15fb2b47e3ab8f2945d.jpeg | 23:19 |
| bkeys | It's on ON | 23:20 |
| bkeys | So no | 23:21 |
| josch | damn :/ | 23:21 |
| josch | i'm out of ideas then | 23:21 |
| josch | i have no explanation for why you see what you are seeing | 23:21 |
| josch | sorry :( | 23:21 |
| bkeys | Maybe the best thing to do would be send it back? I know you guys are really busy as is | 23:23 |
| bkeys | But I already have the battery issue, I just don't know what to do at this point | 23:23 |
| bkeys | It'd be nice to have it repaired and maybe having it in your guys's hands would help | 23:23 |
| josch | minute: ^ | 23:24 |
| bkeys | I'd be willing to pay for shipping both ways | 23:24 |
| minute | bkeys: sure, please contact support@mntre.com | 23:43 |
| + erle (~erle@ip5f5af7b3.dynamic.kabel-deutschland.de) | 23:55 | |
| - bkeys (QUIT: Ping timeout: 276 seconds) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 23:58 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
