Hi,

I have rolled a new FW (pls. make sure you have at least a b08 version, as the password for the GUI is handled different in older versions).

some of the features:

kernel 2.4.35 (inkl. ext3, iso9660, ntfs (r/w))
kernel_nfs (mnt/C autom exported)
samba 3.0.14a
BusyBox 1.7.2
cifs 1.20c
mii-tool (like ethtool)
improved Reboot/Halt (with sync, umount)

via /sbin/init compatibel with paganoV4 (supporting KamiKaze autobootfs)

BEWARE: has to be named autobootfs (long filename) on FAT devices too! (mounted as VFAT)
Forgot: if using autobootfs, new kernel needs new module directory. so before using this upgrade, make 2.4.35 as softlink to 2.4.38 in autobootfs
ln -s /lib/modules/2.4.28 /lib/modules/2.4.35

via autoexec (/mnt/C/autoexec oder /mnt/USB/USB_C/autoexec)
/etc/exports
/etc/init.d/rcS
/etc/init.d/rc.shutdown
/etc/init.d/rc.restart
can be modified according your needs.

a smb/cifs mount looks like:
mount -v -t cifs //server/share /mnt -o user=root,pass=secret,unc=\\\\server\\share

a change to 10Mbit/half duplex needs:
mii-tool -F 10baseT-HD eth1

I tried to integrate MONO but failed miserably since I couldn't find any docs or UGs on the topic of what to do for getting a runtime only for uclibc based embedded systems. Maybe someone can help?

schufti

Edit:
mke2fs and e2fsck are missing in this release
AMIT make broken again ......

New FW with latest components in these threads:
latest & last FW for old GUI
New Years special for Pearl MGB100
Source&Toolchain

Hi martin,

I don't know the price for the WAP-0007 but the similar device from ww.pearl. de/fr is 49Eur.

With 3rd party firmware it has lots of possibilities, even full debian.
All FW come with 2.4 kernel at the moment.

I use it as WLAN-client and didn't have to reboot once (only for fw changes).
Even with HD it consumes only about 5W, so it never gets more then handwarm.
There is no fan, and with original FW the hd has auto spindown.
samba config (from GUI) can be modified by "autoexec" script (on hd or usb) when using 3rd party FW. orig version 2.x, 3rd party has 3.x

schufti

Hi,

get the ones from http://www.airlive.com/support/gpl_code.shtml for the WMU-6000FS they are the most recent and complete.

schufti

Hi,

I think it is perfectly working but you tried a wrong IP. With KK-image it is 192.168.2.1 by default. KK has ssh not telnet.


schufti

Hi gus,

sorry, it looks like the latest auto* features I took over from paganov4.bin to be compatible with existing KK-solution are not compatible with paganov3 and the USBfs (see coments to files in download section).

You could try to rename autoexec to autoinit, but I think then at least the first two lines should be skipped. Maybe pagano can help making a V4 compatible autoinit for the USBfs.

OTOH, since using USBfs leaves the kernel being the only part used from the flash-fw, you might also use paganov3 as base for USBfs.

schufti

Hi gus,

1) funny it doesn't work with original lpd. would be interesting to know the difference. Is the printer detected if you look at the usb devices? what does dmesg say?

2) never tried the usbfs myself; allway trusted it was compatible with the Kamikaze autobootfs method. Did you try that,too? If it's on (V)FAT the filenames need to be max 8 char! So even with the KK autobootfs you have to rename to autoboot (maybe that will change in next release)

schufti

Hi,

I checked this yesterday with MGB100_400s3.img. Copying video and audio to the box (samba) and playing it via the uPNP server and nfs without any kernelmessage. The media was a Kingston 2GB USB Flash.

schufti

Hi,

if you are really so brave as to write a manual on how and what to mofify to get a decent upgrade.img from the AMIT sources, prepare for a lot of writing  You'll sure have my admiration !

with the KK-image loaded on a box with my upgrade-img the ssh works without a problem. So I think this is not a kernel but a dropbear config problem.

schufti

Hi samborambo,

most likely your /sbin/init is still a link to busybox.

The AMIT builscript is crap at best (like the rest they did).
To get 'your' /sbin/init working, you have to make sure it gets copied to .../romdisk/root/sbin after the "root" is built and before the fs_image is created. You have to tweak the makescript(s) a little. You can verify your results by checking .../romdisk/root/sbin/init and checking if it is a link or regular file after the upgrade.img is created.

schufti

@andy:
I guess you are using the KK-Image over autobootfs. As I mentioned before, the GUIs (original FW, KK) don't work.

I also stated that - going with autobootfs (KK-Image) - you have to do your config in the startup/config scripts (there is no NVRAM on the device).

schufti

@paranosh

do yourself a favour and get rid of that latest piece of M$ scrap ...

schufti

Hi,

1) some GUIs don't give exact version#
2) an upgrade image can't change the GUI (fs not yet reversed)
3) try to telnet into the box; if possible, you are running the upgrade version allready!

what OS are you running? I don't know tftp2 from linksys... it has to be a tftp client!

schufti

Hi,
for CHD2WLANU you don't need 'unlock' files to load paganos V4. Just upgrade to 400b7 FW from conceptronic download. If you want to load MGB100_400Sx files, you should rebrand (see wiki, dangerous stuff) your device to LevelOne  or OvisLink and load their orig 400b8/400c1 firmware.

The 'unlock' files mix up the branding of your box and you will have problems to figure out what FW to use for any recovery.

schufti

Hi,

I reccomend http://rapidshare.com/files/57042078/MGB100_400S03.img.html (latest) as it supports kernel nfs if one doesn't use the KK image.

Printserver works like shared printers I suppose (nerver tried it myself) and doesn't work with win-gdi printers.

The ipkg doesn't work because the url is wrong:
in '/etc/ipkg.conf'
it should be
http://xwrt.kicks-ass.org/xwrt/kamikaze/7.06/x86-2.6/packages

but I read that a lot of packages disappeared.

In the KK image the KK-WebIF doesn't work (and orig. WebIF doesn't affect KK). You have to make your configs to the startup/config files.

schufti

Hi!

even if you have autoboot on FAT32 it will only get mounted as FAT, so autobootfs is too long. Rename it to autoboot and magic will happen!

schufti