I used the VNC viewer from my XP, after setting the network up (ifconfig eth0 <ipaddr> up).
Did you install it on nand/sd?
can you post the android boot print?

Hi Thomas,

Basically you can build the ESIA in windows XP or in Linux VM (like using Ubuntu 10.04 in Virtual Box).
So as I see it you do not have to be a Linux guru to modify the ESIA source code and build it.

spunkiie,

It looks like the uboot could not load the instImg from the USB DOK.
Try to place a file on the DOK and load it from uboot: usb start; fatload usb 0 0x00800000 <your-file-name>

Thomas,

Regarding a distro, I meant Ubuntu 10.04, you could install use alternate iso.

The source of the ESIA is in SourceForge web page

can you specify the plug and model you are working with?

Plugdroid installation is on source forge.

1) esia should flash as normal on NAND and MMC

2) you will have to add "video=vfb:" to bootargs_root. If you add it to bootargs_console, you will not get a console.

3) connect to plugdroid UI using VNC viewer on port 5901 (calendar error is known bug so just hit ok and go on). First attempt may have fuzzy screen so just reboot and connect again.

4) download Android SDK to upload apps and use adb program in SDK bin after uncompressing. Lots if good documentation on adb, but highlight is connecting and uploading apps: adb connect ip:port. If you look at running processes on plugdroid you will see adb server on port 5555 I believe.

Thomas,

The old school inline installer did use these files but the ESIA incorporates them within the source code, so basically you have two options:
1) modify the ESIA source code and build it
2) Post installation apply uboot environment changes

Install 10.04 in VirtualBox VM, I think the ESIA should work out of the box, if not it will resolve any dependency issue.
If you have problems tell me.

Thomas,
basically yes

Yes it does, I tested it

It works better on Linux for several reasons: libusb issues on win, FTDI driver problems with win and the windows USB handling.
I would advise to use Linux native or a VM on Windows.

Basically you can pick whatever distro you like (Debian/Gentoo/Fedora) and add to it all the stuff you need and create an installation 'application'.

nurkkis,

Regarding the uboot not identifying the USB correctly,I have the ionics PlugComputer3.0 which includes 6282 SoC, I burned uboot 3.4.26 and I see that it found the DOK fine, the problem with the installer in this version is that the initrd uses mainline kernel that does not support this SoC version and thus the console is not initialized correctly and the ESIA application can not monitor it and stays stuck @ 10% though installation finishes fine.
If you replace the distro kernel that you burn with Marvell LSP based kernel you should be able to burn any distro without console throwing gibberish.

Attached is a patch that adds mainline 6282Z0 support for those of you that want to work with mainline on 6282.

phampson,
does the above explanation suites your setup?

Hopefully next week.

What uboot version are you using?

Did you set the uboot environment mainlineLinux/archNumber?
AFAIK plugs come with Marvell LSP based Kernel, to work with mainline you must enable Mainline support in uboot

same thing that looks odd, never used it. try without the n8

try using only one DOK at a time.
Are you using a hub in between the plug and the DOK? if so try removing it and simply plug one DOK in one of the plug`s USB ports

Hi nurkkis

When doing the installation do you have only one USB DOK connected to the GuruPlug?
Try pluging it in and via console do the It should print the number of USB  Devices it found, try another DOK if you have, I also experienced some DOK not being found by uboot.
And also try to change the USB port you use (assuming the guru plug you have has 2 USB ports)

Go to ESIA Source Forge page and look at the distros directory, there you can find Debian Lenny/Squeeze, FC12