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

haim · 2010-12-23 11:05:21

I'm afraid Joao is on holiday until the 4th of jan or something.

I would suggest not commenting out the safety (ONCE=yes) until you are confident alt-f is booting successfully on your NAS.

You haven't set up ffp right? I'll assume not. If you do then you'll want to think about backing up your existing fun_plug file.

fun_plug and tar file should be copied to the root of you disk (Volume_1, or /mnt/HD_a2), and fun_plug permissions must be executable (chmod +x or 777 does the job).

Looking at your log it seems the free memory is not big enough, that means something is probably being loaded by the dlink firmware or ffp (if you have that set up). I had add-ons which needed removing (these could be bonjour or firefly etc) or any other service (like itunes that you disabled, or torrent or whatever), if you do have ffp then you need to go in the /ffp/start directory and chmod -x the scripts there (although leave telnet as that is useful....).

Then you want to reboot and see if it works. And reboot again as maybe memory didn't clear first time

Note that when I did this I had ffp running so had telnet access which was quite useful for permissions and looking about.

2ma2 · 2010-12-23 11:33:52

Ok thanks.
I'll give it another try.
I don't have ffp. If I decide to install ffp, is it easier to do this after alt-f or before?

haim · 2010-12-23 11:36:01

Well if alt-f is on there I think there is an install button on the admin pages, so super easy that way. Though I've never tried it

But of course the telnet access that ffp gives (as does alt-f) could be useful when getting alt-f to work if there are issues.

2ma2 · 2010-12-23 12:14:44

Hmm did not worrk this time either - there is nothiong lse to disable free memory is still 14K
Could it be because my board is A1 ?

haim · 2010-12-23 12:44:18

Supposedly rev A boards are working now, but Joao does work on a B board so it was only recently it seems things came right. Have a lot at the website http://sites.google.com/site/altfirmware/ in the issues section and the discuss forum and perhaps theres something useful, I can see there was something about the hardrive, but seems this is ok now.

knireis · 2010-12-23 20:31:08

i flashed alt-f on my ch3snas (rev B), works fine, but before flashing i removed funplug and restored factory defaults.
It is very easy to configure alt-f once flashed

2ma2 · 2010-12-24 12:40:49

Ok I won't give up till I have tried flashing, now that fun_plug did not work.
Merry Christmas

2ma2 · 2010-12-25 13:45:40

.. can't flash witout first fun_plug...
I think I'm stuck here. Any other suggestions?

MrGastoso · 2010-12-25 13:57:22

I have a fairly success with a rev A1 board, but only with B5 version, this is what ive done ultil now:

Base system is a DNS-323 Rev A1 with Dlink 1.08 fw

1.- tryed the ffp reloaded method with Alt-F-0.1B6 without success
2.- tryed the reloaded method with Alt-F-0.1B5 with full success, all alt-f pages shown and functional
2.- flashed the Alt-F-0.1B6.bin from the reloaded B5 pages, really bad idea, result in a briked black box
3.- dismantled the box and attach a serial port in the CON4 connector with an ftdi232 usb-serial converter i had lying around (very enjoyable)
4.- seen the u-boot loader and an loop of reloading process, see attach
5.- unbricked the junk box with the guides of the wiki http://dns323.kood.org/dsmg600/howto:recover
6.- flashed again the 1.08 version to get a new start and tryed the reloaded B6 now with an eye on the serial console and it show "Kernel panic - not syncing: reboot code: Out of memory"
7.- finally i have reloaded the B5 and flashed an B5.bin version, having the system fully functional and services are working as expected

definitively the B6 doesnt want to go in A1, but i havent more things to try, any ideas?

Attachments:

u-boot.txt, Size: 1,482 bytes, Downloads: 506

haim · 2010-12-25 17:10:07

One should probably make note that only hardcore clever clogs like MrGastoso can perform step number 3.

Everyone else should really avoid bricking, and flashing alt-f without being certain that the version works in the reloaded fashion.

MrGastoso, Joao would certainly be pleased to have someone with your knowledge to help getting A1 sorted out.

2ma2 · 2010-12-25 17:26:41

Thanks to MrGastoso, I am at least on Alt-f-0-1B5
I'll follow his struggles to go to B6.

nogi · 2010-12-25 21:49:59

haim wrote:
One should probably make note that only hardcore clever clogs like MrGastoso can perform step number 3.

Everyone else should really avoid bricking, and flashing alt-f without being certain that the version works in the reloaded fashion.

MrGastoso, Joao would certainly be pleased to have someone with your knowledge to help getting A1 sorted out.

As Joao is on vacation until January 4. it would be a good idea to inform the forum and /or the Alt-F group where the kernel is throwing up.
Perhaps there is somebody with enough kernel knowledge to point in the right direction.

- Norbert

MrGastoso · 2010-12-29 00:32:54

here i go again, as i said before, the problem are a hang in the kernel booting process showing "Uncompressing Linux... done, booting the kernel" and stop, ive done a series of test to try to locate the source problem

- checked out the B6 svn source and tried to do a build ( failed in the kernel patch process)
- checked out the development source ( that seems to be a B6 already) and successfull compile
- tried the default config with default options and flashed the kernel into the box, result with same hang, not much info to gather
- tried the config now with 2.6.35.9 kernel instead of 2.6.36.2, and its loads!! ( must disable crypto algoritms in the 2.6.35.9 kernel config to reduce size to avoid extrange CRC problems)
- also copied the 2.6.35.9 config and used into the 2.6.36.2 kernel to see if the issue are a config option related, but the bell doesnt ringed this time, problem reappeared

seems that the issue are related with some kernel patch, or something related, that are beyond of my knowledge ( for the moment)
i will try to do more tests with the information gathered, stay tuned

Last edited by MrGastoso (2010-12-29 00:43:23)

jcard · 2011-01-06 21:45:18

MrGastoso wrote:
I have a fairly success with a rev A1 board, but only with B5 version, this is what ive done ultil now:

Base system is a DNS-323 Rev A1 with Dlink 1.08 fw

1.- tryed the ffp reloaded method with Alt-F-0.1B6 without success
2.- tryed the reloaded method with Alt-F-0.1B5 with full success, all alt-f pages shown and functional
2.- flashed the Alt-F-0.1B6.bin from the reloaded B5 pages, really bad idea, result in a briked black box

It's the first reported bricked device with Alt-F!

But also, you fearlessly skipped all security measures I have built, starting with the announcement:

0.1B6 News: Users with an Alt-F flashed box should use the *TryIt* option in the Firmware Updater
web page before actually flashing it, as incompatibilities might happen. Its Beta!

3.- dismantled the box and attach a serial port in the CON4 connector with an ftdi232 usb-serial converter i had lying around (very enjoyable)
4.- seen the u-boot loader and an loop of reloading process, see attach
5.- unbricked the junk box with the guides of the wiki http://dns323.kood.org/dsmg600/howto:recover
6.- flashed again the 1.08 version to get a new start and tryed the reloaded B6 now with an eye on the serial console and it show "Kernel panic - not syncing: reboot code: Out of memory"

This is not B6 specific, its a "reload" issue. Sometimes it just bails out. You could disable all addons and services in the vendors firmware and try again (this is a generic advice, not specific to this post)

7.- finally i have reloaded the B5 and flashed an B5.bin version, having the system fully functional and services are working as expected

definitively the B6 doesnt want to go in A1, but i havent more things to try, any ideas?

Yes.

Now that you have a serial port and B5 working, can you please download B6 again, proceed as if flashing it but hit the "TryIt" button instead of the "FlashIt" button? Can you please post the log?

What does the "TryIt" button does in the Firmware Updater web page? It does the same thing as the FlashIt button but instead of flashing the kernel and rootfs files it puts those files in the /root directory and issues a reboot command.

The reboot/poweroff sequence does a clean shutdown as normal and at the last step it looks at the /root directory to see if a zImage and a rootfs* file exists; then, instead of effectively rebooting, it just kexec those files.
This is the fastest way of testing new kernels and rootfs, and the one I use routinely.

What is kexec? Well, fonz "reloaded" exists because kexec is not available for 2.6.12 kernels, so "reloaded" is a kind of kexec. Hmm, does this explains what kexec is? Only by analogy...

Kexec ... allows you to boot directly to a new kernel from the currently running one. In the boot sequence described above, kexec skips the entire bootloader stage (the first part) and directly jumps into the kernel that we want to boot to.

Take a look at http://en.wikipedia.org/wiki/Kexec

jcard · 2011-01-06 22:08:18

MrGastoso wrote:
here i go again, as i said before, the problem are a hang in the kernel booting process showing "Uncompressing Linux... done, booting the kernel" and stop, ive done a series of test to try to locate the source problem

- checked out the B6 svn source and tried to do a build ( failed in the kernel patch process)

I can't reproduce this. I just checkout a clean B6 svn tag, followed the wiki instructions on how to build, and building runs until the end without errors.
I then downloaded zImage and rootfs.arm.cpio-sq.lzma to the box /root, issue a reboot and it booted (kexec) OK.

- checked out the development source ( that seems to be a B6 already) and successfull compile
- tried the default config with default options and flashed the kernel into the box, result with same hang, not much info to gather
- tried the config now with 2.6.35.9 kernel instead of 2.6.36.2, and its loads!! ( must disable crypto algoritms in the 2.6.35.9 kernel config to reduce size to avoid extrange CRC problems)
- also copied the 2.6.35.9 config and used into the 2.6.36.2 kernel to see if the issue are a config option related, but the bell doesnt ringed this time, problem reappeared

seems that the issue are related with some kernel patch, or something related, that are beyond of my knowledge ( for the moment)
i will try to do more tests with the information gathered, stay tuned

The issue must be 2.6.36 specific. The method used to create the 2.6.36 config was to use the 2.6.35 kernel config and make a oldconfig. You can look at the differences bettwen the two, they are under <svn-checkout>/local/dns323/linux-2.6.3*.config

If 2.6.36 insists in not working for A1 boards I have no problem to revert to the 2.6.35 kernel, just for A1 users benefict.

Thanks for your efforts, and please try the "TryIt" method I suggested in the response to your initial post.

kashmir581 · 2011-01-08 03:22:18

I, too, am having install issues with Alt-F. The quick details to cut to the chase.

I'm running a D-Link DNS-321 with firmware 1.03.
Bought it at Tigerdirect 3 days ago.
It came with firmware 1.03 for the 321 already installed.
ffp went onto it with no issues and works great.
Kernel I'm running is Linux dlink-C0E193 2.6.22.7 #15 Mon Aug 10 17:41:46 CST 2009 armv5tejl unknown
My installation was just to "try it from the command line" which was option 3-a on the Install doc.
copied over the alt-f-01B6.tar file and fun_plug
renamed fun_plug to alt-f.sh
ran alt-f.sh and got nothing.
web page is still the same.

Failure in the reloaded log appears to be a kernel mis-match.
reloaded-2.6.22.7.ko not found, exiting

Rebooting the NAS does not change things.
deleting the entire alt-f directory tree and script and re-installing results in the same thing.

Thoughts or guidance on this would be welcome.

jay

Here's the logs of my core troubleshooting of the issue:

(note the date/time is not right (damn ntp). It's not March 20th....)

root@dlink-C0E193:/mnt/HD_a2# pwd
/mnt/HD_a2
root@dlink-C0E193:/mnt/HD_a2# ls -al
drwxrwxrwx 5 root root 4096 Mar 20 16:36 .
drwxr-xr-x 7 root root 1024 Mar 20 11:15 ..
drwx------ 2 root root 4096 Mar 20 04:42 .systemfile
drwxr-xr-x 2 root root 4096 Mar 20 16:36 alt-f
-rw-r--r-- 1 root root 40 Mar 20 16:36 alt-f-reloaded.log
-rw-rw-rw- 1 nobody 501 2480 Mar 20 17:41 alt-f.sh
drwxr-xr-x 14 root root 4096 Mar 20 15:58 ffp
-rw-r--r-- 1 root root 48207 Mar 20 16:15 ffp.log
-rwxrwxrwx 1 nobody 501 1778 Jan 7 2011 fun_plug
root@dlink-C0E193:/mnt/HD_a2# chmod a+x alt-f.sh
root@dlink-C0E193:/mnt/HD_a2# ls -al
drwxrwxrwx 5 root root 4096 Mar 20 16:36 .
drwxr-xr-x 7 root root 1024 Mar 20 11:15 ..
drwx------ 2 root root 4096 Mar 20 04:42 .systemfile
drwxr-xr-x 2 root root 4096 Mar 20 16:36 alt-f
-rw-r--r-- 1 root root 40 Mar 20 16:36 alt-f-reloaded.log
-rwxrwxrwx 1 nobody 501 2480 Mar 20 17:41 alt-f.sh
drwxr-xr-x 14 root root 4096 Mar 20 15:58 ffp
-rw-r--r-- 1 root root 48207 Mar 20 16:15 ffp.log
-rwxrwxrwx 1 nobody 501 1778 Jan 7 2011 fun_plug
root@dlink-C0E193:/mnt/HD_a2# ./alt-f.sh
root@dlink-C0E193:/mnt/HD_a2# ls -al
drwxrwxrwx 5 root root 4096 Mar 20 17:42 .
drwxr-xr-x 7 root root 1024 Mar 20 11:15 ..
drwx------ 2 root root 4096 Mar 20 04:42 .systemfile
drwxr-xr-x 2 root root 4096 Mar 20 16:36 alt-f
-rw-r--r-- 1 root root 40 Mar 20 17:42 alt-f-reloaded.log
-rwxrwxrwx 1 nobody 501 2480 Mar 20 17:41 alt-f.sh
drwxr-xr-x 14 root root 4096 Mar 20 15:58 ffp
-rw-r--r-- 1 root root 48207 Mar 20 16:15 ffp.log
-rwxrwxrwx 1 nobody 501 1778 Jan 7 2011 fun_plug
root@dlink-C0E193:/mnt/HD_a2# cat alt-f-reloaded.log
reloaded-2.6.22.7.ko not found, exiting
root@dlink-C0E193:/mnt/HD_a2# date
Mon Mar 20 17:42:23 UTC 2000
root@dlink-C0E193:/mnt/HD_a2# uname -a
Linux dlink-C0E193 2.6.22.7 #15 Mon Aug 10 17:41:46 CST 2009 armv5tejl unknown
root@dlink-C0E193:/mnt/HD_a2#

jcard · 2011-01-09 22:21:06

kashmir581 wrote:
I, too, am having install issues with Alt-F. The quick details to cut to the chase.

I'm running a D-Link DNS-321 with firmware 1.03.
Bought it at Tigerdirect 3 days ago.
It came with firmware 1.03 for the 321 already installed.
ffp went onto it with no issues and works great.
Kernel I'm running is Linux dlink-C0E193 2.6.22.7 #15 Mon Aug 10 17:41:46 CST 2009 armv5tejl unknown
My installation was just to "try it from the command line" which was option 3-a on the Install doc.
copied over the alt-f-01B6.tar file and fun_plug
renamed fun_plug to alt-f.sh
ran alt-f.sh and got nothing.
web page is still the same.

Failure in the reloaded log appears to be a kernel mis-match.
reloaded-2.6.22.7.ko not found, exiting

Rebooting the NAS does not change things.
deleting the entire alt-f directory tree and script and re-installing results in the same thing.

Thoughts or guidance on this would be welcome.

jay

Your box, a DNS-321, is not supported.

There are many unknown hardware details.
The first thing to do is to install ffp, in order to get the most possible details about the box.
After that, compile fonz reloaded for 2.6.22, in order to try to reload Alt-F.
A serial port is necessary, in order to watch the kernel log while it boots (and fails, most of the time)

That should be complemented reading Dlink modified and published kernel source (have they published it?)

If you are willing to pursue this track, and are relatively experienced with linux, I can try to help.

This applies to other dlink NAS. Most of them use the orion or kirkwood SoCs, that are supported by the kernel, so success is possible, although not guaranteed.

Last edited by jcard (2011-01-09 22:22:28)

kashmir581 · 2011-01-15 01:40:17

jcard wrote:
kashmir581 wrote:
I, too, am having install issues with Alt-F.

I'm running a D-Link DNS-321 with firmware 1.03.
Your box, a DNS-321, is not supported.

There are many unknown hardware details.
The first thing to do is to install ffp, in order to get the most possible details about the box.
After that, compile fonz reloaded for 2.6.22, in order to try to reload Alt-F.
A serial port is necessary, in order to watch the kernel log while it boots (and fails, most of the time)

That should be complemented reading Dlink modified and published kernel source (have they published it?)

If you are willing to pursue this track, and are relatively experienced with linux, I can try to help.

This applies to other dlink NAS. Most of them use the orion or kirkwood SoCs, that are supported by the kernel, so success is possible, although not guaranteed.

D*mn! I suspected as much. I got ffp working beautifully and have several extra packages and the gcc compiler on hand now. I'm a fair hand a Linux and compiling things so I'll try to compile the fonz reloaded module for 2.6.22. I've already been reading the source wikis on doing this. Regarding the Kernel sources, wouldn't you know it but they've published 2.6.12 as the source in the 1.03 firmware directory on the d-link site. (They must be using the "magic" kernel module that changes the version to 2.6.22 after you compile 2.6.12.) Regardless, this will be an interesting project. May need to ask some stupid questions about getting the environment just right, but I think I can handle most of it.

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

Announcement

#26 2010-12-23 11:05:21

Re: RE install problems

#27 2010-12-23 11:33:52

Re: RE install problems

#28 2010-12-23 11:36:01

Re: RE install problems

#29 2010-12-23 12:14:44

Re: RE install problems

#30 2010-12-23 12:44:18

Re: RE install problems

#31 2010-12-23 20:31:08

Re: RE install problems

#32 2010-12-24 12:40:49

Re: RE install problems

#33 2010-12-25 13:45:40

Re: RE install problems

#34 2010-12-25 13:57:22

Re: RE install problems

#35 2010-12-25 17:10:07

Re: RE install problems

#36 2010-12-25 17:26:41

Re: RE install problems

#37 2010-12-25 21:49:59

Re: RE install problems

haim wrote:

#38 2010-12-29 00:32:54

Re: RE install problems

#39 2011-01-06 21:45:18

Re: RE install problems

MrGastoso wrote:

#40 2011-01-06 22:08:18

Re: RE install problems

MrGastoso wrote:

#41 2011-01-08 03:22:18

Re: RE install problems

#42 2011-01-09 22:21:06

Re: RE install problems

kashmir581 wrote:

#43 2011-01-15 01:40:17

Re: RE install problems

jcard wrote:

kashmir581 wrote:

Board footer