I’m not sure if this is the most appropriate place, but the problem is likely to be hardware related.
The computer is a Dell Inspiron N5010 laptop. I updated on April 19th, and it was running fine at that time. I didn’t reboot to see if it still worked after the updates. The critical update seems to have been to either “systemd” or “udev”.
When I booted it today, I did not have any network. “systemctl status network” showed the network devices as timing out.
On further checking, I found that “synaptiks” was not working - it was running, but was failing to disable the touchpad due to a mouse being plugged in. And the battery monitor said that I did not have a battery.
I spent some time investigating. Leap 42.1 still works, Windows still works, Tumbleweed still works, and the 13.2 live rescue image still works. But the installed 13.2 has those serious problems.
Fortunately, I was able to get the network working by reconfiguring the ethernet device (I made only a trivial change).
With the network working, I use Yast Software Management to check update history. That showed that I had updated udev and systemd on April 19th. There were about 8 packages updated to version ‘210.1459453449.5237776’. So I reverted those to version ‘210.1456152170.f2b9ea6’. And now the system is back to normal functionality.
I have the same problem. I had to look at the hardware info to get the real name of my NIC - Network Interface Card, then I had to search in the folder
/etc/modprobe.d/
I had to check ALL the blacklist files for my NIC and I found it there. I editted the file to remove the entry and it worked. The next time I rebooted, I had internet connectivity.
I had a workaround that I used until I figured it out:
modprobe NIC //replace NIC with the hardware info of the NIC
would enable my NIC and work temporarily until reboot.