building OXNAS 820 kernel

[traetox]

I am in the process of trying to build a new OXNAS kernel and am having a hell of a time.

I am very experienced with kernel dev in the X86 world and have built countless kernels for Android and my Gentoo boxen, but I am apparently screwing something up here.

I am building on my pogoplug V3 (one running Debian and one running ArchLinuxArm). I then use a tftpd-hpa server to load the kernel at the uboot prompt (via serial) to test them. Unfortunately I can't even get output from them. The errors range from "bad magic number", to "invalid instruction", to just flat freezing the pogo.

I am working off of the OXNAS 3.1 kernel on github (owned by WarheadSE). I am also using a slightly modified OXNAS config (also provided by WarheadSE). I do the following:

make menuconfig
make -j2 uImage
make modules
make modules_install

I then copy the uImage out of arch/arm/boot/uImage and load it up via tftp via:

tftp 0x60008000 /tftpboot/uImage
bootm 0x6008000

What am I missing? Could someone with a little more experience building these things give me a tip? I am comfortable with the code, but I am obviously screwing my build environment somehow.


Thanks

[WarheadsSE]

I would suggest using a different load address, for one. 6008000 is lower than is known to work on these. 60500000 I believe is where I have the uboot loading it to. Otherwise, I can update the .config, as it may probably out of date a bit.

[elazar]

Just $this->bbcode_second_pass_code('', 'tftpboot;bootm'). Mine seems to loads to 0x60000000 by default...

[WarheadsSE]

If that works, great. I can vouch for the address I gave though, as that is where I have been loading it to from the beginning.

[xenoxaos]

I second the 0x60500000. The pogoplug oxnas varieties load from 60500000.

[traetox]

Thanks, I was able to finagle your uImage.3lzo kernel to start to boot. My kernels still do nothing at all.

WarheadSE: Would you mind posting the .config you are currently working off of for the 3.1 branch?


Thank you.

[WarheadsSE]

I can. There are occasional issues though

[ftcodes]

What I am curious about that problem, I have simply used the SATA-only boot on my device (compatible one, just same chipset).
All what I did was the arch/arm/boot/uImage on the first partition and getting the modules to /lib/modules/3.1.0+.

The u-boot config is just as it was before from the ox820_sata_boot.tar.gz.

The main issue that can happen with the pogoplug is to have a mismatch of non-PCIe / PCIe between kernel and device.

The PCIe physics is not completely assembled on non-PCIe variants and will result into a failing startup due to never-ending config space read out. Probably that is what breaks your kernel, traetox.

[traetox]

the pci being included WAS breaking my builds. I am getting successful boots now.

I would still like to at least see Warheads current 3.1 config to compare against.

Thanks for your help.

[WarheadsSE]

http://ppl.ug/g3zDLIExc1U/

This is the last one I used to build. Watch for PCI!