Linux Kernel 6.10.11 Kirkwood package and Debian rootfs

Hi bodhi,

I wondered, too.

But according to OpenStora knowledge base:
http://www.openstora.com/forum/viewtopic.php?f=1&t=45&p=442

"Reset is mpp38"

And pioneer's code:
https://github.com/kirov/stora-debian-kernel/blob/master/0001-Support-for-Netgear-Stora.patch

"116: +#define NETGEAR_MS2110_RESET_BUTTON 38"

Be careful, following comment in this patch is probably mistake (at least, source code isn't so):

"184:+ MPP37_GPIO, /* reset button input */"

@Hiro.AK47,

> Be careful, following comment in this patch is
> probably mistake (at least, source code isn't
> so):
>
> "184:+ MPP37_GPIO, /* reset button input */"

Got it. That comment was indeed a mistake!

Thanks! I'm recompiling the DTB and done.

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

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

Thanks a lot!
I'll try the new kernel now.
Btw how does the ext4 encryption work?

@theliquid,

Damn, I did not turn on this kernel config!!! There was a major bug in this area before while it was in released cadicate, so I took it out of my ToDo list and forgot about it :) I'll see if I can compile the module and you can test it that way.

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

@theliquid,

Ext4 encryption: I will add this capability in the next release (using it as module is not doable in the current kernel).

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

@bodhi


Ok, thanks. I'm looking forward to it. Beside the encryption the kernel works flawlessly.

bodhi Wrote:
-------------------------------------------------------
> Summary decription:
>
> These are my ongoing released Kirkwood kernel builds. tld-xx is my own naming convention for a minor version in a kernel. For example, 3.xx.0-kirkwood-tld-1 is version 3.xx.0, custom version tld-1. When you see -kirkwood-tld-xx postfix, it's my custom build (where mainline build has -kirkwood postfix).
>
Hello Bodhi,

What does tld mean, especially when used in Linux-4.1.0-kirkwood-tld-1?

Hi habibie,

> What does tld mean, especially when used in
> Linux-4.1.0-kirkwood-tld-1?

It's just a proper noun, in the same sense "kirkwood" is! It does not have any technical meaning behind it. It's an accronym that is only meaningful to me (feel free to change it to anything meaningful to you, if you build your own kernel from the released patch, just make sure that you can match it with my versions). This serves 2 purposes for my releases.

1. So that I can keep track of minor versions in a kernel release, and I did not want to name it "-bodhi". Some people don't like seeing personal info when they look at the system information, but I need to identify the kernel version to know how to help.

2. The proper name will preserve the kernel uImage file (because it will cause Debian flash-kernel to fail to generate the uImage automatically). This is to help users avoiding the mistake of wiping out this file unintentionally (which will happen if they have flash-kernel installed, and if the kernel name is a standard name from mainline).

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

Hello Bodhi,

Thank you for your clarification. I understand it is just an acronym that is meaningful to you. Perhaps, the question I should have asked is what is the fanciful expansion of tld used in the Linux-4.1.0-kirkwood-tld-1.

@habibie,

> Perhaps, the question I should have asked is
> what is the fanciful expansion of tld
> used in the Linux-4.1.0-kirkwood-tld-1.

Ah :) tld is my initials. It's an old habit from team collaborating works.

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

Hello Bodhi,

When I first saw your initial tld, I used to think it is an acronym of the top-level domain. Hopefully, I won't think in that way anymore after your above clarification. Thank you.

Hello Bodhi,

I really had hard time understanding the steps to make the usb-key, anyway I've arrived using the 3.18 rootfs.tar file and my NSA-325 now runs Debian.

I wanted to try the 4.1.0 kernel, but I haven't found any 4.1.0 rootfs tar file so I suppose I can use it with 3.18.5 rootfs one. There are others alone kernel tars files that are also into the rootfs tars, so I guessed that the kernel tar files are supposed only for upgrading and that they can coexist with different rootfs versions.

Tryng to run the steps reported into the help, I can't understand where I can find the "initramfs-4.1.0-kirkwood-tld-1" and "initrd.img-4.1.0-kirkwood-tld-1" files to run the step:

mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.0.0-kirkwood-tld-1 -d initrd.img-4.0.0-kirkwood-tld-1 uInitrd

to create uInitrd (I chosen the 4b way to use original U-boot without the need to modify u-boot envs)

1) What did I lack into the explanation?

2) Do 3.18 kernel and 4.10 one, work with ext4 rootfs?

3) Does it make sense to prepare the usb key with a swap linux partition too?

4) If it makes sense, then does it be anought 512MB swap space? ( I did it)

5) Is 3.17 the latest wheezy rootfs?

6) How to use the patch file into the kernel tars? Does it mean that the kernel upgrade works only on running systems?

thanks in advance for any help.

desigabri Wrote:
-------------------------------------------------------
> Hello Bodhi,
>
> I really had hard time understanding the steps to
> make the usb-key, anyway I've arrived using the
> 3.18 rootfs.tar file and my NSA-325 now runs
> Debian.
>
> I wanted to try the 4.1.0 kernel, but I haven't
> found any 4.1.0 rootfs tar file so I suppose I can
> use it with 3.18.5 rootfs one. There are others
> alone kernel tars files that are also into the
> rootfs tars, so I guessed that the kernel tar
> files are supposed only for upgrading and that
> they can coexist with different rootfs versions.

It's a normal procedure to update Linux kenel on current rootfs. See the corresponding section on kernel 4.0 for instruction on how to use the "dpkg -i" command to install.

>
> Tryng to run the steps reported into the help, I
> can't understand where I can find the
> "initramfs-4.1.0-kirkwood-tld-1" and
> "initrd.img-4.1.0-kirkwood-tld-1" files to run the
> step:
>
> mkimage -A arm -O linux -T ramdisk
> -C gzip -a 0x00000000 -e 0x00000000 -n
> initramfs-4.0.0-kirkwood-tld-1 -d
> initrd.img-4.0.0-kirkwood-tld-1 uInitrd
>
> to create uInitrd (I chosen the 4b way to
> use original U-boot without the need to modify
> u-boot envs)
>
> 1) What did I lack into the explanation?

Initrd is automaticall generated by the "dpkg -i" command.

>
> 2) Do 3.18 kernel and 4.10 one, work with ext4
> rootfs?

Yes.

> 3) Does it make sense to prepare the usb key with
> a swap linux partition too?

It is simpler to use a swap file instead.

>
> 4) If it makes sense, then does it be anought
> 512MB swap space? ( I did it)

At least 512MB.

> 5) Is 3.17 the latest wheezy rootfs?
>

Yes.

> 6) How to use the patch file into the kernel tars?
> Does it mean that the kernel upgrade works only on
> running systems?

Ignore the patch file if you only want to install kernel. Patch file is for building your own kernel. And it's included so that the release tarball is an open source GPL compliant package.

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

thanks for replay, and for the answers,

1) this is about dpkg:

root@debian-jessi:/media/root/rootfs/boot318#
root@debian-jessi:/media/root/rootfs/boot318#dpkg -i linux-image-3.18.5-kirkwood-tld-1_1_armel.deb
dpkg: errore nell'elaborare l'archivio linux-image-3.18.5-kirkwood-tld-1_1_armel.deb (--install):
l'architettura del pacchetto (armel) non corrisponde a quella del sistema (amd64)

This is why I asked if the kernel upgrade is intended to be done on the running machine.
It seems to me that I can't do that operation directly on my pc to prepare the usb-key...

isn't it?

2) "...It is simpler to use a swap file instead." : nice! but I don't know where chose/set a swap file ik place of a swap partition :( :( :(


thanks in advance again, for your help

desigabri Wrote:
-------------------------------------------------------
> thanks for replay, and for the answers,
>
> 1) this is about dpkg:
>
> root@debian-jessi:/media/root/rootfs/boot318#
> root@debian-jessi:/media/root/rootfs/boot318#dpkg
> -i linux-image-3.18.5-kirkwood-tld-1_1_armel.deb
> dpkg: errore nell'elaborare l'archivio
> linux-image-3.18.5-kirkwood-tld-1_1_armel.deb
> (--install):
> l'architettura del pacchetto (armel) non
> corrisponde a quella del sistema (amd64)
>
> This is why I asked if the kernel upgrade is
> intended to be done on the running machine.
> It seems to me that I can't do that operation
> directly on my pc to prepare the usb-key...
>

It's intended to to be done on a running system. Before doing it, make a back up of your rootfs as a precaution.

>
> 2) "...It is simpler to use a swap file instead."
> : nice! but I don't know where chose/set a swap
> file ik place of a swap partition :( :( :(
>
I don't have a link, but I've posted instructions about swap file in the forum. Please try searching (search box is in the upper right corner), if you can't find it then let me know.

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

So many thanks bodhi for your help.

In the mean while I was waiting for any answer I tried doing it on the running macchine and as you suggested to me it worked.

I'll look for the swap file another time, at the moment I wanted to try whezzy and jessie to see what is possible to run on them.

So I'll search for your instruction on the forum later: now I'm too late, just few hours for sleep.

THANKS AGAIN BODHI, HAVE nice days

Is it possible, that there is something wrong with pam_unix.so module?

I'm trying to use /usr/lib/openvpn/openvpn-plugin-auth-pam.so with openvpn. I did this on 2 x86 machines on Ubuntu which worked fine. But with Kernel 4.1 on my Pogoplug I get error message like this: PAM audit_log_acct_message() failed: Operation not permitted.

Any clue?

Edit: on Raspberry Pi it also works flawlessly, so I think it is Pogoplug/Kernel related.



Edited 1 time(s). Last edit at 07/26/2015 01:50PM by theliquid.

theliquid,

>. But with Kernel 4.1 on my
> Pogoplug I get error message like this: PAM
> audit_log_acct_message() failed: Operation not
> permitted.

Please post the full error text in the log.

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

bodhi Wrote:
-------------------------------------------------------
> theliquid,
>
> >. But with Kernel 4.1 on my
> > Pogoplug I get error message like this: PAM
> > audit_log_acct_message() failed: Operation not
> > permitted.
>
> Please post the full error text in the log.


This is the only error I get; its in auth.log and error.log. I can't find any other error in the logs.

theliquid,

No idea why! since these are not main line packages, dont know what to make of this. RPi rootfs is a prebuilt heavy rootfs so it has many things installed already.

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

bodhi Wrote:
-------------------------------------------------------
> theliquid,
>
> No idea why! since these are not main line
> packages, dont know what to make of this. RPi
> rootfs is a prebuilt heavy rootfs so it has many
> things installed already.

Ok, thanks anyway. Nvm I switched to a RPi v2 for my home server due to 1GB of RAM :)

hello i have put debian on my goflex home

this is the result to uname -ra

Linux debian 2.6.32-5-kirkwood #1 Tue May 13 17:59:08 UTC 2014 armv5tel GNU/Linux

what you tink update or no to a new kernell

regards

pocket Wrote:
-------------------------------------------------------
> hello i have put debian on my goflex home
>
> this is the result to uname -ra
>
> Linux debian 2.6.32-5-kirkwood #1 Tue May 13
> 17:59:08 UTC 2014 armv5tel GNU/Linux
>
> what you tink update or no to a new kernell
>
> regards

Yes. But be sure to make a back up of your existing rootfs first. Then go to the kernel thread for the latest kernel. It will be a massive update when you do

apt-get udate
apt-get upgrade

You will need to regenerate the uInitrd after upgrading.

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

hi bodhi and tanks for your fast reply

i´m dont uderstant a lot of linux i have read the thread kernell but i dont now were to start can you please resume the update.

i only boot my goflex via usb i dont use hdd , have folowed this link for instalation only the part uboot and debian , dont have recue system.



bodhi Wrote:
-------------------------------------------------------
> pocket Wrote:
> --------------------------------------------------
> -----
> > hello i have put debian on my goflex home
> >
> > this is the result to uname -ra
> >
> > Linux debian 2.6.32-5-kirkwood #1 Tue May 13
> > 17:59:08 UTC 2014 armv5tel GNU/Linux
> >
> > what you tink update or no to a new kernell
> >
> > regards
>
> Yes. But be sure to make a back up of your
> existing rootfs first. Then go to the
> kern
> el thread for the latest kernel. It will be
> a massive update when you do
>

> apt-get udate
> apt-get upgrade
>

> You will need to regenerate the uInitrd after
> upgrading.



Edited 1 time(s). Last edit at 07/31/2015 07:52AM by pocket.

pocket,

I am not sure how can I help? Which part you of the installation that you had trouble with?

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

Hi pbg4,

> since I am testing at the moment for a new
> devicetree description to
> let the nsa3xx-hwmon kernel module recognize the
> nsa320 mcu I have here two
> nsa320 boxes,

Any luck in testing this NSA320 DTS change?

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

Hi bodhi,

not really, at least one of the linux-arm kernel devs has answered an email I send to him,
so the plan what to do is clear to me, see my answer here:

http://forum.doozan.com/read.php?3,12381,23047#msg-23047

but it will take some more time due to the normal professional duties,..

best wishes pbg4

Hello i´m stuck here

Quote
root@debian:/boot# fw_setenv load_dtb 'ext2load usb 0:1 0x1c00000 /boot/dts/kirkwood-goflexhome.dtb'
Read error on /dev/mtd0: Cannot allocate memory

so i pass this and then i reboot and now have this

Quote
root@debian:~# uname -snr Linux debian 4.1.0-kirkwood-tld-1

But wen i try apt-get upgrade give this

Quote
root@debian:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

it´s ok ??



Edited 2 time(s). Last edit at 08/04/2015 05:24PM by pocket.

pocket,

Once you're able to log into Debian like this, it is all OK.

root@debian:~#

So you've done the installation!

Now the next step is to update your system:

apt-get update
apt-get upgrade

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