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

Ok, yesterday i had another interesting progress.

I was able to load the kernel and ramdisk from the netboot.img provided by debian.

The installation works quite well, but after reboot, i got again the bad crc error from the kernel check of uboot.

the clue was while booting the debian, it hangs on the usb device detection.
then i thought, maybe to disconnected my serial cable. And that was the trick, the machine booted up, i plugged in my serial cable again and i could get into the installation. During the installation, the debian installer said, he had flashed the kernel to the memory. but i guess there went something wrong again.
because, as i said, after rebooting the uboot hangs on "bad crc checksum" kernel message.

I will try further after work in 2-3 hours.
My next try will be, to load the kernel and try to boot over nfs, and then flash the md2 and md3 block manually with dd.
i hope this will work, otherwise i guess the flash memory is broken or something like this. i can not understand why this happened, but if the nfs method will not work, i guess i have to give up. too bad, that the debian installer didnt flash the thing right, i spend much effort in this, after installing one hour or more, the reboot hangs again, very disappointing...

any ideas, what else i can do, are really really welcome!

bye

Last edited by phlipmode (2009-12-16 13:22:26)

Hey all,

i just want to close that thread, as it should be.

i want to inform all of you, that my CH3SNAS is working again! Yes, and even with Debian!
6 Weeks of reading, soldering, buying, programming and hacking, and its working

i had several problems at least, i will try to put them together here in a few sentence, maybe someone else will need this help.

here we go:

1.
if you are connected over serial cable and watching the boot sequence with kermit or something like this, it show alwas BAD-CRC even if the kernel is flashed correct. That is quite strange, i dont know why, but if im not connected to the device, its booting quite well, if the kernel was flashed correct. Conclusion: Always unplug the serial cable after you flashed a kernel or ramdisk to the flashrom.

2.
if the boot sequence is stopping anywhere, mostly with EHCI HostController error message, try to unplug the serial cable and plug it in again. The device will boot further! had this several times!

3.
using the "dd" command to write the kernel and the ramdisk to the device, didnt worked for me. i dont know why, but i had to do it with "cat"

cat uKernel > /dev/mtdblock2
cat uRamdisk > /dev/mtdblock3
poweroff

After that, i powered off the device, unplugged my serial cable and power it on again! Voilà!

Before all this worked, i had to do it like i described aboved.

connect with kermit

device: loadb r

kermeit: send uRamdisk

after that, copy the ramdisk from the saved placed to a different place in the flash. i did always like this:

cp 00100000 03000000 0015343*
*the lenght of the ramdisk in bytes, you can see this after you send the Ramdisk or Kernel to the device. the length is shown by the device before erasing the flash

than do this with the kernel again

cp 00100000 02000000 0232302*
again, the thrid number is the length in bytes!

after that try to boot up with

bootm 0200000 0300000.

after that, you can user busybox to use wget and get the ramdisk and kernel again, to cat it to the flashrom.
or you can mount a nfs directory where the files are saved. both worked for me.

i recommend the netboot.img from debian it self. its a nice ramdisk with everything you need for!



thats it for now!

mine is working again. YEAH! Hope yours too if not, feel free to contact me.

bye
phlipmode