 |
 |
 |
|
 |
You are not logged in.
Hi all,
I managed to boot puppy linux from a usb flash disk.
See http://wiki.eeeuser.com/howto:installpuppylinux on how to do this.
I have not extensively tested my work, but I did notice the network is not working.
FM
Offline
The wired or wireless networking?
Offline
You need NDSI rapper and to use the windoes driver...
Offline
If you can please try it with Ndiswrapper and tell us if it worked! Puppy would be a good option to have a good part of the 4G free!
Offline
neither wired nor wireless works
also no access to the internal SSD.
Not sure if I will have time to dig into this today.
Offline
Let me make some suggestions. I don't have the eeepc yet but I have some ideas about Puppy Linux.
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
Last edited by raffy (2007-10-30 7:52:58 pm)
Offline
I want to help kick off more wiki documentation on this site. If someone would be willing to post Puppy setup/config screenshots and notes to this thread, I would be more than happy to turn it all into a nice wiki article. Or, start your own wiki entry and I can help edit and refine the article.
Offline
See the 11th post here: http://forum.eeeuser.com/viewtopic.php?pid=1922
"..got on the 'net with ndiswrapper and the windows driver included in the CD."
So the use of ndiswrapper takes care of the wifi for now. See the wiki:
http://wiki.eeeuser.com/howto:configurendiswrapper
The module to be "blacklisted" is the same, ath_pci.
Last edited by raffy (2007-11-13 10:46:49 am)
Offline
Here is how I blacklisted the unwanted drivers and added the correct driver.
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.
Offline
That would take care of wireless. What other things are working or not working with Puppy? I'm interested in this, as if it works, Puppy could be a very cool alternative. It is incredibly light, and you can always dump XFCE on top if you want a more complete Window Manager...
Offline
Well all of the other features that I use are working, I am not sure what is not working on the machine. It has detected and can mount the SSD which a lot of the other distros don't seem to be able to do. The USB ports all work, I can use my printer off of it with a USB connection. Remote desktop works fine, although it is really tiny. With the new Txmmine release I have all the programs that I need already installed, Open Office, Gimp, Many vector drawing programs, internet access, web page design, too many to mention. The only feature it does not have that I can find is a power meter for the battery.
I am not sure about the web camera as I really don't use that. But I will try it and see if it is recognized. Also I have no use for a modem, so I am not sure if it works or not as well.
It would be interesting to get someone who actually knows a lot about Linux to do an install and see what is going on under the hood to be sure it will remain stable.
Puppy on the EEE PC, for me at least, seems to offer way more than the actual program that shipped with it.
Offline
Are you running it off from USB, or did you make an install to the SSD? Also, if you did install it, did you make a normal install, or did you make a Flash install?
Offline
I am running it off of the 4 GB SD card that is in the SD Slot in the side of the EEE PC. I made the install as a USB install onto the SD card. This bypasses the SSD Drive hdc entirely. For operations it runs entirely out of ram and off of the SD card.
You should be able to do an install to the SSD Drive if you want to but my intention was to leave the SSD drive intact, and to leave all three USB slots available for additional equipment like a printer and graphics tablet, and portable DVD drive.
I have not seen anyone so far that has actually done an install to the SSD drive but as the drive shows up and puppy recognizes it as hdc it should be able to install on to it using the normal hard drive install.
Last edited by azieser (2007-11-15 1:23:44 pm)
Offline
azieser wrote:
I am running it off of the 4 GB SD card that is in the SD Slot in the side of the EEE PC. I made the install as a USB install onto the SD card.
Would you consider making available the files/image of the SD card? I'd be glad to host it if that is of help.
Thanks!
Offline
Actually, if you could make an image of your puppy installation with ndiswrapper working, etc, it would be cool, as it would be (kind of) a Puppy variation for EEE!
Did you make the webcam work?
Offline
It will be good if Azieser could compress Puppy's pup_save.2fs (from Xandros) then upload or email it, say to raffym |at| gmail |d0t| c o m. It should be small enough when compressed (without Azieser's personal files, of course).
Offline
I have Puppy up and running with ndiswrapper. The few outstanding issues (for now) I need some help with are:
1) I couldn't get sound working (ALSA setup).
2) Screen resolution in xorg is 640x480 stretched. I have tried adding modline as some used it on this forum but no joy.
3) Tapping on the touchpad is not registered as a click.
If these are sorted then Puppy is a viable alternative to Xandros considering the pros and cons on each side.
Edit: I have added to the list...
Last edited by 9a6or (2007-11-24 5:45:25 pm)
Offline
Puppy is my favourite linux distro on my desktop. It is so fast and easy to install.
I would love to see a special made eeepc puppy distro with all drivers preinstalled and configured as far as it is possible. Puppy is very customizable and if the right person does the job, I think this could be faster and smoother than Xandros.
Offline
anybody get sound or wired network working ?
Offline
Good news! I just uploaded breeezy, a Puppy Linux build for the eee at:
http://minipc.org/safepup/index.php?fil … %20eee.htm
This is useful for users who purchased the eee with Windows XP, but want to try Linux, or for Linux users who want to maximize storage by using all of 4 GB disk space in the eee for data.
NB: The microphone and web cam of the eee are not yet operational for this version of breeezy.
The Puppy Linux forum announcement is here:
http://murga-linux.com/puppy/viewtopic. … 160#163160
Offline
Great job raffy, I'll try this on the second Eee in the house (my son's one). At last he can now use his new 2GB SD card for something serious
Offline
Hi Raffy,
Thank you for making this Breeezy live image. I'm having some trouble with it... I tried it on both USB and SD; in both cases, the drives are bootable FAT16. The Eee sees them and is willing to boot from them, but on boot I just get a black text-mode screen with an underscore cursor and nothing else. The bootloader doesn't prompt me at all, and it just hangs there. I've booted this Eee off other distributions on flash drives before.
Here are the disks (sdb1 is the SD and sdc1 is the USB):
Disk /dev/sdc: 4060 MB, 4060086272 bytes 255 heads, 63 sectors/track, 493 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdc1 * 1 493 3959991 e W95 FAT16 (LBA) Disk /dev/sdb: 4026 MB, 4026531840 bytes 124 heads, 62 sectors/track, 1022 cylinders Units = cylinders of 7688 * 512 = 3936256 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 1022 3928537 e W95 FAT16 (LBA)
I sudo unzip'd the files to my drive and used syslinux (the Linux version), leading to this:
total 64772 drwxrwxrwx 2 root root 16384 1969-12-31 19:00 ./ drwxr-xr-x 3 root root 4096 2007-12-27 15:46 ../ -rw-rw-rw- 1 root root 1259776 2007-10-03 18:37 initrd.gz -r--r--r-- 1 root root 9932 2007-12-27 15:35 ldlinux.sys -rw-rw-rw- 1 root root 62930944 2007-12-27 02:46 pup_213.sfs -rw-rw-rw- 1 root root 72 2007-12-27 03:03 syslinux.cfg -rw-rw-rw- 1 root root 24064 2007-06-10 18:51 syslinux.exe -rw-rw-rw- 1 root root 0 2007-12-23 09:03 usbflash -rw-rw-rw- 1 root root 1751220 2007-12-23 09:03 vmlinuz
My Linux syslinux package is:
ii syslinux 3.31-4 Bootloader for Linux/i386 using MS-DOS flopp
Any thoughts on why the bootloader isn't working? Exactly the same behavior on b both drives.
(Incidentally, you can hold escape at the BIOS splash screen to get a boot menu; it's a much easier way than hitting F2 and then changing the BIOS settings, and since neither way is persistent on the Eee, works just as well.)
Offline
Outstanding job raffy!
I have been running Puppy 3.01 for a few months now under VMware, and it has become my favorite Linux distro. Knowing that someone would quickly get Puppy all dialed-in on the EEE, factored heavily into my buying decision.
One tip for folks: After following the instructions at http://minipc.org/safepup/index.php?fil … %20eee.htm I found I also had to use gparted to turn on the 'boot' flag.
My question is 2 fold:
1) Is the Breeezy image ready to go for wireless networking, or does one still need to follow the instructions found here: http://wiki.eeeuser.com/howto:configurendiswrapper
2) Once the above is resolved and I am presented with the Puppy_Network_Setup window for entering my wireless information, am I going to be able to configure it to work with my WPA (Pre shared Key) network? ,,, or is connecting to a WPA network going to much more involved (e.g. http://www.murga-linux.com/puppy/viewtopic.php?t=13008 )
Offline
QwertyGraves wrote:
One tip for folks: After following the instructions at http://minipc.org/safepup/index.php?fil … %20eee.htm I found I also had to use gparted to turn on the 'boot' flag.
Is there some reason why making the partition bootable from gparted would do something different than making it bootable from fdisk?
Offline
Not that I know of. As I mentioned in the post, I run Puppy on main PC under a VM. Since I had that up and running, the GUI approach offered by Puppy is just what I reached for to do the job.
Offline
