RC3 - update (taken from telegram) - discussion thread


#1

Ken Moore, [10.11.18 09:25]
Status update on the RC3 testing:

  • VirtualBox tests looked good: Fresh install, BE install, and updates are fine. Package availability and functionality from the repo seems fine.
  • Live system tests are a mixed bag: Quite a few of our laptops are experiencing bootup issues either on the install ISO or post-installation when booting the newly-installed system. We have narrowed it down to the fact that FreeBSD enabled the new “lua”-based bootloader by default now instead of the traditional “forth”-based bootloader. This boot issue seems to impact most of our older Lenovo laptops, but newer systems or systems with a newer BIOS revision seem to be working fine.
    Possible Solutions
  1. I have been digging into the FreeBSD build flags, and think I have found the option to disable the lua bootload and use the forth one again.
  2. We try to pull a newer version of TrueOS/FreeBSD and see if anything in the lua bootloader has been fixed recently.
  3. We release this RC3 image with strong warnings about the bootloader.
    Problems With Solutions
  4. The forth loader might be irrevocably broken in source or permanently disabled in the build procedures now (not sure - I have heard mixed reports on it from Kris with regards to TrueOS). It will probably take some time to work this out and do a bunch of builds with different flags.
  5. I have another TrueOS-distro project I work on for iXsystems which does need/use the latest sources and FreeBSD itself is incredibly broken right now. Kris and TrueOS are still trying to “fix” the FreeBSD build procedures after their latest changes so that things actually work again, but it will take some time before things are ready to be used/tested on that side.
    Recommendations
  • Release this build as version RC3, with warnings/notices about bootloader issues.
  • For RC4, try to switch back to the forth-based bootloader via changing the build flags.
  • Wait another month or two for things to stabilize in FreeBSD/TrueOS before moving to a newer version of base.

Thoughts??

edit:
Once on RC3, upgrading/updating should as be simple as before


#2
Option 3. please!
Please post the RC3 ISO to the website and update the repository 
with the RC3 packages.
Put a short "caveat emptor" on the Trident website regarding the known
issues with the bootloader and legacy hardware and that an RC4 will
be forthcoming.
John
groenveld@acm.org

#3

that is/was the general consensus that followed on telelgram.

@beanpole135 is working on things tonight. This thread will be the focal point for discussions on RC3


#4

FreeBSD is still 12-CURRENT or has HEAD flipped to 13-CURRENT? I see that 12-CURRENT is in BETA builds for release.

I’m assuming that TrueOS is tracking FreeBSD-HEAD still.


#5
Does upstream have all the data it needs?
Should we be soliciting about and dmidecode output in our RC3 
problem reports?

John
groenveld@acm.org

# dmidecode
# dmidecode 3.2
# SMBIOS entry point at 0x77eda000
Found SMBIOS entry point in EFI, reading table from /dev/mem.
SMBIOS 3.0 present.
44 structures occupying 3031 bytes.
Table at 0x77ED7000.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
        Vendor: American Megatrends Inc.
        Version: 1.05.15LS1
        Release Date: 05/27/2016
        Address: 0xF0000
        Runtime Size: 64 kB
        ROM Size: 5120 kB
        Characteristics:
                PCI is supported
                BIOS is upgradeable
                BIOS shadowing is allowed
                Boot from CD is supported
                Selectable boot is supported
                BIOS ROM is socketed
                EDD is supported
                Print screen service is supported (int 5h)
                8042 keyboard services are supported (int 9h)
                Printer services are supported (int 17h)
                ACPI is supported
                USB legacy is supported
                BIOS boot specification is supported
                Targeted content distribution is supported
                UEFI is supported
        BIOS Revision: 5.11

Handle 0x0001, DMI type 1, 27 bytes
System Information

# about
===================
General information
===================

boot environment now (N) … bar NR 2018-10-31
       after restart (R) … bar NR 2018-10-31
boot loader …………………………………… BSD
            type ……………………… EFI
CPU ………………………………………………………… Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
    number of cores ……………… 8
host ……………………………………………………… w650rc
memory ………………………………………………… 16384 MB available, 14238 MB free
OS git branch ……………………………………………………………………………………… GENERIC
OS git revision ………………………………………………………………………………… GENERIC
OS kernel build time ………………………………………………………… amd64     
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 ………………………………………………… 6 mins, 1 user, load averages: 0.10, 0.26, 0.16
user  …………………………………………………… root



#6

just did a test upgrade. the test upgrade was 13-CURRENT

looks/works good

edit:

works, installs fine on a lenovo t520 & 2nd gen Carbon X1


#7

I’ll keep on resting on TrueOS 18.03 and will wait for the Trident RELEASE version (no RC for me :wink: )

However, I reflected on something looking at the RC3 file… It’s giant! :astonished:
With 4,9 GB it won’t fit on a regular DVD, You’ll need a Blue-ray, alternative put it on an USB-pin.


#8

There’s still/always DVD DL (8.4 GB).
Also, I’ve never tried creating a bootable BD to this day. Might be interesting to test, though… :slight_smile:


#9

I just booted RC3 from a USB drive. It works fine until X starts. But then I can’t use my plain vanilla USB mouse.The keyboard works, I can switch to other consoles, but the mouse doesn’t.


#11

@rowo, had you read the complete message before you downloaded the ISO, you would know that this is a known issue, and it tells the user how to get the mouse working


#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


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