On Sun, Mar 09, 2025 at 09:57:40PM +, 114465 wrote:
> Few hours became a few days, sorry about that.
>
> Alright so I tried upgrading to -current and I get the same issue as I
> was before. I don't know what more I can do to help identify what the
> problem is but because this issue is on two l
Few hours became a few days, sorry about that.
Alright so I tried upgrading to -current and I get the same issue as I
was before. I don't know what more I can do to help identify what the
problem is but because this issue is on two laptops by system76 I can
assume it is not CPU because the two mo
On Wed, Mar 05, 2025 at 07:25:09PM +, 114465 wrote:
> Thank you for the quick response! I have not tried updating to the very
> newest (the one put out yesterday) but I have been periodically trying
> to update to the snapshot. The last time I tried was about 2 weeks ago
> with the same results
Thank you for the quick response! I have not tried updating to the very
newest (the one put out yesterday) but I have been periodically trying
to update to the snapshot. The last time I tried was about 2 weeks ago
with the same results as I had before but I will try again in a few
hours and send a
Have you tried updating to the current snapshot?
On Mar 05 18:57:21, 114...@disroot.org wrote:
> Hello all,
>
> So I found an issue last year where the OpenBSD 7.6 release and the
> -current wouldn't boot on my laptop. I reported it in the bugs mailing
> list [1] however there was very little int
Hello all,
So I found an issue last year where the OpenBSD 7.6 release and the
-current wouldn't boot on my laptop. I reported it in the bugs mailing
list [1] however there was very little interest in the issue by others
and OpenBSD 7.5 still worked so I stuck with that version. More recently
tho
6 matches
Mail list logo
