Re: My PC is crashing

[Jadi]

I suspect a bad IMG/ISO file. Have you checked its hash? or I suggest a
redownload, rewrite / check and new install.
Jadi

On Sat, May 11, 2024 at 1:04 AM Daniel Hejduk 
wrote:

> Hello again,
> I tried memtest and it passed :D
> But after some trying to debug it I found something the sudden shutdown
> corrupts disk.
> One particular file "/share/relink/kernel/GENERIC.MP/gap.o" was always
> corrupted.
> So it happens when kernel is relinking.
>
> How you told me I tried using i386 but it didn't boot by flashing it on
> USB nor using Ventoy.
> Ventoy will always prompt me "Maybe the image does not support X64 UEFI",
> so I tried enabling legacy but again nothing.
> Is there way to boot i386, or fix the relinking error?
>
> Thank you for helping me on my journey.
>
> Best regards,
> Daniel Hejduk
>
>
> 10. května 2024 9:33:59 SELČ, Stuart Henderson 
> napsal:
>
>> On 2024-05-10, Peter N. M. Hansteen  wrote:
>>
>>> On Fri, May 10, 2024 at 08:48:56AM +0200, Anders Andersson wrote:
>>>
>>>> Missing from the FAQ is IMO step 0: Run memtest over night to rule out
>>>> hard to debug hardware problems. It won't catch everything of course,
>>>> but it usually finds RAM issues which is its main job.
>>>>
>>>
>>>  That is a very valid point.
>>>
>>>  Bad RAM could very well be the cause of the problems described. And on
>>>  a side note, given that the memory allocation in OpenBSD is different than
>>>  what some other systems do, it is not unlikely that other systems never
>>>  or only rarely would hit the failing memory location while OpenBSD would,
>>>  more often.
>>>
>>
>> Yet it was able to do an install and relink the kernel while in the
>> installer. Also IME memory-related problems are more likely to result in
>> crashes rather than the machine shutting down. This doesn't completely
>> rule out memory problems, but it's more likely to result from a
>> difference between RAMDISK and GENERIC.MP kernels.
>>
>> First things first, Daniel:
>>
>> - if you used i386, try amd64 instead.
>>
>> - if you configured to run X in the installer, try without that.
>>
>> - try going back a release or two, is there any difference?
>>
>>

Re: Is there access to dm...@openbsd.org? / arm64 laptops

[Jadi Mirmirani]

Try:
https://dmesgd.nycbug.org/index.cgi?do=index=OpenBSD
Its an awesome list of people submitting their `dmesg`s whils using OpenBSD. 
Have not checked if the ones you mentioned are there or not. But its frequently 
updated.

Yours,
Jadi

> On Apr 27, 2024, at 11:55, Peter J. Philipp  wrote:
> 
> Hi,
> 
> I'm looking for a dmesg of an arm64 laptop, the time I think has come to
> mothball the apple macbook pro from early 2015 (my old laptop called spica),
> I could put a new battery in it but the 80 EUR is not worth it anymore.  I'm
> also gearing up for job interviews overseas in the summer where I need a 
> nice laptop.
> 
> Anyone have dmesgs of "Lenovo Thinkpad X13s Gen 1" or the Apple M1/M2?
> 
> I'd also like to know if you've used these and would like to discourage their
> purchase.
> 
> I'm looking at the snapdragon 16 GB lenovo, the price is not quite right but
> I think I can scrounge up the money begging someone in my family to help me
> finance it.
> 
> Best Regards,
> -pjp
> 

Re: Installing across two SSDs, encrypted

[Grégoire Jadi]

Joe Nelson  writes:

> Second, how do I get the OS to prompt me during startup for a
> passphrase, and mount the encrypted drive? (It's not the primary drive
> with the OS on it, which seems nonstandard.)

Checkout rc(8), in particular rc.local.

I've used something like:

echo 'adding encrypted home partition'
bioctl -c C -l ENCRYPTED_UID.k softraid0 && \
  fsck DECRYPTED_UID.a && \
  mount /home

Could be improved with a loop to retry in case you misstype the
passphrase.

Best,

-- 
gjadi
PGP : AF26 E9C2 A1C8 8D32 A868  4386 1373 5477 2B65 1894

opensmtpd: mta server-cert-check result="failure"

[Grégoire Jadi]

Hi misc@,

I send this mail just in case someone else encounter the issue.

On OpenBSD 6.8-stable, opensmtpd fails to upgrade to TLSv1.2 when
relaying mail to a host with a self-signed certificate.

- In maillog the error is:

mta tls ciphers=TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256
mta server-cert-check result="failure".

- Check with openssl:

openssl s_client -connect smtp.example.com:25 -starttls smtp

-> Verify return code: 20 (unable to get local issuer certificate)


Whereas the same command on OpenBSD 6.8-current returns:

-> Verify return code: 18 (self signed certificate)

Upgrading to OpenBSD 6.8-current fixes the issue.


Note that this is only an issue when enforcing tls verification in
smtpd.conf.  Otherwise, in my case, I ended-up being greylisted.

Thank you all for your work.

Best,

-- 
gjadi
PGP : AF26 E9C2 A1C8 8D32 A868  4386 1373 5477 2B65 1894

Re: lock X on suspend

[Grégoire Jadi]

Jeremie Courreges-Anglas  writes:
Hello,

> On Tue, Aug 15 2017, Stuart Henderson  wrote:
>> On 2017-08-15, Jeremie Courreges-Anglas  wrote:
>>> On Tue, Aug 15 2017, tomr  wrote:
>>>
 I've figured out an effective workaround I think, which is to SIGUSR1 my
 running xidle(1) process, which works.
>>>
>>> That's probably less hackish and better on multi-user machines.
>>
>> fwiw, I sometimes had problems with characters from my password going to
>> xterms when I used xidle. I don't know if it was something odd about my
>> setup, but something to watch out for if anyone's changing config as a
>> result of this thread.

I'm stepping in just to mention that I've observed the same behaviour,
though I thought it was because of the locking program that I used
(slock), not xidle.

Since then, I've switched to i3lock and stopped using xidle (I'm locking
manualy) and haven't observed this behaviour.

I'll give xidle a new try and report here if the problem occurs again.

Best.

> Duh, thanks for the heads-up.  This is a bit scary.
>
>> I like the hackish way :)
>
> ;)

Re: pkg_add -u error

[Grégoire Jadi]

On 09/19/16 16:32, Edgar Pettijohn wrote:
> I recently upgraded to the latest snapshot and when upgrading packages
> I saw this:
> 
> system(/bin/sh, -c, /usr/local/bin/mktexlsr > /dev/null 2>&1) failed:  
> exit(127)
> 
> Which makes sense because there is no /usr/local/bin/mktexlsr on my system.
> I searched for it with pkg_info -Q mktexlsr as well as other variations with
> no luck. Not sure where to go from here. Ignore post to ports@? 
> 
> Any suggestions?

You can use pkg_locate to find files in packages.

# pkg_add pkglocatedb
$ pkg_locate :/usr/local/bin/mktexlsr
texlive_base-2015:print/texlive/base:/usr/local/bin/mktexlsr

Best,

> Thanks,




signature.asc
Description: OpenPGP digital signature