U8 is available

#1

https://project-trident.org/download
There is no description yet, last is https://project-trident.org/post/2019-03-16_infrastructure_changes , but I guess @RodMyers will come around soon with more info.

Two notices:

  1. It’s now 3.0 GB, i.e. 1 GB smaller than before.
  2. It has been very quiet on this discourse for a week now. Where are you people? :wink:
1 Like

#2

Probably on the Telegram channel is where everyone has been.

You may want to wait just a little bit more. This was a big update because of the infrastructure changes, it took (is taking) a while for all the CDN sites to synch (Ken hasn’t given the “all clear” yet) and you will have to switch “trains” before doing the update.

Once it’s all done, from a console as root it will be best to do:
sysup -change-train Trident-release
sysup -check
sysup -update

You may need to do sysup -fullupdate but I don’t think so.
An aside, I like to set the name of the new BE when I’m doing the update:

sysup -update -bename 18.12-RELEASE-U8

it makes it nicer when you do beadm list
beadm list
BE Active Mountpoint Space Created
initial - - 288.7M 2019-02-10 13:24
18.12-RELEASE-U4 - - 265.5M 2019-02-15 03:43
18.12-RELEASE-U5 - - 378.6M 2019-02-21 03:12
18.12-RELEASE-U6 - - 387.6M 2019-02-28 14:17
18.12-RELEASE-U7 NR / 8.4G 2019-03-11 14:57

1 Like

#3

I’m considering doing a fresh install into a boot environment this time.

1 Like

#4

Thanks for the heads-up. Is this why my System Update Manager keeps spitting out these errors?

[2019-03-29 09:36:20] Checking for system updates…
Updating package remote database

[pkg-static: Repository Trident load error: access repo file(/var/db/sysup/pkgdb/repo-Trident.sqlite) failed: No such file or directory
pkg-static: http://pkg.project-trident.org/pkg/release/FreeBSD:13:amd64/latest/meta.txz: Not Found
pkg-static: http://pkg.project-trident.org/pkg/release/FreeBSD:13:amd64/latest/packagesite.txz: Not Found
]
ERROR: Failed running pkg update:pkg-static: Repository Trident load error: access repo file(/var/db/sysup/pkgdb/repo-Trident.sqlite) failed: No such file or directory

pkg-static: http://pkg.project-trident.org/pkg/release/FreeBSD:13:amd64/latest/meta.txz: Not Found
pkg-static: http://pkg.project-trident.org/pkg/release/FreeBSD:13:amd64/latest/packagesite.txz: Not Found

exit status 70
[2019-03-29 09:36:26] Finished: ERROR (1)

1 Like

#5

Yes it is @aocab.
According to Telegram, we’re getting close.

@Sergio I’ve not had any problems doing the updates so far (U3 install, U4 up to U7).
I think AMD GPU is still broken (Upstream FreeBSD issue).

1 Like

#6

No need for me to run a full upgrade, just
sysup -change-train Trident-release
sysup -check
sysup -update
and…
about
Project Trident Information

OS Version: 18.12-RELEASE-U8
Build Date: jeu. 28 mars 2019 13:53:42 CET
Boot Type: BIOS

TrueOS Sources Used:
Base Repository: https://github.com/trueos/trueos
Base Commit Branch or Tag: trueos-stable-18.12-cleanbuild
Ports Repository: https://github.com/trueos/trueos-ports
Ports Commit Branch or Tag: cf1e3da140169d9cccb1bb5cc15a167c722230f3

System Specs:
Boot Method: BIOS
Intel® Core™ i5-6200U CPU @ 2.30GHz
Physical CPUs: 4
Physical Memory: 15.82 GB

GPU Information:
vgapci0@pci0:0:2:0: class=0x030000 card=0x10941025 chip=0x19168086 rev=0x07 hdr=0x00
vendor = ‘Intel Corporation’
device = ‘Skylake GT2 [HD Graphics 520]’
class = display
subclass = VGA
vgapci1@pci0:1:0:0: class=0x030200 card=0x10941025 chip=0x139a10de rev=0xa2 hdr=0x00
vendor = ‘NVIDIA Corporation’
device = ‘GM107M [GeForce GTX 950M]’
class = display
subclass = 3D

Network Device Information
re0@pci0:4:0:1: class=0x020000 card=0x10941025 chip=0x816810ec rev=0x12 hdr=0x00
vendor = ‘Realtek Semiconductor Co., Ltd.’
device = ‘RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller’
class = network
subclass = ethernet

0 Likes

Update to U8 fails on UEFI bootload install
#7

Everything seems to run fine.

0 Likes

#8

@Chris Thanks for the feedback.

1 Like

#9

With the help you give to me for Trident i’m very happy to feedback.
If i can help :beers:

0 Likes

#10

Well folks, I think Ken has announced availability so have at it.
I’ve updated one system (Intel NUC) so far so good.
Don’t forget to change trains. I think you can do it from the GUI, but I’m an old dog and updating via CLI commands is more natural.

0 Likes

#11

This is what I am getting at the end of following Chris’s instructions:

Updating Bootloader
Updating EFI boot-loader on: ada1
ERROR: Unable to mount EFI partition
ERROR: Updating boot-loader failed!

Not sure how to proceed now.

mount:

trident/ROOT/13.0-CURRENT-up-20190313_214427 on / (zfs, local, noatime, nfsv4acls)
devfs on /dev (devfs, local, multilabel)
tmpfs on /libexec/rc/init.d (tmpfs, local, noexec, nosuid)
trident/tmp on /tmp (zfs, local, nosuid, nfsv4acls)
trident/usr/home on /usr/home (zfs, local, nfsv4acls)
trident/usr/jails on /usr/jails (zfs, local, nfsv4acls)
trident/usr/obj on /usr/obj (zfs, local, nfsv4acls)
trident/usr/ports on /usr/ports (zfs, local, nfsv4acls)
trident/usr/src on /usr/src (zfs, local, nfsv4acls)
trident/var/audit on /var/audit (zfs, local, nfsv4acls)
trident/var/log on /var/log (zfs, local, noexec, nosuid, nfsv4acls)
trident/var/mail on /var/mail (zfs, local, nfsv4acls)
trident/var/tmp on /var/tmp (zfs, local, noexec, nosuid, nfsv4acls)
linprocfs on /compat/linux/proc (linprocfs, local)
tmpfs on /compat/linux/dev/shm (tmpfs, local)
linsysfs on /compat/linux/sys (linsysfs, local)
trident/ROOT/updatego-stage on /.updatestage (zfs, local, noatime, nfsv4acls)
devfs on /.updatestage/dev (devfs, local, multilabel)

beadm list:

BE Active Mountpoint Space Created
initial - - 3.3G 2019-03-09 17:35
13.0-CURRENT-up-20190313_214427 NR / 11.8G 2019-03-13 21:16
updatego-stage - /.updatestage 1.3G 2019-03-29 21:25

0 Likes

#12

What instructions?

0 Likes

#13

just these:

1 Like

#14

Your system is booting with UEFI/EFI not BIOS, correct?

0 Likes

#15

Yes, that’s correct.

0 Likes

#16

@sunshine can you type “about” and post the output of that>?

0 Likes

#17

@sunshine, can you start a new thread, so we can concentrate on this issue?

when you do, please type --> about
ans see what the boot method is

2 Likes

#18

Thanks. That worked for me.

0 Likes

#19

Updated the system - It was successful!

Just a small thing happened. When I opened the update manager I first got this:

[2019-03-31 17:09:06] Checking for system updates...
Updating package remote database
read: websocket: close 1006 (abnormal closure): unexpected EOF
write tcp 127.0.0.1:8134->127.0.0.1:11303: use of closed network connection
[2019-03-31 17:09:33] Finished: ERROR (1)

But it fixed it self after a short while and I got the green tick at the taskbar, but I could not open the update manager. But after a quick logout/login it was all back to normal.

[2019-03-31 17:13:53] Checking for system updates...
Updating package remote database
Checking system for updates
No updates available
[2019-03-31 17:14:21] Finished: OK

Just a quick question:
Shall I set the update manager back to Trident or leave it at Trident-release?

0 Likes

#20
I saw similar sporadic failures with sysup -update
After a few invocations, it completed.
Leave it at Trident-release
# sysup -list-trains
sysup -list-trains
Current Train: Trident-release

The following trains are available:
------------------------------------------------------------------
Trident                 Follows the 6-month STABLE releases of TrueOS for the base system, with rolling updates for packages. [Deprecated] [release] [pkg] [official]
Trident-release                 Follows the 6-month STABLE releases of TrueOS for the base system, with rolling updates for packages. [release] [pkg] [official]
Trident-staging                 DANGER: Staging repo for release packages. Used for pre-release QA and testing. [stage] [pkg] [testing] [developer]

John
groenveld@acm.org
0 Likes