Not sure what happened, but I have been doing the updates since the beta came out, and this morning my ethernet port was wigging out. Between it and the router, it was just blinking, and would not get an ip address from the router.
then after rebooting a couple times, and playing with the cable, it would come back on and then after a few minutes, it would die again - right in the middle of downloads or whatever.
I don't know if this is related to the -12 kernel upgrade, but that was the last major update pack before I booted up this time.
then, I went to a live cd of suse just to check and see if it might be a hardware problem, and suse pretty much had the same problem.
I know hardware problems happen spontaneously, but the fact that this problem is intermittent and works now, leads me to believe it isn't completely a hardware problem, but that the hardware somehow might be affected by the recent upgrades.
I really don't want to believe that, but the timing is so leading me to believe that the upgrade messed up the eth0 port somehow. I remember the intel ethernet issue, but I have never seen this with my eth0, which is the 8139 flavor.
Just seems like a very bad coincidence that I really don't like.
then after rebooting a couple times, and playing with the cable, it would come back on and then after a few minutes, it would die again - right in the middle of downloads or whatever.
I don't know if this is related to the -12 kernel upgrade, but that was the last major update pack before I booted up this time.
then, I went to a live cd of suse just to check and see if it might be a hardware problem, and suse pretty much had the same problem.
I know hardware problems happen spontaneously, but the fact that this problem is intermittent and works now, leads me to believe it isn't completely a hardware problem, but that the hardware somehow might be affected by the recent upgrades.
I really don't want to believe that, but the timing is so leading me to believe that the upgrade messed up the eth0 port somehow. I remember the intel ethernet issue, but I have never seen this with my eth0, which is the 8139 flavor.
Just seems like a very bad coincidence that I really don't like.
Comment