Error! For 2.4 some backports exists: i.e. from IODATA for the LANDISK (SH4 platform) and kernel 2.4.21 (not 2.4.28 like MFB100, but without structural differencies): http://eggplant.ddo.jp/www/pukiwiki/index.php?plugin=attach&refer=kexec%20support%20in%20LinuxSH&openfile=linux-2.4.21-iodata-kexec.patch (if link don't work, please, search for "linux-2.4.21-iodata-kexec.patch" in Google)

I know the huge effort to update this patch, but will be very interesting for support/boot new kernels/distributions without troubles! Original firmware will be only like PCBIOS: a simple boot initializator and launcher.

Pagano: You can recompile the FULL kernel? We can do SAFE testing of patchs for the Kernel?

Hi Sanecyclist,

Your proposal of use Debian Etch distribution is a good solution in the beginning, but let me to explain my proposal:

Today several devices are using an embedded version of Linux (uclinux, busybox, etc.), and some of us like to use these devices at maximum. If you think in the concept of the PCBios or a Bootloader, you can view the great opportunity of a Linux kernel with kexec support:

In a PC:  ROM-BIOS -> BootManager -> Operative System (Linux)
In an Embedded device: Bootloader -> Linux Kernel (original from vendor)

My suggestion:

Bootloader -> Linux kernel with kexec (patched from original) -> New Linux Kernel

This approach is safe, because you don’t touch the bootloader (you need JTAG access if you try to do) and the only change in the original firmware is the kexec support (don’t care about anything different of the kernel). After that you can do what you like!

FYI the PS3 from Sony is using this safe approach (look for KBoot) for boot Linux. The only requirement from the provider is the kexec support in the kernel, nothing more (moreover, with kexec support the original kernel don’t need to be Linux!). In this way you can view the original firmware as a “second stage” bootloader. For sure the boot is slow, but safe in any way.

This can be added not only to MFB100, but to any type of devices (OpenWRT’s, Oleg’s, OpenSlug’s, etc.).

In return to your post: the backport of kexec patch for kernel 2.4.29 is very promising (MFB100 is using 2.4.28), but anyone can recompile the current kernel of the firmware? Pagano can you help us?

Great find, jamon. I'll give that a try as well. This could completely open up the device without risk of bricking it, and as you explained, use the firmware Linux only as a fancy bootloader.

Hi guys!

Now I'm doing some testing using an Xbox-1 (IS i386 compatible, USES 2.4.x series kernel, and DON'T have PCBIOS), because with the MFB100 the testing is very slow.

My results:

* TKM (Two-Kernel Monte): don't work as version from FTP "monte-0.3.0-2.4.x.tar.gz", but compiles with some tweaks. I'll try with the last code from CVS server in http://sourceforge.net/projects/monte/ (the last "oficial" page).

* kexec: searching for the "working" patches from Planet-lab in the kernel 2.4 (see about Xenoboot in http://www.cl.cam.ac.uk/research/srg/netos/xeno/xenoboot/

* TKM-mips: Some other version of kmonte (for TiVO/ mips platform) : http://www.numbski.net/downloads/monte-mips-0.1.tar.gz. As you can view for porting TKM to MFB100 we need to recode the bootstrap inside it (perhaps from the bootloader source).

More ideas? Pagano: Can you recompile the full kernel and use it?

Has anyone else been able to download the new firmware recently? I get either 0b files or 404 pages or no links to download.

Confused! I am.

Now why didnt i try that!?
 

lol right lets try getting this on. Oh i've been having problems using a SWSAPUR-5400 with my cable modem.

All i want is to share my internet wirelessly! Is that to much to ask!?

When
hitting the "DOWNLOAD" area selction the following is sent
http://www.macsat.com/macsat/component/option,com_docman/Itemid,63/

and instead of the download area
just gettin'
Fatal error: Class 'dmConfig' not found in /customers/macsat.com/macsat.com/httpd.www/macsat/administrator/components/com_docman/classes/DOCMAN_config.class.php on line 88


Can You fix that ?

Tnx, Udo

Since two full days on vacation ? 
What a workers paradise You live in.... 
Holiday for me means, that I have to use my Pc at home instead the equipment in the company.

But thanks for the reply, I'll keep patient.

 Another question:
Around the forum i can find lots of pieces for getting the modified image running on my WAP-0007.
But I'm still missing the (golden) hint to avoid building a ramdisk at boot time and turn onn swapping to my HHD.

Can somebody give me a hint ?

I'm using a WAP-0007 with a 160 GB HDD
divided into 3 Partitions
hda1 used as system area about 10 GB
hda2 is a 120 MB swap area
hda3 is the rest of the disk for Data storage
1. I've upgraded my WAP using the original Image from Level-One called WAP-0007(R4.00b8)_2006-10-02.BIN transferred via TFTP
2. the upgrade via WEB-Interface to "upgrade.img" from the version 3
3. then I untared using tar -xzf /mnt/D/UsbFS-3.tar.gz to /mnt/C  the USB-filesystem

After reboot i was able to use the upgraded busybox but i'm stuck on getting rid of the ramdisk
# df
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hda1                   7931       1128         6803  14% /root/ramroot
/dev/hda1              9612252     12800    9111172   0% /
/dev/hda1              9612252     12800    9111172   0% /mnt/C
/dev/hda3          144081608       4776 136757896   0% /mnt/D
/dev/hda1              9612252     12800    9111172   0% /share/USB
/dev/hda1              9612252     12800    9111172   0% /share/C
/dev/hda3           144081608      4776 136757896   0% /share/D

Any advise on this ?

Thanks, Udo