Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Tue Jan 16, 2018 4:30 pm

All times are UTC+01:00




Post new topic  Reply to topic  [ 11 posts ] 
Author Message
 Post subject: foonas-em for LS2
PostPosted: Wed Oct 31, 2007 9:40 pm 
Offline
Moderator
User avatar

Joined: Thu Jun 22, 2006 10:54 pm
Posts: 240
Location: UK
Moving this out of the kernel/uboot related thread!

As people may already be aware, foonas-em for ls2s is currently available, however it does have one minor issue in that halt/reboot commands do not work as expected currently. Fixes for this (and proper installation instructions) will be available at foonas.org soon!

In other news, the LS2 is the first platform to gain support for installing an OS via the web interface (foonas, although others will be added!). This is just an initial version (which needs better error checking/reporting throughout the install process) however if people want to test it, great - be wary it will repartition and format your internal hard disk! If you already have installed foonas-em for this platform, they will pop up in the installer interface next time you visit it.

This build features all of the tools contained in the PPC foonas-em firmware, with the exception of the xfs userspace utilities.

_________________
Help the foonas fundraiser!

Click here for more information and donations


Top
   
 Post subject: Re: foonas-em for LS2
PostPosted: Thu Nov 01, 2007 9:32 pm 
Offline
Moderator
User avatar

Joined: Thu Jun 22, 2006 10:54 pm
Posts: 240
Location: UK
The pre-compiled beta at foonas.org has been updated to include linux-2.6.22.3, and it is now possible to reboot or halt from a telnet session or via the web interface (but not via the button, watch this space!).

http://downloads.foonas.org/foonas-em/beta3/lsmipsel/

Edit: Have 2.6.22.10 running locally (with virtually no modification to lnis patch, other than removing the bit that changes the EXTRAVERSION variable which would need modification for every kernel version!). If you pull the patch from foonas.org be wary there is another hack in it so it doesn't need the IDT toolchain, however it makes it OE specific instead.

Also, 2.6.23.1 fails to patch currently due to some stuff being moved around upstream.

_________________
Help the foonas fundraiser!

Click here for more information and donations


Top
   
 Post subject: Re: foonas-em for LS2
PostPosted: Fri Nov 02, 2007 4:42 pm 
Offline
Moderator
User avatar

Joined: Thu Jun 22, 2006 10:54 pm
Posts: 240
Location: UK
The foonas-em binary in the link above has been updated to use 2.6.22.10. Also if anyone who has already installed foonas-em for this platform hits the updater an installer for Openlink 0.52b is also there (I use it for flashing the em firmware to my box in 2.4, again this will repartition and format your hard disk on install).

The only slightly modified patch for the kernel is in svn at foonas.org.

_________________
Help the foonas fundraiser!

Click here for more information and donations


Top
   
 Post subject: Re: foonas-em for LS2
PostPosted: Fri Mar 14, 2008 10:12 am 
Offline
Regular Member

Joined: Mon Nov 07, 2005 4:37 pm
Posts: 205
Location: Germany
Hi timtim,

a short question: In the foonas em wiki is written, that flashing the image to mtd can fail, when u-boot / kernel 2.6 is present. Is this and AND or OR logic ? ;-) Can the foonas-em binary not flash if u-boot AND kernel 2.6 is present or means that, that the binary can not be flashed from u-boot OR kernel 2.6?

prodigy7

_________________
LS2 (U-Boot + Freelink) | Kurobox (U-Boot + Deboostraped) | LS Pro Duo (Freelink)


Top
   
 Post subject: Re: foonas-em for LS2
PostPosted: Fri Mar 14, 2008 11:28 am 
Offline
Site Admin
User avatar

Joined: Mon Jul 11, 2005 7:19 am
Posts: 7703
Location: Austria, Vienna
from my understanding flashing does not properly work from within uboot on LS2`s with the wrong flash chip.

also we experienced problems with flashing from within 2.6 kernels to flash.....but this was on the ppc boxes. i have no clue if this is valid on the LS2 as well.

from my understanding flashing could work from the original kernel...but that would only be save if you had installed uboot before and put the decrypted 2.4 kernel into /boot

then the only problem could be that the flash map used inside the stock kernel does not allow installation of foonas-em....foonas-em is installed on the ppc linkstations from within uboot.....thats the unknown factor.

_________________
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
   
 Post subject: Re: foonas-em for LS2
PostPosted: Thu May 01, 2008 7:32 pm 
Offline
Moderator
User avatar

Joined: Thu Jun 22, 2006 10:54 pm
Posts: 240
Location: UK
foonas-em was updated for LS2s recently to 0.1.0-r0. flash issue mentioned previously still means that this is listed as unsupported but should be fine for those with the other type. Here are some of the major changes for this platform (repeated from the long foonas thread that is getting difficult to read!):

* USB Storage & VFAT - now you can install from a USB stick formatted in any major OS
* Full JFS support - finally the LS2 has repair utils & kernel support in EM mode for a non ext3 fs!
* ipv6 support (enabled, if you have a ipv6 router will just work)
* Linux 2.6.22.19, busybox 1.10.1, vsftpd 2.0.6
* Moved to uclibc instead of glibc
* Partial localisation of web interface to German/Spanish

_________________
Help the foonas fundraiser!

Click here for more information and donations


Top
   
 Post subject: Re: foonas-em for LS2
PostPosted: Tue Aug 12, 2008 4:24 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
How to boot foonas-em from the hard drive on the LS2-lsmipsel (good in case you have one of the LS2's w/ the ST flash chip that won't currently accommodate foonas-em):
We knew it could be done, just like we do on the LSPro's, and after Bauldrick testdrove it, we decided to write it down...

On a uboot-equipted LS2, while booted in linux, (openlink, freelink, foonas, whatever)..., cd to /boot and wget the latest (or desired) foonas-em image, then reboot...
Code:
cd /boot/
wget [ insert the url of the latest foonas-em image for lsmipsel here - we assume its filename to be [b]vmlinuz.gz[/b] ]
reboot


in your netconsole/netcat window, after stopping UBoot's bootprocess w/ an "s", enter the following commands:
Code:
=> ide reset
=> ext2load ide 0:1 82000000  /boot/vmlinuz.gz
=> setenv bootargs netconsole=6666@192.168.11.150/,@192.168.11.149/ root=/dev/ram0 rw
=> bootm 82000000

If you are successful, you will see something like this:
Code:
=> ide reset
ide reset

Reset IDE: Bus 0: OK Bus 1: OK
  Device 0: Model: SAMSUNG HA250JC  Firm: WE100-34 Ser#: 0S491JYS094808
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)
=> ext2load ide 0:1 82000000  /boot/vmlinuz.gz
ext2load ide 0:1 82000000  /boot/vmlinuz.gz

5181098 bytes read
=> setenv bootargs netconsole=6666@192.168.11.150/,@192.168.11.149/ root=/dev/ram0 rw
setenv bootargs netconsole=6666@192.168.11.150/,@192.168.11.149/ root=/dev/ram0 rw
=> bootm 82000000
bootm 82000000
## Booting image at 82000000 ...
Loading .text @ 0x80100000 (2004096 bytes)
Loading __ex_table @ 0x802e9480 (6112 bytes)
Loading .notes @ 0x802eac60 (36 bytes)
Loading .rodata @ 0x802eb000 (122776 bytes)
Loading .pci_fixup @ 0x80308f98 (1352 bytes)
Loading __ksymtab @ 0x803094e0 (15392 bytes)
Loading __ksymtab_gpl @ 0x8030d100 (4064 bytes)
Loading __ksymtab_strings @ 0x8030e0e0 (44780 bytes)
Loading __param @ 0x80318fcc (340 bytes)
Loading .data @ 0x8031a000 (77584 bytes)
Loading .data.cacheline_aligned @ 0x8032d000 (192 bytes)
Loading .init.text @ 0x8032e000 (120048 bytes)
Loading .init.data @ 0x8034b4f0 (6288 bytes)
Loading .init.setup @ 0x8034cd80 (744 bytes)
Loading .initcall.init @ 0x8034d068 (396 bytes)
Loading .exit.text @ 0x8034d1f4 (2032 bytes)
Loading .init.ramfs @ 0x8034e000 (2175450 bytes)
Clearing .bss @ 0x80562000 (93600 bytes)

Starting kernel @ 0x8032E000...


You should be able to log in to its IP (use NMAPFE or some other scanner to find the IP) with telnet.
login : root
password : hydr0g3n

_________________
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
   
 Post subject: Re: foonas-em for LS2
PostPosted: Mon Sep 07, 2009 3:27 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
I just now did what harter Zwieback mentioned that he did w/ his HG that had the ST Micro flash chip (which didn't like flashing)... I only had to adjust weini's directions/values a bit...

...as always... flash at your own risk... and this was/is a custom foonas-em (non-release version)...

foonas-em in the flash of an LS2 w/ the ST Micro chip is possible... thanks to weini & harter for pointing the way on this... :up:
Code:
U-Boot 1.1.4 LiSt V2 (mips) 1.0.1 (Sep 20 2007 - 00:42:23)
stdin :   nc
stdout:   nc
stderr:   nc
IDE:    Bus 0: ..OK Bus 1: OK
  Device 0: Model: WDC WD2500BB-00RDA0  Firm: 20.00K20 Ser#: W -DMWNA2K525080
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 238475.1 MB = 232.8 GB (488397168 x 512)
Boot in 09 seconds ('s' to stop)...s

=> flinfo
flinfo

Bank # 1: Flash chip: STMICRO M29W324DB

CFI Query Results:
Primary Vendor Command Set: 0x0002 (AMD/Fujitsu Standard)
Primary Algorithm Table at 0x0040
Alternate Vendor Command Set: 0x0000 (None)
No Alternate Algorithm Table
Vcc Min.: 2.7 V
Vcc Max.: 3.6 V
Vpp Min.: 11.5 V
Vpp Max.: 12.5 V
Typical byte/word write timeout: 16 us
Maximum byte/word write timeout: 256 us
Full buffer write not supported
Typical block erase timeout: 1024 ms
Maximum block erase timeout: 8192 ms
Chip erase not supported
Device size: 0x400000 bytes (4 MiB)
Flash Device Interface description: 0x0002
  - x8 / x16 via BYTE# with asynchronous interface
Max. bytes in buffer write: 1
Number of Erase Block Regions: 2

Actual values used by U-Boot:
Word   write timeout:      2 ms
Buffer write timeout:      2 ms
Sector erase timeout:   8192 ms

Size: 4 MiB in 71 Sectors
  Sector Start Addresses:
    BFC00000 (RO) BFC02000 (RO) BFC04000 (RO) BFC06000 (RO) BFC08000 (RO)
    BFC0A000 (RO) BFC0C000 (RO) BFC0E000 (RO) BFC10000 (RO) BFC20000 (RO)
    BFC30000 (RO) BFC40000 (RO) BFC50000 (RO) BFC60000 (RO) BFC70000 (RO)
    BFC80000 (RO) BFC90000 (RO) BFCA0000 (RO) BFCB0000 (RO) BFCC0000 (RO)
    BFCD0000 (RO) BFCE0000 (RO) BFCF0000 (RO) BFD00000 (RO) BFD10000 (RO)
    BFD20000 (RO) BFD30000 (RO) BFD40000 (RO) BFD50000 (RO) BFD60000 (RO)
    BFD70000 (RO) BFD80000 (RO) BFD90000 (RO) BFDA0000 (RO) BFDB0000 (RO)
    BFDC0000 (RO) BFDD0000 (RO) BFDE0000 (RO) BFDF0000 (RO) BFE00000 (RO)
    BFE10000 (RO) BFE20000 (RO) BFE30000 (RO) BFE40000 (RO) BFE50000 (RO)
    BFE60000 (RO) BFE70000 (RO) BFE80000 (RO) BFE90000 (RO) BFEA0000 (RO)
    BFEB0000 (RO) BFEC0000 (RO) BFED0000 (RO) BFEE0000 (RO) BFEF0000 (RO)
    BFF00000 (RO) BFF10000 (RO) BFF20000 (RO) BFF30000 (RO) BFF40000 (RO)
    BFF50000 (RO) BFF60000 (RO) BFF70000 (RO) BFF80000 (RO) BFF90000 (RO)
    BFFA0000 (RO) BFFB0000 (RO) BFFC0000 (RO) BFFD0000 (RO) BFFE0000 (RO)
    BFFF0000 (RO)
=> tftp 82000000 vmlinuz.gz-ext4_tune2fs_fw-setwrite
tftp 82000000 vmlinuz.gz-ext4_tune2fs_fw-setwrite
Using rc32434_eth device
TFTP from server 192.168.11.149; our IP address is 192.168.11.150
Filename 'vmlinuz.gz-ext4_tune2fs_fw-setwrite'.
Load address: 0x82000000
Loading: #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    ########################
done
Bytes transferred = 3448260 (349dc4 hex)
=> protect off bfc40000 bffbffff
protect off bfc40000 bffbffff
Un-Protected 56 sectors
=> erase bfc40000 bffbffff
erase bfc40000 bffbffff

Flash erase: first = 11 @ 0xbfc40000
             last  = 66 @ 0xbffb0000
Flash erase: Timeout
Erased 56 sectors
=> erase bfe00000 bffbffff
erase bfe00000 bffbffff

Flash erase: first = 39 @ 0xbfe00000
             last  = 66 @ 0xbffb0000
Flash erase: Done
Erased 28 sectors
=> cp.b 82000000 bfc40000 180000
cp.b 82000000 bfc40000 180000
Copy to Flash... done
=> cp.b 82180000 bfdc0000 40000
cp.b 82180000 bfdc0000 40000
Copy to Flash... done
=> cp.b 821c0000 bfe00000 189DC4
cp.b 821c0000 bfe00000 189DC4
Copy to Flash... done
=> cmp.b 0x82000000 bfc40000 349dc4
cmp.b 0x82000000 bfc40000 349dc4
Total of 3448260 bytes were the same
=> run emboot
run emboot
## Booting image at bfc40000 ...
Found gzip-ed image at 0xbfc40000. Uncompressing ...done
Loading .text @ 0x80002000 (2824056 bytes)
Loading __ex_table @ 0x802b3780 (6776 bytes)
Loading .notes @ 0x802b51f8 (36 bytes)
Loading .rodata @ 0x802b6000 (229504 bytes)
Loading .init.rodata @ 0x802ee080 (292 bytes)
Loading .pci_fixup @ 0x802ee1a4 (1736 bytes)
Loading __ksymtab @ 0x802ee86c (17632 bytes)
Loading __ksymtab_gpl @ 0x802f2d4c (9080 bytes)
Loading __ksymtab_strings @ 0x802f50c4 (57595 bytes)
Loading __param @ 0x803031c0 (3648 bytes)
Loading .data @ 0x80304000 (104608 bytes)
Loading .data.cacheline_aligned @ 0x8031e000 (1536 bytes)
Loading .init.text @ 0x8031f000 (134036 bytes)
Loading .init.data @ 0x8033fb98 (21840 bytes)
Loading .init.setup @ 0x803450f0 (852 bytes)
Loading .initcall.init @ 0x80345444 (632 bytes)
Loading .con_initcall.init @ 0x803456bc (4 bytes)
Loading .exit.text @ 0x803456c0 (3832 bytes)
Loading .init.ramfs @ 0x80347000 (4128768 bytes)
Clearing .bss @ 0x80737000 (109104 bytes)

Starting kernel @ 0x80006230...

_________________
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
   
 Post subject: Re: foonas-em for LS2
PostPosted: Sat Sep 26, 2009 9:26 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
OK, confirmed on a 2nd LS2 with the ST Micro chip... this should indicate that all LS2's, regardless of which ROM chip they have, should be flashable from within uboot. The vmlinuz.gz-ext4_tune2fs_fw-setwrite_inode-safe foonas-em custom image is available in my download folder - flash at your own risk.

Code:
U-Boot 1.1.4 LiSt V2 (mips) 1.0.1 (Sep 20 2007 - 00:42:23)
stdin :   nc
stdout:   nc
stderr:   nc
IDE:    Bus 0: OK Bus 1: OK
  Device 0: Model: SAMSUNG SP1203N  Firm: TL100-30 Ser#: 0SQ02JX00C3140
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 114498.5 MB = 111.8 GB (234493056 x 512)
Boot in 08 seconds ('s' to stop)...s

=> tftp 82000000 vmlinuz.gz-ext4_tune2fs_fw-setwrite_inode-safe
tftp 82000000 vmlinuz.gz-ext4_tune2fs_fw-setwrite_inode-safe
Using rc32434_eth device
TFTP from server 192.168.11.149; our IP address is 192.168.11.150
Filename 'vmlinuz.gz-ext4_tune2fs_fw-setwrite_inode-safe'.
Load address: 0x82000000
Loading: #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    #################################################################
    ############################
done
Bytes transferred = 3466346 (34e46a hex)
=> protect off bfc40000 bffbffff
protect off bfc40000 bffbffff
Un-Protected 56 sectors
=>

Un-Protected 56 sectors
=> erase bfe00000 bffbffff
erase bfe00000 bffbffff

Flash erase: first = 39 @ 0xbfe00000
             last  = 66 @ 0xbffb0000
Flash erase: Done
Erased 28 sectors
=> erase bfc40000 bffbffff
erase bfc40000 bffbffff

Flash erase: first = 11 @ 0xbfc40000
             last  = 66 @ 0xbffb0000
Flash erase: Done
Erased 56 sectors
=> cp.b 82000000 bfc40000 180000
cp.b 82000000 bfc40000 180000
Copy to Flash... done
=> cp.b 82180000 bfdc0000 40000
cp.b 82180000 bfdc0000 40000
Copy to Flash... done
=> cp.b 821c0000 bfe00000 18E46A
cp.b 821c0000 bfe00000 18E46A
Copy to Flash... done
=> cmp.b 0x82000000 bfc40000 34e46a
cmp.b 0x82000000 bfc40000 34e46a
Total of 3466346 bytes were the same
=> flinfo
flinfo

Bank # 1: Flash chip: STMICRO M29W324DB

CFI Query Results:
Primary Vendor Command Set: 0x0002 (AMD/Fujitsu Standard)
Primary Algorithm Table at 0x0040
Alternate Vendor Command Set: 0x0000 (None)
No Alternate Algorithm Table
Vcc Min.: 2.7 V
Vcc Max.: 3.6 V
Vpp Min.: 11.5 V
Vpp Max.: 12.5 V
Typical byte/word write timeout: 16 us
Maximum byte/word write timeout: 256 us
Full buffer write not supported
Typical block erase timeout: 1024 ms
Maximum block erase timeout: 8192 ms
Chip erase not supported
Device size: 0x400000 bytes (4 MiB)
Flash Device Interface description: 0x0002
  - x8 / x16 via BYTE# with asynchronous interface
Max. bytes in buffer write: 1
Number of Erase Block Regions: 2

Actual values used by U-Boot:
Word   write timeout:      2 ms
Buffer write timeout:      2 ms
Sector erase timeout:   8192 ms

Size: 4 MiB in 71 Sectors
  Sector Start Addresses:
    BFC00000 (RO) BFC02000 (RO) BFC04000 (RO) BFC06000 (RO) BFC08000 (RO)
    BFC0A000 (RO) BFC0C000 (RO) BFC0E000 (RO) BFC10000 (RO) BFC20000 (RO)
    BFC30000 (RO) BFC40000 (RW) BFC50000 (RW) BFC60000 (RW) BFC70000 (RW)
    BFC80000 (RW) BFC90000 (RW) BFCA0000 (RW) BFCB0000 (RW) BFCC0000 (RW)
    BFCD0000 (RW) BFCE0000 (RW) BFCF0000 (RW) BFD00000 (RW) BFD10000 (RW)
    BFD20000 (RW) BFD30000 (RW) BFD40000 (RW) BFD50000 (RW) BFD60000 (RW)
    BFD70000 (RW) BFD80000 (RW) BFD90000 (RW) BFDA0000 (RW) BFDB0000 (RW)
    BFDC0000 (RW) BFDD0000 (RW) BFDE0000 (RW) BFDF0000 (RW) BFE00000 (RW)
    BFE10000 (RW) BFE20000 (RW) BFE30000 (RW) BFE40000 (RW) BFE50000 (RW)
    BFE60000 (RW) BFE70000 (RW) BFE80000 (RW) BFE90000 (RW) BFEA0000 (RW)
    BFEB0000 (RW) BFEC0000 (RW) BFED0000 (RW) BFEE0000 (RW) BFEF0000 (RW)
    BFF00000 (RW) BFF10000 (RW) BFF20000 (RW) BFF30000 (RW) BFF40000 (RW)
    BFF50000 (RW) BFF60000 (RW) BFF70000 (RW) BFF80000 (RW) BFF90000 (RW)
    BFFA0000 (RW) BFFB0000 (RW) BFFC0000 (RO) BFFD0000 (RO) BFFE0000 (RO)
    BFFF0000 (RO)
=> print
print
bootcmd=run bootcmd1
nfsboot=run nfsload nfsargs;bootm
bootdelay=10
baudrate=57600
autoload=no
stdin=nc
stdout=nc
stderr=nc
ncip=192.168.11.149
netretry=no
nc=setenv stdin nc;setenv stdout nc;setenv stderr nc
ser=setenv stdin serial;setenv stdout serial;setenv stderr serial
ldaddr=82000000
guaddr=81000000
hdpart=0:1
hdload=echo Loading ${hdpart}:${hdfile};ext2load ide ${hdpart} ${ldaddr} ${hdfile}
flboot=setenv bootargs root=/dev/hda1;bootm bfc40000
emboot=setenv bootargs root=/dev/ram0;bootm bfc40000
rootpath=/opt/nfsroot/mipsel
nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off
nfsfile=vmlinuz
nfsload=nfs ${ldaddr} ${serverip}:${rootpath}/${nfsfile}
bootretry=30
bootcmd1=run hdboot;run flboot
bootcmd2=run flboot
bootcmd3=run emboot
ubpart=0:3
ubfile=share/u-boot/u-boot-v2-mips.flash.bin
ubload=echo Loading ${ubpart}:${ubfile};ext2load ide ${ubpart} ${ldaddr} ${ubfile}
ubsaddr=bfc00000
ubeaddr=bfc2ffff
ubflash=protect off ${ubsaddr} ${ubeaddr};era ${ubsaddr} ${ubeaddr};cp.b ${ldaddr} ${ubsaddr} ${filesize};cmp.b ${ldaddr} ${ubsaddr} ${filesize}
upgrade=run ubload ubflash
ethact=rc32434_eth
serboot=run ser ; bootm 82000000
serlniboot=ext2load ide 0:1 82000000 /boot/vmlinuz-2.6.22.19 ; setenv bootargs console=ttyS0 root=/dev/hda1 rw ; run serboot
hdboot=run hdload boothd
serhddboot=ext2load ide 0:1 82000000 /boot/vmlinuz-2.6.30.4 ; setenv bootargs console=ttyS0 root=/dev/sda1 rw ; run serboot
boothd=setenv bootargs root=/dev/sda1 rw ; bootm
tftpfem=tftp 82000000 vmlinuz.gz ; setenv bootargs netconsole=6666@192.168.11.150/,@192.168.11.149/ root=/dev/ram0 rw ;bootm 82000000
box=small
ttt=tftp 82000000 vmlinuz.gz ; set bootargs root=/dev/ram0 netconsole=6666@192.168.11.150/,@192.168.11.149/ ; bootm 82000000
bootargs=root=/dev/sda1 rw netconsole=6666@192.168.11.150/,@192.168.11.149/
hdfile=boot/vmlinuz
filesize=34e46a
fileaddr=82000000
netmask=255.255.255.0
ipaddr=192.168.11.150
serverip=192.168.11.149

Environment size: 2019/65532 bytes
=> run emboot
run emboot
## Booting image at bfc40000 ...
Found gzip-ed image at 0xbfc40000. Uncompressing ...done
Loading .text @ 0x80002000 (2850008 bytes)
Loading __ex_table @ 0x802b9ce0 (6776 bytes)
Loading .notes @ 0x802bb758 (36 bytes)
Loading .rodata @ 0x802bc000 (231148 bytes)
Loading .init.rodata @ 0x802f46ec (292 bytes)
Loading .pci_fixup @ 0x802f4810 (1736 bytes)
Loading __ksymtab @ 0x802f4ed8 (17648 bytes)
Loading __ksymtab_gpl @ 0x802f93c8 (9120 bytes)
Loading __ksymtab_strings @ 0x802fb768 (57736 bytes)
Loading __param @ 0x803098f0 (1808 bytes)
Loading .data @ 0x8030a000 (104704 bytes)
Loading .data.cacheline_aligned @ 0x80324000 (1536 bytes)
Loading .init.text @ 0x80325000 (134036 bytes)
Loading .init.data @ 0x80345b98 (21840 bytes)
Loading .init.setup @ 0x8034b0f0 (852 bytes)
Loading .initcall.init @ 0x8034b444 (632 bytes)
Loading .con_initcall.init @ 0x8034b6bc (4 bytes)
Loading .exit.text @ 0x8034b6c0 (3868 bytes)
Loading .init.ramfs @ 0x8034d000 (4145664 bytes)
Clearing .bss @ 0x80742000 (109120 bytes)

Starting kernel @ 0x80006230...



_________________
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
   
 Post subject: Re: foonas-em for LS2
PostPosted: Sun Nov 29, 2009 5:37 am 
Offline
Newbie

Joined: Thu Dec 13, 2007 2:31 pm
Posts: 21
Hi Davy.

I tried your new version of foonas-em, seem you got halt/reboot issue again, will you try to fix it? Also a strange thing that it works when I use tftp while when I flashed it into the ROM, it halted after loading the kernel. I can confirm the flash it successful after the cmp.o. ( now I flashed back to the old version of foonas and it works fine)


Top
   
 Post subject: Re: foonas-em for LS2
PostPosted: Wed Dec 02, 2009 1:34 am 
Offline
Newbie

Joined: Sun Nov 20, 2005 7:40 pm
Posts: 51
What about flagging foonas-em for mipsel stable on www.foonas.org? It still says "supported: soon" there, but I think we have at least 5 linkstations (2x davy_gravy, ramp, bauldrick and me) with the flash rom that once was the problem.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 11 posts ] 

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 1 guest


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:
Powered by phpBB® Forum Software © phpBB Limited