Hi all, I am coming across a tough issue. I will understand if you tell me to RTFM.

I have compiled a custom kernel for the first time, no problem booting but I am not able to use X due to i915kms module failing to load. I have determined it's probably because I have been using the pkg of said module and need to build the port.

When building the port I get a OS version mismatch. Should I just mangle the code checking for osversion or is there an easy way around this?

can you paste the output somewhere

mfro: did you rebuild the port after building the kernel?

you'll need to do that

I cannot paste it due to being on tty but simplified: bsd.port.mk UNAME and OSVERSION do not agree on major version number

is what I get when running make for drm-515-kmod

dont disable version checking, its going to use the wrong headers and some structs wont match up between x and the module, probably a crash

did you update the kernelsources it's using?

no... not sure how that is done. Maybe I should have just rtfm lol.

I don't even know which M you would be RTF'ing

forums.freebsd.org/threads/updating-kmod-ports-procedure.96021 ?

sorry not at a freebsd machine rn but hope it helps

I don't think that applies to me unfortunately, since my version number simply doesn't match anything the port expects it refuses to build

at least I believe that's what's happening.

do you know any amount of make? see where it gets OSVERSION from and why they don't match.

i assume UNAME is the correct expected version

oh you know what, it isn't the makefile complaining, it's make

uname is 15.0-CURRENT which I assume it shouldn't be for a custom kernel.

what did you name the kernel?

MYKERNEL, lol

mmm dunno if you're running what you think then...

it does list the custom kernel path in the uname. but it says 15.0-CURRENT beforehand

did you try shutting it off and turning it on again?

lol. yeah, I'm fairly certain I'm booted into the custom kernel

generic actually worked fine.

then what's OSVERSION?

1402000

well

where does the port get OSVERSION from

mfro: I recommend using the LOCAL_MODULES support if you're going to build a custom kernel

mfro: if you clone the drm-kmod repo to /usr/local/sys/modules/drm-kmod (for instance), buildkernel & installkernel will build it as a tied kmod and install it

oh man i scared them off trying to give advice

Whoops. Think I suspended by accident

mfro: it sounds like you didn't properly update to 15-current

follow the steps in the handbook again, then build the port

well, I'm not updating to 15-current, right? I am just building a custom kernel. Or do I need to buildworld for 15-current stuff?

if it says 15-current then you've updated to 15-current

you probably didn't pick the right branch or tag when you checked out the /usr/src

ah. I see. I did in fact use the CURRENT tree, because I didn't read the addendum to the 'using git' page

so am I understanding correctly that my userland stuff is 15-current whereas the osversion is supposed to be stable based on what I originally installed and built the kernel on?

sorry, last question, does releng branch correspond to release src?

TIL yet again that I need XAUTHORITY defined.

I have a laptop that occasionally docks onto a dock. Both the laptop and the dock have a 1TB drive. Could I make the dock's drive mirror the laptop's drive, but the laptop should keep working if I remove the dock? Thanks!

Note: "Drive" refers to SSD

1). i think you're asking too much for an OS without OEM support

I suppose it depends on your setup, but if you're using ZFS, you could certainly snapshot and send to the dock drive .

2). maybe, it really depends on what kind of device the "drive" is.

I'm relatively new to ZFS, but I am considering it, yes

... I could try to attack the dock's disk as a mirror to an existing zpool created on the internal drive... not sure what exactly happens when I unplug or plug the dock's drive

not sure if resilvering is automatic

ek: Actually, hm. I mainly use the dock's drive as a sort of backup drive so perhaps snapshotting makes more sense...

runxiyu: A mirror would not be a good idea. Problem central.

But, you could likely set up some sort of snapshot job if/when the dock drive is connected to make snapshots.

Of course, that would require an initial snapshot and transfer of some magnitude. But, after that, it should be pretty smooth sailing.

ek: Actually, hm. I mainly use the dock's drive as a sort of backup drive so perhaps snapshotting makes more sense...

err sry

got it, thx!

A simple cron job that run if /dev/whatever exists should do the trick.

Snapshot every hour (or whatever you choose) if the dock drive exists.

Or, you could send/recv local snapshots to the external drive when it's connected.

anybody does work pkg 2.0 now?

i did #pkg update -f #pkg upgrade #pkg autoremove -y #pkg clean -a and now does work properly.

Is there a documented process of manually installing FreeBSD?

runxiyu: forums.freebsd.org/threads/installi…freebsd-manually-no-installer.63201

I found this article from DDG

Thanks!

Another question, what does the "Encrypt Disks" option do in the FreeBSD installer? It seems to... make my SeaBIOS ask for a password before booting into any disk???

runxiyu: geli(8) might hold the answer to that one, i hope

thanks

trying to boot into the installer, asks for disk0 geli password three times; if i fail to provide a password it simply continues

100% resilient to human failures

my point was that it shouldn't ask for my disk0 password when i'm booting from installation medium

Potential bug in the installer: It doesn't ask for PSKs, for WPA2 networks whose SSID include Chinese characters

is it serious flaw ?

Serious to the extent that I couldn't install my system over WiFi

ha.. you have to fix your wlan to make FreeBSD compatible pall

hello tsoome

I ended up setting up a Linux machine as a NAT, and connected them wired

My WLAN is not broken, FreeBSD's installer is broken for exhibiting odd behavior on encountering non-ASCII SSIDs

I am provoking, just asking, could it be ever possible to boot from encrypted zpool (encrypted in native to ZFS way)

you are escalating runxiyu

hi

mzar sure, it depends on few things of course, but I can boot illumos from encrypted zpool;)

great, thank you for the answer tsoome and have a nice evening

what's the default value for kern.vt if i don't set it in loader.conf?

i set it to vty and now everything with the display breaks

Hm. I used to be their customer (still am, but only for 2 tiny servers), and it's been a while since I've had dedicated ... does anyone have any comments on Hetzner? I've been hearing numerious rumours about them just canceling entire accounts with no warning (which especially came to the forefront with the Kiwix situation)

I'm looking to move my server to a new host, and deciding between a few >_<

I saw the link of ghodawalaaman earlier. Is that the recommended way of co-installing FreeBSD next to Linux as well? I can’t install a second SSD so a partition must make due

how do I get freebsd to use kms... intel integrated gpu here

I think I understand why I can have pkg-2.0.0 installed but it's not in my repo. If I'm following `latest` for 14.x, then pkg will download from pkg.freebsd.org/FreeBSD:14:amd64/latest/Latest/pkg.pkg and install that - that's where I get it from...

dvl: 2.0.0 is buggy

please install 2.0.3

mzar: that's not my point....

mzar: but thanks, I have 2.0.3

(which in my story, is also not in the repo)

ha.. I have it in the repo, all built fine

mzar: I build my own repo. That's not my point. I am trying to learn more about pkg / confirm a theory. freshPorts/freshports #615

it looks like fresh breakage

what does?

15 hours ago

I do not think it is breakage.

I think my theory may be broken. I just updated pkg from 1.x to 2.2 and Latest was not used - FreshPorts/freshports #615#issuecomment-2614475523

I'm using headscale and when I use it without -c option in CLI, it always shows github.com/juanfont/headscale/cmd/headscale/cli/root.go:49 > Error loading config error="fatal error reading config file: Config File \"config\" Not Found in \"[/etc/headscale /root/.headscale /usr/local/etc]\"" This error

I think /usr/local/etc/headscale should be added in the root.go file

I guess it can be fixed in upstream but it would be better to fix it in freebsd size

side*

and how can I find a log for headscale?

OctopusET: it would be wrong for upstream, /usr/local purity is more of an us-thing

but you're right, /etc/headscale should go away in favor of $LOCALBASE/etc/headscale

Hello - does anyone know the official enlightenment desktop chatroom

ooo man enlightenment....

acu: enlightement? 🤔

thanks tyler82 I found it #e

acu: ok. i have on sxc FreeBSD & DesktopEnvironment group btw. The group is currently on approval phase but once will be available on public repositories u can ask there as well somebody might help u.

thanks tyler82: I just found enlightenment.org/news/2025-01-11-enlightenment-0.27.0

acu: ok

obviously I need to wait a bit for freshports.org/x11-wm/enlightenment

tyler82: so where is this group for desktop ?

acu: are u on sxc? its not on irc

tyler82, I do not know what sxc is - is this another platform I do not know about ?

acu: Ahm.....Yes 😁 github.com/simplex-chat/simplex-chat