• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 2 3 [4] 5 6 ... 9
Author Topic: Sheevaplug installer - alpha-6 release - Testers needed  (Read 49089 times)
mike
Jr. Member
**

Karma: 2
Posts: 55


View Profile
« Reply #45 on: June 25, 2009, 01:24:14 PM »

Hi,

I am having a tough time with the alpha6...

Here's the console out I get.

Mike



         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (May 13 2009 - 13:10:52) Marvell version: 3.4.16

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CF100

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (May 13 2009 - 13:10:52) Marvell version: 3.4.16

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CF100

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
reading uImage

** Unable to read "uImage" from usb 0:1 **
Device NOT ready
   Request Sense returned 06 28 00
** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **

NAND erase: device 0 offset 0x100000, size 0x400000
Erasing at 0x4e0000 -- 100% complete. Cleanmarker written at 0x4e0000.
OK

NAND write: device 0 offset 0x100000, size 0x400000

Writing data at 0x4ff800 -- 100% complete.
 4194304 bytes written: OK
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
## Booting image at 00800000 ...
Bad Magic Number

Logged

Rabeeh Khoury
Administrator
Full Member
*****

Karma: 5
Posts: 218


View Profile
« Reply #46 on: June 25, 2009, 02:22:02 PM »

Looks like the problem is on detecting the USB stick -

Code:
** Unable to read "uImage" from usb 0:1 **
Device NOT ready
   Request Sense returned 06 28 00

Which USB stick are you using? (brand)

Oh - could it be that you are using USB HDD and U-boot timeouts too fast before the drive mechanics spins up?

Anyhow, can you try different USB drive? Possible a simply USB stick?

Don't forget to load all the content of the installer/* to the root directory of the USB stick (FAT32 formatted).
Logged

mike
Jr. Member
**

Karma: 2
Posts: 55


View Profile
« Reply #47 on: June 26, 2009, 09:06:46 AM »

Hi,

I'm using a USB pendrive... not a HDD. I don't know the brands.  I've tried a couple of them that I have hanging around. I reformatted them to FAT32 before using them.  Below is my current output from the console.  Can't really spend much more time on this... Any ideas? 

Mike


         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (May 13 2009 - 13:10:52) Marvell version: 3.4.16

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CF100

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
egiga0 no link
mvEgigaInit: egiga1 mvEthPortEnable failed (error)
mvEgigaInit: egiga1 failed
Using egiga0 device
TFTP from server 10.4.50.5; our IP address is 10.4.50.165
Filename 'uImage'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
## Booting image at 02000000 ...
Bad Magic Number
Marvell>>
Logged

Rabeeh Khoury
Administrator
Full Member
*****

Karma: 5
Posts: 218


View Profile
« Reply #48 on: June 26, 2009, 10:12:00 AM »

Somehow you switched to TFTP boot. Did you change anything?

I suggest you start the installer from the beginning.

Send also the dump of the ./runme command.

Logged

mike
Jr. Member
**

Karma: 2
Posts: 55


View Profile
« Reply #49 on: June 26, 2009, 10:15:46 AM »

I'll run it again.  Below is the dump from the runme.sh


Thanks,
Mike




mike@mike-laptop:~/plug$ sudo ./runme.sh
 ****   Preparing environment variables file ...
grep: installer/uboot-custom.txt: No such file or directory
 ****   Burning uboot and environment variables ... This will take few minutes ...
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-10:32) svn:1800M


BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS


$URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $
2000 kHz
dcc downloads are enabled
Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2)
Info : JTAG Tap/device matched
Error: unknown EmbeddedICE version (comms ctrl: 0x00000018)
Warn : no telnet port specified, using default port 4444
Warn : no gdb port specified, using default port 3333
Warn : no tcl port specified, using default port 6666
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 5 to 6 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
wrote file uboot-env.bin to NAND flash 0 up to offset 0x000c0000 in 32.415634s
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078
NAND flash device 'NAND 512MiB 3,3V 8-bit' found
successfully erased blocks 0 to 4 on NAND flash device 'NAND 512MiB 3,3V 8-bit'
Warn : keep_alive() was not invoked in the 1000ms timelimit. GDB alive packet not sent! (1010). Workaround: increase "set remotetimeout" in GDB
wrote file uboot.bin to NAND flash 0 up to offset 0x00073000 in 116.364677s
 ****   U-boot should be up and running now. Open your console ...
Logged

Rabeeh Khoury
Administrator
Full Member
*****

Karma: 5
Posts: 218


View Profile
« Reply #50 on: June 26, 2009, 10:24:21 AM »

uboot binary and it's env variables seems to be written correctly from the log.

what's happening now on the plug side?
btw - which serial terminal utility are you using? I typically use putty on my Linux PC to connect to the plug, which works without issues.
I know if you use 'minicom' in the installer, things might go wrong (something that has to do with the minicom dial-up functionality).

Another alternative way is trying -

( sudo ./runme.sh ; cu --nostop -s 115200 --line /dev/ttyUSB1 ) 2>&1 | tee install.log

Note that this is a developer kit. Typically the package comes with a load of patience that you can use  Wink
Logged

mike
Jr. Member
**

Karma: 2
Posts: 55


View Profile
« Reply #51 on: June 26, 2009, 10:45:07 AM »

Getting the same thing after rebooting the plug... 

 maybe i'm just doing something incredibly dumb...  so, to check, here's what I am doing:

1.) format usb stick to FAT32
2.) copy contents of intall directory to root of usb
3.) plug usb into sheeva
4.) plug serial cable from laptop into sheeva
5.) power cycle sheeva
6.) fire up putty

I see the u-boot screen pop up.  I let the timer expire.  the sheeva tries to tftp the file.

Hmmm...

I don't mind using tftpd...  I have the tftp-hpa daemon running on my host machine.  I can drop the uImage into my tftp directory.  

Could I configure the plug to do this maybe?

Mike


Logged

Rabeeh Khoury
Administrator
Full Member
*****

Karma: 5
Posts: 218


View Profile
« Reply #52 on: June 26, 2009, 11:14:39 AM »

You are defintely doing the right thing. I still can't understand why it's going through tftp, while it should go through reading from USB stick as you first reported -

Code:
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
reading uImage

** Unable to read "uImage" from usb 0:1 **
Device NOT ready
....

Lets just try back again getting a full dump of everyrthing. Maybe this time you want to try a third usb stick -
1. Power cycle the plug (unplug it from the wall and plug it back again).
2. Connect the mini USB connector.
3. Make sure you have /dev/ttyUSB0 and /dev/ttyUSB1 devices appear in the kernel log /var/log/messages (if you see /dev/ttyUSB2 or else, it means that you have other usb to serial devices in your laptop)
4. Don't open putty for now. We will use 'cu' application. Make sure it's installed too (apt-get install cu on Debian/Ubuntu).
5. Run the following two commands (as root) -
Code:
chown uucp /dev/ttyUSB1
( ./runme.sh ; cu --nostop -s 115200 --line /dev/ttyUSB1 ) 2>&1 | tee install.log

Then please post the whole install.log file.

BTW -
Using tftp would make things a bit difficult, since you need to boot uImage from tftp, NFS mount the rootfs.tar.gz.
The installer was intended to automate all the installation with minimum effort.
Logged

mike
Jr. Member
**

Karma: 2
Posts: 55


View Profile
« Reply #53 on: June 26, 2009, 11:45:10 AM »

Here's the /var/log/messages tail output:

Jun 26 14:28:00 mike-laptop kernel: [11512.832030] usb 2-2: new full speed USB device using ohci_hcd and address 28
Jun 26 14:28:00 mike-laptop kernel: [11513.074358] usb 2-2: configuration #1 chosen from 1 choice
Jun 26 14:28:00 mike-laptop kernel: [11513.078068] usbserial_generic 2-2:1.0: FTDI USB Serial Device converter detected
Jun 26 14:28:00 mike-laptop kernel: [11513.078465] ftdi_sio: Detected FT2232C
Jun 26 14:28:00 mike-laptop kernel: [11513.078904] usb 2-2: FTDI USB Serial Device converter now attached to ttyUSB0
Jun 26 14:28:00 mike-laptop kernel: [11513.112106] usbserial_generic 2-2:1.1: FTDI USB Serial Device converter detected
Jun 26 14:28:00 mike-laptop kernel: [11513.112542] ftdi_sio: Detected FT2232C
Jun 26 14:28:00 mike-laptop kernel: [11513.113051] usb 2-2: FTDI USB Serial Device converter now attached to ttyUSB1



Attached is the log file... looks like it is timing out....

Mike





* install.log (16.47 KB - downloaded 167 times.)
Logged

restamp
Global Moderator
Sr. Member
*****

Karma: 4
Posts: 273


View Profile
« Reply #54 on: June 26, 2009, 08:11:39 PM »

I just wanted to report, while the details are still fresh in my mind, that this afternoon I upgraded my Plug using the alpha-6 installer.  It was ultimately successful, and I am delighted with the results, but it took me a couple attempts to succeed, and I'd like to record the pitfalls in the hope that they might be of benefit to someone else.  BTW, thus far, I am similarly delighted to see that this version of the OS seems much fuller-featured.  It does seem to support loopback devices, and it does recognize my USB-to-serial cable -- something I intend to start testing with soon.

On the first attempt, the new Uboot and Uboot-environment installed fine from openocd (whew!), but the procedure errored-out while trying to invoke the installer software on the thumb drive.  After the failure, I got into the new Uboot and tried to manually investigate what was going on.  What I found was that the usb start command was failing -- 1 USB Device(s) found... 0 Storage Device(s) found.  After resetting the Plug, the command would succeed once -- 2 USB Device(s) found... 1 Storage Device(s) found -- and then fail on subsequent invocations until the Plug was again reset.

So, I reset the Plug, broke out of the Uboot boot sequence to the "Marvell>>" prompt, and then ran the installer again.  This time it worked beautifully.

I do have a couple questions:

+ What is the 2nd USB device that the usb start command finds (and I suppose this is the one that it finds all the time, even on its subsequent invocations)?

+ I changed the ethaddr in the uboot-custom.txt of the installer to my MAC address before running the install.  However, I elected not to change orion_nand to orion_mtd.  The way I read the comments, this change should have been made.  I did not do this because I figured if it needed to be changed, it would have been.  Is this comment wrong?

+ I did not change the bootargs_root even though I want to eventually utilize an SDcard for the root file system (and even boot off of this device at some point, now that I have the new Uboot that supports this).  I wasn't really sure what to change this argument to, so I elected to leave it alone.  Perhaps it would be better if there were commented-out bootargs_root examples for the SD card and USB stick options, so that we could simply uncomment the one we desired.

+ Now that I'm up and running on the new OS, how do I convert to using the SDcard?  Can I simply follow the wiki ( http://www.openplug.org/plugwiki/index.php/SD_Card_As_Root_File_System ) and copy the filesystem to the SDcard and then essentially change bootargs_root to "root=/dev/mmcblk0p1", like I did the last time?  (Do I still need to set up the ubifs if I do this, and if so, how do I do this -- perhaps "bootargs_root=ubi.mtd=1 root=/dev/mmcblk0p1"?  What happens if I want to access the mtd partitions while running from the SDcard?  I suppose I need an active ubifs to do so.)

+ Now that I have a Uboot that can boot from the SDcard, if I want to upgrade to the latest 2.6.30 kernel, can I do so by simply copying it onto the SDcard root partition and boot from there, thus bypassing the mtd/NAND entirely (and can someone provide the bootargs to do this)?

That's enough for now.  Again, my thanks to Rabeeh for all his hard work in producing this excellent installer, and thanks in advance to anyone who can give me some advice on the questions I've asked here.
Logged

restamp
Global Moderator
Sr. Member
*****

Karma: 4
Posts: 273


View Profile
« Reply #55 on: June 26, 2009, 10:03:27 PM »

Addendum:  After copying the filesystem from the pristine Unix I loaded earlier to the SDcard, I changed the Uboot environment from:
Code:
bootargs_nand=ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
to
Code:
bootargs_root=root=/dev/mmcblk0p1 rw,relatime
and successfully booted with the SDcard as my root FS.

I don't believe I can access the MTD root partition from Unix while running in this mode, as I don't think the UBI layer is present to allow it (right?), but that is not a problem for me at the current time.  However, if someone knows how to properly set up the UBIFS, while still running on the SDcard as root, I'd appreciate you filling in the details for me.
« Last Edit: June 27, 2009, 09:57:08 AM by restamp » Logged

mike
Jr. Member
**

Karma: 2
Posts: 55


View Profile
« Reply #56 on: June 29, 2009, 08:47:32 AM »

Hi,

I reloaded my alpha-6 installer on my Linux host.  I'm using a 3rd USB stick.  The plug does not seem to like it either.

See: "** Unable to use usb 0:1 for fatload **"


any ideas?

Mike


Re-running provides the following output:PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
Marvell>>
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (May 13 2009 - 13:10:52) Marvell version: 3.4.16

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CF100

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (May 13 2009 - 13:10:52) Marvell version: 3.4.16

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CF100

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Flash:  0 kB
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
reading uImage

** Unable to read "uImage" from usb 0:1 **
Device NOT ready
   Request Sense returned 06 28 00
** Can't read from device 0 **

** Unable to use usb 0:1 for fatload **

NAND erase: device 0 offset 0x100000, size 0x400000
Erasing at 0x4e0000 -- 100% complete. Cleanmarker written at 0x4e0000.
OK

NAND write: device 0 offset 0x100000, size 0x400000

Writing data at 0x4ff800 -- 100% complete.
 4194304 bytes written: OK
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done
## Booting image at 00800000 ...
Bad Magic Number
Marvell>>


Logged

mgillespie
Full Member
***

Karma: 8
Posts: 239



View Profile
« Reply #57 on: June 29, 2009, 11:41:03 AM »

Should be getting my SheevaPlug in the close future (today is when deliveries arrive from manufacturer Ihave been told).  Thinking of updating with this before I start tinkering.

Are there any updated alphas planned soon?  Should I wait until A7 arrives?  Does it contain the updated "Open U-boot" (is this the same as "DAS U-boot"?) which boots faster?    Lots of information to take in, lots of different information, Lots of informtion written by people that know what they are doing!!!!

Slightly put off updating because it's got a 2.6.30 RC kernel, rather than the final of 2.6.30.  Would rather wait if I knew there was one in the cooker and coming soon...

Thanks.
« Last Edit: June 29, 2009, 01:35:26 PM by mgillespie » Logged

Rabeeh Khoury
Administrator
Full Member
*****

Karma: 5
Posts: 218


View Profile
« Reply #58 on: June 29, 2009, 01:40:57 PM »

Mike,

I think I found the issue. It might be related to the fact the u-boot doesn't like non partitioned USB sticks.
Please check if your USB stick FAT32 filesystem is straight on the USB stick or under partition (when mounted, do you see /dev/sdb1 or /dev/sdb, given that you USB is at /dev/sdb)

If it's /dev/sdb then you should fdisk the USB stick, create a FAT32 partition on it (first partition), format it and then copy the installer/ directory to it's root.

I reproduced a similar problem today with my plug, and partitioning the USB stick solved the problem.

I'll provide a patch for this soon.

Regards,
Rabeeh

Logged

mike
Jr. Member
**

Karma: 2
Posts: 55


View Profile
« Reply #59 on: June 29, 2009, 02:01:33 PM »

Hi,

Ouch...  Dumb mistake on my part.... I added the sdb1 partition and all works great now. 

For those who might find it helpful, here's what I did:

1.) fdisk /dev/sdb to set up the device
2.) mkdosfs /dev/sdb1 to create the partition
3.) mount the /dev/sdb1 to a directory I created (/media/disk)
4.) copy in the content of the install directory (from the alpha 6 download) to the newly created /media/disk
5.) unmount the usb
6.) attach the usb to the plug
7.) start up putty
8.) reboot the plug

And it all works.
Logged

Pages: 1 2 3 [4] 5 6 ... 9
Print
Jump to: