Welcome! Log In Create A New Profile

Advanced

Linux Kernel 5.13.6 Kirkwood package and Debian rootfs

Posted by bodhi 
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 27, 2015 12:03PM
When I want to follow step 4 in the instructions:
Quote
Updated 24 Feb 2015:
This rootfs is the first Debian jessie rootfs in my Kirkwood kernel/rootfs release series, and to keep in sync with kernel Linux-3.18.5-kirkwood-tld-1.


I get an error when creating the uImage.

All the information I can give you is the following:
- ZyXEL NSA325v2 with latest uBoot 2014.7-tld-4 flashed on NAND
- The following printenv
arcNumber=4495
baudrate=115200
bootcmd=run bootcmd_uenv; run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=3
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=b6:d0:5e:0f:a1:17
if_netconsole=ping $serverip
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtddevname=rootfs
mtddevnum=2
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
rootdelay=5
rootfstype=ext4
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext4load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext4load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.0.220
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_import=echo importing envs ...; env import -t 0x810000
uenv_load=usb start; mmc rescan; ide reset; setenv uenv_loaded 0; for devtype in usb mmc ide; do for disknum in 0; do run uenv_read_disk; done; done
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x810000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1

Environment size: 2844/131068 bytes
- uname -a from my linux virtualmachine which I use (Latest and up to date Debian XFCE edition)
Linux debian 3.16.0-4-586 #1 Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) i686 GNU/Linux
- mkimage version (after install via apt-get install u-boot-tools, before that the command wasn't recognized)
mkimage version 2014.10+dfsg1-5
- list of boot directory in rootfs before performing all the steps in 4
totaal 32516
-rwxrwx--- 1 root vboxsf  131204 feb  6  2015 config-3.18.5-kirkwood-tld-1
drwxrwx--- 1 root vboxsf    2414 feb  6  2015 dts
-rwxrwx--- 1 root vboxsf 6535220 feb 19  2015 initrd.img-3.18.5-kirkwood-tld-1
-rwxrwx--- 1 root vboxsf 9460784 feb  6  2015 linux-headers-3.18.5-kirkwood-tld-1_1_armel.deb
-rwxrwx--- 1 root vboxsf 2019506 feb  6  2015 System.map-3.18.5-kirkwood-tld-1
-rwxrwx--- 1 root vboxsf 2865664 feb  8  2015 uImage
-rwxrwx--- 1 root vboxsf 6535284 feb 19  2015 uInitrd
-rwxrwx--- 1 root vboxsf 2865600 feb  6  2015 vmlinuz-3.18.5-kirkwood-tld-1
-rwxrwx--- 1 root vboxsf 2865600 feb  6  2015 zImage-3.18.5-kirkwood-tld-1
- executed steps in 4
root@debian:/Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi/boot# cp -a zImage-3.18.5-kirkwood-tld-1  zImage.fdt
root@debian:/Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi/boot# cat dts/kirkwood-nsa325.dtb  >> zImage.fdt
root@debian:/Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi/boot# mv uImage uImage.orig
root@debian:/Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi/boot# mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.18.5-kirkwood-tld-1 -d zImage.fdt uImage
mkimage: Can't map uImage: Invalid argument
root@debian:/Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi/boot# sync
- list of boot directory in rootfs after performing all the steps in 4
totaal 38148
-rwxrwx--- 1 root vboxsf  131204 feb  6  2015 config-3.18.5-kirkwood-tld-1
drwxrwx--- 1 root vboxsf    2414 feb  6  2015 dts
-rwxrwx--- 1 root vboxsf 6535220 feb 19  2015 initrd.img-3.18.5-kirkwood-tld-1
-rwxrwx--- 1 root vboxsf 9460784 feb  6  2015 linux-headers-3.18.5-kirkwood-tld-1_1_armel.deb
-rwxrwx--- 1 root vboxsf 2019506 feb  6  2015 System.map-3.18.5-kirkwood-tld-1
-rwxrwx--- 1 root vboxsf 2879926 aug 28 07:01 uImage
-rwxrwx--- 1 root vboxsf 2865664 feb  8  2015 uImage.orig
-rwxrwx--- 1 root vboxsf 6535284 feb 19  2015 uInitrd
-rwxrwx--- 1 root vboxsf 2865600 feb  6  2015 vmlinuz-3.18.5-kirkwood-tld-1
-rwxrwx--- 1 root vboxsf 2865600 feb  6  2015 zImage-3.18.5-kirkwood-tld-1
-rwxrwx--- 1 root vboxsf 2879862 aug 28 07:01 zImage.fdt

Can someone look into this, why I get this error?

When I look the new uImage is created even if it gives an error about an invalid argument, I tried booting with the created uImage.
But it gives following error when seeing with serial:
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!
resetting ...

----
Friendly regards


Ziggy



Edited 2 time(s). Last edit at 08/28/2015 12:14AM by ziggy.
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 27, 2015 04:21PM
ziggy Wrote:
-------------------------------------------------------
> When I want to follow step 4 in the instructions:
>
Quote
Updated 24 Feb 2015:
> This rootfs is the first Debian jessie rootfs in
> my Kirkwood kernel/rootfs release series, and to
> keep in sync with kernel
> Linux-3.18.5-kirkwood-tld-1.

>
> I get an error when creating the uImage
>
> root@debian:/Debian-3.18.5-kirkwood-tld-1-rootfs-b
> odhi/boot# mkimage -A arm -O linux -T kernel -C
> none -a 0x00008000 -e 0x00008000 -n
> Linux-3.18.5-kirkwood-tld-1 -d zImage.fdt uImage
> mkimage: Can't map uImage: Invalid argument
>
>
> Can someone look into this, why I get this error?
> When I look the new uImage is created, can I know
> safely try to boot my NSA325v2 with this new
> uImage created?
>
> I tried and uImage isn't correct I get this error
> when seeing with serial:
>
> Wrong Image Format for bootm commeand
> Error occured, error code = 112
> ERROR: can't get kernel image!
> resetting ...
>

Ziggy,

We need more info.

On the Linux box that you use to create the rootfs:

uname -a
which mkimage


And then repeat this step 4, post everything you have in performing this step.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 28, 2015 12:16AM
Sorry about the little information I gave, I updated my previous post to be more complete.
If something is still missing, please let me know and I'll update it.

Thanks in advance for taking a look into this.

----
Friendly regards


Ziggy
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 28, 2015 01:35AM
@ziggy,

Your execution of the steps are all correct, I did not see any thing wrong. So that points to the mkimage command, which might be not working correctly in that Debian 3.16.0-4-586 system.

To make matter simpler, instead of using the 3.18.5 rootfs, use the Debian-3.16.0-kirkwood-tld-2 rootfs, as I recommended in this post:

http://forum.doozan.com/read.php?4,23425,23427#msg-23427

After you've successfully booted into this 3.16 rootfs, you can then upgrade to kernel 4.1 directly.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 28, 2015 10:44AM
Guys, I just set second hard drive in my NSA325v2 and i see that it perform bad during file copy.
When i do copy from one internal drive to another (large files).
Total DISK READ :      47.21 M/s | Total DISK WRITE :      47.26 M/s
Actual DISK READ:      46.84 M/s | Actual DISK WRITE:      55.85 M/s
Cpu on 100% constantly, Im on latest uBoot and kernel.

Is this normal behaviuor?
Thanks.



Edited 1 time(s). Last edit at 08/28/2015 10:46AM by andsol.
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 28, 2015 01:41PM
andsol Wrote:
-------------------------------------------------------

> Cpu on 100% constantly
> Is this normal behaviuor?

I don't have a 2nd disk handy, but just tried from disk to same disk, large file and cpu is at 70% (25MB/sec)
So I guess it's normal.

--
DavideDG
My NAS userspace configs
My Zyxel NSA325 mod
My D-Link DNS325 mod
My Lacie NS2MAX mod
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 28, 2015 01:59PM
davidedg Wrote:
-------------------------------------------------------
> andsol Wrote:
> --------------------------------------------------
> -----
>
> > Cpu on 100% constantly
> > Is this normal behaviuor?
>
> I don't have a 2nd disk handy, but just tried from
> disk to same disk, large file and cpu is at 70%
> (25MB/sec)
> So I guess it's normal.


Hmm, so it looks like file copying speed stuck on cpu, file copy operation it's just a command from where to take and where to put. As I remember I had 75 mb/s on stock firmware without cpu load.
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 28, 2015 02:20PM
andsol Wrote:
-------------------------------------------------------

> Hmm, so it looks like file copying speed stuck on
> cpu, file copy operation it's just a command from
> where to take and where to put. As I remember I
> had 75 mb/s on stock firmware without cpu load.

Did some tests with dd and I confirm it stucks on 100% (mostly kernel time in htop).
Seems related to DMA not activated - makes me wonder if it's available on this platform?

--
DavideDG
My NAS userspace configs
My Zyxel NSA325 mod
My D-Link DNS325 mod
My Lacie NS2MAX mod
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 28, 2015 03:30PM
bodhi Wrote:
-------------------------------------------------------
> @ziggy,
>
> Your execution of the steps are all correct, I did
> not see any thing wrong. So that points to the
> mkimage command, which might be not working
> correctly in that Debian 3.16.0-4-586 system.
>
> To make matter simpler, instead of using the
> 3.18.5 rootfs, use the
> Debian-3.16.0-kirkwood-tld-2 rootfs, as I
> recommended in this post:
>
> http://forum.doozan.com/read.php?4,23425,23427#msg
> -23427
>
> After you've successfully booted into this 3.16
> rootfs, you can then upgrade to kernel 4.1
> directly.

I'm getting further with booting rootfs, but now my NSA325v2 doesn't seem to receive an IP address nor is it detected on the network.
Therefore I can't ssh into NSA325v2 for updating/upgrading the debian rootfs.

See attached log from serial and even there I don't get a prompt...

Is there something I oversee, I followed the steps like stated in the installation instructions for the Debian-3.16.0-kirkwood-tld-2 rootfs.

----
Friendly regards


Ziggy
Attachments:
open | download - CoolTerm Capture 2015-08-28 22-21-12.txt (25.1 KB)
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 28, 2015 04:00PM
> stucks on 100% (mostly kernel time in htop).
> Seems related to DMA not activated - makes me
> wonder if it's available on this platform?

Interesting. I'll hook up a second HDD and see if I can find out why.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 29, 2015 12:49AM
Hi Bodhi

Ah ok, no problem!
I'm happy enough that you can help me with this in your spare time.

Unfortunately I don't have another ARM box around.
I'm now preparing a Wheezy virtual machine to try creating the uImage.

But if this fails, can somebody be so kindly to already create the uImage for me and upload it?

----
Friendly regards


Ziggy



Edited 3 time(s). Last edit at 08/29/2015 01:54AM by ziggy.
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 29, 2015 01:45PM
I've moved ziggy's booting problem to a new thread below:
http://forum.doozan.com/read.php?2,23536

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 08/29/2015 02:14PM by bodhi.
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 29, 2015 02:06PM
@bodhi, did you had a chance to check file copy perfomance issue?
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 29, 2015 02:12PM
andsol Wrote:
-------------------------------------------------------
> @bodhi, did you had a chance to check file copy
> perfomance issue?

Not yet! I will when I have a chance to install another HDD on it.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 29, 2015 11:13PM
I've uploaded a new test kernel for Zyxel NSA 310 and 320:
http://forum.doozan.com/read.php?2,23555

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 30, 2015 01:11AM
bodhi Wrote:
-------------------------------------------------------

> Not yet! I will when I have a chance to install
> another HDD on it.

Oh, but it happens also on single hdd.
If you do a
dd if=/dev/sda of=/dev/null

CPU goes at 100%, mostly kernel times.
I don't know if this is expected, though. - I should try on a Jessie VM.
-- just tried on a single-core VM: same behaviour.
Is it a real problem ?

--
DavideDG
My NAS userspace configs
My Zyxel NSA325 mod
My D-Link DNS325 mod
My Lacie NS2MAX mod



Edited 1 time(s). Last edit at 08/30/2015 01:20AM by davidedg.
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 30, 2015 01:35AM
I've tried this:
# cat /sys/block/sda/queue/scheduler
noop deadline [cfq]
# echo deadline > /sys/block/sda/queue/scheduler
# cat /sys/block/sda/queue/scheduler
noop [deadline] cfq
Slighly better instead of 100% its shows me 85-90%.

Here is my tests:
root@nas:~# hdparm -Tt /dev/sda

/dev/sda:
 Timing cached reads:   556 MB in  2.00 seconds = 277.38 MB/sec
 Timing buffered disk reads: 262 MB in  3.02 seconds =  86.65 MB/sec

root@nas:~# hdparm -Tt /dev/sdb

/dev/sdb:
 Timing cached reads:   622 MB in  2.00 seconds = 310.43 MB/sec
 Timing buffered disk reads: 428 MB in  3.01 seconds = 142.40 MB/sec

Realtime I should get mutch higher results, not:
Total DISK READ :      47.21 M/s | Total DISK WRITE :      47.26 M/s
Actual DISK READ:      46.84 M/s | Actual DISK WRITE:      55.85 M/s

And strange, when I do this:
time sh -c "dd if=/dev/zero of=testfile bs=100k count=1k && sync"
1024+0 records in
1024+0 records out
104857600 bytes (105 MB) copied, 1.09346 s, 95.9 MB/s

Processor goes up to 50%, and results are better on small data.



Edited 2 time(s). Last edit at 08/30/2015 01:58AM by andsol.
Re: Linux Kernel 4.1 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
August 30, 2015 03:54AM
Davide,

> CPU goes at 100%, mostly kernel times.
> Is it a real problem ?

It is not a real problem. If the dd command is the only thing running, we do want it to take most of the CPU :) OTOH, if something else is running actively, then dd should not take that much CPU.

The disk read/write speed is that I meant above, that I want to take a look when I have time.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 08/30/2015 03:55AM by bodhi.
Re: Linux Kernel 4.2 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
September 05, 2015 03:36AM
Kernel linux-4.2.0-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.2 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
September 08, 2015 04:32AM
I have Jeff's old 2.16 kernel running on my Dockstar. Can I directly install the 4.2 kernel directly? My system is booting from a USB HDD. I installed the system 4 yrs back and then did not create separate partitionb for root and data download :(.
Shall I make a separate parttition before I proceed (will there be any data loss?)
Sorry for noob quesions.
Re: Linux Kernel 4.2 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
September 08, 2015 12:17PM
Is there any change to get working debian jessie on NSA310? I've tested the Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2 with dtb/kirkwood-nsa310.dtb but without success :(

here is my boot log
http://pastebin.com/xZ62YkQe
Re: Linux Kernel 4.2 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
September 08, 2015 12:17PM
archat68,

> I have Jeff's old 2.16 kernel running on my
> Dockstar. Can I directly install the 4.2 kernel
> directly? My system is booting from a USB HDD. I
> installed the system 4 yrs back and then did not
> create separate partitionb for root and data
> download :(.
> Shall I make a separate parttition before I
> proceed (will there be any data loss?)
> Sorry for noob quesions.

You need to make a backup of your current HDD, as the first and most important step!

Yes, you can ugrade the kernel to the last non-FDT kernel (3.16) and then go from there to newer version. It's the safest route for someone who is less experience.

1. Backup

2. Perform the same steps as described here:
http://forum.doozan.com/read.php?4,23425,23427#msg-23427

Be aware that upgrade like this will result in a massive change in your system, it will take a while to run it, there is a small chance that something might go wrong. So a good backup of your current HDD is a must.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.2 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
September 08, 2015 01:11PM
sodd,

> Is there any change to get working debian jessie
> on NSA310? I've tested the
> Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2
> with dtb/kirkwood-nsa310.dtb but without success
> :(
>
> here is my boot log
> http://pastebin.com/xZ62YkQe

Your u-boot envs do not seem to set up to boot Debian correctly (it did not load the uInitrd).

Interrupt serial console, list the envs, and post the output here.
printenv

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.2 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
September 08, 2015 01:16PM
it's mess i know... but it works for 3.6.9 kernel

bootdelay=2
baudrate=115200
loads_echo=0
eth1addr=00:19:CB:00:51:82
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
nandEcc=1bit
MODEL_ID=A203
PRODUCT_NAME=NSA-310
FEATURE_BIT=00
CONTRY_TYPE=FF
VENDOR_NAME=ZyXEL Communications Corp.
run_diag=yes
ethaddr=CC:5D:4E:CA:01:39
console=100000
=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root)
CASset=min
ethprime=egiga1
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethmtu=1500
eth1mtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
arcNumber=4022
MALLOC_len=3
usb_set_arg==ahoj
stdin=serial
stdout=serial
stderr=serial
nandEnvBase=100000
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
disaMvPnp=no
hddPowerCtrl=no
enaAutoRecovery=yes
kernel_addr=0x4640000
pcieTune=no
ethact=egiga1
bootcmd=usb start; ext2load usb 0:1 0x8000000 /uImage; bootm 0x8000000
serverip=10.0.0.164
ipaddr=10.0.0.130
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
bootargs=console=ttyS0,115200 root=/dev/sdb2 rootdelay=20 debug
Re: Linux Kernel 4.2 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
September 08, 2015 02:28PM
sodd Wrote:
-------------------------------------------------------
> it's mess i know... but it works for 3.6.9 kernel
>
>
> bootdelay=2
> baudrate=115200
> loads_echo=0
> eth1addr=00:19:CB:00:51:82
> rootpath=/mnt/ARM_FS/
> netmask=255.255.255.0
> nandEcc=1bit
> MODEL_ID=A203
> PRODUCT_NAME=NSA-310
> FEATURE_BIT=00
> CONTRY_TYPE=FF
> VENDOR_NAME=ZyXEL Communications Corp.
> run_diag=yes
> ethaddr=CC:5D:4E:CA:01:39
> console=100000
> =ttyS0,115200
> mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x1
> 00000(root)
> CASset=min
> ethprime=egiga1
> bootargs_root=root=/dev/nfs rw
> bootargs_end=:::DB88FXX81:eth0:none
> image_name=uImage
> standalone=fsload 0x2000000 $(image_name);setenv
> bootargs $(console) root=/dev/mtdblock0 rw
> ip=$(ipaddr):$(serverip)$(bootargs_end)
> $(mvPhoneConfig); bootm 0x2000000;
> ethmtu=1500
> eth1mtu=1500
> mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
> mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2
> :3),mtu=1500
> usb0Mode=host
> yuk_ethaddr=00:00:00:EE:51:81
> netretry=no
> rcvrip=169.254.100.100
> loadaddr=0x02000000
> autoload=no
> arcNumber=4022
> MALLOC_len=3
> usb_set_arg==ahoj
> stdin=serial
> stdout=serial
> stderr=serial
> nandEnvBase=100000
> mainlineLinux=yes
> enaMonExt=no
> enaCpuStream=no
> enaWrAllo=no
> pexMode=RC
> disL2Cache=no
> setL2CacheWT=yes
> disL2Prefetch=yes
> enaICPref=yes
> enaDCPref=yes
> sata_dma_mode=yes
> netbsd_en=no
> vxworks_en=no
> disaMvPnp=no
> hddPowerCtrl=no
> enaAutoRecovery=yes
> kernel_addr=0x4640000
> pcieTune=no
> ethact=egiga1
> bootcmd=usb start; ext2load usb 0:1 0x8000000
> /uImage; bootm 0x8000000
> serverip=10.0.0.164
> ipaddr=10.0.0.130
> if_netconsole=ping $serverip
> start_netconsole=setenv ncip $serverip; setenv
> bootdelay 10; setenv stdin nc; setenv stdout nc;
> setenv stderr nc; version;
> preboot=run if_netconsole start_netconsole
> bootargs=console=ttyS0,115200 root=/dev/sdb2
> rootdelay=20 debug
>

Make sure you have the uInitrd at the same place where your uImage is:
/uInitrd


And then, boot up, interrupt serial console, set bootcmd and then boot:
setenv bootcmd 'usb start; ext2load usb 0:1 0x8000000 /uImage; ext2load usb 0:1 0x1100000 /uInitrd; bootm 0x8000000 0x1100000'
boot

After you've booted into Debian, set it permanently:

fw_setenv bootcmd  'usb start; ext2load usb 0:1 0x8000000 /uImage; ext2load usb 0:1 0x1100000 /uInitrd; bootm 0x8000000 0x1100000'

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.2 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
September 08, 2015 03:10PM
Yep, it works !
I dont understand how it can work before without propre set uInitrd in bootcmd...

Many thx bodhi you save my day and probably my marriage :D
Re: Linux Kernel 4.2 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
September 08, 2015 03:23PM
sodd Wrote:
-------------------------------------------------------
> Yep, it works !
> I dont understand how it can work before without
> propre set uInitrd in bootcmd...

It could work if the Debian kernel was compiled in a similar way Arch Linux was (everything is compiled into kernel, no module needed).

>
> Many thx bodhi you save my day and probably my
> marriage :D

Hey, I'm happy to hear that :))

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 4.2 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
September 08, 2015 11:10PM
bodhi Wrote:
-------------------------------------------------------
> Be aware that upgrade like this will result in a
> massive change in your system, it will take a
> while to run it, there is a small chance that
> something might go wrong. So a good backup of your
> current HDD is a must.


Thanks for the help.
I think I'll install the system in a separate USB flash drive and use the current HDD for swap and data stoarge only.
The main reason for updating the kernel is that I'm unable to install packages like rtorrent and deluge. I've added the repository but I always get a 404 -file not found error and end up with unmet dependencies.
Can I use Jeff's scripts now to install Debian on a flash drive - it it working?
Re: Linux Kernel 4.2 Kirkwood (FDT) and 3.16 Kirkwood (non-FDT) package and rootfs
September 08, 2015 11:58PM
archat68,

> I think I'll install the system in a separate USB
> flash drive and use the current HDD for swap and
> data stoarge only.

That's how I would do it.

> Can I use Jeff's scripts now to install Debian on
> a flash drive - it it working?

Jeff's script is out-of-date, so it is problematic. I would use the prebuilt 3.16 rootfs as I've mentioned in the post above:
http://forum.doozan.com/read.php?2,12096,23672#msg-23672

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Linux Kernel 3.18 (FDT) and 3.16 (non-FDT) Kirkwood package and rootfs
September 09, 2015 06:33AM
Dear bodhi,

I just installed your 4.2 kernel, but the wifi card still does not appear. Can you suggest something to try?

tanya
Attachments:
open | download - dmesg-4.2.txt (19 KB)
Sorry, you can't reply to this topic. It has been closed.