DSM-G600, DNS-3xx and NSA-220 Hack Forum

I was looking for this for months now. I had debian with latest kernel installed, but Led's and buttons didn't work...

Thanks mate

P.S: I've installed Debian on 1GB USB to be able to put my SATA disk to sleep.
When I use hdparm daemon for this I can see after timeout my disk goes to standby only (disk is still spinning)
Do You have idea, why is it not issuing hdparm -Y ?
It appears that hdparm sends -y

Thanks for this useful daemon.

Hmmm, I agree that it doesnt work.

I have Martins latest kernel running and have compiled the script, get the "forked output" when I run it but it doesn't do anything. Not had a chance to look at it properly yet... has anyone else?

For the time being I have some tape over the LED to stop it iluminating the whole room at night as it flashes continually.

Dan

Please follow Martin Michlmayr's installation guide first:

http://www.cyrius.com/debian/orion/d-li … stall.html

After installing debian install the following kernel (it won't work with any other!) and directly apply it with dpkg -i:

- download directly to you dns323:
  wget http://merkel.debian.org/~tbm/tmp/kerne … _armel.deb
- install kernel
  dpkg -i ./linux-image-2.6.30-trunk-orion5x_2.6.30-1dns323_armel.deb
-reboot

Now you should have the latest working kernel

- now install gcc
  apt-get install gcc
- download the attached dns323d.c to your dns323
- compile the daemon
  gcc dns323d.c

- Rename a.out to dns323d and copy it to /bin or /sbin...
  (binary needs to be executable!!! and rc.local, too!)

- Put a new line to your rc.local including /bin/dns323d or /sbin/dns323d
  (Don't forget to reboot after installing)

  Pressing powerbutton for 5 secs will powerdown

  Pressing resetbutton will reboot



Sorry for the delay! Have Fun! This whole thing was created for Hardware Rev. B1 and works just fine using a
Conceptronic CH3SNAS (DNS323 REV. B1).

Currently I am trying to create the latest testing kernel (2.6.32-rc8) because it includes hardware support
for orion5x-cesar-crypto-engine (currently running on my linkstation). I think I will need help from Martin again

Last edited by balou1974 (2009-12-01 10:20:01)

---

Attachments:
dns323d.c, Size: 4,116 bytes, Downloads: 835

hi,

I've tried the script on a ch3snas and it doesn't work.

When i execute the script manually i get a "forked input message" but when  i check the running processes there is no ch3snas (the name of the script)

yes i know. i followed your instructions carefully.

the kernel that i'm currently using is  2.6.30-2-orion5x

By the way does anyone uses a web manager like webmin?

If yes please state which.

I've tried installing webmin but when setup.sh is run the installation hangs with: "Running postinstall scripts"

Does anyone have a solution?

New Kernel + new Daemon:

Kernel - http://merkel.debian.org/~tbm/tmp/kerne … _armel.deb

Daemon - see Attachment !!!!



The new Kernel is running really well!!! Try it out Marvell Cesar-Crypto is supported, too !!!

Last edited by balou1974 (2009-12-22 09:11:05)

---

Attachments:
dns323d.c, Size: 3,397 bytes, Downloads: 937

Well, did you create a startup-script for the daemon? other ways it won't start and work ... you should see entries in the syslog if it is started (and dont forget the script and daemon needs rights for execution).

Last edited by balou1974 (2010-03-13 12:58:27)

I wonder what is wrong, maybe I will write a little debug version for you to see what is wrong.
I am using it many month and it worked without any problems... maybe a different hardware revision or something like that.

ANOTHER HINT: What happens if you press the hidden reset button?

In syslog you should see:

"forked input daemon" OR "unable to fork"

and if a button is pressed you should see

"Power button pressed for 5 seconds. Executing poweroff now..." or "Softreset button pressed. Executing reboot now..."

Last edited by balou1974 (2010-03-14 01:27:51)

You may check if the input device exists on your system and all associated drivers are loaded correctly (which they should if you have the right kernel)

Try #cat /dev/input/event0 | hexdump -C
and press a button (for example the power button)

This should give you some lines of output if it works.

You can also check /sys/class/input/event0/dev which contains the device major and minor number. And also look at  /proc/bus/input/devices.

Let us see where this gets us..

Kai wrote:

If you want to actualy see a bit more sophisticated output of what the device is doing use evtest (hey, you are running debian now #apt-get install evtest ..cool isn't it)

Thanks. Looks like the evtest binary is part of the 'joystick' package in lenny.

Kai wrote:

#evtest /dev/input/event0 will list supported keys and you can test them.  (be prepared that while testing and pressing some buttons that they actualy do what they suppose to..i.e power off)

Here's what I see:

# evtest /dev/input/event0
Input driver version is 1.0.0
Input device ID: bus 0x19 vendor 0x1 product 0x1 version 0x100
Input device name: "gpio-keys"
Supported events:
  Event type 0 (Sync)
  Event type 1 (Key)
    Event code 116 (Power)
    Event code 408 (Restart)
Testing ... (interrupt to exit)
Event: time 1268925919.105836, type 1 (Key), code 408 (Restart), value 1
Event: time 1268925919.105858, -------------- Report Sync ------------
Event: time 1268925919.289475, type 1 (Key), code 408 (Restart), value 0
Event: time 1268925919.289490, -------------- Report Sync ------------

I tried both buttons (Power-116 and Restart-408) but as the text above shows, only the restart button was detected.

The restart button works of course (how else would I power on the box?) and it works with the D-Link stock firmware - so it's not a hardware issue.

This is the input config, though I can't make much of it:

# /sys/devices/platform/gpio-keys/input/input0# cat /sys/class/input/event0/dev
13:64

# cat /proc/bus/input/devices
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="gpio-keys"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/platform/gpio-keys/input/input0
U: Uniq=
H: Handlers=kbd event0
B: EV=3
B: KEY=1000000 0 0 0 0 0 0 0 0 100000 0 0 0

netventure wrote:

On this topic, how can  I get a shutdown command to power of the device? It currently doesn't power off when I give a shutdown from an ssh terminal.

Well, usualy with this kernel a simple #poweroff  will shutdown the machine and power it down. As your device seem to have issues with this the problem seem related. I think it was something about GPIO flags needed to be set in a specific way in order for the device to power down proberly (specific for the revision B - that is exactaly - plus a few other things - this kernel was patched for)

Running out of ideas what to do on your devices as I'm not very familiar with the internals of this. You might want to contact Martin Michlmayer directly - the guy who developed this and backported this patch into this kernel). He might have the right knowledge to trace down what goes wrong.

According to the kernel changelog the fix now went in one of the latest kernel revision (available in squeeze)
http://packages.debian.org/changelogs/p … /changelog

I have updated my device from lenny to squeeze and it works fine but haven't tried the latest kernel yet (but will do an report)