Help with Linux based router

PiKe · 3 Jul 2012 at 10:29

I want to add ext3 support to my Thompson based BT HomeHub router.

I know this is possible as I found a tutorial but the problem is, the modules that are supplied as part of that tutorial are hosted on a dead link.

I need ext3.ko and the dependant modules.

Do I need to build them on the router somehow under the kernel the router is running?

Nunzio · 3 Jul 2012 at 12:09

Yeah, you would need to rebuild them if the poster cant reupload them to somewhere, now that megaupload is gone.

Good luck with that, i will be replacing the homehub the moment the bt engineer leaves my house

PiKe · 3 Jul 2012 at 12:10

I've worked out I need to cross-compile the modules. Difficultly I'm having at the moment is finding a MIPS toolchain.

jack.mitchell · 3 Jul 2012 at 13:27

Hi PiKe,

You could try using one of the OpenEmbedded pre-built toolchains. This is probably one of the easiest ways to get started. The following link is for the nightly toolchain builds from the Yocto project, it is a MIPS toolchain but if it matches your architecture is a different matter.

If you want to get a bit serious read some of the Yocto Project manuals and use it to build a toochain suited for your specific architecture.

http://autobuilder.yoctoproject.org/pub/nightly/CURRENT/toolchain/

A quick getting started is:

1) Extract toolchain to default location (/opt/poky)
2) Source the enviornment setup file

Code:

. /opt/poky/*/env*

3) Build module

I have never used a MIPS toolchain but I would expect the gcc bin files to be named

Code:

mips-poky-linux-*-gcc

If you take a peek in the /opt/poky/*/ directory you will see the binaries and sysroot.

Good luck!

PiKe · 3 Jul 2012 at 14:50

The GPL linux 2.6.8.1 from BT is incomplete so I can't make, any ideas?

jack.mitchell · 3 Jul 2012 at 15:41

The kernel sources are incomplete? If so then try building against a vanilla MIPS kernel and hope for the best, I'm afraid I only have minimal knowledge in cross-compiling kernel modules.

What guide are you following for cross-compiling?

PiKe · 3 Jul 2012 at 15:46

jack.mitchell said:
The kernel sources are incomplete? If so then try building against a vanilla MIPS kernel and hope for the best, I'm afraid I only have minimal knowledge in cross-compiling kernel modules.

What guide are you following for cross-compiling?

This one http://www.abiyo.net/gadgets/ext3onaniomegaiconnectwirelessdatastation

Getting nowhere fast really

jack.mitchell · 3 Jul 2012 at 16:04

What homehub vesion do you have?

http://bt.custhelp.com/app/answers/detail/a_id/35298/~/bt-home-hub-and-bt-voyager-gpl-code

jack.mitchell · 3 Jul 2012 at 16:19

I gave it a quick go but hazarding a guess I would imagine the toolchain I'm trying to use is too new for the ancient 2.6.8 kernel. It bails on the make with:

Code:

[jack@archHP linux]$ make menuconfig ARCH=mips
  HOSTCC  scripts/basic/fixdep
scripts/basic/fixdep.c: In function ‘traps’:
scripts/basic/fixdep.c:359:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
scripts/basic/fixdep.c:361:4: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
  HOSTCC  scripts/basic/split-include
  HOSTCC  scripts/basic/docproc
  HOSTCC  scripts/kconfig/conf.o
scripts/kconfig/conf.c: In function ‘conf_string’:
scripts/kconfig/conf.c:164:20: warning: variable ‘help’ set but not used [-Wunused-but-set-variable]
scripts/kconfig/conf.c: In function ‘conf_sym’:
scripts/kconfig/conf.c:198:6: warning: variable ‘type’ set but not used [-Wunused-but-set-variable]
scripts/kconfig/conf.c: In function ‘conf_choice’:
scripts/kconfig/conf.c:273:6: warning: variable ‘type’ set but not used [-Wunused-but-set-variable]
  HOSTCC  scripts/kconfig/mconf.o
scripts/kconfig/mconf.c:91:21: error: static declaration of ‘current_menu’ follows non-static declaration
In file included from scripts/kconfig/mconf.c:23:0:
scripts/kconfig/lkc.h:63:21: note: previous declaration of ‘current_menu’ was here
make[1]: *** [scripts/kconfig/mconf.o] Error 1
make: *** [menuconfig] Error 2

PiKe · 3 Jul 2012 at 16:36

The 2.0A, I've managed to get a makemenu now, but dies on build in cpu-probe.o with CPU_BCMxxxxx undeclared.

Remove the static declaration from mconf.o

jack.mitchell · 3 Jul 2012 at 16:50

If all else fails then I've built the module against a more recent kernel - chances are it will fail but you don't know until you try.

https://www.dropbox.com/s/60d5xwwz73hrav2/ext3.ko

PiKe · 3 Jul 2012 at 16:53

I need the related modules too please, jbd.ko mbcache.ko too if possible.

I've given up with the HH2 source, full of errors.

jack.mitchell · 3 Jul 2012 at 20:00

It didn't build those modules, I could select them and it would bring them in if required? Have you tried loading just the ext3 module, if that loads then I'll try building the others tomorrow.

I would be extremely suprised if it did work.

The only other way I can think of it working is if you manage to find a really old GCC mips toolchain, we're talking cica 4.0/3.4 here...

PiKe · 3 Jul 2012 at 20:03

Thankfully, I've found someone who has the files on their router!

Really can't get my head around this, and can't even begin to fathom how to statically link files so there's no library dependencies, I was wanting to play with running programs on the router but I don't think it's going to happen.

jack.mitchell · 3 Jul 2012 at 21:32

Statically linking libraries and cross compiling shouldn't be as difficult as compiling old kernels. Try cross compiling a simple program with the toolchain I linked to (or one you've found yourself) and see if the compiled program runs.

It's just a matter of sourcing the envionment-* file and then mips-*-gcc program.c and transfering the output file onto the router.