00:20:50 Thanks for the help everyone. 03:12:50 Howdy, folks! 03:14:11 Well, i managed to install xscreensaver, and tcc. 03:14:50 And i managed to have juggler3d run for so long, it's juggling patterns are starting to get more weird. 03:15:18 In other words, it's now doing juggling patterns that aren't even possible IRL. 03:17:53 :) 03:18:41 that's a good reminder to checkout xscreensaver again 03:18:55 jauntyd: True! 03:19:23 The best ones for me are the OpenGL screen hacks. 03:19:27 i'm just using a lock screen atm. BORING 03:19:59 Despite them using GL 1.2, they use the API pretty darn well. 03:30:17 And yes, you can even run the screensavers as the root window, allowing for them to become animated wallpapers. 03:46:11 server_network.c:191:26: error: use of undeclared identifier 'SOL_IPV6' 03:46:14 What's the equivalent in FreeBSD? 03:48:14 I'm surprised at the amount of windows i have running in the 2nd workspace. 03:49:01 I have: Steam(LSU), vim, irssi, juggler3d, mesa's bounce demo, and ioquake3. 03:55:59 where even is IPPROTO documented 03:57:26 I now have quakeforge running. 03:57:34 In addition to xload. 08:39:04 mail 09:54:46 when will firefox support vaapi on freebsd? 12:59:33 hey, I need to chroot to FreeBSD installed on ZFS from LiveCD, how can I do that? zpool import -R /tmp/zroot zroot does not give me all directories 13:08:58 okay, zfs mount zroot/ROOT/default 14:37:56 al1r4d: might want to ask the firefox people 17:24:29 hello 17:24:56 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280598 17:26:37 weird, I got a page fault... 17:26:48 Does anyone know why, when the version of protobuf from ports matches the internal protobuf version, MySQL links to the port-installed protobuf instead of the bundled one? 17:26:58 I think fusefs/rclone/sshfs is to blame for it 20:50:01 they should invent an extended accept() that returns ipv6 EHs 21:05:41 What can be the reason that I get no result for pkg search vlc ? (running 14.0-RELEASE-p9) 21:08:31 and of course I get 'pkg: No packages available to install matching 'vlc' have been found in the repositories' when I try to install in anyway 21:26:41 guntbert: An out-of-date or bad or wrong repo catalogue, maybe? 21:37:53 ek: everything is possible - I don't remember what I did to this machine - how would I check the repo catalogue? 21:38:38 pkg update -f 21:39:06 https://www.freshports.org/multimedia/vlc/ 21:41:16 rwp: Yes, I know that the port exists :-)) 21:41:20 If that doesn't help, what CPU architecture, and are you using latest ot quarterly? 21:41:24 i have the same issue 21:41:39 (i have installed vlc previously though) 21:41:40 guntbert: skipped in the last build, because x265 failed (as about 1000 other ports) https://pkg-status.freebsd.org/beefy20/build.html?mastername=140amd64-quarterly&build=d032848c5848 21:41:50 I am pretty sure it simply hasn't been built yet. 21:42:16 Ah... Errors during build. 21:45:07 does someone here have an idea why I can't reach beefy12 (https://beefy12.nyi.freebsd.org/) afaik it should do the builds for 14amd64-latest 21:45:35 beefy12.nyi.freebsd.org is IPv6 only and I have that problem too because I am IPv4 only here. 21:45:51 I really need to get an IPv6 solution working here so that I can browse those more easily. 21:46:24 nimaje: ah, thx -- where could I find that info by myself? 21:47:07 RhodiumToad taught me a technique for dealing with the IPv6 problem but the workaround isn't working for me at this moment. Maybe RhodiumToad will see this and jump in. 21:47:14 I have ipv6 here and the mirror via pkg-status.org doesn't work too https://pkg-status.freebsd.org/beefy12/jail.html?mastername=140amd64-default 21:47:56 nimaje, Among other things "host beefy12.nyi.freebsd.org" shows that it has only an IPv6 address and does not list an IPv4 address. 21:48:18 I use "host" but okay to use dig or drill too as is your preference. 21:49:23 I know that it is ipv6 only 21:50:33 I said that in response to the question from guntbert "where could I find that info by myself?" and I don't really know the full answer but that is part of it. 21:52:06 Errors from x265 blocking vlc: https://pkg-status.freebsd.org/beefy20/data/140amd64-quarterly/40008dd78683/logs/errors/x265-3.5_2.log 21:52:59 rwp: this is the first time I hear about beefy - will have a look. 21:56:18 guntbert: the first thing to check should be https://portsfallout.com/ but as the problem here is not a direct build failure, but being skipped because a dependency failed, check https://pkg-status.freebsd.org/builds?type=package next, filter for what repo you want information and use that bomb icon to go to the poudriere webinterface of the build there you can filter success, failure, skipped and 21:56:20 ignored 22:05:47 In this case the error is "SHA256 Checksum mismatch for x265-asm-warnings.patch". The patch is from 2023-06-27 so not a recently changed patch. 22:06:02 nimaje: thx, will do :-)) 22:07:46 a traceroute6 to beefy ends with an !A (Communication with destination network administratively prohibited.) 22:19:54 A different problem... I have installed 14.1-RELEASE on an Intel NUC model D54250WYKH and I can install Legacy BIOS and boot it manually no problem but it won't boot it automatically. 22:20:25 I can select it from the boot menu. Then it boots okay. But at boot time it will only ever automatically attempt a PXE boot. 22:22:21 sounds like the boot menu of the bios times out and tries its default option 22:22:34 Oh! Maybe it is because the default install created a GPT partition? I will guess right now that the BIOS does not know how to boot GPT. 22:22:43 Unfortunately I will have to smash it back to an MBR partition table and reinstall all but I think that is the next thing to try. 22:25:33 but you said it can boot it? from what I heard it seems to be a problem with the configured boot order 22:44:19 Unfortunately smashing and installing using MBR results in "missing operating system" from the BIOS. But it does at least try then. 22:45:02 nimaje, You would think so. But the order is to try the internal disks first and then the network boot second. And the result is that it never tries the internal disk and always tries to network boot. 22:46:17 The Intel NUC for BIOS firmware has this abomination "Intel Visual BIOS" which requires the mouse and is really very annoying and limited in functionality. 22:46:42 I can't tell you how much I would love to see Coreboot running on it instead. But even a classic old AMI Legacy BIOS would be welcome. 22:48:56 I just can't imagine that someone decided they wanted to have a graphical firmware configuration and came up with "Intel Visual BIOS" and then thought it would be an improvement. Wow. It's really terrible. 22:49:17 Not just the interface but it is limited in features. For example I notice that one cannot disable HyperThreading as just one thing I noticed in passing through it. I am sure it is missing other firmware configuration features too. 22:49:54 rwp, i was trying to install 14.1 on an old laptop, and same problem (though i didn't know how to manually boot, so i just got stuck after failing to boot PXE and it just said it failed to boot 22:50:14 That does sound like the same problem. 22:50:38 Here I can F10 to get to the boot menu then arrow down to select the disk then Enter to select the disk and it boots okay doing it that way. 22:51:18 I also imagine I could boot the USB automatically and then have it boot the internal storage. But that would always require something in the USB slot to boot then. 22:52:05 Every firmware uses a different set of function keys. It's F10 on that Intel NUC but it is F8 on this other ASUS motherboard. It's awful that they could not standardize on keys. 22:52:37 There is always a second or two where the firmware boot screen says the keys to select Setup and Boot Menu but you have to be fast to see it. 22:52:39 when i get to the boot menu and choose the HDD/SSD, it just prints "is failed" next to it 22:53:02 Grr... Oh well. 22:53:51 i wanted to revive an old laptop. maybe i will try again with 14.2 22:54:13 This system had been running Ubuntu okay. But the Kingston SSD in it failed off. I pulled it out and replaced it with a Samsung. And if I was doing that then I was going to install FreeBSD. But with this problem I think I need to install Ubuntu again and then verify that it will boot the old system okay. 22:54:15 this actually happened with 12.1 - i think it was - as well, so it didn't seem notable 22:54:21 I haven't given up yet though. Just collecting data on the problem. 22:54:43 interesting.. maybe i will try UFS to see if it behaves differently 22:55:14 I am also installing Legacy BIOS boot mode. I could also try installing UEFI mode. But... I hate UEFI... It's just so pesky. But that might work okay regardless. 22:55:49 Trying UFS as you say is another good thing to try. Another box in the test matrix. 22:56:03 i tried both BIOS and UEFI 22:56:06 Later though. Have to run now. 22:56:10 ttyl 23:27:47 Is this a good way to remote unlock an encrypted system? https://github.com/emtiu/freebsd-outerbase 23:53:31 interesting 23:54:55 linux has something that i dont remember the name 23:56:01 i think its dropbear ssh server