01:43:39 Ug bhyve pass through is killing me: 01:43:57 ppt0@pci0:9:0:0: class=0x0c0330 rev=0x00 hdr=0x00 vendor=0x1b21 device=0x1042 subvendor=0x1043 subdevice=0x84aa 01:44:15 bhyve: PCI device at 9/0/0 is not using the ppt(4) driver 01:45:32 bhyve -AHPD -c $CPU -m $RAM -S -s 3,passthru,9/0/0 \ 01:45:57 did I miss something stupidly obvious? 01:46:07 devctl set driver -f pci0:9:0:0 ppt 02:04:33 put pciconf above already lists it as using ppt0, and it's listed in /boot/loader.conf: pptdevs="9/0/0" 02:07:19 Some devices just don't work as pass through 02:07:22 but running that command line results in the same error messages 02:07:42 does anyone know if the ASMedia chips support that? 02:08:13 I'm looking for a USB controller that supports passthrough and would work in linux running in bhyve 02:25:39 Looks like the problem is that the BIOS turns SR_IOV back off after I swapped out the previous USB board for this board. 02:33:33 Hey, it's all working, thank you so much 02:34:28 Good to hear. 02:43:32 * V_PauAmma_V pours one for portsnap. 02:49:24 mew? 02:49:28 is portsnap dead? 02:53:28 Now that 13.5 reached EOL and since it's not in 14.4, yes. 02:56:38 can someone please send me a test /msg? 02:58:51 Perfect. Thank V_PauAmma_V 08:09:07 hello there, is there a way to run "monthly_status_security_output" manually and get output to stdout by chance ? 08:11:12 try: sudo /etc/periodic/monthly/450.status-security 08:11:56 luser thanks will try now 08:14:21 luser thanks, it is doing something 08:15:45 nope, output is: (output mailed separately) 08:16:59 i guess there is something to do with security_output=/path/to/a/file 08:28:54 a working mailserver is mandatory. I don't know if FreeBSD ships with one? 08:30:10 I recommend installing postfix. But many people are using dma. 08:30:34 freebsd includes both sendmail and dma in both 08:30:40 base 08:30:40 someone sent me this like a year ago. I haven’t even looked in to it yet, but its on my to do list 08:30:40 https://www.iredmail.org 08:30:56 last i used it, it did, sendmail was default, I think y'all switched to dma? locally i first switched to postfix (which had some very funny isde effects involving a misconfigured mailer.conf) then a local fork of qmail 08:31:58 but the question was about how to get the output on stdout, which wouldn't require an MTA. i would suggest looking at what 450.status-security actually does, and see if you can invoke the relevant bit by hand 08:36:21 i suggest postix too 08:37:11 so I guess I will deep dive into the script and will make a my own version ... 08:37:34 if there is that about security_output to a file, you could try setting that in periodic.conf and checking that file after running the script 08:37:49 that was the fastest I'd ever typed in a while, why do i type fast when i panic 08:37:58 you know speaking of mailservers, i was looking for a postifx forum or something and actually came up anything. Anyone know a good place to ask postifx config questions? Not specifically related to bsd at all 08:38:02 also file: /etc/defaults/periodic.conf:164:daily_status_security_output="root" # user or /file 08:38:23 i guess this assumes that I can feed a file into that variable? 08:38:36 GoSox: #postfix, ##email, https://www.postfix.org/lists.html 08:38:37 same is true for weekly and monthly 08:39:08 right now I'm in the middle of upgrade 08:39:17 will test it a bit later 08:46:14 worked: 08:46:14 echo daily_status_security_inline="yes" > /etc/periodic.conf.local 08:46:14 daily_status_security_output="/file" >> /etc/periodic.conf.local 08:49:37 i guess all pastebin are died, credits to ai ... 08:50:05 https://hastebin.ianhon.com/43f1 12:55:31 anyone want to think with me how to connect old ssh hosts from 14? 12:56:36 apparently poof, ssh1 is gone, poof, dsa doesn't magically poof host is upgraded 12:58:36 for one host i have to use old static dropbear binary 13:02:06 whatever is not supported now it sucks 13:12:41 oh the bear helped me agaij 14:36:12 so i fixed it with dropbear-2024.86-static/dbclient 17:58:15 hi, i reported this earlier today: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=294980 17:59:06 is there anybody in here that has encountered a similar issue? maybe years ago when the 14.0 first came out 18:01:00 bugs.freebsd.org is presumably overloaded right now and not responding to me. Can you give a clue as to the topic at least of that bug report? 18:02:28 yeah of course. i'm trying to upgrade from 13.5-RELEASE-p14 to 14.0-RELEASE, and when doing the first reboot, during init (right after the ntp service goes up) mrsas(4) detaches all the drives 18:03:06 it doesn't happen if i go into single-user mode 18:04:07 I don't know, but I will ask a maybe, did the bootcode get upgraded between 13 and 14? Since it works for you in single user mode I doubt that can be it though. 18:04:23 Did you say 14.0? That's unsupporte and has been for a while. Did you try 14.3 or 14.4 instead? 18:04:44 * rwp hates the AI scraper bots, bugs.freebsd.orgggggggg is giving me 504 Gateway Time-out a symptom of being overloaded by the scrapers... 18:04:46 i tried with the older and newer loader.efi, but the problem persists 18:04:58 yeah, fucking bots 18:05:41 V_PauAmma_V, i tried with both of those, yes. still the same (with some extra warnings about deprecated sysctls) 18:05:46 Good spot V_PauAmma_V. (And apparently I have a sticky g key on my keyboard. LOL.) 18:06:45 i first tried to go all-in with 14.4, and when i encountered the issue i decided to go back and update step by step. not sure if that's a good idea 18:07:54 I don't have mrsas(4) disks, so I can't attest to that. 18:08:27 I would try again with the current 14.4-RELEASE but I still don't understand why the mrsas driver would detach all of the drives. I also don't have anything with mrsas here so know nothing. 18:09:35 it's really weird. i also don't see any changes to it nor cam(4) in the release notes 18:09:41 I don't have enough caffeine in me yet today but I recall a command to list out the rc runtime scripts. One might boot single user mode as you have done and then manually run each of those one after the other until you hit the problem. Then you will have narrowed it down. 18:09:54 rcorder(8), no? 18:10:22 sounds like a plan 18:11:30 Yes, rcorder, man page says "rcorder /etc/rc.d/* /usr/local/etc/rc.d/*" to print the list out. It is 196 files here. But maybe some bisecting would speed up the testing. 18:13:04 Again I am just going to mention things like a good stuffed monkey so that they are refreshed. Boot Environments will allow you to boot the previously working BE. From there you can mount the future one and reach into it to fix things or review things. Or destroy it and reset and restart. 18:13:44 haha. sure, i'm currently on the backup 13.5 BE :) 18:14:16 i can also remount rw while in single-user, but i couldn't think of anything to change 18:14:46 It is also possible to boot a BE and then craft a new Boot Environment installation that is upgraded and then try booting that new one. vermaden has a classic post on this https://forums.freebsd.org/threads/howto-freebsd-zfs-madness.31662/ 18:16:08 So if /upgrades/ are just totally problematic it is possible to effectively do a fresh install that way on an existing system and step forward into it. (into? onto?) 18:16:35 that... sounds really neat actually 18:18:09 That article is 14 years old and just as relevant today as when it was written. I love vermaden's quirky writing style. "This is SPARTA!" LOL! 18:24:36 Humorously I am trying to complete system upgrades this morning too. For me a few systems moved to 15.0-RELEASE p7 (which has gone much better than the 14.0-RELEASE did originally) and all of the rest up to 14.4-RELEASE p4 and one canary system on CURRENT. And then the jails. I need to improve my automation! 18:25:34 yeah, i'm too lazy with this stuff ':) 18:26:57 i'm glad freebsd-update still works even after deprecation, but i've been thinking about doing this upgrade since last year 21:42:20 rwp, i was able to track down the issue to smartd(8) 21:43:07 if i disable that service there are no more mrsas detachments, and i've been able to upgrade all the way to 14.4 :) 21:43:21 (i was even able to go all the way to 15.0, but i think it's too early for now) 22:41:59 rodri, Woot! It was smartd? Weird! I did not expect that. Glad you got it figured out! 22:42:46 rodri, 15.1 is scheduled for June 1st so you won't have long to wait for the .1 release to upgrade to it. 22:48:39 Meanwhile... On 15.0R installing postfix has a few annoying configuration bugs at install time. I should file a bug report on it. 22:49:46 The stock file contains both inet_protocols=all and inet_protocols=ipv4 and having both generates an initial warning and then 19 more lines of addition warning. 23:57:56 i love mr. sas