Can I use linux-kirkwood-dt on NSA320 ?

[boteium]

I've been wondering if it's possible to install uboot-nsa320 and linux-kirkwood-dt on my NSA320.
The uboot was untested last time I heard. (from forum post last year)
And there hasn't been much talk about Zyxel devices on the forum.

Are these two packages safe to use ? Or should I avoid them and stick to linux-kirkwood.

[WarheadsSE]

The NSA-320 uboot should be stable at this point, from what I know of.

The package you mention has a dt according to this patch in our github

[boteium]

I tried "pacman -S uboot-nsa320 linux-kirkwood-dt"

The uboot installation failed. It appears that /etc/fw_env.config is not correct.
Because nothing seemed to be changed and fw_printenv gives the correct value (unchanged) after modifyiing fw_env.config, I guess I'm okay. I wouldn't dare to "pacman -S uboot-nsa320" again and have already reverted to linux-kirkwood. Everything is fine. My NSA320 still boots.

$this->bbcode_second_pass_code('', ' Warning: Bad CRC, using default environment
flash_erase: error!: /dev/mtd0
error 13 (Permission denied)
flash_erase: error!: /dev/mtd0
error 13 (Permission denied)
nandwrite: error!: /dev/mtd0
error 13 (Permission denied)
nandwrite: error!: /dev/mtd0
error 13 (Permission denied)
Warning: Bad CRC, using default environment
Can't open /dev/mtd0: Permission denied
Error: can't write fw_env to flash
error: command failed to execute correctly
')

[WarheadsSE]

This happened to you as root?

[boteium]

yes, It's "sudo pacman" after all.
I did tried to manually execute the code in .INSTALL line by line as root once, which gives the same error.
That's before I found fw_env.config wasn't working.

[WarheadsSE]

Check that the partitions it is addressing are actually there, and permissions are correct. It is possible there is a R/W bit that needs flipped first.

[boteium]

What should I be looking at ? I have no idea what to do.

$this->bbcode_second_pass_code('', '[yusuf@nsa ~]$ ls -l /dev/mtd*
crw------- 1 root root 90, 0 Feb 2 00:16 /dev/mtd0
crw------- 1 root root 90, 1 Feb 2 00:16 /dev/mtd0ro
crw------- 1 root root 90, 2 Feb 2 00:16 /dev/mtd1
crw------- 1 root root 90, 3 Feb 2 00:16 /dev/mtd1ro
crw------- 1 root root 90, 4 Feb 2 00:16 /dev/mtd2
crw------- 1 root root 90, 5 Feb 2 00:16 /dev/mtd2ro
crw------- 1 root root 90, 6 Feb 2 00:16 /dev/mtd3
crw------- 1 root root 90, 7 Feb 2 00:16 /dev/mtd3ro
crw------- 1 root root 90, 8 Feb 2 00:16 /dev/mtd4
crw------- 1 root root 90, 9 Feb 2 00:16 /dev/mtd4ro
crw------- 1 root root 90, 10 Feb 2 00:16 /dev/mtd5
crw------- 1 root root 90, 11 Feb 2 00:16 /dev/mtd5ro
crw------- 1 root root 90, 12 Feb 2 00:16 /dev/mtd6
crw------- 1 root root 90, 13 Feb 2 00:16 /dev/mtd6ro
crw------- 1 root root 90, 14 Feb 2 00:16 /dev/mtd7
crw------- 1 root root 90, 15 Feb 2 00:16 /dev/mtd7ro
crw------- 1 root root 90, 16 Feb 2 00:16 /dev/mtd8
crw------- 1 root root 90, 17 Feb 2 00:16 /dev/mtd8ro
')

$this->bbcode_second_pass_code('', '[root@nsa boot]# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "uboot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"
')

[moonman]

You may need to install this uboot from stock, just like for nsa325. The problem is that arch kernel expects different mtdparts from stock.

[WarheadsSE]

Which should be fixable with a definition.

[moonman]

Or that. But mtd is not writable from within arch, so either fix using netconsole/serial or from within stock ( either flash uboot or fix definition for mtd parts).