Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Fri Apr 20, 2018 10:55 pm

All times are UTC+01:00




Post new topic  Reply to topic  [ 38 posts ]  Go to page Previous 1 2 3
Author Message
PostPosted: Sat Sep 19, 2009 3:18 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
check your message inbox ... I pm-ed you...

_________________
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
   
PostPosted: Thu Oct 01, 2009 3:44 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
This is the first box that I have flashed that has the Fujitsu chip. Something was acting strangely here. I'm not sure if it was an intermittent power connect and pins on the board (you can see that the one side of it is broken away - the pins were bent - I straightened them out), or if the PSU is weak... ?

But, after about 6 attempts and 3 trips to the soldering bench, it has a heartbeat.


Code:
192.168.11.150: inverse host lookup failed: Unknown host
(UNKNOWN) [192.168.11.150] 6666 (?) open

U-Boot 1.2.0 (Apr 13 2007 - 22:25:08) LinkStation / KuroBox
stdin :   nc
stdout:   nc
stderr:   nc
IDE:   Bus 0: not available 
Boot in 05 seconds ('s' to stop)...s

=> flinfo
flinfo

Bank # 1: Flash chip: FUJITSU MBM29PL32TM

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
No Vpp line
Typical byte/word write timeout: 128 us
Maximum byte/word write timeout: 256 us
Typical full buffer write timeout: 128 us
Maximum full buffer write timeout: 4096 us
Typical block erase timeout: 1024 ms
Maximum block erase timeout: 16384 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: 32
Number of Erase Block Regions: 2

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

Size: 4 MiB in 71 Sectors
  Sector Start Addresses:
    FFC00000 (RO) FFC10000 (RO) FFC20000 (RO) FFC30000 (RO) FFC40000 (RO)
    FFC50000 (RO) FFC60000 (RO) FFC70000 (RO) FFC80000 (RO) FFC90000 (RO)
    FFCA0000 (RO) FFCB0000 (RO) FFCC0000 (RO) FFCD0000 (RO) FFCE0000 (RO)
    FFCF0000 (RO) FFD00000 (RO) FFD10000 (RO) FFD20000 (RO) FFD30000 (RO)
    FFD40000 (RO) FFD50000 (RO) FFD60000 (RO) FFD70000 (RO) FFD80000 (RO)
    FFD90000 (RO) FFDA0000 (RO) FFDB0000 (RO) FFDC0000 (RO) FFDD0000 (RO)
    FFDE0000 (RO) FFDF0000 (RO) FFE00000 (RO) FFE10000 (RO) FFE20000 (RO)
    FFE30000 (RO) FFE40000 (RO) FFE50000 (RO) FFE60000 (RO) FFE70000 (RO)
    FFE80000 (RO) FFE90000 (RO) FFEA0000 (RO) FFEB0000 (RO) FFEC0000 (RO)
    FFED0000 (RO) FFEE0000 (RO) FFEF0000 (RO) FFF00000 (RO) FFF10000 (RO)
    FFF20000 (RO) FFF30000 (RO) FFF40000 (RO) FFF50000 (RO) FFF60000 (RO)
    FFF70000 (RO) FFF80000 (RO) FFF90000 (RO) FFFA0000 (RO) FFFB0000 (RO)
    FFFC0000 (RO) FFFD0000 (RO) FFFE0000 (RO) FFFF0000 (RO) FFFF2000 (RO)
    FFFF4000 (RO) FFFF6000 (RO) FFFF8000 (RO) FFFFA000 (RO) FFFFC000 (RO)
    FFFFE000 (RO)
=>


-------------------------------------------------------

Part 2:

OK, you do have some sort of intermittent contact/short on the board. It is sporadic and doesn't seem to be influeced by position. It may be that plug that I mentioned or it may be something else. I'll try removing the jtag header pins and make sure that area looks clean/unharmed.

UBoot -is- in flash, but sometimes when it boots it doesn't recognize the flash. Never seen this before, but will send something out to you by Friday, one way or the other. Check you mailbox, as I PM-ed you.

_________________
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
   
PostPosted: Fri Oct 02, 2009 5:32 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
managed to get foonas-em in it successfully...

Code:
root@DuoBuntu:/# telnet 192.168.11.160
Trying 192.168.11.160...
Connected to 192.168.11.160.
Escape character is '^]'.

   ______ _____ _____ __   __  _____  ______
  |   ___|     |     |   \|  |/  _  \|   ___|
 _|   ___|  -  |  -  |       |   _   |\   \
| |__|   |_____|_____|__|\___|__| |__|_\   \
|___________________________________________|

foonas-em for lsppchd - http://foonas.org

lsppchd login: root
Password:
foonas-em$ uname -a
Linux lsppchd 2.6.30.5-foonas-em #1 Sun Aug 23 14:34:52 CDT 2009 ppc GNU/Linux

_________________
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
   
PostPosted: Mon Oct 12, 2009 2:22 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
patrick, I saw your message on the irc.

If you are sure that you have untarred the contents of the Debian image on your hdd, on partition 1, then it is possible that your uboot is not seeing the partition because of some sort of inode size problem.

Are you using the foonas-em image that I installed?

If so, I tested it out and it worked OK for me...

If you can't get anywhere on it, then try posting back your commands & output (yup, everything) & I can take a look at 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
   
PostPosted: Mon Oct 12, 2009 4:21 am 
Offline
Newbie

Joined: Thu Nov 20, 2008 4:37 pm
Posts: 20
As elsewhere in this process, it's quite likely I made a mistake at some point. No doubt fate is messing with me for wanting to tear up a perfectly good, functional foonas installation :D.

I created partitions of size 5G, 512M and whatever's left, ~460G in busybox's fdisk, and marked 1 and 3 as ext3, 2 as swap. Then I used mk2efs on 1 and 3 to make ext3 filesystems with blocksize=2k.

I tried uploading the tgz from http://downloads.buffalo.nas-central.or ... TmpImages/, but the version of tar available on the foonas busybox lacks the -z option so I resorted to unpacking with 7zip to a folder in Win7 and ftp-ing the contents into /mnt/sda1. I imagine this could have caused permissions problems.

I don't have a serial header installed, so I've been getting all of my output from watching wireshark. I don't have the exact output, but it would count down, say that it couldn't find /boot/uImage or /boot/kuroboxHD.dtb, and then proceed to boot foonas. Then I noticed that /boot on sda1 (rather than in flash) was empty, so I grabbed latest-kernel-uboot andlatest-modules from hvkls.dyndns.org, the webinstaller site and unpacked those to their respective directories, again via Win7.

Now, when I boot it still counts down, but prints "Loading 0:1boot/uImage" slowly, one character per packet. Then

0 bytes read
2371 bytes read
## Booting image at 00800000

And it proceeds to boot foonas.

I would have posted earlier, but after all the effort from the community and you davy, in particular I wanted to be especially thorough. I think I read every posted document on freelink, but since foonas doesn't use the stock block device nomenclature I didn't want to risk re-bricking the device.


Top
   
PostPosted: Mon Oct 12, 2009 11:33 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
If I were you, I'd try this:

1. Proceed as you did before, using fdisk to set up the partitions... make sure sda1 & sda3 are both type 83, but sda2 of type 82 (swap).

2. Don't apply any extra operands/options when making your fs in sda1 & sda3 ... just
Code:
mkfs.ext3 /dev/sda1
for instance ... don't specify the block size ...

also use mkswap on /dev/sda2 and then use swapon /dev/sd2

3. mount /dev/sda1 and cd to it...
run df -h to see that you see your expected 5GB size for sda1

if that doesn't work right, then try a different size of partition, say 4GB or 6GB ... back in step 1 &

4. download the tarball onto that partition sda1

gunzip tarballname.tar.gz
tar xvf tarballname.tar


5. use vi to edit and tweak your network setup, and then try booting it again...

If it doesn't work, please post back your output, as we might be able to spot a problem in it that way...

_________________
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
   
PostPosted: Sat Oct 17, 2009 5:42 pm 
Offline
Newbie

Joined: Thu Nov 20, 2008 4:37 pm
Posts: 20
It worked! I followed the procedure and unpacked the webinstaller kernel and modules, and it happily booted. I'm not clear on how this is different from my last try, except that doing it all in linux prevented whatever I did to botch it.

I'll keep my eye on it as I poke it (and hope I don't destroy it again) but thanks to everyone for the help, and davy in particular.


Top
   
PostPosted: Sat Oct 17, 2009 5:53 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
np, happy it worked out 4 u.
:biglol: :up: :)

_________________
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
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 38 posts ]  Go to page Previous 1 2 3

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 6 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:
Powered by phpBB® Forum Software © phpBB Limited