<farkuhar>
SiFuh this is how your bread recipe turned out, in a climate very different from Malaysia: https://snipboard.io/8YPkaM.jpg
<farkuhar>
I was mistaken in my initial impression that the dough would be too dry. I actually had to add another cup of flour, and even then it was so sticky it almost didn't detach from the pan.
<SiFuh>
farkuhar: hmm that link isn't working
<farkuhar>
SiFuh: that site doesn't play nicely with my browser. Try here instead https://imgur.com/TWLbCsY
<SiFuh>
Okay that worked
<SiFuh>
Oh, I forgot to mention it is for plain white flour.
ppetrov^ has joined #crux
lavaball has joined #crux
<farkuhar>
SiFuh: whole wheat flour is all I had, so that's what I used. Anyway, it tastes great, even though the texture is not as fluffy as what you're used to.
<SiFuh>
Yeah, that explains why it was so sticky then
<SiFuh>
farkuhar: I made the recipe to follow the cheap easily available plain flour here in Malaysia. The time is not specific for proofing either. I tell just by lookng at it so it can take 20 minutes to over an hour or two. When done it should be super fluffy.
stoffepojken has quit [Read error: Connection reset by peer]
stoffepojken has joined #crux
stoffepojken has quit [Read error: Connection reset by peer]
stoffepojken has joined #crux
stoffepojken has quit [Ping timeout: 255 seconds]
stoffepojken has joined #crux
<farkuhar>
Yeah, Steffen isn't responsible for the keys currently listed on crux.nu, even though at one point he might have had admin rights on that host.
<SiFuh>
Wasn't there a mention of it in the past and Steffen informed CRUX of it?
<farkuhar>
SiFuh: one of your links regarding nvme-cli led to this interesting claim: "If your SSD is from Lenovo, it'll be locked out. Even the newest Parted Magic can't factory erase it. Gotta use ThinkPad Drive Erase Utility ..."
<SiFuh>
The link I mentioned before that I can't find, shows you how to unlock the drive then secure erase and then lock again.
<SiFuh>
Wonder if it works on Lenovo
<farkuhar>
Just confirmed on a secondhand ThinkPad. The exact error message reads "NVMe status: ACCESS_DENIED. Access to the namespace and/or LBA range is denied due to lack of access rights (0x4286)"
<SiFuh>
Yep that is the one
<SiFuh>
You must unlock it first
<SiFuh>
I don't know why I am thinking of this, but I think hdparm is the program to unlock it
stoffepojken has quit [Ping timeout: 240 seconds]
<SiFuh>
I think but... damn wish I had that site back.
<farkuhar>
I thought hdparm only spoke SATA.
<SiFuh>
Yeah but... fscking hell. I really need to pull up that guys site.
<SiFuh>
I remember my drive was locked, and I had a n access denied but following this guys page I was able to unlock it, secure erase, lock it and move on
<SiFuh>
Actually if I remember correctly after secure erase it was automatically locked again.
<jaeger>
Updated stenur.pub on crux.nu
<farkuhar>
So you had to unlock it twice? Or you left in place the automatic lock after secure erase, since the drive was still usable in that state?
stoffepojken has joined #crux
<SiFuh>
I had to erase a key to unlock it I think. Then secure erase and after secure erase it was locked again but securely erased
<SiFuh>
ukky: ^
<jaeger>
That kinda sounds more like ATA behavior than NVMe, weirdly
<SiFuh>
I scanned through Telegram messages for hdparm and found it.
<SiFuh>
And worse still, no nvme-cli mentioned at all
<jaeger>
Makes sense
<SiFuh>
Yeah, that I am freaking moron. Hahah
<jaeger>
Nah, just that memory isn't 100% perfect
<SiFuh>
Wait, I have an SSD drive that starts with O, maybe I did it to that an not the NVME drive
<jaeger>
But I meant makes sense that it was hdparm in this case, matches up with the ATA vs. NVMe thing
<farkuhar>
Thanks for digging up the references, SiFuh, even if they don't apply to NVMe.
<SiFuh>
HAHAHA starts with T, jaeger it was the TEAM 1TB SATA3 M.2 SSD drive that I was doing that too.
<jaeger>
I recognize the name but haven't used any TEAM drives myself
<SiFuh>
farkuhar: It's been bugging me for a couple of days now. I have been gazing out the window thinking, WTF? Why? When? What words did I use? Whom had I notified about it? and so on.
<SiFuh>
jaeger: probably below average drives. But my CRUX machine is using it as a secondary drive. However, I think it failed already because I gent an ATA SDB error on boot
<SiFuh>
I didn't look into it because that machine is doing other crap and sits in the background melting the lamanex on the table
<farkuhar>
SiFuh: Glad I could inspire you to get the memories straightened out. Now you won't be surprised to hear that `hdparm -I /dev/nvme0n1` returns nothing (because hdparm doesn't speak NVMe).
<SiFuh>
To be honest, I haven't really done much on the CRUX side of things and I am just kind of running the machines into the groun.
<SiFuh>
ground*
<SiFuh>
farkuhar: It was both jaeger and you, don't take all the credit. Secondly I remember using nvme-cli for something... shit now I need to think about that.
<SiFuh>
Lujo is using an NVMe, SAMSUNG MZVLQ1T0
<SiFuh>
Oh wow, my main driver that is the one NVMe, Force MP510
<SiFuh>
It was the MP510 that I remember using the nvme-cli on
stoffepojken has quit [Read error: Connection reset by peer]
stoffepojken has joined #crux
<jaeger>
speaking of nvme...
<cruxbot>
[opt.git/3.7]: thunderbird-bin: updated to version 115.3.1
<cruxbot>
[opt.git/3.7]: nvme-cli: updated to version 2.6
<cruxbot>
[opt.git/3.7]: libnvme: updated to version 1.6
<cruxbot>
[contrib.git/3.7]: python3-psycopg2: updated to version 2.9.8
<SiFuh>
Heh
<SiFuh>
jaeger: and farkuhar: to make myself more ashamed https://i.snipboard.io/Kn5NYj.jpg Here is a screen shot of the actual messages
<jaeger>
oops, heh
<SiFuh>
Yeah, my thoughts exactly
stoffepojken has quit [Read error: Connection reset by peer]
stoffepojken has joined #crux
stoffepojken has quit [Read error: Connection reset by peer]
stoffepojken has joined #crux
ivandi has quit [Quit: WeeChat 4.0.5]
ivandi has joined #crux
farkuhar has left #crux [#crux]
lavaball has quit [Remote host closed the connection]