- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 00:26 | |
+ yankcrime (~nick@gw.tetromino.io) | 00:27 | |
- Ar|stote|is (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.8.17) | 02:17 | |
+ Ar|stote|is (~linx@149.210.8.17) | 02:18 | |
- mjw (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org) | 02:52 | |
- XYZ (QUIT: Ping timeout: 246 seconds) (~XYZ@37-48-16-253.nat.epc.tmcz.cz) | 03:02 | |
+ XYZ (~XYZ@37-48-16-253.nat.epc.tmcz.cz) | 03:03 | |
- nsc (QUIT: Ping timeout: 245 seconds) (~nicolas@86-97-142-46.pool.kielnet.net) | 03:32 | |
+ nsc (~nicolas@149-96-142-46.pool.kielnet.net) | 03:34 | |
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-159-4.tukw.qwest.net) | 04:10 | |
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net) | 04:12 | |
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-159-4.tukw.qwest.net) | 04:21 | |
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net) | 04:23 | |
- GNUmoon2 (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 06:08 | |
+ GNUmoon2 (~GNUmoon@gateway/tor-sasl/gnumoon) | 06:08 | |
- eibachd (QUIT: Ping timeout: 264 seconds) (~eibachd@p200300dcf7231c00b05deb04abf7a856.dip0.t-ipconnect.de) | 07:05 | |
+ eibachd (~eibachd@2a01:599:305:65f5:8bfe:cafd:e386:1480) | 07:06 | |
- brennen (QUIT: Ping timeout: 268 seconds) (~brennen@user/brennen) | 08:41 | |
- arminweigl (QUIT: Ping timeout: 256 seconds) (~arminweig@sourcehut/user/arminweigl) | 08:50 | |
- jagtalon (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@user/jagtalon) | 08:50 | |
+ arminweigl (~arminweig@sourcehut/user/arminweigl) | 08:50 | |
+ jagtalon (~quassel@user/jagtalon) | 08:51 | |
+ brennen (~brennen@user/brennen) | 08:55 | |
- arminweigl (QUIT: Ping timeout: 264 seconds) (~arminweig@sourcehut/user/arminweigl) | 09:10 | |
+ arminweigl_ (~arminweig@sourcehut/user/arminweigl) | 09:10 | |
* arminweigl_ -> arminweigl | 09:10 | |
- bluerise (QUIT: Read error: Connection reset by peer) (~bluerise@user/bluerise) | 09:14 | |
+ bluerise_ (~bluerise@p5b0acf0d.dip0.t-ipconnect.de) | 09:14 | |
josch | i fixed my switch again \o/ | 11:01 |
---|---|---|
josch | after de-soldering it and opening it up, it became clear that a teensy tiny bit of dirt jammed itself into the slot where one of the levers has to slide in, such that when the key is pressed all the way down, the lever would be pushed out again as if the key was not pressed | 11:02 |
josch | if one knows what to look for, this could've even be cleaned up without de-soldering | 11:02 |
josch | one would just have to remove a couple more keycaps to be able to reach the slot with a very thin needle | 11:03 |
josch | 4444444444444444444444444444444444 | 11:03 |
josch | it repeats again :) | 11:03 |
+ minutepocket (~minute@tmo-085-2.customers.d1-online.com) | 11:35 | |
- minutepocket (QUIT: Ping timeout: 268 seconds) (~minute@tmo-085-2.customers.d1-online.com) | 11:41 | |
+ minutepocket (~minute@tmo-087-121.customers.d1-online.com) | 11:42 | |
- minutepocket (QUIT: Ping timeout: 264 seconds) (~minute@tmo-087-121.customers.d1-online.com) | 11:59 | |
+ minutepocket (~minute@p509936c9.dip0.t-ipconnect.de) | 12:11 | |
minute | josch: nice switch repair | 12:20 |
- minutepocket (QUIT: Quit: Lost terminal) (~minute@p509936c9.dip0.t-ipconnect.de) | 12:35 | |
josch | well... "repair" more like "cleaning" :D | 12:45 |
josch | i'm happy that de-soldering and re-soldering worked without much of a fuss | 12:45 |
josch | minute: about the battery shutdown issue that jeff geerling experienced. Do you agree with the theory that the lpc "thought" the batteries were empty because it didn't get to learn what 0% means and thus the software switched off the system long before it was actually dead? | 12:46 |
josch | The problem then is, that with the software switching everything off early, the system will never learn the true 0% | 12:46 |
josch | would it make sense to lower the default voltage that lpc interprets as 0% a lot so that the first time round, the system will just "die" and thus the lpc learn the true 0% and the next time the software can switch it off safely? | 12:47 |
- eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:305:65f5:8bfe:cafd:e386:1480) | 12:49 | |
+ eibachd (~eibachd@p200300dcf7231c0004a1fc2cd3ce3e50.dip0.t-ipconnect.de) | 12:49 | |
- klardotsh (QUIT: Ping timeout: 264 seconds) (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net) | 12:50 | |
minute | josch: yes, i think most of the problems in the review were caused by GNOME | 12:52 |
josch | in my case, i disabled soft-shutdown i have configured in /etc/UPower/UPower.conf, then let the system die by itself, then enabled it in /etc/UPower/UPower.conf again | 12:55 |
josch | but that would not be necessary if the default 0% was lowered -- would such a change have any risk? I think it would also make sense for non-gnome users (for example when people use upower). | 12:56 |
+ mjw (~mjw@gnu.wildebeest.org) | 12:58 | |
minute | josch: there's no risk if you have protected battery boards | 13:03 |
josch | right, that makes sense :) | 13:04 |
josch | so probably not a change you'd like to roll out for everybody | 13:04 |
josch | oh interesting, the voltage values depend on REFORM_MOTHERBOARD_REV | 13:06 |
josch | minute: is the capacity_min_ampsecs variable the one i want to change? | 13:08 |
minute | josch: i would like to rework this code and remove capacity_min_ampsecs | 13:10 |
minute | josch: it's overcomplicated. there really should only be max_ampsecs and it's like an account where ampsecs are added and removed | 13:10 |
minute | i mean, max_ampsecs is the estimated capacity | 13:11 |
minute | and min_ampsecs should be replaced by 0 | 13:11 |
josch | okay! i guess then finish the pocket stuff first and come back to this once you find more head-space for tiny issues like these :) | 13:12 |
- eibachd (QUIT: Ping timeout: 268 seconds) (~eibachd@p200300dcf7231c0004a1fc2cd3ce3e50.dip0.t-ipconnect.de) | 13:12 | |
+ eibachd (~eibachd@p200300dcf7231c007222c86f87cd63cb.dip0.t-ipconnect.de) | 13:12 | |
minute | josch: yep! | 13:13 |
minute | josch: btw i might have a different solution for the charger-hiccup-thing | 13:13 |
minute | josch: i was annoyed by the slow charging and the buzzing of the pwm-style hack | 13:13 |
minute | josch: so what i did is i implemented a timer that lets charging start only after a few seconds after connecting the charger | 13:13 |
josch | haha best way to find solutions is to get annoyed at the status-quo :) | 13:14 |
josch | oh i'd like to try that! | 13:14 |
minute | for me this made the hiccups go away, but i will test a bit longer | 13:14 |
minute | i can send you the patch anyway | 13:14 |
josch | sure! :) | 13:14 |
josch | my usb-pd adapters are at home, so i'll test this tonight | 13:14 |
- eibachd (QUIT: Ping timeout: 264 seconds) (~eibachd@p200300dcf7231c007222c86f87cd63cb.dip0.t-ipconnect.de) | 13:17 | |
+ eibachd (~eibachd@p200300dcf7231c003381661af74b3909.dip0.t-ipconnect.de) | 13:18 | |
minute | josch: dump.mntmn.com/mb25_lpc_charge_delay.patch | 13:21 |
minute | josch: sorry, http://dump.mntmn.com/mb25_lpc_charge_delay.patch | 13:21 |
josch | thank you!! <3 | 13:22 |
minute | josch: thank me later, it might not work in your case :D but i'm eager to know | 13:22 |
- mjw (QUIT: Ping timeout: 268 seconds) (~mjw@gnu.wildebeest.org) | 13:53 | |
- eibachd (QUIT: Ping timeout: 264 seconds) (~eibachd@p200300dcf7231c003381661af74b3909.dip0.t-ipconnect.de) | 14:19 | |
+ eibachd (~eibachd@p200300dcf7231c0132cf13033121ba02.dip0.t-ipconnect.de) | 14:21 | |
* Guest5778 -> mjw | 14:33 | |
- eibachd (QUIT: Ping timeout: 264 seconds) (~eibachd@p200300dcf7231c0132cf13033121ba02.dip0.t-ipconnect.de) | 14:37 | |
minute | there might be some gitlab downtimes today due to security updates | 14:37 |
+ eibachd (~eibachd@2a01:599:305:65f5:8bfe:cafd:e386:1480) | 14:37 | |
- eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:305:65f5:8bfe:cafd:e386:1480) | 14:37 | |
+ eibachd (~eibachd@p200300dcf7231c00a2386c519f555b33.dip0.t-ipconnect.de) | 14:41 | |
mjw | minute, o, no, you won't attend Fosdem... I was hoping to say hi and thanks there. | 15:51 |
mjw | minute, so lets do that virtually then. Hi and thanks! My mnt reform has been so nice! | 15:52 |
minute | mjw: i'm sorry! | 15:52 |
minute | it's too much stress for me atm, it's not good to miss a weekend of rest during pocket production time here | 15:52 |
minute | i really need to be careful of not burning myself out | 15:52 |
mjw | of course! | 15:52 |
minute | and also, the stand situation would have been very suboptimal and crowded with sth like 4-6 projects having to share one stand | 15:53 |
mjw | And no worries, I am already the proud owner of one. I was just hoping to drag other people to your stand and make them drool over the (pocket) reform :) | 15:53 |
minute | and we don't have anything new to show (except production quality pocket reform), i.e. no "next" prototype yet, and there wouldn't be space for it anyway | 15:54 |
mjw | yes, the stands (and really also the devrooms and even the "empty" hallways) are totally overcrowded all the time. | 15:54 |
minute | i did this last year and i really had to recover from it for a while | 15:55 |
mjw | totally understand, same here. | 15:56 |
josch | i hope everybody manages to find a great work/health balance -- being incapacitated for half a year or more is not worth the productivity one had before a break-down :( | 16:40 |
minute | yeah | 16:59 |
+ mark_ (~mjw@gnu.wildebeest.org) | 17:26 | |
- mark_ (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org) | 17:54 | |
+ mark_ (~mjw@gnu.wildebeest.org) | 19:20 | |
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50) | 19:21 | |
- mark_ (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org) | 19:56 | |
+ klardotsh (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net) | 20:02 | |
- S0rin (QUIT: Ping timeout: 252 seconds) (~S0rin@user/s0rin) | 20:03 | |
+ S0rin (~S0rin@user/s0rin) | 20:06 | |
minute | TIL that you can just register your swapfile in /etc/fstab (like a swap partition) | 20:56 |
minute | so now i always have 8GB swap on my encrypted nvme in a311d reform | 20:56 |
- jagtalon (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@user/jagtalon) | 21:23 | |
+ jagtalon (~quassel@user/jagtalon) | 21:23 | |
- kensanata (QUIT: Quit: OK) (~alex@user/kensanata) | 21:26 | |
+ kensanata (~alex@user/kensanata) | 21:26 | |
josch | i had no idea files could be added to fastab either | 21:38 |
josch | but encrypted swap is also possible without a swap file -- the reform-system-encrypted-nvme sets up swap in lvm in luks to achieve this | 21:39 |
f_ | vkoskiv: Want to know how the hdmi dongle works? | 21:58 |
+ sibyla (~sibyl@91.93.173.55) | 22:20 | |
vkoskiv | The A311D is hardwired to try a specific SPI address via HDMI on startup, and then reads some bytes? I've never used SPI in Linux, and don't know how that works over HDMI | 22:20 |
vkoskiv | But I do know it's just shuffling bytes at the end of the day. One way or another :D | 22:20 |
- Gooberpatrol66 (QUIT: Ping timeout: 260 seconds) (~Gooberpat@user/gooberpatrol66) | 22:24 | |
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 22:26 | |
- Gooberpatrol66 (QUIT: Remote host closed the connection) (~Gooberpat@user/gooberpatrol66) | 22:40 | |
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 22:40 | |
minute | vkoskiv: i2c (display data channel) | 22:44 |
vkoskiv | Is that also used for EDID? | 23:03 |
+ mark_ (~mjw@gnu.wildebeest.org) | 23:13 | |
minute | vkoskiv: yep | 23:34 |
- sibyla (QUIT: Quit: WeeChat 4.1.2) (~sibyl@91.93.173.55) | 23:46 | |
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 23:46 | |
- cow321 (QUIT: Remote host closed the connection) (~deflated8@50.39.247.54) | 23:53 | |
+ cow321 (~deflated8@50.39.247.54) | 23:53 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!