I've been using pkg+https://pkg.freebsd.org/${ABI}/kmods_latest_${VERSION_MINOR} to get the working intel kmod on 14.2-RELEASE. I've just realised that the Sydney pkg mirror at pkg0.syd.freebsd.org/${ABI}/latest has same/similar directory for the kmods. Does this mean I can just use the Sydney pkg mirror and drop the default pkg mirror?

is there any chance pci-card realtek chip 8139d be compatible with freebsd? hardware.info shows 8139 and 8139l ... could not find 8139d yet...

Hi, I have neglected my FreeBSD 14.0 install. I would like to update to 14.2. Is this any different if I am still on 14.0 than the instructions for updating from 14.1?

AumShivaya: shouldn't be, just make sure you follow them carefully and create a BE beforehand if you're running ZFS

don't skip documented reboots

nope I am using UFS

It says when I ran freebsd-update fetch it is updating to 14-RELEASE-p11

So it is not directly updating to 14.1 or 14.2 yet?

no, you have to specify -r 14.2-RELEASE or something to that effect to get more than a patch update

Thanks kevans

What should I do, I already ran that command, do I just rerun it with those flags or something else, first?

is there any paste bin website you guys use in freebsd community?

i use termbin

i use privatebin/gist

per1cycle: there is bsd.to mentioned in topic

debdrup: I swapped out the potentially failing nvme devices, and I'm still seeing these issues under load

debdrup: in the same slot again. so it could be the controller itself

or it could be a ventilation/cooling problem

do you have 2 nvme in your board?

at this rate I'm ready to return the mobo and get something else, I have mirrored zfs because my data is important, and it should be able to do a scrub without disconnecting from the bus

no matter what the reason is

it could also be the nvme, there are a lot of reports of issues

anyway today I will attempt updating the firmware on the mobo, maybe that helps

its annoying to power cycle the whole box just to get the drive back

very latest firmware has fixes for my specific nvme, interesting ...

is anyone working on MPLS for FreeBSD?

i have run into a routing problem where i think MPLS is the best solution, and it makes me sad freebsd doesn't support this when openbsd does :-/

ok thx dch

yes, it doesn't

ivy: you can ask on freebsd-net⊙fo just in case, always good to have documented requests for stuff we don't support

I've been experimenting with settings in /etc/rc.conf.d/ instead of everything in /etc/rc.conf - it makes scripted configuration management easier. Easier that is, if I can determine the correct file into which the setting must go. netif contains stuff like 'ifconfig_igc3' or 'ifconfig_vlan219_ipv6' - however, putting ifconfig_igc0="DHCP" doesn't bring up dhclient on that NIC.

We have a Chelsio 6225 with two ports, but only one of the ports work. The second one seems to cause messages like "sysctl_warn_reuse: can't re-use a leaf (dev.cc.1.rxq.0.fl.ba)!" - as if it tries to set up queues for both ports using the same device number.

Interestingly it works on a (very) old 15-CURRENT in our BSDrp routers, but not on 14.2

Oh look, now that I have the correct IPv6 assigned to the vlan interfaces on the gateway, many monitoring checks have gone from red to green. Shock. Horror. I need breakfast.

dvl: yeah, /etc/rc.conf.d has annoyed me since I realized we implemented it as only being read in for the daemon the conf is named after

it's quite different from my mental model of conf.d =\

But what happens during boot, or if you do service -R, though? Will it read a file, run script, and then unset everything - or will it all accumulate if more than one service is being operated on?

In the former case it provides a minimum of isolation, which is good

In the latter case it's just an osbcure foot cannon

man, i miss periodic

(none of my linux comptuers have its equivalent)

nvme firmware update should be performed with clean device or it can be done with installed system on it?

LXGHTNXNG: I have using periodic to implement everythreeminutes < == FreshPorts uses that.

kevans: The problem for me is identifying which daemon uses the particular conf.

Hi, curious of people's thoughts about package update cadence. FreeBSD userland has quarterly and latest branches. Linux distros like Debian seem to be the only projects that champion absolute stability across the board. Is that silly? I am considering the merits of what it aims to do.

but it's also updated continiously

well, in terms of their stable release, not testing/unstable

I guess where I see Debian and FreeBSD similar is that BSD's core is basically LTS except obviously userland, whereas since Debian Linux has no separation of base and userland they just freeze everything, lol.

ivy: committed the fix for your ipv6 nexthop problem, but don't go get the wrong idea that I can be helpful sometimes. it's a fluke

ha... sad story

anyway, I believed that you can be helpful sometimes kevans ;-)

hi

please any helps to make nvidia 390 secondary driver with the latest 14.2 upgrade? Thanks!

my hardware: bsd-hardware.info/?probe=4672d15867

Posterdati: there is a PR about it, please take a look at bugs.freebsd.org/bugzilla/show_bug.cgi?id=285139

mzar: thanks

mzar: mmmh, the problem is with 390 not 570

oh.. sorry to hear that

mzar: very strange bsd are famous for their reliability with older and oldest hw :)

I run OpenBSD and FreBSD on 12+ years old machines with extreme satisfaction

I have a Pentium IV with netbsd 10 too :)

yes, maybe you can install some older version

:(

funky

if I manually invoke xflock4, I get a lockscreen and things are great. If I let it lock naturally from closing laptop lid, it locks but won't draw anything over the screen

so I get to type my password and, with great paranoia, stare and make sure whatever was in focus isn't taking my password in

kevans: could be worse. a lot of linux lockscreens do this thing where if your screens turn off and you wake them up by typing your password, the application that was last in the foreground when the screen locked will take some of the input.

this happens to me on x11. it's not great.

for many reasons.

imagine locking your work desktop and the last thing in the foreground was a shell. someone can now potentially input shell commands if they're quick enough (or have a device that emulates a keyboard and sends quick keystrokes)

ew