Bootmenu useless (and it's MY fault) after latest Os update...
 

I have ( -well had) 2 bootable partitions for my NIT.
Today I updated my flash partition with the latest SSU without problems and when I tried it on the mmc2 partition, I got "update error" -yet i didn't do anything to fix this.

I then tried to update my bootmenu and did so successfully a couple of times yet each time I try to boot from mmc2, the tablet tries but then finally boots into flash without giving a reason ( i don't get the "booting from mmc2 failed, booting from from flash" message)

I think I messed up bad the first time I flashed the bootmenu as I tried to reflash a bootmenu.conf I saved from the pre-SSU period.

I do have a backup of the mmc2 partition but would really appreciate not having to reclone the Os or format the SD.

Any ideas of what I can do? I even tried re-installing bootmenu-installer from penguinbait!

I did search the forum thoroughly, but still haven't encountered anyone with the same problem... :(
Hope I dont get bashed for this:p

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

what did your boot menu show? Does it show any bracket bracket out your choices?

N810 or N800?

bun

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

N800.
And nope I don't get brackets around my choices.
Here are a couple of pics of what I get:

when Im boot from mmc2:
http://i284.photobucket.com/albums/l...r/CIMG2522.jpg

and the bootmenu itself:
http://i284.photobucket.com/albums/l...r/CIMG2521.jpg

What do you think bun?

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

have you tried to switch around the SD cards and see it you can boot from your cloned OS after that?

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

Just tried but wont load from the 1st partition and fails from the second. Any more advice ? :confused:

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

I don't think so but just to be sure, do I, at any point, need to mount my partition? read it somewhere on some recent thread and it put me in doubt...

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

You should boot device from flash then run fsck on the partition on the SD. After that, try to boot from the mmc again.

#sudo gainroot
#fsck /dev/mmcblk1p2 (for example ! )

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

Here what i get when I do fsck /dev/mmcblk1p1 and fsck /dev/mmcblk1p2 :

Nokia-N800-23-14:~# fsck /dev/mmcblk1p1
fsck 1.37 (21-Mar-2005)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
alleged total clusters: 1994972
malloc:Success


Nokia-N800-23-14:~# fsck /dev/mmcblk1p2
fsck 1.37 (21-Mar-2005)
e2fsck 1.37 (21-Mar-2005)
fsck.ext2: No such file or directory while trying to open /dev/mmcblk1p2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>

---> when I do e2fsck /dev/mmcblk0p2 , I get :
e2fsck 1.37 (21-Mar-2005)
/dev/mmcblk0p2: clean, 87563/430272 files, 447017/860160 blocks



even when I reboot it still won't boot from mmc2 :confused:

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

should you do e2fsck -b 8193 /dev/mmcblk1p2 instead?

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

Indeed, and here's the output of e2fsck -b 8193 /dev/mmcblk1p2:

Nokia-N800-23-14:~# e2fsck -b 8193 /dev/mmcblk1p2

e2fsck 1.37 (21-Mar-2005)
e2fsck: No such file or directory while trying to open /dev/mmcblk1p2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>



Thats bad news no? :(

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

:( bad news indeed !

time to format/clone/.......
you fat is still ok - backup that before doing any thing else.

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

how do I do that? do you know where I can get more info on what I have to do now?

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

From looking at your screenshots: Isn't the internal SD card usually listed as immc2 in the boot screen, rather than mmc2?

From Initfs bootmenu.sh
e.g. Booting from immc2 /dev/mmcblk0p2 etc?

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

i know this is desperate, but could someone who has cloned his os to his internal mmc and that is now running the lastest os upload their bootmenu.conf and bootmenu.sh please?

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

I can try, but where is it? (i just used the .deb created by penguinbait to give me my bootmenu back) so I wouldn't know where it is.

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

Here it is, this is the bootmenu straight from fanoush, without any modification, from the initfs_flasher.tgz
==============================================
# bootmenu customisation file
#
# included from bootmenu.sh after default menu is defined
# you can change some items or redefine menu completely

# timeout for automatic selection when no key is pressed
# set to -1 for no timeout (not recommended, can drain battery when device reboots unatteded)
MENU_TIMEOUT=30

# IP address for USB networking
#USB_IP=192.168.2.15

# dim screen when in menu
#/usr/sbin/dsmetest -l 1 #for OS2006/7
#/usr/sbin/dsmetest -l 3 #for OS2008, 1 turns screen completely off

# menu items
MENU_MIN=1 # first item index

#no need to redefine
#MENU_1_NAME="Internal flash"
#MENU_1_ID="flash"

MENU_2_NAME="Internal MMC card, partition 2, ext2"
MENU_2_ID="mmc2"
MENU_2_DEVICE="${INT_CARD}p2"
MENU_2_MODULES="mbcache ext2"
MENU_2_FSTYPE="ext2"
MENU_2_FSOPTIONS="noatime"
[ -d "/sys/block/${INT_CARD}/${MENU_2_DEVICE}" ] || MENU_2_NAME="(${MENU_2_NAME}) N/A"

MENU_3_NAME="External MMC card, partition 2, ext2"
MENU_3_ID="mmc3"
MENU_3_DEVICE="${EXT_CARD}p2"
MENU_3_MODULES="mbcache ext2"
MENU_3_FSTYPE="ext2"
MENU_3_FSOPTIONS="noatime"
[ -d "/sys/block/${EXT_CARD}/${MENU_3_DEVICE}" ] || MENU_3_NAME="(${MENU_3_NAME}) N/A"

MENU_4_NAME="External MMC card, partition 2, ext3"
MENU_4_ID="mmc12"
MENU_4_DEVICE="${EXT_CARD}p2"
MENU_4_MODULES="mbcache jbd ext3"
MENU_4_FSTYPE="ext3"
MENU_4_FSOPTIONS="noatime" #",data=writeback"
[ -d "/sys/block/${EXT_CARD}/${MENU_4_DEVICE}" ] || MENU_4_NAME="(${MENU_4_NAME}) N/A"

MENU_5_NAME="Power off (when not on charger)"
MENU_5_ID="off"

#last item index, change if you add/remove items
MENU_MAX=5
===========================================


Directly from fanoush bootmenu.n8x0.example.

Ok, you have to copy this into your flash, not any MMC then copy to flash. If you do copy to somewhere else, then you may, it is possible, that you may have a different bootmenu depends on which one you boot from.

Say, you edit a bootment and copy to int flash., upon seeing the bootmenu, you choose to boot from ext MMC, and now if you edit a copy of bootmenu, while you are in MMC, then this bootmenu will end up different then the first, and if this one have a mistake in typing, you will keep seeing this one, the 2nd one, the one with typo, till you choose to boot from flash again. I am sorry if this sounds too confusing ;)

So, to make a story simple, try to use fanoush bootmenu straight from the box, and see how it goes, then modify to suit your taste,

Edit: I posted the wrong one. Does not matter. Anyway, this one I made a very little change to suit my situations. This one allows N810 to boot from,

Internal flash
Internal MMC card, part 2, ext2
External MMC card, part2, ext2
External MMC card, part2, ext3
Power off

bun

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

Ladies and Gents, I've tried everything I could with my (narrow) knowledge in Linux but haven't succeeded in solving my problem. So I'm going the only thing I can still do: start all over again.

But for posterity, ill list everything I did, maybe It'll help out a fellow user at some point:
-i tried updating my bootmenu with fanoush's latest one
-i made sure I didn't have any bracket-ed out choices
-i switched around the SD cards and tried to see if I could boot from my cloned OS after that
-checked the integrity of my partitions thanks to
#sudo gainroot
#fsck /dev/mmcblk0p2
-then did:
e2fsck -b 8193 /dev/mmcblk1p2
-i also tried to use different bootmenu.conf but in vain


Anyways, today I took the decision to start back from scratch ( I -thankfully- backed up my my cloned partition!) . What really kills me is that I didn't do that for my Kde :(

Anyways, I hope no one does the same mistakes as me.

FINAL QUESTION: now that I'm going to format my mmc and clone on it my OS, is there any need for me to reflash my flash partition with Diablo in order to delete my (useless) bootmenu?

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

Hey el amir. If you do happen to have the install-tools.deb please upload it for me. I desperately need to clone my os to internal mmc

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

here you go Sachin, hope this is what you're looking for...my records show I downloaded this on 27/06/08 so its pretty much recent!

LINK to install-tools.deb

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

Thank you so much!. Hope you get what you wanted. Thanks

Re: Bootmenu useless (and it's MY fault) after latest Os update...
 

I hope so too...