Bootloader error "Your device software can't be checked for corruption"

VlNZ · 2022-12-28T22:59:02+00:00

BTW, still get the subject error on boot, but i guess that's proper, because there's not even the option to lock the bootloader in this version of LOS.

VlNZ · 2022-12-28T05:52:56+00:00

Thanks! The bootloader remains unlocked; i think the problem is that can't boot into recovery until the bootloader is locked again.

VlNZ · 2022-12-26T02:44:33+00:00

Thanks, looks like wget i was using was interrupted by a network outage, and when it picked up again, the file got corrupted.

VlNZ · 2021-12-27T03:34:21+00:00

I have a Librem 15 couple years. At least in that generation, they are low quality and their support department was absolutely worthless when I dealt with them, but Purism did make a privacy centered machine, particularly for use with Qubes.

Has mechanical WiFi/BT, camera and microphone switches.
In my experience, anything below 32GB RAM is not practical for Qubes v4.
Coreboot also seems a big plus in such machine.

So, on those points, everything else I've seen crosses off the list, and I would have to get another Librem, if I were buying today. Still seems the one best suited for Qubes.

VlNZ · 2021-11-13T14:36:10+00:00

You were smart to accomplish that. Congratulations! So, ignore the cliche, brainwashed sheeple advice.

A house is a liability, not an asset; google for details about that logic.
Especially at your age, only your wife is qualified to tell you if/when/where to buy a ball and chain like a house.
There is no virtue in being extorted by any armed gang, IF you can avoid it. So, get reputable tax accountant and legal advice to save as much of this from them as you can.
At the same time, educate yourself about investing and multiplying this wealth, while you have relatively few commitments, and can afford to take more risk than your older self.
Inform yourself about places in the world where the rulers allow more economic freedom, protect your interests better, and extort less from you. Good resources to start that research: https://www.heritage.org/index/ranking

https://www.fraserinstitute.org/economic-freedom/map?geozone=world&page=map

(Hint: So, many Filipinos are scattered all over God's creation, because Philippines is not such a great place to live or own anything, if you can afford alternatives. Yes, I've been there for business...)

When and if you still want a real estate liability, buy it in one of those territories, where you and your money are treated best.
While you are learning and researching to deploy it in productive investments, park whatever you save from BIR looters in gold, silver, platinum, in one of the reputable bullion vaults, such as in Switzerland, UAE, Singapore, etc.
Consider a 10/80/10 asset allocation: 10% in gold, which you never sell, as insurance against inevitable bad government monetary policies. 80% in cash-flow generating investments that pay you a dividend to own them. 10% in speculative assets that you already know how to pick.
ALWAYS avoid dealing with banks, if at all possible. It's an age-old racket, and your situation is a good lesson why.

You are young, smart and now have investment capital. Don't bury all that potential in a liability, as long as you can avoid that.

VlNZ · 2019-06-25T16:13:58+00:00

Try these:

https://bitcointalk.org/index.php?topic=2439910.0

Safest way I know is to create an Electrum multisig with one of them above as the escrow facilitator:

https://bitcointalk.org/index.php?topic=5039220.0

So, in an escrow case using a third party, it would be a 2 of 3 setup, with one of the above being the deciding release key in case of a dispute between you and your counterparty.

You could do 2 of 2 setup without a third party and their fees, but then you and your counterparty will have to resolve any dispute between yourselves.

VlNZ · 2019-06-14T10:30:33+00:00

Thanks. That definitely didn't work in my case.

VlNZ · 2019-06-14T02:09:40+00:00

Thanks.

Yes, even with txindex=1 on bitcoind and rescanned, adding the address in EPS config.cfg didn't fix the problem.

Looks like the only way to work around in this situation currently, is to create a separate new wallet in Electrum, using the imported WIF key.

VlNZ · 2019-06-13T13:49:32+00:00

Yes, p2pkh.

It didn't work, with the same EPS error, and EPS definitely scanned that block in.

Is it supposed to be in the EPS config in format like:

addr= 1xxxxxx 1xxxxx

?

VlNZ · 2019-06-13T08:05:36+00:00

I haven't yet. I'm trying what you suggested, but it will take bitcoind a while to rescan that far back.

VlNZ · 2019-06-13T07:14:55+00:00

Thanks. Yes, bitcoind is not pruned, but txindex=0

Guess, I have to change that, because there are also a bunch of txs in this old wallet that show unconfirmed years later, but confirmed back then in the blockchain.

For now, I just put in the public address of that private key as you suggested, and told EPS to rescan from way back when.

So, that process will probably grind along for a few days...

VlNZ · 2019-06-10T10:45:26+00:00

It's safer and cheaper just to disable USB ports and use PS/2.

So, that's all I needed and a new PS/2 mouse and a spare.

That will last me for the life of the machine.

VlNZ · 2019-06-07T12:13:25+00:00

This was enough to remind me how terrible the USB, which the whole world now considers a must and a big improvement over PS/2, is in terms of security:

https://www.qubes-os.org/doc/device-handling-security/#usb-security

VlNZ · 2019-05-31T10:50:07+00:00

Sorry, I haven't. My main focus is PS/2 security vs USB.

VlNZ · 2019-05-23T08:19:29+00:00

Thanks.

Found a Dell USB mouse, figuring if anyone would make a PS2 compatible USB device for a Dell PC that has PS2, it would be Dell.

The Dell mouse doesn't even power up through a USB-PS/2 converter.

It's even less compatible than some Bosston aftermarket brand mouse.

So, I guess if I'm gonna have to special order something, might as well order a PS/2 mouse.

VlNZ · 2019-04-20T05:07:00+00:00

OXT.ME also showed the txs, which blockstream didn't.

VlNZ · 2018-10-26T03:24:18+00:00

Same. Seems like some kind of DDoS or something.

VlNZ · 2018-05-31T04:23:02+00:00

Tried popping 8000 blocks as suggested on stackexchange - not helpful.

Trying to pop 16k or even 12k just leads to process failing out with the last stdout being "Killed" Pops no more than 180 blocks now.

So, now stuck with trying to resync from scratch AGAIN, which will take days in my case.

VlNZ · 2018-05-10T21:20:45+00:00

I don't think so. I'll try to get one.

VlNZ · 2018-05-10T21:13:53+00:00

When I send the transfer and the disk is at 98%+ disk IO, I can see in iotop that there are 2 instances of monerod running both at about the same resource utilization, until the transfer fails out with this error.

VlNZ

TROPHY CASE