Comment 28 for bug 40763

Revision history for this message
jerico (jerico-dev) wrote :

I tried the following:
- uninstalling NetworkManager -> network still doesn't go up automatically
- reinstalling + reconfiguring NetworkManager -> again no result
- blacklisting padlock_aes: This keeps the modprobe warning out of my log but does not resolve my problems
- blacklisting intel_rng (to avoid another error message in my kern.log): the above problems persist

Especially the fact that the network is not starting automatically is really annoying as I am not using my computer on the console. I use it as a local samba server. Now every time I want to start the server I have to go to another room, log in on the console and start the network before I can access the server...