How do I use wpa,_supplicsbt to contact to a hotspot?

Or networkmgr ?

jb1277976: freebsd does not hae network manager

Hmm

jb1277976: docs.freebsd.org/en/books/handbook/network/#wireless-authentication

Title: Chapter 7. Network | FreeBSD Documentation Portal

Thanks

Question I'm connected to an open network but I think you have to say yes but I don't know what to do next

you have an ip address on that network?

hmm i'm connected

ifconfig wlan0 up scan list then ifconfig wlan0 ssid <network name> then dhclient wlan0

ok, do what you want. install some software.

something cool preferably

im reading up on the handbook google everything about freebsd and its so new and everything just feels right

i also had to take out WPA out of rc.conf

jb1277976, what are you trying to do

tomorrow i need to connect to my school network. they use LEAP / EAP how would i conncect. trying to get ready for it

like i found man.freebsd.org/cgi/man.cgi?wpa_supplicant.conf(5) EAP but it dosen't give me examples

Title: wpa_supplicant.conf(5)

i found it. i had to read down a little

can someone tell me what '-w' does to bhyve. it's, in `man bhyve` but not explained

" -w Ignore accesses to unimplemented Model Specific Registers (MSRs). This is intended for debug purposes."

my rendering of the manual doesn't have the argument, just the description

Title: dpaste/50s0 (Plain Text)

V_PauAmma_V: thanks

rtprio, that's unexpected. How are you rendering it?

`man bhyve`

i'll git bisect or check bugzilla

at some point

someone probably bjorked the markup

Looking fine in 13.2, if that helps with the bisecting.

s/13.2/13.2-p

-p4

Ah, broken in 14 in online manual pages.

I did `webcamd -d ugen2.3` to make wacom tablet/pen working. it worked but now I see /usr/local/libexec/Xorg :0 -auth /home/user1/.serverauth.2199 taking 200% of cpu. What should I do?

Guys is thre ttf mscorefonts for libreoffice ? im googleing and i'm not finding anything

there is corefonts pkg

jb1277976, Try "webfonts"

Hello everyone! I have a problem, ssh in my truenas core rejects password.  New installation.

hope they found the solution…

Hey all! I've just made my first serious attempt at installing FreeBSD for 25 years. Feels good to be back.

One major issue for me is not getting iwlwifi to work, on a ThinkPad x270. My understading is that it is supposed to show up in the list of network interfaces when running `bsdconfig`?

|cos|: which version did you install?

13.2-RELEASE first, upgraded to 13.0-RC4

sorry 14.0-RC4, of course

There is a relevant hit for `pciconf -l | grep iwm0` (v: 0x8086, d: 0c24f3) so I'm starting off with the assumption there is a misconception on my end.

|cos|: does it show up under the net.wlan.devices OID using sysctl(8)?

I'm on 15-CURRENT, but it was 14-CURRRENT until a little while, and iwm0 has been working fine for me.

Also check tht rfkill isn't enabled, as that's gonna disable the antenna.

debdrup: it is listed at that oid, yes. i'll need to join a meeting now. but will be back. good to know it works for you. thanks!

|cos|: docs.freebsd.org/en/books/handbook/network/#network-wireless has a quick start that should get you going.

Title: Chapter 7. Network | FreeBSD Documentation Portal

debdrup: thanks! got it working. guess it all ran down to getting confused and mitakenly believing bsdconfig(8) should setup everything, given that it has the feature to scan for wiki networks.

my second question, which requires me to reinstall, is due to only being able to boot if bouncing on iPXE...

i kind of understand the issue. one needs a msdos partition with some crap for the uefi-stack to work. what's the best practise/easiest method to add such a thing while installing freebsd? i didn't see anything in bsdinstall, but maybe i should just read the fine manual better there too?

Running `bsdconfig wireless` is meant to do what the handbook does, so if it doesn't work then that might be a bug; if you can reproduce it, it might be worth filing a report about it on bugs.freebsd.org

Title: FreeBSD Bugzilla Main Page

this seems to answer my second question: wiki.freebsd.org/UEFI so sorry about that noise

Title: UEFI - FreeBSD Wiki

On one of the install screens you can pick whether you want MBR or GPT or UEFI

UEFI will give you the ESP (EFI System Partition) that you'll need

ah. i'll look out for that third option. thanks! and see if i can reproduce the wifi-issue.

If you do, you might find docs.freebsd.org/en/articles/problem-reports handy.

Title: Writing FreeBSD Problem Reports | FreeBSD Documentation Portal

Hi

How do I get wifi working? I have a wifi chip that is compatible

Iwm driver on OpenBSD

Ok so itseems I need to enable wpa_supplicant

pretty sure that wpa_supplicant autostarted when you configure your wlan in rc.conf

basically give the interface some name via eg. wlans_iwm0="wlan0" and then configure via the ifconfig_wlan0 variables and wpa_supplicant.conf see also docs.freebsd.org/en/books/handbook/network

Title: Chapter 7. Network | FreeBSD Documentation Portal

So, 14.0 RC4 installer, I'm asked what network interface I want to use, and I say I want my wifi, and it doesn't get past this: 0x0.st/Ht_9.jpg Is this expected? Is there a description of what it wants changed to use it?

I don't think I've ever seen that error message before; have you gone through src/usr.sbin/bsdinstall to figure out what exactly it means?

debdrup: Nah, just seeing it for the first time as I did an install in the background. I was wondering if it was a known thing or not. I mean, the message exists, so someone knows about it I guess.

I'll dig in.

well...

Title: wlanconfig « scripts « bsdinstall « usr.sbin - src - FreeBSD source tree

Title: src - FreeBSD source tree

is that a 7 years old refactoring fail ?

Oh, that seems straightforward enough then. Unfortunate it doesn't try an initial config itself.

Oh, it does. REading more.

I don't like that error message, at all. It's extremely un-clear what that should even mean.

And even after looking at babz' link I have no idea why it even exists.

Yeah, I'm not sure what it's trying to test for.

It makes no logical sense to me either, of course you can configure your wifi without making changes to the local system.

What will that installer do if I just switch to tty2 and use wpa_passphrase/wpa_supplicant/dhcpcd? Throw black confetti at me?

sure that isn't booted with the dvd ?

This is in the context of the installer, which is a read-only thing unless you remount it with -u

And why would I not be able to configure my wireless?

ro

It won't be able to copy my configuration to the installed system, yes, but I can sure as hell configure my wireless.

That message is simply questionable at best.

How can you write to a file that's on a read-only filesystem (possibly because the media isn't rewritable, but even if it was optical media, you'd need DVD-RAM)

You don't need to write to a file that's on an ro FS to connect to your wifi?

I'm wondering if it's got anything to do with bsddialog.

That was imported in early October.

There's simply no need to do that, which renders the message shown pointless.

mason: can you reproduce it?

So that wlanconfig script sources some file /usr/share/bsdconfig/common.subr upon startup, and that's probably how $BSDINSTALL_CONFIGCURRENT gets set.

Still, the whole thing doesn't make sense to me any further from here.

debdrup: Reproduce the error? Sorry, was AFK.

armin: You can get past the read-only install environment a couple ways. What I do for installs is typically: wiki.freebsd.org/MasonLoringBliss/InstallEnvironment

Title: MasonLoringBliss/InstallEnvironment - FreeBSD Wiki

That said, for this I wanted to run the installer as shipped to test.

Yea, uhm, can we reproduce that on our machines with the standard installation images?

I think that's a bug.

I don't know what the intention was when the author wrote this.

armin: Should be able to. I just downloaded FreeBSD-14.0-RC4-amd64-disc1.iso for the purpose.

mason: Will do so somewhen this evening and test. :)

mason: Thanks for your work!

armin: Hardly any work! Just noticing and whining in the right ears. :P

:D

mason: yes, if you can reproduce it then it deserves a report.

armin: I got a T480 and I threw Debian on it, so now my T420 can be devoted entirely to FreeBSD. The real work I want to do on it is to get SMAPI going, likely by starting with github.com/sghctoma/thinkpad-smapi which is already 99% of the way there.

Title: GitHub - sghctoma/thinkpad-smapi: Thinkpad SMAPI driver for FreeBSD

debdrup: I'll run it a couple times to see the error and I'll open up a bug report. I'll mention it here and ping the two of you.

I can continue my trend of late-in-the-game bug findings against RCs.

It's always better to get that done earlier in the work up to a -RELEASE. ;)

Yes. The inspiration didn't strike until today, reading some more discussion of UsrMerge. I had my standard "to Hell with all of this, I'm doing more with FreeBSD" reaction.

Oh, fascinating. Varied the approach, and this time it didn't give me that screen. Didn't change zpool naming, didn't select custom keymap. I'll do it again the way I did the first time and see if I get the error again.

Or, closer to the way... I'd gone into a shell and wiped my EFI variables, then ran bsdinstall.

Hm.

ANOTHER problem is that the script doesn't support WPA-EAP

Which should be pretty simple to solve, actually, too.

Well then, sounds like you'll be contributing in the future then? ;)

Hrm, second try and the installer blew up seeing what the previous run had left.

I'm working on it.

debdrup: Yea I disagree with much of the code style, but that's a different topic. :)

debdrup: UPPERCASE_VARIABLE_NAMES used entirely within shell scripts make me itch.

But still, I believe there's some kind of logical error going on in that script.

You shouldn't end up with that from the installer by any reasonable measure I can apply. There's no reason to not let you configure your wireless even if you can't write to some disk.

That, and the WPA-EAP thing, you simply couldn't connect to your university wireless with that.

That's a huge problem.

(meh!)

elif echo $ENCRYPTION | grep -q EAP; then

USERPASS=$( $DIALOG \

--title "WPA-Enterprise Setup" \

--backtitle "$DIALOG_BACKTITLE" \

oh wait, this is new.

Don't paste into the channel, please.

ok. :)

armin: style(7) isn't really up for discussion.

EAP-TLS is described in the handbook: docs.freebsd.org/en/books/handbook/…rking/#network-wireless-wpa-eap-tls

Title: Chapter 34. Advanced Networking | FreeBSD Documentation Portal

Case in point, this wouldn't work in a read-only environment like the installer, because of the certificates.

Yea and that SHOULD work in an RO env.

I mean the perfect example is you just have the bootonly or memstick booted, and you want to install FreeBSD by utilizing your wireless network.

That's a very reasonable thing to do.

So question remains, is the reason that 0x0.st/Ht_9.jpg popped up that they tried to connect to a WPA-EAP enterprise wifi or not?

I'll be honest, I got no idea why you're so bullish on EAP-TLS, when there's been no mention of it besides yours.

debdrup: because the screenshot shows "FreeBSD Installer" and I want to know why the installer thinks that you can't connect to a wireless just because you can't write to some disk.

Considering that modifications were made to the environment before bsdinstall was run, that's probably more likely to be it than EAP-TLS.

It seems bsdinstall(8) does find my wifi device when booting 15.0-CURRENT, so I'm understanding it being broken in 13.2-RELEASE is not a bug to report.

debdrup: but I'll be honest, I don't like that "bullish" word in that sentence.

armin: are you sure 13.2-RELEASE supports the specific device you have?

armin: that's fair.

err, mistell, sorry

|cos|: The message about 13.2-RELEASE supporting the specific device was for you.

I could rant about dhclient and rsold now, but I refrain from doing so. :)

Please do.

Sorry, that was ambiguous; please do refrain.

for ranting there is -tavern

debdrup: understood. i'm not 100% certain, but i got the impression it should. with 14.0 being days away it's not really something worth digging into..

|cos|: what gave you that impression, if I may ask?

debdrup: on the phone. back soon.

|cos|: when you get in front of the machine again, and if you still have access to 13.2-RELEASE, make sure you've loaded the firmware.

/etc/rc.d/devmatch does quite a lot of work that used to be manual, if memory serves.

13.X will be supported for a while still, so bugs should be reported and fixed

nimaje: I just joined there, thank you.

nimaje: we first need to establish that a bug exists.

yeah, I only made the general statment, that bugs should still be reported for 13.x (until its eol in 2026), no idea if that case is a bug or just hw that isn't supported in 13.2

I did `webcamd -d ugen2.3` to make wacom tablet/pen working. it worked but now I see /usr/local/libexec/Xorg :0 -auth /home/user1/.serverauth.2199 taking 200% of cpu. What should I do?

> kernel: pcm0: es1371_wait_src_ready: timed out 0x10 [0xffffffff]

is it possible to reset sound card without reboot?

pcm0@pci0:5:2:0: class=0x040100 rev=0x02 hdr=0x00 vendor=0x1274 device=0x5880 subvendor=0x1274 subdevice=0x2000

VVD: devctl?

"devctl detach pcm0" ?

or reset

I suggest you read the manual page to find out what the options do.

Already read - descrition isn't clear and without examples…

I'm not sure how they're not clear; detach detaches the driver from the device, reset resets the physical connection.

debdrup, not clear what mean detach/attach/reset - is it same as reboot or not?

After reset players play audieo, but no sound.

Before reset players stalled on 1st second.

detach/attach is about the kernel device interface, reset is the physical connection and requires retraining of the device.

I'm not sure I can explain it any other way.

ix.io/4KRm how should i go about reverting that file to what it should be?

debdrup, what option is equivalent to reboot?

reset -d and reset - no sound

attach it again?

llua: have you read what freebsd-update is telling you?

yeah

llua: do you understand it?

that a file has been changed locally, one i don't remember changing.

hence my question of reverting it

nimaje, detach/attach - pcm0 removed, then added again, but no sound via this sound card

reset pcib5/reset -d pcib5 - still no sound (pcm0 connected to pcib5)

hm, no idea then

llua: the path to the file indicates that it's file that etcupdate has touched, which was done by freebsd-update - ie. it's not your systems sshd_config that's been changed. If you want, you can grab the correct file from the distribution set (base.txz) on download.freebsd.org for the relevant version.

Title: download.FreeBSD.org

i know my /etc/ssh/sshd_config isn't the problem. that wasn't the question, it was /var/db/etcupdate/current/etc/ssh/sshd_config so i can ultimately make that section of the message not show again

debdrup: your condescendingness aside, thank you for informing me that is /var/db/etcupdate/current/etc/ssh/sshd_config was in base.txz. that does indeed resolve the issue for me.

Yea that's another nice example of an error message that makes absolutely no sense to me. "I refuse to download something because you have modified a file on your computer!"

wat.gif

llua: I was trying to understand what you were asking help with

armin: it's being conservative, instead of just overwriting a file.

debdrup: I disagree with that mindset, but ok.

armin: then FreeBSD probably isn't for you.

debdrup: FreeBSD works just fine for me since 15 years.

debdrup: And if some error message is clear nonsense, I will *still* point that out.

armin: I have no issue understanding the error message, and it doesn't seem like llua had any problems either.

I think the error message is appropriate as well.

What's the point in refusing to download something because you edited a file again?

armin: I don't understand how you can use FreeBSD for a decade and a half, and not be used to the conservative approach it has always had.

reboot to fix sound :-(

debdrup: I'm all up for the conservative approach, you might confuse something major time here.

hm, it reads to me like it detects that nothing needs to be downloaded and additionally it detects that this sshd_config changed

armin: I'm not sure why it's such a big issue that it's refusing to download changes.

nimaje: yup this.

debdrup: because it names as a reason that you edited some file, I don't know what you do on your computer, but editing files is a thing I do, and I've never in over 30 years of using computers considered that a boundary to download something.

armin: You don't consider system configuration files important for the OS not to rewrite willy-nilly?

download != override

debdrup: that's a completely different step. downloading something is NOT the same as overwriting some local file, no.

What's the advantage in downloading it and storing it locally vs downloading it later?

wat

I'm not sure what you want freebsd-update to do.

make sense?

#define sense

lolwat

The way it works makes sense to me.

ok then :)

the behavior seems fine to me, just resolving the underlying problem wasn't as obvious.

the command there was fetch, the user explicitly requested downloading

maybe I dont have all the informations, but I'd expect the 'fetch' verb to download things *now* so that I dont have to download them later

nimaje: and it's refusing to download because doing so would risk overwriting files.

I'm willing to accept that I'm wrong here, but nobody has explained to me why it's a bad thing to risk overwriting a file.

Err, to not risk overwriting a file.

shouldn't /var/db/etcupdate/current mirror the current default files so that they can be merged with etcupdate(8) ?

but why would downloading something override some file that is in base.txz?

babz: I'm not sure it would, it depends on what changes etcupdate tried to do to it, I thhink?

nimaje: Sorry, I'm not sure that makes sense to me.

debdrup: because there's no need to overwrite that file, name it differently and inform the user, but refusing to download!?

debdrup: that's like crossing 4 iso/osi-layers at once.

Nope, I'm out.

¯\_(ツ)_/¯

if it comes from base.txz, then why would freebsd-update fetch write to that location?

Is the man page the oldest place to learn more about freebsd and the handbook and wiki of course. Anything else I should read up on ?

Best*

that's a good start; have you used other unix/linux systems before? what are you hoping to accomplish with freebsd?

nimaje: thanks for clarifying that valid bugs all welcome for all supported releases

debdrup: verified, my device works on 13.2 if configured manually. i think my impression came from the vendor and device id for it being mentioned on a webpage which stated to only had been updated during the early development phase or similar.

well, knowing it works in some later release can help find a bug and maybe some change can simply be backported

jb1277976: Back in the day before the web, when we just had man pages, I used to print them out and read them. Learnt Perl that way. The man page is *always* in m view a good place to start.

+1 on mns words

I learnt Motif and OpenLok and xview and X11 using them as well lol. I lost my way after the web, but my return to BSD, FreeBSD, is bringing me back into the habit of reading man pages more.

that and the source code

thanks |cos|

a bigger fish try fry than the backport is perhaps that neither 13.2, 14.0 or 15.0 lists any wifi networks in bsdconfig(8). scanning with ifconfig returns results.

i'll think of by bug filing while grabbing some dinner here

mns: the only reason i learned how to work dialup on freebsd was i had man page for ppp printed out on top of my toilet

lol rtprio

oh noe.

Thanks

i did the 2 floppy install. one box dd's while the other is installing

that also took a long time

So I just got on campus right about to fire up freebsd and configure wpa_supplicant right pressed the power button, didn't turn on pressed it down longer nothing. OMG my laptop is dead 😭

Now I'm using ChromeOS

wat

Can't play with my shiny new freebsd laptop at school cause laptop is dead

I have to use there Chromebook's

rip

FreeBSD broke your laptop?

I've had a laptop refuse to turn on, but restart after removing the battery for a few seconds. A power management bug, I guess.

I remember the good old times when i could just unplug my laptop's battery

lol meena

it took me a month to get this man page committed, and now that it exists people are adding improvements: reviews.freebsd.org/D42458

Title: ⚙ D42458 pmap_kextract(9): some additions

How do i find out what sound system i'm using ? pulseaudio or pipewire ?

jb1277976: by default, probably, OSS

jb1277976: ps awux | grep $suspects

joe 2345 0.0 0.1 107824 10708 - I 13:53 0:00.25 /usr/local/bin/pulseaudio --start --log-target=syslog

yet this gtk app im using says OSS

what's the app ?

it seems that i am observing that under some conditions nullfs does not actually delete data on the underlying filesystem until the nullfs mount is unmounted. wondering if anyone has seen this and if so if there is a workaround that does not involve unomunting