New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The 35network-legacy is still used even if network-scripts isn't installed in Fedora 29 #488
Comments
@lkundrak do you have any suggestions/thoughts about this? |
@nullr0ute I just checked the The relevant code from
|
My understanding is, that without |
Oh, and btw, |
So we're seeing a regression in network related stuff in recent versions of dracut if there's no network link and I'm not sure why that is then. |
@nullr0ute what is the kernel command line? rdsosreport.txt with rd.debug enabled? |
Kernel command line is: |
I don't see any |
This issue is being marked as stale because it has not had any recent activity. It will be closed if no further activity occurs. If this is still an issue in the latest release of Dracut and you would like to keep it open please comment on this issue within the next 7 days. Thank you for your contributions. |
In Fedora 29 there's a lot of use cases where the old initscripts/network-scripts are no longer installed and as of dracut 049 the network bits were split into 35network-legacy and 35network-manager modules but in a lot of cases the network-legacy is still used even if initscripts/network-scripts aren't present.
This seems to cause issues when there's no link on wired ethernet connections and we see timeouts where the device doesn't complete booting with the following errors:
Looking through the modules I can't seem to work out how it chooses the network-manager module vs the network-legacy modules.
The text was updated successfully, but these errors were encountered: