New IT forum Follow us on Twitter
04 February 2012, 04:24:20 pm *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: DreamPlug tutorial in Linux Format issue 145!
 
   Home   SHOP Help Search Login Register  
Pages: [1] 2
  Print  
Author Topic: Installing debian  (Read 4065 times)
Guber1
Newbie
*
Posts: 4


« on: 19 May 2010, 07:38:14 am »

Hi, i want to install debian and boot it from esata disk, i have been reading the forum but im not sure that this were possible and how to do it, actually i have esata uboot version from here and im triying to install debian but the installer nevers starts:
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0
Marvell>> reset

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

U-Boot 1.1.4 (Jul 14 2009 - 06:46:57) Marvell version: 3.4.16

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

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
*** Warning - bad CRC or NAND, using default environment


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
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
Abort
Marvell>> reset

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

U-Boot 1.1.4 (Jul 14 2009 - 06:46:57) Marvell version: 3.4.16

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

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
*** Warning - bad CRC or NAND, using default environment


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
Marvell>> setenv serverip 192.168.1.2
Marvell>> setenv ipaddr 192.168.1.147
Marvell>> tftpboot 0x01100000 uInitrd
Using egiga0 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.147
Filename 'uInitrd'.
Load address: 0x1100000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ###############
done
Bytes transferred = 2735033 (29bbb9 hex)
Marvell>> tftpboot 0x00800000 uImage
Using egiga0 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.147
Filename 'uImage'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #############################
done
Bytes transferred = 1811960 (1ba5f8 hex)
Marvell>> setenv bootargs console=ttyS0,115200 base-installer/initramfs-tools/driver-policy=most mirror/suite=stable apt-setup/local0/repository="http://people.debian.org/~tbm/orion lenny main" apt-setup/local0/key=http://people.debian.org/~tbm/orion/68FD549F
Marvell>> bootm 0x00800000 0x01100000
## Booting image at 00800000 ...
   Image Name:   Debian kernel
   Created:      2010-02-12   1:37:09 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1811896 Bytes =  1.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:   debian-installer ramdisk
   Created:      2010-03-30  15:57:01 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    2734969 Bytes =  2.6 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Logged
NewIT_Marcus
Administrator
Hero Member
*****
Posts: 960


« Reply #1 on: 19 May 2010, 06:10:06 pm »

Hi, i want to install debian and boot it from esata disk, i have been reading the forum but im not sure that this were possible and how to do it, actually i have esata uboot version from here and im triying to install debian but the installer nevers starts:

<snip>

Marvell>> setenv bootargs console=ttyS0,115200 base-installer/initramfs-tools/driver-policy=most mirror/suite=stable apt-setup/local0/repository="http://people.debian.org/~tbm/orion lenny main" apt-setup/local0/key=http://people.debian.org/~tbm/orion/68FD549F
Marvell>> bootm 0x00800000 0x01100000
## Booting image at 00800000 ...
   Image Name:   Debian kernel
   Created:      2010-02-12   1:37:09 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1811896 Bytes =  1.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:   debian-installer ramdisk
   Created:      2010-03-30  15:57:01 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    2734969 Bytes =  2.6 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


So this is an online install? What does the documentation say about this stage of the process?
Logged
Guber1
Newbie
*
Posts: 4


« Reply #2 on: 19 May 2010, 06:49:19 pm »

i don't understand your question, i must install manually a tar ball? or whats thw problem with the online instalation?
Logged
NewIT_Marcus
Administrator
Hero Member
*****
Posts: 960


« Reply #3 on: 19 May 2010, 07:52:40 pm »

The point of my question is, you really haven't explained how you are trying to achieve your goal.

This:

Code:
setenv bootargs console=ttyS0,115200 base-installer/initramfs-tools/driver-policy=most mirror/suite=stable apt-setup/local0/repository="http://people.debian.org/~tbm/orion  lenny main" apt-setup/local0/key=http://people.debian.org/~tbm/orion/68FD549F

looks like an online install to me, but I could be wrong and I wouldn't know how an online install works anyway.

In detail, what is the step that you are trying to achieve, and what are the results (the U-Boot stuff that you copied is a series of steps, none of which I recognise as being part of a debian install to eSATA).
Logged
Guber1
Newbie
*
Posts: 4


« Reply #4 on: 19 May 2010, 08:42:43 pm »

ok perhaps i don't explain well my objective, i want to install debian and boot it from a esata disk and triying to do this following this instructions http://www.cyrius.com/debian/kirkwood/sheevaplug/install.html and when installer loads select the esata disk to do the install but i realy don't if this worls or how to do this install on the esata disk.
Logged
akc42
New IT customer
Newbie
*
Posts: 19


« Reply #5 on: 22 May 2010, 10:49:55 am »

ok perhaps i don't explain well my objective, i want to install debian and boot it from a esata disk and triying to do this following this instructions http://www.cyrius.com/debian/kirkwood/sheevaplug/install.html and when installer loads select the esata disk to do the install but i realy don't if this worls or how to do this install on the esata disk.

When you setup the uImage and uInitrd files and boot into them, it should start the Debian Installation.  It should prompt you for some basic information about what language and keyboard layout you have and then ask about partitioning the target device.

You should see a device there that represents the e-Sata disk.  I haven't got an e-Sata device myself (just using the basic plug) but I am pretty sure Debian will call this /dev/sda . It will ask you how you want to partition this device - with a Guided Install as one of the options.  Follow that, and it should install Debian on to your disk in two (possibly three - not sure if it will add a swap partition at the end) partitions.  The first, small one, should be formated ext2 and be the boot partition.  Debian should put a kernal uImage and uInitrd in there that will ultimately be booted by u-boot. The second partition, which will take up the rest of the disk (unless you tell the installer otherwise) will be the rootfs (ie when you have a running system it will have the root of the entire filesystem at this point).  At some point during the installation process Debian will reboot itself into this new system and then try and install the set of software you want (server/desktop etc etc).

I am not 100% sure if this answers the question you asked, as I am not sure exactly what you are asking. 

If you know what you are doing, it is possible to change the partitioning layout, and the filesystems formats that are used, but remember all the instructions about setting up the Sheeva's environment variables make the assumption that the uImage and uInitrd (if there is one) will reside in their own partition at the start of the disk.

You should also understand that there is a difference is the kernel that is used by Debian in that install, and the one used by the folks here at NewIT.  Debian's standard install creates a small uImage with the core of the kernal, and an uInitrd file that contains some of the modules necessary to boot the systems root filesystem.  As far as I can work out the alternative is to use a kernel from http://sheeva.with-linux.com/ which is built with just uImage file and you load the modules post boot. The main benefit of this alternative kernel is that it supports the ubifs filesystem - which is the faster alternative for the internal nand.  You don't need this if you are just using the e-Sata disk (you will use the traditional filesystems).
Logged
Guber1
Newbie
*
Posts: 4


« Reply #6 on: 25 May 2010, 09:54:06 pm »

ok thanks finally i get all work
Logged
maisondouf
Jr. Member
**
Posts: 68


Crazy hacker's family since 1982


WWW
« Reply #7 on: 30 May 2010, 05:45:25 pm »

I'm interested by your environment....

Do you have to use "ide reset" command before reading "uImage" and "uInitrd" from the eSATA disk ?

If yes, to load them do you use this syntax "ext2load ide 0:1 0x.....  uImage" ?

thanks
Logged

NSLU2 owner since 4 years...
Very new owner of a black eSata Sheevaplug.
(Wiki en français http://plug.maisondouf.fr)
pizzulicchio
Newbie
*
Posts: 7


« Reply #8 on: 13 July 2010, 10:19:24 am »


Good day!
I'm trying to install debian on my esata sheevaplug using an esata box with a 2.5 " sata hard disk inside.
Me too I have used this guide: http://www.cyrius.com/debian/kirkwood/sheevaplug/install.html but i'm not be able to boot debian after  installation is finished.

i have set this environment:

setenv mainlineLinux yes
setenv arcNumber 2678
saveenv
reset



I have used the the uImage and uInitrd of Debian Testing Squeeze installer for eSata sheevaplug uploaded using a TFTp server... And i have started the installer with:

setenv bootargs console=ttyS0,115200n8 base-installer/initramfs-tools/driver-policy=most
bootm 0x00800000 0x01100000

I have done the installation using the guided partitioning method and using the entire disk. Partman makes a small boot partition in ext2, a swap partition and a root partition in ext3.
Finished the installation my plug reboots so i reconfigure my plug to boot from esata.

setenv bootargs_console console=ttyS0,115200
setenv bootcmd_sata 'ide reset; ext2load ide 0:1 0x01100000 /uInitrd; ext2load ide 0:1 0x00800000 /uImage'
setenv bootcmd 'setenv bootargs $(bootargs_console); run bootcmd_sata; bootm 0x00800000 0x01100000'
saveenv

but when i try to start the system:

Marvell Serial ATA Adapter
Integrated Sata device found
[0 1 0]: Enable DMA mode
Device 1 @ 0 1:
Model: WDC WD1200BEVS-22RST0 Firm: 04.01G04 Ser#: WD-WXE808NWD688
Type: Hard Disk
Supports 48-bit addressing
Capacity: 114473.4 MB = 111.7 GB (234441648 x 512)
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 00800000 ...
Bad Magic Number
Marvell>>

What is going wrong?
I'm using the only u-boot avaiable: http://www.newit.co.uk/u-boot/uboot-sata-090903.bin
Any help/suggestion is very appreciated.
Thank you
Logged
NewIT_Marcus
Administrator
Hero Member
*****
Posts: 960


« Reply #9 on: 13 July 2010, 02:20:59 pm »

Bad magic number means that your kernel is missing, or unsuitable.

Bad partition is to a degree self-explanatory, but I can't say I've seen this error before from a plug.

Logged
pizzulicchio
Newbie
*
Posts: 7


« Reply #10 on: 13 July 2010, 04:39:26 pm »

I have tried to change u-boot for booting from usb:

setenv bootargs_console console=ttyS0,115200
setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x01100000 /uInitrd; ext2load usb 0:1 0x00800000 /uImage'
setenv bootcmd 'setenv bootargs $(bootargs_console); run bootcmd_usb; bootm 0x00800000 0x01100000'
saveenv

run bootcmd

But same results....

## Booting image at 00800000 ...
Bad Magic Number


And so i have done another test...
i have connected this esata box via usb ( it has a mini usb connector too ) to my IONICS sheeva plug ( nimbus 100 )
It has booted without any problem my fresh debian system that i have istalled using NewIT esata plug with esata port...
That's without sense...

FREE ADVERTISING :-)  NewIT plug has a better engineering and support instead of Ionics product. I say this because it is the truth. There is no comparison on quality of materials. Not to mention their tech support. Not present absolutely!


Logged
NewIT_Marcus
Administrator
Hero Member
*****
Posts: 960


« Reply #11 on: 13 July 2010, 08:36:51 pm »

I take it you don't have access to the Ionics environment variables?

Anyway, did you try

Code:
arcNumber=2097
Logged
pizzulicchio
Newbie
*
Posts: 7


« Reply #12 on: 14 July 2010, 07:33:10 pm »

I have the jtag for ionics plug, sure...
Why?
Otherwise i have try to set the arc number to 2097 as you have suggestedd but nothing is happened... same error

I have try to use another usb box with a different sata disk and setting to boot from usb :

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

U-Boot 1.1.4 (Jul 14 2009 - 06:46:57) Marvell version: 3.4.16

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

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... 1 USB Device(s) found
       scanning bus for storage devices... 0 Storage Device(s) found
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 00800000 ...
Bad Magic Number


And i have try to boot it using e-sata:

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

U-Boot 1.1.4 (Jul 14 2009 - 06:46:57) Marvell version: 3.4.16

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

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

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 1 0]: Enable DMA mode
  Device 1 @ 0 1:
Model: Maxtor 6Y080M0                           Firm: YAR51EW0 Ser#: Y2QSRPME   
            Type: Hard Disk
            Capacity: 78166.2 MB = 76.3 GB (160084415 x 512)

** Bad partition 1 **
** Bad partition 1 **
## Booting image at 00800000 ...
Bad Magic Number

Is my plug  defective or am i mad ?
:-)
( Sure i'm going crazy ...)
Logged
fragfutter
Newbie
*
Posts: 24


« Reply #13 on: 14 July 2010, 08:45:13 pm »

you can't brick the sheevaplug by software. It's one of the nicest user friendliest embedded boards i have seen.

Three things need to fit together, the u-boot version, the kernel version and the u-boot environment.

i would start by transfering the kernel with tftp. You need a tftp server for that. That way you would be sure that you load the correct image. then set the arc and mainline linux variables depending on the kernel. if this works flash the kernel.

Logged
pizzulicchio
Newbie
*
Posts: 7


« Reply #14 on: 14 July 2010, 09:57:49 pm »

I have try to make an installation into an usb key, exactly a Sandisk cruzuer 8GB.
It is be able to boot debian! 
WHY???

That's without sense!

Same, partition, same installer, same repository....
I continue to not understand...
Logged
Pages: [1] 2
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.16 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!