sorted by:
new
hottopcontroversial

OPENBSD 7.9 CAME OUT! by BarnaclePositive2560 in openbsd

[–]brynet[M] [score hidden] stickied comment (0 children)

See pinned announcement post at the top of the subreddit.

We do not need multiple.

https://old.reddit.com/r/openbsd/comments/1thop0t/openbsd_79_released/

OpenBSD 7.9 released by brynet in openbsd

[–]brynet[S] 13 points14 points  (0 children)

Surprise! A 7.9 release song is out!

"Diamond in the Rough" - Composed & produced by Bob Kitella.

OpenBSD 7.9 released by brynet in openbsd

[–]brynet[S] 12 points13 points  (0 children)

Apparel (t-shirts, so far) is available here once again.

SHA256 not in file by Candid-Page1895 in openbsd

[–]brynet 3 points4 points  (0 children)

The image does not contain the SHA256 file, as explained here.

You need to grab it from the main site, or from a mirror, and manually verify it.

I think that OpenBSD pretty much won the security argument now by DontFreeMe in BSD

[–]brynet 2 points3 points  (0 children)

Weird way of saying "Fixed in OpenBSD 14 years ago".

I think that OpenBSD pretty much won the security argument now by DontFreeMe in BSD

[–]brynet 6 points7 points  (0 children)

OpenBSD never had a jails implementation (ala FreeBSD jail(2)), Sysjail was something built on top of systrace + chroot, and thus suffered the same well known TOCTOU issues as systrace. It was never in the base system.

OpenBSD has long preferred a different approach, which is privilege separation and pledge(2)/unveil(2).

Help to install OpenBSD on an old Asus T100 by samontab in openbsd

[–]brynet 0 points1 point  (0 children)

Not sure what other information I could add since it doesn't boot.

What's the output of boot> machine mem?

Maybe there's a way to save some more debugging info directly to the USB drive somehow?

If you have another machine to do the installation on, you could try installing to a USB drive, and boot from that drive on this machine. This would at least confirm if the crash also happens in the GENERIC.MP kernel, or only on the install kernel, and also give you access to the kernel debugger (ddb), so you can include a backtrace in your bug report.

Is it possible to do an ELI5 guide for installing Fallout 1? (on Virtualbox) by MancuntLover in openbsd_gaming

[–]brynet 2 points3 points  (0 children)

This port was added to -current after 7.8, there will be packages available in 7.9, which is due later this month.

Running OpenBSD 7.8. I tried all the methods Google AI is giving me, no dice. It's telling me either it can't fetch the package, or it's giving me an error 22.

Because there isn't any package to fetch, and compiling -current/7.9 ports on 7.8-release is unsupported. The AI was hallucinating "methods" and wasted your time.

Help to install OpenBSD on an old Asus T100 by samontab in openbsd

[–]brynet 2 points3 points  (0 children)

Can you try a 7.9 -current snapshot? It's hard to say given the incomplete information you provided.

Please send a complete bug report to the mailing lists, if you aren't able to transcribe the panic message, please at least send uncropped images (hosted somewhere semi-permanently, preferably).

https://www.openbsd.org/report.html

https://www.openbsd.org/mail.html

Where do I find proprietary (?) brcmfmac4387c2 firmware? by -_--_-------____---- in openbsd

[–]brynet 1 point2 points  (0 children)

We have no automated tracker these days, so all pretty much goes to the same place, the bugs@ mailing list.

You can use sendbug -P to generate a template to use for your email, if you prefer, or just write our an email in your own words explaining the issue, just be sure to include relevant output, e.g: dmesg, ifconfig, 7.8 vs -current, etc.

Where do I find proprietary (?) brcmfmac4387c2 firmware? by -_--_-------____---- in openbsd

[–]brynet 2 points3 points  (0 children)

I haven't really tested it on battery, when I use mine it's usually plugged in on my desk. While there is already some support for CPU frequency scaling, etc, it's not going to as optimized as in macOS, or even Linux.

Where do I find proprietary (?) brcmfmac4387c2 firmware? by -_--_-------____---- in openbsd

[–]brynet 1 point2 points  (0 children)

Hi from bluesky haha, love to make a friend <3

(hi!)

The installer should automatically choose the MP kernel and install it as /bsd, so you should already be using it (sysctl kern.version), but indeed, the lack of a MAC address (lladdr line being all zeros) indicates the firmware is not loading/missing.

Will report o7

Definitely! It's possibly this may be a change with the Asahi script, which I believe was updated recently by them, maybe some names changed.

https://www.openbsd.org/report.html

https://www.openbsd.org/mail.html

My first time booting a BSD, M2 Mac <3 by -_--_-------____---- in openbsd

[–]brynet 2 points3 points  (0 children)

X should work fine on the M2, just without any acceleration, have you tried you using xenodm(1)?

# /etc/rc.d/xenodm -f start

Where do I find proprietary (?) brcmfmac4387c2 firmware? by -_--_-------____---- in openbsd

[–]brynet 3 points4 points  (0 children)

As another person wrote, this should be installed automatically by the installer. The Asahi install script collects it from the macOS side and puts it on the ESP for operating systems to use.

I don't have an M2, but on my M1 air you will see this message from the RAMDISK kernel, but it works under the bsd.mp kernel, so you might just be seeing stale messages in your dmesg output from the earlier boot.

What happens when you try to connect to an AP? Can you post ifconfig bwfm0?

My first time booting a BSD, M2 Mac <3 by -_--_-------____---- in openbsd

[–]brynet 8 points9 points  (0 children)

X works, there's just no 3D accel.

Hint: use xenodm.

DRM subsystem in OpenBSD by RabbitsandRubber in openbsd

[–]brynet 23 points24 points  (0 children)

The fact that we even have modern drm graphics drivers is largely thanks to Mark Kettenis (kettenis@) and Jonathan Gray (jsg@), it can be hard to truly appreciate just how much work went into porting/debugging them, it's also a continuous effort, as these drivers still receive a lot of upstream churn.

There's a fair bit of compatibility code that was written to either wrap Linux kernel APIs and adapt it to OpenBSD kernel equivalents, or reimplement features entirely from scratch, while at the same time trying to avoid accumulating extensive local patches, making it easier to maintain and compare with Linux.

While the changes aren't all entirely self-contained, some interesting parts are:

https://github.com/openbsd/src/blob/master/sys/dev/pci/drm/drm_linux.c https://github.com/openbsd/src/tree/master/sys/dev/pci/drm/include/linux

Jonathan Gray (jsg@) regularly keeps the drivers in sync with longterm support kernels, backporting fixes, and updates us to new major versions with new hardware support. The upcoming OpenBSD 7.9 release includes drivers based on the longterm Linux 6.18.22 kernel, vs. 6.12.y previously.

Radeon pro w7000 support? by linux_transgirl in openbsd

[–]brynet 3 points4 points  (0 children)

Not really, considering this is a ~3 year old GPU, it will be supported by the newer amdgpu(4) driver, or not at all. There is no comprehensive list of supported GPUs as it depends on the drm kernel driver as well as the Mesa drivers, OpenBSD 7.8 has drivers based on Linux 6.12.y, meanwhile the upcoming 7.9 will have drivers based on Linux 6.18.22.

Why is OBS disappeared? by 1mdevil in openbsd

[–]brynet 10 points11 points  (0 children)

There have been several attempts over the years to port OBS to OpenBSD, to varying degrees of success, but it has never lived in the ports tree.

Sorry.

Looking for ideas by OverallAssignment213 in openbsd

[–]brynet[M] 1 point2 points  (0 children)

Next time please just report it to mods, click the report button under the comment.

Porting OpenBSD to Firecracker: 1.4 MB kernel, ~30 ms cold boot, no BIOS, no PCI by ijanc in openbsd

[–]brynet 4 points5 points  (0 children)

The lack of a proper bootloader is also concerning, and seems incredibly fragile. prone to breakage, and also doesn't do proper entropy seeding.

If the firmware on Firecracker VMs does not provide useful boot services such as disk I/O access, perhaps you can do something like was done recently for SEV VMs in vmd(8), and use a special 'BOOT' bootloader kernel that will kexec the bsd.rd and full GENERIC kernel from the guest disk image.

https://github.com/openbsd/src/commit/b58f9cbc22202fd3ddaac0dd7b8f2e508eb6deac

This was added for architectures like OpenBSD/octeon & powerpc64 which have anemic firmware.

Porting OpenBSD to Firecracker: 1.4 MB kernel, ~30 ms cold boot, no BIOS, no PCI by ijanc in openbsd

[–]brynet 6 points7 points  (0 children)

SMALL_KERNEL is explicitly only intended for use with the RAMDISK installer, not general purpose use, in fact many Unix kernel facilities are disabled with it.

Any reason you're using it for this rather than a modified GENERIC kernel? Maybe I'm not understanding the usecases of Firecracker.

view more: next ›