First attempt to install Trident


#21

OK did a lot last night. Didn’t run the last two commands since I didn’t have web access. TrueOS had qupzilla as a default browser but I couldn’t find one in Trident. I did install the repo and ran the upgrade though. Everything comes up OK but my issue now is that it comes up in xorg using the vesa driver. My old install used the intel driver which allowed me to use an external/second screen via VGA port at work. Helpful for an old guy like me!

I know that xorg drivers are a constantly shifting target, but does anyone know if there’s a better drive for me to use? I tried dropping my old xorg.conf into place with no luck. Also tried “X -configure” but it didn’t work. I used the new xorg.conf and simply replaced “vesa” with “intel” but that failed as well. I noticed that in /boot/kernel/ there are two .ko for intel, ataintel.ko and intelspi.ko. Couldn’t determine what either of these days but I assume the first is for ata devices, not video drivers.

Made good progress though. Thanks for all the help so far and for all the hard work.

My old xorg.conf:

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


#22

Note when I say I didn’t have web access I mean that I had only written down the fetch command. I’ll do the other commands tonight.


#23

can’t do much with RC2, except upgrade

quizill was depreciated for falkon


#24

Well, I did the upgrade, or at least ran that script:

https://pkg.project-trident.org/repo-config/install-trident-repo.sh

It upgraded and rebooted, installed a ton of updated packages and patches.

I’ll run the -update and -check commands tonight and try again.


#25

fetch, run the script, check, then upgrade.

should be that simple


#26
On boot, Trident generates an xorg.conf under /usr/local/etc/X11
What is it?
John
groenveld@acm.org

#27

Ah, I was checking /etc/X11/xorg.conf

I’ll check /usr/local/etc later. Thanks for the tip, didn’t even think about checking /usr/local/


#28
Trident includes an RC script to detect the VGA and load any 
necessary kernel modesetting driver, but its not bulletproof.
<URL:https://github.com/project-trident/trident-core/issues/43#issuecomment-454941876>
Need to see what Trident auto-generated.
John
groenveld@acm.org

#29

here is /usr/local/etc/X11/xorg.conf

#===========

Auto-generated X11 graphics

card/driver configuration

#===========

Created by Project Trident

#===========

DO NOT MODIFY

- Will be replaced on every bootup by trident_init service

- Place alternate X11 settings into separate file(s):

/usr/local/etc/X11/xorg.conf.d/[something].conf

OR

/etc/X11/xorg.conf

#===========
Section “ServerLayout”
Identifier “XFree86 Configured”
Screen 0 “Screen0” 0 0
EndSection

Section “Screen”
Identifier “Screen0”
Device “Card0”
Monitor “Monitor0”
EndSection

Section “Device”
Identifier “Card0”
Driver “vesa”
BusID “0:2:0”

EndSection


#30
Log in via ssh or switch to another VT via CTRL-ALT-F1.
# service pcdm stop
# pkill pcdm
# pkill xinit
# kldload /boot/modules/i915kms.ko
# cp /usr/local/etc/X11/xorg.conf /etc/X11
edit /etc/X11/xorg.conf and change the driver from vesa to intel
# service pcdm start

John
groenveld@acm.org

#31

Like the subject says - “First attempt” to install on the TrueOS 18.03 laptop.

It seems fine at first, it runs though the boot menu, then some rolling text, then the screen just goes black and nothing more. No flashing HDD lamp, no nothing and since it’s a SSD I can’t hear it working (I know it happens on computers that the drive works slightly and you can’t see the lamp flashing).

It has been sitting like this for maybe 10-15 minutes. Is it supposed to do so? Am i just and if I’m just impatient? Or is it something I shall do?

Update:
Easy solved. I just followed this

Solution:
As soon as Trident boot menu appears, press 3 to Enter boot loader prompt. Then type ‘boot’ and hit Enter.

Keeping on with the install attempt :slightly_smiling_face:


#32

OK, doing this turns the VT font into the more familiar, smaller font, but I can’t launch X11. I rebooted and it didn’t come up with the smaller VT font or with X11 running. Changed /etc/X11/xorg.conf back to vesa from intel and it boots again. Still no smaller VT font but X11 comes up.

Oh, and when I did your suggestions, the external monitor works! But again, no X11.

Closer!


#33
Switch to VT1
# service pcdm stop
# pkill pcdm 
# pkill xinit
change the driver in /etc/X11/xorg.conf to modesetting
# kldload /boot/modules/i915kms.ko
# service pcdm start

If X crashes. post /var/log/Xorg.0.log
John
groenveld@acm.org

#34

Worked like a champ! Thanks!

Haven’t rebooted yet but will let you know if it survives.

Really do appreciate all the work you folks put in on the project.


#35

Changes don’t survive a reboot. Probably because the i915kms.ko isn’t being loaded at boot.

Just fixed it by adding the following to /etc/rc.conf

kld_list="/boot/modules/i915kms.ko"


#36
Fixed in a future update:
<URL:https://github.com/project-trident/trident-core/issues/43#issuecomment-455190003>
John
groenveld@acm.org