IPv6 link is not ready Fedora 29 4.20.3 (SOLVED)
I'm experiencing problems during boot. It holds on during the network interface detection, it seems. Specifically during the IPv6 detection for both interfaces, eth0 and wlan0. It shows IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
and doesn't go further. I am able to switch terminals by Alt+F2
and reboot.
I'm running Fedora29 on an I5, 8Gb RAM desktop with a USB Ralink RT2070 Wireless Adapter running the driver rt2800u.
What is actually tricking to me is that, if I choose the kernel-4.19, nothing wrong happens and the system boots normally. Now, if I choose the kernel-4.20, this problem happens. So, I guess it's not a hardware problem. Besides, I also have a laptop I3, 4Gb RAM with Fedora29 as well and Realtek Wireless Adapter, running with kernel-4.20 without any problems. So, not a kernel problem too, I guess.
Anybody's got any ideas?
FINAL UPDATE (SOLVED): After realizing that the problem laid not on the network interfaces but rather on the graphical display, I began to credit the problem to the NVIDIA driver I installed while still using the kernel-4.19 version. So, using the terminal (tty2) I ran inxi -G
and noticed that the driver spot, instead of "Nvidia", showed "none".
So, I looked on the internet for people having trouble with the 4.20 version associated with NVIDIA Cards and found that If-not-true-then-false updated his guide for installing the Nvidia Driver this very month. And, not for my surprise, but for my delight, one of the updates was a patched installer for the 390.xx Nvidia driver for the kernels 4.19 AND 4.20.
So, now, after reinstalling the Nvidia Driver patched up for the kernel-4.20, the system boots up normally and I can once again be happy! :)
Thanks for all the help, guys! Question is finally SOLVED!
If your problem is somewhat similar to mine, follow this guide, for it might help you:
UPDATE: I've just upgraded the kernel version to 4.20.4-200 and tried booting the system without the USB wireless adapter: still no success, BUT something's come up to me: it may not be a network problem, since this time I had no message about the IPv6 link not being ready. My guess now it that it has something to do it the Plymouth Boot Screen. The last lines appearing at the boot process are:
Started Command Scheduler
Starting Hold until boot process finishes up...
Started Terminate Plymouth Boot Screen
Started Hold until boot process finishes up.