Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Wed Jul 18, 2018 2:00 am

All times are UTC+01:00




Post new topic  Reply to topic  [ 120 posts ]  Go to page 1 2 3 4 58 Next
Author Message
PostPosted: Mon Aug 03, 2009 3:20 am 
Offline
Newbie

Joined: Sun Aug 05, 2007 4:15 am
Posts: 36
Alpha testers needed. Please go to http://sites.google.com/site/shihsung/linkstation-mips if you are interested.

DO NOT TRY IT YET IF YOU ARE NOT JTAG PROFICIENT!!!


Top
   
PostPosted: Mon Aug 03, 2009 8:17 pm 
Offline
Betatester
User avatar

Joined: Thu Jul 14, 2005 4:38 pm
Posts: 941
Location: England
Great work!!

I have LNI's uboot (that I'm happy with as it does what I need), but you're patch for latest kernel I shall try now.

Do you know if your uboot solves the problem that certain chips have with flashing foonas-em to second halve.

I'm happy :up:


Top
   
PostPosted: Mon Aug 03, 2009 8:24 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
Hmmm... this is very interesting...

I see your directions for compiling and booting a new kernel... I had tried to do something on this, but couldn't get it to go (I am stuck at 2.6.23.17).

Is your 2.6.30.4 kernel based on something like the RB532 (which is at least partially supported in the vanilla kernel)?

Is the new uboot you built required for booting the new kernel you built? Would the older uboot work instead?

BTW, Shihsung, which ROM chip does your LS2 have?

NOTE: Shihsung's previous post regarding LS2 Kernel&UBoot dev is here : viewtopic.php?f=12&t=3653

_________________
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: Tue Aug 04, 2009 7:14 am 
Offline
Newbie

Joined: Sun Aug 05, 2007 4:15 am
Posts: 36
Bauldrick,
I don't know the answer to your question. It works for both of my MIPS LinkStations. Do you know which chips have problems? You can try the RAM build version to see if it works for you without flashing it. For example,

tftp 81000000 192.168.1.100:u-boot-2009.06-hdhlan-ram.elf
bootelf 81000000


davy_gravy,
I will need more info to diagnose your problem, such as your screen captures. Did you try my U-Boot or use others'? What's your environment settings, output of printenv?
No, I just download the mainline kernel and start porting from scratch.
My old U-Boot doesn't support the new version of the EXT2 filesystem with dynamic inode size and it doesn't know how to retrieve the MAC address from NVRAM and flash.
My systems have STM M29DW324DB(MID=0x20, DID=0x5d) and MXIC MX29LV320AT(MID=0xc2, DID=0xa7).


Top
   
PostPosted: Tue Aug 04, 2009 4:41 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
shihsung wrote:
davy_gravy,
1. I will need more info to diagnose your problem, such as your screen captures. Did you try my U-Boot or use others'? What's your environment settings, output of printenv?
2. No, I just download the mainline kernel and start porting from scratch.
3. My old U-Boot doesn't support the new version of the EXT2 filesystem with dynamic inode size and it doesn't know how to retrieve the MAC address from NVRAM and flash.
4. My systems have STM M29DW324DB(MID=0x20, DID=0x5d) and MXIC MX29LV320AT(MID=0xc2, DID=0xa7).


shisung, thanks for you quick answer back...

1. I had been trying to widen/port florian fianelli's RB532 mainline/vanilla work so that the LS2 would boot, but never got it to go. The RB532 has the same SoC and is based on the same board as the LS2, though there are some differences (peripheral, mainly, IIRC).

I managed to compile the 2.6.30.4 kernel last night (with a slightly wider selection of modules), and will test it today. I used (a fork of) OpenEmbedded to do that. (ipkg needs a minor change in the name of the kernel package in order to finish the build, but the change needed for this is trivial, minor tweak of the config)

2. Awesome.

3. By "new version of the EXT2 filesystem with dynamic inode size", do you mean ext4?

4. A few of the chips we've seen...

STMICRO M29W324DB (AMD/Fujitsu Standard)
STMICRO M29W324DT (AMD/Fujitsu Standard)
FUJITSU MBM29PL32TM (AMD/Fujitsu Standard)
Macronix MX29LV320T

... some of the STMICRO chips have given us problems when trying to flash across certain boundaries... viewtopic.php?f=12&t=3769&start=105

_________________
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: Tue Aug 04, 2009 5:39 pm 
Offline
Site Admin
User avatar

Joined: Mon Jul 11, 2005 7:19 am
Posts: 7703
Location: Austria, Vienna
excellent work shihsung.

do you plan to submit any patches to kernel.org?

_________________
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
   
PostPosted: Wed Aug 05, 2009 7:57 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
Huzzah!
Da shiz! :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: 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

=> ext2load ide 0:1 82000000 /boot/vmlinuz-2.6.30.4
ext2load ide 0:1 82000000 /boot/vmlinuz-2.6.30.4

5807365 bytes read
=> setenv bootargs  root=/dev/sda1 rw
setenv bootargs  root=/dev/sda1 rw
=> bootm
bootm
## Booting image at 82000000 ...
Loading .text @ 0x80002000 (3663256 bytes)
Loading __ex_table @ 0x803805a0 (6672 bytes)
...


Code:
root@LINKSTATION:~# uname -a
Linux LINKSTATION 2.6.30.4 #1 Tue Aug 4 11:00:32 CDT 2009 mips 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: Wed Aug 05, 2009 8:46 am 
Offline
Newbie

Joined: Sun Aug 05, 2007 4:15 am
Posts: 36
davy_gravy,
No, dynamic inode size applies to EXT2 and EXT3 filesystems, too. Here's a link for your reference: http://www.nabble.com/ext2-inode-size-p ... 67976.html. I ran into the issue on my PC, too. The old grub would not boot my newly restored system from my backup because I use the new KNOPPIX 6.01 live cd to prepare the filesystems. I knew the issue when I first encountered it with U-Boot and found a patch by Ryan Chen. BTW, you just remind me to add a credit section where credit is due. :-)

My U-Boot works with STM M29W324DT as shown below. Hopefully someone could verify whether it works on the bottom boot version.

Code:
HD-HLAN# fl                                                          

Bank # 1: CFI conformant FLASH (8 x 16)  Size: 4 MB in 71 Sectors
  AMD Standard command set, Manufacturer ID: 0xC2, Device ID: 0xA7A7
  Erase timeout: 16384 ms, write timeout: 1 ms                     

  Sector Start Addresses:
  BFC00000   RO   BFC10000   RO   BFC20000   RO   BFC30000   RO   BFC40000     
  BFC50000        BFC60000        BFC70000        BFC80000        BFC90000     
  BFCA0000        BFCB0000        BFCC0000        BFCD0000        BFCE0000     
  BFCF0000        BFD00000        BFD10000        BFD20000        BFD30000     
  BFD40000        BFD50000        BFD60000        BFD70000        BFD80000     
  BFD90000        BFDA0000        BFDB0000        BFDC0000        BFDD0000     
  BFDE0000        BFDF0000        BFE00000        BFE10000        BFE20000     
  BFE30000        BFE40000        BFE50000        BFE60000        BFE70000     
  BFE80000        BFE90000        BFEA0000        BFEB0000        BFEC0000     
  BFED0000        BFEE0000        BFEF0000        BFF00000        BFF10000     
  BFF20000        BFF30000        BFF40000        BFF50000        BFF60000 E   
  BFF70000 E      BFF80000 E      BFF90000        BFFA0000        BFFB0000     
  BFFC0000        BFFD0000 E      BFFE0000 E      BFFF0000 E      BFFF2000 E   
  BFFF4000 E      BFFF6000 E      BFFF8000 E      BFFFA000 E      BFFFC000 E   
  BFFFE000 E                                                                   
HD-HLAN# erase bfc40000 bff5ffff                                               

.................................................. done
Erased 50 sectors                                     
HD-HLAN# md bffb0000                                   
bffb0000: 04340000 00000000 00000000 00000000    ..4.............
bffb0010: 746f6f62 6d726170 6f6f723d 642f3d74    bootparm=root=/d
bffb0020: 682f7665 00316164 00000000 00000000    ev/hda1.........
bffb0030: 67616c66 2057463d 61647075 00006574    flag=FW update..
bffb0040: 00000000 00000000 00000000 00000000    ................
bffb0050: ffffffff ffffffff ffffffff ffffffff    ................
bffb0060: ffffffff ffffffff ffffffff ffffffff    ................
bffb0070: ffffffff ffffffff ffffffff ffffffff    ................
bffb0080: ffffffff ffffffff ffffffff ffffffff    ................
bffb0090: ffffffff ffffffff ffffffff ffffffff    ................
bffb00a0: ffffffff ffffffff ffffffff ffffffff    ................
bffb00b0: ffffffff ffffffff ffffffff ffffffff    ................
bffb00c0: ffffffff ffffffff ffffffff ffffffff    ................
bffb00d0: ffffffff ffffffff ffffffff ffffffff    ................
bffb00e0: ffffffff ffffffff ffffffff ffffffff    ................
bffb00f0: ffffffff ffffffff ffffffff ffffffff    ................
HD-HLAN# md bffc0000                                             
bffc0000: 46465542 204f4c41 665f736c 6873616c    BUFFALO ls_flash
bffc0010: 726f6620 0074616d 00000000 00000100     format.........
bffc0020: 0000002c 000023e2 00000000 706d742f    ,....#....../tmp
bffc0030: 6e6f632f 61735f66 742e6576 672e7261    /conf_save.tar.g
bffc0040: 0000007a 00000000 00000000 08088b1f    z...............
bffc0050: 3c7c3702 6f630300 735f666e 2e657661    .7|<..conf_save.
bffc0060: 00726174 8fcb5dec ff524933 c58b8196    tar..]..3IR.....
bffc0070: 84803961 ee9c87b4 99ea561d 68fcbb76    a9.......V..v..h
bffc0080: 0b52dd7f 8ef6ecfc fdcb851f be5d9998    ..R...........].
bffc0090: b6955d2f 9b5eba6b 7f6dd555 cee0272c    /]..k.^.U.m.,'..
bffc00a0: 009fed0d 1c6e2407 01ed2039 909c480e    .....$n.9 ...H..
bffc00b0: 4e05ec38 06e2109c b2ab3222 8fcb976c    8..N...."2..l...
bffc00c0: bcf7719e b3fa662a 17eaa33b 8c888f91    .q..*f..;.......
bffc00d0: 26aacc8c 11627a9e f7a6d1ef 11e5ba27    ...&.zb.....'...
bffc00e0: 712ac23a 7295ed5f 5a772e52 05cabe2c    :.*q_..rR.wZ,...
bffc00f0: 49ccff14 292bd2f9 a74a9d27 cd3a4965    ...I..+)'.J.eI:.
HD-HLAN# erase bffb0000 bffc0000                                 
Error: end address not on sector boundary                       
HD-HLAN# erase bffb0000 bffcffff                                 

.. done
Erased 2 sectors
HD-HLAN# fl     

Bank # 1: CFI conformant FLASH (8 x 16)  Size: 4 MB in 71 Sectors
  AMD Standard command set, Manufacturer ID: 0xC2, Device ID: 0xA7A7
  Erase timeout: 16384 ms, write timeout: 1 ms                     

  Sector Start Addresses:
  BFC00000   RO   BFC10000   RO   BFC20000   RO   BFC30000   RO   BFC40000 E   
  BFC50000 E      BFC60000 E      BFC70000 E      BFC80000 E      BFC90000 E   
  BFCA0000 E      BFCB0000 E      BFCC0000 E      BFCD0000 E      BFCE0000 E   
  BFCF0000 E      BFD00000 E      BFD10000 E      BFD20000 E      BFD30000 E   
  BFD40000 E      BFD50000 E      BFD60000 E      BFD70000 E      BFD80000 E   
  BFD90000 E      BFDA0000 E      BFDB0000 E      BFDC0000 E      BFDD0000 E   
  BFDE0000 E      BFDF0000 E      BFE00000 E      BFE10000 E      BFE20000 E   
  BFE30000 E      BFE40000 E      BFE50000 E      BFE60000 E      BFE70000 E   
  BFE80000 E      BFE90000 E      BFEA0000 E      BFEB0000 E      BFEC0000 E   
  BFED0000 E      BFEE0000 E      BFEF0000 E      BFF00000 E      BFF10000 E   
  BFF20000 E      BFF30000 E      BFF40000 E      BFF50000 E      BFF60000 E   
  BFF70000 E      BFF80000 E      BFF90000        BFFA0000        BFFB0000 E   
  BFFC0000 E      BFFD0000 E      BFFE0000 E      BFFF0000 E      BFFF2000 E   
  BFFF4000 E      BFFF6000 E      BFFF8000 E      BFFFA000 E      BFFFC000 E   
  BFFFE000 E                                                                   
HD-HLAN# tftp 81000000 192.168.1.100:vmlinux-2.6.30.4.uboot                     
Using rc32434-eth device
TFTP from server 192.168.1.100; our IP address is 192.168.1.200
Filename 'vmlinux-2.6.30.4.uboot'.
Load address: 0x81000000
Loading: #################################################################
         ##########################################################
done
Bytes transferred = 1798122 (1b6fea hex)
HD-HLAN# cp.b 81000000 bfd00000 1b6fea
Copy to Flash... 9....8....7....6....5....4....3....2....1....done
HD-HLAN# cmp.b 81000000 bfd00000 1b6fea
Total of 1798122 bytes were the same
HD-HLAN# fl

Bank # 1: CFI conformant FLASH (8 x 16)  Size: 4 MB in 71 Sectors
  AMD Standard command set, Manufacturer ID: 0xC2, Device ID: 0xA7A7
  Erase timeout: 16384 ms, write timeout: 1 ms

  Sector Start Addresses:
  BFC00000   RO   BFC10000   RO   BFC20000   RO   BFC30000   RO   BFC40000 E
  BFC50000 E      BFC60000 E      BFC70000 E      BFC80000 E      BFC90000 E
  BFCA0000 E      BFCB0000 E      BFCC0000 E      BFCD0000 E      BFCE0000 E
  BFCF0000 E      BFD00000        BFD10000        BFD20000        BFD30000
  BFD40000        BFD50000        BFD60000        BFD70000        BFD80000
  BFD90000        BFDA0000        BFDB0000        BFDC0000        BFDD0000
  BFDE0000        BFDF0000        BFE00000        BFE10000        BFE20000
  BFE30000        BFE40000        BFE50000        BFE60000        BFE70000
  BFE80000        BFE90000        BFEA0000        BFEB0000        BFEC0000 E
  BFED0000 E      BFEE0000 E      BFEF0000 E      BFF00000 E      BFF10000 E
  BFF20000 E      BFF30000 E      BFF40000 E      BFF50000 E      BFF60000 E
  BFF70000 E      BFF80000 E      BFF90000        BFFA0000        BFFB0000 E
  BFFC0000 E      BFFD0000 E      BFFE0000 E      BFFF0000 E      BFFF2000 E
  BFFF4000 E      BFFF6000 E      BFFF8000 E      BFFFA000 E      BFFFC000 E
  BFFFE000 E
HD-HLAN#


mindbender,
Yes, if I have time to work it out with the rb532 guys. However, this is not my first priority as my time is very scares nowadays. I can hardly sit in front of my computer for an hour at home with our interruption from my 3 year old daughter and 5 month old son. They are my most demanding boss ever. :-)
I notice rb532 support in the mainline when I started porting, and it seems to be based on the IDT linux code. However, there are compilation issues when I first tried to see how far it got. I started from scratch partly because of that, but also I want a better design where platform specific code is completely separated in its own directory from the SoC common code which should be more generic and easily extensible. For example, the interrupt handling in the SoC common code should be able to handle any interrupt, including GPIO interrupt, configurations a platform decides, especially the PCI interrupt lines remapping per bus/device or whatsoever as the paltform sees fit.


Last edited by shihsung on Fri Aug 07, 2009 5:52 am, edited 1 time in total.

Top
   
PostPosted: Wed Aug 05, 2009 8:54 am 
Offline
Newbie

Joined: Sun Aug 05, 2007 4:15 am
Posts: 36
davy_gravy,
Ah, the timeout problem. I remember now. I did see the problem before. It's the tick skew problem. I don't think it's STM flash specific though. In fact, I had fixed it even in my old U-Boot 1.2.0. Hopefully someone else can verify whether it's fixed with my U-Boot.


Top
   
PostPosted: Wed Aug 05, 2009 5:09 pm 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
thanks, shisung

I'm trying out the kernel compiled after applying your patch, and widening the defconfig you included (webcam drivers, ext4 & a few more fs things, etc.)

seems to work very nicely.

Bauldrick: Oops (a minor but nagging omission) - my oversight. I forgot to include turn on CONFIG_LBD, so ext4 will have to wait until I get a bit of time to recompile:
Code:
EXT4-fs: sda4: Filesystem with huge files cannot be mounted read-write without CONFIG_LBD.

_________________
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 Aug 06, 2009 12:48 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
EDITTED

odd...

my 2.6.30.4 + Sarge tmpimage = bootable
my 2.6.30.4 + Lenny (from debootstrap) = hangs when booting
my (old) 2.6.23.17 + Lenny (from debootstrap) = bootable

shisung, you were right ... sda1 instead of the ram disk is what I mean to use

I'm guessing that maybe something in my debootstrapped image was not correctly configured (though I'm sure it is not the fstab or network/interfaces that is the problem).

I haven't gone through your entire sequence of instructions, will try that later.

_________________
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 Aug 06, 2009 5:48 am 
Offline
Newbie

Joined: Sun Aug 05, 2007 4:15 am
Posts: 36
Nope! This looks like davy_gravy problem! :-) You ask the kernel to use ramdisk, /dev/ram0, as root fs, but you didn't supply one. BTW, I think you have 3 instances of ncb running thus getting the same output 3 times.


Top
   
PostPosted: Fri Aug 07, 2009 12:53 am 
Offline
Betatester
User avatar

Joined: Thu Jul 14, 2005 4:38 pm
Posts: 941
Location: England
Hi shihsung

I have a small problem with network behaviour on 2.6.30.4 (davygravy's build) yours seems to load but doesn't bring system up :? ))

Basically (I think) ksoftirqd is killing the network connection when too much traffic is passing through ethernet, but I'm not that technically minded so bare with me :)

In kern.log I see lots of BUG: scheduling while atomic: transmission-da/437/0x00000100 and BUG: scheduling while atomic: ksoftirqd...
I don't know what that is about, but google told me something like BUG: scheduling while atomic typically means that the function schedule() is called while interrupts are disabled (typically with spin_lock_irqsave and friends) and to look in /proc/interrupts, so:

Code:
          CPU0
  2:          0            MIPS  RC32434 IRQ cascade
  3:          0            MIPS  RC32434 IRQ cascade
  4:          0            MIPS  RC32434 IRQ cascade
  5:          0            MIPS  RC32434 IRQ cascade
  6:          0            MIPS  RC32434 IRQ cascade
  7:      85969            MIPS  timer
 40:      14027  RC32434 IRQ chip  eth rx irq
 41:      62094  RC32434 IRQ chip  eth tx irq
104:        236  RC32434 IRQ chip  serial
109:         18  RC32434 IRQ chip  SPI IRQ
113:          0  RC32434 IRQ chip  eth ovr irq
114:          0  RC32434 IRQ chip  eth und irq
115:          0  RC32434 IRQ chip  eth fc irq
146:       6565  RC32434 IRQ chip  pata_it821x
148:          0  RC32434 IRQ chip  ehci_hcd:usb1, ohci_hcd:usb2, ohci_hcd:usb3

ERR:          0


Don't even know if that's important, thought I'd document it.

I tried to tftp your uboot ram, but didn't get very far. tftp'd it over but it didn't seem to load. I'll post some output tomorrow, when I'm not so tired ..


Top
   
PostPosted: Fri Aug 07, 2009 6:20 am 
Offline
Newbie

Joined: Sun Aug 05, 2007 4:15 am
Posts: 36
Hi Bauldrick,

When you have time, please provide more info, such as what network services you were running and how to reproduce the problem.

My kernel image uses the new ATA driver instead of the old IDE driver, thus you need to change all /dev/hd?? to /dev/sd?? in your /etc/fstab. But, try the ramdisk first with

set serverip 192.168.1.100
tftp 81000000 vmlinux-2.6.30.4.uboot
tftp 807fffc0 initrd-busybox-1.14.2.uboot
set bootargs root=/dev/ram0 ip=192.168.1.200
bootm 81000000 807fffc0

telnet 192.168.1.200

Note: Old U-Boot can only tftp from ONE server specified by "serverip". It doesn't support "tftp 81000000 192.168.1.100:vmlinux-2.6.30.4.uboot" syntax.


Top
   
PostPosted: Fri Aug 07, 2009 8:45 am 
Offline
Site Admin
User avatar

Joined: Mon Aug 28, 2006 1:15 am
Posts: 2606
hi shihsung, great job, this is awesome to see... here is some feedback/info for you.

I've been running it for more than a day now, and works mostly as expected. Here are the only things I've seen to comment on:

1. I can confirm some sort of network lockup as well. The readings below are from while I'm trying to copy a file over via samba. I also see this lockup when I cat a large file when logged into the box. (for reference, my LS2 is running Lenny w/ a kernel compiled using your patch and a widened version of the config you gave.

Code:
Tasks:  55 total,   2 running,  53 sleeping,   0 stopped,   0 zombie
Cpu(s):  1.5%us,  1.2%sy,  0.0%ni,  0.0%id,  0.0%wa,  0.0%hi, 97.2%si,  0.0%st
Mem:     60364k total,    59044k used,     1320k free,     2056k buffers



    3 root      15  -5     0    0    0 R 98.0  0.0   1:17.51 ksoftirqd/0                                                                       
  803 root      20   0  3116 1240 1032 R  1.9  2.1   0:01.02 top                                                                               
  792 root      20   0 10112  952  528 S  0.3  1.6   0:00.55 sshd                                                                               
    1 root      20   0  2484  204  100 S  0.0  0.3   0:00.23 init                                                                               
    2 root      15  -5     0    0    0 S  0.0  0.0   0:00.00 kthreadd                                                                           
    4 root      15  -5     0    0    0 S  0.0  0.0   0:00.01 events/0                                                                           
    5 root      15  -5     0    0    0 S  0.0  0.0   0:00.00 khelper                                                                           
    6 root      15  -5     0    0    0 S  0.0  0.0   0:00.00 async/mgr                                                                         
    7 root      15  -5     0    0    0 S  0.0  0.0   0:00.04 kblockd/0                                                                         
    8 root      15  -5     0    0    0 S  0.0  0.0   0:00.00 ata/0                                                                             
    9 root      15  -5     0    0    0 S  0.0  0.0   0:00.00 ata_aux                                                                           
   10 root      15  -5     0    0    0 S  0.0  0.0   0:00.00 khubd                                                                             
   11 root      20   0     0    0    0 S  0.0  0.0   0:00.00 pdflush                                                                           
   12 root      20   0     0    0    0 S  0.0  0.0   0:00.95 pdflush                                                                           
   13 root      15  -5     0    0    0 S  0.0  0.0   0:00.50 kswapd0                                                                           
   14 root      15  -5     0    0    0 S  0.0  0.0   0:00.00 aio/0                                                                             
   15 root      15  -5     0    0    0 S  0.0  0.0   0:00.00 nfsiod                                                                             
   16 root      15  -5     0    0    0 S  0.0  0.0   0:00.00 cifsoplockd                                                                       
   17 root      15  -5     0    0    0 S  0.0  0.0   0:00.01 scsi_eh_0                                                                         
   18 root      15  -5     0    0    0 S  0.0  0.0   0:00.00 scsi_eh_1                                                                         
   19 root      15  -5   


**Note that the box does not crash, as I'm still able to shut it down gracefully using the power switch (avr-evtd seems to be working properly in that respect. It just seems like the networking process are interrupted/overwhelmed by something.

**Also, it does not seem to affect all networking traffic in an equal way. For instance, I can download (wget http:) a 100MB file from the wiki downloads with no problem at all.


** I can find __nothing__ suspicious in the logs. No errors that I've seen. ( check dmesg*, kern.log, messages)

2. I wasn't sure where to add in the line about the avr-evtd daemon option, in your "Convert to Lenny" page/directions:
Quote:
vi /etc/defaults/avr-evtd
DEBUG=OFF
vi /etc/init.d/avr-evtd
daemonoptions="-d /dev/ttyS0"
NOTE: Add the above line right before launching the daemon.


I'm guessing you mean at line 69...

Code:
start()
{
    #
    # Daemon options
    # e.g -d /dev/ttyS1
    #
    daemonoptions="-d /dev/ttyS0"       

    CONSOLE=OFF

    getDevice


3. The hardware clock is not working for us. Here is some info below. The rtc node that is in /dev (listed in the 3rd block of output below) is the original statically created node from the 2.4-ish firmware/OS - I simply moved it out of the way hoping the new node(s) would be created, but they aren't.

Code:
root@lsmipsel:~# dmesg | grep rtc
rtc-rs5c348 spi0.2: chip found, driver version 0.2
rtc-rs5c348 spi0.2: spiclk 1000 KHz.
rtc-rs5c348 spi0.2: rtc core: registered rtc-rs5c348 as rtc0
rtc-rs5c348 spi0.2: retrieved date/time is not valid.
rtc-rs5c348 spi0.2: setting system clock to 1970-01-01 00:00:00 UTC (0)


root@lsmipsel:~# hwclock --debug
hwclock from util-linux-ng 2.13.1.1
hwclock: Open of /dev/rtc failed, errno=2: No such file or directory.
No usable clock interface found.
Cannot access the Hardware Clock via any known method.


root@lsmipsel:~# ls -lna /dev/rtc*
crw-rw---- 1 0 0 10, 135 Mar  2  2005 /dev/rtc
root@lsmipsel:~#

Aug  7 17:59:15 lsmipsel kernel: udevd version 125 started
Aug  7 17:59:15 lsmipsel exiting on signal 15
Aug  7 17:59:15 lsmipsel syslogd 1.5.0#5: restart.
Aug  7 17:59:55 lsmipsel shutdown[1153]: shutting down for system reboot
Aug  7 17:59:55 lsmipsel init: Switching to runlevel: 6
Aug  7 17:59:59 lsmipsel rpc.statd[294]: Caught signal 15, un-registering and exiting.
Aug  7 18:00:00 lsmipsel kernel: rtc-rs5c348 spi0.2: retrieved date/time is not valid.
Aug  7 18:00:31 lsmipsel last message repeated 10806 times



If I add in udev for dynamic creation of the node(s), the box will no longer boot.

100. (Not a bug, just info) Just FYI, uboot-envtools is in Debian, and the fw_printenv & fw_saveenv seem to work as expected. The example config in examples in the package docs is wrong though. (I submitted a bug report to Debian for this package).

It should read:
Code:
# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundant
# environment sector is assumed present.

# MTD device name   Device offset   Env. size   Flash sector size
/dev/mtd0           0x30000         0x10000     0x10000

I'm assuming that there is nothing in this kernel or your new uboot that would change the layout, right?



again, nice work :)

davy

====================
motd/login-welcome for the lenny lsmipsel tarball I'm creating...
Image

_________________
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  [ 120 posts ]  Go to page 1 2 3 4 58 Next

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 2 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