Custom 1.0.7.8 firmware is ready to download

Finally a custom version of the 1.0.7.8 Asus release is ready to release. This version continues many of the philosophies of the 1.0.4.6 version, but has some additional features that make it much more usable out of the box.

For those of you using the previous 1.0.4.6 version, this one is not 100% backwards compatible, though it's pretty close. Read the documentation carefully and you should be OK.

The documentation and firmware image are on back2basic's web site here:

http://wl700g.homelinux.net/drupal/?q=node/134

I would like to thank him for his generous offer to host everything.

- K.C.

P.S. As usual, this software is provided "AS IS". Use at your own risk.

So, umm, dumb question.. What's the login & pw for the telnet? :) I tried my router's login & pw for the web interface but it didn't work.

nvm, figured it out.. ok, next dumb question.. does the rc.local go in the same spot? My old one was still hanging around but it doesn't look
like it was executed, since watchdog was still running when it all came up, and I had it set to kill watchdog.

Also is there anyway to tell that I'm actually running your 1.0.7.8 and somehow didn't get the stock version?
I remember when I was tinkering with the source a while back I found where the version number was stored and was able to change it..
don't remember if it actually reflected it when I flashed the firmware though. :)

ok, and just to err on the side of paranoia, when I downloaded your image, the website named it something totally random, which made
finding it on my hard drive interesting. :) So I honestly don't know which version I actually downloaded, but from what I read of your
documentation and what I'm seeing on this end, I think I'm running the stock 1.0.7.8. SSH isn't working, and my telnet login is the good
ol' root with no password.. my web interface l/p isn't working.

I install kfirge firmeware follow
http://wl700g.homelinux.net/drupal/?q=node/83

but in step 1.3 Installing optware packages topic 5

Add the following line to /opt/etc/ipkg.conf with the newly installed busybox version of vi:
# src optware http://ipkg.nslu2-linux.org/feeds/op...g/cross/stable

is'show "src: not found" did I miss anything ?

That my stupid -_-""
Now I add src optware http://ipkg.nslu2-linux.org/feeds/op...g/cross/stable
to ipkg.conf

but when I update ipkg
ipkg install uclibc-opt busybox ipkg-opt wget

It show syntex error like this

[u@h W]ipkg -force-overwrite install uclibc-opt busybox ipkg-opt wget
Package uclibc-opt (0.9.28-12) installed in /opt/ is up to date.
Package busybox (1.9.0-1) installed in /opt/ is up to date.
Package ipkg-opt (0.99.163-9) installed in /opt/ is up to date.
Package wget (1.10.2-4) installed in /opt/ is up to date.
Configuring busybox-links
syntax error
syntax error
syntax error
syntax error
syntax error
.....
....
syntax error
syntax error
postinst script returned status 255
ERROR: busybox-links.postinst returned 255
Nothing to be done
Successfully terminated.

What I should do ?

Wooow, cool! Can't wait to flash it! :-) Thanx, kfurge!!!!!!

D.

Quote:

---

Originally Posted by ice-cool

syntax error
syntax error
postinst script returned status 255
ERROR: busybox-links.postinst returned 255
Nothing to be done
Successfully terminated.

---

Read the FAQ section. You need to insure that the environment variable KCSHELL is set to /opt/bin/bash so that the postinstall scripts will run properly:

export KCSHELL=/opt/bin/bash

Logging in as root via ssh will do this, as will a "sudo -l bash" if logged in as the admin user.

Quote:

---

Originally Posted by fireflash

ok, and just to err on the side of paranoia, when I downloaded your image, the website named it something totally random, which made finding it on my hard drive interesting. :) .

---

Interesting... Perhaps back2basic can chime in here! Tonight I'll mirror it to the wl500g.info site which should preserve the filename.

To make sure you got the right file, confirm the md5 sum.

Quote:

---

Originally Posted by fireflash

SSH isn't working, and my telnet login is the good ol' root with no password.. my web interface l/p isn't working.

---

Both of these features are configured via rc.local. If you're running your old rc.local, then the scripts which fix the password file are probably not being executed.

When migrating from 1.0.4.6, I'd recommend temporarily renaming /shares/MYVOLUME1/opt to /shares/MYVOLUME1/opt.DO_NOT_LOAD so that the /opt filesystem from the firmware image is executed.

After that, combine the new 1.0.7.8 rc.local with your old 1.0.4.6 rc.local, rename opt.DO_NOT_LOAD back to opt, and reboot the router.

- K.C.

Quote:

---

Originally Posted by fireflash

ok, next dumb question.. does the rc.local go in the same spot? My old one was still hanging around but it doesn't look like it was executed, since watchdog was still running when it all came up, and I had it set to kill watchdog.

---

Regarding rc.local, please read the documentation. I specifically addressed this point.

It's OK to keep watchdog running now. Asus fixed the problem where it kept the HDD spinning. Also, it's been released as source again, that's how I confirmed the original problem has been fixed.

Quote:

---

Originally Posted by fireflash

Also is there anyway to tell that I'm actually running your 1.0.7.8 and somehow didn't get the stock version?

---

You'll be able to tell by poking around the filesystems. If you have an /bin/kcsh then it's running the custom firmware.

- K.C.

Quote:

---

Originally Posted by kfurge

Read the FAQ section. You need to insure that the environment variable KCSHELL is set to /opt/bin/bash so that the postinstall scripts will run properly:

export KCSHELL=/opt/bin/bash

Logging in as root via ssh will do this, as will a "sudo -l bash" if logged in as the admin user.

- K.C.

---

Thank for your help.
I have read the FAQ but due to I'm a newbie. So, I don't understand. T-T
How ever I try this
[u@h W]sudo -l bash
sudo: not found

but I think I login as root ( because I use login name as root )
so. I try this follow your suggestion
export KCSHELL=/opt/bin/bash
and
ipkg install uclibc-opt busybox ipkg-opt wget

Package uclibc-opt (0.9.28-12) installed in /opt/ is up to date.
Package busybox (1.9.0-1) installed in /opt/ is up to date.
Package ipkg-opt (0.99.163-9) installed in /opt/ is up to date.
Package wget (1.10.2-4) installed in /opt/ is up to date.
Configuring busybox-links
head: error while loading shared libraries: head: symbol vprintf, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
update-alternatives: Error: cannot register alternative [ to /opt/bin/[ since it is already registered to
.......
head: error while loading shared libraries: head: symbol vprintf, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
update-alternatives: Error: cannot register alternative cal to /opt/bin/cal since it is already registered to
xsystem: ERROR: Child process died due to signal 2: `//opt/lib/ipkg/info/busybox-links.postinst configure'
postinst script returned status -1
ERROR: busybox-links.postinst returned -1
Nothing to be done
Successfully terminated.

Could You help me to fix this ?
PS. I'm just a user. And have a litle knowledge about linux T-T

[QUOTE=kfurge;79281]Regarding rc.local, please read the documentation. I specifically addressed this point.

It's OK to keep watchdog running now. Asus fixed the problem where it kept the HDD spinning. Also, it's been released as source again, that's how I confirmed the original problem has been fixed.

Quote:

---

Originally Posted by fireflash

Also is there anyway to tell that I'm actually running your 1.0.7.8 and somehow didn't get the stock version?
[/QUOTE4]

You'll be able to tell by poking around the filesystems. If you have an /opt/bin/kcsh then it's running the custom firmware.

- K.C.

---

Yeah sorry about that, I did notice after I posted that you did put instructions up.. It was late :)

I looked, kcsh isn't there.. But based on your next response, it may not have written the /shares/MYVOLUME1/opt because it already existed. I'll rename my /opt to something else and reflash it and see if that gets it working right.

Also, when I did flash the new firmware, my router didn't reboot like it was suppose to. I had to tell it to reboot.. very strange, but everything fired back up with the new firmware.

UPDATE: I renamed my /shares/MYVOLUME1/opt and reflashed the firmware. This time it took off without a hitch, rebooted, and now my web l&p is working for logging into the telnet session, and SSH works. Still don't see kcsh in /opt though, but I did compare the md5 and they match, so it's definitely the right .nas file.

Ok, so after more tinkering, I noticed it doesn't seem to like my old /shares/MYVOLUME1/opt directory being there.. or any /opt directory being there for that matter. If I rename the old one and reboot the router, dropbear works and everything seems to be working as it should, but as soon as I either rename the old opt dir back to opt, dropbear doesn't work, and the telnet login is back to root, no password. Even if I create a blank /opt directory there, it still doesn't work right (figured it was a nice test). I even renamed my old rc.local to rc.local.OLD in case it was trying to run it. So I guess I should start with a fresh /shares/MYVOLUME1/opt directory, since it symlinks the /opt directory to that if it sees it.. I guess I need to go back over your old tutorials for your 1.0.4.6 firmware and rebuild it..?

Sorry to be a pain, life of an early adopter. :)


UPDATE THE UPDATE: RTFM, that's all I gotta say... I followed your instructions, copied /opt to /shares/MYVOLUME1, rebooted, and everything seems to be working wonderfully. There was definitely something about my old /shares/MYVOLUME1/opt directory it didn't like (probably has a lot to do with it missing your rc.local script lol), but I wasn't attached to it, so I just replaced it and it's working great.

Question though.. if I start changing anything in the web interface, is it going to re-write the passwd file like it use to? making it so I'd have to reboot the router (or at the very least attempt to run your fix scripts) to get it working right?

Kudos on a job well done sir! Nice to see someone has the skills and the desire to help us make this little white brick into something a bit more useful :)

Quote:

---

Originally Posted by ice-cool

Thank for your help.
I have read the FAQ but due to I'm a newbie. So, I don't understand. T-T
How ever I try this
[u@h W]sudo -l bash
sudo: not found

but I think I login as root ( because I use login name as root )
so. I try this follow your suggestion
export KCSHELL=/opt/bin/bash

---

OK, I think your problem is that you must already have a /shares/MYVOLUME1/opt directory. If this directory is present, the firmware assumes you want to use it in place of the static firmware /opt directory.

Follow the directions I gave to fireflash in this thread and read the documentation about upgrading from 1.0.4.6 to 1.0.7.8.

- K.C.

P.S. Along with KCSHELL, you'll have to define and export LD_LIBRARY_PATH and a reasonable PATH. This is illustrated in the /.profile on the router.

Quote:

---

Originally Posted by fireflash

Still don't see kcsh in /opt though, but I did compare the md5 and they match, so it's definitely the right .nas file.

---

My bad. I meant to say /bin/sh

Quote:

---

Originally Posted by fireflash

Question though.. if I start changing anything in the web interface, is it going to re-write the passwd file like it use to?

---

From what I've been able to tell, the passwd file is only updated upon reboot or when a user gets changed/updated in UBSA windows filesharing mode. In either case, I've not yet experienced the passwd file being completely rewritten without rc.local also being called.

- K.C.

Quote:

---

Originally Posted by kfurge

Interesting... Perhaps back2basic can chime in here! Tonight I'll mirror it to the wl500g.info site which should preserve the filename.

To make sure you got the right file, confirm the md5 sum.

- K.C.

---

Somehow all the files downloaded from wl700g.homelinux.net are renamed as 'drupal' maybe there is a fix for this,I'm gonne check it out.

Quote:

---

Originally Posted by ice-cool

I install kfirge firmeware follow
http://wl700g.homelinux.net/drupal/?q=node/83

but in step 1.3 Installing optware packages topic 5

---

Wrong version! The step 1.3 you're referring to is for the super old 1.0.4.6 version, not 1.0.7.8. For 1.0.7.8, you need to be here:

http://wl700ge.hezik.nl/ - http://wl700g.homelinux.net/drupal/?q=node/134

- K.C.

Quote:

---

Originally Posted by back2basic

Somehow all the files downloaded from wl700g.homelinux.net are renamed as 'drupal' maybe there is a fix for this,I'm gonne check it out.

---

I fixed that all files should be displayed with the proper name.

Was mt-dappd updated, or is that still on the to-do list?

Quote:

---

Originally Posted by fireflash

Was mt-dappd updated, or is that still on the to-do list?

---

Unless Asus did it (they updated samba, I didn't check mt-daapd), it's still on the to-do list.

- K.C.

Just flashed my white box to 1078 kfurge. The funny thing is - I thought it didn't work. I used web interface and selected the file, and then screen went blank, URL was something on flashing progress, but page said "done." and nothing was happening. PC wasn't transfering anything, and I waited and waited, had another cigarette.... nothing.

The internet was working, though, so I said, no go. I said i'll restart the router and try again, but router wouldn't react to nothing. power button just didn't do anything.

So after a while I gave up, and unplugged the power cable. After the damn thing booted, I normally logged on to web interface and... it said 1.0.7.8 !!! (was 1.0.4.6)

Cool! :-)

Now... how does one add .torrent files to MLDonkey???? :-)

Mine did something similar. When I flashed it using the web interface, it went through the motions, then said it was going to reboot, but it didn't. So I just let it sit there and spin it's wheels, then it came back to the web interface like nothing had happened.. So I had to make it reboot, after that, it was all good.

To add torrents to mldonkey, go to the mldonkey interface page, and copy and paste the .torrent url into the DL box.

Just updated to 1078. All worked fine via the web interface - none of the oddities reported above.

Couple of things: if i reboot the unit (from the web interface, cos the asus is physically upstairs and i'm lazy) and telnet in, i can work for a bit (with different prompt) before connection is dropped/kicked after say 30secs. then when i log back in, the login prompt is different; all good tho!

Done as said: renamed old opt dir /shares/MYVOLUME1/opt to something else, and copied the 'new' /opt in place to start afresh from. However,
doing 'ipkg update' gives me the following, and i can't add any new packages afterwards (e.g. optware-devel etc)

Code:

---

$ ipkg update
Downloading http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable/Packages.gz
wget: missing URL
Usage: wget [OPTION]... [URL]...

Try `wget --help' for more options.
An error ocurred, return value: 1.
Collected errors:
ipkg_download: ERROR: Command failed with return value 1: `wget    -q -P  http://ipkg.nslu2-linux.org/feeds/optware/oleg/cross/stable/Packages.gz'

---

also, whenever i try to do 'sudo bash' i get something about /opt/etc/sudoers being owned by gid 42000 should be 0.

but i love the whole 'press copy button to use default boot' - great solution to mucked up rc.local, and finally a fix for /bin/sh -> /opt/bin/bash. great stuff.

UPDATE: ok ok ok...so my asus couldn't actually access the wider world (was reset to gateway mode not access point which is how i normally have it). so ipkg thing fixed, but the sudo oddity still there...

Yeeeeehaaaaa big thx, cheers everyone!!! :D

Quote:

---

Originally Posted by neil

also, whenever i try to do 'sudo bash' i get something about /opt/etc/sudoers being owned by gid 42000 should be 0.

---

Something must have happened when the file got copied... The 42000 GID is indicative of an Asus made user. Maybe you didn't copy it as root? The firmware image has the UID:GID for all files set to 0:0.

Fixing is easy with chgrp, though other sudo related files are probably also broken.

- K.C.

Quote:

---

Originally Posted by neil

Couple of things: if i reboot the unit (from the web interface, cos the asus is physically upstairs and i'm lazy) and telnet in, i can work for a bit (with different prompt) before connection is dropped/kicked after say 30secs. then when i log back in, the login prompt is different; all good tho!

---

The first shell is started by the Asus code, but is completely insecure without the firewall enabled (though not having the firewall enabled is suicidal anyway). So, in rc.local I kill the Asus telnet and start my own to close the hole. That's when you get kicked off. This is a good FAQ item.

- K.C.

One small thing: i've taken my asus to work, so i can mess with it during lunchtime to get everything sorted; this has inadvertently led me to set the IP address to a duff value that means i can no longer access it.

so i hold down reset for 10 seconds, which i thought just reset the settings, then reboot - i can access it again (via 192.168.1.1) but the firmware has been reset to 1.0.4.6 -> which obviously means reflashing all over again...is there a better way to just reset to factory settings, without reverting the flash??

Quote:

---

Originally Posted by kfurge

OK, I think your problem is that you must already have a /shares/MYVOLUME1/opt directory. If this directory is present, the firmware assumes you want to use it in place of the static firmware /opt directory.

Follow the directions I gave to fireflash in this thread and read the documentation about upgrading from 1.0.4.6 to 1.0.7.8.

- K.C.

P.S. Along with KCSHELL, you'll have to define and export LD_LIBRARY_PATH and a reasonable PATH. This is illustrated in the /.profile on the router.

---

I try to start at first step again by
remove all file in /shares/MYVOLUME1
except MYSHARE1,__share_MYSHARE1_vars.txt,bin,etc

And I re-flashing via web interface with WL700gE_kc_1078_01.nas
after that I press reset button for 10 second
and run EZsetup again

Everything seem ok.
I can telnet to router as Admin and can Sudo bash -l to gain root
I start MLDONKEY follow http://wl700g.homelinux.net/drupal/?q=node/190
But I can't open MLDONKEY web interface http://192.168.1.1:4080
and MYSHARE in ASUS web interface ( I can't access share, And I can't create new share )

Am I do a big mistake ? (remove all file in /shares/MYVOLUME1 )
T-T
Can I fix it ?

Quote:

---

Originally Posted by ice-cool

I
Am I do a big mistake ? (remove all file in /shares/MYVOLUME1 )

---

Erasing everything in /shares/MYVOLUME1 was probably not the best idea... I'm not sure how to recover from that.

Regarding MLDonkey, the startup output is in /tmp/mldonkey.out. It'll show you why it's not starting. I suspect it's because you don't have a /shares/MYVOLUME1/MYSHARE1 any more.

- K.C.

Quote:

---

Originally Posted by neil

so i hold down reset for 10 seconds, which i thought just reset the settings, then reboot - i can access it again (via 192.168.1.1) but the firmware has been reset to 1.0.4.6 -> which obviously means reflashing all over again...is there a better way to just reset to factory settings, without reverting the flash??

---

I've run across this once or twice in the past. For sure your flash is not being reverted. There's not enough room in it to store two copies. The .nas file consists of two parts, the flash part and a filesystem part. Only the kernel and a very small filesystem reside in the flash. There are two cramfs partitions (I use the term loosely since they're not truly partitions) on the routers HDD which hold the "firmware" contained within the filesystem segment. The router seems to toggle back and forth between them when a .nas file is flashed into it.

I believe you're experiencing a failsafe built into the flash copy of "init" to protect against corruption or failure to one of the cramfs partitions on the HDD. If the reset button is pressed, I think it forces the router to boot from a previously good partition.

I would suspect that flashing the router twice, with a successful boot in between, would completely flush out any old images.

Can you experiment with this concept a bit and try to figure out its behavior?

- K.C.

Quote:

---

Originally Posted by kfurge

I've run across this once or twice in the past. For sure your flash is not being reverted. There's not enough room in it to store two copies. The .nas file consists of two parts, the flash part and a filesystem part. Only the kernel and a very small filesystem reside in the flash. There are two cramfs partitions (I use the term loosely since they're not truly partitions) on the routers HDD which hold the "firmware" contained within the filesystem segment. The router seems to toggle back and forth between them when a .nas file is flashed into it.

I believe you're experiencing a failsafe built into the flash copy of "init" to protect against corruption or failure to one of the cramfs partitions on the HDD. If the reset button is pressed, I think it forces the router to boot from a previously good partition.

I would suspect that flashing the router twice, with a successful boot in between, would completely flush out any old images.

Can you experiment with this concept a bit and try to figure out its behavior?

- K.C.

---

will do...

(and then its time to get cups working again; latest svn 1.4.x fixes the bug that's in the current optware package, so i'll try and compile that one rather than reverting back to the 1.2.12 that i had working under old firmware)

Just flashed your firmware, and had no problems at all after deleting my old opt directory (Was filled with a lot of crap anyways :-)).

Seems to work very impressive, MLDonkey worked out of the box, same with SSH. Thank you very much for this impressive firmware, you have really improved Asus default firmware :)

Hi,

Quote:

---

Originally Posted by kfurge

When migrating from 1.0.4.6, I'd recommend temporarily renaming /shares/MYVOLUME1/opt to /shares/MYVOLUME1/opt.DO_NOT_LOAD so that the /opt filesystem from the firmware image is executed.

After that, combine the new 1.0.7.8 rc.local with your old 1.0.4.6 rc.local, rename opt.DO_NOT_LOAD back to opt, and reboot the router.
- K.C.

---

I assume your image contains a 'default' /opt that contains /opt/etc/rc.local. I also assume /.profile is there 'somewhere'. I can't find it. But I did the minimal thing: copied my rc.local to /opt/etc. That is to my /opt, because I ran your previous firmware.
Now, I like to do what you suggest. But how? /shares/MYVOLUME1/opt is mounted to /opt and always busy (mv: cannot rename 'opt': Device or resource busy).
Should I first rename rc.local to something not functional? But will your rc.local than take over (after reboot), and again mount /shares/MYVOLUME1/opt ?

Sorry, I'm a bit :confused:
Marc

Quote:

---

Originally Posted by mumsoft

I assume your image contains a 'default' /opt that contains /opt/etc/rc.local. I also assume /.profile is there 'somewhere'. I can't find it. But I did the minimal thing: copied my rc.local to /opt/etc. That is to my /opt, because I ran your previous firmware.
Now, I like to do what you suggest. But how? /shares/MYVOLUME1/opt is mounted to /opt and always busy (mv: cannot rename 'opt': Device or resource busy).
Should I first rename rc.local to something not functional? But will your rc.local than take over (after reboot), and again mount /shares/MYVOLUME1/opt ?

---

Sorry, my mistake on the .profile, I set this up a while ago... The default bash profile is in /opt/etc/profile.

Regarding your /opt problem...

The firmware looks for /shares/MYVOLUME1/opt and if it's there, then it mounts /shares/MYVOLUME1/opt over the top of the /opt that's already there and attempts to execute /opt/etc/rc.local. Which rc.local gets executed depends on whether or not /shares/MYVOLUME1/opt exists or not.

To insure the flashed copy of /opt is active, you need to rename /shares/MYVOLUME1/opt (not /opt) to something else:

cd /shares/MYVOLUME1
mv opt opt.DO_NOT_LOAD
reboot

When the router boots again, what's in /opt is the flashed filesystem. Do what you need to do to the /shares/MYVOLUME1/opt.DO_NOT_LOAD/etc/rc.local. After that, repeat the above steps, except step #2 which becomes "mv opt.DO_NOT_LOAD opt" to put everything back.

Lather, rinse, repeat until everything works...

- K.C.

Quote:

---

Originally Posted by Henrikh

Just flashed your firmware, and had no problems at all after deleting my old opt directory (Was filled with a lot of crap anyways :-)).

Seems to work very impressive, MLDonkey worked out of the box, same with SSH. Thank you very much for this impressive firmware, you have really improved Asus default firmware :)

---

Yeah! Finally success for someone!

- K.C.

Quote:

---

Originally Posted by neil

will do...

(and then its time to get cups working again; latest svn 1.4.x fixes the bug that's in the current optware package, so i'll try and compile that one rather than reverting back to the 1.2.12 that i had working under old firmware)

---

How broken is the optware CUPS? That's been my primary (read lazy) way of adding features to the router. Is it unusable?

If so, I guess I'll have to build and install it on the router.

- K.C.

time to nit-pick. :) Something keeps accessing the hard drive, so the drive won't power down. MLDonkey is disabled, and so is the media server.. Not much is running on it except what it needs to do it's job. I could try and kill watchdog just for giggles and see what it does.. Any suggestions?

thanks everyone and most specially to kfurge for all your effort...

anyway, i am getting this warning.. any thoughts?

i just installed this custom firmware version 1.0.7.8 from version 2.0.0.7 via web upload.. at first nothing happened because my box doesnt reboot by itself nor even by the power button in front.. yeah, i know thats really weird.. so i then reset the box totally... and after the reboot, it reverted back to custom firmware version 1.0.4.6... i didnt know where it came from.. anyway, i tried installing the custom firmware version 1.0.7.8 via web upload and everything looks ok... except that i could not log in to the telnet using admin account so i login as root...

i read somewhere you mentioned that i kindoff store the previous firmware as sort of backup or something maybe thats why it reverted back to 1.0.4.6 from 2.0.0.7...

then i noticed that mldonkey is not starting up on its own via the rc.local script.. so i just start it myself after i login via telnet and check the logs and get this messege...

WARNING: Directory /shares/MYVOLUME1/MYSHARE1/.mldonkey is full, MLDonkey shuts down

does this means i dont have enough free space?

Code:

---

[root@(none) MYSHARE1]$ df -h
Filesystem                Size      Used Available Use% Mounted on
rootfs                  67.1M    67.1M        0 100% /
/dev/root                1.3M      1.3M        0 100% /mnt
/dev/ide/host2/bus0/target0/lun0/part2
                        67.1M    67.1M        0 100% /

---

if its is and so... how do i clean up and free up some space? HELP! ='(

Quote:

---

Originally Posted by fireflash

time to nit-pick. :) Something keeps accessing the hard drive, so the drive won't power down. MLDonkey is disabled, and so is the media server.. Not much is running on it except what it needs to do it's job. I could try and kill watchdog just for giggles and see what it does.. Any suggestions?

---

It's not watchdog. Try disabling more applications. You can speed up the trial and error process by issuing the following command from a terminal window:

hdparm -y /dev/ide/host2/bus0/target0/lun0/disc

Keep disabling applications and doing this until the drive stays spun down for at least 60 seconds.

FWIW, the drive does not completely spin down with this firmware. It enters a low RPM mode which reduces drive wear and tear at spin up.

- K.C.

Quote:

---

Originally Posted by exbliss

WARNING: Directory /shares/MYVOLUME1/MYSHARE1/.mldonkey is full, MLDonkey shuts down

---

You have some strange stuff going on. Your primary data partition on the HDD is not there! You should have a /dev/se/2 mounted on /shares/MYVOLUME1.

My output looks like:

[root@WL700gE cups]$ df -h
Filesystem Size Used Available Use% Mounted on
rootfs 67.1M 67.1M 0 100% /
/dev/root 1.3M 1.3M 0 100% /mnt
/dev/ide/host2/bus0/target0/lun0/part2 67.1M 67.1M 0 100% /
/dev/se/2 232.3G 170.6M 232.1G 0% /shares/MYVOLUME1
/dev/se/2 232.3G 170.6M 232.1G 0% /opt


I'd recommend completely purging the router of the 2.0.xx settings by pressing the recessed reset button while powering up the router. You may have to reflash the 1.0.7.8 image after this.

- K.C.

Quote:

---

Originally Posted by kfurge

You have some strange stuff going on. Your primary data partition on the HDD is not there! You should have a /dev/se/2 mounted on /shares/MYVOLUME1.

I'd recommend completely purging the router of the 2.0.xx settings by pressing the recessed reset button while powering up the router. You may have to reflash the 1.0.7.8 image after this.

- K.C.

---

Oh my god! now that you mentioned, yeah i realized its missing.. in the web it says unmounted and there isnt any option to mount it... in the explorer, \\192.168.1.1 doesnt have the share forlder...

what have i done?!?!

i have already reset it a couple of times already and reflash it again and its still not mounting... is there anything i can mount this manually? :confused:

Quote:

---

Originally Posted by kfurge

It's not watchdog. Try disabling more applications. You can speed up the trial and error process by issuing the following command from a terminal window:

hdparm -y /dev/ide/host2/bus0/target0/lun0/disc

Keep disabling applications and doing this until the drive stays spun down for at least 60 seconds.

FWIW, the drive does not completely spin down with this firmware. It enters a low RPM mode which reduces drive wear and tear at spin up.

- K.C.

---

if I disable anything else the poor thing will stop working! :) I'll see what else I can kill, but it's running just enough to do what it needs to do, nothing special.

Edit: Here's what I've got running:

Quote:

---

PID Uid VSZ Stat Command
1 root 9116 S init
2 root SW< [keventd]
3 root SW [events/0]
4 root SWN [ksoftirqd_CPU0]
5 root SW [kswapd]
6 root SW [bdflush]
7 root SW [kupdated]
8 root SW [mtdblockd]
9 root SW [khubd]
14 root SW< [mdrecoveryd]
74 root SW< [ksed]
75 root SW [ksechanged]
77 root SW [gpio_out_pulse]
78 root SW [button_notify_u]
106 root SW< [raid1d]
111 root SW< [raid1d]
120 root SW [kreiserfsd]
195 root 3600 S syslogd -R 255.255.255.255
197 root 3552 S klogd
199 root 11040 S httpd 80 y
201 root 11020 S httpd 8080 share_browsing
207 root 4908 S upnp -D -L br0 -W eth0
208 root 4708 S nas /tmp/nas.lan.conf /tmp/nas.lan.pid lan
217 root 1880 S udhcpd /tmp/udhcpd_lan.conf
221 root 2188 S dnsmasq -i br0 -r /tmp/resolv.conf
228 root 8520 S /usr/local/samba/sbin/smbd
241 root 1856 S udhcpc -i eth0 -p /var/run/udhcpc.pid -s /tmp/udhcpc -H Routerhosen
242 root 6792 S /usr/local/samba/sbin/nmbd
267 root 8520 S /usr/local/samba/sbin/smbd
275 root 5824 S waveservermain
277 root 5824 S rcamdmain
278 root 4808 S infosvr br0
289 root 5824 S usbcopymain
512 root 2164 S utelnetd -d -i br0
519 root 1364 S /opt/sbin/dropbear
4235 root 1444 R /opt/sbin/dropbear
4236 admin 2108 S -bash
4237 root 2108 S bash
4242 root 1792 R ps

---

Am not experienced with linux, anyway i tried to upgrade to kfurge version.
After plain installation I didn't have the new telnet interface and I was not able to run mldonkey (changes do not commit to nvram, "nvram show" seems to be unchanged).
I was playing with rc.local for a while, so i had copy rc.local form /opt/etc to /shares/MYVOLUME1/opt/etc and BIG MISTAKE I deleted rc.local from /opt/etc. After reboot I was no more able to gain login access to system trough a telnet session. Telnet has old interface and system ask for a login and a password but no name/password satisfy the request. My windows is USBA.
Please, what can I do?

Quote:

---

Originally Posted by exbliss

Oh my god! now that you mentioned, yeah i realized its missing.. in the web it says unmounted and there isnt any option to mount it... in the explorer, \\192.168.1.1 doesnt have the share forlder...

what have i done?!?!

i have already reset it a couple of times already and reflash it again and its still not mounting... is there anything i can mount this manually? :confused:

---

i did my homework and took crash course on unix 101 and... eureka! it turns outs i just had corrupted partition table.. so i just fixed with fdisk and rebooted a couple of times after reconfiguring stuff and al... and walla! everything is perfect! Thanks kfurge! :p your the best!