Linux Kernel 6.7.5 Kirkwood package and Debian rootfs

bodhi,

sorry, not 8192 bytes, but 8192 kbytes (8M). people said this mem is used for kernel purposes, someone even advised to set 64M for that, lol.
I've tested this for a few hours and it seems to work - there is no logs related to page failtures yet.

The only storage attached to my GFN is WD Green 1.5T HDD plugged directly to right sata port, cause it wouldn't boot in another due to some bug in uboot code.

~# cat /proc/partitions
major minor #blocks name

8 0 1465138584 sda
8 1 979933 sda1 <-- rootfs
8 2 289170 sda2 <-- swap
8 3 1463866897 sda3 <-- data

SiruS,

I think you probably solved this with this solution! we will see if the error repeat. But looking at the explanation for memory tuning at openSUSE site, it is very specific how this number would help to eliminate page allocation failure error.

Yeah, LOL at 64M :)) we don't have that much to spare :)

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

bodhi,

here's fresh and detailed explanation of things get happened: http://www.yaleman.org/2013/02/03/linode-swapper0-page-allocation-failure-issue/

~# cat /proc/sys/vm/min_free_kbytes
1442
default value is too low, so maybe it's really causing some OOPS

BTW, i saw you have compiled kernel 3.8.x. when will it be public as your 3.6.x kernel?

SiruS,

I will upload kernel 3.8.11 in a couple days.

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

Using the kernel patch (against standard Linux source 3.9.2) that can be found at archlinuxarm and making a few amendments to the archlinuxarm .config file, kernel 3.9.2 compiles and loads cleanly for the Dockstar.

Kernel 3.9.1 for testing (with BFQ, no AUFS)

To turn off the LED:

echo none > /sys/devices/platform/leds-gpio/leds/status:green:health/trigger

For problems with alignment:

echo 2 > /proc/cpu/alignment

For me Kernel 3.9.2 is a worthwhile upgrade from 3.3.3 - no more porblems with kernel-mode PPTP.

All cedit to moonman at archlinuxarm.

that archlinux patch is terrifyingly long, although it's Make options dont look unlike what i see with a vanilla 3.9.2 kernel.

really looking forwards to seeing a newer known-good from bodhi or other. trying to do do everything (uboot+kernel) from recent releases and i have what seems like a good uboot hosting a ubi+ubifs debian, but i cannot get past the "booting the kernel;" no output follows, the system doesn't seem to do anything.

i do have a jtag interface, so i could hypothetically debug what seems like this non-booting kernel although i have not yet researched how i would do that.

I've uploaded kernel 3.8.11 kirkwood package. See 1st post for updates.

I updated my Pogoplug Mobile to your new 3.8.11 kernel. Works like a champ. Thanks for all your hard work Bodhi.

Thank you Bodhi.

-syong

is there an howto describing the build procedure anywhere?

Any reason to think that this will or won't work on a ZyXEL NSA320?

It won't work on NSA320. I did not include support for it, since I don't have the NSA320, and don't have the appropriate patch.

Hi,

Thx for your Kernel who works on my Pogo E02very well. But i have got a problem and need to compile a Driver for a USB Wifi Stick and need folowing Package:

linux-headers-3.8.11-kirkwood-tld

Do you got a Source for me?

Thx

I can upload it, but it will be a while, since I'm on the road for a couple weeks.

Thats no problem, thank you

Here, one more Pogoplug Mobile successfully updated to your new 3.8.11 kernel!
Can boot from mmc or usb, LEDs working (arcNumber=3960, machid=F78).
Thanks for all your hard work and your precious time spent for all of us Bodhi!



Edited 1 time(s). Last edit at 05/30/2013 11:35PM by spooky2012.

Cool :) I am glad everybody found my contribution useful.

bump...
-------------------------------------------------------
> is there an howto describing the build procedure anywhere?

I've uploaded linux-headers-3.8.11-kirkwood-tld package. See 1st post for updates.

would you pls describe the build process?

Thx bodhi

Mhh, doesent seem to work

root@debian /tmp/xy > make
make -C tools
make[1]: Entering directory `/tmp/xy/tools'
gcc -g bin2h.c -o bin2h
make[1]: Leaving directory `/tmp/xy/tools'
/tmp/xy/tools/bin2h
cp -f os/linux/Makefile.6 /tmp/xy/os/linux/Makefile
make -C /lib/modules/3.8.11-kirkwood-tld/build SUBDIRS=/tmp/xy/os/linux modules
make: *** /lib/modules/3.8.11-kirkwood-tld/build: No such file or directory. Stop.
make: *** [LINUX] Error 2
root@debian /tmp/xy >

May be this will help:
http://www.cyberciti.biz/tips/build-linux-kernel-module-against-installed-kernel-source-tree.html

bodhi Wrote:
-------------------------------------------------------
> May be this will help:
> http://www.cyberciti.biz/tips/build-linux-kernel-m
> odule-against-installed-kernel-source-tree.html

the page describes how to compile a kernel module, I'm trying to understand how to create kernel packages instead, as I would like to produce kernel packages as you are doing. Besides that, are you compiling natively? no cross-compiling?

@gaogao,

That response was for Der Freibeuter above.

I don't have time to create a good howto, so I was hoping that you would have found the answer by searching the forum. So I did a search:
http://forum.doozan.com/read.php?2,524,page=1

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

my mistake, tks a lot for the link.

Thanks for that update man!

Is it wanted that all dvb drivers were missing in 3.6* and 3.8*?
No dvb*.ko were present and media build from git failes on 3.8 with the provided headers (timex.h).

Steven

derdigge Wrote:
-------------------------------------------------------
> Thanks for that update man!
>
> Is it wanted that all dvb drivers were missing in
> 3.6* and 3.8*?
> No dvb*.ko were present and media build from git
> failes on 3.8 with the provided headers
> (timex.h).
>
> Steven

Dvb drivers probably were not included in kernel config (I don't have any video device attached so never noticed that). If anybody wanted to request some video drivers to be included, then please post the specific module info, I will recompile another version for it. Device name (as known to Linux) and the ko file name(s) are needed.

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

bodhi Wrote:
-------------------------------------------------------
> derdigge Wrote:
> --------------------------------------------------
> -----
> > Thanks for that update man!
> >
> > Is it wanted that all dvb drivers were missing
> in
> > 3.6* and 3.8*?
> > No dvb*.ko were present and media build from
> git
> > failes on 3.8 with the provided headers
> > (timex.h).
> >
> > Steven
>
> Dvb drivers probably were not included in kernel
> config (I don't have any video device attached so
> never noticed that). If anybody wanted to request
> some video drivers to be included, then please
> post the specific module info, I will recompile
> another version for it. Device name (as known to
> Linux) and the ko file name(s) are needed.

Why so conplycated? If you could sinply add all dvb-drivers
as loadable modules the afford is 60mb of Diskspace and hundreds are supported.
I compiled linuxtvs media_build with 2.6.32 and had 60mb more diskusage after it and can
plugin what ever i want, inculding all those webcams...
An great but small pvr system such an Pogo btw ;)

derdigge Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > derdigge Wrote:
> >
> --------------------------------------------------
>
> > -----
> > > Thanks for that update man!
> > >
> > > Is it wanted that all dvb drivers were
> missing
> > in
> > > 3.6* and 3.8*?
> > > No dvb*.ko were present and media build from
> > git
> > > failes on 3.8 with the provided headers
> > > (timex.h).
> > >
> > > Steven
> >
> > Dvb drivers probably were not included in
> kernel
> > config (I don't have any video device attached
> so
> > never noticed that). If anybody wanted to
> request
> > some video drivers to be included, then please
> > post the specific module info, I will recompile
> > another version for it. Device name (as known
> to
> > Linux) and the ko file name(s) are needed.
>
> Why so conplycated? If you could sinply add all
> dvb-drivers
> as loadable modules the afford is 60mb of
> Diskspace and hundreds are supported.
> I compiled linuxtvs media_build with 2.6.32 and
> had 60mb more diskusage after it and can
> plugin what ever i want, inculding all those
> webcams...
> An great but small pvr system such an Pogo btw ;)

derdigge,

60MB is not significant for a disk-based rootfs, but it is when you want or plan to put it on flash :) But anyhow, most people are using thumb drive for roofts as I can guess.

OK then, please tell me how did you select all dvb-drivers in "make menuconfig"? is there a config option that you just selected or you had to go through the list and select each one?

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