| + mjw (~mjw@gnu.wildebeest.org) | 00:33 | |
| - mtm (QUIT: Ping timeout: 255 seconds) (~textual@47.202.75.129) | 01:04 | |
| - vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 01:05 | |
| + mtm (~textual@47.202.75.129) | 01:06 | |
| + bkeys (~Thunderbi@45.134.140.153) | 01:06 | |
| - chomwitt (QUIT: Ping timeout: 276 seconds) (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 01:09 | |
| - mjw (QUIT: Ping timeout: 260 seconds) (~mjw@gnu.wildebeest.org) | 01:17 | |
| + mjw (~mjw@gnu.wildebeest.org) | 01:24 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 01:51 | |
| + bkeys (~Thunderbi@45.134.140.153) | 01:51 | |
| - aloo_shu (QUIT: Ping timeout: 245 seconds) (~aloo_shu@90.166.98.209) | 01:55 | |
| - bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@45.134.140.153) | 01:56 | |
| + aloo_shu (~aloo_shu@90.166.98.209) | 02:05 | |
| + bkeys (~Thunderbi@45.134.140.153) | 02:20 | |
| - paperManu (QUIT: Ping timeout: 276 seconds) (~paperManu@107.159.243.8) | 02:54 | |
| - jn (QUIT: Ping timeout: 252 seconds) (~quassel@user/jn/x-3390946) | 02:56 | |
| + jn (~quassel@user/jn/x-3390946) | 02:57 | |
| - bkeys (QUIT: Ping timeout: 255 seconds) (~Thunderbi@45.134.140.153) | 03:06 | |
| + jn_ (~quassel@user/jn/x-3390946) | 03:09 | |
| - jn (QUIT: Ping timeout: 276 seconds) (~quassel@user/jn/x-3390946) | 03:09 | |
| - hairu (QUIT: Ping timeout: 260 seconds) (m-uotkmd@user/hairu) | 03:33 | |
| + hairu (m-uotkmd@user/hairu) | 03:46 | |
| - jn_ (QUIT: Ping timeout: 276 seconds) (~quassel@user/jn/x-3390946) | 03:53 | |
| + jn (~quassel@user/jn/x-3390946) | 03:53 | |
| - mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org) | 03:59 | |
| + jn_ (~quassel@2a0a-a549-fc5e-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de) | 06:40 | |
| - jn_ (QUIT: Changing host) (~quassel@2a0a-a549-fc5e-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de) | 06:40 | |
| + jn_ (~quassel@user/jn/x-3390946) | 06:40 | |
| - jn (QUIT: Ping timeout: 248 seconds) (~quassel@user/jn/x-3390946) | 06:41 | |
| + chomwitt (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 06:52 | |
| - jn_ (QUIT: Ping timeout: 260 seconds) (~quassel@user/jn/x-3390946) | 10:07 | |
| + jn (~quassel@user/jn/x-3390946) | 10:07 | |
| - chomwitt (QUIT: Ping timeout: 252 seconds) (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 11:25 | |
| ryukazou | minute: I facing some charging problem again, both my battery show 3.7 3.7 and battery percentage is 45%. Does this mean battery monitor is messed up again? | 12:13 |
|---|---|---|
| ryukazou | Do I need to drain all the battery to recalibrate the battery again? | 12:16 |
| ch | 3.7 is not full if its a pocket | 12:22 |
| ryukazou | Once the battery percentage reach 45% the charging drop to 0.05V | 12:24 |
| ryukazou | I’m not sure what happened | 12:24 |
| ryukazou | Okey new behaviour, when l plug charger into pocket, the oled will suddenly jump to 3.9 4.1 and charging is back to 1.07v, but after 30 second it will drop back to 3.7 3.7 and 0.05v. | 12:28 |
| ch | which voltage does the charger handshake? | 12:32 |
| ch | maybe try a different charger | 12:32 |
| + paperManu (~paperManu@107.159.243.8) | 12:34 | |
| ryukazou | ch: this is before plug into charger https://i.imgur.com/EJnClH0.jpeg | 12:37 |
| ryukazou | This is after https://i.imgur.com/tJaphD3.jpeg | 12:38 |
| ryukazou | After plug into the charger it become -1.09A | 12:41 |
| ryukazou | I have some typo in previous message, it should be A not V | 12:42 |
| ch | strange that the batteries report different voltages | 12:42 |
| ch | maybe thats why it tries slow charging | 12:43 |
| ryukazou | Does that mean I have faulty battery? | 12:43 |
| ch | dont know, sorry | 12:46 |
| + mjw (~mjw@gnu.wildebeest.org) | 12:47 | |
| ryukazou | minute: maybe you would have so ideal. | 12:47 |
| ryukazou | In the mean time I will try drain all the battery to see maybe it will fixed the problem. | 12:49 |
| minute | ryukazou: hmmmm it sounds like charger just stops charging but unclear why | 12:56 |
| ch | josch: re gcc-riscv64-unknown-elf #1086462 - did you see the O bug #1015208 ? (maybe just file the rm bug?) | 12:56 |
| josch | ch: ooooh that's how it works! tracker.d.o says "orphaned" in "action needed" but when i looked at d/control, it still has Keith as the maintainer | 12:58 |
| josch | i now see that it's the "O:" bug where the authoritative information comes from | 12:58 |
| ch | never trust any metadata anywhere ;( | 12:59 |
| ch | yeah | 12:59 |
| ch | as authoritative as it can be i guess | 12:59 |
| ryukazou | minute: battery report 3.4 and 3.2 right not but after plug into charger battery report 3.8 and 4.1 | 12:59 |
| ryukazou | Should I create a post on forums, maybe other has same experience. | 13:02 |
| minute | ryukazou: so -1.09A is a healthy charging current. but after 30 seconds that stops? | 13:02 |
| ryukazou | minute: yes | 13:02 |
| minute | ryukazou: when it stops does it immediately go to 3.7V or stay at 4.x for a while? | 13:02 |
| hramrach | I got cables that light up when PD is negotiated, and a charger that displays the negotiated parameters, and then I can tell if something is charging or not. Without that it's very difficult. The development snapshots of the sysctl firmware dump PD messages to a serial port so you could see the status there as well if you have that. | 13:02 |
| - mtm (QUIT: Ping timeout: 245 seconds) (~textual@47.202.75.129) | 13:02 | |
| + gustav28 (~gustav@c-78-82-54-68.bbcust.telenor.se) | 13:02 | |
| minute | yeah these PD monitoring usb cables with a little display are very useful ryukazou | 13:03 |
| ryukazou | minute: okey I will get one | 13:04 |
| + mtm (~textual@47.202.75.129) | 13:05 | |
| amospalla | ryukazou: my pocket has a combined voltage of 8.09v/100%, 7.10v/50%, 6.00v/0%. | 13:20 |
| ryukazou | amospalla: mine show 6.47V, the two battery icon show 3.4 and 3.2, battery is on 14% | 13:25 |
| amospalla | ryukazou: for me, 6.47V is at 3% . | 13:26 |
| amospalla | These values are from my pocket being new, after I calibrated it a few times. | 13:26 |
| amospalla | 14% -> 6.80V for me. | 13:27 |
| amospalla | https://paste.debian.net/1337270/ | 13:29 |
| - jn (QUIT: Ping timeout: 252 seconds) (~quassel@user/jn/x-3390946) | 13:29 | |
| + jn (~quassel@2001-4dd3-c765-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de) | 13:29 | |
| - jn (QUIT: Changing host) (~quassel@2001-4dd3-c765-0-20d-b9ff-fe49-15fc.ipv6dyn.netcologne.de) | 13:29 | |
| + jn (~quassel@user/jn/x-3390946) | 13:29 | |
| ryukazou | amospalla: this is machine on and didn’t plug into charger https://i.imgur.com/RyBCitj.jpeg | 13:32 |
| ryukazou | This is machine on and plug into charger https://i.imgur.com/kcNQ1D2.jpeg | 13:32 |
| amospalla | Have you tried doing one or two full charge-discharge cycles? | 13:33 |
| ryukazou | Done it once few days age | 13:34 |
| ryukazou | Ago | 13:35 |
| ryukazou | Everything still fine yesterday | 13:35 |
| amospalla | I dunno what may be happening then :/ | 13:35 |
| + bkeys (~Thunderbi@45.134.140.153) | 13:36 | |
| minute | ryukazou: can you make a close up photo of your charger board? there were a (low) number of boards where the charger IC developed an issue (but usually the device doesn't charge/turn on at all then) | 13:37 |
| ryukazou | I’m draining my battery right now to do charge-discharge cycle again, this is the only thing I could try before usb c pd monitor arrive tomorrow. | 13:38 |
| minute | ryukazou: ok! | 13:38 |
| ryukazou | minute: I will give you the photo one I got home, I didn’t bring my screwdriver out today. | 13:39 |
| - bkeys (QUIT: Ping timeout: 276 seconds) (~Thunderbi@45.134.140.153) | 14:14 | |
| + chomwitt (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 14:24 | |
| - aard (QUIT: Ping timeout: 260 seconds) (~bwachter@edna-edison.lart.info) | 14:40 | |
| + aard (~bwachter@217.11.60.132) | 14:49 | |
| - mjw (QUIT: Ping timeout: 246 seconds) (~mjw@gnu.wildebeest.org) | 14:54 | |
| * Guest6251 -> mjw | 15:11 | |
| + andreas-e (~Andreas@2001:861:c4:f2f0::c64) | 15:31 | |
| ryukazou | minute: the picture of my charging board https://i.imgur.com/5ROPsk5.jpeg | 16:09 |
| - kensanata (QUIT: Quit: Ping timeout (120 seconds)) (~alex@user/kensanata) | 16:44 | |
| - gustav28 (QUIT: Quit: Ping timeout (120 seconds)) (~gustav@c-78-82-54-68.bbcust.telenor.se) | 16:44 | |
| + kensanata (~alex@user/kensanata) | 16:44 | |
| + gustav28 (~gustav@c-78-82-54-68.bbcust.telenor.se) | 16:44 | |
| + tadeus_brick (tadeustad@psifactor.pl) | 16:44 | |
| - dodo (QUIT: Quit: dodo) (~dodo@user/dodo) | 16:45 | |
| + dodo (~dodo@user/dodo) | 16:45 | |
| - TadeusTaD (QUIT: Read error: Connection reset by peer) (tadeustad@user/TadeusTaD) | 16:46 | |
| + aloo_shu_ (~aloo_shu@85.51.16.96) | 17:10 | |
| minute | ryukazou: thanks, that looks ok! | 17:11 |
| - aloo_shu (QUIT: Ping timeout: 265 seconds) (~aloo_shu@90.166.98.209) | 17:12 | |
| * aloo_shu_ -> aloo_shu | 17:12 | |
| - chomwitt (QUIT: Ping timeout: 252 seconds) (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 17:13 | |
| - glu (QUIT: Ping timeout: 260 seconds) (~glu@91.141.35.187.wireless.dyn.drei.com) | 17:24 | |
| ryukazou | minute: I re-flash the firmware from August 26th and everything seem become fine, now my pocket reform can charge to 100% | 17:32 |
| minute | oh wow ok | 17:34 |
| minute | cc ch | 17:34 |
| minute | ryukazou: thanks for trying that! | 17:34 |
| ch | uhuh? | 17:34 |
| ch | ryukazou: which firmware did you have before? | 17:35 |
| ryukazou | Same firmware from August 26th | 17:35 |
| ryukazou | Not sure what fixed the problem, maybe discharging-charging cycle or re-flash the firmware. I done both. | 17:36 |
| ch | did you try a different charger btw? | 17:37 |
| + glu (~glu@91.141.63.216.wireless.dyn.drei.com) | 17:37 | |
| ch | i guess we need some way of dumping the charging/usb/... state out of sysctl thats not adhoc printf to get to these problems | 17:38 |
| ryukazou | No, I use the same power bank to charge my pocket reform while going home, it reach 100% when I got home | 17:38 |
| ch | ah power bank | 17:41 |
| ch | would be very interesting what voltage that gives | 17:41 |
| ryukazou | So originally my battery stuck at 45%, when I do the discharging the pocket reform actually shutdown when battery reach 1%, so I think my battery gauge is showing correctly. | 17:42 |
| ch | yeah i think you had a charging problem, not a gauge problem | 17:42 |
| ryukazou | I using this one https://www.amazon.com/Dell-PW7018LC-Notebook-Power-Bank/dp/B079GXGQPY?th=1 | 17:43 |
| ryukazou | Could overnight charging potentially be the problem | 17:44 |
| ch | Supported output 20 V, 3.25 A - 15 V, 3 A - 9 V, 3 A - 5 V, 3 A | 17:45 |
| ch | that should work at least | 17:45 |
| ryukazou | I do leave my pocket reform plugged for a day yesterday. | 17:46 |
| - paperManu (QUIT: Quit: WeeChat 4.1.1) (~paperManu@107.159.243.8) | 17:49 | |
| ryukazou | ch: do you need the information of my power bank from PD monitor? | 17:53 |
| ryukazou | I will post it after the PD monitor arrived | 17:54 |
| ch | ryukazou: yeah would be interesting, especially if you can get it into the broken state again | 17:55 |
| ryukazou | ch: okey I will leave my pocket reform plugged overnight | 17:56 |
| minute | i finally got the production pocket reform display v2s to work... i was pulling my hair over why they wouldn't work in pocket but on the vendor supplied hdmi adapter | 18:37 |
| minute | turns out there is some kind of eeprom in the display panels that is not programmed on the batch displays, but it was programmed on the proto | 18:37 |
| minute | i was lucky that many months ago i already extracted/converted a long init sequence that sets all those tables and i put that back into the driver and the display sprang to life | 18:37 |
| minute | also i found a way to identify the display in the driver via a mipi dcs command | 18:38 |
| minute | so we can have a unified panel driver. now i just need to make sysctl be as flexible and support brightness control creation in the reform2-lpc driver | 18:41 |
| spew | well done minute! | 18:43 |
| hramrach | \o/ | 18:52 |
| ch | oh nice | 18:56 |
| ch | minute: so it can be the same sysctl fw? | 18:57 |
| minute | ch: hopefully. i'm thinking of a way for the lpc driver to check which display model is active. for that i have to communicate between the two drivers somehow | 18:58 |
| minute | or userland has to turn on the backlight control in the lpc driver but that's not that elegant i guess | 18:58 |
| + mark_ (~mjw@gnu.wildebeest.org) | 18:59 | |
| minute | (for display v2, backlight is in the sysctl fw; for display v1, it is in the panel driver) | 18:59 |
| minute | right now what already works is that the panel driver's backlight control is only created on demand if the correct panel is recognized | 18:59 |
| ch | i wonder what the 'correct' way with the dtbs would be, but i have no idea | 19:00 |
| ch | ah but you'll have reform2-lpc act as a new backlight driver, if sysctl indicates it knows how to drive the backlight? | 19:02 |
| minute | i think the simplest semi-correct way would be to export a function from the panel driver (sth like mnt_pocket_reform_get_display_panel_version()) and use that in the lpc driver. i wonder if that could be weakly linked so it would be a nop if the panel driver is not there | 19:02 |
| ch | then you dont need to talk between both? | 19:02 |
| minute | ch: currently sysctl wouldn't need to know by itself which display is there | 19:02 |
| minute | sysctl-fw that is | 19:02 |
| ch | ah | 19:02 |
| minute | only lpc driver needs to learn this | 19:02 |
| hramrach | technically you could turn LPC driver into MFD and bind to a backlight definition in the fw somewhere | 19:03 |
| minute | the fw shouldn't be different for the 2 panels | 19:03 |
| hramrach | it does not have to be. The backlight function would be enabled only if the DT matches | 19:04 |
| hramrach | hm, but you probably do not want a separate DT either | 19:04 |
| minute | there wouldn't be a different dts either | 19:04 |
| minute | exactly | 19:04 |
| * mjw -> Guest9429 | 19:04 | |
| - Guest9429 (QUIT: Killed (iridium.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 19:04 | |
| * mark_ -> mjw | 19:04 | |
| minute | i want it to be as plug and play as possible | 19:04 |
| minute | i think i'll try a weak function to query the display version from lpc and implement the same function strongly in panel driver | 19:05 |
| ch | uboot could provide the DT and patch it on boot (please no) | 19:05 |
| minute | nono :D | 19:05 |
| + Guest9429 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 19:05 | |
| minute | i only need those 2 drivers to exchange 1 byte, that's the job | 19:05 |
| hramrach | aren't weak functions resolved at build time? | 19:06 |
| minute | yeah | 19:07 |
| minute | i would want it to be weak because lpc driver also has to work on non-pocket platforms | 19:07 |
| hramrach | and probe order is random so you cannot rely on the function to be available at LPC probe time | 19:09 |
| hramrach | you could depend on LPC from the display driver but it's out-of-tree | 19:09 |
| hramrach | maybe a reason to move it into the kernel :) | 19:10 |
| minute | i can use a sysfs attr | 19:11 |
| hramrach | It still hs the problem that if thre is no module dependency it may not be available | 19:15 |
| minute | not a big deal... brightness control will only be there if lpc module is loaded, otherwise not. and the panel driver is always compiled into the kernel, so it will always be there before lpc module probes | 19:15 |
| hramrach | it will be there but may not be probed | 19:16 |
| hramrach | BTW a Chinese clone https://www.crowdsupply.com/shenzhen-tianmao-technology/genbook-rk3588 :) | 19:18 |
| minute | yeah | 19:18 |
| minute | they even copied some of our blog post headlines in the first update post | 19:18 |
| minute | but i complained about that to CS and they got changed | 19:18 |
| minute | ah no the headlines are still there | 19:19 |
| minute | https://www.crowdsupply.com/shenzhen-tianmao-technology/genbook-rk3588/updates/using-the-genbook-rk3588 | 19:19 |
| minute | > Linux-y Stuff | 19:19 |
| minute | > GenBook RK3588 Goes to Work | 19:19 |
| minute | see also https://www.crowdsupply.com/mnt/pocket-reform/updates/pocket-reform-goes-to-work :D | 19:20 |
| hramrach | did not realize they went so far with the cloning | 19:22 |
| minute | well, maybe that's another aspect of open source!! | 19:22 |
| minute | it would be great if we also could just put money on the photocopier | 19:22 |
| minute | then i could take a little vacation... | 19:23 |
| hramrach | With SoMs available pretty much anyone can make their own notebook when they have access to the other parts, there is eg. https://www.clockworkpi.com/ | 19:25 |
| minute | sure, that's fine | 19:26 |
| hramrach | once somebody comes up with the idea and implements it it's clear it's doable. No need to directly plagiarize | 19:26 |
| minute | yeah that just feels weird | 19:27 |
| minute | ok i now have a file /sys/devices/platform/soc@0/32c00000.bus/32e60000.dsi/32e60000.dsi.0/mnt_pocket_reform_panel_version | 20:07 |
| minute | that contains a 2 for display version 2 | 20:07 |
| minute | now i need to investigate how to get a more platform-independent path to this | 20:07 |
| minute | /sys/bus/mipi-dsi/drivers/panel-jdi-lt070me05000/32e60000.dsi.0/mnt_pocket_reform_panel_version points to the same file | 20:09 |
| minute | ah, but drivers are not supposed to _access_ sysfs. | 20:18 |
| hramrach | Maybe make an udev script for this. It gets notifications when things are loaded or unloaded so it could copy that value from one file to another or something. In the kernel getting these notifications from a driver is unlikely to be pretty | 20:18 |
| minute | yeah | 20:18 |
| minute | we have reform-hw-setup. it could reload reform2-lpc with a module parameter if this file is found | 20:19 |
| minute | to clarify, the default brightness without any fw/driver support is 100% | 20:20 |
| minute | ok brightness control via lpc driver works | 21:12 |
| minute | if loaded with: insmod reform2-lpc.ko enable_backlight_control=1 | 21:13 |
| hramrach | I think udev rule would be good for this, it does not depend on random service starting, applies whenever the driver is loaded, even if the user reloads it for whatever reason | 21:15 |
| minute | hramrach: do you have some example how i could achieve that? i'm not very experienced with udev rules yet | 21:16 |
| minute | basically the logic is: | 21:16 |
| minute | if content of ./devices/platform/soc@0/32c00000.bus/32e60000.dsi/32e60000.dsi.0/mnt_pocket_reform_panel_version == 2 | 21:16 |
| minute | then modprobe reform2-lpc enable_backlight_control=1 | 21:17 |
| minute | (and rmmod reform2-lpc if already loaded) | 21:17 |
| hramrach | if it was not required to reload the lpc it would be easy | 21:17 |
| hramrach | with driver reload there is quite a bit of potential for endless udev loop | 21:18 |
| hramrach | I haven't seen the code so don't know how problematic it would be to change the value dynamically | 21:20 |
| hramrach | or if it would need to be changed at all, or if whatever LPC does for the backlight control it could do anyway with screen v1, just to no effect | 21:21 |
| - andreas-e (QUIT: Quit: Leaving) (~Andreas@2001:861:c4:f2f0::c64) | 21:33 | |
| digitalrane | is it possible to do that check in tge module? | 22:05 |
| digitalrane | *the | 22:05 |
| digitalrane | then the option could just be used to force enable it | 22:06 |
| - V (QUIT: Quit: No Ping reply in 180 seconds.) (~v@ircpuzzles/2022/april/winner/V) | 22:06 | |
| digitalrane | i guess tricky because the module is not bound to the panel, could get messy | 22:07 |
| + V (~v@ircpuzzles/2022/april/winner/V) | 22:08 | |
| - GNUmoon (QUIT: Ping timeout: 260 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon) | 22:08 | |
| - shdw (QUIT: Ping timeout: 255 seconds) (~shdw@static.218.156.216.95.clients.your-server.de) | 22:12 | |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-54-68.bbcust.telenor.se) | 22:15 | |
| minute | the sysctl's pwm brightness must not be used with display v1 because it would pwm that display's enable pin, causing it to turn off. if it was that simple i wouldn't have written here about the required mechanism. | 22:22 |
| ch | it all sounds like being between a rock and a hard place | 22:23 |
| minute | not at all from my pov, i'm happy that things are working finally | 22:24 |
| minute | just wanted to bounce around some ideas here | 22:25 |
| minute | the default behaviour is harmless too, full brightness and you just can't turn it down. and enabling the feature will give you the control | 22:25 |
| ch | nice | 22:26 |
| minute | i think toggling it via a sysfs attribute at runtime would also be possible | 22:26 |
| minute | i.e. not requiring module reload | 22:26 |
| + cobra_ (~cobra@user/Cobra) | 22:37 | |
| - cobra (QUIT: Ping timeout: 265 seconds) (~cobra@user/Cobra) | 22:37 | |
| ch | i need to dig into the kernel driver model one day and see how its parts are all supposed to work together | 22:45 |
| + chomwitt (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 22:45 | |
| midfavila | outta curiosity will the mnt reform mainboard ever be available for purchase in the shop? | 23:12 |
| josch | midfavila: "ever"? Sure, it was in the past: https://shop.mntre.com/products/mnt-reform-motherboard-25 | 23:14 |
| josch | so i guess future revisions will be sold that way as well -- i cannot think of a reason why they woudl not | 23:15 |
| midfavila | yeah i thought the old version had been but i didn't see it last i checked | 23:16 |
| midfavila | wasn't sure if i was misremembering or what | 23:16 |
| midfavila | i'm desperate to get a replacement mainboard so i can use my reform again instead of my old x86 laptop ;w; | 23:17 |
| josch | midfavila: what continent are you on? | 23:20 |
| digitalrane | minute, i was just offering another perspective | 23:21 |
| midfavila | josch, NA | 23:22 |
| josch | midfavila: i'm in germany -- i could've sold you mine but shipping will be steep... | 23:23 |
| midfavila | yeah | 23:23 |
| midfavila | i'm just waiting on a warranty is all. it's hard to be patient ;w; | 23:23 |
| josch | midfavila: me too, that's why i have a spare motherboard :D | 23:29 |
| - nsc (QUIT: Ping timeout: 255 seconds) (~nicolas@i5C74DF9D.versanet.de) | 23:31 | |
| + nsc (~nicolas@i5C74DF51.versanet.de) | 23:33 | |
| midfavila | fair | 23:33 |
| midfavila | i'm hoping to move to europe in a few years so maybe then i'll be able to go to berlin myself instead of getting everything shipped | 23:33 |
| josch | \o/ | 23:36 |
| midfavila | i'll finally be able to experience the archaeotech known as "passenger trains" | 23:38 |
| midfavila | can't wait | 23:38 |
| josch | :D | 23:40 |
| josch | trains are awesome | 23:40 |
| midfavila | theyre pretty cool | 23:40 |
| midfavila | i just wish canada had a functional train network | 23:40 |
| josch | me and my reform will be in one for 4 hours tomorrow :) | 23:41 |
| midfavila | it takes 18 hours best case to travel 400km from one major city to another and costs 100$ for the cheapest fare | 23:41 |
| midfavila | ACTION dies | 23:41 |
| midfavila | can't even bring a bike with you or anything | 23:42 |
| + paperManu (~paperManu@107.159.243.8) | 23:53 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
