That is strange, I managed to use it with 8G Kingston and 4G Sandisk Cruzer Blade 4G.

May I respectfully suggest that you update the docs if it is not necessary to use small USB sticks <2 GB ? I think many users could benefit from that information since those small USB sticks are not easily obtainable.

Hi everyone. New Plug Computer adopter here. I hit the 8% Starting on-board installer issue too. I flashed up to the latest U-Boot, per Martin's instructions. I actually didn't go back to version 3.4.16 per this thread that reportedly would let the ESIA requester proceed, and took on faith it would work... and it did! I quit ESIA and went back to PuTTY, and there was the Debian login!

I am also setting up a new website where I document my trials and tribulations.

Some technical details:a. downloaded ESIA ver 2.0.5 and Debian_Lenny from http://sourceforge.net/projects/esia/files/b. followed instructions from document Esia_walkthrough.docc. have 2GB FAT32 USB stick for DOKd. plug has uboot ver 3.4.16 e. tried to install Ubuntu904, same result as in #1

any ideas there? I am able to serial to my plug (original Sheeva, pre-ordered before launch day, no modifications done to it since then, just decided to update it now). using win xp host, downloaded the new uboot from the forums here, put it in the correct place in the esia folder, using putty I rebooted the plug, halted the countdown, then disconnected. started up esia, it found it immediately, I changed the MAC to lower case on the set that had two letters when starting the flash.

let me know what else you ned to assist, thanks

Logged

----------------------------------------------------------

1984At the Winter USENIX/UniForum meeting, AT&T describes its support policy for Unix: "No advertising, no support, no bug fixes, payment in advance."

Hey Rooster, first want to say thanks for this tool! I'm trying to install it on my mac osx, but I'm having trouble getting the FTDIUSBSerialDriver to recognize the sheevaplug. I'm using coolterm terminal program. I followed your instructions and installed the FTDIUSBSerialDriver_10_4_10_5_10_6.mpkg installer package. It installs successfully. Then I added the sheevaplug profiles to the Info.plist file as instructed. I then ran "sudo kextload FTDIUSBSerialDriver.kext" to load the module. However when I try "sudo dmesg" I don't see the driver. Also I tried: "cd /dev" and then "ls -l" and I also don't see the sheevaplug listed. I did try: "sudo touch /Extensions" as well. When I open coolterm and try to rescan the serial port, the sheevaplug won't show up.

Hey Rooster, first want to say thanks for this tool! I'm trying to install it on my mac osx, but I'm having trouble getting the FTDIUSBSerialDriver to recognize the sheevaplug. I'm using coolterm terminal program. I followed your instructions and installed the FTDIUSBSerialDriver_10_4_10_5_10_6.mpkg installer package. It installs successfully. Then I added the sheevaplug profiles to the Info.plist file as instructed. I then ran "sudo kextload FTDIUSBSerialDriver.kext" to load the module. However when I try "sudo dmesg" I don't see the driver. Also I tried: "cd /dev" and then "ls -l" and I also don't see the sheevaplug listed. I did try: "sudo touch /Extensions" as well. When I open coolterm and try to rescan the serial port, the sheevaplug won't show up.

Any ideas would be greatly appreciated.

Okay. So I'm happy to say, I finally got it to work. It must have been how the profiles were added to the Info.plist file. I added them just as you instructed, but I think that some thing about how I added the sheevaplug profiles was wrong. Also, I tried following this post: http://openplug.org/plugforum/index.php?topic=34.0but the "patch" command didn't work. I tried copying the text from the post and place it into a text file, then ran the patch command. Finally, I used the pre-created Info.plist from this website: http://www.plugpbx.org/?page_id=119, and it seemed to work. To save others the anguish, I'm uploading that file so anyone can just download it and replace the one that's there. Just make sure to keep the permissions and ownership the same as the originally installed one.