the 8080

cpet: I think you could use `pkg install -g FreeBSD-*` to do what you want

thats wasnt for me

Although I recall there is a `bsdinstall pkgbase` command when I was testing pkgbase in a jail and it installed the right amount of packages. I think bsdinstall can have its env vars configured to install at the root dir. Haven't tried that though and might not be safe.

cpet: gotcha, sorry

cybercrypto: ping

I ran into this annoying bug with pkgbase though: freebsd/pkg #2517

how is that a bug if they basically gave various ways to remove sendmail ?

the issues with pkgs is you either use it or you dont and its not meant to be a workaround for customized installed or people who want to customize

and people will still complain about the weirdest opf issues

such as installing freebsd-pkg-man instals 2kb more than before why?

does anyone know if the newer iwlwifi chipsets are supported on freebsd with hostapd in sta mode?

which newer chipset

cpet: I triggered that bug in a different way, but I don't recall what I did exactly.

any of the 802.11ac ones

maybe the ax210?

right, it's supported but, what about sta mode? I want to use it as an AP on a FreeBSD system

and, does it work in sta mode with 802.11ac configurations

error: did you mean `--depth` (with two dashes)?

hah

well greping the code the onyl thing I see is sta_id

there should be a man page entry that states what does a chipset supports along with the caveats (e.g. 802.11n/g only or what have you). I swear once upon a time there was...

kungfujesus: that kind of stuff is typically proprietary

im still confised as to why im greping code

cpet: greping? as in using grep?

it shows imilarities doesnt it ?

yeah but for the same purpose you can use less too

i was greping for sta in the iwlwifi code

currently, I've been stuck on an 802.11n atheros chipset (ath9k based) for over a decade. I've been waiting forever for ath10k support but it seems like that may never come. I use hostapd with a nanobsd system as a wireless bridge. There's been a lot of press lately about 802.11ac _finally_ being supported but from what I can remember only in client mode

I'd like to know if that situation has changed

the Intel iwlwifi driver was chosen to be used to develop 802.11ac station support. In addition to user-requests, the Dual-License of the newer driver parts (we can simply take the BSD license code, whereas we cannot take any GPL-only code into the tree anymore), already support for 11ax, the clean code structure, previous examples of ports of older versions of the driver, the ability to distribute

dont fancy running alpine linux in a bhyve vm with device passthrough to get half decent wireless speeds? :D github.com/pgj/freebsd-wifibox

firmware, .. all played into the decision,

google is hard

mjp: I do not, hah. I remember seeing that but I also recall that somehow the LinuxKPI stuff made that obsolete?

kungfujesus: you have to expect the maker to do the firmware for you

scottpedia: firmware is included ind river

it's already a bliss if you get that for Linux

cpet: Googling _this_ stuff is hard. It seems like Google has gotten worse at indexing these things and definite sources of information for this stuff (apart from being incredibly familiar with the source code) is hard to come by

blame the user not the machine

cpet: yeah that's what I am saying they don't do the driver for every OS and for every chipset

yeah that wiki article is all out of date, right? It says 802.11ac support is pending

you know you can boot the OS install and test this right ?

I'm deciding whether or not to buy it

buy it test it then return it if it dont work

heh

this seems like a pretty big ask when I'm all I'm asking is if it's notionally supported. I don't get why this isn't documented anywhere to reflect the current state of development

wiki mentions supports devices

in what modes? Am I going to need to do some franken Linux thing like freebsd-wifibox does?

go email adrian@ who is the wifi guru and ask

or ill email him and ask for you heh

seems more likely to answer you than me

why?

one day ill understand why people are afraid to submit PR and email developers directly

as long as its freebsd related and generalized im sure any dev will respond

I'm not afraid but I do have a vague recollection of sending him a question once and never getting a reply

done

see what he says

sctually

lets ask in freebsd-wireless

is virtiofs supported in FreeBSD (or at least planned?)

or do i have to keep my linux+sshfs setup for host data

swee: v9fs is supported

mzar: ah, so virtio-9p?

mzar: v9fs has been supported for, like, a decade, sir.

yes, it should be supported

yes

do i need to install any separate packages, and is it set up like in Linux?

I don't know how to set it up in Linux, but for FreeBSD there is man page p9fs(4)

i.e. /hostshare <TAB> /mnt/hostfs <TAB> 9p <TAB> trans=virtio,version=9p2000.L <TAB> 0 0

in fstab

swee: man.freebsd.org/cgi/man.cgi?query=p…5.0-STABLE&arch=default&format=html

# mount -t p9fs /hostshare ./test

mount: /hostshare: Invalid fstype: Invalid argument

Yeah. Even supported in bhyve now. That's pretty awesome. I tried to boot a p9 VM a while back and it didn't work. Moving forward!

lounge.swee.codes/uploads/c3500867594bca51/image.png lounge.swee.codes/uploads/ea726796c904a547/image.png

swee: Have you loaded the virtio_p9fs kernel module?

kldload: can't load virtio_p9fs: No such file or directory

did I miss a FreeBSD update or something?

What version of FBSD?

14.3

it's latest production version, that's for sure

Ah. Might be why. I believe 15 is the latest to provide the kern module by default.

14 you can build the module into the kernel.

Just give it a few weeks and 15.0-RELEASE will be available and it will be included without have to build a custom kernel.

i did try building that module and loading it last time, someone here helped me

KLD virtio_p9fs.ko: depends on kernel - not available or version mismatch

on other VM

i guess for now i'll keep using linux + sshfs lol

in a separate vm

why dont you just recompile the module

i forgot how to

swee: You rebuilt the kernel and userland for the p9 support?

What, exactly, did you do?

ek: no just the module

Ah, okay. There's likely additional code that needs to be compiled for the kernel to support the p9 module.

If you add the p9 option the kernel and rebuild it (fully), it will include everything you need and it should load just fine.

... well, provided the build/install is successful.

is it difficult to rebuild kernel

Not at all.

p9 should work when module is loaded, if FreeBSD version is fresh enough

kldload virtio_p9fs

mzar: 14.x doesn't have the p9 module. 15.x only (I guess?)

ek: like... is it as difficult (and maybe time consuming) as building the linux kernel

so you compile a kernel module made for 15.x on 14.x ?

then comaplin when you get an error as the above

heh

swee: It's actually much easier, really.

You just choose what you do and do not want from a flat-file with comments and just build it.

ek: ha... you are right

Linux has always confused the hell outta me.

ek gets confused by just being ek

I get confused by the fact I know cpet. :)

dont hate

dunno, am a noob at the BSDs lol

where did you download this so called module

swee: That's fair. It's why the handbook, forums, and IRC exist. Questions are acceptable.

cpet: i think building with /usr/src

we cant help you if you dont even know what you did

seems like it would better if you just updated to 15.0-RC4

fusefs-sshfs-3.7.5

or use that until 15.0 is out

if what you want is the same thing

that's what I'm currently using as a workaround so far

kernel modules want the same kernel and the same userland

even if the module compiles it will still comaplin cause the kernels dont match

right, TIL

would probably be better to just update vs hacking the system

¯\_(ツ)_/¯

what the hell is that

my irc client has a plugin to make things rainbow so i aliased /gayshrug -> /prism ¯\_(ツ)_/¯

hrm

this channel has +c which blocks colours

so your message was boring

didn't notice lol

Might've been boring, but it still presents as expected on irssi/bitchx/weechat...

It's the simple shrugging chars.

¯\_(ツ)_/¯ : shrugging guy?

is it normal not to have any chat history for example of this channel except my own exchange

?

v01d: I suppose it depends on your IRC client. I have all history without any problem.

Wait. Are you talking about when you close your client and open it back up to connect at a later time? You're expecting data that your client wasn't there to collect? Like a cache history that would be dumped to you?

... kinda like Slack or Discord? If so, yes. Totally expected. IRC is a one way street. Either your client gets the data or it doesn't. It needs to be present. There is no backlog dump when you reconnect.

ok thanks sharing with meI did not know

so right now there is no other activity on this channel than you and me?

I use goguma I'm writing to you from android phone

?

swee: yes, updating to 15.0 RC will be good step forward

can we install somehow the freebsd manpage through termux on Android phones

it would be real nice

to have them like that

sure, you can, you need android SGML reader

v01d: are you a FreeBSD user ?

yes iam a freebsd user

mzar: please elaborate

5

(woops)

What are the benefits of running a VM using bhyve versus libvirt/qemu?

libvirt is just a way of managing different VM frameworks, even over a network; it has, iirc, a backend for bhyve and is thus usable with a freebsd hypervisor.

none of those are comparable to each other. bhyve is a catch-all name for freebsd's hypervisor (the vmm + libvmm + the userspace virtio bits/cli tool). qemu is an emulator that can use a hypervisor for acceleration, which could be done through bhyve's bits (although there is currently no support for that in qemu sadly) and libvirt is a configuration tool to manage VMs that can use either of the two

JetpackJackson: Bhyve benefits from the attention of the FreeBSD project directly, instead of relying on third-party software. Moreover, libvirt can use bhyve as a driver :)

Oh ok

I guess I was confused on my terminology

So like I could use bhyve to run Linux-only programs if needed? And i could use a VM that isn't Ubuntu?

yeah, although keep in mind that you won't get "fast" graphics as it will go over vnc

you can likely run a lot of linux stuff via linuxulator though

JetpackJackson: which programs are you thinking of? Sometimes they can use the linux compatibility layers offered by FreeBSD (I'm thinking especially of htop)

Well currently orca slicer cause its a bit buggy in wine

They only have appimage and flatpak

Ran into issues with both in linuxulator chroot

On my Linux system for school I had to run virtualbox and unityhub and was able to use the AUR for that (even though I dislike it) and I can use distrobox and flatpak too so I'm trying to figure out what my "fallback" options are on FreeBSD I guess

Like flatpak and distrobox are my fallbacks when I'm on chimera

sounds like your production machine should stay on linux for now?

did i or my useful idiots ever rant about our project to port ifupdown-ng to freebsd and its workalikes? we realize it's wholly redundant but we thought it'd be cool as a tech demonstrator. we never got it past a truly horrendous pre-alpha stage

LxGHTNxNG: yeah I mean I'm not changing anything until I graduate cause this Linux laptop is my main machine but I like to make sure all my bases are covered before distro hopping

you can always just run freebsd in a headless vm

Yeah I am but im a bit low on space so I haven't given the VM much space

Plus that doesn't give me the opportunity to test GUI stuff or bhyve

v01d: the concept of FreeBSD user is self-explanatory

has anyone here gotten Steam working in FreeBSD?

when I tried it on 14.3.. the games would just stutter.. it was like watching a slideshow

maybe 15.0 will be better

"has anyone here gotten Steam working in FreeBSD?" I didn't.

macos has rendered at least two of my steam games unplayable

that is a shame

is there someone has latest freebsd handbook in .epub format?

Sorry, I don't have one.

Gocmen: you might want to go to archive.org or libgenesis for that kind of resources

Convert the pdf with Calibre

Gocmen: there is also the utility pandoc.org which may take a little work.. but iha ve used it to do markdown -> pdf with some LaTeX love

it also supports converting to epub format

honestly epub is not the most useful when browing through technical documents

i'd still recommend pdf or even plain text

Surely it's more a question of device than content? I've read technical documents just fine on my kindle

Are all the gotchas with freebsd-update and ssh not working still there or were all those fixed post init. release?

Wonder if I should restart sshd each time before any reboots.

9.3 ?

THE 9.3.

did you just pull out a machine from the closet from ten years ago and decide to upgrade it

recent-ish freebsd-update restarts sshd for you. anyway, i'd suggest to at least check the logs.

Yeah, this would never be a machine on the Internet that no one wanted to update due to downtime/breakage/cost to update software.

The big issue is that due to the age the VPS can't attach a OOB console to it.

So not having ssh is kinda of a pain.

otis: That's my hope but I just recall a couple updates either between minors or maybe majors where sshd failed to start unless you restarted it before hand.

I get the feeling maybe it was when some keys types were dropped.

well should be exciting

skered: don't you have ipmi console ?

mzar: This is a VM.

And the VNC console make 9.3 crash at startup.

oh.. you need serial console then

I'm using this a reason to upgrade. So I'm not really looking to fix it.

and you dont install fresh because?

why install if he can upgrade

FreeBSD is easily upgradable

mzar: It is until it isn't. But I think it will be fine.

My only issue was is it even possible. Testing a in a vm it seems all the bits are still out there on freebsd-update servers and the sshd things

I just couldn't seem to find out if the sshd issues were fix or if you had to follow post install pre reboot steps to make sure it all worked.

skered: no worries, you can always boot it from another medium, mount under /mnt and issue command "make installworld DESTDIR=/mnt" if you have world and kernel built and accessible via NFS share

FreeBSD is flexible OS with regard to upgrades

skered: does the vm have a zfs or ufs filesystem?

ufs.

is it 32-bit or 64-bit OS skered ?

64.

kinda makes ya wonder why we have so many secueity breaches

There would be fewer security breaches in general if companies update/patch their systems way more often.

mzar: Doing that zpool shrink on prod now. Just installed the SATADOMs and putting it up, ready to transfer the zpool.

nice

FreeBSD is good OS, everything can be done in-place, without reinstall

hardest part was transitioning from 32-bit to 64-bit using self-hosted builds IIRC

s|good|great| :)

when updates come, install them ASAP. my boss refuses to help people at work if their Chrome or FF is out-of-date.

yep, it's even better to run not released yet software than outdated one, running not released code minimises the surface and vector of attack

This upgrade treadmill is exhausting, especially now that new versions come our not once a year, but once a week.

That's why I jumped off -CURRENT. Upgrading all the time is a chore.

it's a pleasure

not everyone enjoys babysitting their computing equipment

unattended upgrades are solving problems

^ and not creating them?

I just updated my lone desktop FreeBSD system to 14.3-p5, and then ran pkg upgrade to the current quarterly. Result: I can no longer get past sddm. It loops back to the login screen. As this has happened before, I'm suspecting there is a video driver issue.

I forgot to write down notes the last time I had to rebuild the driver.

mariuss: plase go ahead and upgrade to 15.0-RC

it will solve a lot of issues

I wouldn't presume it would fix the video driver issue though

why not

since the issue is most likely that what's in the pkg database is inconsistent with the kernel

mariuss will add Freebsd-ports-kmods

then upgrade

and will be fine

Can you provide instructions? I don't have a desktop FreeBSD system at the moment, so I've forgotten the steps too

sure, there are hundreds of people hanging here, we will guide him

Normal upgrades are no problem. However, all my other FreeBSD boxen are servers, and thus I only run into this issue on this one machine,

IIRC the process is to get the kernel sources and build the kmods agains that.

no worries, you should give a try to 15.0 on this desktop

there is nothing to build

do you have kmods repo in /etc/pkg/FreeBSD.conf ?

OK. As this not a production machine I'll give it a go.

yep, but even with 14.3 it should work

Yes there is a kmods entry in FreeBSD.conf

pkg upgrade -r FreeBSD-ports-kmods

please issue this command

Unfortunately, I can't in single user mode: Insufficient privalege to upgrade packages

you can use it in multiuser environemnt

ah.. you have no network ?

How do I get into multiuser mode w/o the GUI?

start the network, make / writeable and go ahead

sure, you are in multiuser without gui, unless you booted into single user

I booted single user

do you have more then one console working ?

ha..

that's bad

but no worries

remount / rw

and start network

what is / on ?

ZFS

How can I temporarily disable the GUI a t boo time?

s/a t boo/at boot/

the gui ?

UEFI loader ?

it's harmless

I.e. only get the console, but with multiuser login

now you can remount rw /

OK, so look at kld_list

sysrc kld_list-=undesired_driver

but first you need to make / writeateble

zfs get readonly zroot/ROOT/default

UEFI loader. I updated it this morning, after I ran into this problem. It made no difference.

zfs set readonly=off zroot/ROOT/default

sysrc kld_list-=i915kms

sync && reboot

and you will have no gui

but instead of rebooting, you can start network

and upgrade

dhclient em0

pkg upggrade -r FreeBSD-ports-kmods or pkg upggrade -f -r FreeBSD-ports-kmods

and you will be fine

kenrap: i like your style man

kudos or something

I get: No repositories are enabled

ha... you have to enable them

How?

mariuss: in 14 the name was different

please check your confing

I'm still on 14.3!

what do the logs say

check this file /etc/pkg/FreeBSD.conf

one repo has name with "kmod"

Looking at that: FreeBSD-kmods

go ahead

it was reanemed a lot, now the name is different

the log for sddm will tell you what going on

do you have securelevels set to anything hgiher that -1 ?

pastebin your rc.conf and your /etc/pkgs/FreeBSD.conf

er /etc/pkg/*

ek is dead

wrong server

now my shift is over, cpet will guide you, thanks

need to close some of these ssh tabs

OK. I'm now logegd into multiuser mode (with network) by disabling sddm in /etc/rc.conf.

The kld that is in need of being updated is radeonkms

Running pkg upgrade -r FreeBSD-kmods did nothing.

that's sad story

but upgrading to 15.0 RC if it's your destkop is encouradged, at least by my

me

I'm not typically inclined to install non-RELEASE OS versions. However, as this is a non-production system I'll give it a try.

running non-relasesd software decreases sufrace and vector of attack against the desktop

my desktop runs CURRENT

What is the correct OS string? 15.0-RC doesn't seem to exist.

RC3 ? let me check

That was out a few days ago

perhaps RC4 is out, or it should be building now

Looks like RC4 is out.

However, not available yet. Trying RC3.

Hmm I did a fresh VM install of 15, and its all configured nice with pkgbase and such, but I seem to be missing the shutdown command?

Nvm

It seems I have to prefix doas whereas I don't think I needed to before, it would just say that I didn't have permission

Stupid question sorry

Halt should be there also

Oh yeah

There it is

The man page for "man shutdown" says: In order to use the shutdown command, the user must have root privileges or be a member of the operator group.

Were you in the operator group before? But are not now?

Ohh

Yeah I think so

I really like how pkg fetches packages before installing

Does pkgbase play nice with portmaster or poudriere? Dont want to muck up pkg prime-list with dependencies

mzar: done. dan.langille.org/2025/11/25/prod-mo…ot-using-zfs-snapshot-and-send-recv

and look at that formatting. I should proof read before pasting.

dvl: good job, I am following you on mastodon, so observed each your move ;-)

join #not-freebsd

oops sorry

daemon deserves at least nice poking ;-p

:-)

:3

wonder if im still an op

nope

dstolfa, guess I was away a while :P good to see you again

I installed FreeBSD-set-devel to try to compile some things but now I want to remove it but pkg says its vital. I don't want to use -f cause I don't want to break something

If I remove with -f and then run pkg autoremove it just hangs

it could be a but

*bug

How do I fix it

ha... that's hard to answer, probably you can report it

JetpackJackson: youtube.com/watch?v=0JQbeCAlF6s

I don't get it

each time I see your nick reminds me of the jetsons theme

JetpackJackson: you cant mix ports a pkg's

daemon: \o

the only time you can is when the port has the same options as the pkg

cpet: oh

or using poudriere and adding the pkg repo

Lemme send a pastebin

What was that site you mentioned, I forgot

if its less than 3 lines just paste here

Its not

<command> | curl -F 'sprunge=<-' sprunge.us

ls -la | nc termbin.com 9999

that works

so many pastebins most if not all havent been maintained in 5+ years

Alright

Where do I report the pkg auto remove thing?

Im nervous

cpet: You've heard what happened to dpaste.org?

cpet: Right now I'm thinking, I have privatebin configured locally (publicly available, but login required). Now I want o install termbin.com on a local host nearby.

mzar: can you elaborate about android sgml reader and manpages

v01d: I am not using it

I need to see if xwayland dies on KDE or something cause not having it on niri sucks

cpet: oh, you meant the use of the '|' as the regex delimiter for typo correcting?

(forward slashes are overrated imo)

that sucks for dpaste :(

After updating the machine to 15.0-RC3, I'm updating the packages. pkg wants to install every flavor of postgresql-client (14, 15, 16, 17 and 18 so far)

If you are upgrading then that means those previous versions were already installed?

I certainly didn't install them manually! However, they may be dependencies. Personally, I only use mysql and sqlite.

why can't I find the manpages github.com/freebsd/freebsd-doc/tree/main/documentation

where they are?

v01d: in freebsd-src in directories of the programs they are about.

can't I have them all

You can run `find . -name '*.1'` in freebsd-src to get e.g. all the manpages in section 1 (with some false positives).

v01d, For online man pages: man.freebsd.org/cgi/man.cgi

I thought I could have them so I can build them everywhere I want for offline use

what's the source of the online manpages?

v01d: /usr/share/man

mzar: is it in the SRC too so I can clone it?

what's the source of that directory

The all-man Makefile target in the freebsd-src repo seems like a good candidate.

freebsd-src/share/man

I now get libmd.so.6 not found when testing startx.

yakubin: what do you mean

v01d: <cgit.freebsd.org/src/tree/share/mk/bsd.README#n231>.

Hmm I'm trying to mount a drive with ventoy to copy an ISO over and its not working. Pastebin incoming

I need to find out if we have something like udiskie

Great, it seems that somehow I should have know to set BACKUP_LIBRARIES-true in pkg.conf

s/know/known/

yakubin: how is this working? is it that I have to clone the src and make bsd.man.mk?

with option all man

OK used mount.exfat and it worked

mariuss: have you upgraded packages ?

v01d: that's in the installed OS, not src

I know

v01d: running `make all-man` in the root of the source tree (/usr/src) should work.

The specific .mk Makefiles are sourced from the top-level Makefile.

ok that's what I thought but needed confirmation

Yes! However, I ended up manually deleting xorg and reinstalling it. That got me to another error: cannot run in framebuffer mode

ha.. long story

I have to us github to clone the SRC, yes?

or cgit

it's 24M

How do I specify busIDs?

mariuss: do you need config for xorg ?

It was configured before.

usualy it's not required

unless you have 2 cards, touch screen, hid touchpanel or something like that

Perhaps .xintirc needs to be edited

pciconf -lv will tell you about numbers

v01d: you can download a tarball from FTP: <nanxiao.gitbooks.io/freebsd-101-hac…tent/posts/install-source-code.html>, but git will work too.

Currently it's a single line: exec dbus-launch --exit-with-x11 ck-launch-session startplasma=x11

I see the display in pciconf, but which number do I need, and how to I then pass it to xorg?

BusID "PCI:1@0:0:0"

I don't see BusID anywhere in the output, but there the entry starts vgapci0@pci0:0:1:0

So where do I specify "PCI0:0:1:0"?

yakubin: thanks, which git? cgit or github?

Doesn’t matter much I think.

yakubin: ok cgit then

cause fuck GitHub:)

yakubin: thank you

No problem.

cgit is only for web-browsing

I tried to clone from git.freebsd.org/src but don't worked