Page 2 of 2
Posted: Fri 20 Jun 2008, 03:59
by tempestuous
glassparrot wrote:... uninstall and reinstall the wifi patch which dvw provided.
Just a point of clarification: madwifi-ng-r2756-eeepatch-k2.6.21.7.pet is not a patch. It's a complete driver package.
This driver package was compiled from the r2756 MadWifi source code, with 2 patches applied.
The drivers (modules) installed by this dotpet package are in binary form. The end user does not install a patch.
Posted: Sat 21 Jun 2008, 06:42
by glassparrot
Thanks for the clarification, but honestly I wasn't confused. I was using the term "patch" generically, not specifically.
Thank you for your work on the getting the eeepc compatible as well, tempestuous. I have seen your contributions all over this forum.
Posted: Tue 24 Jun 2008, 18:11
by dinky
@dvw86
Thanks so much!!!! Just got an eeepc today, and following your advice on the previous page have been able to configure it near perfectly... I'm just about ready to wipe Xandros and use puppy...
I'm using TigerPup, with Compiz-Fusion enabled, and it works beautifully. A few bugs to work out, but other than that it's fantastic. Thanks for all the work you've put in!!! I'll post some screenshots soon.
2 Questions:
1. Is it possible to get suspend happening when the lid is shut, like in Xandros? All that happens now is it stays on happily... albeit dimming the screen. How can I change this?
2. With resolution set to 800 x 480, sometimes windows open with parts of them of the screen. Important parts. With Compiz-Fusion set to desktop wall I can get around this, but are there any other options I can configure to stop this from happening?
Great work, keep it up. TigerPup is a remastered version of wNOP, which is based on NOP. Cheers!
~dinky
Posted: Wed 25 Jun 2008, 12:52
by dinky
Just got the Puppy to recognise the internal SD drive as a flash drive, with limited writes. Thought a few people might be interested. See topic here:
http://www.murga-linux.com/puppy/viewtopic.php?t=29620
~dinky
Posted: Mon 30 Jun 2008, 05:55
by stlchuck
Thank you Glassparrot! Having the wireless disabled in BIOS when the wireless package is installed is the key I was looking for. I had a feeling there was a simple answer and that method worked like a charm. I'm currently working with Wolfpup 1.00 - booting from a USB key - but any 3.01 based Puppy should work the same. With a bit more tweaking I'll have a lean, mean puppy that does exactly what I need it to do - without all the unneeded/unused extras that the full versions have.
Thanks to dvw86, Tempestuous, and Glassparrot - keep up the good work guys!