In order to make it short, we won’t elaborate on the method used, but we just made 6 fresh installs of Tumbleweed back to back dual boot with 1709. A WIFI bug was introduced on our laptop near the end of February. It was not possible after that to run the OS, there was no Internet access.
To whom who rely on WIFI to reach the Internet, this a very frustrating situation. The source of the bug is in the installer and appears for Ryzen 2700U as a false reading that kills the WIFI circuitry: The network becomes INVISIBLE.
In Network Configuration, Network Manager is not the ownership of the process, it is Wicked or it is in a latent state. Clicking on Wicked enables a Yast popup and clicking back to Network Manager shows the same popup. This action restores the WIFI Network after the fresh install: From invisible to fully active KDE & Gnome.
The Network Manager parameter is marked active at boot. The systemd-networkd parameter is marked dead at boot. With no Ethernet cable this parameter has no incidence with WIFI activity. If we keep it as is, WIFI is fully functional after the clean install: Firefox, sudo zypper up and dup.
Please forward to the second floor and tell the new owners that Tumbleweed is among the best operating systems on the market, by far the most advanced Linux distro. Tell them also, that on the East Coast, the work of Linus Torvald and its 63K collaborators is available at supper time each Sunday, near 6-8PM. Not 4 days after as on the Open Suse Mainline Kernel Server.
To be more persuasive, you may add that for Ryzen U and X, anything under custom Kernel is a waste of electricity.
Regards,
Mike
Bug Location In The Tumbleweed Installer
INSTALLATION SETTINGS PAGE
Network Configuration:
-Switch to wicked
-Switch to network manager
This double switching action triggers WIFI circuitry on first boot. It enables its full functionality, not as for the previous tweak(s).
nmcli general status
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
connected full enabled enabled enabled enabled
Tumbleweed Alongside 1709 GPT Secure Boot Enabled
sudo fdisk -l
Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors
Disk model: SanDisk SDSSDH32
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 4xxxxxxx
Device Start End Sectors Size Type
/dev/sda1 2048 1023999 1021952 499M Windows recovery environment
/dev/sda2 1024000 1228799 204800 100M EFI System
/dev/sda3 1228800 1261567 32768 16M Microsoft reserved
/dev/sda4 1261568 2285567 1024000 500M EFI System
/dev/sda5 2295808 290402303 288106496 137.4G Microsoft basic data
/dev/sda6 290402304 484511743 194109440 92.6G Linux filesystem
/dev/sda7 484511744 500118158 15606415 7.5G Linux swap
mokutil --sb-state
SecureBoot enabled
**Firmware Bug
**
cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-5.0.3-1-default root=UUID=0ae767f0-00ea-4b88-a113-437f2decb99c splash=silent iommu=soft resume=/dev/disk/by-id/ata-SanDisk_SDSSDH3256G_183756420226-part7 quiet