I guess considering the lack of movement on this bug, the only real longterm solution is to not use an ASrock motherboard. I know my next motherboard will either be a Gigabyte or an Asus.
In the meantime though, as a workaround, here's something else you can try: First remove any of the other modifications or workarounds you may have tried from above. Then, edit /etc/modprobe.d/blacklist.conf Below the line that reads: "blacklist evbug" Add a line that reads: "blacklist forcedeth" Save your changes and restart your computer. If all went well, you should *not* have network access. Ubuntu should pop-up a notification saying there's no network access, and the network icon in the top bar should just sit there, instead of spinning and spinning. Log in to your account. Open the terminal and type: "sudo modprobe forcedeth msi=0 msix=0" Your network icon should then spin for a bit and you should get network access. If this works for you, you'll have to use the above command every time you first log into your computer, but it's perhaps the easiest way to work around this issue until they finally fix this bug, if they ever do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003297 Title: Networking and ACPI conflicts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1003297/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
