On 09/05/2015 11:45 PM, Felix Miata wrote:
Before buying anything I would confirm the onboard NIC got "fried" by doing a BIOS reset, just in case the hit caused BIOS corruption rather than NIC destruction.
Awesome! Resetting the BIOS seemed to work - I am back on-line via ethernet, and not just wireless anymore. Thanks for that, saved me a trip and some money! The system behaved kind of funny when I first booted back up. Using network manager, I connected to both the wireless and ethernet. Then all of a sudden, the ethernet connection shut off. I tried to go back to yast and switch over to wicked, and yast manage network devices got hung up for almost an hour trying to pull back from that. I couldn't kill the process or anything. I finally just had to reboot, and when I did, it was back in wicked, and both the wired and wireless are running together now. It seems like Network Manager doesn't handle a wired connection very well. I use it fine on my laptop with wifi, but on my desktop I couldn't get it to manage the wired connection. It would frequently just drop the wired connection - all that happened both before and after the lightning strike. When I switched to wicked, both before and after the lightning strike, it connected without a problem. Anyone else have this same problem? I don't know if I should be running both at the same time - the wireless connects on a different network than the wired connection. The wired network is inside the wireless - I had to do that because the steel in the walls of my house prevent a strong wireless signal from going through the whole house. But, my network connection seems to not only be running, but a bit faster now, as one of my downloads is coming through in about half the time as normal when just on the wired connection. -- George Box #1: 13.2 | KDE 4.14 | AMD Phenom IIX4 | 64 | 16GB Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB Laptop #2: 13.2 | KDE 4.14 | Core i7-4710HQ | 64 | 16GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org