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

Thank you Fonz for the reply!

Well if it doesn't work it doesn't work. However, I am more than willing to act as a guinea pig for making a version of reloaded for the 321.

I am no expert of course, only been messing with Linux for a month now, but I can read, and follow instructions, so if someone takes the time to walk me through the process of extracting a working kernel, and compiling the reloaded program specifically for the 321 I would gladly do it so that it could be included in the fsck package for future use.

I am assuming the compilation part should be the easier, and I might just be able to read up on that front here at the forums, and the extraction of the kernel being a bit more tricky. But then again, I don't have any idea, really

Any takers?

Wow, I never expected this to be easy, but this is really hard. I know the last thing you need is a noob asking silly questions, and I told myself that I will get as far as I possibly can - it's good learning -, but after reading the linked thread a thousand times (thanks for digging it up Fonz), and a ton of others here on the forum, and googling the topic, I seem to be stuck at some basic questions... It's been a while sine I felt this helpless with computers

I understand that to compile a kernel module, I need the source of the kernel I am running, in this case 2.6.22.7, which I got.  I also have the .config from the GPL'd kernel source from D-Links site, but I don't think I need that yet.

My initial idea was to compile the reloaded source against the kernel on the DNS itself, but I am not so sure anymore it is possible. Is it possible to do it with ffpbuildenv or will I have to set up a crosscompile environment with the DLink supplied toolchain etc? I can't seem to find the answer to this anywhere...

So I guess I don't have much to show for countless sleepless nights spent poring over Linux tutorials, forums etc I know. Thank you for any insights in advance.

Hi Fonz, I thought I'd give a quick status update on how far I got, and ask for further pointers.

1) Saved the source of the 2.6.22.7 kernel and the .config of the older GPLd kernel on the DNS
2) Read all of the links you gave and a ton of other links, and guessed that I'd spend at least a week or two trying to set up a cross compile environment (only background in XP, so I'd need to figure out virtual machines, and a real distro, and then setting up the actual environment).
3) Did a make oldconfig. This took me a day or so to realize... I took all the default answers to the extra config options after reading them which was 'no' 99% of the time.
4) Did a make dep clean zImage. I guess dep wasn't needed. After 1h 20m the kernel compiled, so it wasn't bad at all. Actually a lot better than the full day or so I had expected. And I walked away learning about the very useful 'screen' utility.
5) Took out the 'CROSS_COMPILE=${FUN_TARGET}-' part from the reloaded utility's make file as I was going to compile on the box itself, and did a make. Reloaded.ko compiled fine.

So now I have a compiled 2.6.22.7 kernel with 'factory D-Link settings', and a reloaded module compiled for it. I haven't had the guts to try to load the 2.6.22.7 kernel that I made to try out if reloaded works, but I guess the worst that will happen is that I have to reboot the DNS321, right?

I'm guessing that none of the zImages that you supplied with fsck would work for me (although again, I was too afraid to try), so what are the .config options that I need to use to build such a kernel image for the DNS321?

Again, I am very very appreciative of all the help you have given me so far!

Edit: I guess I need to get my hands on an initrd... can I extract that somehow from running system?

Last edited by szidomingo (2010-03-13 05:53:47)

Sorry, it took me a while to try what you said, Fonz. I got a little distracted, and then summer rolled around, and now it's 7 months later

So I got the initramfs.gz you have on your website, and modified the no-bash-reload.sh script so that it uses egiga0 (that is what appears in the DNS-321's dmesg), and ran the script with the 2.6.22.7 kernel that I previously compiled (I did check and CONFIG_IP_PNP was enabled, so I didn't have to compile again).

I didn't work, but at least I didn't lose any of the data on the disc.

I don't know if it helps or not but here is what happened, after which the DNS-321 just stayed in limbo, with the lights on, but not answering any pings.

./no-bash-reload_egiga.sh zImage-2.6.22.7
kernel:   /mnt/HD_a2/reloaded/zImage-2.6.22.7
cmdline:  console=ttyS0,115200 ip=192.168.1.50::192.168.1.1:255.255.255.0:DNS-321:egiga0:none
machtype: 1542
+ sync
+ mount -o remount -r /mnt/HD_a2
mount: mounting /dev/sda2 on /mnt/HD_a2 failed: Device or resource busy
+ mount -o remount -r /mnt/HD_a4
+ mount -o remount -r -a
mount: mounting rootfs on / failed: Invalid argument
mount: mounting /dev/root on / failed: No such file or directory
+ mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (rw)
proc on /proc type proc (rw)
/dev/loop0 on /sys/crfs type squashfs (ro)
/dev/sda2 on /mnt/HD_a2 type ext3 (rw,data=ordered,usrquota,grpquota)
/dev/sda4 on /mnt/HD_a4 type ext3 (ro,data=ordered)
none on /proc/bus/usb type usbfs (rw)
devpts on /dev/pts type devpts (rw)
+ sync
+ sleep 1
+ insmod /mnt/HD_a2/reloaded/reloaded-2.6.22.7.ko machtype=1542 kernel=/mnt/HD_a2/reloaded/zImage-2.6.22.7 initrd=/mnt/HD_a2/reloaded/initramfs.gz cmdline=console=ttyS0,115200 ip=192.168.1.50::192.168.1.1:255.255.255.0:DNS-321:egiga0:none

After this a simple cable pull, and the DNS-321 was back in working order.

Any ideas which way I should try to be going from here? Any ideas for me?