00:51:47 byakuren, just realized i was starting "cat truss.log | grep $(basename $PWD) | cut -d '"' -f 2 | sort | uniq" with cat but you started it by grepping open. i guess you did that because that limits to files whose contents are read (rather than just a stat or smth) right off the bat, right? 00:53:21 kerneldove: yeah exactly, i included the open query in that initial grep - plus cat-ing to grep just uses another process and pipeline in your os, so you might as well do it directly 00:54:07 are there any other syscalls that a proc can use to read the contents of a file than *open* ? 00:56:32 mmap and friends, maybe? 00:56:57 well you've got open* (open, openat...etc), and i guess mmap in case for some reason the process memory maps the file then reads the memory - all other ones i beleive read meta data of the file, like *stat (fstat, lstat), acccess and so on 00:57:39 hmm. so i guess to be safe i should cat (include all dirs) OR grep open + mmap? 00:59:47 grep -E ': open|: mmap' truss.log | ...etc 01:00:54 though a lot of the mmap output seems less than useful, as it's not file names per say - so i think you'll be fine not including it 01:01:21 (looking at the cargo build truss log specifically that is) 01:04:57 interesting. grep -E ': open|: mmap' truss.log | grep $(basename $PWD) | cut -d '"' -f 2 | sort | uniq eliminated the group of relative urls? 01:05:30 oh so did grep open ... 01:10:36 those relative paths were a __readlpathat call 01:10:40 rather than open 01:11:50 ahhh! 01:12:37 s/__readlpathat/__realpathat 01:34:31 i'm trying to track down an issue with the command and it seems grep \.rs matches some lines that don't have ".rs", am i doing it wrong? 01:36:20 try grep '\.rs' quoting it 01:36:56 the . is likely being escaped by your shell, and sent to grep as a normal dot, which is then treated as a singular wildcard 01:37:08 quotting it in a string like that should ensure grep gets the ecaped dot 01:37:49 sigh that worked lol ty 01:40:41 :p np 01:45:24 ya i think there's something wrong with the grep -E ': open|: mmap' truss.log part, it doesn't display as many .rs files as when i start it with cat truss.log ... 01:45:45 i double checked truss.log, and plenty of them *are* openat lines, not just fstat or something irrelevant 01:48:01 You can always test what the shell is doing with quoting by using echo to echo print out the result. Try "echo \." and we see only a single dot. "echo '\.'" shows that then it is "\.". 01:48:50 oh that's really cool ty 01:48:53 And for deep inspection I always use od as in "echo \. | od -tx1 -c" and then one can play with the quoting and see exactly what is being done there. 01:49:18 You can also use "wc -l" to check your impression that there's more occurences of one than the other. 01:56:01 my truss.log has an openat with a path including interface.rs, as i can see with grep -E ': open|: mmap' truss.log | grep interface, but when i run grep -E ': open|: mmap' truss.log | grep $(basename $PWD) | cut -d '"' -f 2 | sort | uniq | grep interface, there's no results ?? 01:57:40 Probably lost it in the cut step at a quick guess in the dark. Start with the first command, pipe it to |less to see what it produces. Then add in the next stage in the pipeline. And then the next. Along the way to the final form you will see the problem. 01:58:07 may be the grep $(basename $PWD) is filtering that line out - as that contains the name of your directory, and if its a relative file that may not exist? 01:58:32 it's a relative path ya 01:58:32 Also you can avoid a process with "sort | uniq" by using "sort -u". 01:59:17 that's a shout! always forgot about sort -u - thanks for the reminder for me as well c: 02:00:20 ok ya i took out the basename part and it's there now, but so is a lot of other noisy build dirs hmm 02:00:51 maybe i can run the truss cargo build from my home dir so there's no relative dir that i can't filter on 02:05:42 nope even if i build from ~, the dirs are still relative damn (must be relative to repo's Cargo.toml) 02:09:44 man this is weird, i added --release to the truss cargo build command and it kept failing midway through that it couldn't find thread lol 02:40:21 there's a lot of noise to wade through going this truss method. what if i enabled atime in zfs so i could use the other method? find . -type f -atime -5m 02:41:10 yeah that could also work 02:43:27 how much more will it work my nvme mirror? 02:43:44 It would also be possible to create a zfs dataset with atime enabled and use it for whatever you are doing. 02:47:33 zfs create -o mountpoint=/var/mydata -o atime=on zroot/var/mydata 02:56:58 could i create the dataset within a dir in my ~ or would that be weird? 03:00:12 that's fine - you can just remove it when ur done with it no worries 03:05:34 i made an 'atimebuild' dir under /var/ just to be safe. now i'm waiting for some time to pass then i'll test! 03:18:21 You can make datasets anywhere you feel they are useful. It's also reasonable to give yourself permissions to create, modify, delete datasets in your home directory and many people do that too. Then you can do those actions as yourself without needing root. 03:19:02 can you make datasets within other datasets? because my home/dir is already a dataset of its own 03:19:47 Yes. That's typical. If you "zfs list" you will see that by default there are already nested datasets. 03:20:24 zfs datasets are light weight. People create them for any reason. The only thing to know is that they are different file systems and therefore _moving_ files to and from datasets is a data copy since it must copy data from one file system to another file system. 03:30:48 i wonder if the mv vs copy thing is why when i moved the repo dir i was working on from within my home into /var/atimebuild/ there were build errors. i rm'd the dir, cloned the repo fresh, then i could build 03:31:15 and btw the find command dumped into a file.txt and now i can see exactly the files touched during build within the repo!!! 03:31:23 tyvm byakuren and rwp 03:31:56 Hooray \o/ 03:33:12 Glad its working, and you got your data c: 03:38:51 ty 03:40:12 to find the changes between versions i guess i do this process for both versions of the repo, then run diff using the list of changed files? 05:05:30 kerneldove, To find what files have changed ask the zfs file system with "zfs diff". Take a snapshot before the build. Then build. Then zfs diff against the snapshot and it will tell you exactly what files changed. It's fast because the file system knows what files changed. 05:52:56 but i'd still need atime enabled for that right? 06:06:56 rwp 06:15:14 kerneldove, zfs knows what files changed regardless of atime. atime will tell you which files were accessed even if they were not changed. But you said "list of changed files" and I thought of zfs-diff. 06:15:52 oh... i'm trying to identify which files in a repo are used in the building of a bin in the repo 06:16:02 that doesn't actually change any of them... except for using atime 06:16:24 tried using truss earlier and it probably worked fine but the log was really noisy (lots of files outside of the repo were included) 06:17:33 So... After you know what files are used during a build... What are you going to do with that information? 06:19:40 limit the diff between 2 versions of the repo, so i can know what's changed from the /relevant/ files, aka the files pertinent to building the bin 06:19:51 because the repo has files (code) for other bins that are irrelevant 06:36:23 rwp 08:41:52 In OpenBSD I can put `pkg_add -ui && syspatch` in a crontab, and it'll automatically update packages/ports and system files. But in FreeBSD I feel like that's not possible since you need to confirm with a "y", but could it be possible to do something like `pkg update && pkg upgrade && freebsd-update fetch` in a crontab, and have the server output the results in my mailbox? 08:53:41 Hi guys, I'm having a lot of trouble with my re0 ethernet device on FreeBSD 14.3. No matter what I do, I cannot establish a connection. I've double checked that it workes on other OS's, so this has to be a FreeBSD issue. Has anyone else seen re0 driver issues..? 08:56:26 is there any way to add more swap space to a system with zfs? 09:12:03 remiliascarlet: read the man pages, freebsd-update has the cron subcommand that is meant for that. Also, setup periodic to check for package updates available, and mail those to you. Preferable in my opinion to running unattended upgrade, but itlf that is what you really want, you can do that to. 09:14:04 I have a lot of BSD servers to manage, so preferrably instead of manually logging into each one of them multiple times a week just to update, I would rather do this automatically, and then read the output with the `mail` command for supervision. 09:15:16 pkg upgrade -y, is what you're after then 09:16:03 freebsd-update cron, will download the update if available and send you mail 09:16:16 I see. 09:18:36 I'd still use the notify approach if I were you, and write an ansible playbook to run the upgrades in parallel 09:19:30 kerneldove: you can, but you need unpartitioned free space on a drive to add or grow an existing swap partition 09:20:22 you can ask dvl, how to swap on zroot 09:23:33 If it was ufs, you could get away with a swap file, but that is discouraged on zfs. Don't know the exact reason 09:23:59 All my FreeBSD servers are ZFS. 09:24:32 It's overkill on anything other than the NAS, but I just like ZFS. 09:26:00 I think the advantages are worth the penalty, I use it even on a tiny vps. overkill or not, it's just so convenient 11:38:07 kerneldove: found it. Swapping to a file on zfs is simply unsupported. What is possible is swap on a zfs volume, but it could lead to deadlocks: https://github.com/openzfs/zfs/issues/7734 11:39:08 Dates back to 2018 ^ 12:19:42 dansimon: I've had issues in the past with Realtek NICs. If the "re" driver doesn't cut it for you, you might have better luck with net/realtek-re-kmod from the FreeBSD-kmods repo 12:30:03 swap best to ufs partition. 2nd best ufs swapfile (both ssd). 3ds best partition spinning rust. 4th best spilling rust ufs swapfile. zfs swap there be dragons 12:30:34 i have such a headache with if_re 12:34:07 divlamir: thanks, I'll give it a try :) 14:07:54 electron37 took 13h06m43s on 3.5ghz i7 parallel_jobs=1 allow_make_jobs=yes 14:11:41 <[tj]> probably faster with more than 1 job 14:12:43 f451: do you have ccache set up? that really helps with electron/node/llvm updates 14:13:08 not the first time obviously, but for updates 14:13:41 other problems happen though, like it'll hit swap or run out of resources elsewhere. this way allows me to keep using the machine this poudriere instance runs on. i'm not complaining about the time it took, not really. electron is rather large 14:13:57 ivy: yeah - ccache4 is the ccache 14:15:12 parallel_jobs=1 and allow_make_jobs means there are 4x llvm20 jobs running, load is btwn 4.00 & 5.00 14:15:45 but it completed and im happy about that :D 14:16:10 Can you potentially set a better nice value on it? I've done that to a bunch of cargo builds that would normally use 100% cpu and make my music skip, with a very high nice value it works much better and I don't get skips 14:17:05 byakuren: have to admit ive not looked or thought about re-nicing. 14:17:25 give it a shot! 14:17:30 :D 14:17:42 renice is for already-ruining commands 14:17:59 So just a nice -n 20 $COMMAND 14:18:32 i'm surprised there isn't a poudriere.conf option for that 14:18:33 (since you say it's very low priority - 20 is the lowest, maybe a 10 is a good middle ground though?) 14:18:41 i mean you can just run poudriere bulk under nice, but... 14:18:44 <[tj]> 10 is the default priority 14:19:00 <[tj]> no, maybe the man page is hard to read 14:19:22 yeah - nice $CMD gives it a nice value of 10 14:19:51 it's a bit confusing that nice is separate from priority, but nice(1) calls the nice value the priority 14:19:52 <[tj]> "The lower the nice value of a process, the higher its scheduling priority." 14:20:03 it took as long as it did because i have it in my tmpfs blacklist (for wrkdir). 14:20:17 i think thats the most likely reason 14:21:00 nice 30 poudriere bulk blah .. yeah might try that 14:21:15 thanks for the suggestion 14:21:25 if you're running zfs - it'll also be using your ARC (zfs ram cache - up to 80% of free ram by default) quite a bit, which might be exausting (or making you think you're exhausting) your ram 14:22:17 20 is the most nice a procss can be c: - but it clamps the value within the acceptable range for ya 14:22:56 i have 2x poud instances here - the older one uses zfs. im using ufs on the other one exactly to eliminate arc pressire 14:23:14 20! 14:23:19 ok ill remember that 14:24:51 im really pleased rn its not hitting swap (thats on the ufs disk - the swap partition) 14:28:02 neat! 14:29:33 * ivy tries to work out how poudriere overlays work 14:30:20 it seems like you have to create a port tree in poudriere to use as the overlay, which is less useful than i was hoping, i just want to testport from a temporary git worktree... 14:31:01 use -O to reference it iirc 14:31:14 right, but i was hoping -O would just take a path 14:31:29 if i have to create a ports tree in poudriere first i may as well just use that as -p, i guess overlays are intended for something else 14:32:03 poudriere bulk -j desktop -O sccache -f ports.txt 14:32:22 ah 14:33:09 no not that i kbow of - you need poudriere ports -c -M path -m null 14:35:08 that seems to work, thanks. i suppose i should write a script to do that 14:35:36 poudriere ports -c -p sccache -m null -M /usr/local/share/sccache/overlay 14:38:34 ivy: is yr poudriere the regular one or the -devel 14:39:00 f451: i always use -devel 14:39:14 yep 14:39:35 i dont think the regualr one supports overlays 14:39:47 yet. might be wrong there 14:41:17 I use /usr/ports/ports-mgmt/poudriere-dsh2dsh because in there the rebuild-rust-needlessly problem is fixed 14:47:28 ty divlamir 14:55:15 huh, i didnt know this: 1.2.p1 is *before* 1.2 14:55:35 f451: err, usually not. what software is versioned like that? 14:55:57 1.2-p1 is *after* 1.2 14:56:14 im looking at the porters handbook, example #5 14:56:42 section 5.2.2 14:57:11 pkg-version -t 14:57:39 that doesn't seem right at all, i wonder if there's a historical reason for that 14:57:53 i've never heard of .p1 meaning "prerelease" 14:58:10 yeah 14:58:33 .pre1, sure, that's quite common 14:58:40 then again - freebsd releng versions go 14.3-p3 not 14.3.p3 14:58:56 maybe it's the dot 14:59:50 in pkgbase the version is 14.3p3 15:00:02 which works because of rule (6) 15:00:08 yep 15:01:17 i do wonder why we don't just call it 14.3.3... 15:01:49 we used to have 3-part version numbers and they dropped around 3.x for reasons i'm not really clear on 15:02:35 i guess it might be confusing if you had 14.3.3 installed but uname -r said 14.3 15:02:51 (but people are already confused about why uname -r doesn't say 14.3p3, so...) 15:03:19 yeah i had the cds from 2.1.3 - remember Walnut Creek i wonder if they're still going 15:04:09 What does the p in -p# stand for? Part? 15:04:11 * ivy stays away from releng things in general, dragons live there 15:04:15 Macer: patch 15:04:19 Ah ok. 15:04:41 Macer: because historically the updates were literally released as source code patches, although nowadays you can also get them as binary updates from freebsd-update or pkgbase 15:05:26 ivy: same. basically if you're managing systems exposed to the internet it's a balancing act btwn the latest patched software and breaking things 15:07:54 f451: i meant more the releng process, rather than using releng releases :-) 15:08:12 ahah 15:08:14 although currently all my systems run main... i think i might switch to releng/15.0 and just backport patches i want 15:09:00 no stable/15 ? 15:10:26 if i was going to run stable i'd just run main, the idea is to make regular maintainance less exciting every time 15:11:44 heh 15:14:01 have to say, pkgbase is scary. i can think of a couple of situations it would be useful to get a new install running or tailor an embedded install, avoiding buildworld etc. On the other hand, single point of failure (pkg) 15:18:10 then again, some embedded - it'd be worthwhile to build on the embedded system for other near-identical ones to get the best out of the os and just dd the image to other instances 15:23:17 thats what i did for a few armv6 and v7 systems a few years ago 15:29:46 https://github.com/freebsd/pkg/blob/main/libpkg/pkg_version.c#L151 - this is the file and code for the -p1 type suffixes btw 15:30:55 so you can get an idea from the commit history about the reasons behind it all c: 15:31:52 f451: i really think we should import pkg to base, but there is some resistance to this right now due to the rate of development 15:32:10 yeah 15:32:19 i'm not sure it makes sense that the officially recommended way of building freebsd requires a tool we don't provide 15:32:29 LOL 15:32:56 also, that would let us do pkgbase cross-builds from Linux and macOS which currently doesn't work 15:33:14 (surprisingly, a lot of people rely on this for both development and production use) 15:34:11 i wish there was a gitlite in base as there used to be a svnlite years ago 15:34:27 we will probably import got into base eventually 15:36:22 I find it bizzare that FreeBSD allows this, but whatevs?: https://bpa.st/PJVQ 15:36:42 ive used got before, it's not a drop-in replacement though. i think by default it makes a shallow clone 15:36:44 why would it not? utf8 is utf8 15:37:04 CrtxReavr: the hostname is just a sequence of bytes. is there an advantage to adding code to disallow that? 15:37:47 f451: it is a drop-in replacement in the sense that its on-disk format is compatible with git, so you can clone with got and switch to git if you need something fancy. the UI might be a bit different, i'm not sure, never actually used it 15:37:56 Well. . . I can say that BIND doesn't allow it as a hostname. . . 15:38:05 Like I said, "whatevs." 15:38:13 f451: but got would be perfect for cloning src, ports, etc. after installing the base system, which you can't do right now, and we can't put git in base 15:38:27 yep 15:38:40 CrtxReavr: the system hostname is not required to be a DNS hostname, the system might not even be connected to an IP network at all 15:40:05 CrtxReavr: also you can use that as a hostname in BIND, but you'll have to convert it to punycode format first 15:40:23 Also: https://bpa.st/G6YA 15:40:36 xn--whatever would be a silly hostname 15:41:05 rtprio: right. but it should work to set a Unicode hostname with a punycode DNS record... i have no idea if our resolver even supports IDN though, but like in principle, it should work 15:41:43 (i don't think anyone should actually do this, but...) 15:41:49 It's supposedly in the works to allow unicode TLDs and domains. 15:41:58 CrtxReavr: in the works? it's been live for years 15:42:16 CrtxReavr: that's what i mean about converting the hostname to punycode, that's the way DNS encodes these non-ASCII hostnames 15:42:57 https://räksmörgås.josefsson.org/ 15:44:39 How show us a domain name example. 15:44:40 Now 15:45:51 http://www.人民网.中国/ 15:45:56 Hi 15:46:04 o.O 15:46:21 This what yoiu mean by "punycode?": https://bpa.st/2TLQ 15:46:33 no, punycode names begin with 'xn--' 15:46:43 I'm ok with browser parsering those (and showing punycode), but I'm surprised that my terminal is parsering them correctly as URLs 15:46:45 https://en.wikipedia.org/wiki/Punycode 15:47:29 lts: did that actually paste correctly? it's missing some characters here, i don't think my font has the full CJK set 15:47:36 but it does work in Firefox 15:48:27 Yeah, alacritty detects http://www.人民网.中国/ perfectly 15:48:49 (I don't think "parsering" is a word.) 15:49:14 "Parsing" sounds & looks correct. 15:49:20 xfce terminal doesn't. It stops at "https://www" 15:49:37 V_PauAmma_V, that could be an issue with the fonts you have installed. 15:49:50 And your terminal configured to use. 15:50:25 it should look like this: https://people.freebsd.org/~ivy/tmp/idn.png 15:50:25 "Parsing" indeed would be correct. Sorry, English as definitely-not-first language here 15:50:27 No, it displays properly, just isn't recognized as a URL. 15:50:46 ivy, am I miss-remembering, you don't you normally have a capital letter in your nick somewhere? 15:51:08 CrtxReavr: i never capitalise my IRC nick, if that's what you mean 15:51:45 huh 15:51:47 * CrtxReavr ivy 15:53:31 Indeed, a quick grep of my logs confirms that. . . I miss-remembered. 15:56:10 i actually never capitalise anything, except commit messages because people complain if you don't do that :-) 15:56:23 also sometimes work emails if it's to a client 15:57:13 ivy saves their pinkies for nose picking. 16:10:26 mintty doesn't seem to have an issue with that URL with it URL detection. 16:11:39 WezTerm doesn't like it, but i think that's because of the missing characters, i wonder why it doesn't take them from an alternate font... perhaps i don't have a proper monospace CJK font installed 16:12:16 What kinda TLD is that anyway? 16:12:40 it's the IDN version of .cn 16:13:29 https://en.wikipedia.org/wiki/.cn (para 2) 16:14:33 also https://icannwiki.org/.%E4%B8%AD%E5%9B%BD which is where i found that URL 16:15:20 actually there are two IDN versions of .cn apparently, one for traditional and one for simplified... i find that surprising since i thought PRC hated traditional script 16:28:07 I took a Chinese history class in college. . . prof was a middle-aged, white, American male. . . 16:28:55 He lectured that he thought China saw its best and longest period of peace and prosperity under the CCP. 16:29:35 I always wondered if he actually believd that, or if he was just trying to keep in the CCP's good graces so he could continue to travel there for research. 16:32:33 This is a very #freebsd-social discussion. 16:33:29 LxGHTNxNG: is it though? the channel is quiet, the discussion started here, there's no immediate need to move it because of the topic police 16:34:04 What ivy said. 16:35:34 Maybe LxGHTNxNG is lonely in #freebsd-social? 16:36:15 I am a god, and I rely on belief for my continued existence /s 16:37:02 hhe... It's been a long time since anyone invited to #social 16:37:46 there, i did one to CrtxReavr for old time's sake 16:37:50 i don't expect they'll join 16:38:11 #freebsd-social is pretty dead recently, i'm sure it used to be (a little) more popular 16:38:21 maybe everyone's on holiday 16:38:33 I've been on IRC since '91. From my perspective, the first rule of IRC, is that it's supposed to be fun. 16:39:50 Not a fan of topic-zealots, 'specially when the chat isn't interferring with people getting help or causing excessive scroll in the channel. 16:43:26 +1 to above, if there is no other active topic then redirecting discussion to a small channel is a net negative effect 16:44:11 Any good movies or tv shows to watch? 16:49:09 :)) 16:56:47 lol 16:57:41 https://m.youtube.com/watch?v=tuI2wX3ol2o&pp=ygUQRnJlZWJzZCBlcGlzb2Rlcw%3D%3D 16:57:47 That’s a good one to watch. 16:58:53 zi, no lurking. 8-P 16:59:17 i didnt want to upset someone by saying something fun! 17:00:16 Make sure you don't have fun, either. 17:00:33 i try not to 17:00:53 If someone has fun, we can always redirect them to #freebsd-social 17:01:35 'fun' sounds like it should be a freebsd.org username, but it is not 17:02:25 lts: is that like telling someone to sit in a corner? :) 17:02:31 TommyC: https://www.youtube.com/watch?v=hMeO4qAG8WY 17:02:44 ivy, how are you enumerating the usernames? 17:02:57 grep fun /etc/passwd 17:03:01 zi: #freebsd-social is definitely a corner 17:03:03 CrtxReavr: i logged into freefall and ran 'finger fun' and it said: finger: fun: no such user 17:03:21 finger fun! 17:03:27 ivy, you have a .plan file? 17:03:38 CrtxReavr: as if i'd be that organised, have you met me? 17:03:50 freefall doesn't allow remote finger anyway, which i think is a shame 17:04:04 echo Wheeeeee! > ~/.plan 17:05:34 ivy has No Plan 17:05:52 zi: accurate 17:06:01 fun fact, you'lk get the same error if you finger me 17:06:32 is it .alias or .aliases ? 17:06:41 yamada: for mail forward? you want .forward 17:06:48 nah for alias commands 17:07:13 ivy, I think more systems would allow it if there was an option for not displaying a user's last login-from IP. 17:07:13 i miss it in the /etc/profile 17:07:14 which shell are you talking about? i don't think /bin/sh supports any specific file for that, just put them in .profile 17:07:23 ok 17:07:57 or you could create .aliases then source it from .profile with the . command 17:08:14 or modify /etc/profile to source $HOME/.aliases, or whatever, but i don't think there's any out-of-the-box support for that 17:08:32 ha. . . I forgot that I had a .plan on here. 17:08:51 A gleekzorp without a tornpee is like 17:08:52 a quop without a fertsneet (sort of). 17:09:46 oh man, just think of how much fun Mr HAPPY has 17:11:12 * ivy wonders if we support $HOME/.environment 17:11:19 i guess not since $HOME/.login.conf already does that 17:14:36 It says "Secure site not available", not sure if it parsered it corectly LOL 17:15:16 sry, must have been in the backlog :-/ 17:16:07 is it possible to get hardware support in freebsd for 1 million usd cash ^^ 17:16:34 Depends on hardware, but probably yes 17:16:37 yamada: sure. get in touch with a contracter like Klara and they'll happily write drivers in exchange for $$$ 17:16:46 Prolly cheaper to give a device drive dev a device and a programmers manual for it. 17:17:01 device driveR dev 17:17:34 hm 17:17:40 i cannot donate my hardware ^^ 17:17:45 i need it myself 17:17:58 At a former employer, I had access to a lot of programmers manuals for a lot of devices, which I quite under-handedly gave to any FreeBSD driver dev that I could. 17:17:59 i bet in 2 3 years it will be supported anyway 17:18:02 what is the hardware? if it'd widely available, they can just buy their own copy of it (of course that would be included in the price) 17:18:29 Most hardware vendors are not so forthcoming with their programming manuals. 17:18:31 check the gigabyte.com site and pick somethign between 100-200 bucks 17:18:35 Sadly. 17:18:57 yamada: $200 is like an hour of developer time, so buying that would not be an issue :-) 17:19:00 i think freebsd 15 will support the mainboard chipset 17:19:14 :( 17:19:15 i wanted zfs 17:19:44 now i have to stick on kali linux or tumbleweed or cachyos 17:19:47 i'm not sure if you're serious about paying someone to add support, but if not, please report your non-working hardware somewhere (mailing lists, bugzilla) so people are at least aware 17:20:04 i didnt know that exists a list for non working hardware 17:22:28 Not exactly a list of non-working hardware, but there is a list of working hardware. 17:23:15 https://www.freebsd.org/releases/14.1R/hardware/ 17:23:54 There's also drivers that are not in the default kernels, that either need to be loaded as a module, or you have to build a custom kernel for. 17:24:18 oh ok 17:25:26 What device and arch are you having issue iwth? 17:27:07 arch amd64 hardware a https://www.gigabyte.com/Motherboard/Z890-EAGLE-WIFI7 17:28:38 yamada: what hardware specifically is not supported? 17:28:42 wifi? network card? 17:33:06 Realtek LAN + Realtek Wifi 7 o-0 17:34:57 They don't even give the name of the chip in the specs those buggers 17:35:22 yamada, pastebin the results of: pciconf -lv 17:51:24 CrtxReavr, i can do that next weekend 17:54:32 Well, that's anti-climactic. 18:15:43 15.0-RELEASE spoiler https://people.freebsd.org/~ivy/tmp/bsdinstall-pkgbase.png 18:17:14 ivy: that is pretty sexy 19:11:36 ivy, meaning the OS can be installed/upgraded with pkg(8)? 19:13:38 CrtxReavr: that's been possible since at least 13.x 19:13:50 the new change here is you can select more components during install 19:19:27 well, i guess bsdinstall support for pkgbase is new in 15.0, but you could still install manually using pkg(8), for jails etc 20:36:24 https://linux-hardware.org/?probe=f7233e7156 20:36:54 tl;dr says: RTL8125 2.5GbE 20:38:56 yamada: https://www.freshports.org/net/realtek-re-kmod/ 20:44:57 yamada: wireless is more complicated, see: https://forums.freebsd.org/threads/mediatek-mt7921-wireless-driver.97165/ 22:50:58 aic: regarding if_re, YMMV see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289168