Created Multiboot Sheevaplug now need help with ESATA

[stalks]

Hi, this is my first post and having owned a Sheevaplug for the last three weeks and being a complete Linux n00bie  I can honestly say I have learned a great deal, which is awesome!

I have so far changed my bog standard  JFFS2 Ubuntu esata sheevaplug so that it can multiboot from Nand and a 32gb SDCard using UBIFS.  It now acts as my proxy, VPN and remote desktop.

I used the following in my current build on both the Nand and the SD card:

•   rootfs-debian-6.0-squeeze-NewIT-v1.5
•   modules-2.6.36-newit.tar.gz
•   uImage-2.6.36-newit

Information comes from this Post http://www.newit.co.uk/forum/index.php?topic=1996.0


The only problem I seem to be facing now is that I have tried to attach an esata drive to the sheevaplug but when it boots from either the Nand or SDCard I get the following errors:


Waiting for /dev to be fully populated...sata_mv sata_mv.0: version 1.28
sata_mv sata_mv.0: slots 32 ports 2
scsi0 : sata_mv
scsi1 : sata_mv
ata1: SATA max UDMA/133 irq 21
ata2: SATA max UDMA/133 irq 21
ata1: SATA link down (SStatus 0 SControl F300)
ata2: link is slow to respond, please be patient (ready=0)
ata2: SRST failed (errno=-16)
ata2: link is slow to respond, please be patient (ready=0)
ata2: SRST failed (errno=-16)
ata2: link is slow to respond, please be patient (ready=0)
ata2: SRST failed (errno=-16)
ata2: SRST failed (errno=-16)
ata2: limiting SATA link speed to 1.5 Gbps
ata2: SRST failed (errno=-16)
ata2: reset failed, giving up
done.


I am confused as to how I should proceed. I am assuming that because I have used the NewIT files specifically outlined in this POST  for esata plugs that my kernel is correct.  I have seen some posts about changing the UBoot to an earlier version (3.4.16) Enable ESATA booting .   I only really want to attach it as additional storage currently as I am not even sure you can multiboot from eSata?


Any advice would be greatly appreciated.

Regards


StalkS

[NewIT_Marcus]

• Did you test your eSATA connection before you started changing your system?
• What are your environment variables, and is what kernel are you using? Don't refer to another post; please copy & paste the relevant output in your reply.

[stalks]

Marcus,  thank you for taking the time to help me out I really appreciate it.

I had not tested the ESATA functionality until after I had begun to modify the Plug.

UBoot = U-Boot 1.1.4 (Jul 19 2009 - 16:03:28) Marvell version: 3.4.19

Printenv:

Code:

baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=a0000
e=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
bootargs_root=ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
mtdpartitions=mtdparts=orion_nand:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs)
ethaddr=f0:aD:4e:00:41:46
bootargs_console=console=ttyS0,115200
recover1=setenv mainlineLinux yes; setenv arcNumber 2097; setenv bootcmd run recover2; saveenv; reset
recover2=run recover3; setenv bootcmd $(real_bootcmd); saveenv; setenv bootargs $(bootargs_console) $(mtdpartitions) root=/dev/ram0 rw ramdisk=0x01100000,8M install_type=nand; bootm 0x00800000 0x01100000
recover3=run recover4; nand erase clean 0x00100000 0x00400000; nand write.e 0x00800000 0x00100000 0x00400000
recover4=usb start; fatload usb 0 0x00800000 uImage; fatload usb 0 0x01100000 initrd
bootargs_root_nand=ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs
bootcmd_nand=setenv bootargs $(bootargs_console) $(mtdpartitions) $(bootargs_root_nand); nand read.e 0x00800000 0x00100000 0x00400000; bootm 0x00800000
bootargs_root_mmc=root=/dev/mmcblk0p2 rootdelay=5
bootcmd_mmc=setenv bootargs $(bootargs_console) $(bootargs_root_mmc); mmcinit; ext2load mmc 0:1 0x800000 /uImage; bootm 0x00800000
real_bootcmd=run bootcmd_mmc; run bootcmd_nand
arcNumber=2097
filesize=37B8DF
bootcmd=run bootcmd_mmc; run bootcmd_nand
stdin=serial
stdout=serial
stderr=serial
nandEnvBase=a0000
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no

dmesg | grep Linux:

Code:

Linux version 2.6.36 (newit@gemini) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-68) ) #3 PREEMPT Sun Dec 5 16:26:45 GMT 2010

I also tried changing the ArcNumber to 2678 which did not seem to work either

Regards


StalkS

[NewIT_Marcus]

Marcus,  thank you for taking the time to help me out I really appreciate it.

I had not tested the ESATA functionality until after I had begun to modify the Plug.

UBoot = U-Boot 1.1.4 (Jul 19 2009 - 16:03:28) Marvell version: 3.4.19

Printenv:

Code:

arcNumber=2097

dmesg | grep Linux:

Code:

Linux version 2.6.36 (newit@gemini) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-68) ) #3 PREEMPT Sun Dec 5 16:26:45 GMT 2010

I also tried changing the ArcNumber to 2678 which did not seem to work either

Regards


StalkS

I believe that the kernel that you are using has eSATA functionality with arcNumber 2097. So your eSATA should work. There are 3 more tests that you can do:

• Download an alternative kernel from sheeva.with-linux.com. You may need to change arcNumber to 2678
• Use the eSATA U-Boot commands. ie ide reset should produce some output
• Use a different eSATA cable

[stalks]

Thanks for tips Marcus.

I tried the 'ide reset' command and got an error so I decided to upgrade my uboot to the uboot-sata-090903.bin version found HERE

Code:

usb start
fatload usb 0:1 0x0800000 uboot.bin
nand erase 0x0 0xa0000
nand write 0x0800000 0x0 0xa0000

The 'ide reset' command worked but Debian did not detect the drive so I changed the arcnumber to 2678.

Code:

setenv arcNumber 2678
saveenv
reset

& now everything is working correctly!

Thanks again.


StalkS