I'm trying to install TrueNAS CORE 13.0-U6.3 on a machine and cannot get past checksum error on base-os....tgz. - Machine Spec: TRIGKEY G4 Mini PC 12th Generation Intel Alder Lake-N N95 Processor,up to 3.4GHz(4C/4T) Micro PC,Mini Computers with 16G DDR4 3200MHz/500GB PCIE1X SSD,Supports 4K@60Hz/Dual HDMI/WiFi5/BT4. - Type: x64_86, EFI - Error during install right after creating or skipping creating of swap space: See pic attached. What have I tried: - Installed Win 11 in the machine successfully Installed FreeBSD 14.1 successfully Machine runs Clonezilla without issues - I'm using Ventoy to load up the ISO. - Checksum of the TrueNAS ISO is correct. I've tried safe mode install - Tried to install version 11, 12, 13 of TrueNAS core, all crash due to a variety of reasons during bootup. Tried to install TrueNAS Scale, it crashes as well. - However, the same flashdisk with the TrueNAS iso runs and installs on an older machine without issues. So what's happening here? Is TrueNAS finding some hardware issue or compatibility issue with the TrigKey Machine.

Forgive my ignorance, I've used a dozen distros of Linux (Debian and Fedora derivatives) but haven't yet wet my feet with BSD. I'm attempting to write the current TrueOS installer to a USB, through the Debian derivative Mint, v. 18.2. However, I'm not having much luck. I've cleared all partitions off of the thumb drive, and then launched the command:

sudo dd if=./latest.img of=/dev/sdf bs=1M

Where sdf is the thumb drive, and latest.img is the disk image. After some time, it completes, and I have a formatted drive which has a partition on it, which, as anticipated, Linux does not recognize (as Linux has zero or next-to-zero support for UFS in most cases). I boot to it, through UEFI of course, and it begins to start, then tells me that there is no bootable system on the chip. This is not an EFI/BIOS message, as the installer starts a self-check briefly before telling me this. I restarted to Mint and looked at it in GParted, and found multiple complaints about the structure of the drive. (I would love to quote this to you directly, but I reformatted the thumb drive earlier today and am currently unable to retrieve it.) As gung-ho as I usually am about installing an OS on a spare drive, I am not willing to goof around further until I've got this problem figured out. I thought disk dump would copy the image byte-for-byte? Does anyone see anything overtly wrong with my method here? I'm attempting to follow the handbook as closely as I can. If I don't get an immediate solution I'll try it again in a couple of days and grab the log verbatim. --ADDENDUM-- I just finished dd-ing the image to the disk again, and opened it in GParted. The two messages were: The backup GPT table is not at the end of the disk, as it should be. Fix, by moving the backup to the end (and removing the old backup)? (Clicked Fix) Not all of the space available to /dev/sdf appears to be used, you can fix the GPT to use all of the space (an extra 10004782 blocks) or continue with the current setting? (Clicked Fix) Afterward, the final partition sizes on /dev/sdf were:

/dev/sdf1 800.0 KiB (boot, esp)
/dev/sdf2 63.00 KiB
/dev/sdf3 2.68 GiB
/dev/sdf4 1.00 MiB
unallocated 4.77 GiB

It's late, but after I try this again I'll either report back with any error messages or submit an answer to my question.

I have installed a TrueOS 13.0-CURRENT desktop system with cups 2.2.8 installed from pkg. Printing works like a charm, but cupsd is not starting at boot, despite this being in /etc/rc.conf:

cupsd_enable="YES"
devfs_system_ruleset="system"

sudo service cupsd start has to be run after boot to start it. It works fine, but it should start at boot. During the boot output where it shows the services being started, there's no visible error; it just doesn't mention any attempt to start cupsd.

Inspired by "https://unix.stackexchange.com/questions/395908/ ": I am using FreeBSD/TrueOS/DragonFly BSD and have some software from Ports that when run complains about a missing /etc/machine-id file. I do not see any such file in /etc. What is this file? Should I have it? How do I make it, if yes?

Update -- They don't! At least, not for me. See my answer. Original question -- According to [last year's Phoronix benchmarks](https://www.phoronix.com/scan.php?page=article&item=freebsd-12-windows&num=4) , applications on FreeBSD mostly run slower than on Debian (including Stockfish chess engine, Node.js, FLAC encoding and other computational tasks). Phoronix article itself attributes some of the performance differences to use of Clang instead of GCC compiler. [Some other](https://www.quora.com/Is-FreeBSD-faster-than-Linux/answer/Ben-Lunsford) opinions say that use of ZFS makes FreeBSD slower, as ZFS is inherently slower than ext4. But even purely computational tasks on FreeBSD compiled with GCC8 performed slower than on Linux. What is the cause of that? Is it inherent to differences between FreeBSD and Linux kernels, might it be caused by worse quality of drivers or is there some other reason? **P.S.** To make it more specific, here is a fairly simple purely computational program that runs slower on FreeBSD than on Linux according to Phoronix: [m-queens 1.2](https://www.phoronix-test-suite.com/benchmark-files/m-queens-1.2.tar.gz) . Compiled like this: gcc -o m-queens.bin main.c -O2 -march=native -mtune=native -std=c99 -fopenmp Since this a multithreaded task that was run on two 20 core CPUs, I suspect the performance difference boils down to how well OS handles multiple threads. **P.P.S.** To make it more clear, I am aware that FreeBSD has [good networking capabilities](https://www.phoronix.com/scan.php?page=article&item=windows-linux-10gbe&num=4) and that it is [used by Netflix](https://fosdem.org/2019/schedule/event/netflix_freebsd/) . The question is specifically about computational tasks, like the one above. **P.P.P.S.** After installing FreeBSD (TrueOS) on my 6-core desktop alongside Ubuntu and trying to run the queens benchmark myself, I didn't notice any significant difference in multithreaded performance. While Phoronix claims that it ran 39% slower on FreeBSD, in my tests it was only 3.7% slower, which could be attributed to slight difference in compiler version (gcc 7.4 on TrueOS, gcc 7.2 on Ubuntu). I will test more later.

I have a TrueOS installation. I was wondering if it was possible to follow the LFS book on my current system.

I am trying to run TrueOS v17.12x64 on QEMU but got corrupted display immediately after booting to GUI: I am just going with the ordinary graphics setup. Here's my domain file: Here's my QEMU version: # qemu-system-i386 --version QEMU emulator version 2.8.1(Debian 1:2.8+dfsg-6+deb9u3) Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers Looks like QEMU is not officially supported as a target platform according to [here](https://www.trueos.org/handbook/install.html) but I am wondering if anyone ran into this before and managed to work it out?

## Background I downloaded a handful of PPD files for Linux, with an expectation that they will work on TrueOS Desktop, which is currently based on FreeBSD 12.0-CURRENT. I know that with the web interface to CUPS – typically http://localhost:631/ – there's 'Or Provide a PPD File:' with the option to browse the file system, but I prefer to have the driver listed after I select the relevant make/manufacturer. ## Success, and the question I experimented with placement of the PPD files at /usr/local/share/cups/model/other where the other directory was made by me. Success (example below), but: - I'd like to know **whether a different path would be more appropriate**. ---- ### Example [gjp4@momh167-gjp4-hpelitebook850g2-trueos /usr/local/share/cups]% ls -l total 796 drwxr-xr-x 2 root wheel 9 30 Oct 14:10 banners -rw-r--r-- 1 root wheel 331836 28 Oct 02:33 calibrate.ppm drwxr-xr-x 2 root wheel 5 30 Oct 14:10 charsets drwxr-xr-x 2 root wheel 15 30 Oct 14:10 data drwxr-xr-x 2 root wheel 4 30 Oct 14:10 drv drwxr-xr-x 2 root wheel 13 29 Oct 18:03 examples drwxr-xr-x 2 root wheel 9 30 Oct 14:10 mime drwxr-xr-x 3 root wheel 5 30 Oct 14:14 model drwxr-xr-x 2 root wheel 10 30 Oct 14:10 ppdc drwxr-xr-x 2 root wheel 2 14 Oct 20:33 profiles drwxr-xr-x 7 root wheel 77 29 Oct 18:03 templates drwxr-xr-x 2 root wheel 4 30 Oct 14:10 usb [gjp4@momh167-gjp4-hpelitebook850g2-trueos /usr/local/share/cups]% cd model [gjp4@momh167-gjp4-hpelitebook850g2-trueos /usr/local/share/cups/model]% ls -l total 19 -rw-r--r-- 1 root wheel 20940 5 Oct 22:52 CUPS-PDF.ppd lrwxr-xr-x 1 root wheel 39 24 Oct 23:43 foomatic-db-ppds -> /usr/local/share/foomatic/db/source/PPD drwxr-xr-x 3 root wheel 3 30 Oct 14:10 gutenprint [gjp4@momh167-gjp4-hpelitebook850g2-trueos /usr/local/share/cups/model]% sudo mkdir other Password: [gjp4@momh167-gjp4-hpelitebook850g2-trueos /usr/local/share/cups/model]% cd other [gjp4@momh167-gjp4-hpelitebook850g2-trueos /usr/local/share/cups/model/other]% sudo cp /usr/home/gjp4/Desktop/BH754ePPDLinux_300000000/English/CUPS1.2/* . [gjp4@momh167-gjp4-hpelitebook850g2-trueos /usr/local/share/cups/model/other]% sudo cp /usr/home/gjp4/Desktop/BHP1250PPDLinux_320/English/CUPS1.2/* . [gjp4@momh167-gjp4-hpelitebook850g2-trueos /usr/local/share/cups/model/other]% ls -l total 284 -rw-r--r-- 1 root wheel 22590 30 Oct 17:39 KO1250opn.ppd -rw-r--r-- 1 root wheel 497755 30 Oct 17:39 KO1250UX.ppd -rw-r--r-- 1 root wheel 24262 30 Oct 17:39 KO754opn.ppd -rw-r--r-- 1 root wheel 199193 30 Oct 17:39 KO754UX.ppd [gjp4@momh167-gjp4-hpelitebook850g2-trueos /usr/local/share/cups/model/other]% Selecting a driver that relates to one of the four files that I placed at /usr/local/share/cups/model/other: Using that driver, a print dialogue:

I would like to try using TrueOS as an alternative to macOS on Apple Mac hardware having 64-bit Intel chips such as MacBook Pro. The system requirements page in the TrueOS User Guide do not say anything specific about Apple Mac hardware. The mentioned requirements of 1-4 gigs of memory and a 64-bit processor are met by modern Macs. ➜ Can TrueOS be installed on modern Mac hardware? I do *not* care about dual-booting . I do not care about supporting Apple Boot Camp . I am asking about a simple wipe-the-drive and install only TrueOS operation.

I have installed TrueOS in Virtualbox. Everything is working perfectly. But after I insert virtualbox guest additions, I am unable to find any way to install it. How can I do so? I am using Ubuntu host.

I installed a new instance of TrueOS (a FreeBSD variant) yesterday, and had a USB keyboard plugged in (Logitech G510). It worked fine in the install env, during the first-boot setup, and up until the new instance rebooted. At this point, it seems like it's stopped sending input entirely, starting from when it's recognized during BSD's boot-time module loading phase, because that's when Scroll Lock stops working. However, the LCD screen and backlights are on, and if I plug another keyboard in it tracks status changes (Caps/NumLock, etc.) and it works fine in Windows/Linux and on my laptop. I've tried various combinations of turning on/off Legacy USB and Hand-off in the BIOS, and using different ports, all to no avail. A different USB keyboard ("vendor 0x1241 USB Keyboard" in the logs below) works fine either way. The USB mouse has always worked. There is no PS/2 port. Any idea what's going on here, and how to fix it? Thanks! % dmesg | grep kb kbd1 at kbdmux0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ukbd0 on uhub5 ukbd0: on usbus6 kbd2 at ukbd0 ukbd1 on uhub0 ukbd1: on usbus0 kbd3 at ukbd1 % ll /dev/*kb* crw------- 1 root wheel 0x47 Oct 31 10:46 /dev/atkbd0 lrwxr-xr-x 1 root wheel 6 Oct 31 10:46 /dev/kbd0 -> atkbd0 lrwxr-xr-x 1 root wheel 7 Oct 31 10:46 /dev/kbd1 -> kbdmux0 lrwxr-xr-x 1 root wheel 5 Oct 31 10:46 /dev/kbd2 -> ukbd0 lrwxr-xr-x 1 root wheel 5 Oct 31 10:46 /dev/kbd3 -> ukbd1 crw------- 1 root wheel 0x25 Oct 31 10:46 /dev/kbdmux0 crw------- 1 root wheel 0x62 Oct 31 10:46 /dev/ukbd0 crw------- 1 root wheel 0x6a Oct 31 10:46 /dev/ukbd1

I want to change the hostname that was generated during installation. How do I do that in Trueos?

The keyboard layout was set to us during installation. setxkbmap -query displays layout as us. How to change it to uk?

I'm using TrueOS (FreeBSD12 current) in my hard disk. when it start after installed it. it suggest VESA to install but when i choise the vesa drive the screen changed to white , i rebooted and changed the driver to intel and it done but the backlight dosn't well i think the driver not well. How I can download the suggested driver vesa and use it. I'm using grub2 and dual-booting TrueOS with a arch and fedora. My lspci output in Arch is: $ lspci 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04) 00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation QM77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04) 02:00.0 System peripheral: Ricoh Co Ltd PCIe SDXC/MMC Host Controller (rev 07) 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 [Taylor Peak] (rev 34) i heared that linux driver maybe using , how i can do that.

uname -v gives me the version level of the booted environment. How can I get the version level of an environment without booting that environment? In the example below, a boot environment (BE) is mounted at a temporary path by TrueOS Desktop. I can access relevant parts of the file system but I don't know where to seek the required information: $ date ; uname -v Fri 25 Nov 2016 21:15:19 GMT FreeBSD 12.0-CURRENT #14 1717ae3(drm-next-4.7): Fri Oct 28 13:49:49 UTC 2016 root@gauntlet:/usr/obj/usr/src/sys/GENERIC $ beadm list BE Active Mountpoint Space Created Nickname initial - - 5.4G 2016-08-22 11:24 initial 20161005193649_201610142022 - - 3.1G 2016-10-14 20:22 12.0-CURRENT-up-20161014_204827 20161028134949_201610291803 - - 753.6M 2016-10-29 18:03 12.0-CURRENT-up-20161029_180801 20161028134949_14_201611081710 NR / 45.4G 2016-11-08 17:10 12.0-CURRENT-up-20161108_171012 12.0-CURRENT-up-20161125_173806 - - 7.5G 2016-11-25 17:12 12.0-CURRENT-up-20161125_173806 12.0-CURRENT-up-20161125_201510 - /tmp/BE-12.0-CURRENT-up-20161125_201510.nsZfNFVo 7.4G 2016-11-25 19:49 12.0-CURRENT-up-20161125_201510 $ ls -hl /tmp/BE-12.0-CURRENT-up-20161125_201510.nsZfNFVo total 215 drwxr-xr-x 2 root wheel 48B 25 Nov 19:56 bin drwxr-xr-x 10 root wheel 60B 25 Nov 20:15 boot drwxr-xr-x 3 root wheel 3B 25 Nov 20:02 compat -r--r--r-- 1 root wheel 6.0K 17 Aug 16:12 COPYRIGHT dr-xr-xr-x 2 root wheel 3B 22 Aug 11:31 dev -rw------- 1 root wheel 4.0K 25 Nov 19:48 entropy drwxr-xr-x 30 root wheel 129B 25 Nov 20:15 etc lrwxr-xr-x 1 root wheel 9B 22 Aug 11:35 home -> /usr/home drwxr-xr-x 4 root wheel 59B 25 Nov 19:56 lib drwxr-xr-x 4 root wheel 6B 25 Nov 19:56 libexec drwxr-xr-x 2 root wheel 2B 21 Nov 03:14 media drwxr-xr-x 2 root wheel 2B 8 Oct 12:21 mnt drwxr-xr-x 2 root wheel 2B 22 Aug 12:05 net drwxr-xr-x 2 root wheel 2B 22 Aug 11:25 packages -rw-r--r-- 1 root wheel 21K 25 Nov 20:15 pkg-add.log dr-xr-xr-x 2 root wheel 2B 17 Aug 16:12 proc drwxr-xr-x 2 root wheel 146B 25 Nov 19:56 rescue drwxr-xr-x 10 root wheel 21B 13 Nov 20:13 root drwxr-xr-x 2 root wheel 146B 25 Nov 19:56 sbin lrwxr-xr-x 1 root wheel 11B 17 Aug 16:12 sys -> usr/src/sys drwxr-xr-x 6 root wheel 8B 25 Nov 20:20 tmp drwxr-xr-x 17 root wheel 17B 22 Aug 11:32 usr drwxr-xr-x 28 root wheel 30B 25 Nov 20:11 var $ ### Reference FreeBSD manual page for beadm(1)

Using TrueOS dated 2016-09-20 with Lumina desktop. **How do we adjust the scaling** of the screen resolution? I cannot find any kind of pixel-density settings in any of the control panels. I see no info in the TrueOS Handbook for Lumina configuration . Using TrueOS in a virtual machine (Parallels 12.0.2) on a MacBook Pro with a Retina display . The VM is set to have resolution scaling enabled, yet every thing visible in the Lumina desktop is teeny-tiny.

I am trying TrueOS , the evolution of PC-BSD . I downloaded the 'TrueOS-Desktop-2016-09-09-x64.iso'. When running the installer in Parallels Desktop 12.0.1 virtual machine the main menu for the installer appears, with a few options to choose from. I let that menu expire after about several seconds to auto-boot. I see all the installer scripts reporting to the console. But then the main menu for installer re-appears, deja-vu. Lather, rinse, repeat. The **main menu and installer scripts keep running in a loop**, endlessly. I never get any further than seeing the installer scripts console output fly-by, never see any success in booting the TrueOS environment. Any suggestions?