Thanks John and Dale. udev was the culprit and everything is now fixed.
Cheers,
Mark
On Sat, Aug 27, 2011 at 6:24 PM, cov...@ccs.covici.com wrote:
Mark Knecht markkne...@gmail.com wrote:
I meant to do ifconfig -a or just ifconfig eth1 or eth2 and see if you
get anything and change your link
Hi,
I've been helping a friend over the phone who's trying to fix a
networking problem. This machine was built a month ago running
something like 2.6.39-gentoo-r2. Networking worked great. I do not
know what driver it was using, but it worked great.
Two weeks ago we updated the machine to
Mark Knecht markkne...@gmail.com wrote:
Hi,
I've been helping a friend over the phone who's trying to fix a
networking problem. This machine was built a month ago running
something like 2.6.39-gentoo-r2. Networking worked great. I do not
know what driver it was using, but it worked great.
On Sat, Aug 27, 2011 at 4:54 PM, cov...@ccs.covici.com wrote:
Mark Knecht markkne...@gmail.com wrote:
Hi,
I've been helping a friend over the phone who's trying to fix a
networking problem. This machine was built a month ago running
something like 2.6.39-gentoo-r2. Networking worked
cov...@ccs.covici.com wrote:
I bet udev renamed the device -- check and see if you have eth
anything. Udev does things like that.
I would suspect the same thing. If that is what it is doing, delete
this file, unless you really need it for some custom settings, and reboot.
Mark Knecht markkne...@gmail.com wrote:
I meant to do ifconfig -a or just ifconfig eth1 or eth2 and see if you
get anything and change your link in /etc/init.d to that. You could use
the persistent-net-rules and rename it to eth0 as well.
--
Your life is like a penny. You're going to lose
6 matches
Mail list logo
