dug up an old thread lists.freebsd.org/archives/freebsd-desktop/2023-December/003877.html

I'll say this, if sound works on Nomad, your hardware is compatible and it should work on regular FreeBSD even if you need to tweak it. The opposite isn't necessarily true: If sound doesn't work in Nomad you still might be able to get it to work in FreeBSD with some tweaking.

Or maybe not.

Thanks

we have an issue with ipv6-only

anyone know how to read this ?bsd-hardware.info/?id=pci:8086-02c8…et+Lake+PCH-LP+cAVS&dev_ident=4414f

How'd it go so far, jb1277976?

win 15

Oops.

more like loser 15

Greetings

is there any problem with freebsd-update repos ?

Fetching 3 metadata files... failed.

I got this error while attempting a 14.1-RELEASE upgrade

lemme try

the fetching seems to have worked, its now inspecting system

I just upgraded to -p4 sucessfully.

14.1-releaes-p4

thank you yourfate , I will check my system

mine used "update2.freebsd.org" as a server. I'm in germany

I cleaned /var/db/freebsd-update directory, seems ok now

nice.

for now , is there any difference for pkg built for 14.0 and 14.1 ?

I don´t see any 141amd64 in pkg-status.freebsd.org/api/1/builds

afaik

s/pkg/packages

Hi, I hope I can explain my question well enough. Here I go; I have in my rc.conf file, two lines; ipv6_defaultrouter="fe80::1%vtnet0" and ifconfig_vtnet0_ipv6="inet6 2a04:e8c0:18:510:1 prefixlen 64"

And my resolv.conf has only: "nameserver 127.0.0.1" (local unbound running), no IPv6 nameserver added there. Now the question is how it's possible that ping6 google.com works and gets responded, an IPv6 hostname resolves without any IPv6 nameserver in my resolv.conf?

tercaL: Try `drill @127.0.0.1 AAAA google.com` I don't think you need a ipv6 nameserver to resolve ipv6 address.

erk: That's the output: pastebin.mozilla.org/8fBOMV1A

tercaL: As you see there you get a response with Googles address which is then pinged.

I don't think ping6 says that the DNS query is also done over ipv6.

erk: So the local unbound of FreeBSD running here (127.0.0.1) actually capable of resolving IPv6 as well?

Yep IPv6 is just the AAAA field in the DNS response.

I see..

Thank you.

is all the breakage from FreeBSD-SA-24:05 (PR 280701) fixed in main now? seems like yes but i'm hesitant to upgrade...

a lot of drama in that PR

yeah, that was weird, seems people are annoyed about bugs in opnsense/pfsense or something? which is nothing to do with freebsd

Is anyone familiar with Burp Suite?

more drama than the "official branding" argument between openbsd and palemoon 6.5 years ago?

to answer my own question, kp@ confirmed all the issues are fixed in freebsd now

antranigv: hey, are you around?

mane: nohello.net/en

:D

sidh: packages have always been built for the oldest supported version

lw: it's always interesting (sometimes the kind found in "Interesting Times" by pterry) seeing the kind of feedback that come from users of downstream project..

Capole_: not surprised that someone's created a website for that, it's a perennial problem

debdrup: i was inclined to ignore it but apparently core@ is getting involved in that PR somehow?!

ok fair that des@ was a bit rude as he always is but this hardly seems like a core issue

<insert gif of Homer walking backwards into the hedge>

as the young folks say nowadays, there's lore involved

so unbound fails to start on boot because some interfaces arent created yet when the unbound script starts

is there any directive correction to solve this?

what causes the interfaces to be created?

if you have a service that creates those interfaces, unbounds rc.d script can be modified to depend on that

that'd delay startup a bit, but it'd make it reliable (provided the interface creation is reliable, i guess - you'll want to build in some error handling in the interface script, i suppose)

mane: try configuring ip-transparent: yes

however, it would be better to fix your rc config to not start unbound until interfaces are available

i also recall having someo weird issues with ip-transparent although i don't remember the details

i used it to let unbound bind to an anycast address that wouldn't be configured until unbound was working

btw, #dns is very helpful for unbound questions in my experience, that's how i discovered that option originally

insert dns haiku here.

How can i get pulseaudio to start automatically when i boot up freebsd ? i installed it via pkg.. also does my pcm need to be there or can i use virtual_oss to get audio ?

jb1277976: you're not meant to use pulseaudio that way, it should be started per-user unless you're doing something extremely unusual, and usually the application handles that

Got it

i'm not sure what you mean by 'does my pcm need to be there' but you do need a /dev/dsp device for pulseaudio to work

lw i have a /dev/dsp and /dev/dsp0

freebsd's /dev/dsp supports multiple opens with an in-kernel virtual mixer so e.g. multiple pulseaudio instances can run at the same time if several users are logged in

(not that you'd really want multiple users to output to the host sound card, but... it works...)

when you have a /dev/dsp etc.. that means your laptop/desktop is recognizing your sound card right ?

sound(4) is also getting actively worked on again

jb1277976: probably yes, but cat /dev/sndstat to be sure

notably, mixer(8) now does hot-swapping

jb1277976: that should tell you the hardware output device it's using

debdrup: yeah Christos and the other guy are doing great work there

they did briefly break my USB audio device but that was fixed pretty quickly

br@ also got some patches for snd_hdspe, which pleases me since i've got one of those from when i was working as a disc jockey at a radio station (just flipping discs)

should let me update the firmware

are those the RME PCIe cards?

yep

lw: let me tell you a little background about me.. i was actually using freebsd for about 2 months. posted lots on the fourms and lists about getting sound to work but it never has. using a chromebook and the only pcm that shows up in /dev/sndstat is pcm0: <Intel Kaby Lake (HDMI/DP 8ch)> (play) default stopped using freebsd since last year and came back to test again. i love freebsd

i wouldn't mind one of those, i have Focusrite stuff because it's cheap but their Windows drivers are terrible

florian (the guy who's working with christos now) was also involved with those

jb1277976: idk sorry, i use a USB audio device which i literally just plug in and it works :(

never really dealt with onboard hda

jb1277976: can I ask what you're using pulseaudio for? With Firefox, it isn't necessary to get audio working..

Got it.. coming from gentoo and i had to use pipewire to get audio working

specially on this chromebook

pulseaudio and pipewire aren't generally needed on freebsd

debdrup: how about virtual_oss ?

jb1277976: short answer is, it depends

cgit.freebsd.org/src/commit/?id=390dc369ef this looks pretty neat

virtual_oss usually isn't needed

i use it because my audio device has 20 channels and i want to force some applications to use a subset of those, like video conferencing / voice chat should only use 1 channel

i've been using it to combine some input channels on one device with output devices on another device - but yeah, i don't think that's very standard :D

yeah

there's definitely situations you'd want to use it but for 99% of use cases like 'i want to play/record audio on my laptop' it's not necessary

lw: what usb audio device do you use ? maybe i can get it so i can have sound ?

you got a link ?

jb1277976: i use a Focusrite 18i20 focusrite.com/products/scarlett-18i20 but you can definitely cheaper (and smaller) options if you just want working audio on a laptop

for example focusrite.com/products/scarlett-solo has headphone and stereo speaker output

lw: you on a desktop ?

jb1277976: yes

Thanks

in fact if you just want headphones, buy one of the Google or Apple USB-to-3.5mm adapters

i've not specifically tested those with FreeBSD but they are just basic stereo audio DACs so they should work fine

(they're sold as 'adapters' but they are a complete DAC in a tiny form factor, it's really amazing)

for the price, the apple usb to 3.5mm DACs are decent quality as well

that's what i just suggested

i know, i was just adding to what you said :)

ah right

i was a bit dubious about the build quality of the Apple one (based on my experience with the old MagSafe PSUs) but i've been using one on my ipad for months and it's working great

The generic kernel that comes with freebsd does it have all modules/drivers in it by default or do you have to create a custom one for a specifc module you want ?

jb1277976: it contains all modules and most drivers (including the drivers that are available as modules)

the only drivers that are not included in GENERIC are some extremely esoteric hardware that you almost certainly don't have

Got it

I can't get any of the freebsd download sites to load. I don't know if this is something on my side or something on the website side, but it won't let me use any of the links.

Welp.

isitdownrightnow.com/download.freebsd.org.html confirms download.freebsd.org is down right now.

Sure seems to work for me.

debdrup, I can certainly ping it too - but I belive we are both from Denmark

BarnabasDK: yep.

so, maybe someone outside could confirm?

I cannot ping either IPv4 or IPv6 download.freebsd.org from Colorado in the US.

hmm, where is it hosted?

DNS wise and physical

173.228.147.97 seems to not be responding

ikolaj@ThinkPad-X1:~$ host download.freebsd.org

download.freebsd.org is an alias for download.geo.freebsd.org.

download.geo.freebsd.org has address 85.30.190.138

download.geo.freebsd.org has IPv6 address 2a02:80:0:3ffd::15:1

download.geo.freebsd.org mail is handled by 0 .

a short host lookup from my end

rwp, what is yours?

download.freebsd.org is an alias for download.geo.freebsd.org.

download.geo.freebsd.org has address 173.228.147.97

download.geo.freebsd.org has IPv6 address 2610:1c0:1040:606c::15:0

trying to see if it is a dns issue or an IP issue

since yours is different from mine, it would lead me to belive your host is down - mine is not

BarnabasDK: 'your' mirror seems fine

does this make sense

mine is not

check - but it could still be a dns issue and/or an IP issue as well

dns issue isnsofaras the geo.dns is still resolving hosts that aren't responding

85.30.190.138 appears to be located in a New York datacenter in an NYI hosting facility.

Oops! Bad paste. Strike that. 173.228.147.97 appears to be located in a New York datacenter in an NYI hosting facility.

so some outage at that facility seems to be the cause

obviously

did a metor finally hit NY

except my mirror, 204.15.11.67 also is not responding

which is on the other side of the country

rtprio, and that is something you run on your own premises?

no, that's what download.geo.freebsd.org resolves to on the west coast

ah

"my" mirror, i use loosely

hah ok :-)

maybe you had a mirror in your basement .. who knows

Seems people.freebsd.org/~dbaio/mirrors/mirrors-new-section.html will be the workaround path for anyone affected by the current outage.

maybe the freebsd team should add a healthcheck or two to their geo resolver

or maybe more than one IP to a name lookup - I think most clients would accept that

ofc you would be depending on said impl

or that

The plus of multiple IPs is that it mostly works when one of the IPs is offline. The negative of multiple IPs is that behavior gets very strange when they are out of sync with each other.

The troublesome case being both online but returning differences.

With one IP the view is usually consistent over the entire repository at least.

and IP lookup caching can make this even more flaky

shifting between ips

I guess there is not one real good solution

I am not using it but the FreeBSD NTP pool also uses GeoDNS too and therefore it is possible to be out of wack right now as well.

oh, for that i use pool.ntp.org

is this a geodns thing?

I actually just learned it by reading freshports.org/dns/go-geodns

Well nothing I can do about it. I am returning to my hole.

Anyone else having issues fetching the ports INDEX-14.bz2, by chance?

I noticed "portmaster -L --index-only" failing and it looks like the FreeBSD.org/ports/INDEX-14.bz2 URL it's attempting to use times out.

took 1s to download

yuripv: Hrm. Very strange. Any chance you can take a look and tell what your host is resolving www.freebsd.org and/or download.freebsd.org to?

Still seems to time out for me. Not sure why. DNS resolution appears to be fine.

ek, Look up in the scrollback to see the recent discussion of some mirrors being down right now.

You can look at people.freebsd.org/~dbaio/mirrors/mirrors-new-section.html and select a different mirror to workaround the outage.

rwp it has been working all along here in europe

i really see no outage here

rwp: Dang. I actually did try to do a lookup to see if anyone had mentioned the index not being unfetchable.

I guess my search-fu failed me. Thanks!

BarnabasDK: It looks like a GEO issue.

ek: 203.80.16.154 and 203.80.16.151

yuripv: Thanks. Very different than mine so that now makes sense.

looks to be Malaysia