Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Fri Aug 01, 2014 7:02 am

All times are UTC [ DST ]




Post new topic Reply to topic  [ 117 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6, 7, 8  Next
Author Message
PostPosted: Sun Mar 30, 2008 12:16 am 
Offline
Newbie

Joined: Sun Mar 23, 2008 2:47 pm
Posts: 15
it is stange.
there is only a checksum value in the first 4-bytes of evn param storage.
if the checksum is wrong,uboot will use initial value.

note that eth's mac address is also recorded in an evn param named "ethaddr"
then you can try this method to check what happened
1.printenv ethaddr
2.set bootcmd
3.saveenv
4.reset
5.printenv ethaddr,check it is the same to the value in the first step you see?

and, initial value of eth's mac address is a hardcode value = 00:00:00:00:51:81

if ethaddr == hardcode value,then uboot has refilled all the env params with initial value.
it means checksum is bad.

if ethaddr != hardcode value.well,so bad things..

there is an another small log.agian,for me,it works.

Code:
Orion1   CPU =  Low

=== BUFFALO LS-GL U-Boot. ===
 ** LOADER **
 ** BUFFALO BOARD: BUFFALO_BOARD_LS_GL LE (CFG_ENV_ADDR=fffff000)


U-Boot 1.1.1 (Apr 18 2007 - 18:35:44) Marvell version: 1.12.1 - TINY

DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB
[256kB@fffc0000] [0kB@f8000000] ## Unknown FLASH at f8000000: Size = 0x00000000 = 0 MB
Flash: 256 kB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done

Soc: 88F5182 A2
CPU: ARM926 (Rev 0) running @ 400Mhz
Orion 1 streaming disabled
SysClock = 200Mhz , TClock = 166Mhz


USB 0: host mode
USB 1: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net:   egiga0 [PRIME]
Using 88E1111 phy

Marvell Serial ATA Adapter
Integrated Sata device found
  Device 1: OK
Model: SAMSUNG SP2504C                          Firm: VT100-50 Ser#: S09QJ1CP211963
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)

Using device ide0, partition 1
** Bad partition 1 **
Using device ide1, partition 1

Loading from block device ide device 1, partition 1: Name: hdb1
  Type: U-Boot  File:/initrd.buffalo

4563455 bytes read
Booting from Device 1
hit any key to switch tftp boot.
Hit any key to stop autoboot:  0
switched to TFTP boot.
<<system_bootend>>
Hit any key to stop autoboot:  0
Marvell>> printenv bootcmd
bootcmd=tftp 0x00100000 $(kernel);tftp 0x00800000 $(initrd);setenv bootargs $(bootargs_base) $(bootargs_root) $(buffalo_ver) tftpboot=yes;bootm 0x00100000 0x00800000
Marvell>> saveenv
Saving Environment to Flash...
.
Un-Protected 1 sectors
Erasing Flash...
.
Erased 1 sectors
Writing to Flash... done
.
Protected 1 sectors
Marvell>> printenv
bootargs=$(bootargs_base) $(bootargs_root)
baudrate=115200
loads_echo=0
ipaddr=192.168.11.150
rootpath=/nfs/arm
cpuName=926
CASset=min
MALLOC_len=4
bootargs_end=:::DB88FXX81:eth0:none
ethact=egiga0
ethaddr=00:16:01:41:4E:2B
serverip=192.168.11.149
buffalo_ver=BOOTVER=1.10
buffalo_minor_ver=BOOT_MINOR_VER=1.00
build_time=18:35:39
initrd=initrd.buffalo
kernel=uImage.buffalo
bootargs_base=console=ttyS0,115200
bootargs_root=root=/dev/sda2 rw initrd=0x00800040,15M panic=5
def_tftp=tftp 0x00100000 $(kernel);tftp 0x00800000 $(initrd);setenv bootargs $(bootargs_base) $(bootargs_root) $(buffalo_ver) tftpboot=yes;bootm 0x00100000 0x00800000
stdin=serial
stdout=serial
stderr=serial
enaMonExt=no
enaFlashBuf=yes
enaCpuStream=no
ethprime=egiga0
bootdelay=3
disaMvPnp=no
overEthAddr=no
usb0Mode=host
usb1Mode=host
filesize=45A1FF
force_tftp=1
bootcmd=tftp 0x00100000 $(kernel);tftp 0x00800000 $(initrd);setenv bootargs $(bootargs_base) $(bootargs_root) $(buffalo_ver) tftpboot=yes;bootm 0x00100000 0x00800000

Environment size: 1004/4092 bytes
Marvell>> set bootcmd ide reset\;ext2load ide 1:1 /$(kernel)\;
Marvell>> printenv bootcmd
bootcmd=ide reset;ext2load ide 1:1 /uImage.buffalo;
Marvell>> saveenv
Saving Environment to Flash...
.
Un-Protected 1 sectors
Erasing Flash...
.
Erased 1 sectors
Writing to Flash... done
.
Protected 1 sectors
Marvell>> reset
Marvell>> Orion1   CPU =  Low

=== BUFFALO LS-GL U-Boot. ===
 ** LOADER **
 ** BUFFALO BOARD: BUFFALO_BOARD_LS_GL LE (CFG_ENV_ADDR=fffff000)


U-Boot 1.1.1 (Apr 18 2007 - 18:35:44) Marvell version: 1.12.1 - TINY

DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB
[256kB@fffc0000] [0kB@f8000000] ## Unknown FLASH at f8000000: Size = 0x00000000 = 0 MB
Flash: 256 kB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done

Soc: 88F5182 A2
CPU: ARM926 (Rev 0) running @ 400Mhz
Orion 1 streaming disabled
SysClock = 200Mhz , TClock = 166Mhz


USB 0: host mode
USB 1: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net:   egiga0 [PRIME]
Using 88E1111 phy

Marvell Serial ATA Adapter
Integrated Sata device found
  Device 1: OK
Model: SAMSUNG SP2504C                          Firm: VT100-50 Ser#: S09QJ1CP211963
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)

Using device ide0, partition 1
** Bad partition 1 **
Using device ide1, partition 1

Loading from block device ide device 1, partition 1: Name: hdb1
  Type: U-Boot  File:/initrd.buffalo

4563455 bytes read
Booting from Device 1
hit any key to switch tftp boot.
Hit any key to stop autoboot:  0
Hit any key to stop autoboot:  0

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
  Device 1: OK
Model: SAMSUNG SP2504C                          Firm: VT100-50 Ser#: S09QJ1CP211963
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)


** No boot file defined **
Marvell>> printenv
bootargs=$(bootargs_base) $(bootargs_root)
baudrate=115200
loads_echo=0
ipaddr=192.168.11.150
rootpath=/nfs/arm
cpuName=926
CASset=min
MALLOC_len=4
bootargs_end=:::DB88FXX81:eth0:none
ethact=egiga0
ethaddr=00:16:01:41:4E:2B
serverip=192.168.11.149
buffalo_ver=BOOTVER=1.10
buffalo_minor_ver=BOOT_MINOR_VER=1.00
build_time=18:35:39
initrd=initrd.buffalo
kernel=uImage.buffalo
bootargs_base=console=ttyS0,115200
bootargs_root=root=/dev/sda2 rw initrd=0x00800040,15M panic=5
def_tftp=tftp 0x00100000 $(kernel);tftp 0x00800000 $(initrd);setenv bootargs $(bootargs_base) $(bootargs_root) $(buffalo_ver) tftpboot=yes;bootm 0x00100000 0x00800000
stdin=serial
stdout=serial
stderr=serial
enaMonExt=no
enaFlashBuf=yes
enaCpuStream=no
ethprime=egiga0
bootdelay=3
disaMvPnp=no
overEthAddr=no
usb0Mode=host
usb1Mode=host
filesize=45A1FF
bootcmd=ide reset;ext2load ide 1:1 /uImage.buffalo;

Environment size: 877/4092 bytes
Marvell>>



Top
 Profile  
 
PostPosted: Sun Mar 30, 2008 1:33 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
:)
@ tiamo : the LSPro V2 stock uboot ( http://buffalo.nas-central.org/download ... bin.tar.gz ) seems to be working for you...

which is great ...

I don't ask you to flash anything again, but just a question if you remember : did the custom LSPro V2 uboot ( http://buffalo.nas-central.org/download ... bin.tar.gz ) work for you the same as the LSPro V2 does?

After all, these two are nearly the same, the u-boot_LSProV2_DG_BuffNASCentral-fullcommands.bin.tar.gz one just has a different prompt, about 6 more commands ... I don't think the changes are that substantial, there isn't any real added code, just some options are turned on ...

_________________
LS1 (foonas, nfs, Tranmission & p910nd print server, Firefly for my Roku)
LS-HG500 (Lenny)
Various LS-Pros v1,v2 (unbricked w/ serial & jtag)
KuroPro, LS2 & KuroHG (foonas)
Working on davysweather.dyndns.org lately...

=> wooohooo!
wooohooo!
Unknown command 'wooohooo!' - try 'help'


Top
 Profile  
 
PostPosted: Sun Mar 30, 2008 7:03 pm 
Offline
Newbie

Joined: Sun Mar 23, 2008 2:47 pm
Posts: 15
Quote:
did the custom LSPro V2 uboot ( http://buffalo.nas-central.org/download ... bin.tar.gz ) work for you the same as the LSPro V2 does?


YES.it works.
the same to stock v2,just only one strange thing,it does another ext2load initrd.buffalo before asking me to switch to tftp mode.

i may wonder,does this behavior exist on your LSProV2?
is this a necessary or important step for LSProV2 hardware running stock v2 uboot?
it just some hdd partition detection?

Code:
Marvell Serial ATA Adapter
Integrated Sata device found
  Device 1: OK
Model: SAMSUNG SP2504C                          Firm: VT100-50 Ser#: S09QJ1CP211963
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)

Using device ide0, partition 1
** Bad partition 1 **
Using device ide1, partition 1

Loading from block device ide device 1, partition 1: Name: hdb1
  Type: U-Boot  File:/initrd.buffalo

4563455 bytes read
Booting from Device 1
hit any key to switch tftp boot.


Top
 Profile  
 
PostPosted: Sun Mar 30, 2008 8:10 pm 
Offline
Site Admin
User avatar

Joined: Mon Jul 11, 2005 7:19 am
Posts: 7702
Location: Austria, Vienna
the v2 hardware (pro/live) is very similar to the kurobox pro. the main difference is that the kurobox pro features a 256 NAND flash and the different (better) daughterboard. with this daughterboard it is easily possible to add a second sata hdd.....maybe this uboot behaviour comes from that?

i mean...what if the engineers tested the OS by connecting a hdd to the second hdd port but wanted to make sure that it will boot from the internal hdd?

_________________
LS1 (2.6 kernel, foonas svn1062, 750 GB, UBoot 1.2) & LS Pro (FreeLink/jtymod/GenLink, changes all the time)
Thx to all donators!


Top
 Profile  
 
PostPosted: Mon Mar 31, 2008 3:40 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
I noticed it before, but it didn't register until (being hit over the head with it now) I saw problems getting foonas to boot straight away w/ uboot on the LSpro V2.

Are they using a password in uboot to do some sort of check on the hdd contents?
around line 980 or so in the buf109 sources...
Code:
            printf (" PASSWORD matched \n");
      }
               if(serch_boot_drv(max_drv) == MV_FAIL)
               {
                  printf ("Lost all init_rd \n");
                        tftp_mode_set() ;
                  


to me it looks like if this could cause it to go into tftp mode if it didn't pass this password match...

which is what I'm seeing w/ the V2 uboot...

@ bbradley, btw, I pulled the uboot-1.1.4 that I had up and replaced it w/ a correction/cleaned version of the patched source... it builds, displays some warnings, but these warnings are the same that are present in the build of the buff109 source...

if you are interested in looking at it, I hope it will be a bit easier to diff now, as I ran a make mproper on it, and restored all of the other boards, cpus and configs... less "missing files" to wade through if you happen to diff it with the plain 1.1.4

_________________
LS1 (foonas, nfs, Tranmission & p910nd print server, Firefly for my Roku)
LS-HG500 (Lenny)
Various LS-Pros v1,v2 (unbricked w/ serial & jtag)
KuroPro, LS2 & KuroHG (foonas)
Working on davysweather.dyndns.org lately...

=> wooohooo!
wooohooo!
Unknown command 'wooohooo!' - try 'help'


Top
 Profile  
 
PostPosted: Tue Apr 01, 2008 9:45 am 
Offline
Newbie

Joined: Sun Mar 23, 2008 2:47 pm
Posts: 15
Quote:
Are they using a password in uboot to do some sort of check on the hdd contents?


Code:
        env = getenv("hdd_pass_wd");
        if(env || (strcmp(env," ") == 0))
      {
         if(unlock_allhdd(env,max_drv) == MV_FAIL)   
         {
            printf ("All drives unmatched PASSWORD \n");
                     if(is_em_mode() != 0x00 )
                     {
                        tftp_mode_set() ;
                     }else
                     {
                        unmatch_password() ;
                     }
              return 0;
         }
            printf (" PASSWORD matched \n");
      }


there is an IF statement.
so,you can check the hdd_pass_wd env with your stock v2 machine(stock v2 uboot + stock v2 kernel + initrd)
i think it will be NULL.

AND,there are two printf statement,so you can check your log to see whether the password is wrong or right.

btw:i think i know why there is an ext2load before it ask me to swith tftp mode.
in the same file.just below password check.
there is a function named "serch_boot_drv".
in the function,uboot will try to ex2load $(initrd)
Code:
/****************************************************************
*****************************************************************
** In RAID system, from which drive Boot program is read      ***
** 1 ,ext2load                                                ***
** 2, check uImage Header(MAGIC,CRC,Checksum,ih_time)         ***
** 3, keep newest_fw_dev                                      ***
** 4, loop all devices                                        ***
** 5, setenv bootcmd to newest_fw_dev                         ***
*****************************************************************
*****************************************************************
***************************************************************/
MV_STATUS serch_boot_drv(char max_disk)

from the comment,
this function is used in a raid station,Tera?
how about Tera's raid implementation
i do not think this function will work with raid0 and raid5 configuration.


Top
 Profile  
 
PostPosted: Wed Apr 02, 2008 4:11 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
yes, tiamo, I agree ...

It would be nice to be able to "clean up" some of these behaviors ... in fact to have a really "open" port of uboot for the lspro and its brothers ...


I wonder how hard it would be to turn some of these things off? (without breaking other functions, of course...)

_________________
LS1 (foonas, nfs, Tranmission & p910nd print server, Firefly for my Roku)
LS-HG500 (Lenny)
Various LS-Pros v1,v2 (unbricked w/ serial & jtag)
KuroPro, LS2 & KuroHG (foonas)
Working on davysweather.dyndns.org lately...

=> wooohooo!
wooohooo!
Unknown command 'wooohooo!' - try 'help'


Top
 Profile  
 
PostPosted: Wed Apr 02, 2008 5:25 am 
Offline
Newbie

Joined: Sun Mar 23, 2008 2:47 pm
Posts: 15
Code:
if(serch_boot_drv(max_drv) == MV_FAIL)
{
   printf ("Lost all init_rd \n");
   tftp_mode_set() ;
                  
/*     if(is_em_mode() != 0x00 )
   {
      tftp_mode_set() ;
   }
        else
   {
      lost_boot_image() ;
   }*/
}


there is a check against with serch_boot_drv's return value.
if serch_boot_drv failed,uboot will swith to tftp mode.

so you must make sure serch_boot_drv returns MV_OK.
you should put a valid initrd.buffalo(create it by mkimage) in your sda1.
and,if you go through serch_boot_drv function,
you can see it WILL MODIFY bootcmd env param.(this is not a problem with LSPro because LSPro just has only one HDD)

did you forget to put an initrd.buffalo in you hdd's first partition?
you have installed a JTAG cable on you LSPro,right?
just make some changes to serch_boot_cmd,recompile,flash.
etc. put some printf in the serch_boot_drv function to see what's wrong with your initrd.buffalo.
with your JTAG cable,even LSPro get bricked,you can still debrick it,right?
so,just modify the code.

i think it is safe to comment out the whole search-boot-drv logic for our LSPro.right?
we set bootcmd correctly,and LSPro boots.
that's all.
we do not need uboot to fix our "correct" bootcmd.

there is another intresting thing.
there is a function named "misc_init_r_env"
Code:
env = getenv("buffalo_ver");
if (!env || strcmp(env,BUFFALO_VER)!=0|| strcmp(getenv("build_time"),__TIME__)!=0 ){
   MV_U32  bid=mvBoardIdGet();
        printf("-- initialize Env for BUFFALO\n");

here,it checked buffalo_ver and build_time env params,
if this check failed,uboot will rewrite buffalo_ver build_time AND BOOTCMD env param.
but just only rewrite them without saving them to flah,right?
so,check your log to see whether there is an "initialize Env for BUFFALO" string?

i think the simplest way is just erase your env cfg,and let uboot to reinitialize it.
when you see the second "hit any key to stop autoboot"
then press any key.and you are in uboot shell
then issue a "saveenv" command.
then "reset"

may i have a favor to ask you to post your log file?
i think we can finger out what is wrong by tracing the log file carefully.


Top
 Profile  
 
PostPosted: Wed Apr 02, 2008 12:33 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
:) very nice ... this seems true ... I was noticing that about it checking for existence of the initrd on the partition first as well... and I fgrep-ed for MV_OK in the source ... it does need to be returned , right.


For those of us working w/ foonas (I think I'm the only one on the LSProV2), we don't ever need an initrd on the hdd to get it to work with the LSProV1 ... but we have noticed differences in behavior between teh UBoot on the LSProV1 and the UBoot on LSProV2 ... so this is probably one of the reasons for the different behavior.

As far as I know, the source for UBoot on the LS ProV1 hasn't been released... we've seen only the source for the LSProV2, I believe. The LSProV1's source must be similar of course, but this serch_boot_drive may be a new thing. If you look at the source, it seems like a single UBoot.bin would work in a lot of different machines, even w/ RAID ... and you can see the machine ID strings there as well... and choices for which functions/capabilities to enable.

Yes, I have jtag and will try these changes... if the image is not usable, I can just flash it w/ a working image.

I'm off to work/job now, but will try this evening ... ;)

EDIT:
and yes, I"ll post my log file this evening as well, but I can tell you that the netconsole uboot I have now works fine with the standard stock firmware, just not with foonas (which has no initrd ... though of course I could supply a "dummy" initrd for it...)

_________________
LS1 (foonas, nfs, Tranmission & p910nd print server, Firefly for my Roku)
LS-HG500 (Lenny)
Various LS-Pros v1,v2 (unbricked w/ serial & jtag)
KuroPro, LS2 & KuroHG (foonas)
Working on davysweather.dyndns.org lately...

=> wooohooo!
wooohooo!
Unknown command 'wooohooo!' - try 'help'


Top
 Profile  
 
PostPosted: Thu Apr 03, 2008 4:06 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
tiamo, with the little time I had this evening, I did comment out all of the logic of serch_boot_drv ... from around line 128 through line 222. It did change the behavior of uboot, but I have to check it some more...


foonas will (as far as I know!) never make use of an initrd, disabling this check make sense to me...


I did not get a chance to reinstall foonas on the hard drive, but I did change bootcmd to this:


and it booted foonas-em from tftp without too much complaining, except a moment of beeping... need to see what causes that

here is the log:

Code:
=> egiga0 [PRIME]
.
Un-Protected 1 sectors
Erasing Flash...
.
Erased 1 sectors
Writing to Flash... done
.
Protected 1 sectors
 
 _____ _____ _____     _____         _           _               
|   | |  _  |   __|___|     |___ ___| |_ ___ ___| |  ___ ___ ___ 
| | | |     |__   |___|   --| -_|   |  _|  _| .'| |_| . |  _| . |
|_|___|__|__|_____|   |_____|___|_|_|_| |_| |__,|_|_|___|_| |_  |
                                                            |___|
 
 
 
 
 
Using 88E1118 phy

Marvell Serial ATA Adapter
Integrated Sata device found
  Device 0: OK
Model: WDC WD2500JD-00HBC0                      Firm: 08.02D08 Ser#:      WD-WCAL77520516
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)

hit any key to switch tftp boot.
Hit any key to stop autoboot:  0
Hit any key to stop autoboot:  0

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
  Device 0: OK
Model: WDC WD2500JD-00HBC0                      Firm: 08.02D08 Ser#:      WD-WCAL77520516
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)

** Bad partition 1 **
<<stop_sound>>
## Booting image at 00100000 ...
Bad Magic Number
bootm fail.
<<system_not_found>>
Using egiga0 device
TFTP from server 192.168.11.149; our IP address is 192.168.11.150
Filename 'uImage_em'.
Load address: 0x800000
Loading: #################################################################
...
         #############################################
done
Bytes transferred = 5551060 (54b3d4 hex)
<<stop_sound>>
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.24
   Created:      2008-02-05  19:27:02 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5550996 Bytes =  5.3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...

arg:netconsole=6666@192.168.11.150/,@192.168.11.149/ root=/dev/ram0 rw


I will try it tomorrow night after work w/ a regular hdd installation...

What seems more clear to me now is that the ProV1 uses 1:1 by default, and the ProV2 and KuroPro use 0:1 by default...

_________________
LS1 (foonas, nfs, Tranmission & p910nd print server, Firefly for my Roku)
LS-HG500 (Lenny)
Various LS-Pros v1,v2 (unbricked w/ serial & jtag)
KuroPro, LS2 & KuroHG (foonas)
Working on davysweather.dyndns.org lately...

=> wooohooo!
wooohooo!
Unknown command 'wooohooo!' - try 'help'


Last edited by davy_gravy on Thu Apr 03, 2008 10:31 pm, edited 1 time in total.

Top
 Profile  
 
PostPosted: Thu Apr 03, 2008 4:28 am 
Offline
Site Admin
User avatar

Joined: Tue Mar 21, 2006 9:11 pm
Posts: 658
I was waiting to be able to boot without an initrd. Great work guys.

_________________
My completely scratch built 832 push-pull tube amplifier with Padauk frame. It matches my custom mini-ITX machine.


Top
 Profile  
 
PostPosted: Thu Apr 03, 2008 11:26 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
well, I pruned too much off the tree ... hehe...

Code:
=> ide reset
ide reset

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
  Device 0: OK
Model: WDC WD2500JD-00HBC0                      Firm: 08.02D08 Ser#:      WD-WCAL77520516
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)

=> ext2load ide 0:1 0x00100000 /boot/uImage
ext2load ide 0:1 0x00100000 /boot/uImage
data abort
pc : [<00f3da0e>]    lr : [<00f3e038>]
sp : 00f0f994  ip : 00000001  fp : 00f0fa20
r10: 010012cc  r9 : 00f0f9dc  r8 : 00f0ffd0
r7 : 010012c8  r6 : 00f0fa25  r5 : 00000001  r4 : 00000001
r3 : 00000ff8  r2 : 010012cc  r1 : 00000002  r0 : 00000001
Flags: nZCv  IRQs off  FIQs off  Mode SVC_32
Resetting CPU ...

egiga0



it did not like that ... so I guess I'll see if I can enable whatever lines are doing some initialization (of the SATA/IDE bus?), though not sure right now what that is...


EDIT:
reflashing now w/ a safer image and will try again... maybe it just needs to sidestep some of the conditionals where it reverts to a previous tftp command ...

or ... hmmm what if we let the "initrd" file that uboot looks for just be the uImage/kernel ? after all, its just checking to see if it is there... it doesn't actually check its contents (AFAWK!)

_________________
LS1 (foonas, nfs, Tranmission & p910nd print server, Firefly for my Roku)
LS-HG500 (Lenny)
Various LS-Pros v1,v2 (unbricked w/ serial & jtag)
KuroPro, LS2 & KuroHG (foonas)
Working on davysweather.dyndns.org lately...

=> wooohooo!
wooohooo!
Unknown command 'wooohooo!' - try 'help'


Top
 Profile  
 
PostPosted: Fri Apr 04, 2008 8:07 pm 
Offline
Newbie

Joined: Sun Mar 23, 2008 2:47 pm
Posts: 15
Quote:
ext2load ide 0:1 0x00100000 /boot/uImage


or
ext2load ide 1:1 0x00100000 /boot/uImage


Top
 Profile  
 
PostPosted: Fri Apr 04, 2008 11:52 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
well, I think device 0 is the correct one, but I did try them both:

Code:
=> egiga0

 [PRIME]
 
 _____ _____ _____     _____         _           _               
|   | |  _  |   __|___|     |___ ___| |_ ___ ___| |  ___ ___ ___ 
| | | |     |__   |___|   --| -_|   |  _|  _| .'| |_| . |  _| . |
|_|___|__|__|_____|   |_____|___|_|_|_| |_| |__,|_|_|___|_| |_  |
                                                            |___|
 
 
 
 
 
Using 88E1118 phy

Marvell Serial ATA Adapter
Integrated Sata device found
  Device 0: OK
Model: WDC WD2500JD-00HBC0                      Firm: 08.02D08 Ser#:      WD-WCAL77520516
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)


** Unable to read "/boot/uImage" from ide 0:1 **
** Bad partition 1 **
Lost all init_rd
hit any key to switch tftp boot.
Hit any key to stop autoboot:  0
=> ext2load ide 0:1 0x00100000 /boot/uImage
ext2load ide 0:1 0x00100000 /boot/uImage

** Unable to read "/boot/uImage" from ide 0:1 **
=> ext2load ide 1:1 0x00100000 /boot/uImage
ext2load ide 1:1 0x00100000 /boot/uImage
** Bad partition 1 **
=>


it is a known good partition... when booted in foonas-em I can mount the partition, read files, write, etc...

oddly enough, I cannot get ext2ls to work correctly, either...

Code:
=> ext2ls ide 0:1 /
ext2ls ide 0:1 /



I sure hope they aren't trying to lock this all down:

Code:
=> security
security
Usage:
security -device -command -options -password

I wasn't aware that uboot had a "security" command... until I noticed this...

_________________
LS1 (foonas, nfs, Tranmission & p910nd print server, Firefly for my Roku)
LS-HG500 (Lenny)
Various LS-Pros v1,v2 (unbricked w/ serial & jtag)
KuroPro, LS2 & KuroHG (foonas)
Working on davysweather.dyndns.org lately...

=> wooohooo!
wooohooo!
Unknown command 'wooohooo!' - try 'help'


Top
 Profile  
 
PostPosted: Sat Apr 05, 2008 11:50 am 
Offline
Newbie

Joined: Sun Mar 23, 2008 2:47 pm
Posts: 15
it seems that uboot can't recognize your partition format

use ide inf,ide dev,ide part to check your partition format?

you can also use LSUpdater.exe to rebuild your partititon table.


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 117 posts ]  Go to page Previous  1, 2, 3, 4, 5, 6, 7, 8  Next

All times are UTC [ DST ]


Who is online

Users browsing this forum: No registered users and 3 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:

Protected by Anti-Spam ACP
Protected by Anti-Spam ACP Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group