Linux Kernel 6.11.6 Kirkwood package and Debian rootfs

I'm new to all of this but interested in getting two bricked ix4-200d boxes back up and running. Is there a link to a tutorial and required equipment to get started? I've read the OP but still don't know where to get started. Thanks!

red9r Wrote:
-------------------------------------------------------
> I'm new to all of this but interested in getting
> two bricked ix4-200d boxes back up and running. Is
> there a link to a tutorial and required equipment
> to get started? I've read the OP but still don't
> know where to get started. Thanks!

You need to connect serial console:
http://forum.doozan.com/read.php?8,13263

And the use Uart booting.
http://forum.doozan.com/read.php?3,12381

Once you have serial console, come back and I wll help you pick the uboot image to use in unbricking.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thank you Bodhi!

I have my serial console in hand and looking forward to learning the process.

red9r Wrote:
-------------------------------------------------------
> Thank you Bodhi!
>
> I have my serial console in hand and looking
> forward to learning the process.

Please create a new thread in U-Boot subforum when you're ready with serial console.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hi Bodhi,
i would like to try install docker on my NSA310, but when i checked dependences for than I stuck with missing CONFIG_MEMCG in your kernel 4.6. So my question is... Is it possible to include this module to your next kernel release?

Thx for you work !

sodd Wrote:
-------------------------------------------------------
> Hi Bodhi,
> i would like to try install docker on my NSA310,
> but when i checked dependences for than I stuck
> with missing CONFIG_MEMCG in your kernel 4.6. So
> my question is... Is it possible to include this
> module to your next kernel release?
>
> Thx for you work !

Sure, I could add it and keep it disabled by default, if it does not cost too much memory for people who are not using it. A lot of Kirkwwood plugs only have 128MB.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I've split the last post to its own thread http://forum.doozan.com/read.php?2,30430

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 10/03/2016 03:12PM by bodhi.

Kernel linux-4.8.0-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

sodd Wrote:
-------------------------------------------------------
> Hi Bodhi,
> i would like to try install docker on my NSA310,
> but when i checked dependences for than I stuck
> with missing CONFIG_MEMCG in your kernel 4.6. So
> my question is... Is it possible to include this
> module to your next kernel release?
>
> Thx for you work !

Hi sodd,

I did not have time to investigate the memory usage of this MEMCG so I did not include it in this 4.8 release. Will try that in the near future.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Problem with PCI (i.e. USB 3.0 and other PCIe interfaces) in kernel 4.8.

Fixed in the following 3 posts.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 10/13/2016 04:05AM by bodhi.

Looks like PCI is broken in kernel 4.8 due to the difference in DTS. So if you have the NSA325 v1/v2, the Pogo V4, and the Iomega ix4 200d, please replace the DTB with the kernel 4.6 DTB (attached in this post).

mv  /boot/dts/kirkwood-nsa325.dtb  /boot/dts/kirkwood-nsa325.dtb.v4.8
cp -a  kirkwood-nsa325.dtb /boot/dts/

mv  /boot/dts/kirkwood-pogoplug_v4.dtb  /boot/dts/kirkwood-pogoplug_v4.dtb.v4.8
cp -a  kirkwood-pogoplug_v4.dtb /boot/dts/

mv  /boot/dts/kirkwood-iomega_ix4_200d.dtb  /boot/dts/kirkwood-iomega_ix4_200d.dtb.v4.8
cp -a kirkwood-iomega_ix4_200d.dtb /boot/dts/

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 10/13/2016 02:53AM by bodhi.

DTBs for Asus_m25, Netgear_Stora, Qizhitong_501m_v2.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 10/13/2016 03:48AM by bodhi.

DTBs for Nsa310s and Nsa320s.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 10/13/2016 03:47AM by bodhi.

Reserved 2.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

he bodhi.

i'm using zram on all my small ram devices to "enlarge" RAM before using slow swap. Have you tought about updating the rootfs with the zram option by default?

its just adding this script to startup: ZRAM on Debian

Sash Wrote:
-------------------------------------------------------
> he bodhi.
>
> i'm using zram on all my small ram devices to
> "enlarge" RAM before using slow swap. Have you
> tought about updating the rootfs with the zram
> option by default?
>
> its just adding this script to startup:
> ZRAM on
> Debian

I have zswap enabled in the kernel. It is better.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

No problem, I'm patient :)

Any plan to release a new Kirkwood kernel to address CVE-2016-5195. See LWN article

Ray

Of course.

However, if your box is not facing the internet, no need to worry. Just be careful, as always: don't run any software that you cant tell whether it is from a reputable repo (such as Debian distribution).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Kernel linux-4.8.3-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Last post moved here: http://forum.doozan.com/read.php?2,30704

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Just updated to kernel 4.8.3 (from 3.16.0, I believe) on my Dockstar and now I'm getting a ton of ECC errors on boot:

[   22.951509] __nand_correct_data: uncorrectable ECC error
[   22.956878] Buffer I/O error on dev mtdblock1, logical block 0, async page read
[   22.964449] __nand_correct_data: uncorrectable ECC error
[   22.970005] __nand_correct_data: uncorrectable ECC error
[   22.975587] __nand_correct_data: uncorrectable ECC error
[   22.981132] __nand_correct_data: uncorrectable ECC error
...

My U-Boot is "U-Boot 2014.07-tld-2 (Sep 20 2014 - 01:10:10)", so I followed the "4b" steps.

I found a similar reference in a U-Boot thread that seemed to indicate that it may be harmless, but it sure is disconcerting. It takes a good 10 seconds for the boot process to get through all the errors. Everything seems to be working ok once it boots. I'm still on wheezy if it matters. My next step was to update to jessie.

-JT

JT,

Yes, update to jessie should get rid of the error message. But it is really harmless. This error occur when the command you issued does not understand NAND mtdblock device. And your system boot process most likey has executed one of those.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks! Will update in the next couple of days.

-JT

Update: After completing the kernel and dist upgrade, I still get the ECC errors:

[   23.932658] __nand_correct_data: uncorrectable ECC error
[   23.938095] blk_update_request: I/O error, dev mtdblock0, sector 2040
[   23.944841] __nand_correct_data: uncorrectable ECC error
[   23.950196] blk_update_request: I/O error, dev mtdblock0, sector 2040
[   23.956669] Buffer I/O error on dev mtdblock0, logical block 255, async page read

There's only 1 or two seconds worth of error messages now instead of 10 seconds, so I guess that's an improvement.

-JT

renojim Wrote:
-------------------------------------------------------
> Update: After completing the kernel and dist
> upgrade, I still get the ECC errors:

[  
> 23.932658] __nand_correct_data: uncorrectable ECC
> error
> [   23.938095] blk_update_request: I/O error, dev
> mtdblock0, sector 2040
> [   23.944841] __nand_correct_data: uncorrectable
> ECC error
> [   23.950196] blk_update_request: I/O error, dev
> mtdblock0, sector 2040
> [   23.956669] Buffer I/O error on dev mtdblock0,
> logical block 255, async page read

> There's only 1 or two seconds worth of error
> messages now instead of 10 seconds, so I guess
> that's an improvement.
>
> -JT

This is odd. Do you have bad blocks on NAND?

dmesg | grep -i bad

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

[    5.730994] Scanning device for bad blocks
[    5.790733] Bad eraseblock 723 at 0x000005a60000
[    5.854769] Bad eraseblock 1496 at 0x00000bb00000

Is that bad? So it had nothing to do with the kernel update? I just noticed the original ECC errors were on mtdblock1 and these are mtdblock0. I never noticed the mtdblock0 ECC errors, but that doesn't mean they weren't there.

-JT

JT,

[ 5.730994] Scanning device for bad
> blocks
> [ 5.790733] Bad eraseblock 723 at
> 0x000005a60000
> [ 5.854769] Bad eraseblock 1496 at
> 0x00000bb00000[/code]

> Is that bad? So it had nothing to do with the
> kernel update? I just noticed the original ECC
> errors were on mtdblock1 and these are mtdblock0.
> I never noticed the mtdblock0 ECC errors, but that
> doesn't mean they weren't there.
>
> -JT

I just want to confirm. The ECC error in dmesg is a red-herring, not real (mtdblock0 is only 1MB so that number is bogus). The bad blocks in this post are real, and they are not in mtd0. I would trust these 2 messages and note the bad blocks for future reference.

> [ 5.790733] Bad eraseblock 723 at
> 0x000005a60000
> [ 5.854769] Bad eraseblock 1496 at
> 0x00000bb00000[/code]

So nothing to worry about. Except that something try to load/check NAND during the kernel boot, and we dont know what it is. At that time, that program does not know how to interpret NAND info.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Can I install grub to enable apparmor on pogo?

GRUB_CMDLINE_LINUX="$1 apparmor=1 security=apparmor"

RyCKY_Martin Wrote:
-------------------------------------------------------
> Can I install grub to enable apparmor on pogo?
>

GRUB_CMDLINE_LINUX="$1 apparmor=1
> security=apparmor"

No, not possible.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)