Ask Your Question
1

IPv6 link is not ready Fedora 29 4.20.3 (SOLVED)

asked 2019-01-25 10:42:07 -0500

loboedu gravatar image

updated 2019-01-29 16:49:21 -0500

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:

https://www.if-not-true-then-false.co...

edit retag flag offensive close merge delete

Comments

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.

loboedu gravatar imageloboedu ( 2019-01-29 15:49:15 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted
2

answered 2019-01-28 19:40:47 -0500

lovepump gravatar image

I am seeing similar problems with some wireless Realtek adapters with newer kernels in other distributions. Since they are "wireless" the unplug/replug cable doesn't apply, and physically removing USB adapters and plugging them back in isn't really a "solution", even if it "works".

Unload and reload the NIC driver using rmmod "driver" or modprobe -r "driver", then modprobe "driver" to bring it back.

This is sort of working for me.

edit flag offensive delete link more

Comments

Thank you for your answer.

I've just tried your workaround: unloaded and reloaded the four drivers related to the usb wireless adaptater: rt2x00lib, rt2800lib, rt2x00usb and rt2800usb, but nothing changed.

I don't know if this is normal, but as the system was booting the kernel-4.19.15 just now, I was able to read the last lines and they were also IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready . Despite the "same error line", the system was able to boot up normally... I really don't know what else could be stalling the process.

loboedu gravatar imageloboedu ( 2019-01-28 20:18:55 -0500 )edit

Most messages are information messages and not error messages. That includes IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready. This might be followed by a message like

[  218.397199] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u5: link is not ready
[  229.862824] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u5: link is not ready
[  229.912766] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u5: link is not ready
[  241.479334] IPv6: ADDRCONF(NETDEV_UP): wlp0s29f7u5: link is not ready
[  248.775722] IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s29f7u5: link becomes ready
villykruse gravatar imagevillykruse ( 2019-01-29 11:18:50 -0500 )edit

@villykruse, indeed these messages appear even when the system boots correctly, but only then does this last one appear. When the system stalls at the boot process, the message about the link becoming ready never appears. Any ideias on how to force it to happen?

loboedu gravatar imageloboedu ( 2019-01-29 15:13:37 -0500 )edit
0

answered 2019-01-28 12:51:35 -0500

xxdressielxx gravatar image

stumbled across that to, workaround --> just re-plugin (pull out / push in) your LAN cable, i see that the system instantly recognised it and said "Link is up"

edit flag offensive delete link more

Comments

Thanks for answering!

Unfortunatelly, I'm not using a wired connection on this desktop machine, only a USB wireless adapter. Plus, I have already tried removing and reinserting the device, but nothing changed. The system only tells me that a USB device has been removed and that a USB device has been inserted.

So far, my workaround has been booting only with the 4.19.15 kernel...

loboedu gravatar imageloboedu ( 2019-01-28 19:25:24 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2019-01-25 10:42:07 -0500

Seen: 417 times

Last updated: Jan 29