View Single Post
Posts: 115 | Thanked: 342 times | Joined on Dec 2010
#44
For zImage i unpacked (the kernel) from latest firmware.bin and i placed the zImage there.
Eh, what? Who told you to do that? Use only the 2.6.37, nothing else.

anyway the file existed on MyDocs and it is the actual reason of disaster.
It was /home/ that you mounted, not MyDocs. MyDocs is in an extra partition (p1), which you didn't mount. So you currently have that easy debian image on the 2G home partition as far as I can understand that.

And from the rest of your post, well, my recommendation stays:
Guess reflashing would be much easier for you...


And it overall looks like you messed up your maemo installation by executing commands you don't understand, which you shouldn't do. So you learned it the hard way I guess...

How can i avoid this?
mount - n /dev/mmcblk0p2 /dev/pts/
You lack basic Linux knowledge(no offense), I don't want to teach you the basics, as rescueOS assumes you are familiar with them. If you are not, you simply shouldn't use it IMO. I admit, it is not the most user friendly piece of software, but that's how it is. Nobody can be blamed for that and unless some volunteer appears to make some things easier, it will stay this way.

From what I can tell, you copied some (easy) debian image to /home/user/MyDocs/, but the MyDocs pratition wasn't mounted (which means your N900 was most likely already messed up prior to that anyway). So it wasn't p1, but p2 you wrote that image to, which MAYBE filled up p2(=/home), which might be the reason it doesn't boot, but it is only a guess...


But I think this is what you wanna read now.
 

The Following 3 Users Say Thank You to NIN101 For This Useful Post: