If the install fails, the "Installation Failed" screen is shown. The text on the second line is not readable in vesa mode. The font is too big and/or the text is too long.

During the installation, if I exit to the shell (for example, to work on disk partitioning), I can't find how to return to the installation. I can't find a trident-install program. I see bsdinstall, but that's not it. From the processes running, it looks like the installation program is exited when going to the shell, so exiting the shell doesn't automatically return to the installer.

p.s. this is not specific to RC2. It happened a month ago, too. I think that was BETA3.

Multiple attempts to configure fresh full disk installation with Swap partition led the overall installation failure. Several values for Swap partition were tested: 520 MB, 1024 MB, 2055 MB. The log indicates the ZFS import trident showing exit error code 1.

pc-sysinstall.log log error message:

cannot import 'trident': invalid vdev configuration

EXITERROR: Error 1: zpool -f -N trident

(Waiting for #47 to generate the corresponding logs.)

Using: Trident-x64-20180831.iso

Downloaded and copied (via dd) to USB thumbdrive.
Booted OK on Lenovo T530 as da0
Installed OK on da1, a USB harddrive (Toshiba USB 3.0)
On reboot, selected Toshiba USB from boot menu
"Missing boot loader"

During the install phase, would it possible to get input for the WiFi we are using.

To at least create the /etc/wpa_supplicant, makes first easier to being on the network

And add the ability to add default route as well.

This is a nicety, not a necessity.

platform lenovo t530, 18.12-PRERELEASE 2018.12.07

on an initial install, checking the "VirtualBox" application does not actually install the VirtualBox package. it installs the "virtualbox-ose-additions" package, which aren't really useful without the "virtualbox-ose" package itself.

If I write the new Trident-x64-TOS-19.07-20190710 installer .iso for an DVD than the installer can't find my HDD and my SSD, when I have to choose the target drives (after the time zone and hostname) or the target partitions of the new system the list is empty. This error already was earlier and solved.
Now if I open a terminal (from the installer) to partitioning and I'm exiting from this terminal than the "Installation is ready - Reboot or Live CD" blue screen come up again.

If I write the installer .iso for an USB key with dd command (block size 1M) than I can choose the target drives and I can make a fresh install, but in the newly installed system all the keyboard layout are empty,I can use my keyboard only with the default US layout.

Interesting the two different behavior of the intaller .iso (in the case of DVD or USB key) maybe the block size can cause this, I will try to write with different block sizes.

I have problems booting my usb drive on uefi with this error:

on laptop:
Model: Lenovo ideapad 310s-15abr 80st
System: Dual-boot linux(Antergos) and windows 10 on another hdd
HDD1: 2x WD Blue 1TB
CPU: AMD A10 9600p
GPU: Radeon R5 iGPU
RAM: 8 GB DDR4(2x4GB)
USB: USB thumb with USB3.0 16GB
Any solutions??

Original post about this issue can be viewed here:

https://discourse.trueos.org/t/first-attempt-to-install-trident/3493

Info from my laptop.

pciconf -lv:

hostb0@pci0:0:0:0: class=0x060000 card=0x040b1028 chip=0x00448086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = 'Core Processor DRAM Controller'
class = bridge
subclass = HOST-PCI
vgapci0@pci0:0:2:0: class=0x030000 card=0x040b1028 chip=0x00468086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = 'Core Processor Integrated Graphics Controller'
class = display
subclass = VGA
em0@pci0:0:25:0: class=0x020000 card=0x040b1028 chip=0x10ea8086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '82577LM Gigabit Network Connection'
class = network
subclass = ethernet
ehci0@pci0:0:26:0: class=0x0c0320 card=0x040b1028 chip=0x3b3c8086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '5 Series/3400 Series Chipset USB2 Enhanced Host Controller'
class = serial bus
subclass = USB
hdac0@pci0:0:27:0: class=0x040300 card=0x040b1028 chip=0x3b568086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '5 Series/3400 Series Chipset High Definition Audio'
class = multimedia
subclass = HDA
pcib1@pci0:0:28:0: class=0x060400 card=0x040b1028 chip=0x3b428086 rev=0x05 hdr=0x01
vendor = 'Intel Corporation'
device = '5 Series/3400 Series Chipset PCI Express Root Port 1'
class = bridge
subclass = PCI-PCI
pcib2@pci0:0:28:1: class=0x060400 card=0x040b1028 chip=0x3b448086 rev=0x05 hdr=0x01
vendor = 'Intel Corporation'
device = '5 Series/3400 Series Chipset PCI Express Root Port 2'
class = bridge
subclass = PCI-PCI
pcib3@pci0:0:28:2: class=0x060400 card=0x040b1028 chip=0x3b468086 rev=0x05 hdr=0x01
vendor = 'Intel Corporation'
device = '5 Series/3400 Series Chipset PCI Express Root Port 3'
class = bridge
subclass = PCI-PCI
pcib4@pci0:0:28:3: class=0x060400 card=0x040b1028 chip=0x3b488086 rev=0x05 hdr=0x01
vendor = 'Intel Corporation'
device = '5 Series/3400 Series Chipset PCI Express Root Port 4'
class = bridge
subclass = PCI-PCI
ehci1@pci0:0:29:0: class=0x0c0320 card=0x040b1028 chip=0x3b348086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '5 Series/3400 Series Chipset USB2 Enhanced Host Controller'
class = serial bus
subclass = USB
pcib5@pci0:0:30:0: class=0x060401 card=0x040b1028 chip=0x24488086 rev=0xa5 hdr=0x01
vendor = 'Intel Corporation'
device = '82801 Mobile PCI Bridge'
class = bridge
subclass = PCI-PCI
isab0@pci0:0:31:0: class=0x060100 card=0x040b1028 chip=0x3b078086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = 'QM57 Chipset LPC Interface Controller'
class = bridge
subclass = PCI-ISA
atapci0@pci0:0:31:2: class=0x01018f card=0x040b1028 chip=0x3b2e8086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '5 Series/3400 Series Chipset 4 port SATA IDE Controller'
class = mass storage
subclass = ATA
none0@pci0:0:31:3: class=0x0c0500 card=0x040b1028 chip=0x3b308086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '5 Series/3400 Series Chipset SMBus Controller'
class = serial bus
subclass = SMBus
atapci1@pci0:0:31:5: class=0x010185 card=0x040b1028 chip=0x3b2d8086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '5 Series/3400 Series Chipset 2 port SATA IDE Controller'
class = mass storage
subclass = ATA
none1@pci0:0:31:6: class=0x118000 card=0x040b1028 chip=0x3b328086 rev=0x05 hdr=0x00
vendor = 'Intel Corporation'
device = '5 Series/3400 Series Chipset Thermal Subsystem'
class = dasp
iwn0@pci0:2:0:0: class=0x028000 card=0x13218086 chip=0x422c8086 rev=0x35 hdr=0x00
vendor = 'Intel Corporation'
device = 'Centrino Advanced-N 6200'
class = network
cbb0@pci0:3:0:0: class=0x060700 card=0x040b1028 chip=0xe4761180 rev=0x02 hdr=0x02
vendor = 'Ricoh Co Ltd'
device = 'CardBus bridge'
class = bridge
subclass = PCI-CardBus
sdhci_pci0@pci0:3:0:1: class=0x080501 card=0x040b1028 chip=0xe8221180 rev=0x03 hdr=0x00
vendor = 'Ricoh Co Ltd'
device = 'MMC/SD Host Controller'
class = base peripheral
subclass = SD host controller
none2@pci0:3:0:4: class=0x0c0010 card=0x040b1028 chip=0xe8321180 rev=0x03 hdr=0x00
vendor = 'Ricoh Co Ltd'
device = 'R5C832 PCIe IEEE 1394 Controller'
class = serial bus
subclass = FireWire
hostb1@pci0:63:0:0: class=0x060000 card=0x80868086 chip=0x2c628086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = 'Core Processor QuickPath Architecture Generic Non-core Registers'
class = bridge
subclass = HOST-PCI
hostb2@pci0:63:0:1: class=0x060000 card=0x80868086 chip=0x2d018086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = 'Core Processor QuickPath Architecture System Address Decoder'
class = bridge
subclass = HOST-PCI
hostb3@pci0:63:2:0: class=0x060000 card=0x80868086 chip=0x2d108086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = 'Core Processor QPI Link 0'
class = bridge
subclass = HOST-PCI
hostb4@pci0:63:2:1: class=0x060000 card=0x80868086 chip=0x2d118086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '1st Generation Core i3/5/7 Processor QPI Physical 0'
class = bridge
subclass = HOST-PCI
hostb5@pci0:63:2:2: class=0x060000 card=0x80868086 chip=0x2d128086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '1st Generation Core i3/5/7 Processor Reserved'
class = bridge
subclass = HOST-PCI
hostb6@pci0:63:2:3: class=0x060000 card=0x80868086 chip=0x2d138086 rev=0x02 hdr=0x00
vendor = 'Intel Corporation'
device = '1st Generation Core i3/5/7 Processor Reserved'
class = bridge
subclass = HOST-PCI

dmidecode:

dmidecode 3.1

Scanning /dev/mem for entry point.
SMBIOS 2.6 present.
67 structures occupying 3618 bytes.
Table at 0x000F4050.

Handle 0xDA00, DMI type 218, 251 bytes
OEM-specific Type
Header and Data:
DA FB 00 DA B2 00 37 1F 1F 32 40 87 01 87 01 00
00 88 01 88 01 01 00 7D 00 7D 00 FF FF 05 00 05
00 03 00 06 00 06 00 05 00 0F 00 0F 00 00 00 11
00 11 00 02 00 12 00 12 00 04 00 28 00 28 00 00
00 29 00 29 00 01 00 2A 00 2A 00 02 00 2D 00 2D
00 02 00 2E 00 2E 00 00 00 6E 00 6E 00 01 00 42
00 42 00 01 00 43 00 43 00 00 00 6E 02 6E 02 00
00 33 02 33 02 01 00 32 02 32 02 02 00 4A 01 4A
01 00 00 4B 01 4B 01 01 00 44 01 44 01 00 00 45
01 45 01 01 00 EA 00 EA 00 00 00 EB 00 EB 00 01
00 EC 00 EC 00 02 00 07 00 07 00 00 00 0B 00 0B
00 01 00 0C 00 0C 00 02 00 0D 00 0D 00 03 00 35
01 35 01 FF 00 37 01 37 01 00 00 38 01 38 01 01
00 39 01 39 01 02 00 02 02 02 02 00 00 03 02 03
02 01 00 04 02 04 02 00 00 05 02 05 02 01 00 2B
00 2B 00 FF FF FF FF 00 00 00 00

Handle 0xDA01, DMI type 218, 251 bytes
OEM-specific Type
Header and Data:
DA FB 01 DA B2 00 37 1F 1F 32 40 2C 00 2C 00 FF
FF 55 00 55 00 00 00 6D 00 6D 00 05 00 98 01 98
01 04 00 16 02 16 02 06 00 A1 00 A1 00 00 00 A3
00 A3 00 01 00 46 01 46 01 00 00 47 01 47 01 01
00 28 02 28 02 02 00 29 02 29 02 01 00 2F 02 2F
02 01 00 30 02 30 02 00 00 0E 01 0E 01 01 00 0F
01 0F 01 00 00 10 01 10 01 01 00 11 01 11 01 00
00 F1 00 F1 00 00 00 F2 00 F2 00 01 00 F3 00 F3
00 02 00 9B 00 9B 00 01 00 9C 00 9C 00 00 00 65
00 65 00 00 00 66 00 66 00 01 00 0A 01 0A 01 01
00 0B 01 0B 01 00 00 D9 01 D9 01 01 00 D8 01 D8
01 00 00 90 01 90 01 01 00 8F 01 8F 01 00 00 95
00 95 00 01 00 96 00 96 00 00 00 94 02 94 02 01
00 95 02 95 02 00 00 89 01 89 01 00 00 8A 01 8A
01 01 00 DE 01 DE 01 00 00 DF 01 DF 01 01 00 44
02 44 02 01 00 FF FF 00 00 00 00

Handle 0xDA02, DMI type 218, 251 bytes
OEM-specific Type
Header and Data:
DA FB 02 DA B2 00 37 1F 1F 32 40 45 02 45 02 00
00 83 01 83 01 00 00 84 01 84 01 01 00 85 02 85
02 01 00 86 02 86 02 00 00 85 01 85 01 00 00 86
01 86 01 01 00 81 01 81 01 00 00 82 01 82 01 01
00 7F 01 7F 01 00 00 80 01 80 01 01 00 7B 01 7B
01 00 00 7C 01 7C 01 01 00 52 01 52 01 01 00 53
01 53 01 00 00 B4 02 B4 02 01 00 B5 02 B5 02 00
00 93 01 93 01 00 00 94 01 94 01 01 00 9B 01 9B
01 00 00 9C 01 9C 01 01 00 9F 00 9F 00 00 00 A0
00 A0 00 01 00 A5 02 A5 02 01 00 A6 02 A6 02 00
00 92 02 92 02 01 00 93 02 93 02 00 00 BD 02 BD
02 01 00 BE 02 BE 02 00 00 A7 02 A7 02 01 00 A8
02 A8 02 00 00 D9 02 D9 02 FF FF DB 02 DB 02 FF
FF D8 02 D8 02 FF FF DA 02 DA 02 FF FF DD 02 DD
02 FF FF DF 02 DF 02 FF FF DC 02 DC 02 FF FF DE
02 DE 02 FF FF FF FF 00 00 00 00

Handle 0xDA03, DMI type 218, 251 bytes
OEM-specific Type
Header and Data:
DA FB 03 DA B2 00 37 1F 1F 32 40 E0 02 E0 02 01
00 E1 02 E1 02 02 00 E2 02 E2 02 00 00 41 01 41
01 01 00 40 01 40 01 00 00 D1 00 D1 00 01 00 D2
00 D2 00 00 00 F0 00 F0 00 01 00 ED 00 ED 00 00
00 EB 01 EB 01 01 00 EA 01 EA 01 00 00 75 01 75
01 02 00 76 01 76 01 01 00 25 03 25 03 01 00 5C
00 5C 00 01 00 5D 00 5D 00 00 00 2D 01 2D 01 01
00 2E 01 2E 01 00 00 4A 02 4A 02 01 00 0C 80 0C
80 00 00 04 A0 04 A0 01 00 40 00 40 00 01 00 41
00 41 00 00 00 B1 02 B1 02 01 00 B2 02 B2 02 00
00 8C 02 8C 02 01 00 8D 02 8D 02 00 00 59 02 59
02 01 00 5A 02 5A 02 00 00 01 F0 01 F0 55 00 03
F0 03 F0 03 00 06 F0 06 F0 7F 00 07 F0 07 F0 00
00 64 02 64 02 01 00 65 02 65 02 00 00 66 02 66
02 01 00 67 02 67 02 00 00 68 02 68 02 01 00 69
02 69 02 00 00 FF FF 00 00 00 00

Handle 0xDA04, DMI type 218, 29 bytes
OEM-specific Type
Header and Data:
DA 1D 04 DA B2 00 37 1F 1F 32 40 6C 02 6C 02 01
00 6D 02 6D 02 00 00 FF FF 00 00 00 00

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: A17
Release Date: 05/12/2017
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 1024 kB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
LS-120 boot is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Targeted content distribution is supported
BIOS Revision: 4.6

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: Latitude E6510
Version: 0001
Serial Number: J7NG0M1
UUID: 4C4C4544-0037-4E10-8047-CAC04F304D31
Wake-up Type: Power Switch
SKU Number:
Family: Not Specified

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
Manufacturer: Dell Inc.
Product Name: 02K3Y4
Version: A00
Serial Number: /J7NG0M1/CN1296105T4918/
Asset Tag:
Features:
Board is a hosting board
Board is replaceable
Location In Chassis: Not Specified
Chassis Handle: 0x0003
Type: Motherboard
Contained Object Handles: 0

Handle 0x0003, DMI type 3, 21 bytes
Chassis Information
Manufacturer: Dell Inc.
Type: Laptop
Lock: Not Present
Version:
Serial Number: J7NG0M1
Asset Tag: Not Specified
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000000
Height: Unspecified
Number Of Power Cords: 1
Contained Elements: 0

Handle 0x0004, DMI type 4, 42 bytes
Processor Information
Socket Designation: CPU 1
Type: Central Processor
Family: Core i7
Manufacturer: Intel
ID: 52 06 02 00 FF FB EB BF
Signature: Type 0, Family 6, Model 37, Stepping 2
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Intel(R) Core(TM) i5 CPU M 520 @ 2.40GH
Voltage: 0.0 V
External Clock: 533 MHz
Max Speed: 4000 MHz
Current Speed: 2399 MHz
Status: Populated, Enabled
Upgrade: Other
L1 Cache Handle: 0x0005
L2 Cache Handle: 0x0006
L3 Cache Handle: 0x0007
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Part Number: To Be Filled By O.E.M.
Core Count: 2
Core Enabled: 1
Thread Count: 2
Characteristics:
64-bit capable

Handle 0x0005, DMI type 7, 19 bytes
Cache Information
Socket Designation: L1-Cache
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 32 kB
Maximum Size: 32 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: None
System Type: Unified
Associativity: 4-way Set-associative

Handle 0x0006, DMI type 7, 19 bytes
Cache Information
Socket Designation: L2-Cache
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Varies With Memory Address
Location: Internal
Installed Size: 512 kB
Maximum Size: 512 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: None
System Type: Unified
Associativity: 8-way Set-associative

Handle 0x0007, DMI type 7, 19 bytes
Cache Information
Socket Designation: L3-Cache
Configuration: Enabled, Not Socketed, Level 3
Operational Mode: Varies With Memory Address
Location: Internal
Installed Size: 3072 kB
Maximum Size: 3072 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: None
System Type: Unified
Associativity: Other

Handle 0x0008, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: PARALLEL
Internal Connector Type: None
External Reference Designator: Keyboard
External Connector Type: DB-25 female
Port Type: Parallel Port PS/2

Handle 0x0009, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SERIAL1
Internal Connector Type: None
External Reference Designator: Serial Port
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible

Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB
Internal Connector Type: None
External Reference Designator: USB
External Connector Type: Access Bus (USB)
Port Type: USB

Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MONITOR
Internal Connector Type: None
External Reference Designator: Video
External Connector Type: DB-15 female
Port Type: Video Port

Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: FireWire
Internal Connector Type: None
External Reference Designator: 1394
External Connector Type: IEEE 1394
Port Type: Firewire (IEEE P1394)

Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Modem
Internal Connector Type: None
External Reference Designator: Modem
External Connector Type: RJ-11
Port Type: Modem Port

Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: Ethernet
Internal Connector Type: None
External Reference Designator: LAN
External Connector Type: RJ-45
Port Type: Network Port

Handle 0x000F, DMI type 9, 17 bytes
System Slot Information
Designation: J5C1
Type: x16 PCI Express x16
Current Usage: Available
Length: Long
ID: 1
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:ff:00.0

Handle 0x0010, DMI type 9, 17 bytes
System Slot Information
Designation: J6C2
Type: x1 PCI Express
Current Usage: Available
Length: Short
ID: 2
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:01:00.0

Handle 0x0011, DMI type 9, 17 bytes
System Slot Information
Designation: J6D2
Type: x1 PCI Express
Current Usage: In Use
Length: Short
ID: 3
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:02:00.0

Handle 0x0012, DMI type 9, 17 bytes
System Slot Information
Designation: J7C1
Type: x1 PCI Express
Current Usage: In Use
Length: Short
ID: 4
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:03:00.0

Handle 0x0013, DMI type 9, 17 bytes
System Slot Information
Designation: J7D2
Type: x1 PCI Express
Current Usage: Available
Length: Short
ID: 5
Characteristics:
3.3 V is provided
Opening is shared
PME signal is supported
Bus Address: 0000:05:00.0

Handle 0x0014, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Disabled
Description: "Intel GM45 Graphics"

Handle 0x0015, DMI type 10, 6 bytes
On Board Device Information
Type: Ethernet
Status: Enabled
Description: NETWORK_NAME_STRING

Handle 0x0016, DMI type 11, 5 bytes
OEM Strings
String 1: Dell System
String 2: 1[040B]
String 3: 3[1.0]
String 4: 12[www.dell.com]

Handle 0x0017, DMI type 12, 5 bytes
System Configuration Options
Option 1: To Be Filled By O.E.M.

Handle 0x0018, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1

Handle 0x0019, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 8 GB
Error Information Handle: 0x001A
Number Of Devices: 2

Handle 0x001A, DMI type 18, 23 bytes
32-bit Memory Error Information
Type: Unknown
Granularity: Unknown
Operation: Unknown
Vendor Syndrome: Unknown
Memory Array Address: Unknown
Device Address: Unknown
Resolution: Unknown

Handle 0x001B, DMI type 17, 28 bytes
Memory Device
Array Handle: 0x0019
Error Information Handle: 0x001D
Total Width: 64 bits
Data Width: 64 bits
Size: 4096 MB
Form Factor: SODIMM
Set: None
Locator: DIMM_A
Bank Locator: BANK 0
Type: DDR3
Type Detail: Synchronous
Speed: 1067 MT/s
Manufacturer: 029E
Serial Number: 00000000
Asset Tag: Unknown
Part Number: CMSA4GX3M1A1066C7
Rank: Unknown

Handle 0x001C, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FFFFFFFF
Range Size: 4 GB
Physical Device Handle: 0x001B
Memory Array Mapped Address Handle: 0x0021
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1

Handle 0x001D, DMI type 18, 23 bytes
32-bit Memory Error Information
Type: Unknown
Granularity: Unknown
Operation: Unknown
Vendor Syndrome: Unknown
Memory Array Address: Unknown
Device Address: Unknown
Resolution: Unknown

Handle 0x001E, DMI type 17, 28 bytes
Memory Device
Array Handle: 0x0019
Error Information Handle: No Error
Total Width: 64 bits
Data Width: 64 bits
Size: 4096 MB
Form Factor: SODIMM
Set: None
Locator: DIMM_B
Bank Locator: BANK 2
Type: DDR3
Type Detail: Synchronous
Speed: 1067 MT/s
Manufacturer: 029E
Serial Number: 00000000
Asset Tag: Unknown
Part Number: CMSA4GX3M1A1066C7
Rank: Unknown

Handle 0x001F, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FFFFFFFF
Range Size: 4 GB
Physical Device Handle: 0x001E
Memory Array Mapped Address Handle: 0x0021
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1

Handle 0x0020, DMI type 18, 23 bytes
32-bit Memory Error Information
Type: Unknown
Granularity: Unknown
Operation: Unknown
Vendor Syndrome: Unknown
Memory Array Address: Unknown
Device Address: Unknown
Resolution: Unknown

Handle 0x0021, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x001FFFFFFFF
Range Size: 8 GB
Physical Array Handle: 0x0019
Partition Width: 4

Handle 0x0022, DMI type 21, 7 bytes
Built-in Pointing Device
Type: Touch Pad
Interface: Bus Mouse
Buttons: 2

Handle 0x0023, DMI type 22, 26 bytes
Portable Battery
Location: Sys. Battery Bay
Manufacturer: Samsung SDI
Manufacture Date: 7/12/2014
Serial Number: 0113
Name: DELL PT43699
Design Capacity: 87000 mWh
Design Voltage: 11100 mV
SBDS Version: 1.0
Maximum Error: 2%
SBDS Chemistry: LION
OEM-specific Information: 0x00000001

Handle 0x0024, DMI type 126, 26 bytes
Inactive

Handle 0x0025, DMI type 32, 20 bytes
System Boot Information
Status: No errors detected

Handle 0x0026, DMI type 34, 11 bytes
Management Device
Description: LM78-1
Type: LM78
Address: 0x00000000
Address Type: I/O Port

Handle 0x0027, DMI type 26, 22 bytes
Voltage Probe
Description: LM78A
Location: Unknown
Status: Unknown
Maximum Value: Unknown
Minimum Value: Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown
OEM-specific Information: 0x00000000
Nominal Value: Unknown

Handle 0x002A, DMI type 29, 22 bytes
Electrical Current Probe
Description: ABC
Location: Unknown
Status: Unknown
Maximum Value: Unknown
Minimum Value: Unknown
Resolution: Unknown
Tolerance: Unknown
Accuracy: Unknown
OEM-specific Information: 0x00000000
Nominal Value: Unknown

Handle 0x002B, DMI type 39, 22 bytes
System Power Supply
Power Unit Group: 1
Location: To Be Filled By O.E.M.
Name: To Be Filled By O.E.M.
Manufacturer: To Be Filled By O.E.M.
Serial Number: To Be Filled By O.E.M.
Asset Tag: To Be Filled By O.E.M.
Model Part Number: To Be Filled By O.E.M.
Revision: To Be Filled By O.E.M.
Max Power Capacity: Unknown
Status: Present, Unknown
Type: Unknown
Input Voltage Range Switching: Unknown
Plugged: Yes
Hot Replaceable: No
Input Voltage Probe Handle: 0x0027
Cooling Device Handle: 0x1B00
Input Current Probe Handle: 0x002A

Handle 0x002C, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard IGD
Type: Video
Status: Disabled
Type Instance: 1
Bus Address: 0000:00:02.0

Handle 0x002D, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard LAN
Type: Ethernet
Status: Enabled
Type Instance: 1
Bus Address: 0000:00:19.0

Handle 0x002E, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard Audio
Type: Sound
Status: Disabled
Type Instance: 1
Bus Address: 0000:08:1b.0

Handle 0x1B00, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD00

Handle 0x1C00, DMI type 28, 20 bytes
Temperature Probe
Description: CPU Internal Temperature
Location: Processor
Status: OK
Maximum Value: 127.0 deg C
Minimum Value: 0.0 deg C
Resolution: 1.000 deg C
Tolerance: 0.5 deg C
Accuracy: Unknown
OEM-specific Information: 0x0000DC00

Handle 0xB100, DMI type 177, 12 bytes
OEM-specific Type
Header and Data:
B1 0C 00 B1 02 00 00 00 00 00 00 00

Handle 0xB200, DMI type 178, 92 bytes
OEM-specific Type
Header and Data:
B2 5C 00 B2 07 01 0C 00 08 01 0A 00 09 01 0B 00
0A 01 12 00 3B 00 20 00 3C 00 1F 00 3D 00 0E 00
41 00 12 00 42 00 18 00 4B 00 15 00 48 00 14 00
50 00 13 00 10 00 FF 00 11 00 FF 00 12 00 FF 00
13 00 FF 00 14 00 FF 00 1E 00 FF 00 1F 00 FF 00
20 00 FF 00 21 00 FF 00 22 00 FF 00

Handle 0xD000, DMI type 208, 16 bytes
OEM-specific Type
Header and Data:
D0 10 00 D0 02 05 FE 00 0B 04 01 02 00 00 00 00
Strings:
20100528
20100719

Handle 0xD100, DMI type 209, 12 bytes
OEM-specific Type
Header and Data:
D1 0C 00 D1 00 00 00 03 04 0F 80 04

Handle 0xD200, DMI type 210, 12 bytes
OEM-specific Type
Header and Data:
D2 0C 00 D2 00 00 00 03 06 80 04 04

Handle 0xD800, DMI type 216, 9 bytes
OEM-specific Type
Header and Data:
D8 09 00 D8 01 02 01 10 01
Strings:
Intel Corp.
2120v28

Handle 0xD900, DMI type 217, 8 bytes
OEM-specific Type
Header and Data:
D9 08 00 D9 01 02 01 03
Strings:
US-101
Proprietary

Handle 0xDB00, DMI type 219, 11 bytes
OEM-specific Type
Header and Data:
DB 0B 00 DB 03 01 02 03 00 00 00
Strings:
System Device Bay
CD-ROM, CD-RW, DVD, DVD+RW, DVD+/-RW, Hard Disk
DVD+/-RW

Handle 0xDB01, DMI type 219, 11 bytes
OEM-specific Type
Header and Data:
DB 0B 01 DB 03 01 02 03 00 00 00
Strings:
System eSATA Bay
CD-ROM, CD-RW, DVD, DVD+RW, DVD+/-RW, Hard Disk
EMPTY

Handle 0xDB02, DMI type 219, 11 bytes
OEM-specific Type
Header and Data:
DB 0B 02 DB 03 01 02 03 00 00 00
Strings:
System eSATA Dock Bay
CD-ROM, CD-RW, DVD, DVD+RW, DVD+/-RW, Hard Disk
EMPTY

Handle 0xDB03, DMI type 219, 11 bytes
OEM-specific Type
Header and Data:
DB 0B 03 DB 03 01 02 03 00 00 00
Strings:
MiniCard SSD
Hard Disk
EMPTY

Handle 0xDC00, DMI type 220, 20 bytes
OEM-specific Type
Header and Data:
DC 14 00 DC 01 F0 00 00 03 F0 00 00 00 00 06 F0
07 F0 00 00

Handle 0xDD00, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 00 DD 00 00 00 00 00 03 00 00 00 00 00 00
00 00 00

Handle 0xDE00, DMI type 222, 16 bytes
OEM-specific Type
Header and Data:
DE 10 00 DE 01 04 FF FF 00 00 00 00 00 01 00 00

Handle 0xDE01, DMI type 127, 4 bytes
End Of Table

Finally, my working xorg.conf from my laptop running 12.0-CURRENT FreeBSD 12.0-CURRENT #26 fa797a5a3(trueos-stable-18.03): Mon Mar 26 00:24:47 UTC 2018 root@chimera:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64:

XFree86 configuration file for RoFreeSBIE

Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
EndSection

Section "Files"
ModulePath "/usr/local/lib/modules"
ModulePath "/usr/local/lib/xorg/modules"
FontPath "/usr/local/share/fonts/cyrillic/"
FontPath "/usr/local/share/fonts/TrueType/"
FontPath "/usr/local/share/fonts/illinoy/"
FontPath "/usr/local/share/fonts/webfonts/"
FontPath "/usr/local/share/fonts/misc/"
FontPath "/usr/local/share/fonts/TTF/"
FontPath "/usr/local/share/fonts/Speedo/"
FontPath "/usr/local/share/fonts/Type1/"
FontPath "/usr/local/share/fonts/CID/"
FontPath "/usr/local/share/fonts/75dpi/"
FontPath "/usr/local/share/fonts/100dpi/"
FontPath "/usr/local/share/fonts/dejavu/"
FontPath "/usr/local/share/fonts/cyrillic/"
FontPath "/usr/local/share/fonts/hebrew/"
FontPath "/usr/local/share/fonts/vietnamese/"
FontPath "/usr/local/share/fonts/indic/"
FontPath "/usr/local/share/fonts/fonts-indic/"
FontPath "/usr/local/share/fonts/ae_fonts1/AAHS"
FontPath "/usr/local/share/fonts/ae_fonts1/AGA"
FontPath "/usr/local/share/fonts/ae_fonts1/FS"
FontPath "/usr/local/share/fonts/ae_fonts1/Kasr"
FontPath "/usr/local/share/fonts/ae_fonts1/MCS"
FontPath "/usr/local/share/fonts/ae_fonts1/Shmookh"
FontPath "/usr/local/share/fonts/local/"
EndSection

Section "Module"
Load "extmod"
Load "record"
Load "dbe"
Load "glx"
Load "dri"
Load "dri2"
EndSection

Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"

DefaultDepth 16

EndSection

Section "Device"
Identifier "Card0"
Driver "intel"
BusID "0:2:0"
EndSection

Verify that an install to a full, single disk works properly

• VirtualBox VM is a good test of this

I get the following error when I try to install project trident on my laptop:

I used the "stable" ISO. X crashes and the system sits there and does nothing. After an hour I then hit ctrl-c and it then told me the installation was complete. Obviously it wasn't, but the ctrl-c ended the launch script so I guess it assumed things went well.
I have an Intel 7th gen CPU and an Nvidia RTX card.
Most peculiarly, it worked A-Ok on my thinkpad with intel graphics and it worked A-Ok in virtualbox.

Possible nvidia bug?

platform lenovo t530, 18.12-PRERELEASE 2018-12-07 fresh install

the llvm60-6.0.1_3 compiler is installed during a fresh installation but the compiler is not immediately usable until

compiler-bootstrap llvm60

is run to set up the missing links. probably should add that to the overlay.

jpb

Is there any chance you will support btrfs on your installer for the void version?

Problem 1 - missing header files.

the default install of llvm60 is missing the "*.h" include files that should populate /usr/include. as a result, a test compile of a "hello world" program will fail to find the standard include files.
to recreate:

1. run compiler-bootstrap llvm60
2. create a "hello world" program (t.c):

#include <stdio.h>
int main()
{
  printf("hello world!\n");
  return(0);
}

3. compile with -v:
   cc -v t.c

the compile fails with clang failing to find stdio.h reading the output, the "#include ..." lines show where the toolchain will look for includes. there are two:

/usr/local/llvm60/lib/clang/6.0.1/include
/usr/include

neither one of these contains standard C program header files (stdio.h, ctype.h, etc.) all of those "*.h" files are missing.

Problem 2 - missing libraries
Copying the "*.h" files into /usr/include allows the compile to proceed. however, the linker abends as it cannot find some required libraries:

-lgcc
-lgcc_s
-lc

examining the output of cc -v t.c notes that the linker is looking for all libraries in /usr/lib

the required libraries do exist on a recent trueos build (snapshot 208), but not on a trident build.

The file /usr/local/etc/devd/cups.conf is used to enable cups to make use of usb printer devices.

With the correct name as /usr/local/etc/devd/cups.conf , devd will read it on startup.

I have TrueOS installed and running fine (17.12, 18.03), booting UEFI with Linux Mint's GRUB2 bootloader.

The installer finds the ZFS partition, I can select it, but it does not enable the option to install to a new boot environment.

(Edit: actually, no 18.06 here)

Verify that the automatic Xorg detection/startup routine works on the ISO.

Relevant files:

• start-trident-installer script
• Runtime dependencies for the port

Sorry,first I opened this issue on the Trident-core section:

project-trident/trident-core#85

This is more of a suggestion if there will ever be an upgrade path, but it's also low hanging fruit, so consider fixing it.

In older releases of TrueOS, new users got an .xprofile created for them that included a line something like:

if [ $i = "/usr/local/share/true/xstartup/enable-inputmethod.sh" ] || [ $i = "/usr/local/share/trueos/xstartup/gpg-agent.sh" ] || [ $i = "/usr/local/share/trueos/xstartup/ssh-agent.sh" ] 

That ran these nice system-wide scripts to enable gpg-agent and so on.

If a user just installs trident into a boot environment, this X configuration won't work since there is no longer a /usr/local/share/trueos but a /user/local/share/trident

Of course most users will only notice this when ssh-agent isn't working as they expect. Then they have to know that this was set up in .xprofile. It's not straightforward and it's not documented anywhere.

In the name of compatibility, I would suggest either:

1. Making a symlink from /usr/local/share/trident to /usr/local/share/trueos OR
2. Make a /usr/local/trueos directory and symlink the scripts from trident.

I suspect number 2 will work in more situations and "just work". You could also go one step further and do the same thing for PC-BSD, but I guess the number of upgrades from that will be low.

When clicking on the Console button, it drops to a black blank screen, and then reloads the installer.

The intended shell access is not provided.

Hello!
I got these error messages under the boot process of the installer media (.iso)

unknown oid "debug.witness.trace" therefore the sysctl failed to start

other error message:

devd line 29:device:syntax error

And when I have to choose the place for the new system, the field of "Select Installaton Location" this is usually empty:

https://imgur.com/a/CR7fZHu

If I click on the "Previous" and after again on the "Next" then after few try the harddrives will appear and I can continue the install procedure:

https://imgur.com/a/6Fno9UU

Under the verbose boot process of the installer the HDD and the SSD are visible (manufacturer, type, serial number etc).

My machine is an hybrid graphical Acer Aspire E17 (Intel-Nvidia combo- Nvidia Optimus) and the Beta2 used the vesa driver, this was not the best, but it could to work.
Now the Beta3 would like to use the Intel driver, but it couldn't not. When the installed system start, I got a black screen with the command prompt, I can login, but if I login the first thing what I get is a "zsh-newuser-install" answer. So far I tried some videodriver variation unsuccessfully. The /etc/X11/xorg.conf is OK, maybe the nvidia or intel_load yes line missing from the /boot/loader.conf, I will check this, now I haven't more idea yet.

Used the following ISO http://pkg.project-trident.org/iso/release/Trident-x64-20180831.iso which booted fine. Setup VM with 4GB memory, and 50GB of space. After booting I get missing boot loader as shown in the screenshot below.

While installing under VMWare on MacBook Pro - Retina, the buttons you need to click to proceed are off screen at the bottom. Makes it hard to continue.

Should that last token be "${ZPOOL}" instead to allow for alternative target pool names?

During the installation of Trident-x64-20180831.iso I noticed there was not any option
for backup recovery from a life-preserver backup.

The cause is incorrect formatting of file /boot/logo-trident.4th read by the forth interpreter.
The words PURPOSE, CONSEQUENTIAL, STRICT, and WAY, all part of the standard legal disclaimer, are incorrectly formatted (looks like bad cut and paste) are are interpreted by forth. This causes an error on processing of logo-trident.4th and no trident is displayed.

However, if corrected, a separate problem occurs. The file "logo-trident.4th" is displayed resulting in an overlapping trident on top of the displayed menu (brand-trident.4th), as shown in the attached image.

A horizontal trident is suggested for

Since I first tried Trident a month ago, and now with RC2, when I'm installing on my Intel NUC (model D34010WYK), I find that the Select Installation Location screen is empty. I found that I can go back to the Previous page, then go forward again it will populate the page with the disk and partitions. Sometimes it has taken four times back and forth to get the page populated.

Background:
The machine has had legacy TrueOS desktop 18.03 installed. Its ZFS pool is tank. It is located on a separate disk drive. Trident installation also resides on its own separate drive where its ZFS pool is trident.

Scenario:

1. Selecting BE upgrade for an existing Trident installation by checking radio button “Boot Environment” at “Select Installation Location” step and selecting trident by hovering mouse over it so the option is highlighted
2. At “System Installation Summary” step configuration shows:
   installMode=upgrade
   zpoolName=tank # <———- expected trident, this TrueOS 18.03 pool where this BE install would not be compatible
3. Going back to “Select Installation Location” and selecting the opposite option “tank”
4. Again proceeding to “System Installation Summary” step where configuration is:
   installMode=fresh # <———— expected upgrade , which would fail anyway because disk drive info was not provided
   zpoolName=trident

Problem:
The configuration summary is read-only in UI and at this step it still seems to be in the installer process memory so it’s not possible to correct / override it

Solution:

1. Fix update of installMode and zpoolName from UI
   OR
2. Enable changing / overriding the resulting “System Installation Summary” configuration

Verify that the GELI encryption option works for both Legacy and UEFI boot methods (full single disk install).

Good test case:

• VirtualBox VM

Ideally I thought gprart would handle such case behind the scenes when acting on the destroy option.
But so that not to be dependent on upstream timelines would it be good idea to include the following step in the installer script which does ZFS formatting?

dd if=/dev/zero of=/dev/$DRIVE bs=$NBYTES

Did not see a way to change the pool name, so to something other than TANK

If the repeat password is incorrect trident cannot be installed. The password can be viewed but the repeat password cannot be viewed.

(I couldn't find any documentation on the installer from which to get this info, nor any other place where to ask this question...)

Last night, I attempted to install BETA3 on my Dell Lattitude D630 laptop. My laptop has an NVIDIA Quadro NVS 135M graphics chip. According to nVidia's website, that particular chip is supported by nvidia-driver-340. During my initial install attempt, I selected the 340 driver. The installation finished successfully. However, upon reboot, the nVidia driver appeared to fail. Below is a screenshot of the error.

I attempted to reinstall with the main nVidia driver, but the same error occurred.

I successfully installed TrueOS desktop on the same laptop earlier this year.

Verify that an install into a new Boot Environment works properly.

Good test system

• Previously-installed TrueOS 18.03 "desktop" edition

Installing Trident on a VBox guest, installer correctly detects VBox video, but the mouse integration is not working and must capture mouse.
John
[email protected]

In the final System Installation Summary step of the installer, the root and user account passwords are shown in plain text.

Should be masked or otherwise hidden somehow.

https://filebin.pw/dpKoH0

Original Issue: project-trident/trident-build#4

While the keyboard/locale options are getting properly set in the pc-sysinstall config, it does not appear that pc-sysinstall is saving those variables on the installed system properly since PCDM still shows the default locale/keyboard settings on first boot.

Possible Solution:

1. In the installer, assemble a custom config file with various options (locale, keyboard, timezone, possibly other options later) and place it into the installed system at the end of the install process.
2. In trident-core (/usr/local/share/trident/scripts/*) write a parsing script for ensure those config options are enabled properly on the installed system as needed for PCDM or other tools.

Hello. Thanks for your work on this promising system. I noticed troubles with localization. The installer doesn't let me choose a time zone nor a keyboard layout (I can choose various keyboard brands but no layout). I can choose a language but it has no effect on the installer, which remains in English. Then, I have to choose passwords using a keyboard layout that's not my real one. Once I reboot in the installed system, the language is en_US, although I had chosen fr_FR in the installer.

Install landing page:

• Go to terminal takes user off of GUI installer onto console vty (not sure if this is expected behavior)
• Text in ISO Date reads "ISO Data %1"
• Cannot expand System, Keyboard, and Local tabs. They open fine, but I can't pull the grip farther to the right. (not sure if this is expected behavior)

Installation busy pages:
Layout of the images and text is still unpolished.

View Log
Cannot expand "View Log" panel (same behavior as above)

Trying to install beta 02 iso on bare metal i7 with dedicated ssd disk. Installer fails after doing gpart thing:


I tried to click on "Go to terminal" to see mentioned log file, but wizzard started again, this time I selected ada0p2:

Same result. Tried to ctrl+alt+F1 and see there is this error:

I installed: Trident-x64-20180831.iso
and during the install prompting, I set the time zone.

After the install completed and the first boot I
discovered the system time zone was not set.