Page 1 of 1

fvdw-sl-10-1 + 2.6.39.4 kernel IT WORKS!

PostPosted: Fri Dec 16, 2011 5:26 am
by bozo29
Hi fvdw,

Yesterday i upload the new image "uImage-26394-nwsp2cl-9" with new kernel and I want to say very clearly:
WORKS FLAWLESSLY. All works.
Thanks.

I would like to know though, if it is possible that in a future release to enter the "p910nd" driver (or else to perform this function), that can be used the front USB to connect a printer.

Thanks again.

Re: fvdw-sl-10-1 + 2.6.39.4 kernel IT WORKS!

PostPosted: Fri Dec 16, 2011 8:44 pm
by fvdw
Hi bozo29 and thansk for the feedback, me and Jocko appreciate this a lot.
If the p190nd is a driver that is included in the Linux vanilla kernel distribution then it is easy to compile it and include it as loadable module. I will look at it for you.

Re: fvdw-sl-10-1 + 2.6.39.4 kernel IT WORKS!

PostPosted: Fri Dec 16, 2011 10:27 pm
by bozo29
Hi, to you and Jocko,
And I apologize for Jocko's I overlooked.
My expression was wrong. P910nd is not a driver. It is a package included in OPTWARE.
Here is the correct definition: "p910nd" - A small printer daemon intended that does not spool to disk but passes the job directly to the printer."
And here is a list of all packages included in optware: http://www.dd-wrt.com/wiki/index.php/Qu ... e_packages
Until i discover you, I used my nwsp2 as a regular HDD, that's because I was totally discontent with the poor interface options and how to operate the "machine download".
So I installed Optware and Transmission on a stick attached to my router (Asus RT-N16). In fact, first I installed "Tomato USB" firmware on the router and then Optware .....
Then, I discovered that there are alternative versions of "TomatoUSB" that included Transmission.
And finally I found you and I realized that I can use for torrents nwsp2 and keep the RT-N16 for wireless routing and internet duties.

For that I thank you again.

I started to explain something and I finished telling more. Sorry.
However, You have done a great job as well as those working in alternative firmware Tomato, OpenWRT, DD-WRT and others.

Finally, I want to ask another question (I hope not become too annoying).
How can i stop my NWSP2, i mean STOP (HALT), not StandBy, because the button from interface "Shutdown server standby", in fact do a STANDBY, not shutdown.
It is not something that bothered me, but if they can stop, I would like to know how.

All the best

Bozo (NWSP2 happy user) ;)

Re: fvdw-sl-10-1 + 2.6.39.4 kernel IT WORKS!

PostPosted: Sat Dec 17, 2011 9:20 am
by moonshadow88
bozo29 wrote:Finally, I want to ask another question (I hope not become too annoying).
How can i stop my NWSP2, i mean STOP (HALT), not StandBy, because the button from interface "Shutdown server standby", in fact do a STANDBY, not shutdown.
It is not something that bothered me, but if they can stop, I would like to know how.

All the best

Bozo (NWSP2 happy user) ;)


I use the command "shutdown" via ssh

Re: fvdw-sl-10-1 + 2.6.39.4 kernel IT WORKS!

PostPosted: Sat Dec 17, 2011 9:29 am
by bozo29
Sorry to contradict you, but the shutdown command does not work.
At the shutdown command response is: "-sh: shutdown: not found"

Re: fvdw-sl-10-1 + 2.6.39.4 kernel IT WORKS!

PostPosted: Sat Dec 17, 2011 10:20 am
by moonshadow88
bozo29 wrote:Sorry to contradict you, but the shutdown command does not work.
At the shutdown command response is: "-sh: shutdown: not found"


sorry, the command is "poweroff", as root obviosly

Re: fvdw-sl-10-1 + 2.6.39.4 kernel IT WORKS!

PostPosted: Sat Dec 17, 2011 10:30 am
by fvdw
The button server shutdown standby in the webinterface performs a "poweroff" command and sets the nwsp2 that pressing the power button will start a reboot. However before doing the poweroff it stops some daemons that are running that could be writing to disk and performs a sync to write all cache to disk. If you don't stop the daemons and perform a sync then there is a risk on data loss or file corruption
So the nwsp is powered off only the bootloader is waiting for a command to start reboot.

The restart button follows the same procedure only it uses the reboot command to perform a reboot directly after shutting down.