Re: [cobalt-users] Lost web interface w/ raq4

[Gerald Waugh <gwaugh@xxxxxxxxxxxxxxxxxxxxxxx>]

On Wednesday 05 June 2002 10:38 pm, Jeff Lasman wrote:
> Gerald Waugh wrote:
> > [root /root]# dmesg | grep eth0
> > eth0: Invalid EEPROM checksum 0xc5f8, check settings before activating
> > this device!
> > eth0: Intel PCI EtherExpress Pro100 82559ER, 00:10:E0:02:18:B3, I/O at
> > 0x6200, IRQ 11.
> > [root /root]# dmesg | grep eth1
> > eth1: Invalid EEPROM checksum 0x11f9, check settings before activating
> > this device!
> > eth1: Intel PCI EtherExpress Pro100 82559ER, 00:10:E0:02:19:FF, I/O at
> > 0x6240, IRQ 10.
> >
> > I checked sever RaQ4s and they all say the above
>
> Hmmm... so it does.  There's a difference between grepping the output of
> the dmesg command and grepping the contents of /var/log/dmesg.
>
> Thank you, Gerald, for bringing that to our attention.
>
> So, Jim, that's why my output and yours didn't match.  I'm truly sorry
> for the confusion I caused you.  Now can anyone tell me why they're
> different?
>
> Jeff

the dmesg command is reading the kernel ring buffer, not the file 
/var/log/dmesg file
There will be information in the ring buffer that may or may not be written 
to /var/log/dmesg, depending on how logging is setup

Always use the dmesg command for troubleshooting, boot up issues.
look at "man dmesg "

-- 
Gerald Waugh 
http://www.frontstreetnetworks.com :: Phone. [011] 203.785.0699
Front Street Networks LLC | SOHO Networks & Web Site Hosting
229 Front Street, Ste. #C, New Haven, CT, 06513-3203 United States