02:35:46 I've got some #ifdef OpenBSD code calling ioctl(DIOCGDINFO) and I'm trying to find the freebsd equivalent, but apparently it was removed in 2015? 02:36:39 I found https://lists.freebsd.org/pipermail/freebsd-current/2015-January/054144.html which says yes it was removed, and linked to https://lists.freebsd.org/pipermail/freebsd-current/2015-January/053960.html which is just a bug report about packages breaking because it was removed. 02:37:28 I followed the thread forward and got "503 backend failed" errors, also when trying to lead the month index. 06:31:51 hello I trying to install freebsd on an apu2d4 over serial console, I got output on the serial console until lo0 link state changed to UP https://dpaste.com/CMT67R8RR any idea what it could be why I dont get the installer prompt.. 06:56:45 Hi, I would like to ask. I have installed KDE, I use Intel GPU, which obviously is properly set up (glxinfo says Intel(R) HD Graphics), and despite that KDE is very laggy, for example when dragging windows or scrolling in a web browser. My question is whether this is normal, simply not so good GPU utilization on FreeBSD? I'm fine if there is worse 06:56:45 GPU utilization on FreeBSD, I just need to know it. Thanks. 07:38:50 It's not normal 08:04:00 Heck! Now I have tried to install gnome and it works well, and not only that - Full HD videos on Youtube, via Firefox, are slighly occasionally lagging on Debian GNome, but not lagging in FreeBSD!!! (I'm not KDE user anyway, so don't care anymore) 11:21:01 fixed my bizarre corrupted directory 11:21:16 which I talked about few months here 11:21:22 *ago 11:22:07 boot into single user.. then fsck -y 3 times 11:23:07 I want just to ask why my ufs partitions corrupt on freebsd all the time 11:23:48 before someone say bad drive I tried 100% new one after a month same thing happends files disappers 11:24:38 I need fsck to fix it 11:26:07 Is there anyway to stop corruption from first place 11:26:14 do you need ufs? 11:26:21 is it bad? 11:26:53 I guess about everyone is on zfs 11:27:11 i was on zfs, been on ufs for a while 11:27:42 what's your experience with it.. good or bad? 11:28:35 kinda good if we don't talk about unsafe shutdowns causing problems sometimes 11:29:04 i still have zfs mirror for my hard drives though 11:31:25 I just heard before if I use freebsd I should go for zfs or ufs. 11:32:05 I choose ufs.. bec zfs is more complicated 11:32:22 yes, UFS is simpler than ZFS but it seems more rock solid 11:32:27 because of how it works i guess 11:32:41 bus as I see ntfs is more stable on "unsafe shutdowns" than ufs 11:33:10 https://freebsdsoftware.org/blog/zfs-vs-ufs-freebsd 11:33:18 sometimes I experience power outages here 11:33:50 I moved to zfs years ago, and never had any issues with my drives whatsoever. 11:34:23 "If you have at least 2 GB of RAM and any interest in snapshots, data integrity, or painless system updates, go with ZFS. If you are running a minimal system on tight hardware, UFS will serve you well without complaint." 11:34:30 I want this 11:34:48 look like I need to get a bigger drive and go zfs soon 11:35:13 zfs may require more ram but can be used with low ram via tuning. why bigger drive? i don't think zfs requires that 11:35:40 yeah I know but my system drive is already ufs 11:36:08 so for the switch to zfs 11:36:16 I need new system install and new drive to separate every part into it's own partition 11:36:24 right 11:37:20 nxjoseph: but I can't now is there anyway to stop this from happening little bit at least 11:37:45 i don't know, how does it happen? 11:37:49 prevent the power outages then... UPS? 11:37:53 unsafe shutdowns can cause issues 11:38:08 maybe enable some UFS properties like journaling, soft updates? 11:38:12 (if not enabled) 11:38:30 yes UPS might be a way but some people cant afford it like me 11:38:51 i guess they also require maintenance every X months? 11:40:06 don't think so.. the U stands for Uninterruptable 11:40:40 is it safe to enable those on working root partition 11:40:58 i am not sure but it's better performed on read-only mounted root i guess? 11:41:07 or not mounted at all ,like from usb drive 11:41:35 The tunefs utility cannot 11:41:35 be run on an active file system. To change an active file system, it 11:41:35 must be downgraded to read-only or unmounted. 11:41:37 man tunefs 11:41:56 yes I will do that sure.. but after I reboot into normal mode will cause problem 11:42:11 i don't think so 11:42:30 you can right now check which are enabled or not 11:42:56 tunefs -p / - this is safe to run 12:05:16 ok, SU+J enabled for partition root.. disabled for other one 12:05:45 but I read SU+J is bad for outages.. and gjournal is better 12:05:58 also bad for big date 12:07:21 hm, i don't know, ymmv 12:07:45 "Also, I've noticed a trend with SU+J in the case where the filesystem uses the journal correctly, it marks the file system as clean, but all too often when followed with a forced non-journaled fsck also in single user mode, it finds many filesystem errors. It should not mark the filesystem as clean in this case, but it does anyway ... so I am very uncomfortable about recommending SU+J to anyone." 12:07:46 same as me 12:08:02 https://forums.freebsd.org/threads/gjournal-vs-soft-updates-journaling.54689/ 12:12:38 looks like I need to read more about it.. and gjournal or zfs is best solution, also thank you 12:12:51 you're welcome 12:30:08 I have this running in the background: `xautolock -time 15 -locker slock`. It dosn't activate slock after 15 min though. It works if I manually run `xautolock -locknow` though. I'm pretty sure it work earlier. Could this have something to do with the fact that I have disableb power saving mode for the USB-ports? 12:39:49 Yep. It works when I removed my Fiio Air Link USB-dongle. 12:51:23 And now it works when it's connected... bah 13:56:47 anyone know if there is an RSS feed for https://www.freebsd.org/security/advisories/? i can see the ports collection VuXML has a feed but what about the base system? 14:20:13 petercs: LLM thinks there used to be at https://www.freebsd.org/security/feeds/advisories.xml 14:20:52 feeds/ gives a 404 14:21:14 ISTR the main site was redesigned. perhaps rss was overlooked 14:33:11 f451: yeah i did try adding `/rss.xml` and `/feed.xml` to the end but no joy :/ i guess i could ask on a mailing list or the forums about it? 14:34:01 because it feels like something that should exist for those who use an RSS aggregator for security advisories rather than mailing lists 14:37:32 yeah, i'd ask on security@ too 15:50:07 https://www.vuxml.org/freebsd/rss.xml could this be anything of value? 15:57:06 Hund: vuxml is for ports afaict 15:59:13 there is this: https://www.vuxml.org/freebsd/index.html 15:59:37 but thta has ports and src mixed in, and it's not an rss feed 16:36:23 oh 17:16:24 aha! i found it! 17:16:58 https://www.freebsd.org/security/feed.xml 17:19:12 Hund: ^^^ 17:22:03 nice 18:05:06 I trying to install freebsd on my apu2d4 over serial console, I have get the serial console to work and I get output.. but after https://dpaste.com/2PU7R95EK I dont get anything (the installer doesnt boot) I have add the configuration for serial-console in loader.conf 18:07:12 Dual Console: Serial Primary, Video Secondary 18:07:22 makes me thing that you shouldn't need to 18:07:27 the speed doesn't change, does it? 18:07:50 rtprio: nope it should be 115200 18:08:53 When switching msata with my openbsd on it´s working (and has working for 14 years). I have test 3 msata with same result..so I it feels I missing something.. 18:11:21 I have also change to only serial but output stops after lo0: link state changed to UP.. and I used this image FreeBSD-15.0-RELEASE-amd64-memstick.img (dd to my usb). must I add something to /etc/ttys or something? 18:11:53 nwe, Hints from my notes: Boot to the installer. Select "Escape to the loader prompt" set comconsole_port=0x3e8 (for my 3rd comm port here, whatever for you there) set console=comconsole boot That must be typed in slowly. If I paste it in then it garbles the data with a buffer overrun. 18:12:15 After install to make that permanent edit /boot/loader.conf and install those settings there. 18:12:42 At that point the console is active. No need to edit /etc/ttys file to configure getty as one is started automatically. 18:13:54 On my IPMI SOL serial over lan console the BIOS screen expects a 100x30 sized terminal. I create an xterm that size so that it has a sane display. And then after I log in "export COLUMNS=100 LINES=30" keeps that end sane too. 18:15:57 rwp: I will test that 18:21:09 I'll just note something that I am sure is obvious but... The serial terminal does not have any support for SIGWINCH signal window size change. Hardware terminals are always of a fixed size. 18:21:16 So don't go resizing the emulator window as that won't track through like it does with an X Window XTerm or other emulator which catches SIGWINCH and reacts to the size change. We can only set the export COLUMNS=100 LINES=30 size to our terminal size manually like that. 18:51:16 rwp: but this has only 1 comport so I dont think I need to set comconsole_port=0x1e8 the strange think is that I see the FreeBSD boot menu and the text after until.. and my terminal is 100x30 now. 18:56:35 are those boards any good? they seem out of stock everywhere? 18:58:15 rtprio: is really good but PC Engines are going end-of-live. so you cant buy them anymore :/ 18:58:59 The FreeBSD boot menu automatically displays /everywhere/ both to the vidconsole and the comconsole. But when the kernel gets going by default it switches to vidconsole unless otherwise directed. Pretty sure. That's from version 12 days but pretty sure it hasn't changed from 12, 13, 14, 15 for that detail. If you find it has please let me know. 19:10:54 shame. i have a soekris 4501 that's sitting in the bin since it feels so obsolete at this point 19:15:18 storage bin, j'espere? 19:20:39 hmm should I choose new package or Distribution Sets now with 15.x? 19:28:51 f451: Cool. Thanks! 21:34:47 hmm I don't see who is in this channel 21:36:16 Was is or was the issue with 14->15 upgrade? freebsd-update is fine (currently) but trying to from non-pkgbase to pkgbase isn't supported? You need to do a fresh reinstall? 21:36:32 Even 15 -> 15 pkgbase. 21:37:47 you can use https://github.com/FreeBSDFoundation/pkgbasify for 15 -> 15 pkgbase 21:39:49 Sounds scary. experimental. 21:39:50 you can't upgrade and pkgbasify at the same time, you need to switch to the same version or it will have issue merging configuration files 21:40:12 ok 21:40:26 I think it's time to move to 15. So freebsd-update first. 21:43:27 skered: https://github.com/FreeBSDFoundation/pkgbasify/commit/a25484da11b8e9fc5f20bcfe8ec742d1857a602f 21:43:51 you can try with 14, but safest bet is probably to freebsd-update first :) 21:44:26 You can also use pkgbasify for 14 -> 15 update. 21:44:43 It's very simple and very fast. 21:45:09 pkgbase then upgrade 21:45:32 can't do both at the same time 21:46:01 Correct. 21:46:08 Only a few simple steps, though. 21:46:18 And the time saved is incredible. 22:35:37 are dedicated arc cards supported? (a310 etc?) 22:36:10 i really can't find anything concrete with drm-kmod 22:54:04 Doesn't look like ARC is supported yet, but work appears to be ongoing: https://github.com/freebsd/drm-kmod/issues/315 23:57:14 Hm. Applying today's updates, /usr/libexec/sshd-auth didn't get applied in a jail. It got applied to the physical systems I tried. Anyone else seen this? 23:57:40 Updated with freebsd-update, FreeBSD 14. 23:58:03 It appears to have popped into existence with this update.