Puppy Linux Discussion Forum

[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/1994505572_e76bbfdff2.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: ”/Drivers/Wireless/ndis5x/net5211.inf”)

ok the files listed do not exist in the puppy directory because when I try to edit this file I can not find it in the directory listed. What am I doing wrong, because puppy runs perfect on the machine with the exception of the wireless. As a work around I have been using an older Dlink Usb wireless adapter and it has been working flawlessly. But I would like to use the internal equipment.

Also just a note on earlier comments the EEE PC has a SD slot on the side that it will boot from like the hard drive, so I just installed the distro onto the SD card and it bypasses the SSD drive entirely. I used the usb key install with a USB adaptor and it works better than it normally does on a USB key.

[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]

[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).

[Teddy89h]

@azieser: do you have wlan and the 800x480 res working?

I just asked Hacao to upload his files on sd-card. would be great, if you could do this as well.

the fine thing: the EEE is always the EEE! One Puppy on sd for every EEE pc! this would be very interesting for those, who prefer winxp on ssd .

thank u very much


pf: is it fast?

[alienjeff]

Taiwanese manufactures are not necessarily your friends. To wit:
http://cliffhacks.blogspot.com/2007/11/asus-eeepc-first-impressions-and-gpl.html
Caveat emptor.

[T_B]

Haven't got an eeepc yet, but it will be delivered soon.
Haven't seen any distro beat the Xandros default distro. It is still more compatible with the hardware and faster (especially booting) than others.
Would love to see anyone take up the challenge and make a customized version for the eeepc.

[Natashquan]

alienjeff, as much as it's good to know that Asus was in violation of the GNU General Public License by not releasing its full source code library, it would help if you just came out and said it instead of dropping a link with no explanation but some ominous statement about Taiwanese manufacturers being shady. More to the point, Asus has since released the aforementioned source, and it is available here:
http://eeepc.asus.com/global/news11272007.htm

Also of note is the announcement on the same page about plans for releasing the Eee PC SDK, though they don't mention a release date.

I can't afford to get an Eee PC for myself yet, but I'm avidly watching to see how this changes the compatibility of Puppy with it. Keep up the good work, guys!

[T_B]

Right now I don't think the right persons are busy trying to get Puppy eeepc ready. Other distros are more lively present on the eeeusers.com forum. I like puppy but if another distro has better results on the eeepc I will go for that.
Most important imo is hardware functionality, booting time and working speed. I think Puppy can beat every other distro on all these points.

I will probably first try the standard Archos distro for a while and after that try Slackware or Arch. I've seen some good reports on that one, only thing bothering me is the booting time. I want the fastest booting time possible.

I'm sure the eeepc will have a great impact on the knowledge and spreading acceptance of Linux. When the eeepc specific distros will come (and they will come I'm sure), we will have the same advantage as Apple. We will all have the same hardware, but a lot more choice

[raffy]

The fastest-booting candidate for the eee is the 214R:
http://murga-linux.com/puppy/viewtopic.php?t=24082

Use the boot parameter "pfix=noramsfs" (put it in syslinux.cfg).