Guys i want to install freebsd on this ACER but it has a QCA9377 but all over the forums it says its not supported yet. was wondering if somebody can confirm. I'm wondering if stable will have it

some of the fourms are from like 2019 and such

Title: Atheros QCA9377 | The FreeBSD Forums

bz@ has been working on a solution for that, but I'm not sure about the state of it.

Thanks

hi everyone, i am looking to try and compile lua-language-server and it is unfortunate there is no /usr/ports entry for this and all documentation assumes linux/mac/windows, no *bsd. My question is: is there a "standard" template for setting up a compile to a BSD structure.. like /usr/local /usr/local/etc ...

voy4g3r2, are you looking for hier(7), the "hier" manual page?

(Specifically, the "local" paragraph under "/usr".)

V_PauAmma_V: that is possible, i am so use to building things in slackware, debian and other linux.. but i am not sure what i am suppose to look for, in freebsd

the hier thing, looks like what i am looking for :)

Don't panic, but pay attention: arstechnica.com/security/2023/11/ha…hic-keys-in-new-cutting-edge-attack

Title: In a first, cryptographic keys protecting SSH connections stolen in new attack | Ars Technica

I'm having crashes with graphics/drm-515-kmod on a amd raven2 gpu on 14.0-RELEASE

It seems okay with graphics/drm-510-kmod

also it began crashing when i updated from 5.15.118 to 5.15.118_1

So, anyone have any ideas on how to redirect audio for OBS? It works fine to capture the audio output on something like Firefox, but when playing Unreal Tournament 99, I hear nothing.

FreeBSD 14 is now released

yay!

CrtxReavr: "it affects only keys using the RSA cryptographic algorithm" phew

i wonder if siort reported by of their graphics/drm-515-kmod crashes…

wat "Of the roughly 1 billion RSA signatures, about one in a million exposed the private key of the host."

hallo

im upgrading a jail to 14.0

etc-update or mergemaster or whatever is not helping me at all, I have to manually fix every file

Merge conflict markers remain in: /etc/ssh/moduli for example

I had not run any jail of much significance. But damn, seems like installing from scratch could be less tedious (save the critical files; set up a new jail; update the files in new jail). Then again, as I mentioned at the start ...

sopparus: can you show what a conflicting file looks like?

i have allready fixed it by hand now, but im soon doing another jail

i have never altered /etc/ssh/moduli myself

it seems like in /etc/ssh/moduli it removed every line and inserted new ones

in other rc scripts, some if code where replaced by other if code, which should be merged automaticly just fine

sopparus, What is the FreeBSD version that you are upgrading from?

13.2

the host machine went fine as usual, its just the jail

Thanks

using freebsd-update -j myjail -r 14.0-RELEASE upgrade

freebsd.org/releases does not list "14.0-RELEASE" ...

Title: Release Information | The FreeBSD Project

... or, does using that strings causes the install of some *RC version?

Title: FreeBSD 14.0 Release Process | The FreeBSD Project

babz, Yes, just found that too! Am late to the party.

yeah, that says the release should be today, not that it actually happened yet

there's no release without the announcement

diizzy: do you have a ryzen system now? just reading latest threads on hackers

afaik the release waits till all pkg repos are build and not sure what else has to happen before the announcement is sent

looking at a ryzen 7950x

meena: for example in rc.conf dumpinen.com/lib7892wJMt

also dumpinen.com/-qpWMXO-vKa

those are automerged on host machine

sopparus: what's the output of

ls -l/var/db/etcupdate/

grep /etc/mtree/BSD.debug.dist /var/db/etcupdate/*.files

in the jail?

yeah

babz: dumpinen.com/T3w9ekBikbd

yeah, you dont have the files from the previous release

so every change results a two conflicting filecreations

how did you install the jail ? how did you upgrade it ?

hm i see

I used freebsd-update -j myjail -r 14.0-RELEASE upgrade

cant remember exactly how I installed it, but it was not ezjail and I followed the handbook

sopparus: while it is not at all helpful with your current situation, I will note that bastille is a pleasure to work with for jail management

I wonder if anyone is working on adding PkgBase support to bastille or pot

hmm seems stuff got a litle broke in the jail

[#] wg setconf wg0 /dev/stdin

ld-elf.so.1: Shared object "libnv.so.0" not found, required by "wg"

you packages are still built against you old base libs

yeah noticed, the reason they didnt update was becouse pressing y just quits

with pkg-static ?

will try

same

sopparus: libnv.so.0 strikes me as a base lib. you sure that upgrade went thru fine?

i have /lib/libnv.so.1 in 14.0

sopparus: pkg just stopping seems strange what is the exit status? echo "$?" after the command; maybe try pkg-static install -f pkg

rafe: how do you update thin containers and their templates with bastille

meena, it's a solid bet that 1:1,000,000 ratio will decrease as more people poke at it.

sopparus: you will need to run `pkg bootstrap -fy` within the jail, so it picks up the right abi.

CrtxReavr: and more vendors fix their devices…

I am wondering tho, if this type of leakage is exclusive to RSA… (I've been using… not RSA for quite some time)

14 when

babz, let's say your thin jails are on 13.1-RELEASE. you do bastille update 13.1-RELEASE for the base jail to be updated. then you can update the pkg database and the packages in the jail. if you need to upgrade from 13.1 to 13.2, you'll first bastille bootstrap 13.2-RELEASE to create a new base jail, and then shut down the jail, change the fstab to point to the 13.2 base jail, then start it up again and update packages

well, it's very weird

it successfully updates the template

bu dont rename it

so you have i2 13.1-RELEASE containing a 13.2-RELEASE

and it never updates the thin containers so you have recover every one of them individually

so now i'm wondering how is it supposed to help in upgrading vs doing everything manually ?

i used to do it that way (i used to update the base jail from 12.1 - 12.2, for example), but after that you can't upgrade it anymore, and it is named incorrectly.

it's best to only do bastille update 13.1-RELEASE, never bastille upgrade 13.1-RELEASE 13.2-RELEASE. only do that style upgrading on a normal thick jail

wtf

because you go into the thin jail's fstab to point to the 13.2-RELEASE, and you're done

well, then you upgrade pkg and packages, and then you're done

and you can zfs destroy the old release when you're done with it

old release base jail

14

babz: something like this: bsd.to/JprL does that make sense?

Title: dpaste/JprL (Plain Text)

well, step 4 fails

I see that sudo-1.9.15p1 has now finished building in the auto-builders and is now available for installation today. Don't take it!

The changelog says it still has the tty bug. It's -p2 or later that we need to fix the recent sudo tty bug introduced in the 1.9.15 version.

hmm, now I am having my own jail problems

is there a preferred way to merge /etc changes when updating a jail?

bastille does nothing

I am so far doing my own thing with jails but isn't etcupdate the preferred tool now, replacing mergemaster?

yes, I haven't needed to use it yet because I'm not building from source, but I guess I must dig in now

I thought that it was when working from source that mergemaster, er..., etcupdate was needed. No? I have mostly worked using freebsd-update and it invoked whatever it does internally and I just follow it.

I wish the FreeBSD Handbook were organized somewhat differently. I always find it difficult to quickly locate the sections I want. It's fine of course. I am just complaining.

Title: Chapter 26. Updating and Upgrading FreeBSD | FreeBSD Documentation Portal

That's the authoritative documentation and where I got my information on etcupdate for this.

odd, i'm doing "df -m /usr" and getting "du: fts_read: No such file or directory" and it aborts.

And this is where my complaints about the Handbook happen. docs.freebsd.org/en/books/handbook/jails/#jail-upgrading

Title: Chapter 17. Jails and Containers | FreeBSD Documentation Portal

rwp: I said I have *not* been building from source

It's there but it just does not seem complete to me. One must really stretch to connect the dots.

rafe, Oh! Not. Sorry! My bad. In that case freebsd-update can update jails and walk through the etc update side of things. That's what I have been using.

yeah, unfortunately I'm not sure that's the case with a bastille-managed thin jail

Demosthenex, Not that I can help but... On what type of file system is that?

since it's a composite

I'll check the handbook, though!

Ah! So with bastille-managed it is built up layers thin-jail. Gotcha. In that case I think a new composition of layers would be needed to be built up.

That's more like what I do. I create a new jail all fresh from the current version and then apply my configuration on top of it.

yup, i had to ruin etcupdate from the host

otherwise, the jail you not let me log in

babz, it's because a pam module was dropped

(I think that's the deprecated pam module)

yep

Demosthenex, Also upon which OS version are you running? "freebsd-version -kru" And I would verify you are using /usr/bin/du and not something layered on.

rwp: 13.2 i think, let me check

nothing but zfs here.

Demosthenex, If it were me I would run "truss -o df-m_usr.out df -m /usr" and then see if there is a clue in the system call trace up until it aborts.

Demosthenex, I am also running 13.2-RELEASE with ZFS and am not having any problem at this time. Try also "zpool status" to verify the integrity of your zfs pool.

status says both pools ok, that was my first check

Good! And "df -h /" is okay too? Does "zfs list /usr" work or also have problems? "zfs list" itself? Sounds like a very strange problem.

babz, which step 4? sorry, i had to step away

nothing but df -m

scoobybejesus: bastille start

very odd.

well, I fail to see how it's supposed to work

you have to update some config files

it is just choosing a new base jail.

Title: Bastille upgrade / downgrade procedures · GitHub

babz, anything special in your invocation of etcupdate? I can run it against /usr/src with different work and destination directories for my jails w/o issue?

did you build it as a tarball first?

yup that's what I did

and it works

sorry, did you build it as a tarball first?

rwp: you know, i think it was failing across jails in /usr/local/bastile... du -smx /usr worked ok

Demosthenex, Wow! *Everyone* is working on their jails today. It's quite the convergence of activity! Glad you have debugged to the root cause. :-)

rwp: hehe

14

I'm not 14 why are you saying that?

polyex, keep an eye on lists.freebsd.org/archives/freebsd-announce/2023-November for the release announcement.

Title: freebsd-announce⊙Fo

polyex, I have not seen anything telling us that FreeBSD 14.0 will not be announced today. I've been checking. ;)

polyex, But 14 is still "upcoming", right? Though it is good to get ahead of things and test, test, test.

I mean, I'm sure people are being disabused of this notion, but it's on the servers

you can update now

rwp, supposedly 14.0 will be announced as ready to go today. See the chart here: freebsd.org/releases/14.0R/schedule

Title: FreeBSD 14.0 Release Process | The FreeBSD Project

rafe, good point. The builds started on Nov 10th, so I am not surprised it is already "out there".

If it is on the schedule then it is on the schedule! I stand newly informed. Though other testing what is still a candidate until it is announced I am going to be patient myself.

*other than testing...

the pkg repos seem like they are prepared too, so I'm not sure what is blocking the announcment currently

It's fun to see everyone excited like it is almost but not quite time to open presents. :-)

:D Right?

tell that to 12yo me lo

l

Maybe the wait is to wait until time 1700000000 rolls around? It's very close now. Time now 1699987613.

It'll be my first freebsd upgrade

rwp: its already past the release candidate stage, this is the actual release today. The builds were started on the 10th. Unless some show-stopper bug came to light, 14.0 according to announcements so far, will come out today.

nimaje: maybe the hold is because they're waiting for the website update or the writeup to be out with the anouncement ? just throwing it out there.

If being scheduled is enough then why make an announcement? Because it's not released until the announcement. :-)

first freebsd upgrade does it usually take this long or is it my intenret connection ?

aw there it goes

the schedule can be updated, I think the initial schedule had the release at the end of october, but as the schedule wasn't changed today, I guess it is unlikely that it will and it is just waiting for the announcement

freebsd-update upgrade -r 14.0-RELEASE is working its going thought a lot of numbers right now

yeah there will be a ton of patch-sets and what not to go through

yeah f-u is kinda slow for larger upgrades

im at 8580

10720 patches

It's easier to do a reinstall right ?

no, just wait

its saying /etc/group has merge conflict and i have to edit for the system to be functional. any ideas what to do ?

remember next time you can take a zfs snapshot before upgrading.. and if something doesnt work for any reason, you can go back to the snapshot

jb1277976: just resolve the merge conflict and keep your changes..

just save it and go ?

no

resolve the conflict

it probably has some partially similar lines

oh

you might want to keep your old lines and delete the new ones

Why would they insert lines in those files?

You probably should have copied them to another dir and then edit them. Many files/configs are looked for in different places, and some that come with installation are meant to be copied to a another of those directories.

Wait no I am dumb now

/etc/group you said

I dunno. forget what I said

Yes /etc/group and /etc/passwd

wat? Maybe ads a group that you already have added manually? This is weird

Oh well it's done. Not at computer

the stock file will not have groups that were added

for example, when you install programs

I meant like dialer, video, input, audio

But ok, not added groups

Just nothing that freebsd-update on zfs automatically creates a snapshot for you like "zroot/ROOT/default@2023-11-09-11:54:26-0" was my last one.

Those are automatically useful for Boot Environments so even if things go very wrong one can boot using the Boot Environment and select the previous one and then rescue.

Meanwhile... Having local changes such as users and groups is *normal* and just need to be merged during update time. Don't panic! Just merge the files. That's normal update operation.

I had to take the lines out though like >>>≥> $Freebsd etc.. was in there I removed them then everything worked

Those ">>" and "<<" lines are conflict markers and are there to highlight the lines that need the local sysadmin to resolve. In other words... Yes. That's what you are supposed to do.

Previous versions included $FreeBSD$ version control tags. Since the move to git those are deprecated and have been removed from the current release.

Those were seen as useful back in the old days but now with distributed version control they are a hindrance because they will always be changed lines and so having them now is counter productive. They have been removed. Though many people will miss them as they were a nice visual indication of the parent of the file.

I am surprised you still have them upgrading from 13 to 14 since I am on 13 and I already had them go away in the upgrade from 12 to 13.

Which makes me think you are upgrading from 12 to 14 and so now seeing that removal happen now.

Thanks

jb1277976: this merge conflict is usually (for 12/13 -> 14) the change on root for shell /bin/sh

and the $FreeBSD stuff as well

I also had a few entries in /etc/group that changed

Thanks

anyone seen this before termbin.com/01oy after a make quicksearch ?

X isn't working now since the update to 14.0 let me get the log file

i guess X dosen't like modsesetting anymore

is the driver loaded ?

babz: i think so its been working for the past week. i did the update to 14.0 and now its not working

let me see what kldstat says

the default loader config now has

module_blacklist="drm drm2 radeonkms i915kms amdgpu"

babz: do i put that in rc.conf ?

jb1277976: did you update your packages after updating freebsd?

nope my first update

so pkg update ?

yes, kernel modules build for the 13.2 kernel will not work on 14.0 for example

ok

nimaje: it says all packages are up to date

hm, should have said that it will reinstall a bunch of stuff because of changed abi

babz: after i blacklist all that what do i do now ?

what no

seems like you messed up somewhere while upgrading, freebsd-update should have told you to reboot and run it again and at one time to reinstall your packages for the new abi

ok

jb1277976: pkg-static upgrade -f

to upgrade all the packages

hernan: before i did that i ran freebsd-update fetch and it said i had a paritally upgrade pending and it wants me to run install then fetch -F or something

Thanks everyone for helping me

I am not aware of freebsd-update with a -F option but there is a pkg upgrade -f option which you will want to run.

no, first finish the os update

-F Force freebsd-update fetch to proceed in the case of an unfinished upgrade.

Right. I think the order is close to this: freebse-update -r 14.0-RELEASE upgrade, freebsd-update install, reboot, freebsd-update install, pkg upgrade -f

run freebsd-update install again and read what it says at the end about the next step

Though I think, not sure this always works but I think, one can pkg upgrade -f before the reboot. I snagged myself last time because I had changed my root shell to bash from ports and the reboot before the pkg upgrade meant that I booted without a working bash executable. Oops. Used the Boot Environment to rescue myself.

jb1277976: run freebsd-update to update the OS.. from minor/major versions... ie from 14.0 to 14.1 (minor) or, from 13.2 to 14.0 (major)

jb1277976: and packages are the software that run in the OS.

jb1277976: after you do a major OS upgrade, you should probably upgrade (as in reinstall) all the pkgs

what rwp said

Thanks

Now I ensure that I have the toor login also enabled so that I have a backup login shell only in base just in case. I actually use toor with bash and root with the default. And then I always use toor which keeps me reminded of my locally modified setup.

freebsd-version finally says 14.0-RELEASE

now let me upgrade the packages

1397 packages upgrading

jb1277976: as rwp said, "freebsd-update install" should be run twice... once, then reboot, then run again "freebsd-update install" and read the messages in case it says you need to reboot and run "freebsd-update install" again

also, update your boot block

It's always safe to reboot and run install again. If there is nothing to do it will also say that upon the re-run too.

Bootcode: docs.freebsd.org/en/books/handbook/cutting-edge/#updating-bootcode

Title: Chapter 26. Updating and Upgrading FreeBSD | FreeBSD Documentation Portal

Also if /usr/local/bin/pkg the port becomes totally broken by a major upgrade (dynamic libraries in base changed) then run "pkg-static upgrade -f" using the statically linked program to fix it.

Maybe just "pkg-static bootstrap -f" to fix just pkg and then a normal "pkg upgrade -f" afterward.

when I have a poudriere jail with src=/path/to/freebsd/src do I just update the source at that path and then run poudriere jail -u to update it or do I have to build the source manually first?

rwp: im using gpt/ufs when i chose the install. was wondering to upgrade the bootvode show i use the man gpt one ? im looking at man.freebsd.org/cgi/man.cgi?query=gpart&sektion=8&format=html#end

Title: gpart(8)

uefi boot or legacy boot?

How old is your system?

Personally, I only do UEFI these days.

for uefi, it's just a matter of copying loader.efi onto the ESP in place of the loader.efi or bootx64.efi that's already there

I think mbr cause it's an old system I forgot

I'm used to gpt

what's the output of gpart show

Let me go upstairs

so that's GPT (nor MBR) and it's uefi-only

ok

so all you need is to mount the efi partition and copy loader.efi onto it

there a guide for that ?

dunno offhand

did the installer put a line in fstab for the ESP?

If I remember right, you just dd the file onto the efi partition.

no!

No?

the efi image file is only for bootable images, not for actual installed systems - it's too small

Let me look at my fstab

termbin.com/sg31

ok, so /boot/efi is already mounted? what files are in it?

should be /boot/efi/efi/boot/bootx64.efi at least, possibly also /boot/efi/efi/freebsd/loader.efi

yep exactly

details will depend on whether you're using any kind of efi boot manager

what you posted is what i have

if both those files exist and are the same size and content, then just copy /boot/loader.efi over both of them

if you have just the bootx64.efi, then copy over that one

look the same

i will do this after the package upgrade

those look larger than i would expect?

what fbsd version?

14.0

from Feb 24 2022 ?

those probably carried from 13.2 when i upgraded today

interesting, 13.x loader.efi is indeed much bigger than the 14.x one

so overwrite loader.efi and bootx64.efi with the /boot/loader.efi ?

yes

ok

a reinstall would have been easiser lol seriously though

but you don't learn anything that way so i can see why people would go this route

I think I've read xen dom should work in uefi mode now

(I have not tested it yet)