On Mon, 29 Jan 2007 15:45:46 -0700, Ashley M. Kirchner wrote: > Beartooth wrote: >> I also tried "cat >> /var/log/dmesg|grep eth0" and got nothing. >> > Try grepping for 'eth' in /var/log/messages. See if that produces > anything. I have some machines whose drivers get logged there as > opposed to dmesg. OK, that got me two screensful >> What should I be looking for in that log?? >> > Something akin to: > > Jan 29 06:59:35 trinity kernel: e100: eth0: e100_probe: addr 0xf4020000, > irq 3, MAC addr 00:02:B3:BE:02:87 I see several lines containing things like "eth0 alias e100" or "eth1 alias 3c501" -- and also a whole bunch containing expresions like "//etc/sysconfig/networking/devices/ifcfg-eth0" or the same with "-eth1" -- but none with addr nor MAC addr. [...] > The fact that it's so old might not be such a bad thing. Sometimes > because a cadr has been around for so long, there's a good chance its > driver has too. On the other hand, it's also possible that the driver > has been ripped out of the current source code and you'd have to do > things manually to get it working again. > > Like I said, let's start by checking to make sure the system knows > the hardware is actually present. Grep /var/log/messages and let me know. -- Beartooth Staffwright, PhD, Neo-Redneck Linux Convert Remember I know precious little of what I am talking about.
