mastodontech.de ist einer von vielen unabhängigen Mastodon-Servern, mit dem du dich im Fediverse beteiligen kannst.
Offen für alle (über 16) und bereitgestellt von Markus'Blog

Serverstatistik:

1,5 Tsd.
aktive Profile

#freebsd

81 Beiträge71 Beteiligte2 Beiträge heute
Antwortete im Thread

@shupfel wow. I literally must have been the other buyer during the FOMO pitch.

Last night, I bought the t14 gen 2. It looks like - to the best that ChatGPT and I could tell - to be a path to #freebsd laptop without the foundation price or lead time.

I bought a Lenovo v15 earlier this week and I hate the keyboard. It also has a flakey WiFi card. It also panics after suspend. It’s weirdly weighted. It sucks. I’m sending it back.

I had

- an ancient Inspiron (great but underpowered and heavy)
- asus zenbook (blissfully weighted, great keyboard, but no DRM support that I could get working despite doing drm-kmod gyrations)
- this v15 (see above)

Hopefully this t15 will bring the keyboard I adored from thinkpad and #freebsd capability.

../But yeah, Mint worked out of the box on the Zenbook with great video, and even found my printer during install. It I couldn’t run XOrg on FreeBSD. :-/

Looked into getting a computer engineering masters in a fit of frustration.

Getting somewhat closer to releasing a new version of #swad. I now improved the functionality to execute something on a different worker thread: Use an in-memory queue, providing a #lockfree version. This gives me a consistent reliable throughput of 3000 requests/s (with outliers up to 4500 r/s) at an average response time of 350 - 400 ms (with TLS enabled). For waking up worker threads, I implemented different backends as well: kqueue, eventfd and event-ports, the fallback is still a self-pipe.

So, #portability here really means implement lots of different flavors of the same thing.

Looking at these startup logs, you can see that #kqueue (#FreeBSD and other BSDs) is really a "jack of all trades", being used for "everything" if available (and that's pretty awesome, it means one single #syscall per event loop iteration in the generic case). #illumos' (#Solaris) #eventports come somewhat close (but need a lot more syscalls as there's no "batch registering" and certain event types need to be re-registered every time they fired), they just can't do signals, but illumos offers Linux-compatible signalfd. Looking at #Linux, there's a "special case fd" for everything. 🙈 Plus #epoll also needs one syscall for each event to be registered. The "generic #POSIX" case without any of these interfaces is just added for completeness 😆

Ok, I'm seriously tired of this hard lock on FreeBSD due to my amdgpu / drivers. How can I get logs on this as it completely locks up my system and turns off my monitor. I cannot ssh into it, I have to hard reset it. It happens in console, x11, wayland. It's random afaik, it will do it randomly is how I feel. I am using 14.2 and a amd 6750XT, probably the only FreeBSD user with one. Do I need to swap GPUs or do something else? Please help, I am so frustrated with this 1 issue. #FreeBSD #amdgpu #amd #drmkmod

Why is #ZFS on #FreeBSD so awesome!! 🙏

Wanted to re-partition my SSD to increase swap space.

<add USB HDD>
# zpool add mypool <hdd>
# zpool remove mypool <ssd>
(wait a while as system copies at full speed)
# <re-partition>
# zpool add mypool <ssd>
# zpool remove mypool <hdd>
(wait a while as system copies at full speed)

The final partition is smaller. No problem as long as all the data fits. ✅

And no down time. It is just a bit slower because of all the IO. ❤️

Opened review for #FreeBSD Bug 287268 on Phablicator as Differential Revision D50697, which adds latest New Feature Branch (NFB) of #nvidia #GPU drivers as x11/nvidia-driver-devel, x11/linux-nvidia-libs-devel and graphics/nvidia-drm[|-510|-515|-61|-66]-kmod-devel.
Once accepted and landed, it would track the latest version of whichever NFB or Production Branch of drivers. Beta Branch of drivers wouldn't be tracked.
reviews.freebsd.org/D50697

reviews.freebsd.org⚙ D50697 [NEW PORT] x11/nvidia-driver-devel, x11/linux-nvidia-libs-devel, graphics/nvidia-drm[,510,515,61,66]-kmod-devel: Add new port
Antwortete im Thread

@lawik Using a #FreeBSD runner is the best line in our CI (forgejo). The new elixir type hints help sometimes, not much linting otherwise. I only published two small things to hex - can't really comment on that.

Minor #FreeBSD upgrade annoyance: upgrading from 13.4 to 14.3 lost my audio mixer settings, and in fact mixer(1) works completely differently from how it used to. Still trying to figure out how to get line-in levels comparable to PCM output.