-
polarian
V_PauAmma_V: if I try to pass ipv6_static_routes I get the following:
-
polarian
ifconfig: ipv6_static_routes: bad value
-
polarian
currently following one of the solutions earlier, I have the following:
-
polarian
ifconfig_wlan0="WPA DHCP inet6 2001:8b0:57a:2385::b prefixlen 64"
-
polarian
ah shite I probably should have filtered the IPv6 address but meh
-
polarian
I am starting to think the other solution was a better one
-
polarian
oh I forgot to add the ssid
-
polarian
oh wait ipv6_static_routes would be well static... and therefore break when moving network...
-
polarian
I will try the DHCLIENT-SCRIPT(8) method which was recommended, this seems simpler than messing with rc.conf
-
V_PauAmma_V
You don't pass it to ifconfig. You define it in rc.conf and let rc parse it and deal with components accordingly.
-
polarian
I realised that, but the issue is that would not be per ssid
-
polarian
it would be global
-
polarian
which isn't what I wanted
-
V_PauAmma_V
Fair enough.
-
polarian
so yeah dhclient-script(8) seems like the best bet
-
polarian
unless someone else has any ideas?
-
scoobybejesus
polarian: have you tried doing dd tasks with pv instead? I believe it will often be a dropin with better defaults
-
polarian
scoobybejesus: no... but after reading the linked docs, just specifying 1M block sizes and setting the conv=sync flag seems to give the expected performance...
-
scoobybejesus
pv will throw in the progress bar capability as well, but true true
-
polarian
scoobybejesus: status=progress gives enough information for me :)
-
polarian
sometimes more is less :P
-
polarian
sorry... less is more... geez
-
rtprio
are you really running dd often enough to be made aware of the status?
-
debdrup
SIGINFO is nice, because it works in a lot more utilities than dd.
-
|cos|
tsoome: do you have suspend-resume working with freebsd on a macbook? arm or intel?
-
rtprio
debdrup: yes, i lament that ^T doesn't work everywhere
-
debdrup
On the BSDs, it'll at least print what the kernel thinks is going on.
-
tsoome
|cos| sorry, I do not have fbsd installed directly on hardware
-
newtonomad1592
Good afternoon all. A quick preface, I'm pretty new to BSD as a daily driver and though I'd pick up a distro to save myself a little bit of sanity. So, I'm running on NomadBSD which is based on FreeBSD 14 p4. I'm here today to ask about setting up Bluetooth audio, as I've just been going in circles over the last day or two trying to get it to work. So far I've followed along with a method I've seen a few times,
-
newtonomad1592
so I'm just going to link the one post that I've actually been using following this. The part I'm getting stuck at is the actual point where I set up audio. I can't seem to connect to the DSP device properly? I think? I'll grab the error in a second, will follow with the link
-
newtonomad1592
-
VimDiesel
Title: [Bluetooth-audio] How to connect and use Bluetooth headphones on FreeBSD | The FreeBSD Forums
-
newtonomad1592
This is where I'm getting stuck virtual_oss -T /dev/sndstat -S -a o,-4 -C 2 -c 2 -r 44100 -b 16 -s 1024 -R /dev/dsp0 -P /dev/bluetooth/headphones -d dsp -t vdsp.ctl
-
newtonomad1592
And this is the error: virtual_oss: Could not open DSP device '/dev/dsp0': Operation not supported
-
newtonomad1592
I'm guessing that /dev/dspX are audio devices, however I'm not sure what is what, and I can't seem to figure out how to figure that out
-
|cos|
tsoome: ok. i can kinda see why, after myself attempting running it on a macbook... thanks for answering!
-
mewt
ls
-
mewt
...
-
mewt
alright, I've just tried to upgrade to 14.0 and encountered a problem
-
mewt
libcrypto and libssl need to rebuilt, seemingly. I was not aware this had to be done, and probably did it wrong. Now I'm in a situation where I cannot run "make install clean" in /usr/ports/ports-mgmt/pkg. It fails with ld_error:duplicate symbol: nbactions and many more similar errors on attempt to build pkg
-
mewt
I cannot upgrade pkg because of the crypto and ssl library issues here
-
mewt
how can I proceed?
-
mewt
-
VimDiesel
Title: Solved - pkg not working - ld-elf.so.1: Shared object "libssl.so.111" not found, required by "pkg" | The FreeBSD Forums
-
mewt
the problem is that random packages still seem to want openssl111
-
mewt
and yet I've upgraded everything
-
mewt
ldd does not show this version if I run it on /usr/sbin/pkg
-
nimaje
/usr/sbin/pkg is just a small wrapper to install and call the real pkg /usr/local/sbin/pkg
-
mewt
so why does it look for libssl.so.111
-
mewt
that shouldn't be part of this release
-
nimaje
you upgraded via freebsd-update ? and try to rebuild your ports after the first restart as it should have told you
-
nimaje
?
-
mewt
I tried to upgrade ports one step too late I believe
-
mewt
pkg-static shows pkg's version as 1.21.3 if I check it
-
mewt
/usr/local/sbin/pkg shows a dependency on .111 even after upgrading pkg via pkg-static
-
nimaje
I think pkg-static install -f pkg should work
-
mewt
it did not
-
mewt
this is the result *after doing this*
-
mewt
"FreeBSD_version: 1302001 " shows as in the info for pkg, which doesn't make sense to me
-
mewt
could this be relevant?
-
mewt
freebsd-version yields 14.0-RELEASE-p6
-
nimaje
ah, pkg-static is detecting ABI wrong, because of that mishap
-
mewt
right that is what that sounded like
-
mewt
is there a way to force it to use correct ABI and re-upgrade everything?
-
mewt
everything in freebsd-version -kru shows 14.0
-
mewt
aha
-
mewt
now I've got the ABI change made, let's see if things will fix
-
mewt
pkg seems to have shaken off its ailment now, so that's promising...
-
mewt
Yep ok, I just set the correct ABI in pkg.conf manually and it appears it's happy now. lmk if that's a bad idea or incomplete I guess
-
nimaje
now that it is fixed pkg should detect ABI corrctly again, so you should change it back to the variable and when upgrade to 15.0 remember to update your packages before the last freebsd-update call removes the old libs and in case it you have that problem again, I think you can set ABI via the environment