Post by badboy1985ro on Jun 10, 2008 0:53:16 GMT 7
I just downloaded the Thecus n1200 gpl code. I wold like to start recompile it. I am not new to the stuff. I recopiled the openwrt firmware so i have a pretty idea about how is it done. Can somebody point me to a tutorial to help me start. The rest i'l figure it out on the way.
Post by appleman1234 on Jun 12, 2008 15:29:47 GMT 7
Why are you recompiling the gpl code ? See your other thread for assistance, as far as I know tutorial for the thecus n1200 don't exist and I don't have any intention of writing them.
It is a simple as installing the build tools and dependencies as modules (using ppc woody binaries) and using the native environment with ssh or using a chroot environment with ssh or using a cross dev setup.
Post by badboy1985ro on Jun 12, 2008 16:33:51 GMT 7
When i run make "menuconfig" the first thing i looked for was the posibility to have iptables. And i found it. Also the firmware support "ttl modifie". It has a "package mangle " module that must be compiled in the kernel, and console acces.
Al that i need is there. i just need to know what packages and dependecies i neet to install so the process works wel. Help please.
Today i'l receive my n1200. So i need to know. pls
Post by appleman1234 on Jun 12, 2008 16:53:43 GMT 7
Why do it that way ? That way means you have to recompile the default kernel instead of loading your additional feature as a kernel module to the existing kerenel. And changing the kernel requires you to change the firmware which requires serial and jtag.
You run the risk of bricking your device if not careful. I just got the replacement hdd to day, so I am currently adding features to my File module, so that it automounts the eSATA hdd regardless of partiton format.
Please give more information and details, I haven't setup a cross dev environment yet, so I can't give instructions for crossdev just yet ...
I just had a look at some stuff, and they are using tc-fsl-x86lnx-ppc-uclibc from www.bitshrine.org/gpp/, so I would start there if you aren't doing local stuff
Post by appleman1234 on Jun 13, 2008 13:31:53 GMT 7
It should be as simple as building the additional modules on thecus 1200 or an cross compiling development environment and then packaging them and changes to the configuration files as a thecus addon module (that can be installed using module management.)
After further research and investigation, I know that you have to download www.bitshrine.org/gpp/mtwk-lnx-powerpc-gcc-3.4.3-glibc-2.3.3-0.28-1.i686.rpm, convert it to a targz using rpm2targz, then move it to /opt/mtwk, this will allow you type make menuconfig and modify the kernel configuration, if you add extra stuff from the same kernel into the directory the menuconfig will allow you to choose it, this includes iptables modules and packet mangle, then compile your additions as a module and insmod in ssh.
Post by badboy1985ro on Jun 17, 2008 17:56:21 GMT 7
Can you be more specific please about developing the modules? I downloaded the file you previously mentiond and ai recopiled the entire firmware also some module where compiled. But when i try to install a module nothing happens. It does not get installed. help please these would sove all my problems
Post by appleman1234 on Jun 19, 2008 11:33:28 GMT 7
Do you even know what the firmware is ?
Have you ever compiling a Linux compile before, what you do to add the modules is.
First install the development environment from the rpm either using rpm -i or extracting it then copying it to /opt/ so that the build path is the same.
Then you download the linux kernel 188.8.131.52 from kernel.org. Then you merge the trees ensuring that you don't delete any thecus specific patches, whether a file is a thecus specific patch can be determined by looking at timestamps of files or grepping for Cizitien Lee or Y.T Lee or Thecus.
Then you either customise the config manually with a text editor or using make menuconfig making sure you add any changes as modules.
Then you make the kernel modules using make modules.
Then you make a Thecus package or module that contains your kernel modules and some loading / initializing code. (Alternately you could just copy the kernel modules to the thecus and then use insmod and rmmod for testing first) Instructions for making Thecus modules are on the wiki.
Then you install your thecus module and enable it or your thecus. Then you are good to go. This method doesn't require kernel or firmware replacement.
I have exams to study for and assignments to work on, so this is all the information I can provide at the moment.
Post by badboy1985ro on Jun 21, 2008 16:50:10 GMT 7
Here is the output from my Thecus n1200 n1200:/# uname -r 184.108.40.206 n1200:/#
Here is the output after i try to load a ko module Dmesg: ipip: version magic '220.127.116.11 SMP gcc-3.4' should be '18.104.22.168 gcc-3.4' ipt_ttl: version magic '22.214.171.124 SMP gcc-3.4' should be '126.96.36.199 gcc-3.4'
And the error i get when try to load module insmod: cannot insert `ipip.ko': Invalid module format (-1): Exec format errorinsmod: cannot insert `ipip.ko': Invalid module format (-1): Exec format e
My laptop has a ubuntu kernel 2.6.22-14-generic But the gpl code i downloaded from nas central has the 188.8.131.52 kernel. When i typed make menuconfig in the top left corner of the screen i saw the kernel ver:184.108.40.206. So i did compite this version.