Linux Kernel 6.11.6 Kirkwood package and Debian rootfs

Last posts moved here:
http://forum.doozan.com/read.php?2,30947

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

The latest linux-4.8.3-kirkwood-tld-1 package works perfectly fine on my GoFlexNet, which I recently brought back to life. Thanks again for the effort bodhi, really appreciated, keep up the good work!

[offtopic] I am no bot, who dares to accuse me of a bot, you brutal monster. [/offtopic]

PogoPlug e02 specs



Edited 1 time(s). Last edit at 11/14/2016 04:23PM by WzL.

WzL Wrote:
-------------------------------------------------------
> The latest linux-4.8.3-kirkwood-tld-1 package
> works perfectly fine on my GoFlexNet, which I
> recently brought back to life. Thanks again for
> the effort bodhi, really appreciated, keep up the
> good work!
>
> [offtopic] I am no bot, who dares to accuse me of
> a bot, you brutal monster. [/offtopic]

Cool!
I think when you click the button too fast twice, the forum sw thinks you tried to post the same thing again, therefore you're a bot :))

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

Many thanks bodhi for your work :)

I currently use your patches to build my own kernel. I used it to patch 4.8.8 kernel source and it works fine except for lirc_rpi.

I did try using your kernel config but it kept giving a kernel panic on boot (no file system), even if I set init=/bin/systemd, so had to use my own .config which worked fine. Link to config I used.

Both my NSA310B & NSA310A running fine, except the A appears to get a lot hotter (not sure how to fix that).

mpmc Wrote:
-------------------------------------------------------
> Many thanks bodhi for your work :)
>
> I currently use your patches to build my own
> kernel. I used it to patch 4.8.8 kernel source and
> it works fine except for lirc_rpi.
>
> I did try using your kernel config but it kept
> giving a kernel panic on boot (no file system),
> even if I set init=/bin/systemd, so had to use my
> own .config which worked fine.
> https://gist.githubusercontent.com/anonymous/
> a9de67c430464553633404394fab5f7c/raw/14fad222d5ff8
> 04225f19e2f4d64a82631b9b652/Config]Link to config
> I used.
>
> Both my NSA310B & NSA310A running fine, except the
> A appears to get a lot hotter (not sure how to fix
> that).

mpmc,

Cool :) Thanks for reporting this! what was the problem in lirc_pi? is it in the source code? and if I do a diff between .config files will I get the exact difference or more?

The hot temp problem might be fan related. I might need to look at the DTS.

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

Hi Bodhi,

I can't remember the exact output during the build, but I believe it was something do to with invalid types being passed to a function, I just disabled it.

As for the .config, I'm honestly not sure what the difference would be. I start with the mvebu_v5_defconfig, make sure everything for systemd is set and add media/filesystem drivers.

I was planning on switching to your uboot (using stock atm) but I have some bad blocks (on both) & I didn't want to risk it.

NSA310S

[    0.797451] Scanning device for bad blocks
[    0.835784] Bad eraseblock 354 at 0x000002c40000

NSA310A (It's actually the B model as it has the lm85 sensor).

[    0.874414] Scanning device for bad blocks
[    0.923008] Bad eraseblock 477 at 0x000003ba0000
[    0.929270] Bad eraseblock 508 at 0x000003f80000

Do these look okay & would it be safe to switch to your uboot?

mpmc,

> I can't remember the exact output during the
> build, but I believe it was something do to with
> invalid types being passed to a function, I just
> disabled it.
>

Thanks, I guess I will find out when I compile kernel 4.9!

> [ 0.835784] Bad eraseblock 354 at
> [ 0.923008] Bad eraseblock 477 at
> [ 0.929270] Bad eraseblock 508 at

> Do these look okay & would it be safe to switch to
> your uboot?

They are way out in NAND stock kernel and rootfs. So it is safe to flash u-boot.

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

Kernel linux-4.9.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)

@bodhi

Do you think you could put your kernel / source on github? :)

Cheers.

mpmc Wrote:
-------------------------------------------------------
> @bodhi
>
> Do you think you could put your kernel / source on
> github? :)
>
> Cheers.

No need to :) you got everything you need to build your own kernel in the released tarball there are 6 files in there, 2 are needed to build. Download the mainline kernel source tree (or clone that Git version) and apply the patch, copy the config file to it, start building.

config-4.8.0-kirkwood-tld-1 
linux-4.8.0-kirkwood-tld-1.patch

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

Last post moved to its own topic.

Any installation problem or not sure how to install, please make a new topic.

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

bodhi, do you see anything in printenv that is preventing boot into rescue system ?

jst818,

I've moved the rescue system problem into new topic:
http://forum.doozan.com/read.php?2,31989

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

I fuck1ng love you bodhi!

Everything is so nicely packed and build together, clarity and well documented, just outstanding work, love you so much!

I'm willing to rebuild the kernel, just to prune out some modules I don't use that are built-in, so I squeeze the most bytes of it. Is there any place where I can get the kernel sources with all patches and such, just like the ones you use for building?

That would be freaking awesome!

Thanks a lot dude, totally own you a drink!

Hey pogolover,

Glad you like it :)

> I'm willing to rebuild the kernel, just to prune
> out some modules I don't use that are built-in, so
> I squeeze the most bytes of it. Is there any place
> where I can get the kernel sources with all
> patches and such, just like the ones you use for
> building?
>

Everything you need is in this tarball:

Quote

Updated 17 Dec 2016:

Kernel linux-4.9.0-kirkwood-tld-1 package has been uploaded.

Latest Linux kernel 4.x general release information can be found at:
LinuxChanges log

Download at Dropbox:

linux-4.9.0-kirkwood-tld-1-bodhi.tar.bz2

Get the kernel source tree from kernel.org, and apply the patch, copy the config file into the source tree and start building.

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

Moved Rob's problem to its own thread:
http://forum.doozan.com/read.php?2,32041

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

Last post moved here:

http://forum.doozan.com/read.php?2,32677

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

where to downlod rootfs?

youxiaojie Wrote:
-------------------------------------------------------
> where to downlod rootfs?

Scroll down and find the section:

Quote

Updated 20 Feb 2016:

This Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 is to keep in sync with kernel Linux-4.4.0-kirkwood-tld-1.

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

thanks a lot. and anther question, is the apps runing in debian compatible which runing in openwrt ? or vice verse.
is the apps binary compatible in debian and openwrt?I leant that openwrt uses musl lib,and debian use glibc ,is it compatible? if binary compatible is not,how about the source compatible?

youxiaojie Wrote:
-------------------------------------------------------
> thanks a lot. and anther question, is the apps r
> uning in debian compatible which runing in openwrt
> ? or vice verse.
> is the apps binary compatible in debian and openwr
> t?I leant that openwrt uses musl lib,and debian us
> e glibc ,is it compatible? if binary compatible is
> not,how about the source compatible?

The kernel ABI should be the same.

But I'm curious why would you want to mix Debian and LEDE? if you are using OpenWrt/LEDE then why not use that rootfs. Is that because you want to run a full rootfs on external drive, but kernel in NAND?

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

I just want to have a try.the other reason is I found your ubi/nand tools is for linux not openwrt. and I have to run some special software, such as softether vpn. so I hope the binary code is compatible.

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

Please post problem booting in a separate thread.

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

Again.

Please post questions that are not relevant to this rootfs and kernel in a different thread.

Last post moved to its own topic.

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



Edited 1 time(s). Last edit at 02/27/2017 03:08AM by bodhi.

Kernel linux-4.10.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)

bodhi Wrote:
-------------------------------------------------------
> Kernel linux-4.10.0-kirkwood-tld-1 package has bee
> n uploaded. Please see 1st post for download link.


Thank you! Updated worked perfect as always! Thank you so much!

Hi all, it has been a while but today as it turned out a friend gave me a black pogoplug e02 to play with. First thing for me is to check out the latest updates from bodhi and friends and voila a new kernel version was available. So what I did was the usual, update uboot and install latest rootfs and update kernel. After that an apt-get update/upgrade/dist-upgrade and done. Some small tuning like disable ipv6 module and replacement of sshd server by dropbear etc. gave me a memory footprint of in the 30's of megabytes of ram used. Which is normal I guess because that's what it has always been for me in the past. Only this time I was in for a challenge, Debian 9 (testing) it was going to be. So I updated /etc/apt/sources to reflect Debian testing repo, ran apt-get again, and 30/40 minutes later I had a working Debian testing implemented on the PogoPlug e02.
This was all nice and all until I looked at the memory footprint; it was a shocking 9.7mb. Same tuning done as always, nothing different there. Did boot a couple of times but seriously, if your not running production sites with your pogoplug, one ought to concider Debian testing! Keep up the good work!!!

PogoPlug e02 specs



Edited 4 time(s). Last edit at 03/17/2017 07:43AM by WzL.

WzL Wrote:
-------------------------------------------------------
> Hi all, it has been a while but today as it turned
> out a friend gave me a black pogoplug e02 to play
> with. First thing for me is to check out the lates
> t updates from bodhi and friends and voila a new k
> ernel version was available. So what I did was the
> usual, update uboot and install latest reports and
> update kernel. After that an apt-get update/upgrad
> e/dist-upgrade and done. Some small tuning like di
> sable ipv6 module and replacement of sshd server b
> y dropbear etc. gave me a memory footprint of in t
> he 30's of megabytes of ram used. Which is normal
> I guess because that's what it has always been for
> me in the past. Only this time I was in for a chal
> lenge, Debian 9 (testing) it was going to be. So I
> updated /etc/apt/sources to reflect Debian testin
> g repo, ran apt-get again, and 30/40 minutes later
> I had a working Debian testing implemented on the
> PogoPlug e02.
> This was all nice and all until I looked at the me
> mory footprint; it was a shocking 9.7mb.

Cool!

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

@ bodhi
I had problems using my stick with your latest rootfs on different plugs.
maybe you could advice user to change the following in their rootfs if the use the stick/cf-card on different Plugs to avoid network issues:

nano /etc/udev/rules.d/70-persistent-net.rules

clear everything and paste the following:

# Pogoplug: net device ()
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

--joerg_999

bodhi Wrote:
-------------------------------------------------------
> mpmc,
>
> The config-4.10.0-kirkwood-tld-1 should not be a p
> roblem with detecting the HDD. You are booting wit
> hout initrd? is that correct?

Yes. The only time I use a initrd is for Debian install (using the initrd for the qnap ts-119, which installs fine :p). I then manually start it back up again & place the kernel on the hard disk so I'm not touching the flash.

>

> Marvell>> bootm 0x800000
> ## Booting image at 00800000 ...
> Image Name:   Linux Kernel for NSA310S
> Created:      2017-04-01  20:30:18 UTC
> Image Type:   ARM Linux Kernel Image (uncompres
> sed)
> Data Size:    3232176 Bytes =  3.1 MB
> Load Address: 00008000
> Entry Point:  00008000
> Verifying Checksum ... OK
> OK
> 
> Starting kernel ...
>

>
> If you use my kernel config, you should boot with
> uImage and uInitrd. So load the uInitrd at 0x11000
> 00, and

I'm not sure which uInitrd to use in this case (or which you're referring). :p

>
>

> fatload usb 0 0x1100000 <path to uInitrd>
> bootm 0x800000 0x1100000
>

>
> By the way, you are still running stock u-boot! I'
> d strongly recommend installing the latest u-boot.
> Try kwboot with serial console to make sure you ha
> ve a recovery path, and then install. You're missi
> ng out too many good features running stock u-boot
> .

I know I am, I'm just a bit wary of upgrading as I feel I'll goof it up :p

I looked at davygravy's UART boot page & when I do [md ff00003c] to view the version, it prints this..

Marvell>> md ff00003c
ff00003c: 00000000 00000000 00000000 00000000    ................
ff00004c: 00000000 00000000 00000000 00000000    ................
ff00005c: 00000000 00000000 00000000 00000000    ................
ff00006c: 00000000 00000000 00000000 00000000    ................
ff00007c: 00000000 00000000 00000000 00000000    ................
ff00008c: 00000000 00000000 00000000 00000000    ................
ff00009c: 00000000 00000000 00000000 00000000    ................
ff0000ac: 00000000 00000000 00000000 00000000    ................
ff0000bc: 00000000 00000000 00000000 00000000    ................
ff0000cc: 00000000 00000000 00000000 00000000    ................
ff0000dc: 00000000 00000000 00000000 00000000    ................
ff0000ec: 00000000 00000000 00000000 00000000    ................
ff0000fc: 00000000 00000000 00000000 00000000    ................
ff00010c: 00000000 00000000 00000000 00000000    ................
ff00011c: 00000000 00000000 00000000 00000000    ................
ff00012c: 00000000 00000000 00000000 00000000    ................

And going from the posts in the thread, lots of others have been having issues too.