Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Tue Aug 14, 2018 11:56 pm

All times are UTC+01:00




Post new topic  Reply to topic  [ 58 posts ]  Go to page Previous 1 2 3 4 Next
Author Message
PostPosted: Fri Apr 03, 2009 4:25 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
Well, that went very well...
I downloaded your kernel and modules, installed them and it booted immediately. Are these the right ones?

I hope I understood you correctly...

Code:
foonas-em$ wget http://hvkls.dyndns.org/downloads/kernel_2.6.18-ls-uboot-nfs-v14.tar.gz
Connecting to hvkls.dyndns.org (78.34.232.101:80)
kernel_2.6.18-ls-ubo 100% |*********************************************************************|  1620k 00:00:00 ETA
foonas-em$ wget http://hvkls.dyndns.org/downloads/modules_2.6.18-ls-nfs-v14.tar.gz
Connecting to hvkls.dyndns.org (78.34.232.101:80)
modules_2.6.18-ls-nf 100% |*********************************************************************|  6351k 00:00:00 ETA






root@kurobox:~# uname -a
Linux kurobox 2.6.18-kurobox #2 Wed Feb 11 09:26:39 CET 2009 ppc unknown
root@kurobox:~# lsmod
Module                  Size  Used by
capability              5416  0
commoncap               8352  1 capability
nfsd                  268428  8
exportfs                6784  1 nfsd
lockd                  76980  2 nfsd
nfs_acl                 4480  1 nfsd
sunrpc                193128  3 nfsd,lockd,nfs_acl
ipv6                  319916  12
rfcomm                 48188  0
ircomm_tty             31464  0
ircomm                 18052  1 ircomm_tty
irda                  155764  2 ircomm_tty,ircomm
crc_ccitt               2176  1 irda
hidp                   19808  0
l2cap                  27140  4 rfcomm,hidp
bluetooth              64620  3 rfcomm,hidp,l2cap



root@kurobox:~# fw_printenv
bootargs=root=/dev/sda1 netconsole=6666@192.168.11.150/,@192.168.11.149/ rtc-rs5c372.probe=0,0x32
bootcmd=run bootcmd1
nfsboot=bootp;run nfsargs;bootm
bootdelay=10
baudrate=57600
autoload=no
stdin=nc
stdout=nc
stderr=nc
ipaddr=192.168.11.150
netmask=255.255.255.0
serverip=192.168.11.149
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=800000
hdpart=0:1
hdfile=boot/uImage
hdload=echo Loading ${hdpart}:${hdfile};ext2load ide ${hdpart} ${ldaddr} ${hdfile};ext2load ide ${hdpart} 7f0000 boot/kuroboxHD.dtb
boothd=setenv bootargs root=/dev/sda1 netconsole=6666@192.168.11.150/,@192.168.11.149/ rtc-rs5c372.probe=0,0x32;bootm ${ldaddr} - 7f0000
hdboot=run hdload boothd
flboot=setenv bootargs root=/dev/hda1;bootm ffc00000
emboot=setenv bootargs root=/dev/ram0;bootm ffc00000
nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off
bootretry=30
bootcmd3=run emboot
writeng=protect off fff70000 fff7ffff;era fff70000 fff7ffff;mw.l 800000 4e474e47 1;cp.b 800000 fff70000 4
writeok=protect off fff70000 fff7ffff;era fff70000 fff7ffff;mw.l 800000 4f4b4f4b 1;cp.b 800000 fff70000 4
ubpart=0:1
ubfile=share/u-boot/u-boot-hd.flash.bin
ubload=echo Loading ${ubpart}:${ubfile};ext2load ide ${ubpart} ${ldaddr} ${ubfile}
ubsaddr=fff00000
ubeaddr=fff2ffff
ubflash=protect off ${ubsaddr} ${ubeaddr};era ${ubsaddr} ${ubeaddr};cp.b ${ldaddr} ${ubsaddr} ${filesize};cmp.b ${ldaddr} ${ubsaddr} ${filesize}
upgrade=run ubload ubflash
ethact=COMET#0
foofl1=cp.b FFC00000 800000 2FFFFF;cp.b fff80000 AFFFFF 7E86B
foofl2=setenv bootargs root=/dev/ram0 rw;bootm ${ldaddr} - FFFFF6AC
fooflboot=run foofl1 foofl2
bootcmd1=run hdboot;run fooflboot
bootcmd2=run fooflboot
bootemhd=ide reset ; ext2load ide 0:1 800000  /boot/vmlinuxEM.UBoot ; ext2load ide 0:1 7f0000  /boot/kuroboxHD-EM.dtb ;  setenv bootargs console=ttyS0,57600 root=/dev/ram0 rw ; bootm 00800000 - 7f0000
root@kurobox:~#






EDIT: Bizarre, I saw something here that I've never seen before. The box spontaneously rebooted, and then gave me a lot of problems (would not boot, LED power light flashes) until I unplugged it.

I think I found a problem, in that my current installed distro has avr-evtd running on S0 normally, but the older kernels have it running on S1:
Code:
root      1978  0.0  0.8   1752   508 ?        Ss   21:48   0:00 /usr/sbin/avr_evtd -d /dev/ttyS1

I'm pretty sure there is some conflict here that is causing it to reboot and then it seems as if the microcontroller becomes confused ... unplugging and letting it sit unpowered for 15 seconds restores normal uboot/boot behavior, but it still reboots after 5 min or so.

EDIT2: OK, I tried killing avr_evtd and restarting it as :
Code:
/usr/sbin/avr_evtd -d /dev/ttyS0
, but this didn't help.

Something is messing w/ the watchdog, I think. Something is crashing avr_evtd.

_________________
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 Apr 03, 2009 10:20 am 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
That's the kernel I'm trying to boot. I've used its non-uboot version for months, with a avr_evtd configuration tweak from the upgradehelper package.

So you can boot it, by "run bootcmd1" I presume?

I would love to try your settings, if only I knew how to transform them into "setenv" commands.

Or could you maybe just create mtd-Dumps I could flash? I really want to get things going, and I do want to keep uboot.

BTW, does your / reside on /dev/hda or /dev/sda, according to /etc/fstab?


Top
   
PostPosted: Fri Apr 03, 2009 12:59 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
andre wrote:
1. That's the kernel I'm trying to boot. I've used its non-uboot version for months,

2. with a avr_evtd configuration tweak from the upgradehelper package.

3. So you can boot it, by "run bootcmd1" I presume?

3.5 I would love to try your settings, if only I knew how to transform them into "setenv" commands.

Or could you maybe just create mtd-Dumps I could flash?

4. I really want to get things going, and I do want to keep uboot.

5. BTW, does your / reside on /dev/hda or /dev/sda, according to /etc/fstab?


1 It is booting reliably for me (the box just shuts down after 5-6 minutes of uptime).
2. I'd be interested in knowing what your avr_evtd config looks like... I'm running foonas so it has a newer version, I think.
3. Actually, It is booting w/ out any intervention or commands from me ... so I guess that is bootcmd1.
3.5 As an example, to get that last line in my env vars, I just executed
Code:
fw_setenv bootemhd 'ide reset ; ext2load ide 0:1 800000  /boot/vmlinuxEM.UBoot ; ext2load ide 0:1 7f0000  /boot/kuroboxHD-EM.dtb ;  setenv bootargs console=ttyS0,57600 root=/dev/ram0 rw ; bootm 00800000 - 7f0000'

fw_printenv and fw_setenv are in Debian's uboot-envtools.

to run that mini-script, then it is just
Code:
run bootemhd
. It is basically a load of both uImage and dtb from the hdd, set bootargs, and then a bootm w/ the proper memory locations.

4. I have some time this next week as I'm on a break for a while, I'd be game to help out some.

5. Mine is on /dev/sda (pata driver).

Off to work now for me. ;)

_________________
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 Apr 04, 2009 4:11 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
OK, got it to stay booted ... had to change my /etc/default/avr_evtd config file. I changed the DEVICE line and turned a few things off. It now reads:

Code:
root@kurobox:/# cat /etc/default/avr_evtd
# Sample avr_evtd daemon configuration file
# PLEASE EDIT THIS FILE TO SUIT
# Debug log file location
LOG=/var/log
# Advanced use only.  Will log events when enabled
DEBUG=ON
# Set to YES to enable the EM-Mode feature, default no
#EMMODE=YES
# Timed shutdown flag (ON enables timed power down/up only
# or use days of the week MONWEDSAT etc
# if SHUTDOWN and POWERON are also specified)
TIMER=OFF
# To override the device scan, specify the desired
# serial port connection to the AVR below and remove the
# comment
DEVICE=/dev/ttyS0
# MACRO day/group switching ON/OFF times in 24hr HH:MM
SUN-SAT=OFF=01:15,ON=06:20
# Shutdown (default) time specified in 24hr format HH:MM
SHUTDOWN=
# Power on (default) time specified in 24hr format HH:MM
POWERON=
# Disk check, set to OFF or a value (0-100) specifying a
# percentage used at which the disk LED will illuminate
DISKCHECK=90
# Specify root partition for disk check, default is none
ROOT=hda1
# Specify working partition for disk check, default is none
#WORK=sda3
# Disk/AVR refresh rate (seconds), default 40
REFRESH=40
# Hold time (seconds) for button power-off, default 3
HOLD=3
# Enable/disable continous disk full messages, default off
DISKNAG=OFF
# Fan stationary fault timer (seconds), default 30
FANSTOP=15

The oddness is that while it does stay up now just fine, I don't think avr_evtd is working properly, as echo -n ZZZZ > /dev/ttyS0 (and other such commands) don't seem to work - in fact the sleeping LED is stuck on.

Maybe I need to change another setting? I'm running foonas, don't know if there is something here that requires a different version of avr_evtd with some tweak maybe?

_________________
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 Apr 04, 2009 8:14 am 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
>>2. with a avr_evtd configuration tweak from the upgradehelper package.

tar -xvzf latest-upgradehelper.tar.gz 'etc/default/avr_evtd' 'etc/init.d/avr_evtd'

avr_evtd is also inside.

>3.5 As an example, to get that last line in my env vars, I just executed
Code:
fw_setenv bootemhd 'ide reset ; ext2load ide 0:1 800000  /boot/vmlinuxEM.UBoot ; ext2load ide 0:1 7f0000  /boot/kuroboxHD-EM.dtb ;  setenv bootargs console=ttyS0,57600 root=/dev/ram0 rw ; bootm 00800000 - 7f0000'


Indeed "bootm 00800000 - 7f0000" could make the difference.

>fw_printenv and fw_setenv are in Debian's uboot-envtools.

Not in etch, and upgrading the debhelper etc. is very much of a hassle if you're planning to upgrade soon. The apps are in foonas-em, so I'll probably copy them over.

The question was targeted at the syntax of the setenv command. The combination of fw_setenv and setenv inside the single quotes should make the difference!

>5. Mine is on /dev/sda (pata driver).

Interesting, you can boot my kernel equipped with the old driver, and I can boot your 2.6.28.8 with /dev/hda.


Top
   
PostPosted: Sat Apr 04, 2009 1:25 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
OK, tried it, doesn't work for me. It just hangs. The /boot/* paths are OK, tried [hs]da1.

setenv bootnfs1 'ide reset ; ext2load ide 0:1 800000 /boot/uImage.nfs; ext2load ide 0:1 7f0000 /boot/kuroboxHD.dtb' ; saveenv

setenv bootnfs2 'setenv bootargs console=ttyS0,57600 root=/dev/sda1 rtc-rs5c372.probe=0,0x32 ; bootm 00800000 - 7f0000' ; saveenv

setenv bootnfs 'run bootnfs1 bootnfs2' ; saveenv

=> run bootnfs
run bootnfs

Reset IDE: Bus 0: OK
Device 0: Model: Hitachi HDT725050VLAT80 Firm: V56OA4NA Ser#: VF1400R4CWK25A
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)

1642081 bytes read

2387 bytes read
## Booting image at 00800000 ...
Image Name: Linux-2.6.18-kurobox
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1642017 Bytes = 1.6 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
Booting using flat device tree at 0x7f0000


Top
   
PostPosted: Sat Apr 04, 2009 2:38 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
I think I'm going to try to use that nfs kernel on my HG that has Lenny on it. That's a little closer to what you have on. There are some difference between foonas and Debian, apples & oranges. Will get back to you after some breakfast and coffee.

=================

OK tried it and it hangs. Since I don't have serial on either of those boxes, I can't tell what how it is crashing, or when in the boot process that it happens.

A few questions come to mind:
A. Is there something in this newer UBoot 1.2.0 that makes booting the older kernels problematic?
B. Is there some sort of arch mismatch - ppc vs. powerpc - that we aren't noticing?
C. Would using an older pre-fdt UBoot work better w/ the older kernels?
D. Is there something in Etch or Lenny that makes them incompatible w/ the kernel? (I can boot my foonas images w/ the older kernel, but not Debian w/ the older kernel.).

I'm going to try it w/ the older UBoot, and see if that makes a difference.

=================
Tried it, no boot. Now trying the legacy-hg-uboot-nfs kernel/module set w/ the older uboot. This has just got to work somehow. :D

Idea: Can we just take http://hvkls.dyndns.org/downloads/archi ... v11.tar.gz and convert it using mkimage? Using the "old" pre-powerpc arch method, like we used to, before needing the dtb files. Those kernels always worked great for me with uboot on my HG - the original ones you used to roll.

=================
I think I found the solution ... now running one of your old kernels very nicely... but using LNI's original 1.1.4 uboot , not the 1.2.0 with the ftd setup.

Code:
FreeLinkStation:~# uname -a    
Linux FreeLinkStation 2.6.20.8-kuroboxHG #33 Thu Apr 26 21:31:51 CEST 2007 ppc GNU/Linux
FreeLinkStation:~# uptime
 13:06:36 up 8 min,  1 user,  load average: 0.08, 0.14, 0.11
FreeLinkStation:~# fw_printenv
bootcmd=run bootcmd1
nfsboot=bootp;run nfsargs;bootm
bootdelay=10
baudrate=57600
autoload=no
...
ethact=RTL8169#0
hdfile=/boot/uImage
filesize=233FEB
...
bootargs=console=ttyS0,57600 root=/dev/hda1 rtc-rs5c372.probe=0,0x32
hdload=echo Loading ${hdpart}:${hdfile};ext2load ide ${hdpart} ${ldaddr} ${hdfile}
boothd=setenv bootargs root=/dev/hda1 netconsole=6666@192.168.11.150/,@192.168.11.149/ rtc-rs5c372.probe=0,0x32;bootm ${ldaddr}

_________________
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 Apr 04, 2009 7:28 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
I'm not sure how conclusive flat device kernel examples are. The problem seem to be the 2.6.18 kernels!

As to the conversion,

NAME="nfs11"
mkimage -A ppc -O linux -T kernel -C none -a 0x0 -e 0x0 -n "${NAME}" -d /path/to/vmlinux.bin /path/to/vmlinux.bin.${NAME}

What do I have to do to flash the older uboot; and will I be able to run kernel 2.6 in EM mode from flash ROM if I have to repair Lenny?


Top
   
PostPosted: Sun Apr 05, 2009 3:41 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
Long story short ... after 3 or 4 hours monkeying in irc (and it was fun :D ) andre and I have discovered that his original upstream-sourced kernels boot fine with either uboot (LNI's 1.1.4 or timtimred's 1.2.0) . Some of the newer uboot kernels that had a Debian(-ish) source did not work w/ uboot when converted w/ mkimage, using either uboot.

The ppc kernels that don't have the dtb files boot just fine w/ the newer uboot.

_________________
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: Sun Apr 05, 2009 11:52 am 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
It still doesn't work for me!

setenv bootargs 'console=ttyS0,57600 root=/dev/hda1 rtc-rs5c372.probe=0,0x32' ; ide reset ; ext2load ide 0:1 800000 /boot/uImage.nfs ; bootm 00800000

Reset IDE: Bus 0: OK
Device 0: Model: Hitachi HDT725050VLAT80 Firm: V56OA4NA Ser#: VF1400R4CWK25A
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)

3510470 bytes read
## Booting image at 00800000 ...
Image Name: 2.6.18-ls-v52-uboot
Image Type: PowerPC Linux Kernel Image (uncompressed)
Data Size: 3510406 Bytes = 3.3 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
OK

and hangs, with 'steady' main LED, until it reboots by itself after a few minutes!


Top
   
PostPosted: Sun Apr 05, 2009 3:02 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
:o I'm installing Debian on my LS1 and see if I can get the same behavior. The only difference between our boxes (as far as I know) is that you have Debian on yours, I have foonas on mine. (... it could make a difference). We will fix 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
   
PostPosted: Sun Apr 05, 2009 5:26 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
I would flash an older uboot version if only I was sure how to do that. More precisely, what device to flash LNI's files to.


Top
   
PostPosted: Sun Apr 05, 2009 6:19 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
andre, I just booted Debian (fresh install from tarball) on my LS1 w/ the newer uboot - the new uboot is fine :
Code:
U-Boot 1.2.0 (Apr 13 2007 - 22:25:08) LinkStation / KuroBox
stdin :   nc
stdout:   nc
stderr:   nc
IDE:   Bus 0: OK
  Device 0: Model: WDC WD1600BB-00GUC0 Firm: 08.02D08 Ser#: WD-WCAL94694474
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 152627.8 MB = 149.0 GB (312581808 x 512)
Boot in 08 seconds ('s' to stop)...s

=> setenv bootargs 'console=ttyS0,57600 root=/dev/hda1 rtc-rs5c372.probe=0,0x32'
setenv bootargs 'console=ttyS0,57600 root=/dev/hda1 rtc-rs5c372.probe=0,0x32'
=> ide reset ; ext2load ide 0:1 800000 /boot/uImage
ide reset ; ext2load ide 0:1 800000 /boot/uImage

Reset IDE: Bus 0: OK
  Device 0: Model: WDC WD1600BB-00GUC0 Firm: 08.02D08 Ser#: WD-WCAL94694474
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 152627.8 MB = 149.0 GB (312581808 x 512)

3510470 bytes read
=> bootm 00800000
bootm 00800000
## Booting image at 00800000 ...
   Image Name:   2.6.18-ls-v52-uboot
   Image Type:   PowerPC Linux Kernel Image (uncompressed)
   Data Size:    3510406 Bytes =  3.3 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
OK

Code:
davygravy@bitbaker-i686:~/Desktop$ telnet 192.168.11.170
Trying 192.168.11.170...
Connected to 192.168.11.170.
Escape character is '^]'.
Debian GNU/Linux 3.1 %h
root@LinkStation:/# uname -a
Linux LinkStation 2.6.18-kurobox #3 Wed Sep 20 22:00:59 CEST 2006 ppc GNU/Linux
root@LinkStation:/# uptime
 15:18:44 up 36 min,  0 users,  load average: 0.00, 0.00, 0.00
root@LinkStation:/#



I'd suggest the following:

Unplug your box and let sit for 30 seconds, plug back in and reboot into foonas-em...

mv your /boot to /bootbackup

do a fresh re-untarring of your two tarballs (kernel_2.6.18-ls-uboot-v52.tar and modules_2.6.18-ls-v52.tar)
make sure your boot looks like this:
Code:
root@LinkStation:/# ls /boot -lnaF
total 4472
drwxr-xr-x   2 0 0    4096 Nov 27 09:23 ./
drwxr-xr-x  24 0 0    4096 Nov 27 09:22 ../
-rw-r--r--   1 0 0   18011 Jun  1  2006 COPYING
lrwxrwxrwx   1 0 0      18 Nov 27 09:23 System.mapKB -> /boot/System.mapLS
lrwxrwxrwx   1 0 0      18 Nov 27 09:23 System.mapKG -> /boot/System.mapHG
-rw-r--r--   1 0 0  930271 Sep 20  2006 System.mapLS
-rw-r--r--   1 0 0   41863 Sep 16  2006 configHG
lrwxrwxrwx   1 0 0       8 Nov 27 09:23 configKB -> configLS
lrwxrwxrwx   1 0 0       8 Nov 27 09:23 configKG -> configHG
-rw-r--r--   1 0 0   44412 Sep 20  2006 configLS
-rw-r--r--   1 0 0 3510470 Sep 20  2006 uImage
lrwxrwxrwx   1 0 0       9 Nov 27 09:22 versionKB -> versionLS
lrwxrwxrwx   1 0 0       9 Nov 27 09:22 versionKG -> versionHG
-rw-r--r--   1 0 0      10 Sep 20  2006 versionLS
lrwxrwxrwx   1 0 0      19 Nov 27 09:22 vmlinux.binKB -> /boot/vmlinux.binLS
lrwxrwxrwx   1 0 0      19 Nov 27 09:22 vmlinux.binKG -> /boot/vmlinux.binHG


check your fstab:
Code:
root@LinkStation:/# cat /etc/fstab 
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>               <dump>  <pass>
/dev/hda1       /               ext3    defaults,noatime,errors=remount-ro      0 0
proc            /proc           proc    defaults                        0 0
none            /dev/pts        devpts  gid=5,mode=20                   0 0
/dev/hda2       swap            swap    defaults                        0 0
/dev/hda3       /mnt            ext3    defaults,noatime                0 0


I don't have avr_evtd installed yet, but I'd look at the config on it - shutting down after 5 minutes is often a symptom of the watchdog timer having a problem.

Finally in netconsole try exactly this:
Code:
=> setenv bootargs 'console=ttyS0,57600 root=/dev/hda1 rtc-rs5c372.probe=0,0x32'
setenv bootargs 'console=ttyS0,57600 root=/dev/hda1 rtc-rs5c372.probe=0,0x32'
=> ide reset ; ext2load ide 0:1 800000 /boot/uImage
ide reset ; ext2load ide 0:1 800000 /boot/uImage


If it doesn't go with this, then post back your output of printenv.

We will figure this out. :)

_________________
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: Sun Apr 05, 2009 6:42 pm 
Offline
Site Admin
User avatar

Joined: Sun Jul 17, 2005 4:34 pm
Posts: 5332
Did as you said, it doesn't work and reboots after about 5 mins. Local differences:

I'm on Etch (Debian 4); /etc/fstab also has got "nodiratime".

=> printenv
printenv
nfsboot=bootp;run nfsargs;bootm
bootdelay=10
baudrate=57600
autoload=no
stdin=nc
stdout=nc
stderr=nc
ipaddr=192.168.11.150
netmask=255.255.255.0
serverip=192.168.11.149
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
hdfile=boot/uImage
hdload=echo Loading ${hdpart}:${hdfile};ext2load ide ${hdpart} ${ldaddr} ${hdfile};ext2load ide ${hdpart} 7f0000 boot/kuroboxHD.dtb
boothd=setenv bootargs root=/dev/sda1 netconsole=6666@192.168.11.150/,@192.168.11.149/ rtc-rs5c372.probe=0,0x32;bootm ${ldaddr} - 7f0000
hdboot=run hdload boothd
flboot=setenv bootargs root=/dev/hda1;bootm ffc00000
emboot=setenv bootargs root=/dev/ram0;bootm ffc00000
nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off
bootretry=30
bootcmd3=run emboot
writeng=protect off fff70000 fff7ffff;era fff70000 fff7ffff;mw.l 800000 4e474e47 1;cp.b 800000 fff70000 4
writeok=protect off fff70000 fff7ffff;era fff70000 fff7ffff;mw.l 800000 4f4b4f4b 1;cp.b 800000 fff70000 4
ubpart=0:1
ubfile=share/u-boot/u-boot-hd.flash.bin
ubload=echo Loading ${ubpart}:${ubfile};ext2load ide ${ubpart} ${ldaddr} ${ubfile}
ubsaddr=fff00000
ubeaddr=fff2ffff
ubflash=protect off ${ubsaddr} ${ubeaddr};era ${ubsaddr} ${ubeaddr};cp.b ${ldaddr} ${ubsaddr} ${filesize};cmp.b ${ldaddr} ${ubsaddr} ${filesize}
upgrade=run ubload ubflash
ethact=COMET#0
sdboot=run sdload bootsd
sdfile=boot/vmlinux.UBoot
sdload=echo Loading ${hdpart}:${sdfile};ext2load ide ${hdpart} ${ldaddr} ${sdfile};ext2load ide ${hdpart} 7f0000 boot/kuroboxHD.dtb
hdpart=0:1
ldaddr=800000
bootsd=setenv bootargs root=/dev/sda1 netconsole=6666@192.168.11.150/,@192.168.11.149/ rtc-rs5c372.probe=0,0x32;bootm 00800000 - 7f0000
bootcmd=run sdboot
foofl1=cp.b FFC00000 800000 2FFFFF;cp.b fff80000 AFFFFF 7E86B
foofl2=setenv bootargs root=/dev/ram0 rw;bootm ${ldaddr} - FFFFF6AC
fooflboot=run foofl1 foofl2
bootcmd1=run hdboot;run fooflboot
bootcmd2=run fooflboot
bootnfs=run bootnfs1 bootnfs2
filesize=190E61
bootnfs1=ide reset ; ext2load ide 0:1 800000 /boot/uImage.nfs; ext2load ide 0:1 7f0000 /boot/kuroboxHD.dtb
bootnfs2=setenv bootargs console=ttyS0,57600 root=/dev/hda1 rtc-rs5c372.probe=0,0x32 ; bootm 800000 - 7f0000



What's weird: There's no "pulse" indicating anything is booting when I run the bootcommand.


Top
   
PostPosted: Mon Apr 06, 2009 6:07 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
I'm still not sure why yours doesn't boot, but mine does. I can't replicate whatever is causing your failure... yet (see #7). The only significant thing I can see that is different about our boxes is that your box (if I understand correctly) had its ROM flashed in one contiguous piece. (If I misunderstand, then you must have flashed in uboot, foonas-em and env vars all in separate dd commands. I am assuming that your blitzer script/program does it in a single flash.)

Here are some things we can try - the order that I present them in is my opinion of what could be done 1st, 2nd, etc. I cut and pasted the commands, and then output straight from my windows... so they've all been tested and worked on my LS1. You may want to consider going straight to step 6.

0. I'm assuming that your kernel is in /boot/uImage and modules as normal, also assuming that you use these three lines to boot while in uboot:

Code:
setenv bootargs 'console=ttyS0,57600 root=/dev/hda1 rtc-rs5c372.probe=0,0x32'
ide reset ; ext2load ide 0:1 800000 /boot/uImage
bootm 00800000



1. (you will have to boot into foonas-em and mount sda1 for this...) From the avr_evtd config on your hdd, could you please post back with the result of

Code:
 cat  etc/default/avr_evtd | grep =


Quote:
root@FreeLinkStation:/# cat /etc/default/avr_evtd | grep =
LOG=/var/log
DEBUG=ON
EMMODE=YES
TIMER=OFF
#DEVICE=/dev/ttyS1
SUN-SAT=OFF=01:15,ON=06:20
SHUTDOWN=
POWERON=
DISKCHECK=90
ROOT=hda1
#WORK=sda3
REFRESH=40
HOLD=3
DISKNAG=OFF
FANSTOP=15



2. Start it up in Christmas Tree mode, just in case this has something to do w/ the watchdog. Press and hold the red reset button on the back, and then start it with the normal power button on the front. Use the boot commands above in #0. If it doesn't shut down after a 5 minutes, it may indicate that something is interfering w/ the watchdog timer.

In case there is something odd with the microcontroller, you could leave the device powered down and unplugged overnight.


3. Check to see that your flash layout is what we expect:

Code:
cat /proc/mtd


Quote:
root@LinkStation:/bootnewbackupgood# cat /proc/mtd
dev: size erasesize name
mtd0: 00300000 00010000 "mtd_firmimg"
mtd1: 00070000 00010000 "mtd_bootcode"
mtd2: 00010000 00010000 "mtd_status"
mtd3: 00080000 00010000 "mtd_conf"
mtd4: 00400000 00010000 "mtd_allflash"
mtd5: 000f0000 00010000 "mtd_data"




4. Reflash uboot 1.2.0, separately. In terms of trying to reflash anything, this should be our first try, I think. Boot into foonas-em, and:
Code:
wget http://downloads.buffalo.nas-central.org/LS1_PPC/Bootloader/Uboot/Precompiled/u-boot-lsppchd-flash-1.2.0-r2.bin
dd if=u-boot-lsppchd-flash-1.2.0-r2.bin of=/dev/mtdblock1 bs=1k
cmp u-boot-lsppchd-flash-1.2.0-r2.bin /dev/mtd1



Quote:
foonas-em$ wget http://downloads.buffalo.nas-central.or ... 2.0-r2.bin
Connecting to downloads.buffalo.nas-central.org (140.211.169.172:80)
u-boot-lsppchd-flash 100% |****************************************************************************************************************************| 174k 00:00:00 ETA
foonas-em$ dd if=u-boot-lsppchd-flash-1.2.0-r2.bin of=/dev/mtdblock1 bs=1k
174+1 records in
174+1 records out
foonas-em$ cmp u-boot-lsppchd-flash-1.2.0-r2.bin /dev/mtd1
cmp: EOF on u-boot-lsppchd-flash-1.2.0-r2.bin


Reboot, and then do #0.


5. Erase the env vars section (return/reset to compiled-in values) in case something odd is set in ROM env vars (copied from Bauldrick's settings? - something we aren't seeing?). Note that if you do this, then any values that you had changed would have to be re-entered using the "setenv" commands. For that reason, you may want to do a "printenv" and then copy the output to a text file for safe keeping.

Code:
protect off fff60000 fff6ffff
era fff60000 fff6ffff
protect on fff60000 fff6ffff
reset



I tested this commands, output is below, showing Before and After...


Quote:
U-Boot 1.2.0 (Apr 13 2007 - 22:25:08) LinkStation / KuroBox
stdin : nc
stdout: nc
stderr: nc
IDE: Bus 0: OK
Device 0: Model: WDC WD1600BB-00GUC0 Firm: 08.02D08 Ser#: WD-WCAL94694474
Type: Hard Disk
Supports 48-bit addressing
Capacity: 152627.8 MB = 149.0 GB (312581808 x 512)
Boot in 09 seconds ('s' to stop)...s
Boot in 08 seconds ('s' to stop)...
=> printenv
printenv
bootargs=root=/dev/sda1 netconsole=6666@192.168.11.150/,@192.168.11.149/ rtc-rs5c372.probe=0,0x32
bootcmd=run bootcmd1
nfsboot=bootp;run nfsargs;bootm
bootdelay=10
baudrate=57600
autoload=no
stdin=nc
stdout=nc
stderr=nc
ipaddr=192.168.11.150
netmask=255.255.255.0
serverip=192.168.11.149
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=800000
hdpart=0:1
hdfile=boot/uImage
hdload=echo Loading ${hdpart}:${hdfile};ext2load ide ${hdpart} ${ldaddr} ${hdfile};ext2load ide ${hdpart} 7f0000 boot/kuroboxHD.dtb
boothd=setenv bootargs root=/dev/sda1 netconsole=6666@192.168.11.150/,@192.168.11.149/ rtc-rs5c372.probe=0,0x32;bootm ${ldaddr} - 7f0000
hdboot=run hdload boothd
flboot=setenv bootargs root=/dev/hda1;bootm ffc00000
emboot=setenv bootargs root=/dev/ram0;bootm ffc00000
nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off
bootretry=30
bootcmd3=run emboot
writeng=protect off fff70000 fff7ffff;era fff70000 fff7ffff;mw.l 800000 4e474e47 1;cp.b 800000 fff70000 4
writeok=protect off fff70000 fff7ffff;era fff70000 fff7ffff;mw.l 800000 4f4b4f4b 1;cp.b 800000 fff70000 4
ubpart=0:1
ubfile=share/u-boot/u-boot-hd.flash.bin
ubload=echo Loading ${ubpart}:${ubfile};ext2load ide ${ubpart} ${ldaddr} ${ubfile}
ubsaddr=fff00000
ubeaddr=fff2ffff
ubflash=protect off ${ubsaddr} ${ubeaddr};era ${ubsaddr} ${ubeaddr};cp.b ${ldaddr} ${ubsaddr} ${filesize};cmp.b ${ldaddr} ${ubsaddr} ${filesize}
upgrade=run ubload ubflash
ethact=COMET#0
foofl1=cp.b FFC00000 800000 2FFFFF;cp.b fff80000 AFFFFF 7E86B
foofl2=setenv bootargs root=/dev/ram0 rw;bootm ${ldaddr} - FFFFF6AC
fooflboot=run foofl1 foofl2
bootcmd1=run hdboot;run fooflboot
bootcmd2=run fooflboot
bootemhd=ide reset ; ext2load ide 0:1 800000 /boot/vmlinuxEM.UBoot ; ext2load ide 0:1 7f0000 /boot/kuroboxHD-EM.dtb ; setenv bootargs console=ttyS0,57600 root=/dev/ram0 rw ; bootm 00800000 - 7f0000

Environment size: 2038/65532 bytes
=> protect off fff60000 fff6ffff
protect off fff60000 fff6ffff
Un-Protected 1 sectors
=> era fff60000 fff6ffff
era fff60000 fff6ffff

Flash erase: first = 54 @ 0xfff60000
last = 54 @ 0xfff60000
Flash erase: Done
Erased 1 sectors
=> protect on fff60000 fff6ffff
protect on fff60000 fff6ffff
Protected 1 sectors
=> reset
reset

U-Boot 1.2.0 (Apr 13 2007 - 22:25:08) LinkStation / KuroBox
stdin : nc
stdout: nc
stderr: nc
IDE: Bus 0: OK
Device 0: Model: WDC WD1600BB-00GUC0 Firm: 08.02D08 Ser#: WD-WCAL94694474
Type: Hard Disk
Supports 48-bit addressing
Capacity: 152627.8 MB = 149.0 GB (312581808 x 512)
Boot in 08 seconds ('s' to stop)...
Boot in 06 seconds ('s' to stop)...s

=> print
print
bootargs=root=/dev/sda1 netconsole=6666@192.168.11.150/,@192.168.11.149/ rtc-rs5c372.probe=0,0x32
bootcmd=run bootcmd1
nfsboot=bootp;run nfsargs;bootm
bootdelay=10
baudrate=57600
autoload=no
stdin=nc
stdout=nc
stderr=nc
ipaddr=192.168.11.150
netmask=255.255.255.0
serverip=192.168.11.149
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=800000
hdpart=0:1
hdfile=boot/uImage
hdload=echo Loading ${hdpart}:${hdfile};ext2load ide ${hdpart} ${ldaddr} ${hdfile};ext2load ide ${hdpart} 7f0000 boot/kuroboxHD.dtb
boothd=setenv bootargs root=/dev/sda1 netconsole=6666@192.168.11.150/,@192.168.11.149/ rtc-rs5c372.probe=0,0x32;bootm ${ldaddr} - 7f0000
hdboot=run hdload boothd
flboot=setenv bootargs root=/dev/hda1;bootm ffc00000
emboot=setenv bootargs root=/dev/ram0;bootm ffc00000
nfsargs=setenv bootargs root=/dev/nfs rw nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off
bootretry=30
bootcmd1=run hdboot;run flboot
bootcmd2=run flboot
bootcmd3=run emboot
writeng=protect off fff70000 fff7ffff;era fff70000 fff7ffff;mw.l 800000 4e474e47 1;cp.b 800000 fff70000 4
writeok=protect off fff70000 fff7ffff;era fff70000 fff7ffff;mw.l 800000 4f4b4f4b 1;cp.b 800000 fff70000 4
ubpart=0:1
ubfile=share/u-boot/u-boot-hd.flash.bin
ubload=echo Loading ${ubpart}:${ubfile};ext2load ide ${ubpart} ${ldaddr} ${ubfile}
ubsaddr=fff00000
ubeaddr=fff2ffff
ubflash=protect off ${ubsaddr} ${ubeaddr};era ${ubsaddr} ${ubeaddr};cp.b ${ldaddr} ${ubsaddr} ${filesize};cmp.b ${ldaddr} ${ubsaddr} ${filesize}
upgrade=run ubload ubflash
ethact=COMET#0

Environment size: 1673/65532 bytes
=>



6. Try flashing in the old uboot 1.1.4 that LNI made for us. It will boot 2.6 kernels up to 2.6.whenever-dtbs-were-introduced... If you do this, you won't be able to use foonas-em, but you'll still have mindbender's 2.4.33.3v3 firmimg.bin to use, and it is pretty good. It doesn't have wget, just ftp. I've never used it for chrooting - can't confirm that it works w/ that. (When using it, just remember one thing... The ftp is fine, just remember to create a dir on your hda called ftpin and chmod -R 777 ftpin so that you can write to it.)

Note, the 2nd flash takes a longer time... like 4 or 5 minutes. Don't be worried if it seems like it is taking a while.


Code:
wget http://downloads.buffalo.nas-central.org/Users/linuxnotincluded/uboot/u-boot-1.1.4-2.01LNI_patched_binaries/u-boot-hd-2.01.LNI.Patched
dd if=u-boot-hd-2.01.LNI.Patched of=/dev/mtdblock1 bs=1k
cmp u-boot-hd-2.01.LNI.Patched  /dev/mtd1

wget http://downloads.buffalo.nas-central.org/LS1_PPC/Initrds/telnet_and_ftp_enabled/LS1/firmimg.bin
dd if=firmimg.bin of=/dev/mtdblock0 bs=1k
cmp firmimg.bin /dev/mtd0



Quote:
foonas-em$ cd /
foonas-em$ wget http://downloads.buffalo.nas-central.or ... NI.Patched
Connecting to downloads.buffalo.nas-central.org (140.211.169.172:80)
u-boot-hd-2.01.LNI.P 100% |****************************************************************************************************************************| 162k --:--:-- ETA
foonas-em$ dd if=u-boot-hd-2.01.LNI.Patched of=/dev/mtdblock1 bs=1k
162+1 records in
162+1 records out
foonas-em$ cmp u-boot-hd-2.01.LNI.Patched /dev/mtd1
cmp: EOF on u-boot-hd-2.01.LNI.Patched
foonas-em$ wget http://downloads.buffalo.nas-central.or ... irmimg.bin
Connecting to downloads.buffalo.nas-central.org (140.211.169.172:80)
firmimg.bin 100% |****************************************************************************************************************************| 2901k 00:00:00 ETA
foonas-em$ dd if=firmimg.bin of=/dev/mtdblock0 bs=1k
2901+1 records in
2901+1 records out
foonas-em$ cmp firmimg.bin /dev/mtd0
cmp: EOF on firmimg.bin
foonas-em$


Once you reboot, via netconsole you will probably have to change one uboot env var. Your kernel in boot is probably called uImage. If that is teh case, it is easiest to just change the var hdfile from its current value of boot/vmlinux.UBoot to boot/uImage:

Code:
setenv hdfile boot/uImage
saveenv
run writeng
run emboot


Quote:
=> print hdfile
print hdfile
hdfile=boot/vmlinux.UBoot
=> setenv hdfile boot/uImage
setenv hdfile boot/uImage
=> saveenv
saveenv
Saving Environment to Flash...
Un-Protected 1 sectors
Erasing Flash...
Flash erase: first = 54 @ 0xfff60000
last = 54 @ 0xfff60000
Flash erase: Done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
=> run writeng
run writeng
Un-Protected 1 sectors

Flash erase: first = 55 @ 0xfff70000
last = 55 @ 0xfff70000
Flash erase: Done
Erased 1 sectors
Copy to Flash... done
=> run emboot
run emboot
## Booting image at ffc00000 ...

******* Product Information *******
----------------------------------
Product Name: HD-HLAN(IENOBU)
VER: 1.51
Date: 2005/12/28 10:0:5
----------------------------------
Verifying checksum... OK
Uncompressing kernel...done.
Loading Ramdisk at 0x03C68000, end 0x03E6EB00 ... OK
Booting the kernel


This will take you into bender's EM mode...
Quote:
telnet 192.168.11.162
Trying 192.168.11.162...
Connected to 192.168.11.162.
Escape character is '^]'.

Linkstation HD-HLAN - http://www.linkstationwiki.net

You are in EM-Mode!

There is no root-password. Just enter "root".

FTP-Access
User: operator
Pass: operator

fdisk is included. use it for custom partition sizes.

Execute "mount_disk" to mount the system + data partitions to /mnt/hdaX
Both partitions can be accessed via FTP then.

It is essential that no HDD is mounted if you want to flash with Buffalo`s firmwareupdater. If you mounted the partitions, execute "reboot" before trying to flash.

You can get out of EM-Mode either by flashing or by executing "write_ng"

HD-HLAN-EM login: root


BusyBox v0.60.5 (2003.07.30-12:03+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

#



It has no uboot-envutils built in, so with this setup you need to make adjustments only in uboot mode.





7. I can try flashing in the full ROM image that Bauldrick sent to you on _my_ box. If there is something odd in it then I might be able to troubleshoot 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
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 58 posts ]  Go to page Previous 1 2 3 4 Next

All times are UTC+01:00


Who is online

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