bootmenu initfs flasher updated for OS2008

[fanoush]

Hi,

http://fanoush.wz.cz/maemo/initfs_flasher.tgz is now updated for OS2008. Seems to work with N800. Not sure about N810 but hopefully it is same.

Booting old 2007 system somehow works. So far I noticed wi-fi doesn't see any APs so you cannot connect (pretty major issue :-) and arrow keys do not work (other keys do). Otherwise it works, tried bluetooth, touchscreen, sound, video. USB may need some tweaking too due to enabled host mode, haven't tried yet.

[penguinbait]

Guess you got it done before it was released, this is one thing to make upgrading easier.

Thanks again Fanoush!!!!

[JeffElkins]

Just excellent!

I'm going to wait for the "official" release before I re-clone my SD card, but it's sure great to know all the pieces are falling into place!

[tolou]

Czech mate, man!
This would be my showstopper. Now we are resuming countdown for the OS2008 liftoff. Very soon I hope. T-???

[hns]

Thanks fanoush!

worked exactly as described. i'd love to have a dual boot tablet. do you have any idea on how to solve the wlan issue?

[maxilogan]

sorry, i don't understand a thing. Will I be able to just boot up my already cloned OS2007 and use it at all? Are the problems related to cloning the 2008OS so tha if I het 2008 internal and 2007 SD-cloned I will be able to run always a normal system?

[hns]

I have a cloned os2007 on sd card. i can now boot it, but wlan isnt working. os2008 is running fine, haven't tried cloning it yet (i think there's another thread going about that).

[pearl62]

Could OS2008 have updated the WLAN firmware?

[fanoush]

Could OS2008 have updated the WLAN firmware?
Not sure why you are asking but yes, it is very likely. They update it even with minor OS updates. However it is not permanent, firmware is loaded at runtime to WLAN chip when you connect to network so you can safely reflash older firmwares.

[fanoush]

do you have any idea on how to solve the wlan issue? Yes, several. None is easy except forgetting OS2008.

1. one can have two sets of kernel and initfs images and flash correct one from device before rebooting to another OS200x system, initfs images should be customized to allow booting from correct places.

Kernel can be extracted from firmware image or you already have customized one from other sources, correct initfs.bootmenu.jffs2 should be in initfs_flasher directory in both systems, you just copy them to another OS200x system. True that this is cumbersome and wears off initfs and kernel flash partitions but otherwise quite workable.

2. one can investigate the issue and try to backport WLAN userspace code from newer system (if available) to older one

3. solution 1 can be improved by using kexec mechanism (i.e. boot one kernel from another) and merging both initfs images and select correct part at boot time. This is the hardest one.

Looks like this time we are not lucky and newer kernel and wlan driver breaks something in older system.

[hns]

Yes, several. None is easy except forgetting OS2008.

I think I'll just go back to OS2007 for now. Thanks for your help!

[pearl62]

Not sure why you are asking but yes, it is very likely. They update it even with minor OS updates. However it is not permanent, firmware is loaded at runtime to WLAN chip when you connect to network so you can safely reflash older firmwares.

I was thinking that OS2007 may be expecting an older version of the WLAN firmware.

I am more familiar with embedded systems where the firmware may only be loaded and fixed in place once, not at runtime. Please pardon my lack of intimate knowledge of the internal software architecture of the IT...

[fanoush]

I was thinking that OS2007 may be expecting an older version of the WLAN firmware.
Yes this is true, more correctly it simply expects specific older kernel (2.6.18) with specific version of wlan driver which uses specific firmware. This means it does not work with newer kernel and driver but you can safely go back to using older kernel with older driver (and older firmware).


I am more familiar with embedded systems where the firmware may only be loaded and fixed in place once, not at runtime.
I was surprised too, but it looks like nowadays this is widely used since it is cheaper (i.e. there is no flash memory on the chip) and easier to upgrade. Also since you load specific firmware yourself, you can in theory customize your driver to specific version of the firmware and do not need to bloat it with workarounds for multiple firmwares (if you always distribute it together and it makes sense)

[pearl62]

Yes, I have seen that in newer WLAN and even Bluetooth chipsets. Do you happen to know what WLAN chipset is used in the N800/810?

[fanoush]

Google for STLC4370 (770) and STLC4550 (N800 and N810) the whole driver is called CX3110x so google for that too, it is made by Conexant and perhaps uses one of those two STLC parts.

[fanoush]

I have updated initfs_flasher for latest 1.2007.44-4 OS2008 beta for N800. Surprisingly there was change in initfs between weeks 42 and 44.

I am not sure about that slightly updated N810 one (.42-18 vs .42-19) but since week number is same it should work, anyone tried?

[roblynn]

I have updated initfs_flasher for latest 1.2007.44-4 OS2008 beta for N800. Surprisingly there was change in initfs between weeks 42 and 44.


I just tried your updated initfs_flasher with the OS2008 beta for N800. Everything went fine, except that the keys do not work when I get to the boot selection menu. This looks very much like the problem on the first few releases of OS2007 on N800.

Has anyone encountered this before?

Robert B.

[fanoush]

Everything went fine, except that the keys do not work when I get to the boot selection menu.
This happens always or only sometimes? Is it same after reboot and after power on (i.e device was off with no charger connected)? Do you hold menu key on boot or have root device set to include 'ask' and just wait for menu without touching anything?

[roblynn]

This happens always or only sometimes? Is it same after reboot and after power on (i.e device was off with no charger connected)? Do you hold menu key on boot or have root device set to include 'ask' and just wait for menu without touching anything?

So far it happens always, and it is the same after a reboot or after a power on. I use the hold menu key on boot (but only when the message appears). At that point the boot menu appears and removing the battery is the only thing I can do to recover.

I have not tried the 'ask' facility yet -- I was hoping to use the menu the same way as I was using it on OS2007.

I'll re-run the initfs setup script first (to remove the USB facility), and try it again. If that does not work, I'll give the 'ask' facility a go and report back.

Thanks!

Robert B.

[penguinbait]

Would it be possible to have bootmenu be able to boot images on mmc cards?

For example, a 1.5GB file sitting on vfat. mount the 1.5GB file as boot drive.

dd if=/dev/zero of=/media/mmc1/EXT2.img bs=1500000000 count=1

mkfs.ext2 /media/mmc1/EXT2.img

mount the file and copy the flash to it.

Would this be possible to boot from, I am not sure if it could be done because it needs to mount the vfat somewhere to have access to the file.


Fanoush? Any thoughts?

[roblynn]

Reporting back... I re-installed initfs without USB support and this did not make any difference.

I configured the 'ask' facility (ask:flash so that I don't get locked out of the defice). The keys were still locked up, but the 30 second count-down worked and the device booted from flash when it expired.

Robert B.

[fnordianslip]

No real help from me but just a note to say that I set up to boot latest 2008 beta for n800 from SD on Saturday and all seems good so far. It seems that you have to be really on the ball to catch the boot options in time, but I just hog the menu key after applying power and almost always get it ok.

The window of opportunity is pretty short though. Is there an easy way to modify the timeout and/or the default selection?

[Milhouse]

The default timeout is 30 seconds - the window of oppurtunity is plenty long IMHO. There's been a few previous posts about changing the timeout/default selection - can't recall the specific search keywords but you should be able to track them down with the search feature.

[fanoush]

The window of opportunity is pretty short though. Is there an easy way to modify the timeout and/or the default selection?
It is mentioned in README inside initfs_flasher directory and in most guides too. As root you can run
chroot /mnt/initfs cal-tool -R ask:yourdefault
where ask means to show menu everytime with no need to hold home key and yourdefult is id of your selection (flash,mmc2,...)
As for timeout in menu, again check the README

[fanoush]

I use the hold menu key on boot (but only when the message appears). At that point the boot menu appears
I see. So at least home key works which means this is not problem with kernel. Did you modify bootmenu.sh file? keys are read via evkey command with kernel device name that is different for 770 and N800/N810. On the beginning of bootmenu.sh there should be
EVNAME=event1 # default, n770
grep -q RX-34 /proc/component_version && EVNAME=event2 #n800
grep -q RX-44 /proc/component_version && EVNAME=event2 #n810
#wait 1 second for keyup event
GETKEY="evkey -u -t 1000 /dev/input/${EVNAME}"

you can debug it yourself when system is booted, as root run
chroot /mnt/initfs on the tablet an then paste lines one by one as they appear in your bootmenu.sh. it is best to do it when logged in via ssh and using clipboard on PC.
After you do it you can directly run
$GETKEY and press up or down key on keypad in one second and it should print a number. Can you verify GETKEY variable contains event2?

echo $GETKEY
evkey -u -t 1000 /dev/input/event2
If there is event1, can you post output of
cat /proc/component_version

Also if arrow keys still don't work, can you include USB recovery mode and try to press home when in menu, and escape arrow to go back, does it work?

Also if you tried to edit bootmenu.sh or it become somehow corrupted it may be easiest to redownload initfs_flasher.tgz, extract it again and reflash initfs with clean version.

[fanoush]

Would it be possible to have bootmenu be able to boot images on mmc cards?
Well yes but it would probably conflict with mounting/dismounting FAT partition by the OS and usb storage functionality so it wouldn't be pretty. Also it would be a bit complicated to set up inside initfs - there is currently no losetup command for setting up loopback device and it would need modification of not just bootmenu.sh but original Nokia's linuxrc too (which changes from time to time so I try to minimize changes there to absolute minimum). I'm not convinced this would benefit to many users and would compensate added complexity. Lets say that this is low priority and I would accept patches adding this functionality :-)

[penguinbait]

Well yes but it would probably conflict with mounting/dismounting FAT partition by the OS and usb storage functionality so it wouldn't be pretty. Also it would be a bit complicated to set up inside initfs - there is currently no losetup command for setting up loopback device and it would need modification of not just bootmenu.sh but original Nokia's linuxrc too (which changes from time to time so I try to minimize changes there to absolute minimum). I'm not convinced this would benefit to many users and would compensate added complexity. Lets say that this is low priority and I would accept patches adding this functionality :-)


Well, I guess it sounds like a big hassle. My main goal is to make it easier for 'know nothings' to boot from mmc. This is the biggest obstacle to many who want to run KDE. Turning kde into a deb makes no sense, when they still have to setup boot from mmc manually.

[fanoush]

My main goal is to make it easier for 'know nothings' to boot from mmc. This is the biggest obstacle to many who want to run KDE. Turning kde into a deb makes no sense, when they still have to setup boot from mmc manually.
I see. Maybe improving the partitioning and cloning process (i.e.porting gparted, writing some GUI wizard to run tar) would solve this too and benefit also others. But I see advantages of simply copying couple of random images to mmc and booting and testing them without any hassle. But can you make such image downloadable without copying some nokia proprietary stuff you have no right to re-distribute?

Anyway, I will look into it and see how complex it really is and what breaks in which ways with the FAT partition being locked by the image.

[fanoush]

Also I fear there will be problem with unmounting the fat partition when system booted from image shuts down or crashes. With no clean unmount it will cause data corruptions on FAT partition and/or having it read only after next boot. This will confuse those 'know nothings' a lot. Looks like can of worms.

[roblynn]

I see. So at least home key works which means this is not problem with kernel. Did you modify bootmenu.sh file? keys are read via evkey command with kernel device name that is different for 770 and N800/N810. On the beginning of bootmenu.sh there should be
EVNAME=event1 # default, n770
grep -q RX-34 /proc/component_version && EVNAME=event2 #n800
grep -q RX-44 /proc/component_version && EVNAME=event2 #n810
#wait 1 second for keyup event
GETKEY="evkey -u -t 1000 /dev/input/${EVNAME}"


The second grep line was missing from the copy of bootmenu.sh that I was using (I grabbed the file bootmenu.sh (https://garage.maemo.org/svn/bootmenu/trunk/bootmenu.sh) thinking that it was the latest and greatest). My mistake.

Once I reverted back to the original one from the package which includes a check for OS2008, it worked.

Sorry for the trouble, many thanks for the assistance!

Robert B.

[fanoush]

I see. I should commit it. I do it usually, forgot about it this time. The RX-44 line is not needed for N800 device but the filename should be different, /proc/component_version not /etc/initfs_version. The latter no longer tells what device it is since the firmware is shared between N800 and N810.

[penguinbait]

Also I fear there will be problem with unmounting the fat partition when system booted from image shuts down or crashes. With no clean unmount it will cause data corruptions on FAT partition and/or having it read only after next boot. This will confuse those 'know nothings' a lot. Looks like can of worms.


I am thinking your first thought is probably the correct one. As you say the perhaps a gui tool, or some easy way to setup boot from SD/mmc would be nice. Althoug its probably easier to script, create and clone the install process into a file on vfat than partitioning the SD cards themselves since people already have data on the often, and so many variables with card sizes. But if you can not boot it, it does ont really matter how easy it is.


For XFCE, I created a 1GB file on VFAT, but it only mounted as /usr/local giving enough space to install everything without need for them knowing how to partition. This does not seem the cleanest way though.

So I think we need a way to easily configure boot from mmc.

On the 810 if you use the internal 2GB space, this could probably be easily scripted to convert to boot from providing you dont mind erasing it.

Sorry many disjointed thoughts flying through my mind, I am just trying to spit out the relevant ones :D

Some community brainstorming is needed!!

[Peet]

I've been reading this and various other threads (and wiki entries) trying to figure out the ideal method of setting up my N800 with easy post-OS2008-install maintainability in mind.

Despite being comfortable with Linux, the methods and components people talk about sound somewhat unfamiliar. ;)

I apologize if these questions have been hashed over and over again in various threads, but I just haven't got a cohesive picture yet...

The setup I'd be interested in achieving is:

1) Using the non-user-replacable Flash (mmc?) as a glorified boot manager (like supergrub, perhaps with some useful utilities, like cloning internal SD card to external, fsck etc.).

This "#1 partition" should probably sit on wear-levelling jffs2 to guarantee long life, but in any case writing here should be very limited to protect the precious internal Flash.

2) The internal SD slot, which can be easily backed up or replaced, should contain a larger (and faster) SD card holding one or more partitions with the full OS and apps. One could have e.g. different OS versions on the first/second/third SD partitions, or perhaps different users could have their own personalized versions of OS2008 (multiboot).

The choice of partitition sizes and filesystems would depend on the user's preferences (?), but all formatting and initial install and setup (and backing up) on the (main) internal SD card could also be performed separately on a PC.

A setup wizard or Wiki/Howto explaining various strategies (wrt. intended usage and card size) and providing (semi)automated scripts could take lot of the xterm pain and fear out of this process.

3) User data could either reside on the "OS partitions" themselves (MyDocs), on a shared "data partition" (SharedDocs) on the same internal SD card, or on the external SD card the user could insert when required (automounted).


I don't know if such a setup already exists or whether it is even feasible or desirable, but from my desktop Linux user's point of view it would be more familiar and perhaps more easily maintainable than the current way which I obviously don't completely understand so please be gentle with your criticism. :p

[vormund]

I recently installed initfs flasher on my n810 and I was able to get it working and boot from the internal media card. I could only get it to work with version 1.2007.42-18 or 2008OS, I had upgraded to .42-19 but I was not able to get it working until I downgraded back to .42-18. Also when the boot menu comes up none of the keys on the n810 work so it just boots to what I have set as default (mmc2, partition 2) after the 30 secs or so count down. But other than that I'm able to boot into the internal media card on the n810 with version 1.2007.42-18 of 2008OS.

[penguinbait]

I recently installed initfs flasher on my n810 and I was able to get it working and boot from the internal media card. I could only get it to work with version 1.2007.42-18 or 2008OS, I had upgraded to .42-19 but I was not able to get it working until I downgraded back to .42-18. Also when the boot menu comes up none of the keys on the n810 work so it just boots to what I have set as default (mmc2, partition 2) after the 30 secs or so count down. But other than that I'm able to boot into the internal media card on the n810 with version 1.2007.42-18 of 2008OS.


I have not read through the every post but look at #25 in this thread, this talks about the keys, (evkey) I am not sure what levels are supported. Fanoush is 42-19 supposed to be working?

[fanoush]

I recently installed initfs flasher on my n810 and I was able to get it working and boot from the internal media card.

Thanks for your report, this is first one with real N810 :-)

I could only get it to work with version 1.2007.42-18 or 2008OS, I had upgraded to .42-19 but I was not able to get it working until I downgraded back to .42-18.

Yes, that's possible I have only tried -18 on my N800 and hoped -19 won't be so different. I'll take a look at newer N810 firmware.

Also when the boot menu comes up none of the keys on the n810 work so it just boots to what I have set as default (mmc2, partition 2) after the 30 secs or so count down.
So my guess was wrong and N810 uses different input device name or perhaps it uses different key codes. Can you help with debugging this?

As root try to run this

chroot /mnt/initfs evkey -u -t 5000 /dev/input/event2
And then press left or right arrow. Yu have 5 seconds for this. Do you see some number printed? If not, try same command but with event1 or 3 or 4 or 5 (try "ls /dev/input/event*" to see all of them). If you find right event device for keyboard, can you post key codes for four arrow keys, center key and two buttons next to display? It is even possible that display buttons will be different eventX device than the keyboard. Thanks.

[vormund]

Ok I ran that command and found that I only got key codes for event0. The n810 has event0-3 listed on mine, heres the codes I got for the keys I tried (all event0):
up: 103
right: 106
down: 108
left: 105
center key: 96
window switcher (top button next to display): 63
back (button under window switcher): 1
enter on keyboard: 28
menu key: 62

Let me know if you need any others.

[fanoush]

Thanks a lot. Keycodes are same (except center key which was 28 before) only device name differs. If you wish you can edit bootmenu.sh inside initfs_flasher and replace 2 with 0 in
grep -q RX-44 /proc/component_version && EVNAME=event2 #n810
and reflash initfs and menu keys should work. I will check -19 FW and update flasher archive.

[vormund]

Ok I'll try that and let you know how it goes.

[fanoush]

OK, I have updated initfs flasher archive. it uses event0 for N810, both enter and select keys should work for selecting menu and -19 N810 firmware should now work too (initfs version changed in -19 but otherwise linuxrc script is same as in -18). If someone tries this with N810, let me know here how it works. Thanks.

[penguinbait]

OK, I have updated initfs flasher archive. it uses event0 for N810, both enter and select keys should work for selecting menu and -19 N810 firmware should now work too (initfs version changed in -19 but otherwise linuxrc script is same as in -18). If someone tries this with N810, let me know here how it works. Thanks.


Thank you !!


Seriously, as soon as I hit post reply, I wondered why I did not just hit the Thanks button. I guess I will go do that now:D

[vormund]

OK, I have updated initfs flasher archive. it uses event0 for N810, both enter and select keys should work for selecting menu and -19 N810 firmware should now work too (initfs version changed in -19 but otherwise linuxrc script is same as in -18). If someone tries this with N810, let me know here how it works. Thanks.

I'll just upgrade mine to -19 before reflashing then and I'll let you know how it goes. Thanks for getting that done so fast.

[vormund]

Ok I updated my n810 to -19 and initfs flasher worked fine, also the keys now work on the n810 as well. However Ive found that if I have my external sd card in when booting it cant boot to the internal mmc2, partition 2 and it boots from the flash memory.

[fanoush]

However Ive found that if I have my external sd card in when booting it cant boot to the internal mmc2, partition 2 and it boots from the flash memory.
There was/is similar/same bug with N800. The problem I've seen is that when you only had card in N800 external slot, it was named /dev/mmcblk0 but with both cards or card only in internal slot the internal was mmcblk0 and external mmcblk1. You can verify that it is this bug by customizing menu via optional bootmenu.conf and creating item for both external and internal card partition 2. Then you can try to boot the external one and see whether the internal one boots. Maybe it is even this bug combined with the fact that N810 has MMC slots named differently? With N800 internal one is mmcblk0 and external mmcblk1, can you check how it it with N810?

[vormund]

There was/is similar/same bug with N800. The problem I've seen is that when you only had card in N800 external slot, it was named /dev/mmcblk0 but with both cards or card only in internal slot the internal was mmcblk0 and external mmcblk1. You can verify that it is this bug by customizing menu via optional bootmenu.conf and creating item for both external and internal card partition 2. Then you can try to boot the external one and see whether the internal one boots. Maybe it is even this bug combined with the fact that N810 has MMC slots named differently? With N800 internal one is mmcblk0 and external mmcblk1, can you check how it it with N810?

I added an option to boot from mmcblk1p2 and that worked when I had the external card in. It looks like when theres no external card the internal card is mmcblk0, and when the external card is in the internal is mmcblk1 and external is mmcblk0.

[fanoush]

Hmm, so it is same problem but card slots are switched. This is unfortunate. With N800 people rarely boot from external card with internal slot empty because internal slot is ideal for booting. Looks like with N810 mmc interfaces are switched so this bug will bite more people. What is interesting is that after the device boots the device name changes back. I remember when I booted system from external card 'df' command printed root partition being on mmcblk0p2 but FAT partition (on the same card) was named mmcblk1p1, do you see it too (if you still have FAT partition on internal card)? I am not sure where the bug is - kernel or udev or something else. Perhaps it is time to report it in Maemo bugzilla.

[vormund]

Hmm, so it is same problem but card slots are switched. This is unfortunate. With N800 people rarely boot from external card with internal slot empty because internal slot is ideal for booting. Looks like with N810 mmc interfaces are switched so this bug will bite more people. What is interesting is that after the device boots the device name changes back. I remember when I booted system from external card 'df' command printed root partition being on mmcblk0p2 but FAT partition (on the same card) was named mmcblk1p1, do you see it too (if you still have FAT partition on internal card)? I am not sure where the bug is - kernel or udev or something else. Perhaps it is time to report it in Maemo bugzilla.

Yeah I noticed that it switches back after booting because when I partitioned the internal card I partitioned and formated mmcblk0 and the external card was also in and it wasnt formated. Mines showing that I've booted from mmcblk1p2 and that my FAT partition on the internal card is mmcblk0p1, and my external card is mmcblk1p1.

[fanoush]

http://fanoush.wz.cz/maemo/#initfs is now updated for latest 2.2007.50-2
I have not tested it yet with my N800 but linuxrc script in 2.2007.50-2 is same as in OS2008 beta for N800 (1.2007.44-4) so I have just updated list of supported versions and it should work both for N800 and N810. Will try this evening.

I updated also README.txt with some info about usb network recovery mode. Nothing new, just stuff that was already said here in the forum.

[tolou]

Soo, what about a dual boot with OS2007? Is there a way to perhaps modify OS2007 kernels to the updated versions of WLAN modules to get online with OS2007 as well? Once over this obstacle I´ve no plans for going back, soo...

[ascherjim]

Hi,

http://fanoush.wz.cz/maemo/initfs_flasher.tgz is now updated for OS2008. Seems to work with N800. Not sure about N810 but hopefully it is same.


Fanoush: Rather that start a new thread at this time, I'll try to append to this thread a description of my current (quite serious!) problem.

I have had to reflash the new firmware twice now in the last 24 hours, reinstalling all my apps, etc., because after I've executed your latest initfs_flash, not only can't I boot from my trusty mmc2 clone, but trying to boot from flash then fails also. The Nokia screen comes up, I get the menu screen, then it automatically tries to reboot -- failing each time, with no ultimate success.

My initial attempts at executing initfs_flash were in fact failing with the message stating "Cannot find initfs.bootmenu.jffs2, something failed, nothing flashed." Following this, I restored my previous (2007) MyDocs/.documents directory, and then I was able to effect what I though was a successful establishing of my bootmenu. But it doesn't work, and now I'm going to have to reflash a third time! Will I have to abandon my mmc clone? Thanks and regards, Jim

[lbattraw]

I can confirm problems with the initfs flasher with the new OS2008/n800 image. I've tried it a couple times and it will never boot from the mmc card, using the default settings as before. It will fail to boot from mmc and boot from flash but then I find I can't mount anything in the second SD slot; it's like I have a n810 without the keyboard/GPS :rolleyes:

Larry

[fanoush]

Hmm, that's strange. Yesterday evening I downloaded flasher from the web to N800 with latest firmware and my bootmenu installation works fine. The only difference may be that I have my own bootmenu.conf which may override something. Will try with default bootmenu.sh with no customization. Do you use custom bootmenu.conf or copy one of examples included or have none?


My initial attempts at executing initfs_flash were in fact failing with the message stating "Cannot find initfs.bootmenu.jffs2, something failed, nothing flashed."

This looks like something serious, posting of full output (including extraction via tar) would tell more. Looks like full disk or currupted archive.



Following this, I restored my previous (2007) MyDocs/.documents directory, and then I was able to effect what I though was a successful establishing of my bootmenu.

Again full output of such "what I though was a successful establishing of my bootmenu" would say more.


But it doesn't work, and now I'm going to have to reflash a third time!


With linux flasher you can restore just initfs so your rootfs in flash (with all applications) is not touched. I think you need to add '--flash-only initfs' to flasher arguments (-f -F RX-34......bin -R) or you can first unpack firmware (flasher-3.0 -u -F RX-34...bin) and then flash just initfs.jffs2 (flasher-3.0 -n initfs.jffs2 -f) to be safe from flashing full firmware in case you make some typo with full firmware image as a parameter.


Will I have to abandon my mmc clone? Thanks and regards, Jim
No. Your clone on mmc is 2007 or 2008 system?

[fanoush]

I can confirm problems with the initfs flasher with the new OS2008/n800 image. I've tried it a couple times and it will never boot from the mmc card, using the default settings as before. It will fail to boot from mmc and boot from flash but then I find I can't mount anything in the second SD slot
Larry
Looks like different problem. So in this case boot from flash works but mmc fails. Which slot doesn't work, the one you tried to boot from? If you select first item and boot from flash directly (i.e. no mmc boot failure) then second slot works? If you restore original initfs from firmware then second slot works?

Is anyone except me actually having no problem with initfs_flasher and latest 2008 firmware?

[ascherjim]

Hmm, that's strange. Yesterday evening I downloaded flasher from the web to N800 with latest firmware and my bootmenu installation works fine. The only difference may be that I have my own bootmenu.conf which may override something. Will try with default bootmenu.sh with no customization. Do you use custom bootmenu.conf or copy one of examples included or have none?

I tried it once with my own customized bootmenu.conf and once with the default. It failed in both instances.


This looks like something serious, posting of full output (including extraction via tar) would tell more. Looks like full disk or currupted archive.

The only way I can post this is to repeat the (failing) effort, which I am understandably loathe to do.

Again full output of such "what I though was a successful establishing of my bootmenu" would say more.

Ditto, my reluctance.

With linux flasher you can restore just initfs so your rootfs in flash (with all applications) is not touched. I think you need to add '--flash-only initfs' to flasher arguments (-f -F RX-34......bin -R) or you can first unpack firmware (flasher-3.0 -u -F RX-34...bin) and then flash just initfs.jffs2 (flasher-3.0 -n initfs.jffs2 -f) to be safe from flashing full firmware in case you make some typo with full firmware image as a parameter.

This is clearly a safer way for me to proceed -- if I entirely understood it, which I don't. I'm afraid you'd have to be a bit more explicit, i.e. give me the actual code language and place of the command. Sorry.

No. Your clone on mmc is 2007 or 2008 system?

My clone is of quite recent vintage.

Many thanks and regards,

[coffeedrinker]

I successfully used the bootmenu by editing bootmenu.sh and I am using it to boot from the external slot on my n800 (/dev/mmcblk1p1).

[fnordianslip]

I followed the cloning to sd card procedure with new OS2008 image on N800 and had no probs.

[ascherjim]

Hmm, that's strange. Yesterday evening I downloaded flasher from the web to N800 with latest firmware and my bootmenu installation works fine. The only difference may be that I have my own bootmenu.conf which may override something. Will try with default bootmenu.sh with no customization. Do you use custom bootmenu.conf or copy one of examples included or have none?


This looks like something serious, posting of full output (including extraction via tar) would tell more. Looks like full disk or currupted archive.



Again full output of such "what I though was a successful establishing of my bootmenu" would say more.



With linux flasher you can restore just initfs so your rootfs in flash (with all applications) is not touched. I think you need to add '--flash-only initfs' to flasher arguments (-f -F RX-34......bin -R) or you can first unpack firmware (flasher-3.0 -u -F RX-34...bin) and then flash just initfs.jffs2 (flasher-3.0 -n initfs.jffs2 -f) to be safe from flashing full firmware in case you make some typo with full firmware image as a parameter.


No. Your clone on mmc is 2007 or 2008 system?

FANOUSH: WELL, I DECIDED TO THROW CAUTION TO THE WINDS, AND ON THE BASIS OF ALL YOUR PRIOR EXCELLENT ADVICE OVER YEARS I GAVE IT ANOTHER TRY. THIS WAS NOT STRICTLY A BLIND ROLLING OF THE DICE ON MY PART, BUT THERE WAS ONE CHANGED CIRCUMSTANCE WHICH MADE ME WILLING TO TRY AGAIN: IN MY THIRD FLASHING OF THE NEW FIRMWARE, I DID NOT RESTORE ANY FILES FROM PREVIOUSLY. I WAS THEREFORE, I FIGURED, STARTING WITH A CLEAN SLATE. (OH, THESE METAPHORS!)

ANYWAY, EVERYTHING WENT FINE AND I CAN USE MY MMC SYSTEM AGAIN. WHICH IS GREAT, IN THAT THERE ARE FEW APPLICATIONS YET AVAILABLE TO ME THROUGH SUCCESSFUL DOWNLOADING IN THE NEW FIRMWARE. AGAIN, MANY THANKS. SORRY TO HAVE TROUBLED YOU. WE MUST BE VERY CAUTIOUS (OR SELECTIVE) IN RESTORING AFTER A RE-FLASHING, WHICH WE HAVE BEEN VARIOUSLY WARNED AGAINST ELSEWHERE IN THIS FORUM

[fanoush]

This is clearly a safer way for me to proceed -- if I entirely understood it, which I don't. I'm afraid you'd have to be a bit more explicit, i.e. give me the actual code language and place of the command. Sorry.

You can flash full firmware from linux PC via
flasher-3.0 -f -F RX-34_2008SE_2.2007.50-2_PR_COMBINED_MR0_ARM.bin -R

You can flash only initfs part by adding --flash-only initfs so whole line is
flasher-3.0 --flash-only initfs -f -F RX-34_2008SE_2.2007.50-2_PR_COMBINED_MR0_ARM.bin -R

This will, restore initfs without losing any other data.

Anyway, I am happy it worked fine after all. Still, restoring backup should not affect anything. Well except when it is so large it fills whole flash leaving not enough space for initfs flasher to create initfs.bootmenu.jffs2 image.

Thanks to others for confirming that it works for them.

[ascherjim]

You can flash full firmware from linux PC via
flasher-3.0 -f -F RX-34_2008SE_2.2007.50-2_PR_COMBINED_MR0_ARM.bin -R

You can flash only initfs part by adding --flash-only initfs so whole line is
flasher-3.0 --flash-only initfs -f -F RX-34_2008SE_2.2007.50-2_PR_COMBINED_MR0_ARM.bin -R

This will, restore initfs without losing any other data.

Anyway, I am happy it worked fine after all. Still, restoring backup should not affect anything. Well except when it is so large it fills whole flash leaving not enough space for initfs flasher to create initfs.bootmenu.jffs2 image.

Thanks to others for confirming that it works for them.

Fanoush: Thanks. I will definitely save those code commands for possible future use.

There's always a slight cloud in a silver lining! My mmc clone will now not allow me to access wi-fi and the internet -- it doesn't recognize my router, and my codes are still all right -- and the directional toggles in the D-button don't work. But since I can access wi-fi all right in the main flash firmware, I'm not at this point seriously inconvenienced. Thanks again.

[fanoush]

My mmc clone will now not allow me to access wi-fi and the internet -- it doesn't recognize my router, and my codes are still all right -- and the directional toggles in the D-button don't work
Yes, this is known issue. You may check beginning of this thread for more details.

[ascherjim]

Yes, this is known issue. You may check beginning of this thread for more details.

In view of the wlan and D-button problems on the 2007 mmc clone, I think I'll give up on using it and remove it from the mmc and reformat the card to gain use of the entire mmc for file storage purposes. I think I'll retain the bootmenu, though, for possible future use if I choose to clone the present 2008 firmware if and when new firmware is released, correcting all the present bugs being detected. I may have to acquire an additional card to do so, but by then the prices will really have dropped. Thanks again.

[tolou]

Soo, what about a dual boot with OS2007? Is there a way to perhaps modify OS2007 kernels to the updated versions of WLAN modules to get online with OS2007 as well? Once over this obstacle I´ve no plans for going back, soo...

One more thought. Is the OS2008 perhaps backwards compatible and what if I were to re-install a earlier version of initsfs with a bootloader for OS2007, will the OS2008 be able to boot on that?
A long shot maybe after having read the boot issues above but might be worth a try don´t you think?

[roblynn]

Is anyone except me actually having no problem with initfs_flasher and latest 2008 firmware?

I am using your latest version, and have no problem with either OS2008beta or OS2008 clones (on a N800)

Robert B.

[FGol]

After installing init_flasher, I get the "Press Menu to activate boot menu" message for like a half a second and it immediately goes to booting from flash. No pressing of menu or any key seems to affect it. I wonder if the problem is that I upgraded the OS to Nokia's latest fix level after unpacking my N810 on Dec 30. Has anyone else experienced this kind of behavior?

hmm... iwhen removing "extra stuff" the shell text says "extracting boot menu files for initfs version osso-RX-44.2007-49..." Should that be 2008?

Thanks
Frank

[PinCushionQueen]

After installing init_flasher, I get the "Press Menu to activate boot menu" message for like a half a second and it immediately goes to booting from flash. No pressing of menu or any key seems to affect it. I wonder if the problem is that I upgraded the OS to Nokia's latest fix level after unpacking my N810 on Dec 30. Has anyone else experienced this kind of behavior?

hmm... iwhen removing "extra stuff" the shell text says "extracting boot menu files for initfs version osso-RX-44.2007-49..." Should that be 2008?

Thanks
Frank

No 2007 is correct but the newest OS is 50-2 not 49-18/19.

I've flashed my N810 after the OS2008 50-2 upgrade and the only way to get it to boot from my new clone was to add the bootmenu.conf file to the init_flasher directory and then rerun/rebuild ( # ./initfs_flash ).

There are some samples included in the init_flasher tarball for the 770 & 800. There appears to be a bug in the 810s find out more here (http://www.internettablettalk.com/forums/showthread.php?p=109055&highlight=bootmenu.conf+external#post109055).

Here's what my bootmenu.conf looks like:
# 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=3

# IP address for USB networking
USB_IP=192.168.1.2

# dim screen when in menu
#/usr/sbin/dsmetest -l 1

# 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, partition 2, ext2"
MENU_2_ID="mmc2"
MENU_2_DEVICE="mmcblk1p2"
MENU_2_MODULES="mbcache ext2"
MENU_2_FSTYPE="ext2"
MENU_2_FSOPTIONS="noatime"

MENU_3_NAME="External MMC card, partition 2, ext3"
MENU_3_ID="mmc12"
MENU_3_DEVICE="mmcblk0p2"
MENU_3_MODULES="mbcache jbd ext3"
MENU_3_FSTYPE="ext3"
MENU_3_FSOPTIONS="noatime" #",data=writeback"

MENU_4_NAME="Power off (when not on charger)"
MENU_4_ID="off"

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

[FGol]

Thank you PCQ. Yes, I had updated a /home/user/initfs_flasher/bootmenu.conf and rebuilt. This time I copied your text directly into the N810, made it the bootmenu.conf, rebuilt again, rebooted and no affect. I don't get the menu at all. I can update the message the shell puts out so I know it's running; it just doesn't seem to recognize or react to the menu button.

??

Thank you,
Frank

[fanoush]

it just doesn't seem to recognize or react to the menu button.

Yes, this is a bug and I think I know how to fix it. Sorry, it is hard to spot such bugs without having N810. Meanwhile as a workaround you can force the menu to appear everytime by running
chroot /mnt/initfs cal-tool --set-root-device ask:mmc2
as root on your tablet. The 'ask' part is important, mmc2 is preselected choice.

[fanoush]

No 2007 is correct but the newest OS is 50-2 not 49-18/19.
initfs partition has its own version numbering and it can be shared between various firmware releases so version of firmware (50-2 in this case) does not matter for initfs flasher (and is not checked). The only thing that matters is content of /mnt/initfs/etc/initfs_version.

Also the flasher should always refuse to modify unknown (newer) initfs. With every new firmware release I need to check it and see if it needs different patch or I can make an alias (soft link) to any older one.

[FGol]

Yes, this is a bug and I think I know how to fix it. Sorry, it is hard to spot such bugs without having N810. Meanwhile as a workaround you can force the menu to appear everytime by running
chroot /mnt/initfs cal-tool --set-root-device ask:mmc2
as root on your tablet. The 'ask' part is important, mmc2 is preselected choice.

Excellent -- thank you. That forces the menu and the preselected mmc2 boot. I guess moving the menubar via up and down hardware presses fails also due to the same problem as the menu key?

Thank you,
Frank

[fanoush]

I guess moving the menubar via up and down hardware presses fails also due to the same problem as the menu key?

No, D-pad arrows in menu should work. Make sure you got latest version, this was fixed recently (2 weeks?).

http://fanoush.wz.cz/maemo/initfs_flasher.tgz - 349993 bytes

[dan]

Fanoush and others,

I'm really new to this linux and I barely understand these threads about dual booting.
Can someone point me in the right direction.
I would like to have only the os2008 boot from my removable 16gb card. I don't want or need os2007. Is this possible and will all my apps and updated apps from os2008 work properly? If there is a final version of this coming i will gladly wait. Thanks, lol, Dan

[nhanquy]

Fanoush and others,

I'm really new to this linux and I barely understand these threads about dual booting.
Can someone point me in the right direction.
I would like to have only the os2008 boot from my removable 16gb card. I don't want or need os2007. Is this possible and will all my apps and updated apps from os2008 work properly? If there is a final version of this coming i will gladly wait. Thanks, lol, Dan

Dual booting means you have an option either booting from internal flash or from an SD card. In the case of the N800, the SD card is
also installed internally. It could be your new 16gb! Don't confuse
the internal flash which is very small in size and running OS in compression for space saving.

To be able dual boot you have to format the new card, create partitions on the card, put a new boot loader into flash so the Nokia can do a dual boot, and lastly clone the OS into your SD.


In order to format the card, you have to become (unix super user) root and be able to access to a command window, called xterm.

Some related links:

http://maemo.org/community/wiki/HowTo_EASILY_BecomeRoot
http://maemo.org/community/wiki/HowTo_EASILY_Boot_From_MMC_card
http://www.internettablettalk.com/forums/showthread.php?p=111975#post111975

Link you can download apps after cloning and booting from your SD:

http://www.internettablettalk.com/wiki/index.php?title=Working_2008_OS_Software

Please read more!

[Graham Cobb]

I have been bitten by the N810 device names changing with/without the removable card present but I think I have found a solution. I have put the following code at the top of my bootmenu.conf:


# Set up card names by model
# Assume 770
INT_CARD=""
EXT_CARD="mmcblk0"
if grep -q RX-34 /proc/component_version
then #N800
INT_CARD="mmcblk0"
if grep -q mmcblk1 /proc/partitions
then # Removable card present
EXT_CARD="mmcblk1"
else # Removable card not present
EXT_CARD=""
fi
fi
if grep -q RX-44 /proc/component_version
then #N810
if grep -q mmcblk1 /proc/partitions
then # Removable card present
INT_CARD="mmcblk1"
EXT_CARD="mmcblk0"
else # Removable card not present
INT_CARD="mmcblk0"
EXT_CARD=""
fi
fi


This then allows me to create entries that look like:


MENU_2_NAME="Boot internal MMC card, partiton 2, ext2"
MENU_2_ID="mmcint2"
MENU_2_DEVICE=${INT_CARD}p2
MENU_2_MODULES="mbcache ext2"
MENU_2_FSTYPE="ext2"
MENU_2_FSOPTIONS="noatime"

MENU_3_NAME="Boot removable MMC card, partiton 2, ext2"
[ -z "$EXT_CARD" ] && MENU_3_NAME="No removable card -- do not select this"
MENU_3_ID="mmcext2"
MENU_3_DEVICE=${EXT_CARD}p2
MENU_3_MODULES="mbcache ext2"
MENU_3_FSTYPE="ext2"
MENU_3_FSOPTIONS="noatime"


This has only been tested on my N810 but it works there. Would someone with an N800 like to test it as well?

Maybe Frantisek could consider adding the device name logic to the standard bootmenu.sh and we could all just use the device name variables in our bootmenu.conf?

Graham

[fanoush]

Yes, I guess I should add something like this to bootmenu.sh. I was trying to find it in kernel sources and I would rather try to fix this bug in kernel so the names are consistent but it can be done as a temporary workaround. And also having such variables could be useful so one does not need to remeber naming of the slots for various devices. I'll try to add it but I'll try to figure out slot naming from information in /sys/devices/platform/mmc...

But still this bug needs to be fixed. Once you boot from such mismatched device the system device naming is not consistent. With N800 it happens when you only have card in external slot, with N810 in internal slot. Sadly with N810 this is more likely. See output of df after you boot, you may see two partitions mounted from same card but one starting with mmcblk0 and the other with mmcblk1. This may be confusing to some (system) programs and even dangerous. Imagine e.g. formatting external card in file manager and having the other card erased by mistake. Also the usb storage functionality may be confused when trying to unmount the card when you insert usb cable.

[fanoush]

But still this bug needs to be fixed.
I have reported it here http://bugs.maemo.org/show_bug.cgi?id=2747

[Zebee]

You can flash full firmware from linux PC via
flasher-3.0 -f -F RX-34_2008SE_2.2007.50-2_PR_COMBINED_MR0_ARM.bin -R

You can flash only initfs part by adding --flash-only initfs so whole line is
flasher-3.0 --flash-only initfs -f -F RX-34_2008SE_2.2007.50-2_PR_COMBINED_MR0_ARM.bin -R

This will, restore initfs without losing any other data.



I currently have 2008 on the SD card and 2007 on internal. If I boot from SD, then wireless doesn't work as you have noted.

If I flash the initfs with 2008 as above and boot from SD card, will that work or break everything? And then when booted with SD/2008, flash with 2007 and then can boot from internal/2007? (I ask rather than trying for fear of brick...)

Is it possible to redo the initfs from the tablet itself, rather than having to flash from a PC?

Still looking for dual boot os2007/OS2008. Seems that the initfs is the key?

Zebee

[fanoush]

I currently have 2008 on the SD card and 2007 on internal. If I boot from SD, then wireless doesn't work as you have noted.

If I flash the initfs with 2008 as above and boot from SD card, will that work or break everything?

You should always have matching kernel and initfs or tablet may not boot. So if you flash initfs for OS2008 you should also flash kernel for OS2008.


Is it possible to redo the initfs from the tablet itself, rather than having to flash from a PC?

Yes, you can flash prepared initfs image from the tablet, just run initfs_flash script with existing jffs2 initfs image.This will skip the wizard and just flash the image (original or with bootmenu, doesn't matter). There should be one or two such images in initfs_flasher directory if you installed bootmenu.

If you combine this with kernel flasher you can do it in one go before rebooting to different OS200x. First flash kernel, then initfs and reboot.

[Zebee]

You should always have matching kernel and initfs or tablet may not boot. So if you flash initfs for OS2008 you should also flash kernel for OS2008.

That makes sense (and I should have thought of it, aggh!) THe kernel is /mnt/initfs/linuxrc?

So I need to have a copy of the 2007 kernel image available to 2008 and the 2008 image to 2007. Do they need to be in /mnt/initfs, or can they be elsewhere?

Yes, you can flash prepared initfs image from the tablet, just run initfs_flash script with existing jffs2 initfs image.This will skip the wizard and just flash the image (original or with bootmenu, doesn't matter). There should be one or two such images in initfs_flasher directory if you installed bootmenu.

If you combine this with kernel flasher you can do it in one go before rebooting to different OS200x. First flash kernel, then initfs and reboot.

Is there a kernel flasher for the tablet, or only one for the PC? (In my case a linux PC.) Does your initfs_flash do it?

And which initfs? Presumably it does matter if it's a 2007 or 2008 one, where are they and how do I tell the difference?

so...

1) find kernel for required OS
- be somewhere on SD card or internal
2) find initfs for required OS
- I have the backup I made on original flash, so I know where that is
3) use PC version of flasher to flash kernel
4) reboot

THe obvious pain is step 3, but initfs_flash doesn't do kernels does it?

Zebee

[Machster]

Fanoush,

Just some feedback from a relatively new user here. When I received my n800 a few weeks ago I immediately flashed to the latest release OS2008. I was surprised at the lack of memory after adding just a few applications.

I searched for a solution and found the thread for using the SD card instead of the internal flash for OS2007. Then Sunday I successfully (i.e. no errors) completed instructions posted by Millhouse using your initfs_flasher. However I have had no luck booting from the internal slot using a partitioned 16GB card. The bootmenu is installed but selecting the second partition results in a failure every time. I have repeated the installation process to no avail.

I have read here in the forums that some have had success (albeit without access to WIFI???) and some like myself that have not. It is yet unclear to me after browsing the forums that this process is successful with the n800 and OS2008. This thread makes it sound that a custom bootmenu file may need to be in the initfs_flasher folder?

[vormund]

Do you have a card in both slots? When I did this on my n810 the labels for the internal and external cards would switch when booting and then switch back after booting. To fix this I had to add an entry to the boot menu to boot from partition 2 of what would normally be the external card. This was discussed back on page 5 of this thread for more info on what to do if this is your problem. If you do have two cards in try booting with only the internal card in first to see if that works.

[qwerty12]

At the moment, I am not interested in MMC booting (I just got it yesterday, from what I see, if I want to boot a dump of OS2007, I'll have to flash back).
But the USB Network Recovery Mode does sound great (due to my habit of "bricking" things) but I am unsure if I use the default N800 config supplied (bootmenu.conf.n800.example), I will be able to still reboot into my internal flash after a 10 sec timeout? (I really don't want to brick it because I don't have a Linux install ATM and my Dad will kill me if it don't boot :\)

Thank you.

[fanoush]

But the USB Network Recovery Mode does sound great (due to my habit of "bricking" things) but I am unsure if I use the default N800 config supplied (bootmenu.conf.n800.example), I will be able to still reboot into my internal flash after a 10 sec timeout?
You don't need to add bootmenu.conf and unless you set different root device name or press menu key at boot time, there is no significant difference, the menu will be hidden and it will still boot directly from flash (no timeout, no slowdown).

[fanoush]

That makes sense (and I should have thought of it, aggh!) THe kernel is /mnt/initfs/linuxrc?

So I need to have a copy of the 2007 kernel image available to 2008 and the 2008 image to 2007. Do they need to be in /mnt/initfs, or can they be elsewhere?

If you don't use custom kernel, dafault kernel can be extracted from firmware .bin image via flasher-3.0 -u -F firmwareimagename.binGet the zImage file.

Is there a kernel flasher for the tablet, or only one for the PC?

http://fanoush.wz.cz/maemo/#kernelflasher

And which initfs? Presumably it does matter if it's a 2007 or 2008 one, where are they and how do I tell the difference?

initfs.bootmenu.jffs2 in initfs_flasher directory. This is created when you install bootmenu. You probably have two of them one in each OS200x installation. Just copy them to the other system or have both on SD card. Both initfs and kernel can be on SD but the flashers needs to be in internal flash. Then you can run something like
kernel_flasher/kernel_flash /media/mmc2/zImage-OS200x
initfs_flasher/initfs_flash /media/mmc2/initfs.OS200x.jffs2
and let it reboot and select matching OS200x item for current kernel and initfs version.

Unfortunately you need to confirm flashing of both parts. In next version of flashers I will add -f option to disable the confirmation.

[fanoush]

Then Sunday I successfully (i.e. no errors) completed instructions posted by Millhouse using your initfs_flasher. However I have had no luck booting from the internal slot using a partitioned 16GB card. The bootmenu is installed but selecting the second partition results in a failure every time. I have repeated the installation process to no avail.
Yes, people reported similar issues also with 8GB cards. I got 8GB card few days ago, partitioned via sfdisk on device and cloned it via tar and have no problem so I am not sure what is wrong here, see http://www.internettablettalk.com/forums/showthread.php?p=131682#post131682
I think either partitioning or cloning went somehow wrong for you.

[qwerty12]

You don't need to add bootmenu.conf and unless you set different root device name or press menu key at boot time, there is no significant difference, the menu will be hidden and it will still boot directly from flash (no timeout, no slowdown).


w00t, thank you :). I flashed it fine and it works great. I just have one small question, the extra unneeded stuff that is removed, is there any way to get it back (i.e reflash image again)? I'm not bothered if you cant, but I am just interested out of curiosity.

Thank you for the flasher and all your help.

[fanoush]

w00t, thank you :). I flashed it fine and it works great.
So you actually logged in over usb networking?

I just have one small question, the extra unneeded stuff that is removed, is there any way to get it back (i.e reflash image again)?
Either you flash the backup initfs.orig.jffs2 image created by initfs_flasher (if you answered yes to backup question) or you can extract initfs image from firmware .bin image.

[qwerty12]

So you actually logged in over usb networking?


I tried but Putty keeps timing out. I don't know if I have the drivers installed properly or if my computer hates me (I chose to install the dropbear and the ssh server). But I will try on a linux machine sometime.


Either you flash the backup initfs.orig.jffs2 image created by initfs_flasher (if you answered yes to backup question) or you can extract initfs image from firmware .bin image.

Ok, thank you :)

[Machster]

Do you have a card in both slots? When I did this on my n810 the labels for the internal and external cards would switch when booting and then switch back after booting. To fix this I had to add an entry to the boot menu to boot from partition 2 of what would normally be the external card. This was discussed back on page 5 of this thread for more info on what to do if this is your problem. If you do have two cards in try booting with only the internal card in first to see if that works.

Thanks for the suggestion, vormund. I read about that situation but I don't think that's the problem here. It will not boot from SD if there is a card in the external slot or not.

[Machster]

Yes, people reported similar issues also with 8GB cards. I got 8GB card few days ago, partitioned via sfdisk on device and cloned it via tar and have no problem so I am not sure what is wrong here, see http://www.internettablettalk.com/forums/showthread.php?p=131682#post131682
I think either partitioning or cloning went somehow wrong for you.
Actually reformatted and partitioned now about four times (just to make sure). Each time cloned without errors. Card and file system look as they should when viewed on my Mac too.

[kernelpanic]

Fanoush,
I think I know what's up with the mmc's switching. The device nodes for the mmc's are reversed between the initfs and the root fs!

If I do-
# cd /mnt/initfs/dev && ls -l mmcblk*

I get-
brw------- 1 root root 254, 0 ..... mmcblk0
...
brw------- 1 root root 254, 8 ..... mmcblk1

if I do-
# cd /dev && ls -l mmcblk*

I get-
brw------- 1 root root 254, 8 ..... mmcblk0
...
brw------- 1 root root 254, 0 ..... mmcblk1
...

The nodes are reversed. mmcblk0 is 254, 8 and mmcblk1 is 254, 0. I'm going to make the initfs /dev entries match the root filesystem and see if it bricks my tablet. I'll post back in a bit

kernelpanic ;-)

[kernelpanic]

o.k. closer...

I extracted the initfs.osso-RX-44.2007-49.tgz file from initfs_flasher and rewrote all of the /dev/mmcblk* nodes to match the root fs. Then I recreated the tgz file and ran initfs_flash.

Success! (mostly)

Now can boot to mmc and df shows the correct devices for the root filesystem (mmcblk1p2) and the external mmc (mmcblk1p1) (Yes, I'm booting to the external card. I'm hacking this thing a lot right now.. If I wear out the flash, I'd like to be able to replace it.)

However, df now shows that the /mnt/initfs device is /dev/mmcblk1p2 (or if booted from flash /dev/mtdblock4), and not /dev/root??? But /etc/mtab correctly shows /mnt/initfs as /dev/root in either case...

Interesting eh?

kernelpanic

As /dev/root is mounted read-only, I'm not too worried about it...

[Machster]

Fanoush,

Just some feedback from a relatively new user here. When I received my n800 a few weeks ago I immediately flashed to the latest release OS2008. I was surprised at the lack of memory after adding just a few applications.

I searched for a solution and found the thread for using the SD card instead of the internal flash for OS2007. Then Sunday I successfully (i.e. no errors) completed instructions posted by Millhouse using your initfs_flasher. However I have had no luck booting from the internal slot using a partitioned 16GB card. The bootmenu is installed but selecting the second partition results in a failure every time. I have repeated the installation process to no avail.

I have read here in the forums that some have had success (albeit without access to WIFI???) and some like myself that have not. It is yet unclear to me after browsing the forums that this process is successful with the n800 and OS2008. This thread makes it sound that a custom bootmenu file may need to be in the initfs_flasher folder?

Update:

I have now also attempted to clone the OS to a 1GB Kingmax card. During the cloning process outlined by Millhouse many errors are being generated when taring the ./usr directory. These errors include "Cannot open: No such file or directory" or "Cannot open: Input Output error". If I let xterm run it takes about 12 hours for step 4 to stop. After that it won't complete step 5 and the file system on the second partition is corrupt. Xterm is also unresponsive at this point.

I decided to reflash OS2008 and start from scratch. But after repeating all the steps again, including installing the bootmenu, the results have been exactly the same. The new cloned 16GB will not boot and the seasoned 1GB card is still generating errors during cloning.

[mbfrog]

Trying to boot from MMC with a N810 and the latest OS2008 2.2007.50-2 I came across a few issues like mmcblk0 and mmcblk1 being swapped after booting (like vormund earlier). I finally got it right by swapping the devices in the initfs and also managed to prevent the root file system from being mounted over USB. A few pointers here (http://tabletoid.blogspot.com/2008/01/finally-got-clean-way-to-boot-from.html).

For the MMC swapping problem, It may be a good idea to add specific initfs patches in the initfs flasher, but I do not know if this applies only to the N810, to OS2008 2.2007.50-2 or both...

[kernelpanic]

I finally got it right by swapping the devices in the initfs and also managed to prevent the root file system from being mounted over USB. A few pointers here (http://tabletoid.blogspot.com/2008/01/finally-got-clean-way-to-boot-from.html).

For the MMC swapping problem, It may be a good idea to add specific initfs patches in the initfs flasher, but I do not know if this applies only to the N810, to OS2008 2.2007.50-2 or both...

To solve the mmc swapping issue, I just changed the device nodes in the appropriate *tgz file for my initfs in the initfs_flasher package. (Added nodes for the device and partitions 1 and 2 and changed the nodes for partitions 3 and 4.) That way if I reflash later I don't need to redo the hack.

kernelpanic

p.s.- thanks for pointing out the osso-usb-mass-storage-enable.sh hack. I'd been looking for a way to disable the root fs mounting over usb...

[Machster]

Trying to boot from MMC with a N810 and the latest OS2008 2.2007.50-2 I came across a few issues like mmcblk0 and mmcblk1 being swapped after booting (like vormund earlier). I finally got it right by swapping the devices in the initfs and also managed to prevent the root file system from being mounted over USB. A few pointers here (http://tabletoid.blogspot.com/2008/01/finally-got-clean-way-to-boot-from.html).

For the MMC swapping problem, It may be a good idea to add specific initfs patches in the initfs flasher, but I do not know if this applies only to the N810, to OS2008 2.2007.50-2 or both...

Using your tips page I've verified that the MMC swapping problem is not affecting my n800. You used the Maemo wiki (http://maemo.org/community/wiki/howto_easily_boot_from_mmc_card/) to clone your card. Those instructions are only intended for 2006, 2007. Did you follow the one for OS2007?

[geneven]

The problem has certainly affected me. I tried the instructions given in the Millhouse thread and the Nuclear instructions, as recommended on the tablet hacker site. I will try the fixes mentioned above.

[fanoush]

I finally got it right by swapping the devices in the initfs
No, this does not solve anything except cosmetic issue with naming. Device minor number is still wrong. Also you now have it 'right' only for situation when you boot with external card inside slot. Once you remove the card and boot it will be wrong again.

and also managed to prevent the root file system from being mounted over USB.
Is there some OS that automounts second partition on mmc card (formatted as ext2)? At least Windows does not see past first partition on removable devices so this does not matter much. But of course with linux one should not mount same partition which is currently booted.


It may be a good idea to add specific initfs patches in the initfs flasher, but I do not know if this applies only to the N810, to OS2008 2.2007.50-2 or both...
Swapping device names is not solution, this needs to be fixed in kernel (http://bugs.maemo.org/show_bug.cgi?id=2747), see also few pages back in this thread. There is also workaround which at least boots from correct card in both situations.

[fanoush]

After installing init_flasher, I get the "Press Menu to activate boot menu" message for like a half a second and it immediately goes to booting from flash. No pressing of menu or any key seems to affect it.
This little N810 specific bug is fixed now. And BTW, I got my N810 yesterday :-)

Also my kernel flasher didn't work on n810 at all and nobody told me :-) Fixed this one too, it was just matter of adding RX-44 to the script.

[kernelpanic]

Is there some OS that automounts second partition on mmc card (formatted as ext2)? At least Windows does not see past first partition on removable devices so this does not matter much. But of course with linux one should not mount same partition which is currently booted.



Debian automouunts every partition it can find. (I had a fat32 partition and 2 ext2 partitions on my external MMC and all of them were being automounted.... Then my laptop crashed with my root mmc partition mounted and I ended up in the endless boot cycle. I had to boot from flash and re-copy...


cheers,
kernelpanic

[mbfrog]

No, this does not solve anything except cosmetic issue with naming. Device minor number is still wrong. Also you now have it 'right' only for situation when you boot with external card inside slot. Once you remove the card and boot it will be wrong again.

Right, I didn't think about booting without an external card... That would be pretty bad indeed. I don't like having my root partition mounted on a non-existing device, but until the kernel is fixed I'll have to live with it I guess ;)

Is there some OS that automounts second partition on mmc card (formatted as ext2)? At least Windows does not see past first partition on removable devices so this does not matter much. But of course with linux one should not mount same partition which is currently booted.
I confirm what kernelpanic just said: Debian (or at least Ubuntu Gutsy) mounts everything the kernel can read. So limiting the USB sharing to the first partition is definitely a good idea for those using Linux.


Using your tips page I've verified that the MMC swapping problem is not affecting my n800. You used the Maemo wiki to clone your card. Those instructions are only intended for 2006, 2007. Did you follow the one for OS2007?
Yes, that's the one I used. The whole cloning process works on 2008 (no reason why it wouldn't). And I didn't find anything specific to 2007.

[Machster]

Yes, that's the one I used. The whole cloning process works on 2008 (no reason why it wouldn't). And I didn't find anything specific to 2007.

Thanks for the confirmation. I tried that too now. I had to make a slight adjustment to the kernel version in the insmod code as OS2008 apparently has 2.6.21 instead of 2.6.18. But still no success. Do I now conclude that both of my cards are not compatible? I don't know what to think. I will continue to watch here for an answer.

[bunanson]

The problem has certainly affected me. I tried the instructions given in the Millhouse thread and the Nuclear instructions, as recommended on the tablet hacker site. I will try the fixes mentioned above.

this maybe your fix, http://www.internettablettalk.com/forums/showthread.php?p=137162#post137162. Kind to tell us what brand of the SD card you are using?

TIA,

bun

[locutus]

I want to buy a new SDHC card for booting OS2008 from it.
What do you think is the card with the best performace? I think about transfer speed that the OS runs very fast.
The capacity is really not important as long as it is 4 or 8 or 16 GB.
And would the OS be faster or slower with this card compared to the build-in memory?

(didn't know if i should post in the sdhc thread or here, but it's related to OS-booting so...)
Thanks

[bunanson]

I want to buy a new SDHC card for booting OS2008 from it.
What do you think is the card with the best performace? I think about transfer speed that the OS runs very fast.
The capacity is really not important as long as it is 4 or 8 or 16 GB.
And would the OS be faster or slower with this card compared to the build-in memory?

(didn't know if i should post in the sdhc thread or here, but it's related to OS-booting so...)
Thanks

Just for you, http://www.internettablettalk.com/forums/showthread.php?t=16067,

bun

[locutus]

Oh, thank you.

[bunanson]

@Fanoush: On N800, how can I edit/add a pointer to bootmenu to have options boot from 1) internal flash,
2) internal SD (mmcblk0)
3) external SD (mmcblk1)

I already cloned OS on 2 SD cards, and they have different contents, I would like to have options to choose booting, rather than physically swap them. Would edit the bootmenu.conf work? If so, please spoon feed with instructions, thanks.

I want to do the same to N810, are they,

1) internal flash, 256 MB
2) internal card, 2G (mmcblk0)
3) external card, SD (mmcblk1)

I made these up. I am totally confused with this internal/external things. They are like playing rudby :(


I did read up thread #50s, not quite sure 'how to approach it though, in particular to avoid re-flash if possible as i have accumulated quite some progs by now and dont quite trust 'restore'.



TIA,

bun

[penguinbait]

NOKIA:~ ROOT#df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mmcblk1p2 2048 1916 132 94% /mnt/initfs
none 512 104 408 20% /mnt/initfs/tmp
/dev/mmcblk0p2 3748988 1359760 2198788 38% /
none 512 104 408 20% /tmp
none 1024 32 992 3% /dev
tmpfs 1024 0 1024 0% /dev/shm
/dev/mmcblk0p1 128220 121360 6860 95% /media/mmc2
/dev/mmcblk1p1 122952 122542 410 100% /media/mmc1


Fanoush is this a bug? I am booting N810 off both mmc1 and mmc2. I noticed it when trying to mount /dev/mmcblk1p2 to access some files.

Any Ideas?

[vormund]

NOKIA:~ ROOT#df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mmcblk1p2 2048 1916 132 94% /mnt/initfs
none 512 104 408 20% /mnt/initfs/tmp
/dev/mmcblk0p2 3748988 1359760 2198788 38% /
none 512 104 408 20% /tmp
none 1024 32 992 3% /dev
tmpfs 1024 0 1024 0% /dev/shm
/dev/mmcblk0p1 128220 121360 6860 95% /media/mmc2
/dev/mmcblk1p1 122952 122542 410 100% /media/mmc1


Fanoush is this a bug? I am booting N810 off both mmc1 and mmc2. I noticed it when trying to mount /dev/mmcblk1p2 to access some files.

Any Ideas?

I had a problem with the internal and external cards switching labels when I formatted to get KDE working on my N810. The internal card would remain named mmcblk0 if there was no external card in the slot, but once the external card was in they would switch, I noticed it when I couldnt boot from mmcblk0 when I had the external card in. I'm not sure what causes it, just that it happens for some reason.

[fanoush]

NOKIA:~ ROOT#df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mmcblk1p2 2048 1916 132 94% /mnt/initfs
none 512 104 408 20% /mnt/initfs/tmp
/dev/mmcblk0p2 3748988 1359760 2198788 38% /
..
Fanoush is this a bug?
Yes, was discussed here too, see also
http://bugs.maemo.org/show_bug.cgi?id=2747

[fanoush]

I already cloned OS on 2 SD cards, and they have different contents, I would like to have options to choose booting, rather than physically swap them. Would edit the bootmenu.conf work?

Yes.

If so, please spoon feed with instructions, thanks.

There is a README in initfs_flasher folder and example bootmenu.conf.*.example files.



I want to do the same to N810, are they,
1) internal flash, 256 MB
2) internal card, 2G (mmcblk0)
3) external card, SD (mmcblk1)

With N810 beware of bug
http://bugs.maemo.org/show_bug.cgi?id=2747 and see workaround here http://www.internettablettalk.com/forums/showthread.php?p=124657#post124657

Sadly I still had no time to update flasher with similar workaround. I'd like to fix it in kernel and have the workaround working with both fixed and broken kernel.


not quite sure 'how to approach it though, in particular to avoid re-flash if possible as i have accumulated quite some progs by now and dont quite trust 'restore'.

you can re-run bootmenu installation many times (with reboots between), rootfs is not touched, when you screw up initfs and system does not boot, you can reflash just initfs part via linux flasher

[pisti]

do you have any idea on how to solve the wlan issue?

Replace all old udev files in OS2007 root directory with OS2008 udev files and wlan works.

Udev files:
/etc/udev
/lib/udev
/lib/firmware
/sbin/udevd
/usr/bin/udevinfo
/usr/sbin/udevmonitor

[pisti]

do you have any idea on how to solve the wlan issue?

Replace udev files and replace /usr/sbin/wlancond
And copy new files:
/usr/lib/libdbus-1.so.3
/usr/lib/libdbus-1.so.3.2.0
/lib/libiw.so.29

[fanoush]

I have been bitten by the N810 device names changing with/without the removable card present but I think I have found a solution. I have put the following code at the top of my bootmenu.conf:


# Set up card names by model
# Assume 770
INT_CARD=""
EXT_CARD="mmcblk0"
...


This has only been tested on my N810 but it works there. Would someone with an N800 like to test it as well?

Maybe Frantisek could consider adding the device name logic to the standard bootmenu.sh and we could all just use the device name variables in our bootmenu.conf?

Hi,

here is version that I'd like to put to boomenu.sh

INT_CARD=""
EXT_CARD=""
case `grep product /proc/component_version` in
*SU-18)
[ -d /sys/block/mmcblk0 ] && EXT_CARD="mmcblk0"
;;
*RX-*)
for i in mmcblk0 mmcblk1 ; do
if [ -d /sys/block/$i ] ; then
case `cat /sys/block/$i/device/../slot_name` in
internal) INT_CARD=$i ;;
external) EXT_CARD=$i ;;
esac
fi
done
;;
esac

Anyone wants to put it to beginning of their bootmenu.conf instead of Graham's code and report how it works? Seems to work here with N810 and 770 at least. Should work with N800 too.

[tolou]

do you have any idea on how to solve the wlan issue?

Replace udev files and replace /usr/sbin/wlancond
And copy new files:
/usr/lib/libdbus-1.so.3
/usr/lib/libdbus-1.so.3.2.0
/lib/libiw.so.29

Was that a question or a suggestion? Are you on to something?

[mscdex]

I am unable to boot to the internal flash on my n810 even after using the modifications I've read in this thread (quoted below). When I try to boot to it it says "boot to mmcint2 failed. booting from flash..." or similar.

Here is what I have in my bootmenu.conf file (changes from the n800 example conf file anyway):



INT_CARD=""
EXT_CARD=""
case `grep product /proc/component_version` in
*SU-18)
[ -d /sys/block/mmcblk0 ] && EXT_CARD="mmcblk0"
;;
*RX-*)
for i in mmcblk0 mmcblk1 ; do
if [ -d /sys/block/$i ] ; then
case `cat /sys/block/$i/device/../slot_name` in
internal) INT_CARD=$i ;;
external) EXT_CARD=$i ;;
esac
fi
done
;;
esac



Followed by:


MENU_2_NAME="Boot internal MMC card, partiton 2, ext2"
MENU_2_ID="mmcint2"
MENU_2_DEVICE=${INT_CARD}p2
MENU_2_MODULES="mbcache ext2"
MENU_2_FSTYPE="ext2"
MENU_2_FSOPTIONS="noatime"

MENU_3_NAME="Boot removable MMC card, partiton 2, ext2"
[ -z "$EXT_CARD" ] && MENU_3_NAME="No removable card -- do not select this"
MENU_3_ID="mmcext2"
MENU_3_DEVICE=${EXT_CARD}p2
MENU_3_MODULES="mbcache ext2"
MENU_3_FSTYPE="ext2"
MENU_3_FSOPTIONS="noatime"



Is there something I am doing wrong?

[fanoush]

Hi, just to let you know that there is newer initfs_flasher.tgz (http://fanoush.wz.cz/maemo/initfs_flasher.tgz) with workaround for inconsistent mmc device names (http://bugs.maemo.org/show_bug.cgi?id=2747) (N8x0 only).

Additional changes:
- there are now boot items for both internal and external cards in default bootmenu.sh so no custom bootmenu.conf needed (unless you want to)
- if partition does not exist, item name "x" is renamed to "(x) N/A"
- the 'booting from ..." message contains also mmc device name and filesystem (for better troubleshooting)

Thanks to Graham Cobb for initial idea.

EDIT:
two default items are named 'mmc2' for external card and 'immc2' fro internal card, I kept mmc2 name for compatibility with 770 and various guides on the net. If you are booting from internal card with N8x0 you may need to update default choice (as root)
chroot /mnt/initfs cal-tool -R ask:immc2
or remove the "ask:" part if you want to boot straight from it without seeing menu

[cdmackay]

hi, thanks much for these tools; just cloned my OS2008 to external 8GB, working perfectly :)

Two comments:

o in the default n8x0 bootmenu.conf, the external SD card defaults to ext3. Was that intentional? It caught me out as I was using Milhouse's clone script which defaults to ext2. Changing it in bootmenu.conf worked fine, of course

o timeout: changing MENU_TIMEOUT in bootmenu.conf (and reflashing) seems to have no effect, for me. Whatever it's set to (e.g 15, 20, 30), I only get about 1/2sec to hold down MENU before it boots the default flash. Is it just me?

thanks again...

[fanoush]

o in the default n8x0 bootmenu.conf, the external SD card defaults to ext3. Was that intentional? It caught me out as I was using Milhouse's clone script which defaults to ext2. Changing it in bootmenu.conf worked fine, of course

Yes, that's just example how to do it. You are supposed to edit the file, not just rename blindly to bootmenu.conf. Also you don't need bootmenu.conf file at all, default menu has ext2 for both cards. Still, I could change the example to leave 2nd partitions as ext2.

o timeout: changing MENU_TIMEOUT in bootmenu.conf (and reflashing) seems to have no effect, for me. Whatever it's set to (e.g 15, 20, 30), I only get about 1/2sec to hold down MENU before it boots the default flash.

Timeout is used later for the menu itself (when you set default choice via cal-tool -R ask:youridofchoice), not for triggering it via menu key. If you have troubles hitting it, use cal-tool and set root device to 'ask'.

[cdmackay]

Thanks very much indeed, Fanoush,

Yes, that's just example how to do it. You are supposed to edit the file, not just rename blindly to bootmenu.conf.


heh; well I wasn't quite blind; I *did* edit the file, but I failed (stupidly) to spot the ext3 in that line whilst I was in there.

Timeout is used later for the menu itself (when you set default choice via cal-tool -R ask:youridofchoice), not for triggering it via menu key.


Ah! that makes sense now, thanks.

If you have troubles hitting it, use cal-tool and set root device to 'ask'.


that does require red-pill mode, yes? I've avoided having to do that at all, so far, so hadn't tried it. The menu key timeout is ok, I just have to be ready for it.

thanks again for a great tool.

[fanoush]

that does require red-pill mode, yes?
no need to take any pills, you just need root privileges (= run 'sudo gainroot') to run cal-tool as mentioned above, you already needed root for installing bootmenu so there should be no problem

[cdmackay]

thanks; that's odd, I did try it but it moaned something about not being able to read block 0.

Will try again, thanks.

[st5150]

The default timeout is 30 seconds - the window of oppurtunity is plenty long IMHO. There's been a few previous posts about changing the timeout/default selection - can't recall the specific search keywords but you should be able to track them down with the search feature.

I'm not having any luck with the search feature. Can someone tell me how to change the boot menu timeout from 30 seconds to 3? I found ./mnt/initfs/bootmenu.conf but it looks like /mnt/initfs is a -ro partition. I thought I'd ask before digging any further. I've already hosed my NIT once, had to reflash.... and I never want to do it again :)

[PinCushionQueen]

I'm not having any luck with the search feature. Can someone tell me how to change the boot menu timeout from 30 seconds to 3? I found ./mnt/initfs/bootmenu.conf but it looks like /mnt/initfs is a -ro partition. I thought I'd ask before digging any further. I've already hosed my NIT once, had to reflash.... and I never want to do it again :)

You need to make a bootmenu.conf file and add it to your initfs_flasher directory and then rerun the flasher. Fanoush has included samples of the text file in the zip for the flasher. There are also several samples posted in various threads here on the itT.

Basically you add the line

MENU_TIMEOUT=3

[st5150]

Okay, thanks for the info, I'll look into it. I just used penguin bait's clone deb so I'm not familiar with famoush's flasher, but I think I can take it from here.

[GeneralAntilles]

You need to make a bootmenu.conf file and add it to your initfs_flasher directory and then rerun the flasher. Fanoush has included samples of the text file in the zip for the flasher. There are also several samples posted in various threads here on the itT.

Basically you add the line

MENU_TIMEOUT=3

No need to make a new file, just rename the appropriate example file (770 or n8x0) to bootmenu.conf and set it up how you like.

It should be noted to anybody reading this thread with questions about bootmenu, the .zip contains a perfectly good README, so do what the file says and read it. . . .

[whereur]

Hi
I have updated the sys to the Diablo and rerun the whole process. But at the end of initfs_flash, it reported an error "unkown initfs version 2008-24, cannot install bootmenu"

So, do we have any update solution for Diablo?

[whereur]

http://www.internettablettalk.com/forums/showthread.php?t=19639&page=27

seems to work... but i didnt like the partion size it created :D

[fanoush]

So, do we have any update solution for Diablo? Yes, the http://fanoush.wz.cz/maemo/initfs_flasher.tgz archive was updated few days ago with Diablo support.

[bunanson]

No need to make a new file, just rename the appropriate example file (770 or n8x0) to bootmenu.conf and set it up how you like.

It should be noted to anybody reading this thread with questions about bootmenu, the .zip contains a perfectly good README, so do what the file says and read it. . . .

It is probably common sense to the Linux guru or GA, but not to the Linux uninitiated. If you want to modify the bootmenu.conf.example, you have to do it with a word processor that DO NOT add a LF/return to the end of the line. Leafpad, vi, emelfm2 are OK, M$Word, tablet/notes, notepad, wordpad are NOT OK. Penalty? It ranges from bootmenu showed up with 'funny' character at the end of the choice or, even worse, continous reboot. If continuous reboot, dont panic, just press the escape button at the menu screen, and hold on to it, that will take you to a flash boot for you to change things. Do not have to reflash for this reason.

Why do bun knows it? Cause I was there :) , painfully and panick.
Hope this helps someone,

bun

[ChillyWilly]

How do I upgrade my MMC clone to the new diablo kernel?

Could I flash the new kernel and then copy just the new kernel to the MMC partition?