From: Marcus <li...@wo...> - 2007-04-25 17:45:42
|
On Wednesday 25 April 2007 03:45, Kristian Kielhofner wrote: > Grab 0.4.5 and remember the "service network restart" trick. Kris, I tried this and the result is unfortunately "no lease, forking to background". I noticed a boot message scroll by about "try 8139too instead". I guess it may be using the 8139 NIC driver because 8139too is not available? That may explain why eth0 is up, but cannot connect. The NIC driver is not quite the right one. Is that possible? I have the NIC connected to my ADSL router, the one I am using now for my internet connection. That's all, no other network connections. I would then use another PC via wifi to connect to astlinux...when I get an IP. Is that setup correct, or have I missed something? Btw, where are the complete system messages so I can send them to you? dmesg and /var/log/messages get overwritten before I can grab the info you wanted. Astlinux would be the best solution for the thin clients I want to use, so I hope we can find a solution to this networking issue. I don't get the fact that with most any Linux distro I can run pppoeconf and either of the two NICs connected to the router is setup. What can be missing? Thanks again, Marcus |