(old)Puppy Linux Discussion Forum

Hey Dougal,

Turned out to be faulty hardware. IE: The 16 bit PCMCIA card. Confirmed it using several OS and laptops. The card would turn on, blink, throw back a hit every now and then and then finally no hits at at. The laptops would pick up the card and the LED would flash through all steps like normal. Very annoying. It's taken a week off working on my Libretto only pupplet,

That's always a potential issue with old hardware unfortunately.

I have replacements coming via eBay. The nice thing about old hardware is it's cheap, if not free to replace.

Thanks for all your help.

The tip about loading the module through the bootloader was great. No more need to mess with rc.local . i82365 module works fine on the Libretto 50, 70, 100, 110 laptops. The "# this driver is broken and should not be loaded automatically" is probably the reason why it's turned off in Puppy at boot up. Without it. PCMCIA is not detected at all.

Again thank you for your time and attention to this. You went well above and beyond.

Hopefully, some of the issues I posted above will help you troubleshoot faulty hardware as being the cause if it comes up again in the future.

What I don't understand is why there isn't a download link on page 1 of this post with the latest version or on your last post, I looked around 10 of 40 pages here and nothing, not a single link.
ttuuxxx

i think dougal removed it after some discussions with whodo. but you'll find the last updated version here:

http://www.murga-linux.com/puppy/viewtopic.php?t=40537

aragon

thanks aragon
ttuuxxx

hi
I tried to read the whole thread, but I did not understand the exact procedure to be able to get that puppy 4.2(kernel 2.6.25.16) autoconect network wireless. Can someone help me figure out which files I need and what to do?
thank you

Yes, some people do use static ip with wireless.

Fewer dropouts (no issues with dhcp lease renewals)

But also because I am sharing printers through my router to a Ubuntu desktop.

imnotrich wrote:Yes, some people do use static ip with wireless.

Fewer dropouts (no issues with dhcp lease renewals)

But also because I am sharing printers through my router to a Ubuntu desktop.

Anyone who (shame on them) has to use Windoze will find it beneficial as 'doze will relinquish a lease if it goes offline (e.g. it hibernates) which is quite understandable, but then the problem comes when it is woken up again as it will try and use the same I/P address again. Meanwhile the Router may well have allocated it to another user and you have an immediate problem.

It must be feasible to configure it to not behave like this otherwise communities with a large number of users would encounter this all the time, but in my experience most 'doze versions misbehave like this out of the box.

I get round this by assigning the I/P address by MAC address in the Router, so the clients can use simple option to 'Let DHCP allocate the I/P address' and don't need to be any the wiser.

Can anyone tell me what script or scripts need to be re-run after my laptop resumes from standby? I've been reading these long posts for days and I'm sure it is a simple answer...

Please help...

At risk of being outdated here is the answer I know:

Executing the startup script should do the trick.

/etc/rc.d/rc.network

Thanks! I'll give it a shot when I get home!

Works perfectly! Thanks very much!