SOLUTION TO WPA WIRELESS PROBLEM
This is a "simple" solution that I used to "fix" this problem, though it doesn't address the underlying problem overall.
After struggling with this for 2 days I thought "hmmm"... noticing that the button says "WPA / TKIP". I checked with my router and noticed that the option I had was for WPA with the "AES" algorithm selected. I changed it to TKIP. Then it didn't like that my password (shared key) is only 8 characters, so I simply added 2 more characters making it a total of 10 characters now.
By changing my router's WPA settings to have "TKIP" and more than 8 characters in the password made it work.
THIS CAN BE A SOLUTION FOR ANYONE ELSE BANGING THEIR HEADS WITH WPA WIRELESS PROBLEMS. Though like I said it doesn't address the problem that puppy doesn't have a solution for WPA / AES... which is something that perhaps should be looked into by developers for future releases.
eeetiger
Thanks luckylucky, let us know how you go with installing eeetiger onto your sd card, and which install you choose. Dougal is redesigning puppy's network wizard, you can check it out here: http://www.murga-linux.com/puppy/viewto ... 132#216132
Might be something useful for you. I've asked about WPA, if this is fixed I'll add it to future releases. Cheers!
~dinky
Might be something useful for you. I've asked about WPA, if this is fixed I'll add it to future releases. Cheers!
~dinky
-
luckylucky
- Posts: 4
- Joined: Wed 20 Aug 2008, 18:30
Hi Dinky,
I'll be installing eeetiger to internal ssd (AGAIN) today. I'm having grub problems. I've tried doing a universal install from a USB but I think it tries to do drive lettering wrong (right from the perspective of the USB drive). I.e. the main hdd (internal ssd) is of course hd0 or hda, but from the USB perspective it shows up as hdc.
So now, today my problem is trying to get grub working with ONLY the internal 2gig ssd of the eee pc. Yesterday I have attempted various methods to get grub working (even "stealing" the boot folder from other machines in desperation and editing the menu.lst) but nothing seemed to work. I'm going to try again to install grub from live CD of eeetiger, and if it fails then I'll just download something else. Does knoppix or gparted live CDs somehow allow for fast grub fixes?
I will do a frugal install, with a small personal save file (which can always grow), and will do a link to the drive out of /root/Desktop where I will save my documents, as you suggested.
I'll be installing eeetiger to internal ssd (AGAIN) today. I'm having grub problems. I've tried doing a universal install from a USB but I think it tries to do drive lettering wrong (right from the perspective of the USB drive). I.e. the main hdd (internal ssd) is of course hd0 or hda, but from the USB perspective it shows up as hdc.
So now, today my problem is trying to get grub working with ONLY the internal 2gig ssd of the eee pc. Yesterday I have attempted various methods to get grub working (even "stealing" the boot folder from other machines in desperation and editing the menu.lst) but nothing seemed to work. I'm going to try again to install grub from live CD of eeetiger, and if it fails then I'll just download something else. Does knoppix or gparted live CDs somehow allow for fast grub fixes?
I will do a frugal install, with a small personal save file (which can always grow), and will do a link to the drive out of /root/Desktop where I will save my documents, as you suggested.
-
luckylucky
- Posts: 4
- Joined: Wed 20 Aug 2008, 18:30
Love Letter For Dinky
Dinky,
I am very grateful to you Dinky for mastering the eeeTiger, and also grateful to the person who mastered the original Tiger. Though I am a predominantly Ubuntu user for years, and will continue to be on most machines, I have to say, after much "playing around" with various distros, that for a 2 gig surf eee pc that the eeeTiger is, IMHO & IMHE, the BEST distro to have on it. Its tiny size allows for plenty of file storage space (unlike most other distros on such a tiny drive), it is loaded with enough useful programs to be versatile & functional, and it is actually pretty. Unlike most of the other Puppy Linux variants I have seen, I don't feel like I'm using some old lame computer, but rather feel like I have a trendy machine, one I'm proud to flaunt & show off to others (I've already gotten a few drools).
I am looking forward to future releases of eeeTiger, and though I have been aware of puppy linux for years I am finally motivated to take it more seriously, and will now take the time to explore & learn all that puppy has to offer. I hope to be able to contribute something useful to the community in the future.
Thank you again Dinky, and everyone involved with this marvelous distro!
I am very grateful to you Dinky for mastering the eeeTiger, and also grateful to the person who mastered the original Tiger. Though I am a predominantly Ubuntu user for years, and will continue to be on most machines, I have to say, after much "playing around" with various distros, that for a 2 gig surf eee pc that the eeeTiger is, IMHO & IMHE, the BEST distro to have on it. Its tiny size allows for plenty of file storage space (unlike most other distros on such a tiny drive), it is loaded with enough useful programs to be versatile & functional, and it is actually pretty. Unlike most of the other Puppy Linux variants I have seen, I don't feel like I'm using some old lame computer, but rather feel like I have a trendy machine, one I'm proud to flaunt & show off to others (I've already gotten a few drools).
I am looking forward to future releases of eeeTiger, and though I have been aware of puppy linux for years I am finally motivated to take it more seriously, and will now take the time to explore & learn all that puppy has to offer. I hope to be able to contribute something useful to the community in the future.
Thank you again Dinky, and everyone involved with this marvelous distro!
Great praise luckylucky, thanks mate. I'm also responsible for TigerPup, though I can't call it original. It's heavily based on wNOP, so kudos goes to tombh for the compiz scripts, and booting automatically from many different computers. Likewise for eeetiger, kudos to dw86 for the scripts specific to the eeepc. Not sure if he created them, but he's where I found them. I'm wanting to rebuild both TigerPup and eeetiger from unleashed at some pont, then I will claim more credit...lol.
Re your grub problems, it shouldn't be that hard. Actually, hdc IS the correct drive, your usb device has read it fine. If you're still having problems, post your grub config file here for me to look at. This is /boot/grub/menu.lst
from wherever grub is installed. Grub is very easy to install on the eeepc701 with 4Gb, and can't imagine it will be any different on the 2G. If we can't figure it out from your menu.lst file, I'll talk you through reinstalling grub. Cheers.
~dinky
Re your grub problems, it shouldn't be that hard. Actually, hdc IS the correct drive, your usb device has read it fine. If you're still having problems, post your grub config file here for me to look at. This is /boot/grub/menu.lst
from wherever grub is installed. Grub is very easy to install on the eeepc701 with 4Gb, and can't imagine it will be any different on the 2G. If we can't figure it out from your menu.lst file, I'll talk you through reinstalling grub. Cheers.
~dinky
Hi rhadon, that shouldn't be hard to fix. I think you just need to tweak your syslinux config file, or something similar. Can you give me a list of files on your 2G card which works (booting eeetiger, if I'm correct), and also on your 16G card (which has all the files, but doesn't work). I'm looking for the list of files when you read the card from eeetiger booted from the usb flash drive. Are you with me? So boot into eeetiger from the usbflash, put your card in the reader, mount it and tell me the names of all the files there. You may have to click on the drives icon on the dockbar to open "mut", and manually mount it. I'm not sure if the card reader is recognized automatically. I'm specifically looking for the boot file, which will be something like syslinux.conf, depending on what you've installed to boot it. To be on the safe side, just list all the names of the files on both cards, and let me know which is which. If it's working before, we can get it working again. Cheers.rhadon wrote:Hi dinky, that was the fastest answer I've ever got! Thank you. Sorry, for your confusion, that was my fault. English is not my first language, so it takes time for me to write, more time to write what I mean and sometimes there is a difference between what I mean and what I write.
My 900 has internal 4G and 8G where XP is installed. I used eeetiger with an external card (SDHC, 16G) in the card reader. I have no external cd-rom, so I think, I installed eeetiger on my eeepc in this way:
Burning the iso-file to a CD-RW in another notebook.
Booting it there and installing eeetiger with the universal installer to an USB-stick (TOSHIBA, 4G).
I booted my eeepc with this USB-stick and installed eeetiger on the 16G- SDHC-card in the card reader.
Unfortunately I can't remember exact what I did 2 month ago, I know only it was a lot. But that was past and I don't think its the reason for the troble I have now.
I've made a complete copy of all files on the SDHC- card when it worked fine and I copied the 2fs-file to the USB-stick. It works. Booting from the USB-stick is no problem, no matter I boot the 2fs-file or pfix=ram.
Trying to Install eeetiger now which I boot from that USB-stick to an old 2G-SD-card in the card reader is no problem. Only installing eetiger to the big 16G-SDHC-card fails with the message I posted before. No matter I boot with the 2fs-file or pfix=ram.
During installation I choose USB Flash drive, than sda USB2.0 CardReader SD0.
Puppy finds sda: vfat, size 15,31 GiB.
i choose 'Install Puppy to sda'.
Next it makes no difference choosing the standard Linux console with pfix=nosplash or choosing 1024x768x256 frame buffer console.
Every time I get the message I posted before and the SDHC-card is empty.
In the meantime I copied back all the files I backed up before to the empty SDHC-card, boot flag on. I tried fat32 and ext3. No matter, if I try to boot from the card reader, screen is going to black and I see a white twinkling underline in the upper left corner and that's all.
I hope this informations will be more clearly and helpful.
~dinky
Hi dinky,
I'm very glad about your optimism, here are the informations:
Files from 4GB-USB-stick (bootable)
file:///mnt/home/pup_save-Tosh02.2fs 512.0MB
file:///mnt/home/pup_save-tiger2.2fs 768.0MB
file:///mnt/home/pup_301eeetiger.sfs 235.3MB
file:///mnt/home/madwifi-hal-0.10.5.6-r3698-k2.6.25.11.pet 418.2kB
file:///mnt/home/ldlinux.sys 9.9kB
file:///mnt/home/isotostick.sh 5.9kB
file:///mnt/home/isobuster_all_lang.exe 4.3MB
file:///mnt/home/initrd.gz 2.5MB
file:///mnt/home/Everest_GE_Databases.zip 9.7MB
file:///mnt/home/Everest_EN_Databases.zip 14.5MB
file:///mnt/home/asus_acpi-071127-k2.6.25.11.pet 28.9kB
file:///mnt/home/AFUDOS_XP_080514.zip 23.6kB
file:///mnt/home/900-ASUS-0802.zip 401.6kB
file:///mnt/home/zdrv_301.sfs 17.5MB
file:///mnt/home/vmlinuz 1.7MB
file:///mnt/home/usbflash 0B
file:///mnt/home/syslinux.cfg.orig 74B
file:///mnt/home/syslinux.cfg 74B
file:///mnt/home/QDictionary.zip 3.2MB
Files from the 16GB-SDHC-card (not bootable):
file:///mnt/sda1/zdrv_400.sfs.test 17.6MB
file:///mnt/sda1/zdrv_301.sfs 17.5MB
file:///mnt/sda1/vmlinuz 1.7MB
file:///mnt/sda1/usbflash 0B
file:///mnt/sda1/syslinux.cfg 74B
file:///mnt/sda1/pup_save-tiger2.2fs 768MB
file:///mnt/sda1/pup_301eeetiger.sfs 235.3MB
file:///mnt/sda1/OpenOffice-2.3.1.sfs 139.5MB
file:///mnt/sda1/lve_version_3.iso 628.5MB
file:///mnt/sda1/ldlinux.sys 9.9kB
file:///mnt/sda1/jre-6u7-linux-i586.bin 18.8MB
file:///mnt/sda1/java-1.6u7.pet 33.5MB
file:///mnt/sda1/initrd.gz 2.5MB
file:///mnt/sda1/2008-03_PCWL-eBooklet.pdf 18.2MB
Both syslinux.cfg-files are identical:
default vmlinuz initrd=initrd.gz pmedia=usbflash vga=normal pfix=nosplash
Now I installed eeetiger with universal installer to the 2GB-SD-card (booting works):
file:///mnt/sda1/initrd.gz 2.5MB
file:///mnt/sda1/ldlinux.sys 9.9kB
file:///mnt/sda1/pup_301eeetiger.sfs 235.3MB
file:///mnt/sda1/syslinux.cfg 58B
file:///mnt/sda1/USBFLASH 0B
file:///mnt/sda1/vmlinuz 1.7MB
file:///mnt/sda1/zdrv_301.sfs 17.5MB
syslinux.cfg:
default vmlinuz initrd=initrd.gz pmedia=usbflash vga=773
Then I copyed these files manually to the 16GB-SD-card:
All files are there but still not possible to boot from it.
So I made an Imagefile with Pudd from the 2G-card and restored it to the 16GB-card: all files are there but booting is not possible.
I'm not familiar with the way datas will be stored on cards but I think cards have also a 'hidden' part, e.g. where boot flag or a possible bootloader will be stored. In the meantime I think there is a fault. If I'm wrong, (I hope so) or if you see another possibility, please tell me. If not, do you know a possibility to test this part of the card?
Thank you very much for spending your time to such a stupid problem.
rhadon
Edit:
I found an older Info from you in TigerPup- section and changed the
syslinux.cfg to:
default vmlinuz initrd=initrd.gz pmedia=usbflash append vga=785 layerfs=aufs
no success.
I'm very glad about your optimism, here are the informations:
Files from 4GB-USB-stick (bootable)
file:///mnt/home/pup_save-Tosh02.2fs 512.0MB
file:///mnt/home/pup_save-tiger2.2fs 768.0MB
file:///mnt/home/pup_301eeetiger.sfs 235.3MB
file:///mnt/home/madwifi-hal-0.10.5.6-r3698-k2.6.25.11.pet 418.2kB
file:///mnt/home/ldlinux.sys 9.9kB
file:///mnt/home/isotostick.sh 5.9kB
file:///mnt/home/isobuster_all_lang.exe 4.3MB
file:///mnt/home/initrd.gz 2.5MB
file:///mnt/home/Everest_GE_Databases.zip 9.7MB
file:///mnt/home/Everest_EN_Databases.zip 14.5MB
file:///mnt/home/asus_acpi-071127-k2.6.25.11.pet 28.9kB
file:///mnt/home/AFUDOS_XP_080514.zip 23.6kB
file:///mnt/home/900-ASUS-0802.zip 401.6kB
file:///mnt/home/zdrv_301.sfs 17.5MB
file:///mnt/home/vmlinuz 1.7MB
file:///mnt/home/usbflash 0B
file:///mnt/home/syslinux.cfg.orig 74B
file:///mnt/home/syslinux.cfg 74B
file:///mnt/home/QDictionary.zip 3.2MB
Files from the 16GB-SDHC-card (not bootable):
file:///mnt/sda1/zdrv_400.sfs.test 17.6MB
file:///mnt/sda1/zdrv_301.sfs 17.5MB
file:///mnt/sda1/vmlinuz 1.7MB
file:///mnt/sda1/usbflash 0B
file:///mnt/sda1/syslinux.cfg 74B
file:///mnt/sda1/pup_save-tiger2.2fs 768MB
file:///mnt/sda1/pup_301eeetiger.sfs 235.3MB
file:///mnt/sda1/OpenOffice-2.3.1.sfs 139.5MB
file:///mnt/sda1/lve_version_3.iso 628.5MB
file:///mnt/sda1/ldlinux.sys 9.9kB
file:///mnt/sda1/jre-6u7-linux-i586.bin 18.8MB
file:///mnt/sda1/java-1.6u7.pet 33.5MB
file:///mnt/sda1/initrd.gz 2.5MB
file:///mnt/sda1/2008-03_PCWL-eBooklet.pdf 18.2MB
Both syslinux.cfg-files are identical:
default vmlinuz initrd=initrd.gz pmedia=usbflash vga=normal pfix=nosplash
Now I installed eeetiger with universal installer to the 2GB-SD-card (booting works):
file:///mnt/sda1/initrd.gz 2.5MB
file:///mnt/sda1/ldlinux.sys 9.9kB
file:///mnt/sda1/pup_301eeetiger.sfs 235.3MB
file:///mnt/sda1/syslinux.cfg 58B
file:///mnt/sda1/USBFLASH 0B
file:///mnt/sda1/vmlinuz 1.7MB
file:///mnt/sda1/zdrv_301.sfs 17.5MB
syslinux.cfg:
default vmlinuz initrd=initrd.gz pmedia=usbflash vga=773
Then I copyed these files manually to the 16GB-SD-card:
All files are there but still not possible to boot from it.
So I made an Imagefile with Pudd from the 2G-card and restored it to the 16GB-card: all files are there but booting is not possible.
I'm not familiar with the way datas will be stored on cards but I think cards have also a 'hidden' part, e.g. where boot flag or a possible bootloader will be stored. In the meantime I think there is a fault. If I'm wrong, (I hope so) or if you see another possibility, please tell me. If not, do you know a possibility to test this part of the card?
Thank you very much for spending your time to such a stupid problem.
rhadon
Edit:
I found an older Info from you in TigerPup- section and changed the
syslinux.cfg to:
default vmlinuz initrd=initrd.gz pmedia=usbflash append vga=785 layerfs=aufs
no success.
Interesting. Lets wipe your 16 G card totally, after copying any files you want to save of course. Then boot into eeetiger from your usb. Open gparted, and totally wipe the card. reformat it so it's clean, choosing the file system on the 2G card (this is for simplicity, really shouldn't matter what you use, assuming you don't need to encrypt it, this only works on fat16 and fat32 for puppy 3.01 and derivitives).
Then go to puppy universal installer, and do a fresh install of eeetiger. It should work. Make sure you choose syslinux for your boot manager. Once finished, rename the syslinux.conf file to syslinux.conf~ and copy the syslinux.conf file from your 2G card across to it. Try that, and let me know how you go.
~dinky
Then go to puppy universal installer, and do a fresh install of eeetiger. It should work. Make sure you choose syslinux for your boot manager. Once finished, rename the syslinux.conf file to syslinux.conf~ and copy the syslinux.conf file from your 2G card across to it. Try that, and let me know how you go.
~dinky
Hi dinky,
your first § was no problem for me. I deleted all the files with the file manager, in gparted I deleted the Partition, built a new one as primary, formatted it with FAT32 and set the boot flag on. Copied all files (last post, last table) from 2GB card to the 16 GB card and run the universal installer: Installing doesn't work:
In universal installer I choose USB Flash drive, next (which drive to install to): sda USB2.0 CardReader SD0.
Next window: In the upper half of the window, Puppy found out about the choosen drive: sda: vfat, size 15.31 GiB and there is the button 'Install Puppy to sda'.
The lower half informs that drive is currently in Superfloppy mode and has no MBR and no partitions. Clicking the appertaining button opens gparted where I can see sda1 with FAT32, boot flag on.
I think here is a possible problem: it seems to me, that the universal installer only detects the drive sda as in gparted I can see the partition sda1.
If I click the upper button 'Install Puppy to sda:'
Next window informs that I have chosen ...the entire drive... Superfloppy mode with no MBR and no partitions.
Next window is named 'configure bootloader to use frame buffer console': I tried standard (with bootparameter pfix=nosplash) and 1024x768x256 without any bootparameter. Next is the 'FINAL SANITY CHECK' -> 'ENTER' and I see the message:
Making sda bootable...
syslinux: this doesn't look like a valid FAT filesystem
mount: mounting /dev/sda on mnt/data failed
copying vmlinuz...
Creating syslinux.cfg...
Creating marker file for wakepup boot floppy...
Copying inird.gz...
Copying .sfs files...
umount: cannot umount /mnt/data: Invalid argument
Finished, press ENTER key to continue.
Formatting disks, there is often the choice quick format - safe format. I have the suspicion, gparted runs a quick format or someething similar. Maybe here is the problem? Please tell me if you think I'm on the wrong tack or if you have another idea.
In the meantime I will do what I did the last weeks: searching in forums, try and error, hoping for 'try and success', and often feeling like a single-bit-shiftregister.
with best regards
rhadon
your first § was no problem for me. I deleted all the files with the file manager, in gparted I deleted the Partition, built a new one as primary, formatted it with FAT32 and set the boot flag on. Copied all files (last post, last table) from 2GB card to the 16 GB card and run the universal installer: Installing doesn't work:
In universal installer I choose USB Flash drive, next (which drive to install to): sda USB2.0 CardReader SD0.
Next window: In the upper half of the window, Puppy found out about the choosen drive: sda: vfat, size 15.31 GiB and there is the button 'Install Puppy to sda'.
The lower half informs that drive is currently in Superfloppy mode and has no MBR and no partitions. Clicking the appertaining button opens gparted where I can see sda1 with FAT32, boot flag on.
I think here is a possible problem: it seems to me, that the universal installer only detects the drive sda as in gparted I can see the partition sda1.
If I click the upper button 'Install Puppy to sda:'
Next window informs that I have chosen ...the entire drive... Superfloppy mode with no MBR and no partitions.
Next window is named 'configure bootloader to use frame buffer console': I tried standard (with bootparameter pfix=nosplash) and 1024x768x256 without any bootparameter. Next is the 'FINAL SANITY CHECK' -> 'ENTER' and I see the message:
Making sda bootable...
syslinux: this doesn't look like a valid FAT filesystem
mount: mounting /dev/sda on mnt/data failed
copying vmlinuz...
Creating syslinux.cfg...
Creating marker file for wakepup boot floppy...
Copying inird.gz...
Copying .sfs files...
umount: cannot umount /mnt/data: Invalid argument
Finished, press ENTER key to continue.
Formatting disks, there is often the choice quick format - safe format. I have the suspicion, gparted runs a quick format or someething similar. Maybe here is the problem? Please tell me if you think I'm on the wrong tack or if you have another idea.
In the meantime I will do what I did the last weeks: searching in forums, try and error, hoping for 'try and success', and often feeling like a single-bit-shiftregister.
with best regards
rhadon
Hi dinky,
I solved my problem-
At last I run the HP USB disk storage format tool (XP) from eeepc. Before I wrote my first post here I tried it with another notebook and an external card reader. Now I know that this couldn't work. After formatting, the universal installer detected partition sda1 on sda, only boot flag was missing. I set this with gparted (the flag 'lba' was marked by HP tool) and installing was no problem.
After this success I run gparted again, deleted the partition on sda, build it new and formatted again with fat32, setting only boot flag. It worked again.
So the HP tool did something while formatting, gparted didn't.
Let me say thank you again because you gave me hope were I hadn't much.
Now i try to wait patiently for the next version of eeetiger. You have my best wishes.
rhadon
I solved my problem-
At last I run the HP USB disk storage format tool (XP) from eeepc. Before I wrote my first post here I tried it with another notebook and an external card reader. Now I know that this couldn't work. After formatting, the universal installer detected partition sda1 on sda, only boot flag was missing. I set this with gparted (the flag 'lba' was marked by HP tool) and installing was no problem.
After this success I run gparted again, deleted the partition on sda, build it new and formatted again with fat32, setting only boot flag. It worked again.
So the HP tool did something while formatting, gparted didn't.
Let me say thank you again because you gave me hope were I hadn't much.
Now i try to wait patiently for the next version of eeetiger. You have my best wishes.
rhadon
Thanks rhadon, glad you got it working. Still not sure what you did, and how you managed to use XP to get the mbr working again. Sounds like somehow the MBR was erased, and you were trying to install it in Superfloppy mode.... anyway, glad it's sorted. Slowly working on next version of eeepc, will let you know when it's out. Cheers.
~dinky
~dinky
-
Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Hi Dinky 
A relative had found an Eeepc that no one claimed
He got a charger
and it was booting into Xandros OK
Then for some reason it stopped working
I tried installing Xandros from my CD and from a borrowed CD
No luck, then I installed Eeetiger to USB
and finally on to the internal IDE flash dive
Success!
Below is the procedure
also available here
http://tmxxine.com/wik/wikka.php?wakka=TigerPup
Tiger Power!
Lobster Installation Guide:
It is probably best to use the Xandros default OS
and run Eeetiger from USB keydrive by pressing Ctrl + Esc during boot
This will install EeeTiger to the Eeepcs internal drive taking over the Xandros OS
You will need a 512 or more USB key drive
1. Download the Eeetiger ISO
2. Boot from CD and install to the USB using the Universal Installer
Make sure USB is bootable (you may have to use gparted - choose the 3rd boot option)
3. Boot from USB key drive by pressing Ctrl + Esc during boot and choose the USB device
4. When Eeepup loads run the universal installer
5. Run Gparted
6. Format the hdc1 (internal drive) to 16FAT and set the flag to boot when prompted
7. Reboot from USB
8. Click on the USB icon to mount
9. Run the Universal installer
10. Install to IDE flashdrive
11. Follow the instructions, select the Barry recommended boot option - 3rd option)
A relative had found an Eeepc that no one claimed
He got a charger
and it was booting into Xandros OK
Then for some reason it stopped working
I tried installing Xandros from my CD and from a borrowed CD
No luck, then I installed Eeetiger to USB
and finally on to the internal IDE flash dive
Success!
Below is the procedure
also available here
http://tmxxine.com/wik/wikka.php?wakka=TigerPup
Tiger Power!
Lobster Installation Guide:
It is probably best to use the Xandros default OS
and run Eeetiger from USB keydrive by pressing Ctrl + Esc during boot
This will install EeeTiger to the Eeepcs internal drive taking over the Xandros OS
You will need a 512 or more USB key drive
1. Download the Eeetiger ISO
2. Boot from CD and install to the USB using the Universal Installer
Make sure USB is bootable (you may have to use gparted - choose the 3rd boot option)
3. Boot from USB key drive by pressing Ctrl + Esc during boot and choose the USB device
4. When Eeepup loads run the universal installer
5. Run Gparted
6. Format the hdc1 (internal drive) to 16FAT and set the flag to boot when prompted
7. Reboot from USB
8. Click on the USB icon to mount
9. Run the Universal installer
10. Install to IDE flashdrive
11. Follow the instructions, select the Barry recommended boot option - 3rd option)
Hi Lobster, thanks for that. Great instructions, if a bit different from how I've done it before. Couple questions. When the internal drive is formatted to fat16, does eeetiger recognise it as a usb drive, or a flash medium? I've only tried formatting the internal drive as ext 2 or ext 3, as there are more possibilities. However, using a fat system means you can also encrypt the save file, as that's broken with ext2 and ext3 partitions in Puppy 3.01.
Anyway, on a frugal install the intermittent saving to disk (30 minutes or so) only works on the internal drive with an edited init... or so I thought... canyou check this for me? Look for the PUPMODE file, I think it's in /etc/rc.d/, though I can't check that right now. If it's set to pupmode 13 we have liftoff... and I'm guessing with this you're talking about a frugal install, not full...
I've been working on eeetiger based on Puppy4, though I don't have much to speak of at the moment. I do know it will be alot smaller, roughly 150 to 160Mb or so. Possibly smaller still if I include most of the programs in an sfs extension. Also looking at replacing wbar with avant window navigator.
Still having issues getting the rebuilds from unleashed booting correctly and installing Compiz-Fusion. I'm planning a total re-write of eeetiger, and eventually TigerPup from unleashed. The boot time should be faster as well, using the default pebble bootsplash. Anyway, will post more when I've done more... could be some time, so don't hold your breathe. My wife is due any day now, with our second baby on the way. Cheers matey, and thanks for your enthusiasm.
~dinky
Anyway, on a frugal install the intermittent saving to disk (30 minutes or so) only works on the internal drive with an edited init... or so I thought... canyou check this for me? Look for the PUPMODE file, I think it's in /etc/rc.d/, though I can't check that right now. If it's set to pupmode 13 we have liftoff... and I'm guessing with this you're talking about a frugal install, not full...
I've been working on eeetiger based on Puppy4, though I don't have much to speak of at the moment. I do know it will be alot smaller, roughly 150 to 160Mb or so. Possibly smaller still if I include most of the programs in an sfs extension. Also looking at replacing wbar with avant window navigator.
Still having issues getting the rebuilds from unleashed booting correctly and installing Compiz-Fusion. I'm planning a total re-write of eeetiger, and eventually TigerPup from unleashed. The boot time should be faster as well, using the default pebble bootsplash. Anyway, will post more when I've done more... could be some time, so don't hold your breathe. My wife is due any day now, with our second baby on the way. Cheers matey, and thanks for your enthusiasm.
~dinky
-
Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
Flash medium.When the internal drive is formatted to fat16, does eeetiger recognise it as a usb drive, or a flash medium?
I had to return the Eeepc this morning - so can not answer the other question.
I created a new ethernet cable for the router to his Linux machine (better than wifi anyday) and tested it on Eeetiger - worked OK
I formatted to fat 16 because of compatibility and usability.
Good luck with the sprog (baby) and great to hear of a new EeeTiger.
Keep on your toes, Barry might be creating a Classmate/Eeepc puplet and Tom seems keen to try new stuff . . .
Also be aware of LIT which provides major 4.xx series software links
http://www.murga-linux.com/puppy/viewto ... 732#229732
-
bingobetty
- Posts: 1
- Joined: Fri 12 Sep 2008, 23:51
nice distro - my experiance of eeetiger
Gotta say I love this but was having some sound problems. I got the sound working (on an eee701) for the media player but then on reboot no sound whatsoever.
What worked for me (after a few trys).
Firstly set the xfce mixer "wannabe master" to "front,0"
Then in the music player app that gave choppy sound set the sound driver to ALSA.
Now I can say I fooking love it! Booted off an SD card on the train from London and peeps were looking over their shoulders at the compiz effects and stuff!
Top work everyone!
What worked for me (after a few trys).
Firstly set the xfce mixer "wannabe master" to "front,0"
Then in the music player app that gave choppy sound set the sound driver to ALSA.
Now I can say I fooking love it! Booted off an SD card on the train from London and peeps were looking over their shoulders at the compiz effects and stuff!
Top work everyone!
-
LaneLester
- Posts: 209
- Joined: Mon 15 Sep 2008, 01:14
- Location: Rural Georgia, USA
I guess I'm doomed to not run Puppy on the Eee PC. I failed with Breeezy, Puppeee, and eeeTiger. The interesting thing to me is that the symptoms were completely different in every case.
I tried eeeTiger last, and it seemed the simplest and most foolproof approach... although evidently not proof against this fool.
When I selected the USB stick to boot, the Eee quit with "Missing operating system." I looked at the files on the stick, and I noticed that not all of the ones from the .iso were on there. But adding them didn't make any difference.
Both gparted and fdisk showed the stick as bootable. I had used gparted to create an ext2 partition.
The only thing I did out of the procedure was put a zero-byte pup_400.sfs file in the .iso directory. This was needed, because I was doing this in Dingo. I then deleted it from the USB stick before testing it.
Later: Having tried it on a 512 MB stick, I decided to try a 2 GB. While going through the installer, I was reminded about the possible necessity of trying different boot sector things. I had taken the default on the 512 MB stick, and this time I took the mbr.bin approach. The difference when I tried it was the "Missing OS" message just flashed on the screen, and then it immediately went to the Xandros on the internal flash drive.
Lane
Lane
I tried eeeTiger last, and it seemed the simplest and most foolproof approach... although evidently not proof against this fool.
When I selected the USB stick to boot, the Eee quit with "Missing operating system." I looked at the files on the stick, and I noticed that not all of the ones from the .iso were on there. But adding them didn't make any difference.
Both gparted and fdisk showed the stick as bootable. I had used gparted to create an ext2 partition.
The only thing I did out of the procedure was put a zero-byte pup_400.sfs file in the .iso directory. This was needed, because I was doing this in Dingo. I then deleted it from the USB stick before testing it.
Later: Having tried it on a 512 MB stick, I decided to try a 2 GB. While going through the installer, I was reminded about the possible necessity of trying different boot sector things. I had taken the default on the 512 MB stick, and this time I took the mbr.bin approach. The difference when I tried it was the "Missing OS" message just flashed on the screen, and then it immediately went to the Xandros on the internal flash drive.
Lane
Lane
Hi Lane, your problem might be that you're using Dingo. Haven't extensively tested it, but I think the installer for flash medium is hosed. Try downloading the TigerPup iso (parent of eeetiger) and burning that onto a live cd. Then run the 'universal puppy installer', and follow the same steps to create a bootable usb stick. After that, pull the eeetiger files from the iso, and copy them onto the usb in place of the TigerPup files. This should solve your problems. Don't give up, we'll definitely get it going. The other thing to check are the settings in your bios. You need to change your hard disk boot priority... should recognize the usb as another hard drive. Let me know how you go. TigerPup is here: http://www.curiouslegends.com.au/tigerpup/current
~dinky
~dinky
-
aarf
more than occasionally EeePC fails to see the plugged usb. Hold down the escape key when booting and confirm that the usb is in the choices . If it exist there selected it, if it is not there reboot and replug the flash drive. Press/hold the escape key on each boot to be sure of booting what you want.LaneLester wrote:I guess I'm doomed to not run Puppy on the Eee PC. I failed with Breeezy, Puppeee, and eeeTiger. The interesting thing to me is that the symptoms were completely different in every case.
I tried eeeTiger last, and it seemed the simplest and most foolproof approach... although evidently not proof against this fool.
When I selected the USB stick to boot, the Eee quit with "Missing operating system." I looked at the files on the stick, and I noticed that not all of the ones from the .iso were on there. But adding them didn't make any difference.
Both gparted and fdisk showed the stick as bootable. I had used gparted to create an ext2 partition.
The only thing I did out of the procedure was put a zero-byte pup_400.sfs file in the .iso directory. This was needed, because I was doing this in Dingo. I then deleted it from the USB stick before testing it.
Later: Having tried it on a 512 MB stick, I decided to try a 2 GB. While going through the installer, I was reminded about the possible necessity of trying different boot sector things. I had taken the default on the 512 MB stick, and this time I took the mbr.bin approach. The difference when I tried it was the "Missing OS" message just flashed on the screen, and then it immediately went to the Xandros on the internal flash drive.
Lane
Lane
-
LaneLester
- Posts: 209
- Joined: Mon 15 Sep 2008, 01:14
- Location: Rural Georgia, USA
Thanks for the help, dinky! It worked perfectly, even though I cheated and let the installer put the eee files directly on the usb. The first time I ran the installer, it asked me where the files were located, and I pointed to a directory where I had extracted the .iso. Then I had to exit and use gparted, because the installer couldn't use the ext2 on the usb. I changed it to fat16, and I'm pretty sure when I ran the installer again, it didn't ask me where the files were. Maybe it saved that info from the first run.dinky wrote:Hi Lane, your problem might be that you're using Dingo. Haven't extensively tested it, but I think the installer for flash medium is hosed. Try downloading the TigerPup iso (parent of eeetiger) and burning that onto a live cd. Then run the 'universal puppy installer', and follow the same steps to create a bootable usb stick. After that, pull the eeetiger files from the iso, and copy them onto the usb in place of the TigerPup files.
With compiz on the eee, it's like having a new video game to play with! I used compiz with Xubuntu a while back, but I didn't stick with it, because I wanted functionality more than eye candy. I might have gotten things the way I wanted them, but the controls were too confusing and I couldn't find any decent help.
And thanks, aarf, for your suggestion. I've never had any trouble with the usb sticks getting recognized. I wish I could say the same thing for the SD card. I have a 4 GB in there, and it seems totally random whether or not it is seen.
Lane