01:12:49 nimaje/oxbar: thank you, I had the exact same question. nice to see its answered when I look for it, didnt even have to scroll back :-) 01:13:01 I guess I will try 14.1 for now 06:06:26 good morning! I trying to get my macbook air from 2012 with swedish keyboard layout to work.. at the moment I using this configuration https://pastebin.com/n7K5mQJ5 in my keyboard.conf under (/usr/local/etc/X11/xorg.conf.d/), but my FN doesnt work :( so neither brigthness or volume up/down/mute works.. I hope someone can point me in right direction to get it to work, One strange thing is when I remove 'us' 06:06:32 from XkbLayout and I starting X I dont get swedish it still using us keyboard layout, but when I adding it back it´s swedish keyboard.. 07:17:13 <|cos|> nwe: interesting problem. it appears linux has some `hid_apple` kernel module to deal with apple keyboards. i fail at finding something similar for us. 07:24:18 |cos|: yes, as you mention with linux they are using hid_apple and there it´s working, but now I dont want to run linux on it ^^ I have run linux for severral years, and like freebsd more in that sense it taking care of everything not like linux everything is picked from everywhere and it glue it together.. BSD is a whole OS :) 07:27:48 tsoome: I reduced the panic to this commit 2eeb95ccf39ac5d79326c4482112b6b7dd5fc8b2 - reverting it fixes the problem 07:43:34 Hey all. I have the following ever since I started to use VNET jails, and I never really bothered to look at it. But now I'm moving some more mission critical things to this server and setup the daily root mails and get annoyed by it. can someone help please? 07:43:57 https://dpaste.org/0xoah 07:44:27 the ip (192.168.10.12) is configured on vlan6, which is configured on one of the physical interfaces of the server 07:45:46 02:ff:60:31:10:84 is the mac address of the vnet intefrace of a jail, 00:25:90:c0:63:b8 is the mac address of the physical nic + the vlan configured on the host 07:46:05 the jail does not have this ip configured, that's the first thing I checked 07:46:45 mvanbaak: i'm no network specialist. but to me the message looks like the opposite of what you say is actually the case 07:47:16 mvanbaak: which doesn't mean i don't trust what you're saying 07:49:42 ifconfig output: https://dpaste.org/7RCQC 07:51:20 jail config of the jail with the mac address in the log: https://dpaste.org/zgLtt 07:51:34 SKull: believe me, I have thought the same way for months 07:52:39 ifconfig inside that jail: https://dpaste.org/0M1CK 07:55:51 mvanbaak: if you have an physical interface for that ip, then why do you give the jail an epair instead of that physical interface? 07:56:38 the jail has a different ip. it has 192.168.10.249 07:56:44 the 10.12 ip is for the host 07:58:46 yeah, I misunderstood your problem description at first 07:59:55 recap: the ip 192.168.10.12 is configured on vnet6 on the host, which is configured on one of the physical interfaces of the host. This is also what I want. This way I can reach the host on that ip. 08:00:08 why do igb0 vlan6 and vlan100 have the same mac address? 08:00:30 There's a jail called 'ssh' with the ip 192.168.10.249 (using VNET) and this is also what I want 08:00:52 erm, good question. They are cloned interfaces 08:01:22 ifconfig_igb0="up" 08:01:24 cloned_interfaces="vlan6 vlan100 bridge0 bridge1" 08:01:29 o0x1eef it would be best if you can mail the details to kib@ - so he can check what is going on there... 08:03:00 tsoome: I reported a bug here https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285976 - should I cc him there? 08:03:55 yes, because he is the author and the commit has MFC flag - if there is indeed problem, the MFC should be postponed till issues are fixed 08:04:04 +1 08:04:29 I can drop the link for him now too. 08:05:09 Thanks! 08:05:10 did it:) 08:46:00 So, if someone has an idea, please let me know 10:05:21 mvanbaak: do you currently need vlan6 and vlan100? if not, try removing them and see if the problem continues to exist 10:07:12 I do :( without vlans there's no traffic to the machine 10:08:08 reading the handbook again, it looks like setting up vlans no longer works with `cloned_interfaces` in rc.conf, but with `vlans_` and `create_args_` so I will update that later and reboot to see if that fixes it 11:13:43 Is something up with the pkg latest release? It seems packages that should be there are missing, like e.g. go124 11:24:30 <|cos|> nwe: you already knew about the linux kernel module? it was news to me, but the source code i would start looking at to see how it actually works. maybe those apple usb vendor and product id:s are possible to search for. i'm not sufficiently motivated to dig further. my macbook doesn't even have sound. 11:25:55 seems like there is/was a bug in -CURRENT, that resulted in a fail to build the pkg repo(?) https://lists.freebsd.org/archives/freebsd-ports/2025-April/007557.html and if you look at the builds themselve they have some build failures which result in many skipped packages, e.g. go* and webkit-gtk failed to build 11:25:57 https://pkg-status.freebsd.org/beefy22/build.html?mastername=142amd64-default&build=4ff0a7ba4d1f 11:35:55 mvanbaak: do not put IP addresses on bridge member interfaces. the IP addresses should be configured on the bridge. 11:37:11 hum, so vlan6 should not have an ip, it should be added to bridge0 as is done already, and the ip address should be on bridge0? is that the solution? 11:37:27 yes, correct 11:37:38 i can't guarantee this is actually the cause of your arp message but it's possible 11:37:39 oh wow, TIL 11:38:03 I will update my configuration later today and try. thanks a lot 11:39:58 nimaje: Ah, thanks! 11:46:52 |cos|: I understand which model is your macbook? 13:58:33 Hello people. This snippet compiles fine on godbolt; on FreeBSD-14.2-RELEASE (same clang version, 18), it just fails inexplicably. 13:59:37 now that I think about, godbolt might not be using libc++ by default.. *ponders* 13:59:53 so, I have a really strange issue right now 14:00:08 I'm trying to set up syncthing 14:00:22 and I followed the guide on the wiki, minus opening the ports because I don't even have pf running currently 14:01:03 and whenever I start the syncthing daemon, my network goes down 14:01:22 and it only comes up once i stop syncthing, and redo dhcp 14:02:29 can't find anything in any logs, including dmesg, ifconfig output remains the same 14:06:05 xcvb: i don't have a system with llvm 18 to test, but fwiw this compiles fine for me on 15.0 using llvm 19.1.7 14:07:05 I'm completely stumped on this one. can't find anyone having the same problem. I am on CURRENT though, could be some strange bug I suppose\ 14:11:53 xcvb: with clang 19 it compiles fine if you explicitly request -std=c++20 14:12:14 what error do you get with 18? 14:15:13 I guess I can try a different network connection to see if it's a driver issue 16:02:19 mtll: i had syncthing running on 14.2 until fairly recently 16:06:49 I try to build py-psycopg2 from ports, but it seems that somewhere along the build process, py311-wheel044 gets installed which then later clashes with py311-wheel. 16:06:49 here is a build log from a fresh jail: https://pastebin.com/pgvrDnaB 16:12:46 Anyone got a clue on how to get networking to work on bhyve ? Obviously it’s not easy cause there are so many how to’s and troubleshooting guides.. I thought you just create a switch then bind it to your interface like wlan0 and it should work 16:13:01 I been at it trying different things since yesterday. 16:15:10 <[tj]> Setup a bridge and Nat WiFi 16:15:29 <[tj]> WiFi is special and needs complicated magic to bridge 16:16:10 [tj]: there a guide I can follow ? 16:16:15 i've only done that with wired ethernet so far, and that seemed to work okay 16:18:29 Bridging is bridging. Same process for any interface (providing it can be successfully bridged.) 16:21:09 Here are the rc.conf options I used: ifconfig_igb1="up" cloned_interfaces="bridge0" ifconfig_bridge0="addm igb1" 16:21:09 then, when creating the VM, i've used "virtio-net,tap0", and then added the tap interface to the bridge: "ifconfig bridge0 addm tap0" 16:21:13 <[tj]> https://adventurist.me/posts/00304 16:21:27 after that, my bhyve vm was up and running 16:22:18 Grabunhold_: Yep. It's pretty straight forward. 16:23:40 i've written a small python daemon to manage it all: https://github.com/avollmerhaus/Anlasser 16:23:40 it's mostly a stupid hack, but i'm using it for my hobby projects. i should port it to async python when i have the time. 16:24:14 ek: that's not true on the protocol level, bridging wireless requires the 4-address packet format (WDS) - that's why wifibox does routing instead 16:24:25 [tj]: Thanks.. I don’t have a jail but I’m assuming I can use the vm as a jail.. also after I create that bridge and bar so I still add vm switch create public then cm switch add wlan0 ? 16:24:50 Vm* 16:26:34 ivy: I've bridged wifi interfaces before using the same process as I use for wired interfaces. Haven't had a problem. 16:27:01 Granted it was *only* bridging. Nothing special after that. No NAT or anything. 16:29:29 perhaps the wireless driver is rewriting the MAC address to be its own address, which would work if you're only bridging local interfaces (for jails etc) but not if you want to bridge an actual ethernet into a wireless network... if the latter setup works by default i would be surprised 16:54:18 <[tj]> oxbar: an epair and a tap here are equivalent and it will work 16:58:54 <[tj]> oxbar: but also, read the entire thing it covers a vm in bhyve 17:01:53 I trying to install xfce with pkg install xfce, but only got 'No packages available to install matching 'xfce' habe been found.. 17:02:12 running Fbsd 14.2 17:04:02 nwe: pkg search xfce 17:05:00 ah looks like the metadata package is named xfce4-wm :) 17:07:47 nwe: i think that might just be the WM, not the xfce4 meta package 17:11:12 Grabunhold_: I'm not sure how, but the problem magically went away 17:11:27 I went to test with usb tethering instead of ethernet, that worked 17:11:36 then I went back to the ethernet and it still worked 17:12:14 I guess I'm just gonna cross fingers that it'll never recur 17:12:50 Grabunhold_: aha, but I cant find any other packages that looks like xfce4 meta package. 17:13:37 is there a way to tell zfs list to output all values as MB or GB so they are consistent? i know -p outputs bytes, but that's too big ;] 17:14:39 all values in gb, not 'whichever human readable' ? 17:14:50 yep 17:14:54 like df -g 17:15:45 i do not recall that being an option 17:17:36 man zfs-list doesn't indicate anything 17:19:12 what would be kinda useful is a little program you can pipe stuff like zfs list into an convert the units to the units of your choice 17:19:44 surely someone must've written something like that at some point, it's very unix philosophy 17:20:34 closest helpful thing might be zfs list -S used (or whatever) to sort by size, so at least you aren't going back and forth randomly between K/M/G/T 17:22:11 scoobybejesus_tl: that does help 17:22:22 "human readable" breaks so much stuff 17:22:25 even for humans 17:22:35 i still scream on redhat boxes where they don't have df -g 17:27:36 how do you make 'kyua test' just print why the test failed instead of writing it to a database? 17:28:18 try kyua debug instead, maybe 17:29:12 mtll: that sort of exists for zpool list 17:29:33 https://drop.17es.net/-zkWHcWMt9M 17:29:50 (my script adds hours/temperature to the drives) 17:31:16 kevans: ah that's a bit better, thanks 17:37:43 ivy: I think there's some ongoing work to make kyua debug more useful for debugging 17:38:19 creature comforts like giving you a chance to debug with artifacts on the fs before it nukes everything 18:05:34 any ideas on this build failure? https://pastebin.com/pgvrDnaB it seems that py311-wheel044 and py311-wheel are both pulled into the dependency tree 18:14:28 it seems py-psycopg2 depends on py311-setuptools, which in turn pulls in py311-wheel044. but py-psycopg2 itself pulls in py311-wheel 18:14:49 leading to a clash later on 18:28:47 note to self ... the packets do not go through the firewall if the wifi interface is down 18:31:18 anyone tried to build https://github.com/koreader/koreader in freebsd? 18:39:28 dch: how long were you looking for that problem before the lightbulb moment happened :P 18:39:44 polarian: both before and after dinner 18:39:54 yikes, not as bad as this https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=285833 18:39:55 long enough to start pflog on the server 18:41:56 couldn't figure out the issue, had a sneaky suspicion what it could be, I believe it was i vy which reassured my suspicions that the docs were wrong :P 18:42:14 it caused me to procratinate for 1 month :P 18:43:19 installing py311-setuptools via pkg before attempting to install py-psycopg2 from ports fixes the issue with py311-wheel044 18:44:45 fold: I don't see why it would not, lua works just fine on freebsd afaik, I assume it just hasn't been ported yet, you could give it a shot yourself? has a nasty licence though 18:47:16 polarian: yeah I just want to set a laptop to read and take notes 18:47:26 and I was thinking of using freebsd 18:47:32 maybe I should try then and report 18:48:17 it's mentioned here what to take in account https://github.com/koreader/koreader/blob/master/doc/Porting.md 18:48:41 I've never ported anything to freebsd so maybe you understand better if that could happen? polarian 19:07:58 19:22 [ Demosthenex] i still scream on redhat boxes where they don't have df -g ...wait until you realize redhat has default aliases for rm/mv/cp to include "-i" 19:08:28 and while we're at it, try to use --group-directories-first with ls... ;-) 19:09:27 fold: actually there appears to be Linuxisms within the C code 19:10:25 it also seems to be GNU makefile which sucks too 19:10:29 BSD make is different 19:10:40 https://github.com/koreader/koreader/blob/master/Makefile#L17-L25 also checks for Linux 19:11:12 and apropos linuxism, bsd ls doesn't have --group-directories-first but --color ;-) 19:12:37 I didnt see the C code because they have split off the code into different repositories 19:12:58 I am not a porter so I cant advice on it sorry... 19:13:00 hmm, "pkg install caddy" -> "No packages available to install matching 'caddy'" 19:13:00 it's still in ports, and I installed just yesterday. where did it go? will it come back? was there any decision to remove it? how can I find out what's going on? 19:13:12 fold: I do suggest trying xournal++ though 19:13:27 handwritten and text note support 19:13:39 its within the freebsd port tree if you want to try it 19:13:49 its what I used before I finished school 19:14:33 oh wait 19:14:57 I have misunderstood what koreader is lol 19:15:10 xournal++ is quite different in that regard... 19:19:00 yeah koreader is just a book reader 19:19:49 the good thing is that I use that on android,kindle,linux 19:19:59 I wanted to use it on freebsd 19:20:16 but seems like a lot of things depends strictly on linux 19:20:46 it happens, some thing are just too linuxy 19:24:10 maybe using the linux compat? 19:36:59 that's worth a shot 19:39:44 anyone? any way to know why the "caddy" port has no prebuild package any more as of right now? 19:44:56 just set up FreeBSD 14.2 with DWM on a Thinkpad T490s, working nicely. 19:49:23 Grabunhold_: py-setuptools only build depends on py-wheel044, so first building that and later py-psycopg2 should work (or building in clean environments) 19:50:25 armin: nice! I'm waiting for the arrival of a carbon x13 gen 1 19:50:27 or something like that 19:50:37 I want to try niri in that one 19:50:40 and sometimes stuff fails to build (like recently go) and all that depends on it gets skipped and aren't part of the pkg repo as a result of that 19:51:25 nimaje: "pkg install py-setuptools" beforehand did the trick. all of this stuff is part of my ansible playbook, and after fixing the pgsql installation now caddy breaks =/ 19:52:33 yep, go failed to build on the official builders, so everything written in go (like caddy) got skipped 19:53:22 nimaje: do you have a link to the build logs? i'd like to have a place i can go check when i run into surprises like these 19:54:42 https://portsfallout.com/ and https://pkg-status.freebsd.org/ 19:56:16 fold: Well, quite frankly put, I lost faith in Thinkpad's :-( It's sad to have to admit that, but I bought a T490s 6 weeks ago and I'd say it wasn't worth the money even though I paid only 300 bucks for it. These things are plastic bombers in the todays world and it's faaaaaar from the build-quality I was used to in Thinkpad's to say the least... 19:57:07 fold: It runs FreeBSD just fine so I'm more than happy, but still, the decay in build-quality over the last 10 years is not to be neglected... 19:58:20 fold: so yea I would say get one if you can get a used one for cheap, but other than that, ewwwwwwww, difficult to even justify the purchase compared to the Macbook's I got over the last 10 years, yeah. 19:59:26 fold: Still, it works nicely with DWM, it runs pretty solid even, yes slower than Linux but as long as it 19:59:37 ...'s all scripts I know how to get that stuff going... 20:00:01 (sorry, ISO-DE typer here, the #/' key is next to enter here) 20:00:29 <|cos|> nwe: I think it might be called "MacBookPro11,1 (A1502, EMC 2678)" 20:01:28 I got a 13 (!!!) years old Macbook Air here that runs Linux just fine, I'd be surprised if the trackpoint support would even be halfway usable under FreeBSD (hello 3-finger-drag...), but I might try it 20:02:59 nimaje: thanks! 20:03:37 armin: i bought a used x13s a few weeks ago and i'm quite happy with the hardware so far (now the firmware is another story...) 20:04:45 Grabunhold_: well congratulations, I love my T490s, too, but compared to literally all the Macbook's, even the 13 years old (which I just cleaned entirely, looks quite nice) I'd say the build-quality just can't hold up... 20:05:49 armin: well, be that as it may, the non-standard keyboard layout and the firmware on the macbooks is a dealbreaker for me 20:05:51 Grabunhold_: that being said, I'm pretty much an Apple fan, I must admit that... yes, both hardware and software... 20:06:20 Grabunhold_: not much of an issue, you get the thing you're used to back with Linux (by default) and you can even switch to that on macOS 20:06:38 Grabunhold_: but I get your point, took me a couple of months, too 20:08:16 Grabunhold_: Muscle-memory dies HARD, I got to that problem the hard way, being used to ^A as a prefix from screen, coming to tmux (hello, ^B) 20:09:27 Grabunhold_: there's this thing deeply rooted in your veins that you need to be cautious about, I totally agree, if you have something in muscle-memory, definitely configure your environment exactly so you have it again. 20:09:44 armin: i decided at some point that i just don't want to deal with the muscle-memory problem, and fighting the firmware to let you install your own OS seems to be an uphill battle. so, thinkpads it is. 20:10:11 Grabunhold_: sure, there's thousands of valid approaches here, if that works for you, all fine. 20:10:41 Grabunhold_: but meh, I type ISO-DE since 1985 now, there's NO way I'll go ANSI 21:01:02 armin: fwiw, it's pretty easy to remap tmux to use ^a (i didn't want to fight muscle memory, so it's "set -g prefix C-a" for me) 21:03:29 afaik they used ^B for tmux, because they developed it in screen and wanted to test it easily, so the default prefix couldn't conflict 23:29:45 cyric: yup got that one, too, thank you. :)