minute | well, you can already detect charging | 00:00 |
---|---|---|
minute | if there's current flowing into the batteries, you're charging | 00:01 |
cinap_lenrek | how do we know its flowing in or out? @_@ | 00:02 |
cinap_lenrek | <- elecronics noob | 00:03 |
minute | cinap_lenrek: positive vs negative number | 00:09 |
minute | cinap_lenrek: atm not at the computer so i don't remember which is which in the firmware... iirc the sign is negated on the oled display? | 00:10 |
minute | cinap_lenrek: it's the amps (A) number on the battery status screen | 00:10 |
minute | cinap_lenrek: if you turn the power on and current is flowing out of the batteries, then you know for sure you are not on wall power. if the power is off and current is flowing into the battery, you know for sure that you are on wallpower. | 00:12 |
minute | cinap_lenrek: if the power is off and no current is flowing, you can't tell for sure. | 00:12 |
minute | (it could be that the batteries are fully charged) | 00:13 |
cinap_lenrek | fascinating, thank you very much for the explaination | 00:20 |
+ MajorBiscuit (~MajorBisc@46-229-126.internethome.cytanet.com.cy) | 00:52 | |
- S0rin (QUIT: Ping timeout: 256 seconds) (~S0rin@user/s0rin) | 00:59 | |
+ S0rin (~S0rin@user/s0rin) | 01:03 | |
- mtm (QUIT: Ping timeout: 248 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 02:03 | |
- chomwitt (QUIT: Ping timeout: 268 seconds) (~chomwitt@2a02:587:dc16:4100:194d:beae:942b:9603) | 02:11 | |
- MajorBiscuit (QUIT: Quit: WeeChat 3.5) (~MajorBisc@46-229-126.internethome.cytanet.com.cy) | 02:16 | |
- bkeys (QUIT: Ping timeout: 256 seconds) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 02:27 | |
+ mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 02:38 | |
+ chartreuse (~chartreus@S0106f0f249dfd9c3.cg.shawcable.net) | 03:28 | |
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 06:57 | |
+ MajorBiscuit (~MajorBisc@46-229-126.internethome.cytanet.com.cy) | 10:53 | |
Boostisbetter | You know, one thing I've noticed is that suspend performance has been super rock solid the past few months. | 10:58 |
Boostisbetter | I wonder if SoC support in the kernel is responsible for that through incremental improvement or if updates to another system is responsible. It has just been nice to all but rely on the suspend and resume functionally of the Reform these days. | 11:20 |
Boostisbetter | I wonder if SoC support in the kernel is responsible for that through incremental improvement or if updates to another system is responsible. It has just been nice to all but rely on the suspend and resume functionality of the Reform these days. | 11:21 |
+ reform4711 (~ckeen@94.45.226.178) | 13:49 | |
reform4711 | hi! I would like to present on a hdmi projector, how do I use the hdmi output on the reform? | 13:50 |
* reform4711 -> ckeen | 13:50 | |
ckeen | I am using sway atm and a get_ouputs swaymsg does not show the hdmi output | 13:51 |
ckeen | ah it is an FAQ :D | 13:54 |
- ckeen (QUIT: Remote host closed the connection) (~ckeen@94.45.226.178) | 13:55 | |
- mtm (QUIT: Ping timeout: 256 seconds) (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 14:03 | |
+ ephase (~ephase@2a01:e0a:168:1211::885) | 14:43 | |
- ephase (QUIT: Quit: WeeChat 3.6) (~ephase@2a01:e0a:168:1211::885) | 14:50 | |
Boostisbetter | Indeed, I think it is still controlled via the dcss_use_hdmi variable. | 15:07 |
+ bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 15:07 | |
- bkeys (QUIT: Ping timeout: 268 seconds) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 15:57 | |
+ mtm (~mtm@c-73-27-62-116.hsd1.fl.comcast.net) | 16:09 | |
- qwer (QUIT: Ping timeout: 268 seconds) (~qwer@37.48.16.23) | 16:15 | |
minute | sudo reform-display-config dual | 16:21 |
+ bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 16:31 | |
- S0rin (QUIT: Ping timeout: 252 seconds) (~S0rin@user/s0rin) | 16:41 | |
+ S0rin (~S0rin@user/s0rin) | 17:07 | |
chartreuse | I still need to redo mine with the newer system image (after I repair/replace my two 18650's) | 17:09 |
chartreuse | But yeah even without that update I've found it super stable, though I avoided the suspend resume mostly | 17:09 |
- S0rin (QUIT: Ping timeout: 256 seconds) (~S0rin@user/s0rin) | 17:15 | |
+ bkeys1 (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 17:18 | |
+ S0rin (~S0rin@user/s0rin) | 17:23 | |
- S0rin (QUIT: Ping timeout: 252 seconds) (~S0rin@user/s0rin) | 17:28 | |
+ S0rin (~S0rin@user/s0rin) | 17:30 | |
- bkeys (QUIT: Ping timeout: 268 seconds) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 17:41 | |
* bkeys1 -> bkeys | 17:41 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 18:05 | |
+ bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 18:05 | |
+ bkeys1 (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 18:09 | |
- bkeys (QUIT: Client Quit) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 18:10 | |
* bkeys1 -> bkeys | 18:10 | |
+ chomwitt (~chomwitt@2a02:587:dc16:4100:8951:37:5070:7277) | 18:58 | |
- MajorBiscuit (QUIT: Ping timeout: 252 seconds) (~MajorBisc@46-229-126.internethome.cytanet.com.cy) | 19:15 | |
- chomwitt (QUIT: Ping timeout: 248 seconds) (~chomwitt@2a02:587:dc16:4100:8951:37:5070:7277) | 19:15 | |
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 19:30 | |
+ qwer (~qwer@37.48.26.212) | 20:18 | |
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 20:44 | |
+ bkeys (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 20:46 | |
+ bkeys1 (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 20:50 | |
- GNUmoon2 (QUIT: Ping timeout: 268 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon) | 20:51 | |
- bkeys1 (QUIT: Remote host closed the connection) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 20:54 | |
+ GNUmoon2 (~GNUmoon@gateway/tor-sasl/gnumoon) | 20:55 | |
Boostisbetter | minute: the dual at the means that both the internal display and HDMI out will be active? I didn't know it could drive both at the same time. | 20:56 |
- GNUmoon2 (QUIT: Ping timeout: 268 seconds) (~GNUmoon@gateway/tor-sasl/gnumoon) | 21:00 | |
+ GNUmoon2 (~GNUmoon@gateway/tor-sasl/gnumoon) | 21:03 | |
+ mjw (~mark@gnu.wildebeest.org) | 21:07 | |
+ bkeys1 (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 21:07 | |
- bkeys1 (QUIT: Remote host closed the connection) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 21:18 | |
- GNUmoon2 (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 21:23 | |
+ GNUmoon2 (~GNUmoon@gateway/tor-sasl/gnumoon) | 21:24 | |
grubman | hm it seems something is borked with the reform-setup-encrypted-nvme script from the latest system image | 21:28 |
grubman | it seems to set up everything ~correctly but come boot time ends up booting from the sdcard still | 21:28 |
grubman | at boot there is a prompt to decrypt the nvme drive even | 21:28 |
josch | grubman: do you have some time now to debug this? | 21:29 |
grubman | sure | 21:31 |
josch | grubman: can you post the output of findmnt after your system has booted? | 21:31 |
grubman | can i PM? | 21:32 |
josch | grubman: sure, we can talk via query | 21:33 |
- kitty4 (QUIT: Ping timeout: 252 seconds) (~kitty@096-039-147-043.res.spectrum.com) | 21:49 | |
+ chomwitt (~chomwitt@2a02:587:dc16:4100:595d:9ae5:1b71:8d3d) | 22:08 | |
- bkeys (QUIT: Ping timeout: 248 seconds) (~Thunderbi@static-198-54-135-69.cust.tzulo.com) | 22:20 | |
- GNUmoon2 (QUIT: Remote host closed the connection) (~GNUmoon@gateway/tor-sasl/gnumoon) | 23:07 | |
+ GNUmoon2 (~GNUmoon@gateway/tor-sasl/gnumoon) | 23:08 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!