RC3 - update (taken from telegram) - discussion thread


#12

Hi.
When installing Trident from usb onto a clean disk…
I have mouse failure (USB wired and wireless) AND I the keyboard (USB wired and wireless) doesn’t respod appropriately [tab, esc, arrows, pgup, pgdn, end… don’t) so “dropping to a terminal” seems somewhat tricky - any ideas please?
Thx

System info
MSI - H110M PRO-VH PLUS (MS-7A15) on latest bios.
Intel® Core™ i3-6100 CPU @ 3.70GHz

From messages log file on TrueOS-Desktop the wireless mouse and keynoard reports:
kernel: ugen0.2: <Logitech USB Receiver> at usbus0
ukbd0 on uhub0
ukbd0: <Logitech USB Receiver, class 0/0, rev 2.00/29.00, addr 1> on usbus0
kbd2 at ukbd0
ugen0.3: <Microsoft Microsoft 2.4GHz Transceiver v7.0> at usbus0
kernel: ukbd1 on uhub0
kernel: ukbd1: <Microsoft Microsoft 2.4GHz Transceiver v7.0, class 0/0, rev 2.00/6.33, addr 2> on usbus0
kernel: kbd3 at ukbd1


#13

did you read the text below the download button?

It tells of moused NOT starting and a way to fix that


#14

On my system CTRL+ALT+F4 brought me to a shell with root as the user but unfortunately starting the moused service didn’t help on my system to use the graphical installer.


#15

on my test machine, I had to drop to shell 3 times before the mouse started working


#16

My way to this:

===================
General information
===================
boot environment now (N) … 13.0-CURRENT-up-20181112_130401 NR 2018-11-12
after restart (R) … 13.0-CURRENT-up-20181112_130401 NR 2018-11-12
boot loader …………………………………… BSD
type ……………………… BIOS
CPU ………………………………………………………… AMD A4-3300 APU with Radeon(tm) HD Graphics
number of cores ……………… 2
host ……………………………………………………… trident-2863
memory ………………………………………………… 4096 MB available, 1975 MB free
OS git branch ……………………………………………………………………………………… amd64
OS git revision ………………………………………………………………………………… amd64
OS kernel build time …………………………………………………………
OS kernel identity …………………………………………… (uname -i) GENERIC
OS platform (architecture) ……………………… (uname -m) amd64
OS release level ………………………………………………… (uname -r) 13.0-CURRENT
OS version and patch level …… (freebsd-version) 13.0-CURRENT
TrueOS package set …………………
TrueOS version ……………………………
uptime ………………………………………………… 12 mins
user …………………………………………………… root

was a little complicated. Coming from Project-Trident RC1 I couldn’t update because of this error:


Installing in a new boot environment wasn’t possible since nothing got the graphical installer to work.
Looking at my /etc/pkg folder got me wondering why there is a TrueOS.conf though @beanpole135 was talking (see above) about Trident.conf. So I took a look at the content of my TrueOS.conf:

TrueOS-ports: {
url: &quot;http://pkg.project-trident.org/pkg/release/ports/${ABI}/latest&quot;,
signature_type: &quot;pubkey&quot;,
pubkey: &quot;/usr/share/keys/pkg/trueos.pub&quot;,
enabled: yes
}
TrueOS-base: {
url: &quot;http://pkg.project-trident.org/pkg/release/base/${ABI}/latest&quot;,
signature_type: &quot;pubkey&quot;,
pubkey: &quot;/usr/share/keys/pkg/trueos-base.pub&quot;,
enabled: yes
}

These URLs are not existing anymore. So I removed this file and replaced it by a new TrueOS.conf:

TrueOS-ports: {
url: &quot;http://pkg.project-trident.org/pkg/release/FreeBSD:13:amd64/latest&quot;,
signature_type: &quot;pubkey&quot;,
pubkey: &quot;/usr/share/keys/pkg/trueos.pub&quot;,
enabled: yes
}

Now the command # trueos-update check worked without error and afterwards the # trueos-update upgrade triggered two hours of downloading and installing. After two reboots I seem to be back in the game. :slightly_smiling_face:

Just for reference the current pkg info of trident-core:

root@trident-2863:/etc/pkg # pkg info trident-core
trident-core-201811061143
Name           : trident-core
Version        : 201811061143
Installed on   : Mon Nov 12 13:12:08 2018 CET
Origin         : trident/trident-core
Architecture   : FreeBSD:13:amd64
Prefix         : /usr/local
Categories     : trident
Licenses       : BSD2CLAUSE
Maintainer     : jt@ixsystems.com
WWW            : https://github.com/project-trident/trident-core
Comment        : Core distribution files and utilities for Project Trident
Annotations    :
        FreeBSD_version: 1300002
Flat size      : 1.26MiB
Description    :
Core distribution files and utilities for Project Trident

WWW: https://github.com/project-trident/trident-core

#17

there is way to upgrade from RC1. I did it

taken from telegram

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

sudo ./install-trident-repo.sh

this will do dirty work


Failed to update
Project Trident 1812 release - discusion here
New release unleashed today
#18

Here’s my experiences with upgrading a Lenovo Thinkpad S1 Yoga from RC2 to RC3 with the method described at the Trident download page:

Finalizing-time from login to desktop has become excruciating long - from “not being able to read the quote”-short to much more than 10 seconds!
One of the changes I’ve noticed on tty0:
hdac0: <Intel Haswell HDA Controller> mem 0xf0610000-0xf0613fff at device 3.0 on pci0
hdacc0: <Intel Haswell HDA CODEC> at cad 0 on hdac0
hdac0: Unexpected unsolicited response from address 0: 00000000
hdac0: Unexpected unsolicited response from address 0: 00000000
hdac0: Unexpected unsolicited response from address 0: 00000000 # repeated hundred of times
changed to a:
hdac0: Command timeout on address 0 # repeated almost as many times
ending with a:
hdac0: Reset setting timeout

Changing Lumina color scheme makes the desktop unresponsive for a looooooong time.

Trident controlpanel wouldn’t launch (fixable libressl/openssl clash)

The quicklaunch bar is still there, but without icons. (changing "Icons" in Lumina settings got them back)

BUT it has fixed a lot of my problems from RC2 and earlier


#19

the first boot into RC3 does take a very long time


#20

Every login takes a loooong time now!!!
But the first boot login took even longer…


#21

i did a reboot this morning, thank you firefox.

I did not notice any hang time this time


#22

Was it on a upgraded RC3 or new install RC3?

I’m getting ready to nuke the upgraded RC3 to test a bare metal install RC3


#23

was on an upgrade from RC1 to RC3


#24

Ok, hopefully I get back to a lightning quick login time on the “new install RC3” :slight_smile:
PS.
And the icon-stuff is also fixed in next RC - perfect!


#25

Ok, then 3 times. I only did it 2 times and it still didn’t work although it shows that the service was started.

service moused start
service moused status
status: started


#26

i have had to keep moving the mouse during each switch back to the installer.

Is this a new install? or BE upgrade?


#27

if you can be at a console what is the output of “ps aux | grep -i mouse” does it actually show a process running?


#28

I tried a fresh install. Now I actually repeated start/stop the process 20 times but it still doesn’t work. I also went to the first console, stopped the installer, checked the mouse service, restarted it several times but still no success. I’ll try the “move the mouse all the time” trick right now. The process table didn’t show any “mouse” process.


#29

If the output of ps aux does not show anything for moused then the process is not running. The process not running means the mouse does not work.


#30

On Telegram a user had the problem, that a HW kernel module wasn’t loaded and had to do:

> kldload i915kms

Maybe try to load your required HW kernel modules…


#31

That is only needed for Intel hardware but I have an AMD system with a NVIDIA 520 GT, which works well except for the USB mouse.