2025-12-08.log

+ schalken (~schalken@117-118-178-69.gci.net)00:11
+ bkeys (~Thunderbi@75.sub-174-229-20.myvzw.com)00:14
- pomel0 (QUIT: Ping timeout: 264 seconds) (~pomel0@user/pomel0)00:16
+ pomel0 (~pomel0@user/pomel0)00:16
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@75.sub-174-229-20.myvzw.com)00:23
+ bkeys (~Thunderbi@75.sub-174-229-20.myvzw.com)00:24
+ bkeys1 (~Thunderbi@h193.131.19.98.dynamic.ip.windstream.net)00:25
- bkeys (QUIT: Read error: Connection reset by peer) (~Thunderbi@75.sub-174-229-20.myvzw.com)00:27
* bkeys1 -> bkeys00:28
- pomel0 (QUIT: Ping timeout: 246 seconds) (~pomel0@user/pomel0)00:35
+ pomel0 (~pomel0@user/pomel0)00:35
- bkeys (QUIT: Ping timeout: 264 seconds) (~Thunderbi@h193.131.19.98.dynamic.ip.windstream.net)00:35
- chomwitt (QUIT: Ping timeout: 264 seconds) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)02:09
- vagrantc (QUIT: Quit: leaving) (~vagrant@2600:3c01:e000:21:7:77:0:50)02:25
- schalken (QUIT: Ping timeout: 264 seconds) (~schalken@117-118-178-69.gci.net)02:34
+ schalken (~schalken@117-118-178-69.gci.net)02:36
- robin (QUIT: Quit: Leaving) (~robin@user/terpri)03:37
- colinsane (QUIT: Quit: bye) (~colinunin@97-113-73-113.tukw.qwest.net)05:10
+ colinsane (~colinunin@97-113-73-113.tukw.qwest.net)05:13
+ chomwitt (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)06:28
- Ar|stote|is (QUIT: Quit: No Ping reply in 180 seconds.) (~linx@149.210.3.83)07:59
- lidstah (QUIT: Remote host closed the connection) (~lidstah@gateway/tor-sasl/lidstah)08:04
+ lidstah (~lidstah@gateway/tor-sasl/lidstah)08:04
+ Ar|stote|is (~linx@149.210.3.83)08:05
- Ar|stote|is (QUIT: Ping timeout: 260 seconds) (~linx@149.210.3.83)08:51
+ Ar|stote|is (~linx@149.210.3.83)08:55
- chomwitt (QUIT: Ping timeout: 265 seconds) (~chomwitt@2a02:85f:9a5f:900:1ac0:4dff:fedb:a3f1)09:13
- nybble (QUIT: Ping timeout: 260 seconds) (~sprang@user/csprng)11:06
- mjw (QUIT: Quit: Leaving) (~mjw@gnu.wildebeest.org)11:07
lidstahHi all, I was wondering, but can I use my thinkpad 65W usb-c charger with the reform classic? (it should, but I just want to be sure)11:25
joschlidstah: if you either have motherboard 3.0 or if you have a usb-c to barrel jack adapter (for older motherboards) then yes11:35
- aelius (QUIT: Ping timeout: 246 seconds) (~aelius@user/aelius)11:35
lidstahHey josch, thanks :) - I don't have the reform right now - my order is from mid-october so , reading the november news/recap, I should have the motherboard 3.0 with the usb-c PD and PCIe 4x NVMe slot (which is really neat!), and it should be delivered around february (3/4 monthes after order per november news). But I was shopping for an NVMe drive and wondered if I should get a usb-c PD 65W+11:42
lidstahcharger or if I could use the thinkpad usb-c power brick I already have (in fact, I even have two of them, one for my x13 and one for my partner X390). Better safe than sorry, although they should be pretty standard :)11:42
joschlidstah: here is the lenovo usb adapter which works for motherboard 3.0 here:11:45
joschADLX65YCC3D11:45
joschalso works: ADLX65YLC3D11:46
lidstahmmh, going downstairs to check, but looks like my charger :) thanks alot josch !11:47
gordon1ffs third WD SSD turned itself into a pumpkin, that feels like trend now11:49
gordon1and it is always with rk3588 (either rock 5b+, or, today, reform), feeling that people here reporting wd blue being absolutely fine i'm starting to wonder if that's either pci PM features that i enforce or it's because of heatsink i use?11:51
gordon1wd blue turns into this https://0x0.st/KwYX.txt11:52
lidstahhttps://celeano.lidstah.info/-ZxustMKhwb/IMG_20251208_114911713_MFNR.jpg << great, it's an ADLX65YCC3D :)11:53
+ chomwitt (~chomwitt@2a02:85f:9a67:8b00:1ac0:4dff:fedb:a3f1)11:55
amospallaI just saw reform-tools 1.82 appear in my Pocket with Debian stable :D12:08
grimmwareniiiiice12:08
- _justin_kelly71 (QUIT: Quit: The Lounge - https://thelounge.chat) (~justinkel@user/justin-kelly/x-6011154)12:11
joschamospalla: stable-backports :)12:13
amospallathank you !12:14
joschgordon1: i have 81 TB written on my WDC WDS100T2B0C-00PXH0 (because a311d with 3.6 GB of ram and 8 Gigs of swap on the disk)12:16
josch2.8 years of power-on in my classic reform, nice :)12:17
joschgordon1: but that was first with imx8mq and then with a311d, not with rk358812:17
gordon1josch: i definitely have single failure mode with those, they all turn into this SANDISK POLARIS ROM MODE12:21
joschand then all data lost?12:21
gordon1yep, 0 capacity12:21
gordon1cannot read or write12:21
joschwow12:22
joschlet this be a reminder for all of us to do regular backups... rip :(12:22
amospallareform-check states my u-boot on Pocket/rk3588 could be upgraded, from 2024.10-g424c714eb247-dirty to 2025-11-04. Does upgrade add any new feature?12:22
amospallabackups are a pain to do somethimes, specially with some devices, but yeah, a must.12:23
gordon1josch: worst story was the previous, when both wd blacks died at the same moment in my rock 5b+, two wd blacks that were in raid112:23
joschamospalla: yes, the newer u-boot gives you serial output via uart on rk3588 by default12:23
gordon1good that i _did_ did backups12:23
joschgordon1: no way o012:24
gordon1it happens during reboot or power-cycle12:25
amospallanice, that's good :)12:25
gordon1that said, wd black in my steamdeck feels perfectly fine and clocks second year of life so i guess it is something that i'm doing12:25
gordon1i mean it is both probably, bug in wds and me who triggers it somehow12:26
joschamospalla: that being said, unless you want the serial thing, maybe you want to hold off with upgrading until the next version is getting tagged soon12:26
amospallajosch: thank you, I'll wait.12:26
joschthe nicest upgrade for me with the newer u-boot versions is the consistent version reporting12:27
josch2024.10-g424c714eb247-dirty does not say much12:27
amospallaI had serial output a couple months ago, it was adding something to the kernel boot args (something that now I added to u-boot-menu to make permanent).12:27
joschrecent u-boot versions tell you the MNT version and then reform-check can compare versions instead of just comparing hashes and telling you "well it's different but no idea which u-boot version that is"12:27
joschamospalla: yes, with the new u-boot it works out of the box without having to add a tty argument12:28
joschconsole=ttyS2,150000012:28
joschthat was missing12:28
amospallathat's good :)12:28
amospallajust chit-chatting, because I use emmc (fast and plenty on rcore for me), I moved my user home folder to gocryptfs. Moderately easy, add a line to pam.mount, create the encrypted folder with your user login password, and move files. But it does not like hard reboots and corrupts files.12:31
amospallaA couple weeks ago, looked for an alternative, and tried fscrypt. Much better. Just install the pam fscrypt package, create the encrypted folder and move files.12:33
lidstahgordon1: looks like you're not the only one with similar issues with WD Blue and black: https://www.reddit.com/r/HomeNAS/comments/1frmlb8/friendlyelec_cm3588_nvme_issues/ - I'm wondering if it's due to what the first comment explained (lack of AC coupling capacitor compared to other brands).12:57
+ gustav25 (~gustav@c-78-82-54-48.bbcust.telenor.se)13:02
gordon1lidstah: yeah, i saw that thread, but then at least some of the users of the reform should have same issue with wd blues and they're not13:03
lidstahor maybe related to the RK3588 PCIe lanes? https://taoofmac.com/space/blog/2024/10/26/1900 << that's a CM3588, and the writer experienced similar problems (3 of 4 drives died)13:10
* Guest2303 -> mjw13:52
+ paperManu (~paperManu@modemcable141.205-200-24.mc.videotron.ca)14:41
+ bkeys (~Thunderbi@92.sub-174-218-50.myvzw.com)14:47
- pomel0 (QUIT: Read error: Connection reset by peer) (~pomel0@user/pomel0)15:03
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@92.sub-174-218-50.myvzw.com)15:04
+ bkeys (~Thunderbi@92.sub-174-218-50.myvzw.com)15:04
- bkeys (QUIT: Ping timeout: 244 seconds) (~Thunderbi@92.sub-174-218-50.myvzw.com)15:11
+ bkeys (~Thunderbi@98.19.131.193)15:13
- bkeys (QUIT: Ping timeout: 244 seconds) (~Thunderbi@98.19.131.193)15:17
+ bkeys (~Thunderbi@98.19.131.193)15:18
- bkeys (QUIT: Client Quit) (~Thunderbi@98.19.131.193)15:19
- Ar|stote|is (QUIT: Read error: Connection reset by peer) (~linx@149.210.3.83)15:28
+ Ar|stote|is (~linx@149.210.3.83)15:34
- MartiniMoe (QUIT: Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) (~quassel@user/MartiniMoe)15:58
+ MartiniMoe (~quassel@user/MartiniMoe)15:58
- Ar|stote|is (QUIT: Ping timeout: 264 seconds) (~linx@149.210.3.83)16:51
+ Ar|stote|is (~linx@149.210.3.83)16:55
+ andreas-e (~Andreas@2a02-8434-b6a3-e901-facc-8e87-8e54-890d.rev.sfr.net)16:58
+ wielaard (~mjw@gnu.wildebeest.org)17:05
- Ar|stote|is (QUIT: Quit: No Ping reply in 180 seconds.) (~linx@149.210.3.83)17:13
+ Ar|stote|is (~linx@149.210.3.83)17:14
- paperManu (QUIT: Ping timeout: 240 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca)17:16
+ paperManu (~paperManu@modemcable141.205-200-24.mc.videotron.ca)17:18
- cow321 (QUIT: Ping timeout: 240 seconds) (~deflated8@user/meow/deflated8837)17:41
+ cow321 (~deflated8@user/meow/deflated8837)17:44
+ AnimaInvicta (~AnimaInvi@88-120-179-216.subs.proxad.net)18:17
- Ar|stote|is (QUIT: Ping timeout: 244 seconds) (~linx@149.210.3.83)18:36
- mrbcmorris (QUIT: Ping timeout: 264 seconds) (~mrbcmorri@1513413-static.lxtnkya3.metronetinc.net)18:41
+ mrbcmorris (~mrbcmorri@1513413-static.lxtnkya3.metronetinc.net)18:42
+ nybble (~sprang@user/csprng)18:59
jfredeep, I use a WD blue in my big reform... time to get backups going19:02
+ Ar|stote|is (~linx@149.210.3.83)19:11
+ aelius (~aelius@user/aelius)19:12
* mjw -> Guest36119:19
- Guest361 (QUIT: Killed (molybdenum.libera.chat (Nickname regained by services))) (~mjw@2001:1c06:2486:a800:a09a:fc1c:5a8:e74d)19:19
* wielaard -> mjw19:19
+ Guest361 (~mjw@2001:1c06:2486:a800:a09a:fc1c:5a8:e74d)19:20
minutegordon1: jfred: josch: you probably googled this error and the possible fixes? (sandisk polaris rom mode)19:26
gordon1minute: i googled it and it yielded only that reddit post19:26
joschno clue -- my wd blue never had any problems19:27
+ user47384 (~Guest75@128.205.160.74)19:27
josch(but i also never used it with rk3588 like gordon1)19:28
gordon1i found no fixes and i returned my previous 2x wd blacks already, however wd blue recovered after a while and now i have a theory that i potentially can try to nvme fw-log upload its own firmware and see if that does anything, i will definitely try it next time it craps out19:28
gordon1since i assume it for some reason cannot read its own firmware?19:30
gordon1(or maybe connection to the flash chip is lost or something)19:30
gordon1ACTION going to keep his reform powered on until new ssd arrives 19:31
- user47384 (QUIT: Quit: Client closed) (~Guest75@128.205.160.74)19:53
- Ar|stote|is (QUIT: Ping timeout: 260 seconds) (~linx@149.210.3.83)19:55
+ pomel0 (~pomel0@user/pomel0)20:13
+ vagrantc (~vagrant@2600:3c01:e000:21:7:77:0:50)20:18
- jogu (QUIT: Remote host closed the connection) (~jogu@user/jogu)20:18
+ jogu (~jogu@user/jogu)20:19
- paperManu (QUIT: Ping timeout: 244 seconds) (~paperManu@modemcable141.205-200-24.mc.videotron.ca)20:25
- jogu (QUIT: Remote host closed the connection) (~jogu@user/jogu)20:28
+ jogu (~jogu@user/jogu)20:29
- pomel0 (QUIT: Remote host closed the connection) (~pomel0@user/pomel0)20:30
+ pomel0 (~pomel0@user/pomel0)20:30
- jogu (QUIT: Remote host closed the connection) (~jogu@user/jogu)20:31
+ jogu (~jogu@user/jogu)20:32
- jogu (QUIT: Remote host closed the connection) (~jogu@user/jogu)20:36
+ jogu (~jogu@user/jogu)20:37
- jogu (QUIT: Remote host closed the connection) (~jogu@user/jogu)20:38
+ jogu (~jogu@user/jogu)20:39
- jogu (QUIT: Remote host closed the connection) (~jogu@user/jogu)20:42
+ jogu (~jogu@user/jogu)20:43
+ Ar|stote|is (~linx@149.210.3.83)20:48
- jogu (QUIT: Remote host closed the connection) (~jogu@user/jogu)20:53
gordon1minute: https://www.friendlyelec.com/index.php?route=product/product&product_id=294 has a big disclaimer about WD now, it also refers to critical firmware update for aformentioned drives and I can assure that both my wd blacks and wd blue had latest available firmware20:53
gordon1something to keep an eye on, just in case20:53
+ jogu (~jogu@user/jogu)20:54
- jogu (QUIT: Remote host closed the connection) (~jogu@user/jogu)20:55
+ jogu (~jogu@user/jogu)20:56
- jogu (QUIT: Remote host closed the connection) (~jogu@user/jogu)20:59
+ bkeys (~Thunderbi@98.19.131.193)21:00
+ jogu (~jogu@user/jogu)21:01
- bkeys (QUIT: Ping timeout: 265 seconds) (~Thunderbi@98.19.131.193)21:08
+ bkeys (~Thunderbi@h193.131.19.98.dynamic.ip.windstream.net)21:14
+ spew (~spew@user/spew)21:22
- AnimaInvicta (PART: !!unknown attribute: msg!!) (~AnimaInvi@88-120-179-216.subs.proxad.net)21:35
sigridI have SN570 which I assume does not suffer the same problem21:35
gordon1i think i have exhaustive list here in my lspci :)21:39
gordon10001:11:00.0 Non-Volatile memory controller: Sandisk Corp WD SN560/SN740/SN770/SN5000 NVMe SSD (rev 01)21:39
gordon1so far sn770 and sn5000 did die21:39
sigridthat's quite sad. I try to keep firmware updated just in case but WD makes it quite hard21:42
gordon1sigrid: i followed the guide here, you can easily download unencrypted firmware for any of their nvme https://wiki.archlinux.org/title/Solid_state_drive/NVMe#Western_Digital21:42
gordon1with samsung it is a bit more of a PITA21:43
- bkeys (QUIT: Ping timeout: 240 seconds) (~Thunderbi@h193.131.19.98.dynamic.ip.windstream.net)21:44
gordon1but hopefully i don't need to update it21:44
- Ar|stote|is (QUIT: Ping timeout: 246 seconds) (~linx@149.210.3.83)21:44
sigridthat's the guide I use as well21:44
gordon1and for the record i did update wd black's fw, wd blue came with the latest fw out of the box21:45
- pomel0 (QUIT: Remote host closed the connection) (~pomel0@user/pomel0)21:48
- schalken (QUIT: Quit: Leaving) (~schalken@117-118-178-69.gci.net)21:53
+ Ar|stote|is (~linx@149.210.3.83)21:55
+ paperManu (~paperManu@107.159.15.124)21:55
+ paperManu_ (~paperManu@107.159.15.124)21:57
+ pomel0 (~pomel0@user/pomel0)21:58
+ schalken (~schalken@117-118-178-69.gci.net)22:06
- gustav25 (QUIT: Quit: Quit) (~gustav@c-78-82-54-48.bbcust.telenor.se)22:15
- Ar|stote|is (QUIT: Ping timeout: 245 seconds) (~linx@149.210.3.83)22:24
- spew (QUIT: Quit: nyaa~) (~spew@user/spew)22:46
+ bkeys (~Thunderbi@92.sub-174-218-50.myvzw.com)23:08
- andreas-e (QUIT: Quit: Leaving) (~Andreas@2a02-8434-b6a3-e901-facc-8e87-8e54-890d.rev.sfr.net)23:10
+ bkeys1 (~Thunderbi@h193.131.19.98.dynamic.ip.windstream.net)23:13
- bkeys (QUIT: Quit: With every step we take, danger will follow closely) (~Thunderbi@92.sub-174-218-50.myvzw.com)23:15
+ bkeys (~Thunderbi@92.sub-174-218-50.myvzw.com)23:15
- bkeys1 (QUIT: Ping timeout: 264 seconds) (~Thunderbi@h193.131.19.98.dynamic.ip.windstream.net)23:18
+ Ar|stote|is (~linx@149.210.3.83)23:20
minutegordon1: very strange @ friendlyelec + wd23:25
minutei personally never encountered this problem yet23:31
+ elb (~elb@2600:4041:6682:ea00:b353:7898:87f:f2aa)23:33
- chomwitt (QUIT: Ping timeout: 244 seconds) (~chomwitt@2a02:85f:9a67:8b00:1ac0:4dff:fedb:a3f1)23:40
+ bkeys1 (~Thunderbi@92.sub-174-218-50.myvzw.com)23:50
- bkeys (QUIT: Ping timeout: 240 seconds) (~Thunderbi@92.sub-174-218-50.myvzw.com)23:51
* bkeys1 -> bkeys23:51
gordon1well, i hope not 100% of wds are affected, or you have some slightly different model or something23:54
gordon1hard to judge with n=3-523:55

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