Re: N900 rescue OS - testing release
 

Hi,
My n900 doesn't seem to like rescueOS.
Thru ubuntu, i load rescueOS with flasher and after i type:
/rescueOS/mass-storage-enable.sh
It says:
[ 02950.651885] g_file_Storage gadget: No serial-number string provided!
[ 02950.662231] g_file_storage gadget-lun0: unable to open backing file: /dev/mmcblk1p2
modprobe: 'kernel/drivers/usb/gadget/g_file_storage_.ko' : unknown symbol in module or invalid parameter
If i type at flasher:
flasher-3.5 -k zImage -n rescueOS-initrd-0.5.3.img -l -b"rootdelay root=/dev/ram0 autostart=/rescueOS/usbnetworking-enable.sh"
My phone doesn't boot.
If instaed of zImage i replace with 2.6.37 then it boots fine.
I enter telnetd at phone.
Then in linux-pc it displays on top right [Wired Connection disconnected]
on xterm if i try to telnet at 192.168.2.15
after a long w8 it fails.
I can not even find MyDocs folder (with my things inside).
What am i doing wrong?

Re: N900 rescue OS - testing release
 

Did you mess with EMMC partitions?

Correct, if there is no kernel with "zImage" in the directory, it of course doesn't work...

Not sure what the problem here is. A wild guess: It could be the network manager...

Assuming the name of the interface is usb0, you might want to give the following a try
Because it isn't mounted.

Also note that rescueOS, unfortunately, requires at least a little basic knowledge of the linux command line.

Flashing rootfs only doesn't kill the files on MyDocs (and also not your contacts as the wiki page says). Guess reflashing would be much easier for you...
http://wiki.maemo.org/index.php?titl...ablet_firmware

Re: N900 rescue OS - testing release
 

For zImage i unpacked (the kernel) from latest firmware.bin and i placed the zImage there.


After typing the above, the msg appears on the upper right saying "Wired Network: Disconnected."
On the network manager there is a "Wired network (nokia N900)" in grey collor.

If i do them really fast i can connect
I managed to connect once. it Said on phone
login [1020]: root login on "pts/0"
the pts folder is on /dev/pts
On /dev/ are listed
mmcblk0
mmcblk0p1
mmcblk0p2
mmcblk0p3
I can only mount the mmcblk0p2, the others just gices input/output error.
So i mounted using mount - n /dev/mmcblk0p2 /dev/pts/
And after getting on /dev/pts/user/MyDocs/
There were only 1 folder and one file
the file was debian-m5-v3e.img.ext2
and the folder DCIM
anyway the file existed on MyDocs and it is the actual reason of disaster.

The problem came when i installed debian, after using the below command to expand the image size:
dd if=/dev/zero bs=1M count=1048576 >> /path/to/image.ext3

Is there a possibility that this command messed my files?


Also when i type
flasher-3.5 -k 2.6.37 -n initrd.img -l -b"rootdelay root=/dev/ram0
i usually get below a
>
How can i avoid this?

Re: N900 rescue OS - testing release
 

Eh, what? Who told you to do that? Use only the 2.6.37, nothing else.

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:


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...

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.

Re: N900 rescue OS - testing release
 

My phone after doing all this "stupid" things, booted.
And i managed to take all my files + contacts.
Thank you for your time.

Re: N900 rescue OS - testing release
 

I have a n900 which doesn't boot and needs to be flashed. I tried booting rescueOS to recover my data but failed.

It gets stuck there, not able to find my n900. Even when I do a lsusb, I am not able to see n900 in the listing.

Can you please help? Any kind of help will be appreciated.

Re: N900 rescue OS - testing release
 

Could you please add a description how to add RescueOS as entry in multiboot?
Please leave the note in the documentation.txt.

Yeah I know I should be able to figure myself after a bit of googling but it would be always nice to have it documented.
I wanted your stuff as recovery console which would be preinstalled so I wouldn't need to bother with flasher if I need some simple recovery task
I would love this as alternative to backupmenu with full-grown rescue console (which backupmenu doesn't seem to have).

Re: N900 rescue OS - testing release
 

Did you run the flasher as root?

Nah sorry... I don't use it and I have 0 need for it, therefore I am not going to install and figure out how to do that. According to my memory (which may be wrong) it depends on bootmenu. If this is the case, then it has the same problems as backupmenu(death on messed up /sbin/preinit, libc, etc.).

Then you can figure it out and also document it :-).

Re: N900 rescue OS - testing release
 

NIN101, you save my life with your rescueOS, thank you very very much.

Re: N900 rescue OS - testing release
 

@elyout: yw :-)

Anyway, I have just uploaded version 0.5.4, which adds absolutely nothing special but only increases useability a bit.

-Midnight commander has been removed because it eated too much space and wasn't really useful. I doubt someone was using it...
-After bootup it asks the user now whether he/she wants to have an ftp server activated with anonymous up/downloads everywhere, which shouldn't be a security risk because most likely you have it connected over usb networking to your machine... But this makes file transfer much more convenient as you can download files from your browser simply by visiting ftp://192.168.2.15/ or something.
It also asks whether you want to have telnetd activated and finally, whether usb networking should be set up.
Basically something that always should have been there.

Download (Use at your own risk as always ;). After all, it's still testing... )

Contributionts are still welcome. Keymaps for example because the default one isn't that optimal for most N900 with non-english keyboards.