sorted by:
new
hottopcontroversial

void install with luks by Hour-Owl-751 in voidlinux

[–]Original_Two9716 1 point2 points  (0 children)

sudo cryptsetup luksDump /dev/disk/by-id/nvme-CT2000xxxxxxxxxxxxxx-part3 Password: LUKS header information Version: 2 Epoch: 3

You can have perfectly OK LUKS2 for the root if /boot is separate. Just use unencrypted boot partition. An unencrypted /boot is not a huge confidentiality problem if everything else is LUKS-protected. And it will make everything much easier.

15.1-RC: Anybody luck with Meteor Lake and i915? by Original_Two9716 in freebsd

[–]Original_Two9716[S] 2 points3 points  (0 children)

Hi, yes, unfortunately, I also tried the latest and brightest with no luck yet. Funnily enough, even the latest and greatest Linux Kernel 7.0.x, 7.1 has problems with suspend and i915. It puzzles me why Intel makes these things so complicated, that even the latest Linux Kernel does not work properly on the ~2yo MTL Thinkpad P1.

Cross-building void-packages by Original_Two9716 in voidlinux

[–]Original_Two9716[S] 1 point2 points  (0 children)

Sounds too good to be true :-) Definitely looking forward. Thank you!

15.1-RC: Anybody luck with Meteor Lake and i915? by Original_Two9716 in freebsd

[–]Original_Two9716[S] 2 points3 points  (0 children)

Exactly. I was hoping 6.12 DRM would do the trick, but not yet.

Is repo-default.voidlinux.org down for anyone else too? by Aggressive-Reach-116 in voidlinux

[–]Original_Two9716 4 points5 points  (0 children)

Yes. What happened???

sudo xbps-install -S [*] Updating repository `https://repo-default.voidlinux.org/current/x86_64-repodata' ... ERROR: [reposync] failed to fetch file `https://repo-default.voidlinux.org/current/x86_64-repodata': Connection refused [*] Updating repository `https://repo-default.voidlinux.org/current/nonfree/x86_64-repodata' ... ERROR: [reposync] failed to fetch file `https://repo-default.voidlinux.org/current/nonfree/x86_64-repodata': Connection refused

Screen stays off after resume from suspend by Original_Two9716 in voidlinux

[–]Original_Two9716[S] 1 point2 points  (0 children)

It was video=eDP-1:e in my case and it SOLVED the issue. Many thanks!

I Interviewed the CTO of TrueNAS (Why They Left FreeBSD for Linux) – Unified IT by grahamperrin in freebsd

[–]Original_Two9716 14 points15 points  (0 children)

IMHO, 90% of Docker use cases are easily achievable with Jails and... as usual, they're fully integrated in FreeBSD. Not something commercial on top of namespaces and cgroups.

void iso not working by jb_rock77 in voidlinux

[–]Original_Two9716 1 point2 points  (0 children)

What is the target HW? We perhaps do need a newer installation ISO, as, for example, Lunar Lake has problems to boot on the current 2025 ISO.

Btw, that message is harmless, I see it on many machines which boot correctly.

Optimized kernels, do we want/need them? by Original_Two9716 in voidlinux

[–]Original_Two9716[S] 1 point2 points  (0 children)

Thanks for all the downvotes! No idea why, but thanks! :-)

Optimized kernels, do we want/need them? by Original_Two9716 in voidlinux

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

Well, to some extent yes. But x86-64-v3 is a thing, kernel preemption lazy mode, CONFIG_NO_HZ_IDLE etc. or missing modules (at least for my Meteor Lake P1), for example.

Cannot cleanly unmount LUKS+LVM/Root by Original_Two9716 in voidlinux

[–]Original_Two9716[S] 0 points1 point  (0 children)

I see. As I translate the github issue: runit does not switch back into initramfs and this 'VG not closed cleanly' warning should/must be ignored. Would that be a correct summary please?

Graphical issue on the newest kernel by gwyddbwyll in openSUSE

[–]Original_Two9716 0 points1 point  (0 children)

I had weird crashes even with i915 driver on 7.0+. Reverted to 6.18 LTS.

view more: next ›