01:23:13 I've been using OpenBSD for a while now and I am considering running FreeBSD on one of my machines but I have one thing I want to clarify first. I am aware the FreeBSD does include proprietary binary driver blobs but I have found that one can compile their kernel use WITHOUT_SOURCELESS in src.conf. Would this paramater remove ALL the proprietary blobs to the same extent as OpenBSD or are there other things I need to do aswell? Thanks 01:23:13 so much. 01:25:27 Bumblehorse: is it true openbsd automatically downloads non-free software if the hardware requires i? 01:25:39 the option seems fairly explicit; it excludes all drivers that contain either binary native blobs or binary microcode 01:26:13 * RhodiumToad hasn't used it, though 01:27:00 johnjaye: yes 01:27:48 johnjaye, as far as I am aware, it does download non-free firmware, not device drivers though. 01:28:15 i'm not savvy enough to appreciate the distinction 01:28:20 WITHOUT_SOURCELESS_HOST is the option you want if you're ok with binary device firmware but not binary host code 01:29:28 I think the option only impacts modules, not stuff directly compiled into the kernel; you might also need to check that you don't statically configure any unwanted drivers 01:30:07 / 01:30:09 oops 01:32:22 seems there are not many binary host drivers; hpt*, ce, cp, are all I can find 01:34:34 hpt is a highpoint raid driver, ce and cp look like synchronous serial cards 01:35:03 disabling binary firmware takes out a bunch of wifi and network cards 01:36:49 there's also the GPU firmware modules, but those are not part of the base system 01:37:41 The machine is a thinkpad X200 that I put a certain Atheros card in already; I think it should be fine. 01:45:37 Is there anyway I can use these parameters during my initial installation? 01:46:10 The installation section of the handbook doesn't seem to say much about that. 01:48:40 not if you're installing from the ordinary distribution 01:48:50 which doesn't recompile anything 01:49:51 if you are absolutely determined, what you could do is compile everything yourself in some vm, and then install from that 01:55:14 So aslong as I reconfigre/install the custom kernel, delete the unwanted drivers (if any were present), 01:55:23 oops 01:56:08 ... then I shouldn't have anything to worry about with kernel modules, right? Only 'statically' configured drivers as you say. 02:03:30 l/win bal 02:11:42 at least one of the hpt* drivers is in the generic kernel, for what little that means 02:12:06 if you're building your own kernel you can strip almost all the hardware drivers out, and load only the ones you need as modules 02:12:28 * RhodiumToad doesn't go quite that far, I leave in the ones I usually need for boot 02:19:34 I ran zpool upgrade after an update and got the message, "Pool 'zroot' has the bootfs property set, you might need to update the boot code." What's the right way to update my boot code these days? 02:19:50 what partitioning scheme? 02:21:11 https://pastebin.com/6nqyXtmA 02:21:12 Title: # gpart show ada0 ada1=> 40 3907029088 ada0 GPT (1.8T) 4 - Pastebin.com 02:21:55 and from what you said before, this is legacy bios and not uefi? 02:22:16 yes, `sysctl machdep.bootmethod` says BIOS 02:22:46 for legacy bios, gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 2 ada0 (the 2 is the partition index of freebsd-boot) 02:22:52 and same for ada1 02:23:19 thanks again 02:24:01 ada1 is also failing smart tests so I wanna get this right, heh 02:24:15 for EFI, which you should probably do to keep it consistent, mount ada0p1 as an msdosfs partition and copy /boot/loader.efi to efi/freebsd/loader.efi and efi/boot/bootx64.efi 02:24:29 and same for ada1p1 02:25:04 your efi partition is much too small, did the installer do that? 02:25:25 probably, but I don't recall for sure 02:25:48 it's a few years old 02:27:26 Ok, I think I'm getting it now. So aslong as I unload, delete and prevent compilation with WITHOUT_SOURCELESS, I won't have to worry about non-free MODULES. Then, as long as I configure a custom kernel using the info in conf(5) and comment out the unwanted drivers, then I won't have to worry about drivers being compiled directly IN the kernel and these two combined should cover everything. Am I confused or is this correct? 02:27:40 And thanks a ton by the way! 02:27:52 think I will retire this machine soon and exit OVH for good. 02:28:01 as far as I know you're correct 02:30:20 Awesome, I hope you don't mind one more question. Earlier you were listing off example non-free drivers that fall under the categories of WITHOUT_SOURCELSS_HOST/UCODE. Where did you find this information? Was it on the web somewhere or did you look directly in your source tree? 02:31:25 I looked at sys/modules/Makefile 02:32:36 it doesn't seem to be a common question, I don't recall anyone asking it before and I've been hanging around here for several years 02:34:04 you mean mine? 02:34:09 yes 02:37:36 Well to be honest I came from a fully libre GNU/Linux distro on a librebooted thinkpad. I always had interest in BSD systems and then one day my distro removed package managers like pip from their repositories because one could use them to install non-free software. I found this to be overkill and switched to OpenBSD right away. Recently I've been wanting to try FreeBSD for some extra software availability though. 02:40:00 removing a package manager seems like a strange thing to do 02:42:41 very very strange. I understand they want to be ideologically consistent and make sure the user doesn't accidentally install non-free software, but anyone who installs and uses an OS like Parabola obviously doesn't need hand holding to the extent of removing a the main package manager of one of the most popular programming languages... 02:43:11 you might aswell disable networking because one can use it to install non-free software 02:43:35 I think that's about the point where your OS converts from a non-toy OS to a pretend playground 02:43:36 and mounting any devices that could have non-free software written to them 02:45:35 exactly 02:48:18 I was a little hesitant to switch but as soon as I understood that firmware doesn't run the in the kernel and exists in ROM already, I had not issues moving to OpenBSD. I don't understand why the distinction between the firmware and drivers isn't meaningfull to the FSF crowd. 02:51:03 I think I do understand it, though I don't make an issue of it myself 03:35:05 <_xor> nVidia sucks with their firmware blobs. 03:35:32 <_xor> It's sad to see because when I was more into lower-level gfx coding in the 90s & 2000s, nVidia drivers were a boon to the consumer market. 03:36:47 <_xor> 3dfx was really pushing Glide and hap-hazardly provided a crappy OpenGL "driver" (which wasn't even a full driver, just enough implemented to let specific games look good). 03:37:49 <_xor> OpenGL used GetProcAddress to load the parts of the API that it could find and then fallback to the software implementation for what it couldn't load. 03:38:15 <_xor> Then nVidia started shipping more closed firmware blobs. Really frustrating. 03:39:30 <_xor> "Most notably, binary blobs are very uncommon for non-wireless network interface controllers, which can almost always be configured via standard utilities (like ifconfig) out of the box; Theo de Raadt of OpenBSD attributes this to the work done by a single FreeBSD developer." 03:39:50 <_xor> What and to whom is he referring? 06:59:50 haha what 07:03:19 i might not take too much stock in that 08:41:31 Looking for a working command line example for ffmpeg invoking quicksync hwaccel. Supposedly i have all the drivers firing for it on my system. /dev/dri and /dev/drm are populated.. but im Having a hell of a time with figuring out the frmpeg side of it. 08:47:01 Has anyone successfully built security/openssh-portable with blacklistd enabled? 08:48:36 It fails for me without adding this patch, even after the recent update to 9.3p1 -- https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=269623 08:48:38 Title: 269623 – security/openssh-portable blacklistd extra-patch broken with 9.2p1 09:28:28 Hello, Thinkpad p14s gen1/intel is not listed in the FreeBSD wiki laptop page and I wrote this howto about making FreeBSD run on the Thinkpad p14s Gen1/intel. 09:28:31 https://codeberg.org/mco-system/freebsd-lenovo-p14s 09:28:32 Title: mco-system/freebsd-lenovo-p14s: Tips, tricks and configuration for running a Lenovo P14s (Gen1 / Intel) with FreeBSD - freebsd-lenovo-p14s - Codeberg.org 09:28:43 So how this can be added to the wiki page ? 09:29:51 As I'm a new FreeBSD user, comments and error correction would also be appreciated :) 09:33:22 doug_713705, I think you can make an account on the wiki and propose the change by editing wiki page, but I haven't done anything with wiki in quite a while so I might be wrong 09:36:00 meka: The Wiki about page states that that account must be asked to the Wikiadmin on IRC 09:37:10 I stand corrected :o) 09:38:11 oh, asked on the #freebsd-wiki chan 09:38:20 Good luck! 09:38:56 You make it sounds like an impossible mission :D 09:39:31 Nah, just ... everything I did for the first time was a disaster, so I wish people more luck than I had :o) 12:29:30 Hi! I have a freebsd 13.1 server with igb0 and igb1 connected to my switch in a lagg. I have a bunch of non-vnet jails with their addresses on igb0, but now I'm experimenting with turning them into vnet jails 12:30:39 I'm using the standard jail/jail.conf stuff. My problem is that my vnet jail cannot access the network. It can ping itself, but not the defaultrouter etc 12:31:07 I suspect that I neet do bridge lagg0 and the vnet ethernet device? (I haven't) 12:34:27 https://clbin.com/ICd0Z here the host net config 12:35:23 jail net config: https://clbin.com/jD3p9 12:38:17 and the jail config: https://clbin.com/nEupv 12:39:18 did you run `jib addm www lagg0`? not sure if that's quite right, as I let bastille do the heavy lifting for my jails. 12:40:36 jschmidt: I am wondering if I perhaps should add jailether to lagg0? 12:41:16 jailether is a 3rd interface? 12:43:17 yes, it is a third physical interface (that is not connected to the switch with any cable) 12:44:40 BTW, `jib` is located here: /usr/share/examples/jails/jib 12:45:12 you're end goal is to get the converted VNET jail to connect through lagg0, though, correct? 12:49:40 yes 12:49:53 I moved jib to /usr/local/bin 12:49:56 or well, copied 12:50:21 but yes, the end goal is to have the nvet jail connect through lagg0 12:54:22 ok, sounds like you're on the right track. you'll need something like exec.prestart+="jib addm www lagg0"; to connect the epair and physical nic, and exec.poststop+="jib destroy www"; to tear it down when you stop the jail. 12:55:16 so, I should scrap using the third interface at all, and just jib addm to lagg0 instead? 12:55:48 (I got the idea about using a third interface from mwl's freebsd jail book :) 12:56:12 I'm looking at page 161 right now. :^) 12:56:58 jschmidt: heheh! See how he suggests using a seperate interface which he calls jailether? 12:58:17 yeah, that's an option if you want. I do something similar in the homelab w/ an LACP lagg and have all my jails use it. 12:59:11 if you want to manage the host out-of-band, I'd use the dedicated jail interface. 13:00:29 in the book, he doesn't do anything special to "connect" the jailether interface and the "regular" external interface 13:00:45 it all seems to be taken care of by using defaultrouter="..." on the jail host? 13:02:55 I'm on my kindle, so I'm not 100% sure the page numbers match what's in the dead tree book. see the loghost jail.conf on page ~160/161? that has the addition of the VNET specific additions you need. 13:06:52 Yep, I see it (I also have the kindle version). But I think I'm using that config more or less, using a seperate interface for the vnet jails 13:06:54 hrmmm 13:08:18 you'll need to plug that 3rd nic in, then. is it up? I see you set it to up in rc.conf, but that won't apply w/out a reboot. `ifconfig jailether` 13:37:55 https://clbin.com/hBjjU jailether 13:38:05 https://clbin.com/4dv7J jailetherbridge 13:39:03 can lagg0 contain interfaces that aren't plugged in? 13:51:33 yes 13:53:25 that looks right. if you plug jailether in to your network, www should be on the network. 13:55:02 oh, wait... if you're asking if jailether can be part of lagg0, then yes, BUT... www isn't going to magically jump onto lagg0 - it's still tied to just the one (disconnected) nic. 13:59:24 and, if you want to use DHCP for the jails, don't forget to add 'add path 'bpf*' unhide' to a devfs ruleset in /etc/devfs.rules and call that ruleset out in jail.conf 14:00:11 (I usually forget that part when setting up a new jail host) 15:37:31 So, I just read through https://freebsdfoundation.org/resource/using-freebsd-as-a-virtual-host-quick-guide/ and I was wondering if the base vbox in Ports has the option to record VM audio and video, or if that's a feature of the extension pack. 15:37:35 Title: Using FreeBSD as a Virtual Host – Quick Guide | FreeBSD Foundation 16:29:19 Is there a simple way to sync users and groups between two jails? Or am I going to have to figure out NIS or LDAP or something? 16:31:49 do you mean that users newly-created in one jail need to show up in the other? 16:32:07 yes 16:37:03 I can't think of any simple way to handle that. 16:39:17 I was trying to puzzle out some shared null mount and symlink-ing the files in /etc to it, but... passwd is still gonna regenerate stuff on update in local /etc 16:39:45 haroldp: Maybe just script up a sync on creating the new jail. Or do you need users unique to new jails to propagate backwards? 16:40:03 nah, it will be one-way 16:40:27 If just coping existing accounts into new jails... Yeah, I'd just seed the new jail with data from the old. Anything more complex, a directory seems reasonable. 16:40:38 syncing on creating the jail would be no problem, but users get added and removed regularly\ 17:21:46 may be nullfs mount of specific files from the host somewhere? 17:22:24 can only do directories, not individual files, unless something changed 17:22:38 checking on current, it can do both 17:25:33 and it's also in 13.2 17:26:12 huh, do you have a keyword i can use to google that? 17:26:46 https://man.freebsd.org/cgi/man.cgi?query=mount_nullfs&apropos=0&sektion=0&manpath=FreeBSD+13.2-RELEASE+and+Ports&arch=default&format=html 17:26:48 Title: mount_nullfs 17:26:51 I'd bet that that interferes with renaming the files, which I'm pretty sure pw relies on 17:27:14 ah heh 17:28:17 "The mount_nullfs utility supports mounting both directories and single files." 17:28:22 hot damn 17:28:31 woah 17:30:26 Ok, who wrote this: it serves as a demonstration of layering by providing a layer which does nothing. (It actually does everything the loopback file system does, which is slightly more than noth- ing.) 17:31:52 at least it no longer says BEWARE OF DOG. 17:32:01 haroldp: "BSD 4.4 Lite sbin Sources" ;) 17:32:22 RhodiumToad: i think that was about unionfs? 17:32:42 pretty sure nullfs used to say it too. 17:32:58 that's like calling up air traffic control on the radio and getting a surfer voice. the random tone is disconcerting. 18:17:05 https://www.irccloud.com/pastebin/um95U2zY/posix_makefile 18:17:06 Title: Snippet | IRCCloud 18:17:27 I'm trying to get the basename of the directory that the Makefile is in, as a variable to use elsewhere 18:17:38 finding info on POSIX make seems to be sparse 18:17:46 uh, posix make has no $(shell) feature 18:17:49 and the WAT:= line evidently doesn't get executed 18:18:04 its a gnu-pollution then? 18:18:29 ok I can drop that and just use pwd -P 18:18:35 and it all works 18:18:35 ffs 18:19:06 use pwd for what? posix make lacks that too 18:19:44 make is posix, but im running this on bsd ofc + linux + mac 18:19:53 they all have `pwd -P` 18:20:14 Could you not switch to GNU Make? 18:21:07 parv: no 18:21:09 it's almost always a mistake to try and do anything nontrivial in posix make 18:21:22 well the whole makefile is ~ 20 lines 18:21:41 usual boring stuff, clean, dist 18:21:56 you know that even := is not in posix make? 18:22:03 sigh 18:22:21 no 18:22:23 only = is supported for setting variables 18:22:23 TIL 18:22:36 Use separate makefile🤷🏽‍♂️ 18:23:34 Using GNU make might be the most reasonable thing. Remember that FreeBSD wouldn't exist without the GNU tools being there early on. 18:23:54 As a workaround, you can pass the current directory as a parameter to make. For example, you can run make CURRENT_DIR=$(pwd), and in your Makefile, you can refer to $(CURRENT_DIR). This way, you're using shell features outside the Makefile, and the Makefile itself remains POSIX compliant. 18:24:13 or you can re-invoke the make from within itself 18:24:25 *shrugs* 18:24:30 Cool idea, RhodiumToad 18:24:49 jfc I thought this would be a trivial fix 18:25:06 I'll just hardcode the name and if anybody renames the repo good for them to figure this out 18:25:17 hah 18:25:31 hi all 18:25:50 this is making me feel less salty about coding /bin/sh 18:26:05 ;-) 18:26:25 there are worse things :-) 18:26:36 Just make sure to avoid bashisms! =snicker= 18:27:08 I mean, I have to code some "classic" ASP when I am done with this, so there are for sure worse things. :) 18:29:07 I have seen shell scripts with "#!/bin/sh" on CentOS|Rocky Linux that use(d) "[[ ]]" & other Bash specific features. Frankly Bash behaviour as (plainer) bourne shell is not strict enough 18:30:28 I try to teach people if you need bash do "#!/usr/bin/env bash" 18:31:33 * parv had converted a csh script here and there to /bin/sh; now do not care anymore unless I would be the maintainer 18:33:12 man env 18:33:44 I have a friend who's working on a visual basic 16 bit app atm 18:33:53 the business plan is to migrate it to perl 18:33:58 a modern language for modern times 18:34:14 I wrote my first and last csh script for zsh, and still get yelled at for creating a csh script 18:34:33 * RhodiumToad yells some more 18:34:41 RhodiumToad++ 18:34:49 I love perl, and I know it much better than a lot of langs, but I think most people think of it as a dead boomer language ;-) Python, doood! 18:35:02 python is horrible 18:35:12 Agreed... Only because of the whitespace issue 18:35:13 How so, RhodiumToad? 18:35:37 I prefer C style syntax and whitespace agnosticism. 18:37:17 Perl, Python, Ruby are similar enough🤷🏽‍♂️ (not counting issues with respective package|module management). Now Tcl ... 18:37:34 tcl is nice but flawed 18:37:36 hahah tcl... May only experience with that is eggdrop related. 18:37:40 ok, so /etc/sysctl.conf, is it key="value" or key=value? 18:38:12 I don't quote my sysctls. 18:38:33 * parv quotes unless that would cause some issue 18:38:52 I only wuote if it has spaces, and not sure if that is required or not 18:38:57 quote even 18:38:57 "It's all strings" 18:39:09 Demosthenex: quotes are not required in general 18:39:27 key = "value" or key="value" 18:39:48 All these personal questions... 18:39:50 i'm looking at all the man pages, and there's no formal spec. it's very loose 18:39:51 whitespace around the = is disregarded 18:40:16 I enter mine all in unicode. 18:41:12 the only spec is probably src/sbin/sysctl/sysctl.c:parse() 18:41:21 loader.conf says key="VALUE" explicitly 18:41:31 rc.conf says "sh syntax" 18:41:38 loader.conf isn't necessarily the same 18:41:51 rc.conf is literally read in by doing ". rc.conf" in shell 18:41:55 And mine there are quoted. Dunno if required. 18:41:59 use the source 18:42:18 what can i run to confirm the rc.conf, sysctl.conf, loader.conf are valid and don't contains typos or invalid values? 18:43:35 using only sysrc to update rc.conf can help ensure it stays valid, though it won't detect typos 18:43:41 Reboot and watch the console ;-) 18:43:50 sysrc does validation for adding and removing things, but if you've hand-edited the file you're assumed to be smart enough to spot mistakes or figure out how to correct them I think (meaning there's no tool to do a check; though I think making one might be a good idea) 18:44:34 it's almost impossible to detect typos in names in those files, since in many cases the names are not from a fixed list 18:44:47 something small in c or lua that can be added to base seems like an idea, if someone wants to run with it 18:44:47 and sysrc doesn't work on sysctl or loader.conf 18:45:08 Would be a nice tool to have.... Rebooting and checking dmesg or watching it is the only sure fire way right now that I know of. If you don't do this then you sometimes pay for it later when a reboot occurs by choice or otherwise. 18:45:10 right, because one thing that sysrc checks is that the name is a valid shell variable name 18:45:41 Erhard: Yeah, it's just rather difficult to get right 18:46:17 I think I have only had a problem once or twice in 35 years or so, but it is a problem when it happens. 18:46:29 Typo something, or misunderstand something, etc. 18:46:30 ct(1) - configuration tester; test configuration files. 18:46:42 Free realestate! 18:47:02 Demosthenex: in shell variables you cannot use key = value 18:47:04 Would be a good tool that would likely be adopted scross OSes. 18:47:09 `service foo enable` which is a wrapper around sysrc can at least help with enable/disable 18:47:10 across even 18:47:26 beastie: yep, spaces break it 18:47:27 you must stick the equal sign to both the variable name and the value. 18:47:54 Oddly, I prefer to edit the file myself rather than use sysrc. But I guess that is because I am old. 18:48:02 It'd have to be able to handle UCL, shell variables, and probably at least a handful of other things.. 18:48:12 Which basically means.. Good luck! :D 18:48:16 There may be a reason it doesn't exist ;-) 18:48:27 it's required to distinguish a command name and argument list from a list of environment variables specified before the command name. 18:48:40 Maybe the tool could instead fire up a vm for tetsing or something. 18:48:49 Though I am not sure that would help with loader.conf 18:49:02 e.g: CFLAGS="-g -O0" make a.out 18:49:21 for a lot of shell, yes. 18:49:35 I hate that too... because whitespace should not matter. 18:49:49 dch: I'm much happier coding perl than VB. Much happier, heh 18:49:58 would be nice if augeas could do ucl 18:50:03 haroldp: I think everybody would be 18:50:08 wow, perl.... ufff 18:50:16 $_ baby! 18:50:23 have you tried python? 18:50:29 meena0: in the interests of scope creep and yak shaving, I think you should add it 18:50:39 I'm definitely a functional programming zealot 18:50:54 but I quite like lua 18:51:24 dch: yeah, i should 18:51:52 anyone know offhand if there's a simple incantation to disable aesni in a kernel that has it compiled in? 18:52:26 if we're standardising on UCL, standard configuration management tools should be able to process it 18:52:50 Maybe sysctl hw.crypto.disable_aesni=1 18:52:54 ? 18:53:23 UCL? 18:53:37 Erhard: unknown oid, at least in 13.x 18:53:42 ah 18:53:52 Demosthenex, Configuration in Lua 18:57:57 almost, 18:58:19 bah, took me 3 goes to get the device hint right in loader.conf 18:58:29 hint.aesni.0.disabled="1" works 18:58:43 Cool 19:05:56 RhodiumToad: yeah, bizarrely a boolean value needs to be a string. 19:05:59 That always gets me. 19:06:27 first time I typoed "aesni", second time I had "disable" instead of "disabled" 19:07:10 Wait, you're right, it doesn't. I've got hw.nvme.use_nvd=0 without any quotation marks. 19:07:16 When did that change? 19:24:11 RhodiumToad: you were correct that null_mount-ing the various passwd files wouldn't work. I presume due to due to copying, as you suggested 20:00:03 what packages do i need if i want to compile arm firmware with clang on my freebsd? does the preinstalled version already support that? if so, where do i find the header files defining uc pins and stuff? 20:03:16 phryk: in theory, base clang can build arm, or rather, all supported architectures (with possible exception for the ones that still need gcc) 20:04:17 you can also use qemu-user-static(-devel) 20:05:45 meena0: okay, where do i find the header files that define the cpus supported for cross-compilation? 20:06:11 been find | grep'ing through /usr/include but i'm not really finding anything that looks like the right thing. 20:06:37 right. hmmm 20:07:58 cross-building stuff isn't installed anywhere by default 20:08:43 the files used for cross-building kernels can be found in, e.g., src/sys/{arm,arm64}/include 20:09:40 I don't want to build freebsd. i want to build raw firmware for ucs. 20:10:07 well, that may require tools not in base 20:12:11 RhodiumToad: not seeing any llvm/clang arm packages tho. does that mean i have to use arm-gcc? 20:12:48 the llvm packages include all supported targets 20:13:25 but again, that won't necessarily include things like header files with details of specific arm hardware 20:14:56 some of that sort of thing is in the kernel header files for arm, which I pointed out before 20:28:50 I've tried switching from mysql57-server to mariadb1011-server. However, running service mysql-server start does nothing (as does running mysqld_safe &). I must be missing something. 20:29:25 did you enable the service in rc.conf? 20:30:53 do you have any logs? 20:30:54 Yes. mariadb uses the same items as mysql, i.e. mysql_enable="YES". 20:31:28 Nothing in the logs. 20:31:50 * RhodiumToad is a postgres person, knows little of mysql 20:33:00 same here, not using mysql since years 20:33:35 in vt can I change the resolution itself, or just the font? 20:33:38 postgres has too much overhead for my uses. 20:33:38 try running with --syslog 20:33:46 mysqld_safe that is 20:33:47 it could be permission issue. do you use the same user on your /var/db or /var/run directories now as for the mysqld? 20:34:25 johnjaye: which backend is vt using? 20:34:33 Or check mysql/error.log wherever that is on your system 20:34:39 er... i'm not sure. i just thought vt was the driver itself 20:35:01 A permission issue is a good idea, but mariadb uses the same user/group as mysql 20:35:54 i'm trying various .fnt files and the ones in vidfont, but they're either too small or too big for my screen 20:35:56 can you truss the mysqld_safe process? 20:36:10 johnjaye: vt can be backended by e.g. vga (for legacy boot), efifb (for EFI boot), drm (when a GPU driver is loaded), etc. 20:36:39 johnjaye: are you booted with no GPU driver loaded? 20:37:22 i don't know if any of the 12 things kldstat listed is gpu but i'm not in x11 if that's what you mean 20:37:44 ok. grep '^VT' /var/run/dmesg.boot # what does this say? 20:38:17 it says VT(efifb): resolution 800x600 20:38:44 i guess changing resolution to smaller is what i want here. then the default font would be the right size 20:39:17 ok. so you are booting with EFI. you can either change the resolution in EFI, or you can load a KMS driver and have vt set the mode 20:39:58 kms driver would be what? 20:40:10 i know the radeon driver is what i need for this laptop to run X 20:41:29 if you load the radeon driver, then vt will set modes according to the setting of kern.vt.fb.default_mode or kern.vt.fb.modes.OUTPUTNAME 20:41:51 and yes, it's the same driver that you'd need for X 20:43:12 mysqld_safe --log-error+/tmp/mariadb.err doesn't save anything to the error file 20:43:23 ok. how do i tell efi then 20:43:36 that may be more platform independent 20:43:37 if you don't want to do that, then efi_max_resolution in loader.conf can configure a maximum requested resolution 20:43:53 or you may be able to set things like that in the bios config 20:44:36 ooh. didn't know about efi_max_resolution yet. any other fancy features i can use to make efi boot more beautiful? can i pick a custom background? :3 20:44:47 although I get " mysqld_safe Logging to '/tmp/mariadb.err'." and "mysqld_safe Starting mariadbd daemon with databases from /var/db/mysql" and nothing beyond that. 20:45:12 phryk: there are loads of things you can do in loader.conf 20:45:30 plus you can supply your own lua code to make it as fancy as you please 20:45:41 is that new? o_O 20:46:05 ah wait, that's the other loader. 20:46:07 the lua version of loader has been the default since 12.x I think? 20:46:22 yeah 20:47:09 well, that's new for me. i think the last new setup i did when 11.0 was fresh. :P 20:47:17 in 14.0 you'll be able to be even spiffier with a loader.conf.lua rather than having to hook into config loading in local.lua 20:48:17 * RhodiumToad rarely bothers with such things, I even use beastie_disable="YES" 20:48:41 bah 20:50:09 btw kevans, can anything be done about D24324 ? 20:50:38 I've had it in my own ports tree for three years, but it's been sitting in phab for two 20:52:14 let me poke some people 20:53:01 I don't like to have my ports tree diverge too much from upstream 20:55:24 RhodiumToad: is efi_max_resolution="640x480" the right syntax in loader.conf? 20:55:40 i tried a few different ways but it stubbornly stays on 800x600 20:55:41 yeah, understandable 20:55:42 I believe so. kevans would probably know better than I 20:55:55 oh wait 20:55:59 try "480p" 20:56:01 yeah, it accepts WxH or, IIRC, some common ones line "1080p" 20:56:05 ok. brb 20:56:17 the default should be 1x1 20:56:33 i.e. we won't touch the resolution at all, whatever the firmware left us at 20:56:53 usually the lowest res gop mode on the hardware I was working on at the time 20:58:27 it's worth noting that efi_max_resolution can only result in changes to modes the firmware makes available to us (as seen by executing `gop list` at the loader prompt) 20:58:42 no luck. i'll have to try the radeon driver. i don't recall how i determined which one I needed though 20:58:46 what are the way to free up some space 20:58:50 pkg reports at least a dozen different radeon drivers 20:58:51 i ran pkg clean 20:59:00 some ideas ? 20:59:19 i remove /usr/ports 20:59:22 removed 21:01:08 johnjaye: there are only two you need to worry about: radeonkms (old radeon cards) and amdgpu (newer cards) 21:01:24 johnjaye: the package will figure out what to load. 21:01:50 eoli3n: what's using the space, and do you need it? 21:02:01 my backups, and yes 21:02:39 johnjaye: use pciconf -lv to identify the GPU 21:05:20 It looks like a "Warning" was really an error "secure-file-priv" in my.cnf caused the problem. On to the next issue. 21:05:45 johnjaye: for the actual package, what you want to install is drm-kmod 21:06:04 ok. what do i do after that 21:06:17 did you identify your GPU? 21:06:20 yes 21:06:42 what is it? 21:07:01 mullins r4/r5 graphics 21:07:25 pci ids? 21:07:35 i also have drm-kmod installed 21:08:20 is that the vgapci@0:0:1:0 part? 21:08:25 no 21:08:38 there should be a vendor and a chip id 21:09:15 vendor x1002, device 9851, that? 21:09:38 {0x1002, 0x9851, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_MULLINS|RADEON_IS_MOBILITY|RADEON_NEW_MEMMAP|RADEON_IS_IGP}, 21:09:59 pciconf -lv | nc termbin.com 9999 21:10:01 pciconf just has numbers 21:10:36 right, what I gave is the line from the driver that matches it 21:10:58 have you had X working on freebsd on this hardware before? 21:11:19 if you do not have the correct drivers installed does it not simply fall back to vesa 21:11:51 i think so yes 21:11:57 but after i reinstalled i lost everything 21:12:09 daemon: it won't let me ch ange the resolution from 800x600 21:12:23 so yes it fell back to vesa 21:12:45 so should i add kldlist="amdgpu" to /boot/loader.conf 21:13:03 https://wiki.freebsd.org/Graphics#Radeon_KMS_.28kernel_mode_setting.29 21:13:04 Title: Graphics - FreeBSD Wiki 21:13:16 johnjaye: kld_list="..." and it's either amdgpu or radeonkms 21:13:21 but I would stick with RhodiumToad all my bsd boxes have been headless since it was xfree86 21:13:35 i don't need x. this is a different issue 21:13:55 I haven't used any recent amd/radeon gpus, I had an old radeonkms one but am now on nvidia 21:15:02 looks like amdgpu is the one for this. 21:16:04 is the hack disabling console output still needed for amdgpu on EFI? 21:17:47 ah, seems that's fixed now 21:18:16 hmm. i added it to loader.conf but it doesn't load automatically 21:18:28 then i hard freeze when i do kld_load amdgpu 21:18:29 drm drivers are blacklisted in loader.conf 21:18:51 oh ok 21:19:08 er kldload 21:19:37 hm. kldload should work. 21:19:42 should kld_list="amdgpu" go into my rc.conf instead? 21:20:09