Puppy on the EEEPC?

[rozojc]

There's also something that I really don't get:

I was just looking at the explanation found in http://www.puppylinux.com.

According to that page I could:

1. Use the universal installer and install it to the disk as a flash drive (which would only generate like 3 files)
2. Make a complete install to the hard drive, which would generate a complete linux system structure, files, folders, etc.
3. Make a frugal install to the hard drive, which generates the same 3 files or so as the install to flash drive option.

Which is recommended for my scenario? I mean, my partition will be a blank ext3 partition. So, assuming I have my laptop with solid state drive containing only one ext3 partition should I:
a) Use the Universal installer and choose the "flash drive" option
b) Use the Universal installer, go for complete install, and choose frugal
c) Use the Universal installr and tell it to take the entire partition...

Again, really sorry to ask so much but although I'm not clueless regarding Linux in general, I am completely clueless regarding Puppy linux...

[raffy]

No, you have a good grasp of things. I guess our problem here now is "learning by doing". Please get hold of any flash device and get started experimenting with it, and see for yourself the results.

Good luck.

[PaulBx1]

My guess is the hardware is made to emulate a disk drive, even if it is flash, for compatibility. So you would not choose flash install in the Universal Installer unless you wanted to put Puppy on a USB flash key.

If I were you I would not mess with the default Xandros installation; the manufacturer probably invested a lot in making that useful. It also may have some eeepc-specific utilities, etc. Instead, install Puppy on a USB flash key and run that way for a while. Maybe later you might try something else, like installing Puppy on the internal flash "disk".

[macadavy]

PaulBx1: I think you've offered really good advice (why didn't I think of it?). I hope you'll keep us posted about your experience, rozojc...

[rozojc]

PaulBx1: I think you've offered really good advice (why didn't I think of it?). I hope you'll keep us posted about your experience, rozojc...

Definitely! I already created a Virtual machine with puppy in it to be able to experiment with the different types of installations. There is one option, however, which I what I suppose I have to choose (Install to a CF connected to IDE). This options seems to be "You will install to something that is recognized as a hard drive, but which you know is really Flash memory, and therefore writes will be kept to a minimum"

So apparently that should be my choice. I've been having some trouble getting some things to work (like the user contributed package for XFCE, but I'm getting there).

I'll keep you posted of everything (unfortunately it seems they are going to move the release date... again...)!

Thanks again for all the useful info!

[macadavy]

rozojc: Reason I ask is 'cause you're one of the first I've heard of who gets a chance to play with the eeePC. Looking at the specs it seems Puppy-perfect, 'cause Puppy is totally into 'low-end' machines.
We have a fair amount of experience with USB flash drives (I'm running Lighthouse Puppy on a 4GB Kingston DataTraveler) but I haven't seen a lot of mention of IDE CF. So we're happy to help wherever we can, and you can help us by letting us know how it goes!

[MyPup]

I have been looking at these for awhile with great anticipation I was hoping to wait for the 8 or 16gig version. I believe that the 8gig will be released the end of November. I know that there are many flavors of puppy that should work with this unit and as we all know certain versions of puppy work better than others just depends on the individual machine. I am looking forward to getting one soon and trying fatfree3 with some add ons like ezpup3 or maybe the new revpup 213 a remaster of one of my favorite puppy versions. From all the various EEEPC sites out there I have found that they will boot from sd slot although, I haven't heard at what speed the sd slot is. I really hope that puppy will be tweaked by someone as a specialty for this particular pc as many of you are interested in the device. I hope that it will be able to boot as fast as the distro that comes with the unit which is between 20-27 seconds depending on the youtube video or sites you can visit. I will be getting mine from http://www.allasus.com/ Looking forward to some fellow puppy fans enjoying a new tiny sub notebook hopefully running puppy Linux on it.

[rozojc]

Well, someone seems to have tried Puppy, but there seem to be problems with both the Ethernet and the WiFi.

You can read it at:
http://forum.eeeuser.com/viewtopic.php?id=778
BTW, that page is for EEE users in case you're interested

[raffy]

The USB installation procedure is OK, and I posted there about the possible solutions:

If you start the network wizard from the setup menu, you will see a button "Load module" (driver). This will require some knowledge of the chip that is in your network device. Both wired and wireless devices are included there.

The wifi is an atheros chip: "The Eee PC uses an Atheros AR5BXB63 wireless module for 802.11b/g wireless Internet access." ( http://www.brighthand.com/default.asp?newsID=13453 )

ath_pci module is in Puppy.

There is an old version specially built to address new devices, the 2.17.1. Maybe you can try this. Hopefully, version 2.17.1 can load the SSD. Get it via http://puppylinux.net/download/downpage.htm

[Lobster]

Did Asus miss the chance for this level of cuteness?


Be interesting to see how xandros compares to Puppy
http://puppylinux.org/wikka/HardwareTesting

Any screenshots yet?

Here is Puppy on Intels Puppy


http://www.desktoplinux.com/news/NS7384572891.html

woof woof

[BlackAdder]

Deb Shinder writes newsletters for XP and Vista, but she has her hands on an Eee. You can read some of her comments here. It is the second post on that page; follow the link for more. She comments that the operating system takes 2.4GB, so I don't know how people would go with the 2GB model. 9 seconds to boot - she says. Wow!

[headfound]

someone has loaded Puppy 2.14 on an sd card AND got networking going!
(post 11)

http://forum.eeeuser.com/viewtopic.php?id=152

[pinzoy]

... and here's the online screen !


Using ndiswrapper and the windoze driver in the supplied CD.
Only works with WEP at the moment.
I'll try fiddling around with WPA supplicant soon.

Have fun... Yay!
http://farm3.static.flickr.com/2355/199 ... f2.jpg?v=0

Still can't figure out how to display the photo in this post

[macadavy]

Easily done, pinzoy (we all had to learn).
After you've written your post scroll to the bottom to the section: 'Add an Attachment' and enter a URI (like the one in your post) and add any comments you want, then click on 'Add Attachment'. If you wish to check things before submitting the post, just click on 'Preview' to make sure everything is as you want it, then click 'Submit'.
Simple, eh - care to try again?

[raffy]

Using the image link, just enclose it in the [img] BBcode (see the button above the editing window).

[azieser]

Ok I looked on the EEEPC forum and also this forum and they mention that you need to blacklist the ath_pci file see EEE PC Forum Site:

1. Go to a terminal as root.
2. Edit /etc/modprobe.d/blacklist using your favorite editor (nano /etc/modprobe.d/blacklist)
3. Add the following lines:

blacklist ath_pci
blacklist ath_hal

4. Restart the computer
5. To configure ndiswrapper, unzip the Windows drivers of your WiFi card somewhere (/home/jdoe/drivers in this example. The driver itself is usually).
6. Open up a terminal and go to that location (cd /home/jdoe/drivers)
7. Add the driver to ndiswrapper (ndiswrapper -i ./net5211.inf*)
8. Run: modprobe ndiswrapper
9.You also want to make sure ndiswrapper loads on startup. add ndiswrapper to /etc/modules

* (net5211.inf is avalible from the within the Asus EeePc 701 Support DVD Rev:1.1 at location:

[raffy]

Thanks for the booting info. I have posted a suggestion here. Let us know how it goes.

BTW, what is the name of the SSD drive after Puppy was booted from it? Is it sda, sdb, hda or hdb? The default drive (with Xandros) and the new SSD boot device should be visible when you use the mount utility. Having a picture of this will be sweet.

[azieser]

In Puppy right click on the desktop to bring up the program listings, go to system then select "BootManager configure bootup" This will bring up a window that has 3 buttons click on blacklist a module. This opens a window up with two columns select from the left column ATH_PCI and click the add bar to move it to the right column, then pick the ATH_HAL on the left column and move it to the right column.

Reboot your EEE PC after it starts up again these modules will be blacklisted then click on the connect icon and goto Connect to internet by network interface. Click Load Module and select the more tab. Then select the NDISWrapper and select the driver from the wireless folder from the EEE PC Restore dvd and follow the prompts it will connect to the wireless card now because the ATH drivers are out of the way.

I hope this makes it a little easier for other people to get their EEE PC's online and it bypasses the need for manually editing files in your system.

[azieser]

Thanks for the booting info. I have posted a suggestion here. Let us know how it goes.

BTW, what is the name of the SSD drive after Puppy was booted from it? Is it sda, sdb, hda or hdb? The default drive (with Xandros) and the new SSD boot device should be visible when you use the mount utility. Having a picture of this will be sweet.

Well it booted from the SD card not the SSD drive. Actually it sees the SD card as sda and the SSD Drive as hdc Also I am running the new TMXXINE Puppy Linux that came out today, it has everything you could possible want already loaded onto it and the ICEWM themes are excellent.

[raffy]

eee as the platform for Tmxxine time travel - how impossibly true.

Thanks, azieser. (And thanks again for resizing that desktop image to fit the board.)

As to blacklisting, I wonder if it is needed in Puppy, especially if the Network Wizard has not picked up any "ath" module.

Plus, if you had to reboot, then you must already be using a pup_save in your SD card. Using the Network Wizard at first boot should be cool (if that is at all possible).