| * bkeys1 -> bkeys | 00:00 | |
| * edenist_ -> edenist | 00:01 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 00:01 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 00:02 | |
| * edenist -> edenist_ | 00:03 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 00:16 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 00:17 | |
| * edenist_ -> edenist | 00:29 | |
| * edenist -> edenist_ | 00:31 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 00:32 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 00:33 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 00:48 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 00:48 | |
| - mtm (QUIT: Ping timeout: 265 seconds) (~textual@47.202.75.129) | 01:02 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 01:03 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 01:03 | |
| + mtm (~textual@47.202.75.129) | 01:06 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 01:18 | |
| minute | damn, i tested this _a lot_ but still... https://community.mnt.re/t/display-driver-issue/2816 | 01:20 |
|---|---|---|
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 01:25 | |
| minute | (FWIW it's fine on rk3588 pocket) | 01:27 |
| minute | hmm, but it looks like the loaded driver here is not the right one | 01:29 |
| minute | ah nevermind i'm using extlinux still | 01:34 |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 01:34 | |
| minute | ok, now on > 6.12.5-mnt-reform-arm64 #1 SMP Debian 6.12.5-1+reform20241216T105228Z | 01:36 |
| minute | display still fine :3 | 01:36 |
| minute | > cat /sys/devices/platform/fde30000.dsi/fde30000.dsi.0/mnt_pocket_reform_panel_version | 01:36 |
| minute | > 1 | 01:36 |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 01:38 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 01:50 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 01:50 | |
| + jacobk (~quassel@2603:8080:b200:7b02:77cb:6304:f9db:dda1) | 01:52 | |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@2603:8080:b200:7b02:77cb:6304:f9db:dda1) | 01:56 | |
| mhoye | minute: ship that reflective jacket with a bill of materials | 01:58 |
| mhoye | and also how do I get to the front of the line | 01:59 |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 02:05 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 02:11 | |
| - mark_ (QUIT: Ping timeout: 265 seconds) (~mjw@gnu.wildebeest.org) | 02:12 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 02:22 | |
| + kerntallett (~kerntalle@2a02:c7c:d128:6600:6fa2:26e3:23a9:6fcf) | 02:26 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 02:26 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 02:36 | |
| - edenist_ (QUIT: Quit: l8rsk8r) (edenist@rdns.robotprofessor.net) | 02:36 | |
| + edenist (~edenist@rdns.robotprofessor.net) | 02:38 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 02:39 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 02:52 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 02:52 | |
| - kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 03:02 | |
| + kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 03:03 | |
| - kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 03:03 | |
| + kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 03:04 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 03:07 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 03:08 | |
| - paperManu (QUIT: Ping timeout: 260 seconds) (~paperManu@107.159.243.8) | 03:11 | |
| * edenist -> edenist_ | 03:21 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 03:23 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 03:23 | |
| * edenist_ -> edenist | 03:28 | |
| * edenist -> edenist_ | 03:29 | |
| - kerntallett (QUIT: Quit: kerntallett) (~kerntalle@2a02:c7c:d128:6600:6fa2:26e3:23a9:6fcf) | 03:31 | |
| * edenist_ -> edenist | 03:34 | |
| * edenist -> edenist_ | 03:35 | |
| * edenist_ -> edenist | 03:36 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 03:39 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 03:39 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 03:54 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 03:54 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 04:09 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 04:10 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 04:25 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 04:25 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 04:40 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 04:41 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 04:57 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 05:01 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 05:11 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 05:12 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 05:27 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 05:27 | |
| - aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.17.85) | 05:41 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 05:43 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 05:43 | |
| + aloo_shu (~aloo_shu@85.51.17.85) | 05:50 | |
| - patsavoura (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~linx@149.210.4.16) | 05:54 | |
| + Ar|stote|is (~linx@149.210.4.16) | 05:55 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 05:58 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 05:58 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 06:14 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 06:14 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 06:29 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 06:30 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 06:45 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 06:45 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 07:02 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 07:10 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 07:17 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 07:17 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 07:31 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 07:32 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 07:47 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 07:47 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 07:47 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:02 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:03 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:18 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:18 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:34 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:35 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:49 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 08:49 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:05 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:05 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:20 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:20 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:36 | |
| + bkeys1 (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:36 | |
| * bkeys1 -> bkeys | 09:38 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:51 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 09:52 | |
| minute | mhoye: hehe | 10:01 |
| minute | bkeys: your connection... oscillates | 10:01 |
| josch | i was just about to write the same thing... | 10:01 |
| josch | minute: i uploaded an image for you to test :) | 10:01 |
| josch | well, CI did | 10:02 |
| - jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 10:04 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 10:04 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:07 | |
| + chomwitt (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 10:07 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:07 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:22 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:23 | |
| sevan | "rockchip rk6502" they're making 6502 CPUs now!? | 10:25 |
| - cobra_ (QUIT: Ping timeout: 244 seconds) (~cobra@user/Cobra) | 10:34 | |
| + cobra (~cobra@user/Cobra) | 10:34 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:37 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:38 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:53 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 10:54 | |
| - cobra (QUIT: Quit: ZNC 1.8.2 - https://znc.in) (~cobra@user/Cobra) | 11:03 | |
| - chomwitt (QUIT: Ping timeout: 265 seconds) (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 11:05 | |
| + cobra (~cobra@user/Cobra) | 11:08 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:09 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:09 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:24 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:30 | |
| ch | *cough* /filter add irc_smart * irc_smart_filter * | 11:36 |
| josch | and apparently this is not just for weechat but also for irssi: https://github.com/lifeforms/irssi-smartfilter | 11:39 |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:40 | |
| josch | ch: but then how will i be able to take part in complaining about the things that everybody else in the channel is complaining about? :D | 11:40 |
| ch | "sorry" :D | 11:42 |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:46 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:55 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 11:56 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 11:56 | |
| sevan | "-!- Irssi: Loaded script smartfilter" | 12:04 |
| sevan | ch, josch, thanks for the pointer :) | 12:05 |
| - iank (QUIT: Ping timeout: 248 seconds) (~iank@fsf/staff/iank) | 12:05 | |
| * mark_ -> mjw | 12:09 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:11 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:11 | |
| sevan | ... | 12:15 |
| sevan | ACTION wonders is smartfilter has muted entire channel | 12:16 |
| sevan | s/is/if | 12:16 |
| minute | sevan: test 123 | 12:25 |
| BoostisBetter | sevan: I am seeing everything you are saying as well | 12:26 |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:27 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:28 | |
| sevan | minute: <3 | 12:28 |
| sevan | BoostisBetter: ok, this thing is on! :) | 12:29 |
| sevan | thanks. | 12:29 |
| + paperManu (~paperManu@107.159.243.8) | 12:29 | |
| BoostisBetter | anyone else here running the Signal flatpak client on your Pocket? I have to run it twice before it will come up. | 12:38 |
| BoostisBetter | Anybody else noticing that? | 12:38 |
| BoostisBetter | it probably has to do with a setting that it didn't have permissions to make from the sandbox | 12:40 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:42 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:42 | |
| + iank (~iank@fsf/staff/iank) | 12:44 | |
| grimmware | BoostisBetter: I've run a different version of Signal and I also have to launch it twice *if* I do the needful configuration for native wayland (i.e. ozone) | 12:45 |
| grimmware | it always launches straight away on XWayland | 12:45 |
| BoostisBetter | grimmware: exactly. It seems to work perfectly after launching, just curious that it needs to be launched twice. | 12:48 |
| - ndufresne (QUIT: Quit: The Lounge - https://thelounge.chat) (~ndufresne@apple.collaboradmins.com) | 12:51 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:57 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 12:58 | |
| grimmware | very similar experience, had it happen on other laptops, don't know why :/ | 12:59 |
| - digitalrane (QUIT: Ping timeout: 260 seconds) (~rane@user/digitalrane) | 13:00 | |
| + digitalrane (~rane@user/digitalrane) | 13:01 | |
| + gustav28 (~gustav@c-78-82-53-236.bbcust.telenor.se) | 13:02 | |
| - mtm (QUIT: Ping timeout: 248 seconds) (~textual@47.202.75.129) | 13:04 | |
| + mtm (~textual@47.202.75.129) | 13:05 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 13:13 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 13:13 | |
| minute | i have a fix, now jumping through all the patching hoops | 13:15 |
| - aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.17.85) | 13:17 | |
| minute | ok, pushed to CI | 13:22 |
| + aloo_shu (~aloo_shu@85.51.17.85) | 13:26 | |
| + pandora (uid585533@id-585533.ilkley.irccloud.com) | 13:28 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 13:29 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 13:29 | |
| - mjw (QUIT: Ping timeout: 244 seconds) (~mjw@gnu.wildebeest.org) | 13:33 | |
| minute | (also tested on a311d with display v1+display v2) | 13:35 |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 13:44 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 13:45 | |
| + glu_ (~glu@user/glu) | 13:45 | |
| - glu (QUIT: Ping timeout: 248 seconds) (~glu@user/glu) | 13:45 | |
| * glu_ -> glu | 13:45 | |
| josch | nice! :) | 13:48 |
| + murph_nj (~murph@pool-108-35-93-154.nwrknj.fios.verizon.net) | 13:52 | |
| * Guest1555 -> mjw | 13:52 | |
| + kerntallett (~kerntalle@90.196.184.225) | 13:56 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:00 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:00 | |
| - aloo_shu (QUIT: Read error: Connection reset by peer) (~aloo_shu@85.51.17.85) | 14:02 | |
| + aloo_shu (~aloo_shu@85.51.17.85) | 14:03 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:15 | |
| + chomwitt (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 14:15 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:16 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:31 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 14:31 | |
| BoostisBetter | So I have a script which sets pocket keyboard leds using amospalla's rmt tool. The script will work if I invoke it in the terminal with ./ but is not doing anything in sway | 14:35 |
| - kerntallett (QUIT: Quit: kerntallett) (~kerntalle@90.196.184.225) | 14:35 | |
| BoostisBetter | i have it bound to a combo and and trying to using the script like this after the binding: exec .config/sway/wrapper.sh | 14:36 |
| BoostisBetter | this does not work though | 14:36 |
| - jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 14:39 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 14:39 | |
| + ndufresne (~ndufresne@apple.collaboradmins.com) | 14:42 | |
| ch | maybe you need to say ~/.config/... | 14:50 |
| ch | just guessing though | 14:50 |
| amospalla | You probably need permissions, you are writing to a device in /dev. | 14:50 |
| amospalla | My script is a simple wrapper that ends doing a `printf > /dev/hidrawN`, but needs to be run as root, or at least with permissions to write to the device. | 14:54 |
| BoostisBetter | yeah I did a chmod +x | 14:59 |
| BoostisBetter | I thought this would make runnable but it does need root to work. | 15:00 |
| gsora | have you tried with a udev rule? | 15:02 |
| BoostisBetter | would need help with that. | 15:04 |
| BoostisBetter | I know they allow you to alias sudo on commands, and give those commands to run as root, but I don't know how to make the rule. | 15:05 |
| gsora | let's see if i can be helpful then! | 15:08 |
| BoostisBetter | gsora: that would be great | 15:08 |
| BoostisBetter | the command in the wrapper is | 15:08 |
| BoostisBetter | sudo rmt leds set 0 0 255 | 15:08 |
| BoostisBetter | basically I want to use a key combo to just make the keyboard backlight blue. | 15:09 |
| gsora | without sudo of course | 15:09 |
| BoostisBetter | I would need a udev rule for rmt, I believe. | 15:09 |
| gsora | yup, there's prior art on it as well: https://unix.stackexchange.com/questions/85379/dev-hidraw-read-permissions | 15:09 |
| BoostisBetter | no because it is rightin the /dev/hidraw I believe it is necessary | 15:09 |
| gsora | the accepted answer should work, provided your user is in the plugdev group | 15:09 |
| BoostisBetter | ok the solution is for hidraw, if I replace that with rmt | 15:15 |
| BoostisBetter | is it ithe same? | 15:15 |
| gsora | well if rmt accesses /dev/hidrawN directly, then it should work the same | 15:16 |
| gsora | that is, running rmt without sudo should have read/write access to /dev/hidrawN | 15:16 |
| - ericsfraga (QUIT: Quit: ERC 5.6.1-git (IRC client for GNU Emacs 31.0.50)) (~user@2a00:23cc:b43d:4b00::3ce) | 15:16 | |
| BoostisBetter | meaning that I leave hidraw in there and don't substitue rmt for it? | 15:16 |
| gsora | i'm assuming that rmt read/writes to /dev/hidrawN here | 15:18 |
| BoostisBetter | it does | 15:19 |
| BoostisBetter | so I can just use hidraw* in the udev rule | 15:19 |
| BoostisBetter | that is what you mean | 15:19 |
| gsora | yeah i think | 15:20 |
| gsora | that rule should allow plugdev users to read/write to any /dev/hidrawN device | 15:20 |
| amospalla | my script shows your hidraw device path. Putting this on cron should work too '@reboot my_username "$(/usr/local/bin/rmt wait hidraw)" && chmod g+w "$(/usr/local/bin/rmt wait hidraw)"' | 15:21 |
| BoostisBetter | I added the udev, but not sure how to restart the udev services. I'll try rebooting. | 15:22 |
| amospalla | Sorry, this '@reboot chgrp my_username "$(/usr/local/bin/rmt wait hidraw)" && chmod g+w "$(/usr/local/bin/rmt wait hidraw)"' | 15:23 |
| amospalla | An udev rule is cleaner though. | 15:24 |
| amospalla | More event oriented. | 15:24 |
| BoostisBetter | just reboot and it is working calling rmt directly from the sway config. Thank you very much for the help | 15:24 |
| gsora | so no need for sudo right? | 15:25 |
| BoostisBetter | yep, just can call rmt leds set and pass the argument and it works. | 15:25 |
| gsora | awesome! glad i could help | 15:29 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 15:37 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 15:37 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 15:52 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 15:53 | |
| + kerntallett (~kerntalle@2a02:c7c:d128:6600:6fa2:26e3:23a9:6fcf) | 15:53 | |
| BoostisBetter | gsora and amospalla: thank you for the help! | 15:59 |
| amospalla | you're welcome | 15:59 |
| + mark_ (~mjw@gnu.wildebeest.org) | 16:26 | |
| - kerntallett (QUIT: Quit: kerntallett) (~kerntalle@2a02:c7c:d128:6600:6fa2:26e3:23a9:6fcf) | 16:44 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 16:46 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 16:46 | |
| - kensanata (QUIT: Read error: Connection reset by peer) (~alex@user/kensanata) | 16:59 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:01 | |
| + bkeys1 (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:02 | |
| * bkeys1 -> bkeys | 17:04 | |
| - mark_ (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org) | 17:13 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:17 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:17 | |
| minute | just came back from errands for video shoot, and the pocket update seems to be rolled out and apparently fixed the display problem for user morph | 17:28 |
| + kensanata (~alex@user/kensanata) | 17:29 | |
| josch | so much success this week :) | 17:30 |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:32 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 17:33 | |
| * mesaoptimizer -> mesaoptimizer0 | 17:36 | |
| minute | new kernel also works on my rk3588 pocket reform with display v1 | 17:44 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:02 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:02 | |
| BoostisBetter | na wunderbar! | 18:16 |
| BoostisBetter | minute: that is really good news! | 18:16 |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:21 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:21 | |
| minute | i wonder why my session doesn't autostart dunst anymore | 18:33 |
| minute | it works on the current reform system image | 18:33 |
| minute | if i manually do: systemctl --user start dunst | 18:33 |
| minute | it's fine | 18:33 |
| + ericsfraga (~user@2a00:23cc:b43d:4b00::3ce) | 18:34 | |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:36 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:37 | |
| + mark_ (~mjw@gnu.wildebeest.org) | 18:42 | |
| + kerntallett (~kerntalle@2a02:c7c:d128:6600:6fa2:26e3:23a9:6fcf) | 18:43 | |
| murph_nj | @minute, Thanks for the quick display fix! | 18:44 |
| - murph_nj (QUIT: Quit: Leaving) (~murph@pool-108-35-93-154.nwrknj.fios.verizon.net) | 18:45 | |
| + murph_nj (~murph@pool-108-35-93-154.nwrknj.fios.verizon.net) | 18:45 | |
| - murph_nj (QUIT: Client Quit) (~murph@pool-108-35-93-154.nwrknj.fios.verizon.net) | 18:48 | |
| + murph_nj (~murph@pool-108-35-93-154.nwrknj.fios.verizon.net) | 18:48 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:52 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 18:52 | |
| sevan | It's been an interesting couple of days. Went to wake my other laptop up & it reset & it wouldn't boot back up. Dead SSD. Now waiting on another delivery of an SSD :D | 18:55 |
| sevan | back on reform, now just running it without any batteries attached until the new ones show up :) | 18:55 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:07 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:08 | |
| - kerntallett (QUIT: Ping timeout: 266 seconds) (~kerntalle@2a02:c7c:d128:6600:6fa2:26e3:23a9:6fcf) | 19:12 | |
| - aperezdc (QUIT: Ping timeout: 244 seconds) (~aperezdc@2a03:6000:6e61:633::43) | 19:17 | |
| + vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 19:18 | |
| - robin (QUIT: Ping timeout: 276 seconds) (~robin@user/terpri) | 19:19 | |
| sevan | hmm, finally got to check my emails today, looks like it's not so bad. cable to hook up to sysctl port has shipped, same for batteries. When they'll arrive I have no idea but I guess Saturday at the very latest if I'm lucky. :) | 19:21 |
| sevan | otherwise other side of Christmas / NY?? | 19:21 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:23 | |
| + bkeys1 (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:23 | |
| + robin (~robin@user/terpri) | 19:25 | |
| * bkeys1 -> bkeys | 19:25 | |
| - hairu (QUIT: Remote host closed the connection) (m-uotkmd@user/hairu) | 19:27 | |
| + hairu (m-uotkmd@user/hairu) | 19:28 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:38 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:39 | |
| * mesaoptimizer0 -> mesaoptimizer | 19:42 | |
| - hairu (QUIT: Remote host closed the connection) (m-uotkmd@user/hairu) | 19:44 | |
| + hairu (m-uotkmd@user/hairu) | 19:46 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:54 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 19:54 | |
| - glu (QUIT: Ping timeout: 244 seconds) (~glu@user/glu) | 20:00 | |
| + glu (~glu@user/glu) | 20:00 | |
| - jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 20:11 | |
| + jacobk (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 20:12 | |
| - mjw (QUIT: Killed (tantalum.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 20:14 | |
| * mark_ -> mjw | 20:14 | |
| + Guest1132 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 20:15 | |
| * mesaoptimizer -> mesaoptimizer0 | 20:45 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:48 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 20:48 | |
| BoostisBetter | does anyone even use the emmc on their Reform or Pocket Reform? I was never that interested in it because I was always under the impression that it will wear out much faster than an NVME. | 20:50 |
| BoostisBetter | I'm using it on the Pocket to boot, but that is it. | 20:51 |
| nocko | I've only used it for /boot | 21:01 |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 21:04 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 21:04 | |
| nocko | Unrelated question: I have an original reform2 motherboard (#83). The battery meter (oled) recently stuck at 0%. However charge/discharge and the meter in swaybar function as intended. I assumed my firmware was old, and installed a newer one using ./download_fw.sh in reform/reform-lpc-fw . I selected 20_R3 (because I have a 2.0 motherboard (I think that was the first shipping versio). | 21:05 |
| nocko | After the upgrade, the battery meter (oled) is stuck at ???% and charging no longer works. | 21:05 |
| nocko | It will run from AC, but not charge. | 21:05 |
| nocko | Upon closer inspection, the motherboard version says: <obscured by cable>MOB20R02. | 21:06 |
| nocko | This sounds like I have an older motherboard and should build the fw myself with #define REFORM_MOTHERBOARD_REV REFORM_MBREV_R2. | 21:07 |
| nocko | I just wanted to confirm before I get started. | 21:08 |
| sevan | nocko: somewhere in the LPC firmware I recall it states that if you got your motherboard before 2023, it's an R2 version. | 21:10 |
| nocko | Okay. I tried to save myself the build/setup and use the downloader... and that doesn't support R2. It advises to use 20_R3 "if you have a 2.0 motherboard". | 21:11 |
| sevan | nocko: https://source.mnt.re/reform/reform/-/blob/master/reform2-lpc-fw/src/boards/reform2/board_reform2.c?ref_type=heads#L40 | 21:14 |
| + aperezdc (~aperezdc@2a03:6000:6e61:633::43) | 21:15 | |
| sevan | nocko: https://source.mnt.re/reform/reform/-/jobs/7052/artifacts/browse/reform2-lpc-fw/ | 21:16 |
| nocko | Yeah, it doesn't build an artifact and the script only accepts 25_R2 or 20_R3 | 21:18 |
| nocko | It's fixable. I'll try to put in a patch. | 21:18 |
| + kerntallett (~kerntalle@90.196.184.225) | 21:19 | |
| sevan | nocko: I meant to say download firmware-20_R3.bin from there and save it as 'firmware.bin' in your reform/reform-lpc-fw/bin directory. | 21:19 |
| nocko | I don't have an R3, I have an R2 | 21:19 |
| sevan | nocko: you can then run ./flash.sh | 21:20 |
| nocko | I can build it myself, but it would be nice if it was prebuilt. | 21:20 |
| sevan | that's release 3 for the 2.0 motherboard, right? | 21:20 |
| sevan | and release 2 for the 2.5 motherboard | 21:21 |
| sevan | or that's what I understood. Let me double check | 21:21 |
| nocko | I have release 2 of the 2.0 board. | 21:21 |
| sevan | ahh, are you refering to '#define REFORM_MBREV_R2 12 // stock R2' | 21:23 |
| nocko | I think that is me, yes. | 21:23 |
| sevan | understood. | 21:24 |
| sevan | nocko: just to double check, when you upgraded to the latest firmware, did you upgrade the lpc driver package on the OS side? (assuming you're running debian) | 21:25 |
| nocko | I wanted to check my understanding, like maybe the 20_R3 is also supposed to support the 20_R2... the help text on the download_fw.sh command says use 20_R3 "if you have a 2.0 motherboard". | 21:25 |
| nocko | The lpc driver is current. | 21:26 |
| sevan | nocko: according to comment in src "#define REFORM_MBREV_20_R3 13 // R2 with "NTC instead of RNG/SS" fix | 21:27 |
| nocko | I read that, but I don't know if mine has this fix. It's quite an early unit. | 21:27 |
| nocko | March 2021 | 21:29 |
| sevan | appologies, I don't want to waste your time or give the wrong info, but my impression is that the board is largely the same aside for the one change but I think it's best for minute to answer, being the one who worked on it :) | 21:31 |
| nocko | I built an 20_R2 version just now. I'll see how it goes. | 21:32 |
| - bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 21:37 | |
| + bkeys (~Thunderbi@254.sub-97-150-246.myvzw.com) | 21:37 | |
| nocko | Still not charging. boo. | 21:40 |
| nocko | Full model number is MREFPMOB20R02, dated 2020-10-29. | 21:41 |
| + mesaoptimizer (~mesa@user/PapuaHardyNet) | 21:45 | |
| sevan | nocko: is that from the transparent sticker? | 21:50 |
| sevan | nocko: just curious :) | 21:50 |
| nocko | no that's from the motherboard. The transparent sticker is dated 2021-03-12 | 21:53 |
| nocko | Oof, now a key is wonky on the keyboard, only since the last flash. | 21:56 |
| sevan | nocko: you mean physically wonky? | 21:57 |
| - kerntallett (QUIT: Quit: kerntallett) (~kerntalle@90.196.184.225) | 22:00 | |
| sevan | nocko: the transparent sticker on mine is dated the same. 2021-03-12 | 22:00 |
| - mesaoptimizer0 (QUIT: Quit: nyaa~) (~mesaoptim@user/PapuaHardyNet) | 22:06 | |
| sevan | nocko: also on the motherboard MREFPMOB20R02 | 22:06 |
| josch | nocko: https://source.mnt.re/reform/reform-handbook/-/issues/4 | 22:13 |
| josch | for MREFPMOB20R02 you want firmware-20_R3.bin which is auto-built | 22:13 |
| - gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-53-236.bbcust.telenor.se) | 22:15 | |
| - bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@254.sub-97-150-246.myvzw.com) | 22:17 | |
| - jacobk (QUIT: Ping timeout: 248 seconds) (~quassel@47-186-65-73.dlls.tx.frontiernet.net) | 22:35 | |
| - chomwitt (QUIT: Quit: WeeChat 3.8) (~chomwitt@2a02:587:7a14:db00:1ac0:4dff:fedb:a3f1) | 22:38 | |
| sevan | josch: thanks for the link. | 22:38 |
| + ephase (~ephase@2a01:e0a:2a:5300:37a2:e71a:ace3:241d) | 22:41 | |
| ephase | Hi! | 22:42 |
| minute | yo! | 22:43 |
| ephase | does someonne have a black screen after updating reform to 6.12 kernel (a311D). Same occurs with last image downloaded form gitlab! | 22:44 |
| ephase | How are you minute? | 22:44 |
| minute | ephase: uh oh! reform or pocket? | 22:44 |
| ephase | reform 2 minute | 22:44 |
| ephase | But with linux magih, I started it from the last week image and start a chroot to launch weechat :D | 22:45 |
| minute | ephase: do you know which kernel you had before 6.12? | 22:45 |
| josch | i... actually had 6.12 tested on a311d | 22:46 |
| minute | yeah i thought so too | 22:46 |
| ephase | 6.11.9 | 22:46 |
| minute | is that also the kernel you're using now? | 22:47 |
| josch | i'm not on 6.12 right now, i only tested it with a system image last week. I also used the linux6.12 branch which did not have your pocket display patches | 22:47 |
| ephase | 6.11.10 on my previous workin installation and on this sd cartd created with last week image | 22:48 |
| minute | ok, i can check tomorrow if something in that branch could have touched something there | 22:48 |
| minute | now i'm too tired and would just make mistakes | 22:48 |
| minute | in any case sorry for the trouble ephase | 22:48 |
| ephase | on my side I will create a system dist with the last available image an check another time | 22:49 |
| ephase | no problem minute, Im choose reform to have toubles! | 22:51 |
| minute | :D | 22:52 |
| ephase | So, I will try to update my current new install with last kernel ann check if all reboot | 22:53 |
| + jacobk (~quassel@2603:8080:b200:7b02:77cb:6304:f9db:dda1) | 22:54 | |
| ephase | I try rebooting | 22:58 |
| - ephase (QUIT: Quit: WeeChat 4.4.3) (~ephase@2a01:e0a:2a:5300:37a2:e71a:ace3:241d) | 22:59 | |
| - jacobk (QUIT: Ping timeout: 276 seconds) (~quassel@2603:8080:b200:7b02:77cb:6304:f9db:dda1) | 23:22 | |
| + ephase (~ephase@2a01:e0a:2a:5300:c5cc:4869:a349:3003) | 23:39 | |
| ephase | re, so after another tests : last -> black screen, last week image -> boot, apt update+upgrade on last week update -> black screen | 23:42 |
| sevan | If you have OpenZFS 2.2.7 installed, you're good for the 6.12 kernel upgrade. | 23:56 |
| - ephase (QUIT: Ping timeout: 276 seconds) (~ephase@2a01:e0a:2a:5300:c5cc:4869:a349:3003) | 23:57 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!