How do you get puppy to stop hanging up on startup,it seems to not recognise the network connection.I always seem to have this problem every 2nd startup,and I have to set up the network connection again.Is there a way to permanantly set up my eth0 connection?I am running 2.10r1 installed on a sata hard disk.No other problems worth mentioning,great distro!!

I don't use puppy, but I'd hate to leave your drowning. If puppy uses BSD style init scripts then you just need to edit /etc/conf.d/net

If that dosen't exit, puppy dosen't use BSD style and I can't really help you, sorry! If it does post back and we'll talk.

Not that I know of,Ive never hacked into this distro before,so I dont know what scripts it uses,thanks anyway!

You don't have to hack anything, just goto the terminal and type

then

and see if eth0 is listed.

Are you getting a system-freeze or does it look like a 50sec delay while puppy is trying to get an IP from your Access Port (router?). In other words - do you have to reboot?

If your system timesout but stays up can you access rxvt and type ifconfig?

Your right,its a 50 sec delay,but I dont have to reboot,and I can get my connection restarted once puppy loads up,I just dont know why its doing this,and if there is a way to stop it.Ill try rvxt,and type ifconfig and let you know what happens.

Well,there is way too much to type here,but I did notice that where "LO"(loopback)is is when I timeout while booting up.As I said,this only happens every 2nd time I boot up,then I have to reset my eth0 connection.Sorry I cant give more info,Im not very good at this....All I can say is that it didnt happen with earlier versions of puppy I have installed.Once I set the eth0 connection,it stayed up.

Here is what it says when I turn on my computer:
eth0 link up 100 mbps fullduplex
Trying to get IP address from DCHP server(60 sec timeout)
then it repeats this,and after 50 or so secs says:
lo eth0 not responding
then it boots up normaly and I have to reset my connection.
thats all the info I can give,anyone else having this problem?

We figured this out on John Murgas forum,and it just might be a bug.It seems that my modem isnt syncing up with the startup sequence fast enough,causing the bootup sequence to request a 60 sec DCHP query,but sometimes this dosent happen,and all goes well.I end up having to wait for my modem(A DSL modem from Verizon,Westell model 327W)to reset to continue.As I said,annoying .It dosent stop me from logging on to the internet,so I can deal with it,its just odd.Thanks for all the help,and if anyone else is having a similar problem,perhaps it should be reported so a fix can be concocted,just a suggestion.

In your init script you could tell it to pause for several seconds before it attempt to connect to give your modem time to catch up.

I occasionally get a dhcp IP request timeout on pups and Win-PCs on my home network which is controlled by a D-Link DI514 802.11b router.

When the timeouts occur I find that the date of the router has been altered to or some earlier or later year - maybe by an access attempt from some passing road-warrier or some weird handshake from my cable internet ISP during access renewal. Anyway - this plays havok with the router's IP lease-schedules and gives the aforementioned dhcp IP delays & hangups. Resetting the router's date solves the problem.

Now I know the cause it's no longer a problem - maybe this is just a quirk of my system but I thought I'd pass it on.

-------------------
edited 29sep06
As noted above my problem is not puppy-specific - the IP failures also occur on the PCs in W98SE, WME and WXP mode - but I have noticed on a few occasions it is easier to renegotiate an IP in Windoze while pups sometimes need to be rebooted.

Im beginning to think that the type of router we use has alot to do with the way DHCP operates in puppy.In Johns forum,we found out that different modems caused different delays,which sometimes caused our modems to hang.This is a weird phenomenon that Ive only seen happen in puppy.All other distros I have used set the DHCP signal at startup,and thats that.It just works,no hang ups or delays,no need to reset.I think its time for puppy to update to a different way to set their DHCP.The ethernet wizard just aint cutting it.....at least they include Roaring Penguin pppoe,it may require resetting every time you log on,but at least it works.

A modem that suffers slow sync or a DHCP server that does not return an address with a plausible lease expiry time are not the kind of thing that can easily be fixed in Puppy, since Puppy is behaving correctly, and being let down by a different device on the network. Be fair!

That wasnt really meant as a 'shot',just a suggestion to upgrade to what everyone else is using.On all other distros Ive tried and used(more than I can count),they all recognise and start up the dhcp connection automatically,and it stays that way everytime I boot up.What ever puppy is using is a step backward,or at least not fully matured to a point that its automatic yet.DSL is the only other distro Ive used that does this,so it may be a size problem,in which case using rp-pppoe is perfectly acceptable to save space.Ive been using the same equipment to log onto the web for over 2 and a half years now,so I know it isnt my equipments fault as to why Im not getting the wizard to work right,so it must be a problem with it,not me.Sorry to state that,but its true.Puppy is the best distro Ive used in years,so all I want is to see it improve,and to improve all issues must be presented,be they good or bad.Just doing my part to help improve the breed ,so please dont take everything personally,it slows down progress.