@Dashrender said in Miscellaneous Tech News:

@wrx7m said in Miscellaneous Tech News:

@mlnews said in Miscellaneous Tech News:

Microsoft Now Supports Office 365 ProPlus on Windows Server 2019

Microsoft has reversed an earlier position and now plans to support the use of Office 365 ProPlus on Windows Server 2019
Even for organizations using it in virtual desktop infrastructure (VDI) scenarios.

This is very interesting. I have been trying to figure out which way to go in my replacement of a 2008 R2 RDS where I will need Excel.

how could they ever not have expected to do this for RDS farms?

I am guessing they are right when they said this-
"The lack of support, now reversed, was expected to perhaps drive organizations accessing Office 365 ProPlus on remote servers in VDI scenarios toward the use of Microsoft's new Windows Virtual Desktop service instead."

@mlnews said in Miscellaneous Tech News:

Microsoft Now Supports Office 365 ProPlus on Windows Server 2019

Microsoft has reversed an earlier position and now plans to support the use of Office 365 ProPlus on Windows Server 2019
Even for organizations using it in virtual desktop infrastructure (VDI) scenarios.

This is very interesting. I have been trying to figure out which way to go in my replacement of a 2008 R2 RDS where I will need Excel.

Edit: Looks like it is still only the ProPlus option. (As indicated by the title)

@scottalanmiller said in Miscellaneous Tech News:

If you read the bit in the article that mentions mobile, you will notice that it is about the WAN backhaul for mobile carriers to use, not the mobile system itself. The Amazon Kuiper system is meant for direct to home access, direct to business access, as well as light use WAN backhaul. These low earth orbit systems are for fixed location endpoints, not mobile ones.

That would allow them to put towers in remote locations where all they need is a means to power them.

To set the dnf-automatic timer to run every day at 1AM:

nano /usr/lib/systemd/system/dnf-automatic.timer

[Unit]
Description=dnf-automatic timer
# See comment in dnf-makecache.service
ConditionPathExists=!/run/ostree-booted
Wants=network-online.target

[Timer]
OnCalendar=*-*-* 01:00:00

[Install]
WantedBy=multi-user.target

Vultr support was interested after my previous response.

"We understand your concerns and appreciate you bringing issues to our attention, however, we are not seeing this issue with our Fedora 30 build when running updates. It is possible that something is different when upgrading the distribution manually and this is not something we would be able to troubleshoot as we are not seeing the issue.

Does the OS itself throw an error when attempting the update? If there is an error being throw by the OS we can try to assist in figuring out what it means and try to point you in the right direction, but as a self-managed service our in depth troubleshooting steps for software issues is extremely limited.

Thank you for your understanding."

I provided them with specifics on how to produce the error.

@scottalanmiller said in Fedora 29 and 30 - EDAC skx: Can't Get tolm/tohm Error on Vultr:

As a starting point, are these installed when you install via ISO?

# dnf list | grep edac
edac-utils.i686                                                        0.16-20.fc30                                               fedora         
edac-utils.x86_64                                                      0.16-20.fc30                                               fedora         
edac-utils-devel.i686                                                  0.16-20.fc30                                               fedora         
edac-utils-devel.x86_64                                                0.16-20.fc30                                               fedora

From one that was upgraded to 30.

To add to this- I have an error that started appearing after updating their Fedora 29 and 30 instances. Further testing found that the error appears in different regions using their server type template installers or even a custom iso option that I used with net install. All I have to do is deploy, run dnf update and reboot. The error is present in every boot after the update.
https://mangolassi.it/topic/19903/fedora-29-and-30-edac-skx-can-t-get-tolm-tohm-error-on-vultr

@scottalanmiller said in Fedora 29 and 30 - EDAC skx: Can't Get tolm/tohm Error on Vultr:

dnf list | grep edac

From one of their own server type installers, as shown in my previous post.

@scottalanmiller said in Fedora 29 and 30 - EDAC skx: Can't Get tolm/tohm Error on Vultr:

As a starting point, are these installed when you install via ISO?

# dnf list | grep edac
edac-utils.i686                                                        0.16-20.fc30                                               fedora         
edac-utils.x86_64                                                      0.16-20.fc30                                               fedora         
edac-utils-devel.i686                                                  0.16-20.fc30                                               fedora         
edac-utils-devel.x86_64                                                0.16-20.fc30                                               fedora

The error is present using their own installer - Compute 55GB Server Type, Fedora 29 or 30.

However, I also tried an install using the custom iso option and net install. That one yielded the error during the first boot after install, as whatever patch causing the issue was applied during the install.

@scottalanmiller said in Fedora 29 and 30 - EDAC skx: Can't Get tolm/tohm Error on Vultr:

@wrx7m said in Fedora 29 and 30 - EDAC skx: Can't Get tolm/tohm Error on Vultr:

@dafyre said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):

@black3dynamite said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):

I wonder if its the CPU model that you are assign to.

This would be my guess. It looks to be related to the Intel i10nm Ice Lake(?) CPUs.

Yeah, the few Google results I found mentioned a CPU, although I thought I saw skylake.

What Vultr "level" is the VM?

Compute 55GB SSD LA and Dallas.

Vultr replied -

"Hello,

The software one your VPS is outside of our scope of support.

Thank you."

I replied -
"I understand. Just thought your guys might want to figure out why your instances can't handle fully-patched versions of Fedora."

@dafyre said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):

@black3dynamite said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):

I wonder if its the CPU model that you are assign to.

This would be my guess. It looks to be related to the Intel i10nm Ice Lake(?) CPUs.

Yeah, the few Google results I found mentioned a CPU, although I thought I saw skylake.

@black3dynamite said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):

I wonder if its the CPU model that you are assign to.

That is what I was thinking and why I tried a different region. I also updated my Vultr ticket to let them know. They may or may not even care. We shall see.

@black3dynamite said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):

By default Fedora 30 Server uses ext4 for boot and xfs for /.
Change xfs to ext4 instead.
When using the your uploaded ISO.

Just to be clear - This error occurs during boot, but doesn't prevent the system from booting. I just don't know if it is something that will cause actual issues, or can be ignored.

Used Fedora 30 netinstall iso and first boot had the error. So, Fedora doesn't like something there.

Tried ruling out region/data center (maybe different hardware/hypervisor version). Tried Dallas Fedora 30 and got the same error after updating.

Fedora 30-
Deploy, Login, Reboot - No error
Deploy, Login, Update, Reboot - Error

To me, this means, anyone using Vultr's Fedora 29 or 30 instances will have this error. Now, is it something that I need to be concerned about? I don't know.

Rebooting 29, without updating, remains error free.

@wirestyle22 said in Fedora 30 - EDAC skx: Can't Get tolm/tohm Error After Upgrade From 29 (Vultr):

@wrx7m I would try to create a new instance with their image of 29 and upgrade to 30 to see if it works. If that doesn't work then I'd try to re-create what you are running on a custom iso and see if you can upgrade that successfully.

Just deployed a new Fedora 29 instance on Vultr. Updated it and rebooted. Got the same error in the logs. I went back in some other instances and found that the error started appearing between the end of May and beginning of June. So, this has nothing to do with my customization of the OS. All I did was- Deploy, Login, Update, Reboot.

Now, I am going to deploy and reboot without updating.

@black3dynamite said in User's PC is unstable:

It's been years ago, but the last time I dealt with excel issues. It was because of the Intel storage controller.

I hadn't heard that before. I'll have to keep that in mind.