josch | conv=notrunc only makes sense for files i thought | 00:00 |
---|---|---|
vagrantc | ch: suggested where? i just have whatever the original reform came with | 00:03 |
ch | ah, for reform i have no clue | 00:04 |
ch | the rk3588 module has no wifi onboard afaik | 00:04 |
vagrantc | i think there is an ath9k card in the pcie slot | 00:04 |
ch | and you dont have an antenna attached to that? | 00:05 |
vagrantc | there is an antenna attached to that ... but the laird antenna is supposedly better ... but claims to only be comptible with imx8mq and a311d modules ... but i suspect that was written before the rk3588 existed | 00:06 |
ch | i somewhat doubt that it is module-specific | 00:07 |
vagrantc | yeah, it seems odd\ | 00:07 |
vagrantc | do i need to somehow get the old antenna off the plastic antenna holder pastic bit? | 00:08 |
vagrantc | guess i can just get the rk3588 in and see where to go from there | 00:08 |
minute | vagrantc: apropos that antenna, we should probably discontinue it because it makes sense only with the "old" wifi carrier (acrylic) that will conflict a bit with the hdmi adapter. rk3588 comes with a new one that sits atop the sd card slot. if you have an mpcie card you'll need a wifi antenna that has longer leads than the old laird one in the shop | 00:15 |
minute | vagrantc: ok, so you have the old molex antenna only? | 00:16 |
minute | hmm it would be better if we had included a long leads molex antenna with the rcore | 00:17 |
minute | vagrantc: i'm writing down that we'll replace that laird antenna in the shop with something more useful | 00:18 |
josch | minute: is it true what ch said above and reform-flash-uboot can actually not work for rk3588? i thought that's why we did the last reform-tools release with the version you tagged last week? | 00:20 |
ch | https://paste.debian.net/hidden/58005673/ just sayin' | 00:21 |
minute | josch: yeah, i thought it was doing the right thing... i.e. writing not to the boot partition but to the main one | 00:21 |
vagrantc | minute: yeah, old molex i think | 00:21 |
josch | minute: currently, when writing to eMMC, it would look for the boot0 partition -- i don't think you told me that r3588 works different from the rest | 00:22 |
minute | josch: aha, the reason why i thought everything was fine is because i did: `sudo reform-flash-uboot sd` | 00:22 |
minute | and that worked | 00:22 |
josch | ooooh | 00:22 |
josch | i think then we need just another variable in the machines/*.conf files: for the u-boot partition | 00:22 |
minute | josch: that's possible and i'm sorry! i stumbled over this more than once myself | 00:22 |
josch | then lets fix it now :) | 00:22 |
minute | because it's pretty strange | 00:23 |
vagrantc | curiously, the at9k wifi is not detected with a 6.10.x kernel from reform.debian.net ... will check 6.11.x soon, as it appears to be available | 00:23 |
vagrantc | works fine with the 6.1.x kernel from reform.debian.net | 00:23 |
vagrantc | (or at least, an old 6.1.x, don't yet have the current one) | 00:23 |
josch | minute: also currently, rk3588 still has EMMC_BOOT=false, only BPI-CM4 and i.MX8MP have EMMC_BOOT=warn. Should rk3588 also have EMMC_BOOT=warn? | 00:25 |
minute | maybe they (rockchip) just wanted to keep their ROM simple and reused the SD code for emmc | 00:25 |
minute | josch: yeah sounds good! | 00:25 |
minute | josch: just to double check, which offset do you have in there? | 00:25 |
josch | oh no... was that the board with different offset on emmc compared to sd-card? | 00:26 |
ch | 32768 works | 00:26 |
ch | and is the right offset afaict from hexdump | 00:26 |
josch | minute: UBOOT_OFFSET=32768 | 00:26 |
minute | josch: sounds good | 00:26 |
minute | the different offset is only needed on other modules because they use emmc boot partition where the offset is 0 :D | 00:27 |
minute | apparently the offset is chosen by rockchip so that it is between a GPT table and it's first entry (???) | 00:27 |
josch | yes, debian-installer was recently changed to only let the first partition start at 16 MiB because of rockchip | 00:28 |
+ bkeys (~Thunderbi@45.134.140.153) | 00:28 | |
minute | uff | 00:29 |
josch | oh it was imx8mplus. when flashing to sd-card the correct offset would be 33792 but imx8mplus cannot boot from sd-card so that's irrelevant | 00:29 |
ch | unsure why they didn't just use a partition | 00:29 |
josch | ch: rockchip or d-i? | 00:29 |
ch | sifive puts two entries into gpt and then you know whats going on | 00:29 |
ch | d-i could probably also have done that? | 00:30 |
vagrantc | because the habits were developed before gpt partitioning was ever considered (or maybe even existed at all) | 00:30 |
ch | doesnt sound like the bootrom would care | 00:30 |
josch | ch: d-i is using a dummy partition. There is apparently no way to tell d-i "here must be X MiB of *nothing*" | 00:30 |
vagrantc | ch: then you need a separate image for every board, just to handle the different partition offsets. | 00:31 |
ch | ok dummy partition is nice | 00:31 |
josch | and yes what vagrantc said -- other rockchip boards also have the same offset | 00:31 |
josch | like, much older ones | 00:31 |
ch | at least on the installed system you need to know the offsets anyway | 00:31 |
ch | (afair the d-i change is about the installed system) | 00:31 |
josch | ch: the installed system? | 00:32 |
ch | josch: the to-be-installed system, not d-i itself | 00:32 |
josch | yes, the to-be-installed system | 00:32 |
vagrantc | all the various upstream vendors used different offsets... i was able to make an image that booted both pinebook (allwinner A64) and pinebook pro (rockchip rk3399) by just installing the bootloader for each board at non-overlapping offsets (as there are alternate offsets that some vendor boot roms try) | 00:32 |
vagrantc | meh. must have left the mnt/reform running or something ... came back with cells down to ~2.7v ... thanks batery protection board for keeping it from getting worse! | 00:34 |
vagrantc | now the cells seem to claim 93% power remaining when some of them are down to 3.1v though :( ... that does not bode well | 00:35 |
vagrantc | getting used to the new keyboard (v3?) at least :) | 00:36 |
ch | https://github.com/util-linux/util-linux/blob/master/include/pt-gpt-partnames.h#L271 this is a good idea imo | 00:39 |
vagrantc | so ... which kernels support the rk3588? | 00:39 |
ch | i have 6.11.9-mnt-reform-arm64 on rk3588 | 00:40 |
ch | (and -4 until earlier today iirc) | 00:40 |
ch | pocket, however | 00:40 |
josch | vagrantc: i have the rk3588 for classic reform ordered but still waiting for it -- i thus cannot test it myself | 00:41 |
vagrantc | confirmed that the 6.11.x kernel from reform.debian.net does not detect the ath9k either | 00:45 |
- chomwitt (QUIT: Ping timeout: 272 seconds) (~chomwitt@2a02:587:7a16:a200:1ac0:4dff:fedb:a3f1) | 00:54 | |
vagrantc | or at least, not at every boot ... finally worked on 6.11.x | 00:56 |
josch | o0 | 00:57 |
vagrantc | e.g. the device just wasn't there on the pcie bus | 00:57 |
- aloo_shu (QUIT: Ping timeout: 255 seconds) (~aloo_shu@85.51.16.59) | 01:03 | |
vagrantc | ah, i see now, the rk3588 comes with aa molex antenna with larger leads ... i had not opened the box to much to look | 01:05 |
minute | vagrantc: ah good | 01:08 |
+ aloo_shu (~aloo_shu@85.51.16.59) | 01:11 | |
vagrantc | the printed paper i got with my rk3588 module is different from https://mntre.com/documentation/reform-rcore-rk3588-manual.pdf ... the online one notably missing the wifi antenna stuff | 01:21 |
vagrantc | well, thanks for all the help. i might be bold ... or might put things off another day. :) | 01:28 |
vagrantc | ACTION waves | 01:28 |
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50) | 01:28 | |
+ _justin_kelly1 (~justinkel@user/justin-kelly/x-6011154) | 01:37 | |
- _justin_kelly (QUIT: Ping timeout: 255 seconds) (~justinkel@user/justin-kelly/x-6011154) | 01:38 | |
* _justin_kelly1 -> _justin_kelly | 01:38 | |
- _justin_kelly (QUIT: Client Quit) (~justinkel@user/justin-kelly/x-6011154) | 01:42 | |
+ _justin_kelly (~justinkel@user/justin-kelly/x-6011154) | 01:57 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 01:59 | |
+ bkeys (~Thunderbi@45.134.140.153) | 01:59 | |
- Gooberpatrol66 (QUIT: Ping timeout: 260 seconds) (~Gooberpat@user/gooberpatrol66) | 02:02 | |
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 02:06 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 02:12 | |
+ bkeys (~Thunderbi@45.134.140.153) | 02:12 | |
josch | okay, here is my untested mmc boot0 support for rk3588: https://paste.debian.net/hidden/89292714/ | 02:32 |
josch | early testers welcome | 02:32 |
- cobra (QUIT: Ping timeout: 252 seconds) (~cobra@user/Cobra) | 02:47 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 02:53 | |
+ bkeys (~Thunderbi@45.134.140.153) | 02:53 | |
- kop316 (QUIT: Remote host closed the connection) (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 03:03 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 03:03 | |
+ bkeys (~Thunderbi@45.134.140.153) | 03:03 | |
+ kop316 (m-6f6zq6@static.138.159.90.157.clients.your-server.de) | 03:04 | |
- paperManu (QUIT: Ping timeout: 276 seconds) (~paperManu@107.159.243.8) | 03:05 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 03:13 | |
+ bkeys (~Thunderbi@45.134.140.153) | 03:13 | |
mhoye | staticbunny: the behavior that's set in /etc/login.defs is overridden by settings in /etc/pam.d/login | 03:16 |
mhoye | So while I _think_ you can define /etc/issue behavior somewhere in login.defs, in my case I uncommented a line in /etc/pam.d/login and /etc/issue works. | 03:19 |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 03:23 | |
+ bkeys (~Thunderbi@45.134.140.153) | 03:24 | |
- chrcav (QUIT: Ping timeout: 244 seconds) (~chrcav@user/chrcav) | 03:30 | |
+ chrcav (~chrcav@user/chrcav) | 03:31 | |
- Gooberpatrol66 (QUIT: Ping timeout: 260 seconds) (~Gooberpat@user/gooberpatrol66) | 03:33 | |
+ Gooberpatrol66 (~Gooberpat@user/gooberpatrol66) | 03:33 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 03:34 | |
+ bkeys (~Thunderbi@45.134.140.153) | 03:34 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 03:44 | |
+ bkeys (~Thunderbi@45.134.140.153) | 03:44 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 03:54 | |
+ bkeys (~Thunderbi@45.134.140.153) | 03:54 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 04:04 | |
+ bkeys (~Thunderbi@45.134.140.153) | 04:05 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 04:17 | |
+ bkeys (~Thunderbi@45.134.140.153) | 04:17 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 04:22 | |
+ bkeys (~Thunderbi@45.134.140.153) | 04:22 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 04:27 | |
- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org) | 04:27 | |
+ bkeys (~Thunderbi@45.134.140.153) | 04:27 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 04:32 | |
dominicm | did some testing and the RP2040 continues to drive the GPIO pins during sleep! so it should definitely be possible to wake on keypress | 04:32 |
+ bkeys (~Thunderbi@45.134.140.153) | 04:32 | |
dominicm | although now I have no idea why it isn't waking up...will do some more fanangling around but theoretically all the pieces are there | 04:33 |
dominicm | butttt hopefully if this works standby power consumption on the pocket will be negligible? | 04:34 |
- bkeys (QUIT: Client Quit) (~Thunderbi@45.134.140.153) | 04:36 | |
+ bkeys (~Thunderbi@45.134.140.153) | 04:36 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 04:41 | |
+ bkeys (~Thunderbi@45.134.140.153) | 04:41 | |
+ vagrant_ (~vagrant@97-120-14-2.ptld.qwest.net) | 04:44 | |
vagrant_ | well, rk3588 upgrade went mostly smoothly ... typing from it right now! | 04:44 |
vagrant_ | only oops was i must not have properly seated the edp adapter onto the motherboard ... so on the first try the screen did not light up | 04:45 |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@45.134.140.153) | 04:46 | |
+ bkeys (~Thunderbi@45.134.140.153) | 04:47 | |
vagrant_ | does it use the same physical pins for serial console? | 04:47 |
- bkeys (QUIT: Remote host closed the connection) (~Thunderbi@45.134.140.153) | 04:48 | |
vagrant_ | the spot where i wedged my serial adapter no longer fits with the new location for the wireless antennas | 04:48 |
vagrant_ | the acrylic mount for the new antennas is slightly interfered with by the headers for the audio output ... the pins stick up just a little bit high ... maybe if i carve out a hole for those i can fit my serial consoel adapter back in there... | 04:51 |
vagrant_ | and now almost out of battery! | 04:52 |
vagrant_ | ACTION waves | 04:52 |
vagrant_ | back for more another day... | 04:52 |
- vagrant_ (QUIT: Quit: leaving) (~vagrant@97-120-14-2.ptld.qwest.net) | 04:52 | |
ch | josch: in your diff, "MNT Reform 2 with LS1028A Module.conf" has DEV_MMC_BOOT0=false, is that an accident? | 05:03 |
josch | ch: maybe. I wasn't quite sure what to do about LS1028A because it's now the only platform where u-boot is *not* allowed on emmc. So it seemed not "wrong" to say that there is no "boot0" partition if u-boot cannot be on emmc in the first place. | 07:31 |
+ chomwitt (~chomwitt@2a02:587:7a16:a200:1ac0:4dff:fedb:a3f1) | 07:37 | |
- blast007 (QUIT: Read error: Connection reset by peer) (~blast@user/blast007) | 08:37 | |
+ blast007` (~blast@user/blast007) | 08:37 | |
[tj] | grimmware: what antennas did you get? | 10:28 |
[tj] | is there a wiki with this sort of information? | 10:28 |
* blast007` -> blast007 | 10:31 | |
josch | minute: so... i'm considering to flash u-boot on my a311d. If I understand it correctly, then this will allow my reform to boot without an sd-card, correct? To let it read u-boot from an sd-card I could just zero the boot0 partition similar to how you said you'd do it for rk3588, right? | 10:34 |
josch | i was hesitant for a long time because, if the flashing goes wrong, i loose my computer XD | 10:35 |
josch | but i guess i should just go and do it at some point... | 10:35 |
grimmware | [tj]: they’re the laird ones in the picture at the top of https://shop.mntre.com/products/mnt-pocket-reform-upgrade-bundle - if you can’t make out the product details from the image I can take the backplate off my pocket and take a photo :) | 10:35 |
minute | josch: correct, that should work. | 10:35 |
josch | phew... lets try this | 10:36 |
josch | my next message will either not happen or be from a flashed a311d :) | 10:36 |
[tj] | grimmware: these? https://shop.mntre.com/products/mnt-reform-laird-wi-fi-antenna | 10:36 |
minute | i really really need to put the part numbers for the new laird antennas up. sorry for the confusion | 10:38 |
grimmware | [tj]: hmm they look different :/ | 10:45 |
grimmware | [tj]: I’ll be at my desk in a bit, I’ll send you the details then if minute doesn’t get there first | 10:47 |
josch | phew, i guess that was as good a test as any that the new reform-flash-uboot actually works :) | 10:50 |
josch | huh i got it's my reform birthday this november. I received it at the end of 2021, then hacked on it a lot, then took it on a long trip in summer 2022 and have been using it as my only machine since fall 2022. That's 2 years of use now. | 10:59 |
josch | minute: you made a really sturdy laptop which apparently survives everything i'm subjecting it to on a daily basis for around 2 years now :) | 10:59 |
minute | josch: niiice | 11:02 |
[tj] | minute: do the pocket reforms shipping november need newer antennas or do they already have them? | 11:03 |
- chomwitt (QUIT: Ping timeout: 260 seconds) (~chomwitt@2a02:587:7a16:a200:1ac0:4dff:fedb:a3f1) | 11:06 | |
grimmware | [tj]: you'll need the new antennas for the asiarf card, but the imx8mp has onboard wifi and an antenna for it. The asiarf is, in my experience, better | 11:15 |
[tj] | there is gonna be so much wifi in this tiny computer | 11:16 |
[tj] | is there a reason that ax200/210 intel wireless can't work? I so rumors about it being locked to intel, but that doesn't seem to be true | 11:16 |
+ paperManu (~paperManu@107.159.243.8) | 12:20 | |
+ gustav28 (~gustav@c-78-82-52-175.bbcust.telenor.se) | 13:02 | |
+ gsora_ (~gsora@user/gsora) | 13:04 | |
- gsora (QUIT: Ping timeout: 260 seconds) (~gsora@user/gsora) | 13:04 | |
* gsora_ -> gsora | 13:04 | |
- gsora (QUIT: Remote host closed the connection) (~gsora@user/gsora) | 13:08 | |
+ gsora (~gsora@user/gsora) | 13:08 | |
- buckket (QUIT: Quit: buckket) (~buckket@vps.buckket.org) | 13:32 | |
+ buckket (~buckket@vps.buckket.org) | 13:33 | |
+ cobra (~cobra@user/Cobra) | 13:38 | |
- ericsfraga (QUIT: Quit: ERC 5.6.1-git (IRC client for GNU Emacs 31.0.50)) (~user@2a00:23cc:b43d:4b00::3ce) | 13:42 | |
+ ericsfraga (~user@2a00:23cc:b43d:4b00::3ce) | 13:49 | |
+ mjw (~mjw@gnu.wildebeest.org) | 14:12 | |
+ chomwitt (~chomwitt@2a02:587:7a16:a200:1ac0:4dff:fedb:a3f1) | 14:19 | |
minute | [tj]: i think that rumor is not true | 14:27 |
[tj] | I found a discussion on the framework forums on the amd framework where people had just swapped it in | 14:27 |
[tj] | I am very deep in the ax200/210 driver right now and I don't see anything that would limit to intel hardware | 14:28 |
minute | i think those are usually bios limited | 14:38 |
minute | on pc notebook platforms, but we don't have a pc platform | 14:38 |
ch | josch: now that reformusbtool is not C anymore, do you still think it should be its own package? (https://source.mnt.re/zeha/reform-mcu-tool/) | 14:42 |
[tj] | consistently evil | 14:42 |
- mjw (QUIT: Ping timeout: 252 seconds) (~mjw@gnu.wildebeest.org) | 14:50 | |
* Guest5002 -> mjw | 14:57 | |
minute | [tj]: Antenna Model: 2x Ezurio EFB2455A3S-20MHF1 | 15:14 |
+ bkeys (~Thunderbi@72.sub-97-150-200.myvzw.com) | 15:21 | |
grimmware | oh shit yeah I was supposed to find that out severl hours ago | 15:26 |
jfred | I don't remember for sure but I think I'm using an intel wireless card of some sort in my big reform | 15:28 |
[tj] | that is a wonderful comment, it implies it works so well you can forget what it is | 15:45 |
[tj] | project 3.9, shipping 12 | 15:45 |
- chomwitt (QUIT: Ping timeout: 264 seconds) (~chomwitt@2a02:587:7a16:a200:1ac0:4dff:fedb:a3f1) | 15:51 | |
- nsc (QUIT: Ping timeout: 260 seconds) (~nicolas@i5C74DCCD.versanet.de) | 15:54 | |
+ nsc (~nicolas@i5C74DCCD.versanet.de) | 16:22 | |
+ Guest17 (~Guest17@141.206.231.10) | 16:34 | |
- ericsfraga (QUIT: Quit: ERC 5.6.1-git (IRC client for GNU Emacs 31.0.50)) (~user@2a00:23cc:b43d:4b00::3ce) | 16:42 | |
- aloo_shu (QUIT: Ping timeout: 252 seconds) (~aloo_shu@85.51.16.59) | 16:43 | |
+ ericsfraga (~user@2a00:23cc:b43d:4b00::3ce) | 16:44 | |
staticbunny | Has anyone tried changing colors in tuigreet? i cant the background/box colors to work. | 16:48 |
+ aloo_shu (~aloo_shu@85.51.16.59) | 16:52 | |
+ andreas-e (~Andreas@2001:861:c4:f2f0::c64) | 16:52 | |
- andreas-e (QUIT: Remote host closed the connection) (~Andreas@2001:861:c4:f2f0::c64) | 16:52 | |
+ dodo__ (~dodo@user/dodo) | 16:55 | |
- dodo (QUIT: Ping timeout: 252 seconds) (~dodo@user/dodo) | 16:55 | |
- xha (QUIT: Ping timeout: 252 seconds) (~xha@user/xha) | 16:56 | |
- gsora (QUIT: Ping timeout: 252 seconds) (~gsora@user/gsora) | 16:56 | |
* dodo__ -> dodo | 16:57 | |
+ xha (~xha@user/xha) | 16:58 | |
ch | i just realised my 5v-hwmod should also just be a flag in the sysctl fw configblock | 16:58 |
+ gsora (~gsora@user/gsora) | 16:58 | |
- Guest17 (QUIT: Ping timeout: 256 seconds) (~Guest17@141.206.231.10) | 17:04 | |
staticbunny | my intel card was no problem to install. 0004:41:00.0 Network controller: Intel Corporation Wi-Fi 7(802.11be) AX1775*/AX1790*/BE20*/BE401/BE1750* 2x2 (rev 1a) just had to find the right driver | 17:09 |
+ jacobk (~quassel@47-186-105-237.dlls.tx.frontiernet.net) | 17:14 | |
+ glu__ (~glu@91.141.52.220.wireless.dyn.drei.com) | 17:24 | |
- glu (QUIT: Ping timeout: 272 seconds) (~glu@77.119.213.90.wireless.dyn.drei.com) | 17:24 | |
* glu__ -> glu | 17:24 | |
- Twodisbetter (QUIT: Quit: Gateway shutdown) (2cc0e4ea1c@irc.cheogram.com) | 17:44 | |
- SavagePeanut (QUIT: Quit: Gateway shutdown) (59eaa45ac7@irc.cheogram.com) | 17:44 | |
+ chomwitt (~chomwitt@2a02:587:7a16:a200:1ac0:4dff:fedb:a3f1) | 17:48 | |
- bkeys (QUIT: Remote host closed the connection) (~Thunderbi@72.sub-97-150-200.myvzw.com) | 17:53 | |
+ SavagePeanut (59eaa45ac7@irc.cheogram.com) | 17:56 | |
+ bkeys (~Thunderbi@72.sub-97-150-200.myvzw.com) | 17:58 | |
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:20) | 18:00 | |
- chomwitt (QUIT: Ping timeout: 248 seconds) (~chomwitt@2a02:587:7a16:a200:1ac0:4dff:fedb:a3f1) | 18:09 | |
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@72.sub-97-150-200.myvzw.com) | 18:24 | |
+ bkeys (~Thunderbi@72.sub-97-150-200.myvzw.com) | 18:24 | |
vagrantc | hrm. after flipping over my newly refreshed mnt/reform a few times, the circle key on the keyboard seems to be snagging on something | 18:26 |
vagrantc | and for some reason, ethernet does not register a link ... the OS shipped on the eMMC registers the ethernet link just fine, but not my install on NVMe. FWIW the linux 6.11.x kernel from reform.debian.net does work! :) | 18:28 |
vagrantc | my NVMe install is pretty much just Debian with a few manually hand-picked stuff from reform-tools ... because, well, gotta shoot myself in the foot now and again | 18:28 |
ch | iirc reform-tools does some resetting of the ethernet links | 18:29 |
vagrantc | was there any special tweaks with the rk3588 needed for the ethernet to work? | 18:29 |
ch | s/links/link/ | 18:29 |
vagrantc | ok, i'll take a look at what it does. | 18:29 |
ch | https://source.mnt.re/reform/reform-tools/-/blame/main/sbin/reform-hw-setup?ref_type=heads#L49 | 18:30 |
vagrantc | so much the better :) | 18:30 |
ch | should probably understand why thats necessary | 18:30 |
vagrantc | oh wow, what a hack. :/ | 18:30 |
ch | yes :/ | 18:30 |
josch | vagrantc: do you have gpiod >= 2.0? | 18:30 |
vagrantc | josch: not sure, it's still a bookworm install | 18:31 |
josch | ch: yes, your tool being in python makes a difference | 18:31 |
josch | vagrantc: then i guess we need a gpiod backport for rk3588 | 18:32 |
josch | ch: you now have the "maintainer" role for reform-tools -- so now, if you like, nothing stops you from adding your tool to it :) | 18:35 |
vagrantc | oh wow, hdmi output works out of the box. | 18:36 |
ch | https://source.mnt.re/reform/reform-debian-packages/-/merge_requests/67/diffs | 18:36 |
vagrantc | which means i could finally use this to present at conferences, maybe ... :) | 18:37 |
ch | would be nice if that (well the reverse) could be made to work :/ | 18:37 |
ch | josch: cool, i'll see about making an MR. then i hope we can move forward with the usbids | 18:38 |
josch | nice :) | 18:38 |
ch | is dt-overlay support now in mainline? | 18:42 |
vagrantc | i think debian still does not enable dt-overlay support in the kernel... but from vague memory it is upstream | 18:43 |
hramrach | from vague memory it's still done in u-boot. There is the infrastructure in mainline but because 'something could break' there is no userspace API for it | 18:51 |
hramrach | the 'something' being drivers keeping references to memory pointing inside the DT because it won't ever go away without overlay support .. if you are not on powerpc .. .. | 18:52 |
- SavagePeanut (QUIT: Ping timeout: 255 seconds) (59eaa45ac7@irc.cheogram.com) | 19:01 | |
ch | josch: https://source.mnt.re/reform/reform-tools/-/merge_requests/101 let me know what you think | 19:03 |
hramrach | nice | 19:05 |
minute | yay @ landing of reform-mcu-tool! | 19:11 |
+ SavagePeanut (59eaa45ac7@irc.cheogram.com) | 19:12 | |
- jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-105-237.dlls.tx.frontiernet.net) | 19:30 | |
+ jacobk (~quassel@47-186-105-237.dlls.tx.frontiernet.net) | 19:31 | |
vagrantc | josch: it definitely needs a recent version og gpiod? if so, i can take a quick look at what it might take to backport | 19:34 |
+ mark_ (~mjw@gnu.wildebeest.org) | 19:40 | |
- bkeys (QUIT: Remote host closed the connection) (~Thunderbi@72.sub-97-150-200.myvzw.com) | 19:52 | |
+ bkeys (~Thunderbi@72.sub-97-150-200.myvzw.com) | 19:52 | |
- _justin_kelly (QUIT: Read error: Connection reset by peer) (~justinkel@user/justin-kelly/x-6011154) | 20:21 | |
+ _justin_kelly0 (~justinkel@user/justin-kelly/x-6011154) | 20:22 | |
ch | minute: how did you get gnome-firmware to work? did you install fwupd + gnome-firmware from source then? | 20:23 |
+ chomwitt (~chomwitt@2a02:587:7a16:a200:1ac0:4dff:fedb:a3f1) | 20:25 | |
vagrantc | is it reasonable to expect the mnt reform 2 rk3588 to recover from suspend? | 20:30 |
vagrantc | ACTION just testing the waters again | 20:30 |
vagrantc | as does the rk3588 u-boot variant support loading kernel, initrd, etc. from NVMe? | 20:32 |
vagrantc | and serial console ... on the same pins? ... different speed or something? (rockchip tends to do 1500000 baud, at least on several other boards) | 20:33 |
ch | iirc you need the 1500000 baud | 20:34 |
minute | ch: no, gnome-firmware from apt, fwupd from source | 20:39 |
minute | ch: i disabled the fwupd that got pulled in by debian | 20:39 |
minute | ch: and maybe i ran gnome-firmware from inside the fwupd venv | 20:40 |
* mjw -> Guest568 | 20:45 | |
- Guest568 (QUIT: Killed (molybdenum.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 20:45 | |
* mark_ -> mjw | 20:45 | |
+ Guest568 (~mjw@2001:1c06:2486:a800:7602:5eff:dc71:a72c) | 20:45 | |
ch | ah. kinda obvious that gnome-firmware can just use the old libfwupd to talk to the newer fwupd | 20:58 |
ch | thanks for the hint | 20:58 |
+ paperMan1 (~paperManu@107.159.243.8) | 21:02 | |
minute | ch: yeah it worked for me :D | 21:04 |
- paperManu (QUIT: Ping timeout: 265 seconds) (~paperManu@107.159.243.8) | 21:05 | |
- _justin_kelly0 (QUIT: Read error: Connection reset by peer) (~justinkel@user/justin-kelly/x-6011154) | 21:05 | |
+ _justin_kelly (~justinkel@user/justin-kelly/x-6011154) | 21:08 | |
- _justin_kelly (QUIT: Read error: Connection reset by peer) (~justinkel@user/justin-kelly/x-6011154) | 21:23 | |
vagrantc | josch: fwiw, libgpiod backport at least builds trivially ... might be some quirks due to the 64-bit time transition stuff, though (although arm64 is not technically affected, package name shifts, etc.) | 21:24 |
+ _justin_kelly (~justinkel@user/justin-kelly/x-6011154) | 21:25 | |
vagrantc | huh. ended up with reproducible builds differences, and i wasn't even trying ... oh ... probably build paths | 21:27 |
- _justin_kelly (QUIT: Read error: Connection reset by peer) (~justinkel@user/justin-kelly/x-6011154) | 21:53 | |
+ _justin_kelly (~justinkel@user/justin-kelly/x-6011154) | 21:55 | |
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@72.sub-97-150-200.myvzw.com) | 22:04 | |
- shdw (QUIT: Ping timeout: 252 seconds) (~shdw@static.218.156.216.95.clients.your-server.de) | 22:08 | |
josch | vagrantc: next sbuild upload will have /build/reproducible-path for all builds | 22:10 |
+ shdw (~shdw@static.218.156.216.95.clients.your-server.de) | 22:13 | |
- gustav28 (QUIT: Quit: Quit) (~gustav@c-78-82-52-175.bbcust.telenor.se) | 22:15 | |
vagrantc | josch: ooooh! | 22:15 |
- _justin_kelly (QUIT: Read error: Connection reset by peer) (~justinkel@user/justin-kelly/x-6011154) | 22:28 | |
+ _justin_kelly (~justinkel@user/justin-kelly/x-6011154) | 22:30 | |
josch | vagrantc: it will come with a big fat NEWS entry, so maybe there will be opposition but i guess you'll read about that if that should happen :) | 22:31 |
- jacobk (QUIT: Ping timeout: 260 seconds) (~quassel@47-186-105-237.dlls.tx.frontiernet.net) | 22:35 | |
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:20) | 22:37 | |
- chrcav (QUIT: Ping timeout: 276 seconds) (~chrcav@user/chrcav) | 22:47 | |
+ chrcav (~chrcav@user/chrcav) | 22:48 | |
- paperMan1 (QUIT: Ping timeout: 252 seconds) (~paperManu@107.159.243.8) | 22:58 | |
+ paperManu (~paperManu@107.159.243.8) | 22:59 | |
josch | minute: reform-compstat has no copyright header -- did you write it from scratch or does it come from elsewhere? | 23:14 |
minute | josch: ohhh that can go away | 23:19 |
minute | josch: it's not in use for a long time | 23:19 |
minute | josch: i think i wrote this myself but it's so long ago i don't remember the details | 23:21 |
minute | tried to search for some code snippets of that in github and google and can't really find anything meaningful where i could have stolen this from | 23:22 |
josch | minute: i'm still using and improving it, that's why i'm asking :) | 23:22 |
minute | ohh | 23:23 |
josch | i'm now letting it show CPU utilization for all my six cores (one bar each) | 23:23 |
minute | josch: if you want you can add a GPLv3+ header with mnt copyright :DD | 23:23 |
minute | and your own of course | 23:23 |
josch | okay, will do, thank you! | 23:23 |
minute | nice @ 6 cores | 23:24 |
+ bkeys (~Thunderbi@45.134.140.153) | 23:39 | |
josch | there it is | 23:40 |
josch | it's from commit f3c66507bc6db4e61ba1ee01490cab8f3166119c in reform-system-image | 23:40 |
josch | in 2020 | 23:40 |
staticbunny | can someone share the command thats in /etc/greetd/config.yaml | 23:40 |
josch | staticbunny: you probably mean /etc/greetd/config.toml? | 23:41 |
staticbunny | yeah | 23:41 |
staticbunny | is it "command = "/usr/bin/tuigreet --window-padding 4 --remember --asterisks --cmd /usr/bin/wayfire" | 23:42 |
josch | taht looks okay | 23:42 |
josch | the reform-setup-wizard sets it to: command = "/usr/bin/tuigreet --window-padding 4 --remember --asterisks --cmd /usr/bin/${DESKTOP}" | 23:43 |
josch | where $DESKTOP is sway or wayfire | 23:43 |
staticbunny | for some reason dpkg or apt wiped mind | 23:43 |
staticbunny | *mine | 23:43 |
staticbunny | so im just working to restore it | 23:43 |
josch | if that happened, then that's a really bad bug | 23:43 |
josch | can you reproduce it? | 23:43 |
josch | if you have details how it happened i'd like to hear them | 23:44 |
staticbunny | i'll try and go back through my history and see if anything sticks out | 23:44 |
- bkeys (QUIT: Ping timeout: 252 seconds) (~Thunderbi@45.134.140.153) | 23:45 | |
josch | staticbunny: how did it "wipe" it? the file is just gone? | 23:46 |
+ bkeys1 (~Thunderbi@45.134.140.153) | 23:46 | |
staticbunny | it created config.toml.dpkg-old but the command was slightly off | 23:46 |
staticbunny | i also made some tweaks playing with the theme, so wanted to know the actual default command the wizard sets | 23:47 |
* bkeys1 -> bkeys | 23:48 | |
josch | staticbunny: if there is a config.toml.dpkg-old then that is a hint that another package tried to install a config.toml | 23:48 |
josch | staticbunny: can you run this command and see what shows up: dpkg-query --search /etc/greetd/config.toml | 23:49 |
ch | greetd updated its config file in a recent update | 23:49 |
ch | if you accept the new version, you get the new version | 23:49 |
josch | well... if that is what happens, then staticbunny probably would know? | 23:50 |
staticbunny | that would have done it, because i did an upgrade and this happened right around that time | 23:50 |
josch | oh | 23:50 |
josch | sure, if you told dpkg to overwrite your config then it will override your config :) | 23:50 |
staticbunny | ive been doing a lot over ssh, so it wasnt apparent right away | 23:50 |
josch | it should offer you a diff between your current config and the new config | 23:50 |
staticbunny | i might have ran apt install upgrade and walked away =D | 23:51 |
staticbunny | i was trying to figure out my ntp issue | 23:52 |
staticbunny | which im suprised hasnt come up more. I think apparmor is blocking ntp or there is some other weirdness doing on. | 23:53 |
staticbunny | https://community.mnt.re/t/pocket-reform-is-not-keeping-time-anymore/2231/7 | 23:54 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!