You did something wrong about a month ago on Gnome, because we rely on WIFI and the clean install must be deleted since then. Network stuff in services are all marked dead, enabling them end in a question mark icon.
Machine Firmware Bug: Ryzen 2700U Vega mobile x4
iommu=soft to boot in. Mok Manager (disable-validation) to keep secure boot (SB) enabled, to dual boot a second distro, to compile mainline Kernel and to see WIFI circuitry below Kernel 4.18. We have the same issue now, there is no Network on task bar after the fresh install.
This is Kernel 5.0.2 and we are looking for 5.1-rc’s. We did not try to wake-up WIFI with the offline RPM package of Kernel 5.1-rc1.
How to force WIFI after a fresh install of Tumbleweed? How to configure the dam card?!?
On other distros, mokutil --disable-validation appears to be the solution. Re-enabling it, disabling SB has no effect. Our very first problem with secure boot was on the arrival of 18.04.2 with the Grub updates (Feb.1st Ubuntu 18.04.x daily ISO after updates).
The machine was unusable with secure boot enabled on mainline Kernel: invalid signature(error1), you need to load the Kernel first(error2). Since then, Linux is a constant battle to win.
Tumbleweed WIFI is an unknown equation for now and Tumbleweed is the only distro that detects the secure boot issue, boots in MOK Manager and offers the solution. Which is to enroll both Key and hash in Grub x64 twice.
Ryzen 2nd gen is at best on mainline Kernel, Tumbleweed is among our best friends. Please fix it!
It is the first time that mainline Kernel does not wake-up the WIFI network. The BIOS born date is Dec. 10th 2018 and we do not have wired network.
There is a long lasting bug here in Tumbleweed ISO’s. Trying to debug it alone since 5 weeks, the list of attempts is pretty long.
The solution in Yast system under services manager:
Network Manager = Start/on boot
systemd-networkd = Start/manually
Force network in Yast>system>services manager>network manager>start>on boot>+>systemd-networkd>>start>manually. Apply changes.
The two services enable WIFI on taskbar. Restart to see if WIFI starts automatically on boot.
Windows Ten was detecting the boot error and I let it check disk to see what is going on. The error message was about bootmgfw.efi. After check disk, a 200MB partition was created before the main NTFS partition. I deleted the partition and resize C: drive to its original size.
Then, I went back to MOK Manager to enroll Microsoft key and hash in bootmgwf.efi and bootx64.efi. It didn’t work. The message was displayed again. Went back in MOK utility to re-enable validation:
sudo mokutil --enable-validation
The message is gone now and Windows Boot Manager boots normally without the error. Since mainline Kernel comes from repo, it is not an unsigned Kernel and there is no need to disable secure boot momentarily on startup. At least for Tumbleweed that comes with Kernel 5.0.
Will now double check the WIFI issue by deleting the Gnome installation and re-install it with KDE.
Tumbleweed KDE 20190327 build /The bug is also present in KDE
Prior to this, in Network Settings the network setup method must be set to << NetworkManager Service. Click OK after to apply changes.
An error will be shown: No Network Running, click OK. The WIFI Network will be shown on the taskbar. Then do the above for Network Manager and systemd.
The installer needs attention**. There is no setup configuration for WIFI, the r8169 driver is for Ethernet. WiFi driver not listed in the installer nor even after the fresh install:
Thanks @ karlmistelberger for pointing out the systemd issue. In our previous attempts over the last month, we were trying to enabled too many services at the same time. Two of them need attention only.