2021-06-01.log

- S0rin (QUIT: Ping timeout: 265 seconds) (~S0rin@ns3078682.ip-217-182-133.eu)00:16
+ S0rin (~S0rin@ns3078682.ip-217-182-133.eu)00:22
- tarxvf (QUIT: Quit: out) (~tarxvf@mail.tarxvf.tech)00:30
+ tarxvf (~tarxvf@mail.tarxvf.tech)00:31
- tarxvf (QUIT: Quit: out) (~tarxvf@mail.tarxvf.tech)00:41
+ tarxvf (~tarxvf@mail.tarxvf.tech)00:42
- Neelfyn (QUIT: Read error: Connection reset by peer) (uid180106@id-180106.stonehaven.irccloud.com)00:45
- mjw (QUIT: Quit: Leaving) (~mark@herd.wildebeest.org)00:47
+ Neelfyn (uid180106@id-180106.stonehaven.irccloud.com)00:51
- S0rin (QUIT: Ping timeout: 268 seconds) (~S0rin@ns3078682.ip-217-182-133.eu)01:09
flowymntmn: so the blinking went away when i started charging. i went up to 100%, removed power, and now that it's down to 61%, the blinking has begun again.01:09
flowythe lowest cell is at 2.901:10
mntmnflowy: strange, the behavior was normally only with older keyboard firmware01:13
mntmnflowy: what rev/date is the kb firmware when you press circle and then s?01:14
flowyr1 2021041901:14
flowyabout a week ago, i did run the charge down pretty low a couple times.01:16
flowydidn't see this behavior then01:16
flowybut then i guess i left it without power for five days01:16
flowyhad no idea about the discharging01:17
flowyfirst experience with these kinds of batteries01:17
flowyi think i ran it down to 3 or 4% before, as i guessed it might be good for the controller to learn capacity01:18
mntmnflowy: that's all fine01:30
mntmnat the moment it sounds like a bug in the keyboard fw to me, that it blinks even if there's no reason to do so.01:31
+ S0rin (~S0rin@ns3078682.ip-217-182-133.eu)01:44
- freakazoid333 (QUIT: Read error: Connection reset by peer) (~freakazoi@2001:5b0:2a0c:8568:169:1c5:5f2d:6745)01:53
+ freakazoid333 (~freakazoi@2001:5b0:2a0c:8568:169:1c5:5f2d:6745)01:54
flowymntmn: hmmm just shutdown01:57
flowyit jumped from something like 46% to 0%... and i was refreshing the battery screen somewhat frequently01:58
flowyone cell reached down to 2.501:58
flowyi think the runtime on batteries was around 2-2.5hrs02:01
mntmnok02:28
mntmnnow i recommend to charge it again fully02:29
- S0rin (QUIT: Remote host closed the connection) (~S0rin@ns3078682.ip-217-182-133.eu)04:35
+ specing_ (~specing@APN-123-242-220-gprs.simobil.net)06:12
- specing (QUIT: Ping timeout: 265 seconds) (~specing@user/specing)06:14
+ odnes (~odnes@109-178-131-97.pat.ren.cosmote.net)06:53
- chartreuse (QUIT: Ping timeout: 265 seconds) (~chartreus@S0106f0f249dfd9c3.cg.shawcable.net)08:17
- lexik (QUIT: Remote host closed the connection) (~lexik@171.25.222.217)10:13
+ lexik (~lexik@171.25.222.217)10:19
+ mjw (~mjw_@2001:1c06:2488:200:9e5c:8eff:fe8f:a440)11:30
+ rasmus-mk (~rasmus@c83-253-223-217.bredband.tele2.se)12:18
- rasmus-mk (QUIT: Quit: WeeChat 3.0.1) (~rasmus@c83-253-223-217.bredband.tele2.se)12:39
+ rasmus-mk (~rasmus@c83-253-223-217.bredband.tele2.se)12:41
+ odnes_ (~odnes@109-178-131-97.pat.ren.cosmote.net)13:45
- odnes (QUIT: Read error: Connection reset by peer) (~odnes@109-178-131-97.pat.ren.cosmote.net)13:45
bluerisemntmn: why is leaving the batteries connected, machine off, not good? battery status is 99% right now... a day later14:26
blueriseso doesn't look like it's draining a lot14:26
mntmnbluerise: yes but it might drain after a few weeks14:26
blueriseok14:27
mntmnbluerise: it just happened to someone that i know, he left it for 2 or 3 weeks and it was empty14:27
blueriseyeah, ok, that I can understand :)14:27
mntmnit probably depends on the initial charge though14:27
blueriseFelt like you meant days instad of weeks14:27
blueriseyup14:27
mntmnand he was still able to revive the battery with a nightcore charger14:27
blueriseSome of my stuff often isn't running for quite a while, so I guess I need to take some precautions14:28
- rasmus-mk (QUIT: Quit: WeeChat 3.0.1) (~rasmus@c83-253-223-217.bredband.tele2.se)14:29
+ alex4nder (~alexander@189.250.205.241)16:48
alex4nderhey16:48
* alex4nder -> register16:49
* register -> Guest457516:49
FUZxxlhey Guest4575 16:49
* Guest4575 -> alex4nder16:50
alex4ndergo nickserv go16:50
alex4nderhow goes the hacking?16:51
FUZxxlfine16:51
FUZxxlworking on some FreeBSD ports r/n16:52
alex4nderlookig forward to hacking on things myself16:54
- odnes_ (QUIT: Ping timeout: 264 seconds) (~odnes@109-178-131-97.pat.ren.cosmote.net)17:45
+ odnes (~odnes@109-178-131-97.pat.ren.cosmote.net)17:46
+ specing (~specing@user/specing)18:14
- specing_ (QUIT: Ping timeout: 264 seconds) (~specing@APN-123-242-220-gprs.simobil.net)18:15
+ rasmus-mk (~rasmus@c83-253-223-217.bredband.tele2.se)18:29
- artfwo (QUIT: Remote host closed the connection) (~artfwo@2a02:8109:8500:26d0:388a:c204:3654:ccc1)18:43
- patrick (PART: WeeChat 3.0.1) (~patrick@2001:8b0:ca70:32b2:feaa:14ff:fe0a:92d4)18:59
- alex4nder (QUIT: *.net *.split) (~alexander@189.250.205.241)19:24
- Neelfyn (QUIT: *.net *.split) (uid180106@id-180106.stonehaven.irccloud.com)19:24
- FUZxxl (QUIT: *.net *.split) (~fuz@fuz.su)19:24
- ezequielg (QUIT: *.net *.split) (sid363064@id-363064.highgate.irccloud.com)19:24
- dodo (QUIT: *.net *.split) (~dodo@user/dodo)19:24
- arminweigl (QUIT: *.net *.split) (~arminweig@user/arminweigl)19:24
- piroko (QUIT: *.net *.split) (~piroko@104.225.216.16)19:24
+ FUZxxl (~fuz@fuz.su)19:24
+ ezequielg (sid363064@id-363064.highgate.irccloud.com)19:24
+ Neelfyn (uid180106@id-180106.stonehaven.irccloud.com)19:24
+ piroko (~piroko@104.225.216.16)19:26
+ dodo (~dodo@user/dodo)19:26
+ arminweigl (~arminweig@user/arminweigl)19:27
+ alex4nder (~alexander@189.250.205.241)19:29
- mjw (QUIT: Quit: Leaving) (~mjw_@2001:1c06:2488:200:9e5c:8eff:fe8f:a440)19:47
- alex4nder (QUIT: Ping timeout: 265 seconds) (~alexander@189.250.205.241)20:05
- odnes (QUIT: Remote host closed the connection) (~odnes@109-178-131-97.pat.ren.cosmote.net)20:15
+ odnes (~odnes@109-178-131-97.pat.ren.cosmote.net)20:16
+ S0rin (~S0rin@82-64-116-66.subs.proxad.net)20:31
mntmnFUZxxl: freebsd? that's nice!20:43
mntmnFUZxxl: if you don't already you can probably share some notes with bluerise who is working on OpenBSD20:44
- S0rin (QUIT: Quit: WeeChat 2.3) (~S0rin@82-64-116-66.subs.proxad.net)20:46
+ S0rin (~S0rin@82-64-116-66.subs.proxad.net)20:59
- odnes (QUIT: Read error: Connection reset by peer) (~odnes@109-178-131-97.pat.ren.cosmote.net)21:16
+ chartreuse (~chartreus@S0106f0f249dfd9c3.cg.shawcable.net)21:28
+ S0rin_ (~S0rin@ns3078682.ip-217-182-133.eu)21:37
- S0rin (QUIT: Ping timeout: 244 seconds) (~S0rin@82-64-116-66.subs.proxad.net)21:39
- freakazoid333 (QUIT: Read error: Connection reset by peer) (~freakazoi@2001:5b0:2a0c:8568:169:1c5:5f2d:6745)21:43
+ freakazoid333 (~freakazoi@2001:5b0:2a66:fc58:42f:154a:842c:dca2)21:46
- rasmus-mk (QUIT: Quit: WeeChat 3.0.1) (~rasmus@c83-253-223-217.bredband.tele2.se)22:00
+ mjw (~mark@herd.wildebeest.org)22:13
flowyi haven't been able to build a new system image from the reform-system-image repo. i've tried both in and outside of the build-base-image-docker, on the reform, but both stop at the same point:22:18
flowy__populate_fs: symlink increased in size between lstat() and readlink()22:18
flowy__populate_fs: Could not allocate block in ext2 filesystem while writing file "kcore"22:18
flowymke2fs: Could not allocate block in ext2 filesystem while populating file system22:18
flowyalso, ninja and meson not found while attempting builds...22:19
+ alex4nder (~alexander@189.250.203.159)22:33
mntmnflowy: hmmmmm. i will test it very soon agai23:20
mntmnagain23:20
+ erle (~erle@dynamic-046-114-033-182.46.114.pool.telefonica.de)23:43
- erlehmann (QUIT: Killed (NickServ (GHOST command used by erle!~erle@dynamic-046-114-033-182.46.114.pool.telefonica.de))) (~erle@dynamic-046-114-038-118.46.114.pool.telefonica.de)23:43
- S0rin_ (QUIT: Ping timeout: 264 seconds) (~S0rin@ns3078682.ip-217-182-133.eu)23:47

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!