Which kernel is Pogo actually running?

[vic]

Hi there. Quite new to the whole Arch+PogoPlug thing. So, basically, I'm just goofing around and (still) I haven't find a stable configuration for my P-24.

I've recently fresh installed the root-fs from tar, and now I've a few questions I'm not able to figure out an answer myself.

Pogo has the root-fs from ArchLinuxARM-2012.12-oxnas.tar.gz (latest), pacman-syu_ed everything. All seems all right as it boots fine.

Now, since depmod says:

$this->bbcode_second_pass_code('', '
[root@alarm ~]# depmod -a
depmod: WARNING: could not open /lib/modules/2.6.31.6_SMP_820/modules.builtin: No such file or directory
')

I asked some questions about the kernel. Pacman says:

$this->bbcode_second_pass_code('', '
[root@alarm ~]# pacman -Qs linux kernel
local/iptables 1.4.16.2-1
Linux kernel packet control tool
local/kmod 11-2
Linux kernel module handling
local/linux-api-headers 3.6.3-1
Kernel headers sanitized for use in userspace
local/linux-firmware 20121118-1
Firmware files for Linux
')

but uname...

$this->bbcode_second_pass_code('', '
[root@alarm ~]# uname -a
Linux alarm 2.6.31.6_SMP_820 #6 SMP Thu Jun 14 19:49:57 CDT 2012 armv6l GNU/Linux
')

Ok so... this sounds a bit wierd to me.
Am I missing some steps? :-s

Thanks a lot to all maintainers and users reading this. And sorry for my noobness

[pepedog]

What happens if you touch /lib/modules/2.6.31.6_SMP_820/modules.builtin to create, and then depmod -a

The kernel is in NAND on this device, you can't upgrade it further at this point, I think someone is working on it

[vic]

Thank you pepedog for your answer.

Don't really know why I didn't thought to touch it, I've been really dumb. Effectively it cleared the warning:

$this->bbcode_second_pass_code('', '
[root@alarm ~]# depmod -a
depmod: WARNING: could not open /lib/modules/2.6.31.6_SMP_820/modules.builtin: No such file or directory
[root@alarm ~]# touch /lib/modules/2.6.31.6_SMP_820/modules.builtin
[root@alarm ~]# depmod -a
[root@alarm ~]#
')

For the kernel thing, I believed that NAND was hosting a "pointer" to the actual kernel. Anyway, nice to know the truth!

[pepedog]

There is a thread [How-To] Boot Entirely from SATA
viewtopic.php?f=29&t=2146
Not having one of these devices I can't understand why a later kernel can't be done that way (yet)

[xenoxaos]

The kernel has to be in nand because the u-boot is old and limited. It can only boot from either tftp or nand. There's a guy that's working (and fairly close to done) to bring uboot up to date. There's a 3.1 branch of the kernel that is buggy as hell and will have cache coherency problems under load. Sadly at this time, the only stable kernel is 2.6.31