minute | maybe a scheduled task ran | 00:00 |
---|---|---|
minute | now for the bad news: the disk space is still occupied | 00:00 |
josch | huh | 00:00 |
minute | ah, now it happened | 00:01 |
minute | i guess these are scheduled tasks with not super high frequency | 00:01 |
minute | ok: /dev/sdb 98G 65G 29G 69% /mnt/gitlab-artifacts | 00:02 |
minute | you should be able to build again! | 00:02 |
josch | that looks much better :) | 00:02 |
josch | the job is already running in the hope that disk space would be freed on time for its completion :D | 00:02 |
minute | haha :D | 00:02 |
minute | just-in-time | 00:02 |
josch | mntre.com/reform-debian-repo already has new reform-tools 1.34 and linux-image 6.6.8 | 00:03 |
josch | so anybody feeling adventurous can try it out now :) | 00:03 |
minute | great | 00:03 |
minute | i guess i am feeling adventurous | 00:03 |
josch | gogogo! :D | 00:03 |
josch | i'll still be awake for a bit in case some emergency fixes are required XD | 00:04 |
minute | > linux-image-6.6.9-reform2-arm64 | 00:05 |
minute | didn't you say 6.6.8... | 00:05 |
josch | i... did... huh? | 00:05 |
minute | am i seeing an image from the future? | 00:05 |
josch | oh 6.6.9 got uploaded to unstable yesterday | 00:06 |
josch | i only tested 6.6.8... | 00:06 |
minute | ok, lets try 6.6.9 then | 00:06 |
josch | funny, this log says: | 00:07 |
josch | Get:54 https://mntre.com/reform-debian-repo reform/main arm64 linux-image-6.6.8-reform2-arm64 arm64 6.6.8-1+reform20231225T111019Z1 [62.9 MB] | 00:07 |
josch | but now indeed 6.6.9 is here: https://mntre.com/reform-debian-repo/pool/main/l/linux/ | 00:08 |
josch | did i mess up and 6.6.8 got wrongly uploaded to mntre.com days ago? | 00:10 |
minute | installed, rebooting | 00:11 |
josch | minute: also reform-tools 1.34? | 00:12 |
josch | it includes changes to poweroff | 00:12 |
minute | josch: working fine so far! | 00:13 |
josch | uff.. that relieves me a lot :) | 00:13 |
josch | minute: you are on a311d as well, right? | 00:13 |
minute | josch: yes | 00:14 |
minute | josch: i think i have to manually delete the old poweroff hook... where does that go again | 00:14 |
josch | /usr/lib/systemd/system-shutdown/reform-poweroff (which sent xPWR0 to the keyboard) is gone now in favour to the lpc dkms module doing the poweroff | 00:14 |
josch | minute: maybe there is an equivalent in /etc and that's why you have to delete it manually? | 00:15 |
minute | ah no. there is fwupd.shutdown in there | 00:15 |
minute | (i only saw apt complaining that it couldn't delete that directory) | 00:15 |
josch | ah okay | 00:16 |
minute | unclear why i have fwupd | 00:16 |
minute | uninstalling | 00:16 |
minute | anyway, i will keep on using/testing ^^ | 00:16 |
josch | i'm most happy that it works on a311d because the whole patch stack got switched out -- but seems to have worked like a charm! | 00:17 |
minute | (and yes, i also upgraded reform-tools) | 00:17 |
josch | great :D | 00:17 |
josch | then i can go to bed in peace :) | 00:17 |
minute | also just checked hdmi, works | 00:18 |
josch | oh i didn't check that | 00:18 |
minute | josch: indeed, thanks for everything! | 00:18 |
josch | nice, good night! _o/ | 00:18 |
minute | n8n8 | 00:19 |
josch | installed reform2-lpc-dkms package post-installation script subprocess returned error exit status 127 | 00:27 |
josch | oh no... | 00:27 |
minute | hmmm, for me it worked | 00:28 |
josch | it's in reform-system-image | 00:28 |
josch | it worked two days ago | 00:28 |
bluerise | minute: got the NVMe adapter, have it installed nicely :) | 00:28 |
minute | bluerise: ah great | 00:29 |
josch | maybe the change 6.6.8 to 6.6.9 is involved | 00:29 |
bluerise | btw, I feel like after updating the LPC the battery status works better? | 00:34 |
bluerise | with the updated battery board in there, it had 'troubles' with the cells | 00:34 |
bluerise | but now it shows the status just fine | 00:34 |
+ erle (~erle@2a02:3102:4286:16:2620:917b:97db:eb06) | 00:41 | |
minute | bluerise: i think the cells look weird at first before connecting a charger. if the cell protectors are not all "open" | 00:43 |
- chomwitt (QUIT: Ping timeout: 256 seconds) (~chomwitt@2a02:587:7a0f:8900:1ac0:4dff:fedb:a3f1) | 00:51 | |
+ f_[xmpp] (fffdb90022@fases/developer/funderscore) | 01:00 | |
josch | minute: turns out the problem was a new upload of the dkms package yesterday | 01:01 |
josch | minute: just make sure not to upgrade your dkms package to the version in unstable | 01:03 |
josch | in case you want to follow the bug progress, it's tracked here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059885 | 01:03 |
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 01:11 | |
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@45.134.140.153) | 02:39 | |
+ bkeys (~Thunderbi@45.134.140.153) | 02:41 | |
- S0rin (QUIT: Ping timeout: 260 seconds) (~S0rin@user/s0rin) | 03:13 | |
+ S0rin (~S0rin@user/s0rin) | 03:14 | |
- mjw (QUIT: Ping timeout: 264 seconds) (~mjw@gnu.wildebeest.org) | 03:31 | |
- nsc (QUIT: Ping timeout: 245 seconds) (~nicolas@166-121-142-46.pool.kielnet.net) | 03:42 | |
+ nsc (~nicolas@173-48-142-46.pool.kielnet.net) | 03:44 | |
- jagtalon (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@user/jagtalon) | 04:44 | |
+ jagtalon (~quassel@user/jagtalon) | 04:59 | |
- erle (QUIT: Quit: Just say no, then Putin can not legally invade your nation without your consent.) (~erle@2a02:3102:4286:16:2620:917b:97db:eb06) | 06:07 | |
- klardotsh (QUIT: Ping timeout: 256 seconds) (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net) | 07:10 | |
josch | okay, great the reform2-lpc-dkms postinst failure was indeed not my fault but due to the new dkms version in sid trying to source a bash script in dash which fails if it happens to include bash-isms | 07:13 |
- eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf7231c001fa87565e7775b4e.dip0.t-ipconnect.de) | 07:34 | |
+ eibachd (~eibachd@p200300dcf7231c00b1069ee9dc117d32.dip0.t-ipconnect.de) | 07:34 | |
+ julianwgs (~julian@p4fc2f9b8.dip0.t-ipconnect.de) | 08:03 | |
- julianwgs (QUIT: Client Quit) (~julian@p4fc2f9b8.dip0.t-ipconnect.de) | 08:03 | |
- jagtalon (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@user/jagtalon) | 08:04 | |
+ jagtalon (~quassel@user/jagtalon) | 08:04 | |
- jagtalon (QUIT: Client Quit) (~quassel@user/jagtalon) | 08:05 | |
+ jagtalon (~quassel@user/jagtalon) | 08:05 | |
- eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@p200300dcf7231c00b1069ee9dc117d32.dip0.t-ipconnect.de) | 09:25 | |
+ eibachd (~eibachd@2a01:599:321:17dd:5128:9a38:8a88:4a97) | 09:30 | |
+ julianwgs (~julian@p4fc2f9b8.dip0.t-ipconnect.de) | 09:39 | |
- julianwgs (QUIT: Ping timeout: 268 seconds) (~julian@p4fc2f9b8.dip0.t-ipconnect.de) | 09:44 | |
+ julianwgs (~julian@2a01:599:607:7b73:879c:abd2:9d43:eb36) | 09:44 | |
- eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:321:17dd:5128:9a38:8a88:4a97) | 10:17 | |
+ eibachd (~eibachd@p200300dcf7231c00243e7f0decac5b14.dip0.t-ipconnect.de) | 10:18 | |
- eibachd (QUIT: Ping timeout: 240 seconds) (~eibachd@p200300dcf7231c00243e7f0decac5b14.dip0.t-ipconnect.de) | 10:35 | |
+ eibachd (~eibachd@2a01:599:321:17dd:5128:9a38:8a88:4a97) | 10:36 | |
+ mjw (~mjw@84.241.203.146) | 10:44 | |
- eibachd (QUIT: Ping timeout: 246 seconds) (~eibachd@2a01:599:321:17dd:5128:9a38:8a88:4a97) | 10:48 | |
- mjw (QUIT: Ping timeout: 246 seconds) (~mjw@84.241.203.146) | 11:14 | |
- yankcrime (QUIT: Quit: "") (~nick@gw.tetromino.io) | 11:14 | |
+ eibachd (~eibachd@2a01:599:321:17dd:5128:9a38:8a88:4a97) | 11:18 | |
+ yankcrime (~nick@gw.tetromino.io) | 11:26 | |
- eibachd (QUIT: Read error: Connection reset by peer) (~eibachd@2a01:599:321:17dd:5128:9a38:8a88:4a97) | 11:28 | |
+ eibachd (~eibachd@p200300dcf7231c0009a4152b6b97566c.dip0.t-ipconnect.de) | 11:28 | |
+ mjw (~mjw@84.241.203.146) | 11:29 | |
- julianwgs (QUIT: Ping timeout: 276 seconds) (~julian@2a01:599:607:7b73:879c:abd2:9d43:eb36) | 11:33 | |
- shdw (QUIT: Remote host closed the connection) (~shdw@ip-037-201-005-171.um10.pools.vodafone-ip.de) | 11:43 | |
+ julianwgs (~julian@p200300e9d74175002db5732af09997ab.dip0.t-ipconnect.de) | 11:48 | |
- mjw (QUIT: Ping timeout: 264 seconds) (~mjw@84.241.203.146) | 12:00 | |
- eibachd (QUIT: Ping timeout: 246 seconds) (~eibachd@p200300dcf7231c0009a4152b6b97566c.dip0.t-ipconnect.de) | 13:51 | |
- yankcrime (QUIT: Quit: "") (~nick@gw.tetromino.io) | 13:51 | |
+ eibachd (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 14:03 | |
- eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 14:14 | |
+ Twodisbetter (2cc0e4ea1c@irc.cheogram.com) | 14:34 | |
+ eibachd (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 14:36 | |
- eibachd (QUIT: Ping timeout: 268 seconds) (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 14:46 | |
+ eibachd (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 15:19 | |
- eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 15:28 | |
+ erle (~erle@2a02:3102:4286:16:45fd:d54e:dd4c:6900) | 16:06 | |
+ eibachd (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 16:09 | |
Twodisbetter | josch: it has to be your software stack then. Because suspend works near perfect on my Reform these days. | 16:24 |
- eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 16:24 | |
Twodisbetter | josch: really sorry to hear that though. | 16:24 |
Twodisbetter | I wonder if all of your modification might be contributing to this? | 16:25 |
josch | Twodisbetter: the modifications were with the mainboard and i swapped that out for 2.5 | 16:44 |
josch | it's unlikely to be my software stack because i use the same OS and kernel patches like you do | 16:45 |
Twodisbetter | hmmm, I do wonder though why it still isn't working. | 16:47 |
Twodisbetter | I don't hear people talking much about suspend, so I wonder if there are a lot of other people who have suspend working for them. | 16:47 |
josch | Twodisbetter: it is entirely possible that different imx8mq boards just behave differently | 16:54 |
josch | the first imx8mq board i had, had the TX line of the UART broken. RX worked. Sometimes this just happens. Unfortunately, not all boards are created equally. | 16:55 |
minute | yeah | 17:01 |
+ eibachd (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 17:13 | |
- eibachd (QUIT: Ping timeout: 256 seconds) (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 17:22 | |
+ mjw (~mjw@89.205.135.243) | 17:35 | |
- erle (QUIT: Ping timeout: 276 seconds) (~erle@2a02:3102:4286:16:45fd:d54e:dd4c:6900) | 17:41 | |
AbortRetryFail | wasn't there a thing in the lpc firmware to disable the uart? | 17:42 |
AbortRetryFail | oh, i misread.. nvm | 17:43 |
+ erle (~erle@2a02:3102:4286:16:fb3b:63a:be5:cdd8) | 17:43 | |
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 17:45 | |
- mjw (QUIT: Ping timeout: 256 seconds) (~mjw@89.205.135.243) | 17:46 | |
+ ephase (~ephase@2a01:e0a:2a:5300:f8d4:1fb6:b769:4362) | 17:55 | |
ephase | hello | 17:55 |
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net) | 18:13 | |
+ eibachd (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 18:17 | |
- julianwgs (QUIT: Quit: Leaving.) (~julian@p200300e9d74175002db5732af09997ab.dip0.t-ipconnect.de) | 18:22 | |
+ julianwgs (~julian@p4fc2f9b8.dip0.t-ipconnect.de) | 18:23 | |
ephase | Does someone here have a CM3 adapter + bananapi module? I want to know about temperatures and power consumption | 18:29 |
- julianwgs (QUIT: Ping timeout: 252 seconds) (~julian@p4fc2f9b8.dip0.t-ipconnect.de) | 18:29 | |
- eibachd (QUIT: Ping timeout: 260 seconds) (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 18:33 | |
minute | ephase: i use it right now (you mean CM4 i think) | 18:38 |
minute | it doesn't run hot and i get around 4-5h usage | 18:38 |
ephase | minute: yes CM4 :) sorry | 18:42 |
ephase | minute: hooo great thank you | 18:42 |
+ chomwitt (~chomwitt@2a02:587:7a0f:8900:1ac0:4dff:fedb:a3f1) | 18:54 | |
ephase | minute: does the battery support with proection worth it? I had some problem with batteries (some died prematurely and others discharged quickly after) | 19:04 |
minute | ephase: absolutely 110% worth it ^^ | 19:04 |
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-159-4.tukw.qwest.net) | 19:07 | |
- chomwitt (QUIT: Ping timeout: 256 seconds) (~chomwitt@2a02:587:7a0f:8900:1ac0:4dff:fedb:a3f1) | 19:08 | |
+ eibachd (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 19:09 | |
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net) | 19:09 | |
ephase | minute: putted in my cart :D | 19:12 |
ephase | minute: last question, does trackball cups are avaiable and does it solve the trackball on screen problem? | 19:14 |
ephase | when the lid is closed | 19:15 |
minute | ephase: with the current trackball design it should not press on the screen | 19:15 |
minute | trackball cups are printed in house | 19:16 |
ephase | mine does it (bit I have the Reform N.5) | 19:16 |
minute | what's n.5? | 19:17 |
ephase | number 5 | 19:17 |
minute | oh you mean serial numbe 5 | 19:17 |
minute | number | 19:17 |
ephase | yes | 19:17 |
minute | ohh ok | 19:17 |
minute | and still has the original trackball from back then? | 19:18 |
minute | getting a new tb cup is a good idea then | 19:18 |
minute | ah i see it says "availability unknown" in the shop, gonna fix that | 19:18 |
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-159-4.tukw.qwest.net) | 19:23 | |
minute | ephase: fixed | 19:24 |
minute | https://shop.mntre.com/products/mnt-reform-trackball-cup | 19:24 |
+ colinsane (~colinunin@97-113-159-4.tukw.qwest.net) | 19:27 | |
- eibachd (QUIT: Ping timeout: 276 seconds) (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 19:28 | |
josch | too late for my display i guess -- the black spot is already there :) | 19:29 |
ephase | thanks minute | 19:31 |
minute | i also have a spot but i don't see it during regular use, only when the display is off | 19:32 |
minute | (and my reform has gone through many versions) | 19:32 |
ephase | minute: yes the spot is invisible whe the screen is on | 19:33 |
ephase | And I put a litte piece of thin foam (same you have on brand new laptop) when I close it | 19:34 |
ephase | since | 19:34 |
josch | huh for me it's the opposite. I see the spot when there is white content around the area but not when it's black. | 19:34 |
ephase | josch: I have a dark theme everywhere with minimal backlight here | 19:38 |
ephase | I will test it on white screen | 19:38 |
josch | ephase: me too -- i see it on websites without dark-mode :) | 19:40 |
ephase | josch: I have DarkReader on Firefox ^_^ | 19:42 |
ephase | Without battereis, Oled screen show 5.3V on each cells, it's normal? | 19:48 |
minute | ephase: normal yep | 19:56 |
ephase | yes TY minute | 20:00 |
+ mjw (~mjw@93.191.1.237) | 20:00 | |
+ eibachd (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 20:02 | |
jfred | Hmm, I've got some key bounce on the rightmost space key on my standalone keyboard. Wonder if I've got some dust in the switch or something | 20:05 |
- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@93.191.1.237) | 20:06 | |
+ klardotsh (~klardotsh@c-67-170-115-80.hsd1.wa.comcast.net) | 20:06 | |
- eibachd (QUIT: Ping timeout: 240 seconds) (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 20:09 | |
- XYZ_ (QUIT: Remote host closed the connection) (~XYZ@37-48-49-146.nat.epc.tmcz.cz) | 20:46 | |
+ XYZ_ (~XYZ@37-48-49-146.nat.epc.tmcz.cz) | 20:49 | |
- ephase (QUIT: Quit: WeeChat 4.1.1) (~ephase@2a01:e0a:2a:5300:f8d4:1fb6:b769:4362) | 20:57 | |
+ tiskaan (~tiskaan@84.70.121.60) | 20:58 | |
+ ephase (~ephase@2a01:e0a:2a:5300:f8d4:1fb6:b769:4362) | 21:03 | |
ephase | Haa good nees jr_caam seems fixed in new kernel avaiable for the Reform, Wifi woek like a charm now | 21:04 |
ephase | 'good news' | 21:06 |
+ eibachd (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 21:12 | |
- eibachd (QUIT: Ping timeout: 268 seconds) (~eibachd@p200300dcf7231c00c9f922ec2f267ed3.dip0.t-ipconnect.de) | 21:17 | |
+ mjw (~mjw@84.241.195.137) | 21:19 | |
- ephase (QUIT: Quit: WeeChat 4.1.1) (~ephase@2a01:e0a:2a:5300:f8d4:1fb6:b769:4362) | 21:22 | |
- tiskaan (QUIT: Ping timeout: 256 seconds) (~tiskaan@84.70.121.60) | 21:45 | |
- mjw (QUIT: Remote host closed the connection) (~mjw@84.241.195.137) | 21:51 | |
+ mjw (~mjw@84.241.195.137) | 21:51 | |
- mjw (QUIT: Read error: Connection reset by peer) (~mjw@84.241.195.137) | 22:07 | |
+ mjw (~mjw@84.241.197.197) | 22:11 | |
+ eibachd (~eibachd@pd9509587.dip0.t-ipconnect.de) | 22:24 | |
- mjw (QUIT: Ping timeout: 260 seconds) (~mjw@84.241.197.197) | 22:31 | |
- XYZ_ (QUIT: Ping timeout: 260 seconds) (~XYZ@37-48-49-146.nat.epc.tmcz.cz) | 22:41 | |
+ chomwitt (~chomwitt@2a02:587:7a0f:8900:1ac0:4dff:fedb:a3f1) | 22:51 | |
+ XYZ_ (~XYZ@37-48-8-216.nat.epc.tmcz.cz) | 22:53 | |
+ mjw (~mjw@gnu.wildebeest.org) | 22:54 | |
+ tiskaan (~tiskaan@84.70.121.60) | 23:05 | |
hramrach | minute: is thre any plan to incorporate the bearings in the trackabll cup? I think it's well enough researched by now that it's clear that both ceramic nad steel bearings do improve the trackball usability over plastic bearings. | 23:14 |
minute | hramrach: i am not sure what you mean. the bearings are in the cup. | 23:29 |
minute | as seen here https://shop.mntre.com/products/mnt-reform-trackball-cup | 23:29 |
minute | (we use steel bearings) | 23:30 |
+ cwebber- (~Christine@user/cwebber) | 23:51 | |
- cwebber (QUIT: Ping timeout: 264 seconds) (~Christine@user/cwebber) | 23:52 | |
- tiskaan (QUIT: Ping timeout: 252 seconds) (~tiskaan@84.70.121.60) | 23:52 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!