>>>>> "Dynamite" == Dynamite <[EMAIL PROTECTED]> writes:
Dynamite> Try to check the file /etc/host, there must be a line with your ip and Dynamite> alias. Thanks for the advice. My etc hosts file has two lines. One for the loopback address and one for my machine. That file was not changed in upgrading to 2.4.9-31 and when I boot from the old kernel, everything works fine. In looking at some of the logs, I think that it may be a problem in that the new kernel cannot allocate resources for my network card. -- Wojciech Komornicki Dept of Mathematics [EMAIL PROTECTED] Hamline University http://www.hamline.edu/~wnk/ St Paul, MN 55104 USA The skill of writing is to create a context in which other people can think. Edwin Schlossberg wnk> I have just upgraded to kernel 2.4.9-31 using the update tool. wnk> wnk> After upgrading I can no longer connect to my local network. When I wnk> look at the network settings using the network configurator, eth0 is wnk> inactive. When I activate it, after several minutes it shows as active wnk> but if I close down the configurator and open it up again, it shows as wnk> inactive. When I try to ping one of my local machines, I am told that wnk> the network is unreachable -- obviously since my interface is not wnk> active. wnk> wnk> Under 2.4.2, I did not have this problem. Has anyone else encountered wnk> this and knows how to fix the problem. I have looked at the various wnk> configuration files and they do not seem to have changed due to the wnk> upgrade. _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
