Firmware v1.9.2.7 CR4 [Oleg]

[elpaso]

rmdir /mnt
reboot

Once rebooted it should not mount rootfs and you should follow original instructions.

Thanks oleg, it worked perfectly

I'm now trying to install packages (gift) from unslung, but there is a libc issue:

[admin@wl /root]$ gift-setup
-sh: gift-setup: not found
[admin@wl /root]$ giftd
giftd: linked against GNU libc!

Should I install other libs to run this packages?
Are thy meant to run in chroot?

[Oleg]

Thanks oleg, it worked perfectly

I'm now trying to install packages (gift) from unslung, but there is a libc issue:

[admin@wl /root]$ gift-setup
-sh: gift-setup: not found
[admin@wl /root]$ giftd
giftd: linked against GNU libc!

Should I install other libs to run this packages?
Are thy meant to run in chroot?

Well, looks like gift build is broken then. Unslung packages are not tested at the moment. Someone should take care of this.

[hezik]

[about the gift unslung package]

Well, looks like gift build is broken then. Unslung packages are not tested at the moment. Someone should take care of this.

giftd doesnt give the 'compiled against libc' (or something like that) error anymore, however it doesn't work either. It complains about me not having run gift-setup, which is correct since gift-setup uses perl..

I have the feeling changing the gift-setup with one that doesn't use perl, or including perl as a package would do the trick.

//edit
It appears perl is not needed, and that the current gift package does contain the correct binary. All that is needed to do to get it to work after using ipkg to install it, is editing the config templates, and copying them to the proper locations.

[rwhitby]

[Edit: good to hear that gift is now working :-) Kudos to hezik.]

Just to be very clear about these Unslung packages: They were written for, and have been verified on, the Linksys NSLU2 device only. That device is an XScale (armeb) processor (as opposed to the WL500g which is mipsel), and uses Glibc (as opposed to the WL500g which uses uClibc).

"Including Perl as a package" might sound like a simple thing to do, but it took at least three months of significant effort by at least three people in parallel to get Perl compiled and working on the Linksys NSLU2 (we first had to get a native compilation environment working, and then compile all the things you need to compile perl, and then compile perl itself). It would probably take roughly the same amount of time to port it to the WL500g (if it is even possible).

So don't be surprised when a package doesn't work. And don't be surprised if reports of packages (that have not been released into the ipk feed) not working fall upon deaf ears and are not answered :-)

Also, the chance of someone else fixing a package for you is quite small. The wl500g developers will be working on those packages that they individually need, and there is no-one who's job it is to port other packages to the wl500g. We certainly don't want to distract Oleg from producing his fine firmware, so please don't expect him to do it :-)

With that all said, both Oleg and myself welcome patches to the Unslung packages to get them working for the wl500g.

-- Rod

[hezik]

[Edit: good to hear that gift is now working :-) Kudos to hezik.]

Thanks, but you're thanking the messenger, not the one who created the message :P.. I didn't do anything besides installing it :P So thanks to the unknown fool who repaired it

"Including Perl as a package" might sound like a simple thing to do, but it took at least three months of significant effort by at least three people in parallel to get Perl compiled and working on the Linksys NSLU2 (we first had to get a native compilation environment working, and then compile all the things you need to compile perl, and then compile perl itself). It would probably take roughly the same amount of time to port it to the WL500g (if it is even possible).

I didn't mean to ... eh.. 'step on' the effort needed to do such a thing (can't find the proper english term for it). I apologize if i did so.

We certainly don't want to distract Oleg from producing his fine firmware, so please don't expect him to do it :-)

Just don't tell Oleg they even exist, and chain him to his firmware development machine :P

With that all said, both Oleg and myself welcome patches to the Unslung packages to get them working for the wl500g.

Ok, I'm willing to fix the gift package so that it works immediatly after installing it. Before i do that, a question about 'unslung'. Is 'unslung' a fork of a package depot for that linksys device, with the sole purpose to be used for the asus, or is it the linksys depot itself?

[rwhitby]

I didn't mean to ... eh.. 'step on' the effort needed to do such a thing (can't find the proper english term for it). I apologize if i did so.

No need to apologise - you did not offend anyone. :-)

Just don't tell Oleg they even exist, and chain him to his firmware development machine :P

Too late - Oleg was instrumental in getting the wl500g packages started :-)

Ok, I'm willing to fix the gift package so that it works immediatly after installing it. Before i do that, a question about 'unslung'. Is 'unslung' a fork of a package depot for that linksys device, with the sole purpose to be used for the asus, or is it the linksys depot itself?

The Unslung CVS is meant to be a common source code repository for Unslung packages that started with the NSLU2 and now are designed to be able to support the WL500g too.

wl500g.dyndns.org/ipkg is Oleg's offical ipk binary repository for non-Unslung packages. wl500g.dyndns.org/unslung is Oleg's ipk binary repository for Unslung packages. ipkg.nslu2-linux.org/feeds/unslung is the nslu2-linux project's ipk binary repository for Unslung packages.

So the source code is meant to be common, but the binary download locations are separate.

-- Rod

[Oleg]

//edit
It appears perl is not needed, and that the current gift package does contain the correct binary. All that is needed to do to get it to work after using ipkg to install it, is editing the config templates, and copying them to the proper locations.

Well, great! Could you please write a wiki on how to properly configure it?

[tomilius]

*cough* I'm a little embarrassed, but so far it seems as though this firmware has worked perfectly without that darn MN-710. I still don't know why it had such a bad reaction to 1.9.2.7-based firmwares whereas the WL-138g has shown indifference.

Thanks, Oleg!

[dejay]

There is a problem with "Idle Disconnect Time" in this firmware, which wasn't in the previous firmware.

When I set the "Idle Disconnect Time" to "0" it told me that it wasn't valid or something like that (did it a few day ago and cant remember) and it wouldn't connect to the internet, but when I set it to 32 000 it started working.

Did anyone else got this error?

[mike777]

Hello,

I tried Firmware v1.9.2.7 CR4, works well except for one thing. Browsing became much slower.
I tried going back to wg01090207_WL500g_EN.trx and the problem disappeared.

Anything i could do about it? I would like to keep the costum firmware installed but not at the price of slow surfing.

[Oleg]

There is a problem with "Idle Disconnect Time" in this firmware, which wasn't in the previous firmware.

Nothing is changed if you mean 1.9.2.7-3c. Most likely this due to your settings.

When I set the "Idle Disconnect Time" to "0" it told me that it wasn't valid or something like that (did it a few day ago and cant remember) and it wouldn't connect to the internet, but when I set it to 32 000 it started working.

Did anyone else got this error?

Try again and if it does not work, then please post an output (using telnet session or hidden admin page) for these commands (remove your password as well):

cat /tmp/ppp/options.wan0
nvram get wan_pppoe_idletime
nvram get wan0_pppoe_idletime