Newest version of NomadBSD crashes during install

Help Section
1

Well the title states most of what I know, except that I realize my hardware is relatively new. Unfortunately, I fell in love with FreeBSD… The motherboard on the tower computer is an AsusTek Prime Z390-A and the graphics card is an NVIDIA GeForce RTX 2080 Ti. Here is the output that I have:

pciconf -lv

hostb0@pci0:0:0:0: class=0x060000 rev=0x0d hdr=0x00 vendor=0x8086 device=0x3e30 subvendor=0x1043 subdevice=0x8694
vendor = ‘Intel Corporation’
device = ‘8th/9th Gen Core 8-core Desktop Processor Host Bridge/DRAM Registers [Coffee Lake S]’
class = bridge
subclass = HOST-PCI
pcib1@pci0:0:1:0: class=0x060400 rev=0x0d hdr=0x01 vendor=0x8086 device=0x1901 subvendor=0x1043 subdevice=0x8694
vendor = ‘Intel Corporation’
device = ‘6th-10th Gen Core Processor PCIe Controller (x16)’
class = bridge
subclass = PCI-PCI
xhci1@pci0:0:20:0: class=0x0c0330 rev=0x10 hdr=0x00 vendor=0x8086 device=0xa36d subvendor=0x1043 subdevice=0x8694
vendor = ‘Intel Corporation’
device = ‘Cannon Lake PCH USB 3.1 xHCI Host Controller’
class = serial bus
subclass = USB
none0@pci0:0:20:2: class=0x050000 rev=0x10 hdr=0x00 vendor=0x8086 device=0xa36f subvendor=0x1043 subdevice=0x8694
vendor = ‘Intel Corporation’
device = ‘Cannon Lake PCH Shared SRAM’
class = memory
subclass = RAM
none1@pci0:0:22:0: class=0x078000 rev=0x10 hdr=0x00 vendor=0x8086 device=0xa360 subvendor=0x1043 subdevice=0x8694
vendor = ‘Intel Corporation’
device = ‘Cannon Lake PCH HECI Controller’
class = simple comms
ahci0@pci0:0:23:0: class=0x010601 rev=0x10 hdr=0x00 vendor=0x8086 device=0xa352 subvendor=0x1043 subdevice=0x8694
vendor = ‘Intel Corporation’
device = ‘Cannon Lake PCH SATA AHCI Controller’
class = mass storage
subclass = SATA
pcib2@pci0:0:27:0: class=0x060400 rev=0xf0 hdr=0x01 vendor=0x8086 device=0xa340 subvendor=0x1043 subdevice=0x8694
vendor = ‘Intel Corporation’
device = ‘Cannon Lake PCH PCI Express Root Port’
class = bridge
subclass = PCI-PCI
pcib3@pci0:0:27:4: class=0x060400 rev=0xf0 hdr=0x01 vendor=0x8086 device=0xa32c subvendor=0x1043 subdevice=0x8694
vendor = ‘Intel Corporation’
device = ‘Cannon Lake PCH PCI Express Root Port’
class = bridge
subclass = PCI-PCI
pcib4@pci0:0:28:0: class=0x060400 rev=0xf0 hdr=0x01 vendor=0x8086 device=0xa338 subvendor=0x1043 subdevice=0x8694
vendor = ‘Intel Corporation’
device = ‘Cannon Lake PCH PCI Express Root Port’
class = bridge
subclass = PCI-PCI
pcib5@pci0:0:28:7: class=0x060400 rev=0xf0 hdr=0x01 vendor=0x8086 device=0xa33f subvendor=0x1043 subdevice=0x8694
vendor = ‘Intel Corporation’
device = ‘Cannon Lake PCH PCI Express Root Port’
class = bridge
subclass = PCI-PCI
pcib6@pci0:0:29:0: class=0x060400 rev=0xf0 hdr=0x01 vendor=0x8086 device=0xa330 subvendor=0x1043 subdevice=0x8694
vendor = ‘Intel Corporation’
device = ‘Cannon Lake PCH PCI Express Root Port’
class = bridge
subclass = PCI-PCI
isab0@pci0:0:31:0: class=0x060100 rev=0x10 hdr=0x00 vendor=0x8086 device=0xa305 subvendor=0x1043 subdevice=0x8694
vendor = ‘Intel Corporation’
device = ‘Z390 Chipset LPC/eSPI Controller’
class = bridge
subclass = PCI-ISA
hdac1@pci0:0:31:3: class=0x040300 rev=0x10 hdr=0x00 vendor=0x8086 device=0xa348 subvendor=0x1043 subdevice=0x8724
vendor = ‘Intel Corporation’
device = ‘Cannon Lake PCH cAVS’
class = multimedia
subclass = HDA
ichsmb0@pci0:0:31:4: class=0x0c0500 rev=0x10 hdr=0x00 vendor=0x8086 device=0xa323 subvendor=0x1043 subdevice=0x8694
vendor = ‘Intel Corporation’
device = ‘Cannon Lake PCH SMBus Controller’
class = serial bus
subclass = SMBus
none2@pci0:0:31:5: class=0x0c8000 rev=0x10 hdr=0x00 vendor=0x8086 device=0xa324 subvendor=0x1043 subdevice=0x8694
vendor = ‘Intel Corporation’
device = ‘Cannon Lake PCH SPI Controller’
class = serial bus
em0@pci0:0:31:6: class=0x020000 rev=0x10 hdr=0x00 vendor=0x8086 device=0x15bc subvendor=0x1043 subdevice=0x8672
vendor = ‘Intel Corporation’
device = ‘Ethernet Connection (7) I219-V’
class = network
subclass = ethernet
vgapci0@pci0:1:0:0: class=0x030000 rev=0xa1 hdr=0x00 vendor=0x10de device=0x1e04 subvendor=0x1043 subdevice=0x86e5
vendor = ‘NVIDIA Corporation’
device = ‘TU102 [GeForce RTX 2080 Ti]’
class = display
subclass = VGA
hdac0@pci0:1:0:1: class=0x040300 rev=0xa1 hdr=0x00 vendor=0x10de device=0x10f7 subvendor=0x1043 subdevice=0x86e5
vendor = ‘NVIDIA Corporation’
device = ‘TU102 High Definition Audio Controller’
class = multimedia
subclass = HDA
xhci0@pci0:1:0:2: class=0x0c0330 rev=0xa1 hdr=0x00 vendor=0x10de device=0x1ad6 subvendor=0x1043 subdevice=0x86e5
vendor = ‘NVIDIA Corporation’
device = ‘TU102 USB 3.1 Host Controller’
class = serial bus
subclass = USB
none3@pci0:1:0:3: class=0x0c8000 rev=0xa1 hdr=0x00 vendor=0x10de device=0x1ad7 subvendor=0x1043 subdevice=0x86e5
vendor = ‘NVIDIA Corporation’
device = ‘TU102 USB Type-C UCSI Controller’
class = serial bus
nvme0@pci0:3:0:0: class=0x010802 rev=0x01 hdr=0x00 vendor=0xc0a9 device=0x540a subvendor=0xc0a9 subdevice=0x540a
vendor = ‘Micron/Crucial Technology’
device = ‘P2 NVMe PCIe SSD’
class = mass storage
subclass = NVM
iwm0@pci0:5:0:0: class=0x028000 rev=0x78 hdr=0x00 vendor=0x8086 device=0x24fd subvendor=0x8086 subdevice=0x1010
vendor = ‘Intel Corporation’
device = ‘Wireless 8265 / 8275’
class = network
nvme1@pci0:6:0:0: class=0x010802 rev=0x03 hdr=0x00 vendor=0x2646 device=0x2263 subvendor=0x2646 subdevice=0x2263
vendor = ‘Kingston Technology Company, Inc.’
device = ‘A2000 NVMe SSD’
class = mass storage
subclass = NVM

I suspect that the problem is with the Nvidia drivers, but there is also an experimental driver for a USB drawing pad that I load at boot. There is also some hardware without drivers, but that doesn’t seem to have anything to do with the immediate problem, so… any ideas?

***Side notes:

  1. When the desktop computer crashes, it sometimes takes a couple of days of “rest” that is needed before I can successfully boot any system from it again.
  2. I have considered completely reformatting the M.2 drives (including the boot loader area - ESP and /boot (?), but am not sure how to do that from the NomadBSD USB, or if the task can be completed before the computer crashes again…
2

I managed to get NomadBSD installed on my desktop computer, but it is too early to tell regarding the Nvidia drivers. What I did was to reject loading the experimental driver (iichid driver for 12c HID devices) that I get prompted for, which actually appears to be for my Logitch trackball, and not my drawing pad as it currently plugged in. I have also set the display settings blanktime to 70, 81 and 92, but it doesn’t seem to persist despite saving, so that probably doesn’t have anything to do with things… I will have to wait and see how things go with my new daily driver…

As it appears at this time, I think that the display power settings are to blame. It would however, also be useful if the iichid driver for 12c HID devices could be prevented from loading, as the prompt at boot as to whether to use it or not is very tiresome.

3

I just found that there was a line in /etc/rc.conf where load_iichid_enable=“NO” could be set.

1 Like
4

I experienced three unrecoverable crashes today on my tower computer with nvidia-driver and nvidia-xconfig installed. Interestingly, the Nvidia splash screen that is supposed to come on at boot time never came on, and there was no menu item even after a menu refresh and reboot. I will try a low level erase of my M.2 drive with Active@ KillDisk tomorrow and try reinstalling NomadBSD for the third time to see if I can get it running FreeBSD, but it isn’t looking good at the moment. Should @vladas see this, my computer is an ARTLINE-9745E0U, which is a locally produced brand that most people probably wouldn’t recognize…

I just discovered that another SSD is fried and I am not sure whether I want to spend more money on purchasing SSD’s for this computer. Best to end this post now without a solution…

5

Sorry, I am a simple desktop user, refugee from MS Windows, still newbie in NomadBSD, with neither programmer nor sysadmin experience. I turned Nvidia on thanks to @mk1 last year:

2 Likes