bootmenu updated, n800 support

[fanoush]

Hi,

just to let you know that thanks to penguinbait who did guinea pig for me with his N800, bootmenu now supports this device. It still supports N770 of course and has some new features.

Check http://fanoush.wz.cz/maemo/#initfs or directly here http://fanoush.wz.cz/maemo/initfs_flasher.tgz (n770 is dropped from the name)

New features (nothing fancy) described here:
http://maemo.org/pipermail/maemo-developers/2007-January/007111.html

Also fanoush.webpark.cz is retired, maybe you noticed that it went down last week and it took them some time to recover. Now it is back up but I can no longer login properly. If I regain access I'll add some redirect to new page and use it as a backup.

[penguinbait]

There appears to be no USB host mode available, has anyone been able to confirm if it was just left out of the Kernel support? Do we just need a module? I really want USB support.

[fanoush]

Forgot to say that for N800 device bootmenu supports only newer IT2007 version (2.2006.51-6). It may be that some early N800 devices in shops are still with older firmware 1.2006.47-20 which is currently not supported by bootmenu script. If you have this older version (check Control panel->Device->About) then I would be interested in /mnt/initfs/linuxrc file (before you upgrade) so I can add support for it.

[richie]

Hi,

just to let you know that thanks to penguinbait who did guinea pig for me with his N800, bootmenu now supports this device. It still supports N770 of course and has some new features.

Thanks Fanoush, appreciate your work!. Hopefully Nokia will be inviting you to get the N800 at a discount. In fact I'll drop them a line to make sure!

I don't have an N800 myself at the mo. How does bootmenu work with the two SD card slots? Is there a choice?

And does anyone know whether the Navicore map kit could use one slot (presumably needs fat format), whilst booting of an SD card (with ext2) on the other, using bootmenu?

Cheers
Rich

[penguinbait]

I do not have navicore, but you can boot from either slot, any partition. You could then put the 1gb navicore card in the other slot. whichever "other" slot you want. There is a bootmenu.conf where you can change the slot or the partition number, you can even have a bootable card in both slots.

You should also be able to use say a 2GB mmc and have a 1gb bootable partition, and 1gb navicore partition and put say a 4 GB SD in the other slot.

You should also be able to boot from 4GB SD card, I just only have rsmmc available to test. I wonder which is faster mmc or SD? I want to wait for the 8GB to come down in price.

[fanoush]

How does bootmenu work with the two SD card slots? Is there a choice?
Not by default but as penguinbait said you can copy included bootmenu.conf.example to bootmenu.conf and add what you want.

It is probably a good idea to add n770 and N800 specific examples and external slot configuration to N800 example. I'll do it.

I'm not sure how it is with free space in initfs partition on N800 but you may probably edit/create the /mnt/initfs/bootmenu.conf later without reflashing initfs. It is a bit problematic (at least on N770) due to low free space in intfs and journaling nature of jffs2 system. You may edit it few times in place but then you run out of space in initfs and no further writes are possible so it is better to minimize number of writes to files inside /mnt/initfs. When you run out of space, initfs reflash and reboot is needed to have another round of limited writes. It is caused by jffs2 garbage collector that needs lot of free space to reclaim unused space and initfs partition is too small and too full for it to work correctly.

[penguinbait]

I reflash and I am having some problems flashing bootmenu now. I am going to reflash again and do this before I install any other software and see it it makes any difference? Here is the output from the failure????





Nokia-N800-51:~/initfs_flasher# ./initfs_flash

=== Flasher for initfs with onscreen bootmenu ===

For safe flashing please do the following:

- close all aplications (to free available RAM and prevent system crash)
- disconnect from network (to prevent system crash)
- make sure you have at least 5MB free disk space in flasher directory
- make sure you know how to reflash device in usual way if this fails

Are you sure to continue? (yes/no) : yes

Create backup of current initfs (yes/no) : yes
*** creating initfs.orig.jffs2 ...
-rw-r--r-- 1 root root 1686436 Jan 17 15:02 initfs.orig.jffs2
Press enter to continue

Part 1 - Preparing initfs.bootmenu.jffs2 image
*** copying current initfs ... done.
If you remove extra stuff you may write to initfs and customize bootmenu.
Remove unneeded extra (and factory testing) stuff? (yes/no) : yes
*** removing extra stuff ...
*** extracting boot menu files for initfs version osso-RX-34.2006-51 ...
.
./linuxrc
./dev
./dev/mmcblk0p3
./usr
./usr/bin
./usr/bin/evkey
*** copying bootmenu.sh
*** searching for optional bootmenu.conf in current directory ...
Found, do you want to add it to initfs? (yes/no) yes
*** OK, bootmenu.conf added
*** creating initfs.bootmenu.jffs2 ...
-rw-r--r-- 1 root root 1413760 Jan 17 15:02 initfs.bootmenu.jffs2

Part 2 - Ready for flashing this image? (yes/no) : yes
*** remounting initfs read only ...
*** glibc detected *** double free or corruption (fasttop): 0x00047050 ***
Aborted
Press enter to reboot device (or ctrl+c to quit, not recommended)

[penguinbait]

OK, I completely reflashed and it still does not work for me. I am going to try the original instructions. The only things installed before this was becomreroot and xterm.

Any Ideas?

[penguinbait]

OK, I tried the original package and the new package and I get the same results. Fanoush I need some help here??????


All stop on same glibc stop error?????

[penguinbait]

Nokia-N800-51:~/initfs_flasher# mount -o remount,ro /dev/mtdblock3 /mnt/initfs
*** glibc detected *** double free or corruption (fasttop): 0x00047050 ***
Aborted


Not sure why this is causing this error, is my initfs corrupt?

[lbattraw]

Nokia-N800-51:~/initfs_flasher# mount -o remount,ro /dev/mtdblock3 /mnt/initfs
*** glibc detected *** double free or corruption (fasttop): 0x00047050 ***
Aborted

Not sure why this is causing this error, is my initfs corrupt?

Nope, it never started to flash. You can still take the .jffs2 file it creates and use the USB flasher utility to flash, but for whatever reason on-device flashing is broken. I'm having other issues now. I can never get it to recognize I'm pressing the menu button. It will display the "press menu button" message and then boot from flash without ever displaying the menu. Trying other buttons doesn't seem to do anything but stop it from booting at all. It will sit at the Kernel version screen forever.

Larry

[richie]

*** glibc detected *** double free or corruption (fasttop): 0x00047050 ***
Aborted

That looks like a memory pointer issue, maybe with nandwrite? No idea to fix, other than following Larry with using the safe way to flash with the official flashing tool, flasher-3.0.

I don't have an N800 yet, but I wonder if Larry's problem can be replicated?

Rich

[penguinbait]

Read the README.txt use flash tool or use the command in the README.txt to set the boot device to ask:mmc2 or whatever

This will fix the automatically boot from flash.


Yes, I was able to flash initfs manually, I think I must have had a package prior, which allowed me to flash from the command line. I had several OS2006 packages installed.

[fanoush]

Part 2 - Ready for flashing this image? (yes/no) : yes
*** remounting initfs read only ...
*** glibc detected *** double free or corruption (fasttop): 0x00047050 ***
Aborted
Press enter to reboot device (or ctrl+c to quit, not recommended)

This means flashing was not even tried and it failed on remounting initfs read only. Looks like mount command failed. there is
mount -o remount,ro /dev/mtdblock3 /mnt/initfs || return 1
line so it aborts if mount fails (it wouldn't be safe to continue)

Try to run just mount in command line as root (as above or just mount without parameters), does it work? Check if you didn't upgrade to busybox-sdk from bora repository - this is big NO NO as it has mount disabled. Maybe application manager dit it to you by mistake. check via dpkg -l | grep busybox

Most probably initfs is not corrupted, just rootfs :-)

[fanoush]

I'm having other issues now. I can never get it to recognize I'm pressing the menu button. It will display the "press menu button" message and then boot from flash without ever displaying the menu. Trying other buttons doesn't seem to do anything but stop it from booting at all.
please check bootmenu.sh if there are lines

EVNAME=event1 # default, n770
grep -q RX-34 ${initfs_prefix}/etc/initfs_version && EVNAME=event2 #n800
#wait 1 second for keyup event
GETKEY="evkey -u -t 1000 /dev/input/${EVNAME}"

on the beginning. If not, redownload from http://fanoush.wz.cz/maemo/initfs_flasher.tgz (try wget if you get old version - firefox did it to me once on different site).

If yes then please debug this for me. As root run
chroot /mnt/initfs first to get to busubox inside initfs and then paste lines as above one by one, maybe first try simple

grep -q RX-34 /etc/initfs_version && echo It works

and then one by one as above (verbatim, including comment, one never knows with busybox ash) and check to run $GETKEY if it works then, it should wait second and output key code if you press something.

[penguinbait]

Hey Fanoush, any idea what the mount issue is? Has anyone else run into this. It worked the first time I used it, so I assuming something I had installed must have allowed it to work?

[fanoush]

I guess something is corrupted in your rootfs, maybe it was not correctly reflashed? Does it happen also when you boot from mmc (i.e. you are using mount and initfs flasher executed from mmc)? Or if you regulary boot from mmc, does it happen when you boot from flash? Check dmesg log for i/o errors or any other suspicious things there. When mount doesn't work something is seriously wrong with the OS. Some people here or on IRC complain that reflashing is not 100% stable on n800.

*** glibc detected *** double free or corruption (fasttop): 0x00047050 *** looks like corrupted data in RAM, something that should not happen, can be caused by corrupted executable or library in flash

Also it is not the busybox issue I mentioned, right?

[penguinbait]

I initially installed the bootmenu after have lots of packages updated on 2006 OS. So I decided to use my currently running from mmc OS as my default boot. I created a second bootable partition and use tar to backup my first mmc partition. So I can boot to either mmc with Then I decided to use the flash and only install packages built for n800, once everything I wanted was available for n800 platform, I would promote it to mmc and use it as my promary os.


So I had to good copies of my OS on the slots, and reflashed my n800 again with the latest copy 51-6

I then installed becomeroot and installed xterm, then tried to run both initfs_flashers, the original you posted and then the final version.


I used the flasher to flash the initfs that was created by your script to manually install initfs image. I will do some more testing, also note that the change to ask:mmc2, should that stay through reflashing? Mine did? I guess maybe that makes sense?

[fanoush]

I then installed becomeroot and installed xterm, then tried to run both initfs_flashers, the original you posted and then the final version.

Yes, but what system you booted from when using initfs flasher, flash or mmc? Does the error (while flashing initfs) happens when booting from mmc or (maybe corrupted) flash rootfs or both?

[penguinbait]

well once I reflashed I could only boot from flash, I probably could have used the flasher tool and set it to mmc2, but I did not think of that at the time.

When I run from flash the mount command, I get

Nokia-N800-51:~# mount -o remount,ro /dev/mtdblock3 /mnt/initfs
*** glibc detected *** double free or corruption (fasttop): 0x00047050 ***

Aborted

df shows
/dev/mtdblock3 2048 1784 264 87% /mnt/initfs



Has anyone else gotten this from a fresh install?

I tried from my mmc to see if I could mount it and I did not get an error, but if I do a df I see nothing changed.

Nokia-N800-51:~# mount -o remount,ro /dev/mtdblock3 /mnt/initfs
Nokia-N800-51:~# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mmcblk0p2 2048 1784 264 87% /mnt/initfs
none 512 68 444 13% /mnt/initfs/tmp
/dev/mmcblk0p2 1545240 619920 846824 42% /
none 512 68 444 13% /tmp
none 1024 76 948 7% /dev
/dev/mmcblk1p1 40034 6736 33298 17% /media/mmc1
/dev/mmcblk0p1 402968 327888 75080 81% /media/mmc2


I still think its something I installed that made it work, but I can not confirm, unless someone else is having the problem out of the box also.

Is anyone else booting from mmc on n800? Did you get this error? Was it a fresh install, or added to an OS with already lots of 2006 catalog apps?
Do you think its my hardware?

[fanoush]

Oh, I see you don't have bootmenu installed so you boot everytime from flash. Well if one has problems and decides to reflash, there is possibility (with linux flasher) to reflash only rootfs keeping initfs with bootmenu intact. Now the easiest is to copy created initfs.bootmenu.jffs2 to PC and reflash just initfs via linux flasher. But I'd suggest reflashing rootfs or whole device. The glibc error does not seem like the system on device is OK.

Or if initfs on N800 is in fact writable and not full, you can do the same thing as the initfs flasher does when preparing the image. Extract proper bootmenu data for initfs (to initfs directly)
# tar zxvf initfs.oss.RX-34.2006.51.tgz -C /mnt/initfs
then copy over the bootmenu.sh
# cp bootmenu.sh /mnt/initfs/
and bootmenu is installed :-) This is not possible on n770.

[fanoush]

I still think its something I installed that made it work, but I can not confirm, unless someone else is having the problem out of the box also.

No, mount command is what fails and it is provided by busybox package included in OS image. Unless you upgraded it from bora repository by mistake of course (when installing other packages).

[penguinbait]

/opt # ls -l /bin/mount
-rwsr-xr-x 1 root root 64396 May 26 2006 /bin/mount
/opt # ls -l bin/mount
lrwxrwxrwx 1 root root 7 Dec 20 06:23 bin/mount -> busybox
/opt #


Well flash is busybox, mmc is not? Has anyone else been been able to do this? With the mount failing on mmc, with no error, maybe it did just copy them direct????

[fanoush]

Hmm, can you try to add -t jffs2 to the failing mount if it makes a difference? Looks like you really installed different mount which works. The crash can be some busybox bug/feature after all. On n770 it works fine, though. Please try
mount -t jffs2 -o remount,ro /dev/mtdblock3 /mnt/initfs

[penguinbait]

*** This was updated

Check this out its failing to remount, but exiting 0, so it must have been copying them directly to the initfs with the replaced mount command? This was run from mmc, I will boot to flash and post the results below

MMC BOOT, with changed mount command
__________________________________________________ _______
Nokia-N800-51:~# mount -t jffs2 -o remount,ro /dev/mtdblock3 /mnt/initfs
Nokia-N800-51:~# echo $?
0
Nokia-N800-51:~# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mmcblk0p2 2048 1784 264 87% /mnt/initfs
none 512 72 440 14% /mnt/initfs/tmp
/dev/mmcblk0p2 1545240 621276 845468 42% /
none 512 72 440 14% /tmp
none 1024 76 948 7% /dev
/dev/mmcblk1p1 40034 6736 33298 17% /media/mmc1
/dev/mmcblk0p1 402968 327888 75080 81% /media/mmc2
Nokia-N800-51:~#


Flash BOOT, busybox mount command
__________________________________________________ _______
Nokia-N800-51:~# mount -t jffs2 -o remount,ro /dev/mtdblock3 /mnt/initfs
*** glibc detected *** double free or corruption (fasttop): 0x00047050 ***
Aborted
Nokia-N800-51:~# echo $?
134
Nokia-N800-51:~#
Nokia-N800-51:~# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mtdblock4 2048 1784 264 87% /mnt/initfs
none 512 64 448 13% /mnt/initfs/tmp
/dev/mtdblock4 257536 92936 164600 36% /
none 512 64 448 13% /tmp
none 1024 76 948 7% /dev
/dev/mmcblk1p1 40034 6736 33298 17% /media/mmc1
/dev/mmcblk0p1 402968 327888 75080 81% /media/mmc2
/dev/mtdblock3 2048 1784 264 87% /mnt/initfs

Should it have unmounted /mnt/initfs from /dev/mtdblock4 ??

SAME ERROR (134 exit code ???), I guess I am the only guinea pig, have no other N800 users tried this yet? HELLO? If so are you getting the same error or is it just me, I dont think it is but who knows!! Its working great, I just want to help Fanoush get the package correct.

[penguinbait]

What is the deal with the mount anyway? I just reflashed and here is what I did to install the bootmenu.

REFLASHED

installed becomeroot

installed xterm

installed ssh (just to get me a real keyboard)

copied your linuxrc to /mnt/initfs

copied evkey to /mnt/initfs/usr/bin

It failed out of space

I use your to_remove.lst
cd /mnt/initfs
cat /media/mmc1/bootmenu/to_remove.lst | xargs rm -rf

Again, copied evkey to /mnt/initfs/usr/bin

copied bootmenu.sh and bootmenu.conf /mnt/initfs

REBOOT

Had my menu, it worked great, I would still like somebody to confirm the glibc error with that mount, I want to confirm its not a hardware issue?

[fanoush]

MMC BOOT, with changed mount command
__________________________________________________ _______
Nokia-N800-51:~# mount -t jffs2 -o remount,ro /dev/mtdblock3 /mnt/initfs
Nokia-N800-51:~# echo $?
0
Nokia-N800-51:~# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mmcblk0p2 2048 1784 264 87% /mnt/initfs
...

This is OK, it worked. 'df' (and 'mount' too) print just bogus value in first column. It substitues current root filesestem for all entries. Due to the way system boots first root is /dev/mtdblock3 and in linuxrc root is changed via pivot_root command to real root (mtdblock4 or mmc partition). Mount and df cannot cope with this change.
Use cat /proc/mounts to see better picture.



Flash BOOT, busybox mount command
__________________________________________________ _______
Nokia-N800-51:~# mount -t jffs2 -o remount,ro /dev/mtdblock3 /mnt/initfs
*** glibc detected *** double free or corruption (fasttop): 0x00047050 ***
Aborted
Nokia-N800-51:~# echo $?
134
Nokia-N800-51:~#
Nokia-N800-51:~# df
..
/dev/mtdblock3 2048 1784 264 87% /mnt/initfs

This is strange and maybe it actually worked despite the error, can you post 'cat /proc/mounts | grep initfs'? If there is (ro) in last column it worked.


Should it have unmounted /mnt/initfs from /dev/mtdblock4 ??

No, it is not possible. That's why remount option is used.


What is the deal with the mount anyway? I just reflashed and here is what I did to install the bootmenu.

Explained few posts above (including similar steps). In N770 initfs is completely full so the only way to modify it is by reflashing (removing files don't work). With N800 it looks like there is some free space so removing files work. Then it is possible just to copy files to it without reflashing anything. That's nice. With this mount bug it looks like the best way to go on N800.

[penguinbait]

So it looks like the mount problem is not just me. You should have enough info now, will there be a updated package to follow???


Sorry about the first test , I probably should have used a fresh flash to start... but at least I found it eventually ;-)

[fanoush]

You should have enough info now
Well, actually no but never mind :-)

will there be a updated package to follow???

Yes, looks like there may be easy workaround that works (at least on N770), we can use mount command which is inside /mnt/initfs instead of the one in rootfs. Can you run this for me (as root)?

# grep '/mnt/initfs jffs2' /proc/mounts

should print 'rw' in 4th column, and then please run on single line

chroot /mnt/initfs mount -t jffs2 -o remount,ro /dev/mtdblock3 /

and again the grep line above, now it should print 'ro', does it work when booted from flash? No error?

[fanoush]

And if it works, could you redownload the flasher (already contains this change) and check if keys work fine in menu (i.e. event2 is used properly) with my version of bootmenu.sh? Thanks a lot.

[penguinbait]

No error, but no mount, exit 0


BusyBox v1.1.3 (Debian 3:1.1.3-3.osso17) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

Nokia-N800-51:~# grep '/mnt/initfs jffs2' /proc/mounts
/dev/root /mnt/initfs jffs2 rw 0 0
Nokia-N800-51:~# chroot /mnt/initfs mount -t jffs2 -o remount,ro /dev/mtdblock3
/
Nokia-N800-51:~# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mtdblock4 2048 1796 252 88% /mnt/initfs
none 512 68 444 13% /mnt/initfs/tmp
/dev/mtdblock4 257536 87908 169628 34% /
none 512 68 444 13% /tmp
none 1024 76 948 7% /dev
/dev/mmcblk1p1 40034 6796 33238 17% /media/mmc1
/dev/mmcblk0p1 402968 327888 75080 81% /media/mmc2
Nokia-N800-51:~# ls -l /bin/mount
lrwxrwxrwx 1 root root 7 Dec 20 11:23 /bin/mount -> busybox
Nokia-N800-51:~# chroot /mnt/initfs mount -t jffs2 -o remount,ro /dev/mtdblock3 /
Nokia-N800-51:~# echo $?
0
Nokia-N800-51:~# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mtdblock4 2048 1796 252 88% /mnt/initfs
none 512 68 444 13% /mnt/initfs/tmp
/dev/mtdblock4 257536 87908 169628 34% /
none 512 68 444 13% /tmp
none 1024 76 948 7% /dev
/dev/mmcblk1p1 40034 6796 33238 17% /media/mmc1
/dev/mmcblk0p1 402968 327888 75080 81% /media/mmc2
Nokia-N800-51:~#

[midiwall]

fwiw, I just followed Fanoush's directions in the first post and bootmenu is running.

AWESOME. :)


THANK YOU MAN! (and you too PB for the legwork!)

[fanoush]

No error, but no mount, exit 0
That's OK. The whole point of the 'mount -o ro,remount ...' is to remount initfs read only while initially it is mounted read/write. The only thing that should change is 'rw' flags to 'ro'. df output doesn't help me, I was interested in 4th column of one line of /proc/mounts before and after the mount command. Does it change to 'ro'?

Thanks midiwall for confirmation that it works (on n800? including keys?).

[midiwall]

Thanks midiwall for confirmation that it works (on n800? including keys?).Yeup, on N800.

Now, I think I may be seeing things. I DO get the menu, but I can't move the cursor nor hit [] to bypass the timer. The timeout expires and it boots from flash. I could have sworn that the first time the box rebooted (right after the flashing) I was able to walk that menu, but I may have been wrong.

Is it possible that the menu is "smart" and it'll only allow the cursor to move to partitions that have a boot image?

fwiw, this is my session:
Nokia-N800-51:~# cp /media/mmc2/initfs_flasher.tgz .

Nokia-N800-51:~# tar zxvf initfs_flasher.tgz
initfs_flasher
initfs_flasher/nanddump
initfs_flasher/nandwrite
initfs_flasher/to_remove.lst
initfs_flasher/initfs_flash
initfs_flasher/mkfs.jffs2
initfs_flasher/flash_eraseall
initfs_flasher/initfs.osso-n770.2006-25.tgz
initfs_flasher/initfs.osso-RX-34.2006-51.tgz
initfs_flasher/README.txt
initfs_flasher/bootmenu.sh
initfs_flasher/bootmenu.conf.n770.example
initfs_flasher/bootmenu.conf.n800.example
initfs_flasher/initfs.osso-n770.2006-38.tgz

Nokia-N800-51:~# cd initfs_flasher/

Nokia-N800-51:~/initfs_flasher# ls
README.txt initfs.osso-RX-34.2006-51.tgz nanddump
bootmenu.conf.n770.example initfs.osso-n770.2006-25.tgz nandwrite
bootmenu.conf.n800.example initfs.osso-n770.2006-38.tgz to_remove.lst
bootmenu.sh initfs_flash
flash_eraseall mkfs.jffs2

Nokia-N800-51:~/initfs_flasher# ./initfs_flash

=== Flasher for initfs with onscreen bootmenu ===

For safe flashing please do the following:

- close all aplications (to free available RAM and prevent system crash)
- disconnect from network (to prevent system crash)
- make sure you have at least 5MB free disk space in flasher directory
- make sure you know how to reflash device in usual way if this fails

Are you sure to continue? (yes/no) : yes

Create backup of current initfs (yes/no) : yes
*** creating initfs.orig.jffs2 ...
-rw-r--r-- 1 root root 1686436 Jan 19 11:11 initfs.orig.jffs2
Press enter to continue

Part 1 - Preparing initfs.bootmenu.jffs2 image
*** copying current initfs ... done.
If you remove extra stuff you may write to initfs and customize bootmenu.
Remove unneeded extra (and factory testing) stuff? (yes/no) : yes
*** removing extra stuff ...
*** extracting boot menu files for initfs version osso-RX-34.2006-51 ...
.
./linuxrc
./dev
./dev/mmcblk0p3
./usr
./usr/bin
./usr/bin/evkey
*** copying bootmenu.sh
*** searching for optional bootmenu.conf in current directory ...
*** not found, no problem
*** creating initfs.bootmenu.jffs2 ...
-rw-r--r-- 1 root root 1412932 Jan 19 11:11 initfs.bootmenu.jffs2

Part 2 - Ready for flashing this image? (yes/no) : yes
*** remounting initfs read only ... OK
*** caching old initfs to memory (for crash prevention)
*** erasing initfs partition (/dev/mtd3) ...
Erasing 128 Kibyte @ 1e0000 -- 93 % complete. Cleanmarker written at 1e0000.
*** flashing initfs.bootmenu.jffs2 image ...
Writing data to block 0
Writing data to block 20000
Writing data to block 40000
Writing data to block 60000
Writing data to block 80000
Writing data to block a0000
Writing data to block c0000
Writing data to block e0000
Writing data to block 100000
Writing data to block 120000
Writing data to block 140000
*** done
Press enter to reboot device (or ctrl+c to quit, not recommended)


Broadcast message from root (pts/1) (Fri Jan 19 11:11:59 2007):

The system is going down for reboot NOW!
Nokia-N800-51:~/initfs_flasher#


I don't want to confuse the time you're spending with PB. Please continue working with him. I'm booting, I'm fine. We can work on me later. :)

[fanoush]

midiwall, can you do the steps I asked here
http://www.internettablettalk.com/forums/showpost.php?p=30294&postcount=15
Seems like key detection is still not right on N800, I'm interested if GETKEY variable is set correctly and when executing it whether it print key code when you press something or not.

[penguinbait]

Here you go

Nokia-N800-51:~# grep '/mnt/initfs jffs2' /proc/mounts
/dev/root /mnt/initfs jffs2 rw 0 0
Nokia-N800-51:~# chroot /mnt/initfs mount -t jffs2 -o remount,ro /dev/mtdblock3 /
Nokia-N800-51:~# grep '/mnt/initfs jffs2' /proc/mounts
/dev/root /mnt/initfs jffs2 ro 0 0
Nokia-N800-51:~#



Ok here is my question. I don't mean to sound ignorant but, and I dont want you to have to spend a bunch of time explaining things to me, but. Why do I want to make it "read only" before I write to it. I am not claiming to be a genious, but I am a unix admin, and this is just totally counter intuitive. Is this for the backup? I am bewildered, :confused:


I have not looked at the new package yet, I will download that and see what the deal is with the evkeys

[fanoush]

Here you go

Nokia-N800-51:~# grep '/mnt/initfs jffs2' /proc/mounts
/dev/root /mnt/initfs jffs2 rw 0 0
Nokia-N800-51:~# chroot /mnt/initfs mount -t jffs2 -o remount,ro /dev/mtdblock3 /
Nokia-N800-51:~# grep '/mnt/initfs jffs2' /proc/mounts
/dev/root /mnt/initfs jffs2 ro 0 0
Nokia-N800-51:~#

Thanks a lot, so it works as expected

Why do I want to make it "read only" before I write to it.
because the flashing script does the erasing and flashing via accessing underlying /dev/mtd3 device (i.e. raw NAND flash memory). I really do not want the jffs2 garbage collecting thread (do 'ps -ef | grep mtd3' while mounted rw) to touch the device at the same time as the erasing/flashing is done or after it is done before reboot. That could corrupt something.

[penguinbait]

That makes sense, two things accessing the same filesystem would cause issues.

I told you I had copied the files and deleted them previously, so this is not a fresh flash test. But everything is working including the keys.


midiwall, can you reboot again, did it happen over and over again? It will occaisionally happen where the keys will not work, sometimes on reboots, I had not yet mentioned that to Fanoush, never had a problem with shutdowns and starts, only occaisionally when rebooting. Please try again and see if your keys are working.

I looked at mine and all the files timestamps were updated so I think everything is looking good. If midiwalls keys are working you shoudl be all set, if his are really not working I can reflash and see if I can recreate the problem from scratch. Unless someone else shows up to test?


Nokia-N800-51:/home/user/MyDocs/.documents# cd initfs_flasher/
Nokia-N800-51:/home/user/MyDocs/.documents/initfs_flasher# ls
README.txt initfs.osso-n770.2006-38.tgz
bootmenu.conf.n770.example initfs_flash
bootmenu.conf.n800.example mkfs.jffs2
bootmenu.sh nanddump
flash_eraseall nandwrite
initfs.osso-RX-34.2006-51.tgz to_remove.lst
initfs.osso-n770.2006-25.tgz
Nokia-N800-51:/home/user/MyDocs/.documents/initfs_flasher# df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/mtdblock4 2048 1804 244 88% /mnt/initfs
none 512 64 448 13% /mnt/initfs/tmp
/dev/mtdblock4 257536 77584 179952 30% /
none 512 64 448 13% /tmp
none 1024 76 948 7% /dev
/dev/mmcblk1p1 40034 6796 33238 17% /media/mmc1
/dev/mmcblk0p1 402968 327888 75080 81% /media/mmc2
Nokia-N800-51:/home/user/MyDocs/.documents/initfs_flasher# grep '/mnt/initfs jffs2' /proc/mounts
/dev/root /mnt/initfs jffs2 rw 0 0
Nokia-N800-51:/home/user/MyDocs/.documents/initfs_flasher# cp /mnt/initfs/bootmenu.conf .
Nokia-N800-51:/home/user/MyDocs/.documents/initfs_flasher# ls -ltr
-rwxr-xr-x 1 user users 12400 Jul 8 2006 nandwrite
-rwxr-xr-x 1 user users 7464 Jul 8 2006 nanddump
-rwxr-xr-x 1 user users 18084 Aug 5 16:41 flash_eraseall
-rwxr-xr-x 1 user users 35260 Aug 14 20:29 mkfs.jffs2
-rw-r--r-- 1 user users 9444 Aug 24 19:32 to_remove.lst
-rw-r--r-- 1 user users 5698 Jan 1 19:55 initfs.osso-n770.2006-25.tgz
-rw-r--r-- 1 user users 5944 Jan 1 19:56 initfs.osso-n770.2006-38.tgz
-rw-r--r-- 1 user users 4415 Jan 14 20:02 bootmenu.sh
-rw-r--r-- 1 root root 17931 Jan 15 08:10 initfs.osso-RX-34.2006-51.tgz
-rw-r--r-- 1 user users 1127 Jan 17 12:38 bootmenu.conf.n800.example
-rw-r--r-- 1 user users 1031 Jan 17 12:41 bootmenu.conf.n770.example
-rw-r--r-- 1 user users 3007 Jan 17 13:36 README.txt
-rwxr-xr-x 1 user users 5275 Jan 19 13:19 initfs_flash
-rwxr-xr-x 1 root root 902 Jan 20 15:49 bootmenu.conf
Nokia-N800-51:/home/user/MyDocs/.documents/initfs_flasher# ./initfs_flash

=== Flasher for initfs with onscreen bootmenu ===

For safe flashing please do the following:

- close all aplications (to free available RAM and prevent system crash)
- disconnect from network (to prevent system crash)
- make sure you have at least 5MB free disk space in flasher directory
- make sure you know how to reflash device in usual way if this fails

Are you sure to continue? (yes/no) : yes

Create backup of current initfs (yes/no) : yes
*** creating initfs.orig.jffs2 ...
-rw-r--r-- 1 root root 1413572 Jan 20 15:50 initfs.orig.jffs2
Press enter to continue

Part 1 - Preparing initfs.bootmenu.jffs2 image
*** copying current initfs ... done.
If you remove extra stuff you may write to initfs and customize bootmenu.
Remove unneeded extra (and factory testing) stuff? (yes/no) : yes
*** removing extra stuff ...
*** extracting boot menu files for initfs version osso-RX-34.2006-51 ...
.
./linuxrc
./dev
./dev/mmcblk0p3
./usr
./usr/bin
./usr/bin/evkey
*** copying bootmenu.sh
*** searching for optional bootmenu.conf in current directory ...
Found, do you want to add it to initfs? (yes/no) yes
*** OK, bootmenu.conf added
*** creating initfs.bootmenu.jffs2 ...
-rw-r--r-- 1 root root 1413760 Jan 20 15:51 initfs.bootmenu.jffs2

Part 2 - Ready for flashing this image? (yes/no) : yes
*** remounting initfs read only ... OK
*** caching old initfs to memory (for crash prevention)
*** erasing initfs partition (/dev/mtd3) ...
Erasing 128 Kibyte @ 1e0000 -- 93 % complete. Cleanmarker written at 1e0000.
*** flashing initfs.bootmenu.jffs2 image ...
Writing data to block 0
Writing data to block 20000
Writing data to block 40000
Writing data to block 60000
Writing data to block 80000
Writing data to block a0000
Writing data to block c0000
Writing data to block e0000
Writing data to block 100000
Writing data to block 120000
Writing data to block 140000
*** done
Press enter to reboot device (or ctrl+c to quit, not recommended)


Broadcast message from root (pts/0) (Sat Jan 20 15:54:13 2007):

The system is going down for reboot NOW!ts/initfs_flasher#

I did connect to another terminal and it was read-only before reboot

Nokia-N800-51:~# grep '/mnt/initfs jffs2' /proc/mounts
/dev/root /mnt/initfs jffs2 ro 0 0

[midiwall]

please check bootmenu.sh if there are lines
EVNAME=event1 # default, n770
grep -q RX-34 ${initfs_prefix}/etc/initfs_version && EVNAME=event2 #n800
#wait 1 second for keyup event
GETKEY="evkey -u -t 1000 /dev/input/${EVNAME}"
Yeup, got 'em.


If yes then please debug this for me. As root run
grep -q RX-34 /etc/initfs_version && echo It works
This doesn't work because of the the leading "/". The initfs partition shows as:

Nokia-N800-51:/mnt/initfs#

So, you'd want:
grep -q RX-34 etc/initfs_version && echo It worksWhich _does_ work.

Are you expecting ${initfs_prefix} to be set to something when you're actually running at boot? If so, then the script should be "okay", but executing it as root will fail since ${initfs_prefix} isn't defined. (so it returns NULL which makes it look like "/etc..." is based from the root of the partition).


I'm trying to modify bootmenu.sh to try a couple of things, but my wireless connection here in the office is flaky so I keep dropping the connection.

[midiwall]

midiwall, can you reboot again, did it happen over and over again? It will occaisionally happen where the keys will not work, sometimes on reboots, I had not yet mentioned that to Fanoush, never had a problem with shutdowns and starts, only occaisionally when rebooting. Please try again and see if your keys are working.Nope, multiple reboots and no keys. See the above post for what I think the issue is on my machine.

[penguinbait]

That just does not make sense, we have the same scripts?

do you have /mnt/initfs/usr/bin/evkey, it sounds like that is missing?

[midiwall]

Nope, multiple reboots and no keys. See the above post for what I think the issue is on my machine.Well, I lied... They keys just worked. That's about 1 out of 7 times. How weird.


do you have /mnt/initfs/usr/bin/evkey, it sounds like that is missing?Yeup, it's there, and the initfs_version file is there and "correct" in the sense that it has what fanoush is looking for.

Given that I just saw the keys work, and I didn't edit the script (so, it's fanoush's original) something else is going on.

I'm gonna keep playing.

[penguinbait]

midiwall, try to boot and when it does not work, try this and see what event device its set to? Were you rebooting or shutting down and then starting up, is your power cord plugged in?

chroot /mnt/initfs evkey -u -t 5000 /dev/input/event2

If you run this it will just sit there, then if you hit the down key it should print 108, 103 for up, 105 for left, or 106 for right.

If nothing is printer on the screen, hit control-c to exit then try changing event, but it should be 2 unless we have a hardware difference?

This will confirm your evkey is working, if so some reason they are not working try changing the event number. Just want to confirm.

chroot /mnt/initfs evkey -u -t 5000 /dev/input/event0
chroot /mnt/initfs evkey -u -t 5000 /dev/input/event1
chroot /mnt/initfs evkey -u -t 5000 /dev/input/event2
chroot /mnt/initfs evkey -u -t 5000 /dev/input/event3

let me know what happens?

[fanoush]

it would be good to add to bootmenu.sh before it is exiting (i.e. last line)
dmesg >/tmp/dmesg.txt
and then when it booted check that file to see how the input subsystem is configured (i.e. what is tied to which input number)
maybe it gots selected randomly (i.e sometimes event2 is keys sometimes touchcreen ???)? Does the output differ when keys do work and when they do not?

[fanoush]

this is what i see on n770

[87717.938812] OMAP Keypad Driver
[87717.940032] input: omap-keypad as /class/input/input1
[87717.941223] ads7846 spi2.0: touchscreen, irq 175
[87717.942687] input: ADS784x Touchscreen as /class/input/input2

[penguinbait]

here is mine

Nokia-N800-51:~# cat /tmp/dmesg.txt
: 4096 (order: 2, 16384 bytes)
[ 311.688385] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[ 311.688537] TCP: Hash tables configured (established 4096 bind 2048)
[ 311.688568] TCP reno registered
[ 311.689758] NetWinder Floating Point Emulator V0.97 (double precision)
[ 311.690277] dsp dsp: OMAP DSP driver initialization
[ 311.705322] JFFS2 version 2.2. (NAND) (SUMMARY) (C) 2001-2006 Red Hat, Inc.
[ 311.706481] lowmem: Module initialized.
[ 311.706573] io scheduler noop registered (default)
[ 311.707611] omapfb: ls041y3 rev 8f LCD detected
[ 311.707946] omapfb: configured for panel ls041y3
[ 311.722167] omapfb: DISPC version 2.0 initialized
[ 311.722351] omapfb: RFBI version 1.0 initialized
[ 311.741912] omapfb omapfb: can't determine maximum RFBI transfer rate
[ 311.742034] omapfb: s1d13745 LCD controller rev 1 initialized (CNF pins 3)
[ 311.742218] omapfb omapfb: s1d1374x: setting update mode to manual
[ 311.743713] omapfb: Framebuffer initialized. Total vram 2310144 planes 3
[ 311.743804] omapfb: Pixclock 21940 kHz hfreq 24.9 kHz vfreq 51.0 Hz
[ 311.768096] OMAP Watchdog Timer: initial timeout 60 sec
[ 311.768249] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[ 311.779510] RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
[ 311.783081] loop: loaded (max 8 devices)
[ 311.784576] PPP generic driver version 2.4.2
[ 311.785125] PPP Deflate Compression module registered
[ 311.785186] PPP BSD Compression module registered
[ 311.785247] tun: Universal TUN/TAP device driver, 1.6
[ 311.785308] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 311.785675] Linux video capture interface: v2.00
[ 311.797393] FCLK = 96000000 [96000000], usecount = 1
[ 311.797973] omap24xxcam: registered device video0 [v4l2]
[ 311.802856] tea5761 0-0010: tea5761 (version 7) detected at 0-0010
[ 311.806549] Menelaus rev 2.2
[ 311.807067] menelaus: Setting VCORE FLOOR to 1050 mV and ROOF to 1400 mV
[ 311.820251] menelaus: regulator sleep configuration: ff
[ 311.821044] Retu power button driver initialized
[ 311.821105] retu: Registering interrupt 0 for device PwrOnX
[ 311.821807] input: retu-pwrbutton as /class/input/input0
[ 311.822845] retu: Registering interrupt 2 for device RTCS
[ 311.823059] retu: Registering interrupt 5 for device RTCA
[ 311.824127] Retu watchdog driver initialized
[ 311.824218] Retu/Vilma headset driver initializing
[ 311.825164] input: retu-headset as /class/input/input1
[ 311.825317] retu: Registering interrupt 6 for device hookdet
[ 311.826232] OMAP2 OneNAND driver initializing
[ 311.826965] omap2-onenand omap2-onenand: initializing on CS0, phys base 0x04000000, virtual base c8880000
[ 311.827087] OneNAND Manufacturer: Samsung (0xec)
[ 311.827117] Muxed OneNAND(DDP) 256MB 1.8V 16-bit (0x48)
[ 311.827178] OneNAND version = 0x0011
[ 311.846374] Scanning device for bad blocks
[ 311.899230] Creating 5 MTD partitions on "omap2-onenand":
[ 311.899291] 0x00000000-0x00020000 : "bootloader"
[ 311.900512] 0x00020000-0x00080000 : "config"
[ 311.901702] 0x00080000-0x00280000 : "kernel"
[ 311.902862] 0x00280000-0x00480000 : "initfs"
[ 311.904083] 0x00480000-0x10000000 : "rootfs"
[ 311.906524] TSC2301 driver initializing
[ 311.908996] input: TSC2301 keypad as /class/input/input2
[ 311.909851] input: TSC2301 touchscreen as /class/input/input3
[ 311.910736] mice: PS/2 mouse device common for all mice
[ 311.912231] tmp105: initializing
[ 311.913146] menelaus: Setting voltage 'VAUX' to 2800 mV (reg 0x0a, val 0xb8)
[ 311.929809] tmp105: found at address 0x48
[ 311.969482] hci_h4p hci_h4p: Registering HCI H4P device
[ 312.198272] menelaus: Setting voltage 'VMMC' to 3100 mV (reg 0x0a, val 0xf8)
[ 312.211608] mmci-omap mmci-omap.1: cover is now closed
[ 312.211914] omap_pwm_led omap_pwm_led: OMAP PWM LED (keypad) at GP timer 10/9
[ 312.212371] Registered led device: keypad
[ 312.226715] Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).
[ 312.228271] omap24xx-eac omap24xx-eac: EAC version: 1.0
[ 312.232635] ALSA device list:
[ 312.232727] #0: OMAP24xx EAC with codec TSC2301
[ 312.232757] Netfilter messages via NETLINK v0.30.
[ 312.232879] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 312.292083] menelaus: Setting voltage 'VMMC' to 2800 mV (reg 0x0a, val 0x78)
[ 312.304748] TCP bic registered
[ 312.304901] NET: Registered protocol family 1
[ 312.304992] NET: Registered protocol family 17
[ 312.305084] Bluetooth: L2CAP ver 2.8
[ 312.305114] Bluetooth: L2CAP socket layer initialized
[ 312.305175] Bluetooth: SCO (Voice Link) ver 0.5
[ 312.305206] Bluetooth: SCO socket layer initialized
[ 312.305328] Bluetooth: RFCOMM socket layer initialized
[ 312.305450] Bluetooth: RFCOMM TTY layer initialized
[ 312.305511] Bluetooth: RFCOMM ver 1.8
[ 312.305572] Bluetooth: BNEP (Ethernet Emulation) ver 1.2
[ 312.305603] Bluetooth: HIDP (Human Interface Emulation) ver 1.1-mh1
[ 312.305664] Power Management for OMAP2 initializing
[ 312.305725] PRCM revision 1.0
[ 312.305847] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 2
[ 312.305969] Disabling unused clock "uart3_fck"
[ 312.306030] Disabling unused clock "uart3_ick"
[ 312.306060] Disabling unused clock "uart2_fck"
[ 312.306121] Disabling unused clock "uart2_ick"
[ 312.306152] Disabling unused clock "gpt12_fck"
[ 312.306182] Disabling unused clock "gpt12_ick"
[ 312.306243] Disabling unused clock "gpt11_fck"
[ 312.306274] Disabling unused clock "gpt11_ick"
[ 312.306335] Disabling unused clock "gpt8_fck"
[ 312.306365] Disabling unused clock "gpt8_ick"
[ 312.306427] Disabling unused clock "gpt7_fck"
[ 312.306457] Disabling unused clock "gpt7_ick"
[ 312.306488] Disabling unused clock "gpt6_fck"
[ 312.306549] Disabling unused clock "gpt6_ick"
[ 312.306579] Disabling unused clock "gpt5_fck"
[ 312.306640] Disabling unused clock "gpt5_ick"
[ 312.306671] Disabling unused clock "gpt4_fck"
[ 312.306701] Disabling unused clock "gpt4_ick"
[ 312.306762] Disabling unused clock "gpt3_fck"
[ 312.306793] Disabling unused clock "gpt3_ick"
[ 312.306854] Disabling unused clock "gpt2_fck"
[ 312.306884] Disabling unused clock "gpt2_ick"
[ 312.306915] Disabling unused clock "dss2_fck"
[ 312.307586] Bootup reason: sw_rst
[ 312.307678] OMAP GPIO switch handler initializing
[ 312.310577] headphone (GPIO 107) is now disconnected
[ 312.310668] cam_turn (GPIO 12) is now inactive
[ 312.310729] cam_act (GPIO 95) is now inactive
[ 312.310791] bat_cover (GPIO 110) is now closed
[ 312.311004] OMAP Random Number Generator ver. 40
[ 312.311309] 128 words of entropy generated
[ 312.311401] FCLK = 96000000 [96000000], usecount = 1
[ 312.311523] mmci-omap mmci-omap.1: cover is now closed
[ 312.311889] menelaus: Setting voltage 'VMEM' to 1500 mV (reg 0x0a, val 0x78)
[ 312.343780] menelaus: Setting voltage 'VIO' to 2500 mV (reg 0x0a, val 0x78)
[ 312.380645] mmcblk0: mmc0:0001 MMCm 2039296KiB
[ 312.380950] mmcblk0: p1 p2 p3
[ 312.385314] menelaus: Setting voltage 'VDCDC3' to 3300 mV (reg 0x07, val 0x39)
[ 312.479553] menelaus: Setting voltage 'VDCDC3' to 2800 mV (reg 0x07, val 0x29)
[ 312.485229] tcm825x_find_size(): size 3
[ 312.485290] tcm825xsensor_try_format(): isize = 3 num_capture = 2
[ 312.485321] tcm825xsensor_try_format(): format = 0x50424752
[ 312.485351] Sensor is TCM825x
[ 312.515655] menelaus: Setting voltage 'VIO' to 0 mV (reg 0x0a, val 0x70)
[ 312.546875] menelaus: Setting voltage 'VMEM' to 0 mV (reg 0x0a, val 0x70)
[ 312.615570] mmcblk1: mmc1:0001 SDR01G 1003264KiB
[ 312.615905] mmcblk1: p1 p2 p3
[ 312.661529] VFS: Mounted root (jffs2 filesystem).
[ 312.661865] Freeing init memory: 108K
Nokia-N800-51:~#

[midiwall]

crap you guys... now I can't get it to fail. :) I'm 5 for 5 in having the keys working at boot.


pb: I've rebooted with and without the powercord. Until "now" (whatever that means) neither way was allowing keys at boot.


demsg output:
[ 5054.822448] TCP reno registered
[ 5054.823608] NetWinder Floating Point Emulator V0.97 (double precision)
[ 5054.824127] dsp dsp: OMAP DSP driver initialization
[ 5054.839202] JFFS2 version 2.2. (NAND) (SUMMARY) (C) 2001-2006 Red Hat, Inc.
[ 5054.840362] lowmem: Module initialized.
[ 5054.840454] io scheduler noop registered (default)
[ 5054.841522] omapfb: ls041y3 rev 8f LCD detected
[ 5054.841857] omapfb: configured for panel ls041y3
[ 5054.855804] omapfb: DISPC version 2.0 initialized
[ 5054.855957] omapfb: RFBI version 1.0 initialized
[ 5054.875762] omapfb omapfb: can't determine maximum RFBI transfer rate
[ 5054.875885] omapfb: s1d13745 LCD controller rev 1 initialized (CNF pins 3)
[ 5054.876037] omapfb omapfb: s1d1374x: setting update mode to manual
[ 5054.877563] omapfb: Framebuffer initialized. Total vram 2310144 planes 3
[ 5054.877655] omapfb: Pixclock 21940 kHz hfreq 24.9 kHz vfreq 51.0 Hz
[ 5054.901977] OMAP Watchdog Timer: initial timeout 60 sec
[ 5054.902130] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[ 5054.913452] RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
[ 5054.916992] loop: loaded (max 8 devices)
[ 5054.918487] PPP generic driver version 2.4.2
[ 5054.919036] PPP Deflate Compression module registered
[ 5054.919097] PPP BSD Compression module registered
[ 5054.919158] tun: Universal TUN/TAP device driver, 1.6
[ 5054.919219] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 5054.919586] Linux video capture interface: v2.00
[ 5054.931304] FCLK = 96000000 [96000000], usecount = 1
[ 5054.931884] omap24xxcam: registered device video0 [v4l2]
[ 5054.936737] tea5761 0-0010: tea5761 (version 7) detected at 0-0010
[ 5054.940429] Menelaus rev 2.2
[ 5054.940948] menelaus: Setting VCORE FLOOR to 1050 mV and ROOF to 1400 mV
[ 5054.954101] menelaus: regulator sleep configuration: ff
[ 5054.954895] Retu power button driver initialized
[ 5054.954956] retu: Registering interrupt 0 for device PwrOnX
[ 5054.955657] input: retu-pwrbutton as /class/input/input0
[ 5054.956695] retu: Registering interrupt 2 for device RTCS
[ 5054.956909] retu: Registering interrupt 5 for device RTCA
[ 5054.958007] Retu watchdog driver initialized
[ 5054.958068] Retu/Vilma headset driver initializing
[ 5054.959045] input: retu-headset as /class/input/input1
[ 5054.959197] retu: Registering interrupt 6 for device hookdet
[ 5054.960113] OMAP2 OneNAND driver initializing
[ 5054.960845] omap2-onenand omap2-onenand: initializing on CS0, phys base 0x04000000, virtual base c8880000
[ 5054.960968] OneNAND Manufacturer: Samsung (0xec)
[ 5054.960998] Muxed OneNAND(DDP) 256MB 1.8V 16-bit (0x48)
[ 5054.961059] OneNAND version = 0x0011
[ 5054.980285] Scanning device for bad blocks
[ 5055.001861] Bad eraseblock 808 at 0x06500000
[ 5055.001983] Bad eraseblock 810 at 0x06540000
[ 5055.002075] Bad eraseblock 812 at 0x06580000
[ 5055.034759] Creating 5 MTD partitions on "omap2-onenand":
[ 5055.034820] 0x00000000-0x00020000 : "bootloader"
[ 5055.036041] 0x00020000-0x00080000 : "config"
[ 5055.037231] 0x00080000-0x00280000 : "kernel"
[ 5055.038391] 0x00280000-0x00480000 : "initfs"
[ 5055.039886] 0x00480000-0x10000000 : "rootfs"
[ 5055.042114] TSC2301 driver initializing
[ 5055.044555] input: TSC2301 keypad as /class/input/input2
[ 5055.045410] input: TSC2301 touchscreen as /class/input/input3
[ 5055.046295] mice: PS/2 mouse device common for all mice
[ 5055.048126] tmp105: initializing
[ 5055.049072] menelaus: Setting voltage 'VAUX' to 2800 mV (reg 0x0a, val 0xb8)
[ 5055.063690] tmp105: found at address 0x48
[ 5055.103363] hci_h4p hci_h4p: Registering HCI H4P device
[ 5055.332092] menelaus: Setting voltage 'VMMC' to 3100 mV (reg 0x0a, val 0xf8)
[ 5055.345458] mmci-omap mmci-omap.1: cover is now closed
[ 5055.345764] omap_pwm_led omap_pwm_led: OMAP PWM LED (keypad) at GP timer 10/9
[ 5055.346221] Registered led device: keypad
[ 5055.360595] Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).
[ 5055.362121] omap24xx-eac omap24xx-eac: EAC version: 1.0
[ 5055.366485] ALSA device list:
[ 5055.366546] #0: OMAP24xx EAC with codec TSC2301
[ 5055.366607] Netfilter messages via NETLINK v0.30.
[ 5055.366729] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 5055.423583] menelaus: Setting voltage 'VMMC' to 2800 mV (reg 0x0a, val 0x78)
[ 5055.438598] TCP bic registered
[ 5055.438751] NET: Registered protocol family 1
[ 5055.438842] NET: Registered protocol family 17
[ 5055.438934] Bluetooth: L2CAP ver 2.8
[ 5055.438964] Bluetooth: L2CAP socket layer initialized
[ 5055.439025] Bluetooth: SCO (Voice Link) ver 0.5
[ 5055.439056] Bluetooth: SCO socket layer initialized
[ 5055.439178] Bluetooth: RFCOMM socket layer initialized
[ 5055.439300] Bluetooth: RFCOMM TTY layer initialized
[ 5055.439361] Bluetooth: RFCOMM ver 1.8
[ 5055.439422] Bluetooth: BNEP (Ethernet Emulation) ver 1.2
[ 5055.439453] Bluetooth: HIDP (Human Interface Emulation) ver 1.1-mh1
[ 5055.439514] Power Management for OMAP2 initializing
[ 5055.439575] PRCM revision 1.0
[ 5055.439727] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 2
[ 5055.439849] Disabling unused clock "uart3_fck"
[ 5055.439880] Disabling unused clock "uart3_ick"
[ 5055.439941] Disabling unused clock "uart2_fck"
[ 5055.439971] Disabling unused clock "uart2_ick"
[ 5055.440032] Disabling unused clock "gpt12_fck"
[ 5055.440063] Disabling unused clock "gpt12_ick"
[ 5055.440093] Disabling unused clock "gpt11_fck"
[ 5055.440155] Disabling unused clock "gpt11_ick"
[ 5055.440185] Disabling unused clock "gpt8_fck"
[ 5055.440246] Disabling unused clock "gpt8_ick"
[ 5055.440277] Disabling unused clock "gpt7_fck"
[ 5055.440338] Disabling unused clock "gpt7_ick"
[ 5055.440368] Disabling unused clock "gpt6_fck"
[ 5055.440399] Disabling unused clock "gpt6_ick"
[ 5055.440460] Disabling unused clock "gpt5_fck"
[ 5055.440490] Disabling unused clock "gpt5_ick"
[ 5055.440551] Disabling unused clock "gpt4_fck"
[ 5055.440582] Disabling unused clock "gpt4_ick"
[ 5055.440643] Disabling unused clock "gpt3_fck"
[ 5055.440673] Disabling unused clock "gpt3_ick"
[ 5055.440704] Disabling unused clock "gpt2_fck"
[ 5055.440765] Disabling unused clock "gpt2_ick"
[ 5055.440795] Disabling unused clock "dss2_fck"
[ 5055.441467] Bootup reason: sw_rst
[ 5055.441558] OMAP GPIO switch handler initializing
[ 5055.444427] headphone (GPIO 107) is now disconnected
[ 5055.444549] cam_turn (GPIO 12) is now inactive
[ 5055.444580] cam_act (GPIO 95) is now inactive
[ 5055.444641] bat_cover (GPIO 110) is now closed
[ 5055.444885] OMAP Random Number Generator ver. 40
[ 5055.445190] 128 words of entropy generated
[ 5055.445251] FCLK = 96000000 [96000000], usecount = 1
[ 5055.445404] mmci-omap mmci-omap.1: cover is now closed
[ 5055.445983] menelaus: Setting voltage 'VMEM' to 1500 mV (reg 0x0a, val 0x78)
[ 5055.477630] menelaus: Setting voltage 'VIO' to 2500 mV (reg 0x0a, val 0x78)
[ 5055.563903] mmcblk0: mmc0:e624 SD128 123008KiB
[ 5055.564208] mmcblk0: p1
[ 5055.568542] menelaus: Setting voltage 'VDCDC3' to 3300 mV (reg 0x07, val 0x39)
[ 5055.619079] tcm825x_find_size(): size 3
[ 5055.619110] tcm825xsensor_try_format(): isize = 3 num_capture = 2
[ 5055.619140] tcm825xsensor_try_format(): format = 0x50424752
[ 5055.619171] Sensor is TCM825x
[ 5055.649505] menelaus: Setting voltage 'VIO' to 0 mV (reg 0x0a, val 0x70)
[ 5055.660644] menelaus: Setting voltage 'VDCDC3' to 0 mV (reg 0x07, val 0x01)
[ 5055.680328] mmci-omap mmci-omap.1: card status error (CMD13)
[ 5055.680816] menelaus: Setting voltage 'VMEM' to 0 mV (reg 0x0a, val 0x70)
[ 5055.786468] Empty flash at 0x00158f44 ends at 0x00159000
[ 5055.790618] VFS: Mounted root (jffs2 filesystem).
[ 5055.790954] Freeing init memory: 108K

[midiwall]

demsg output:
Sorry, that was useless to you since it happened on a boot where the keys worked.

I understand what you're looking for now. I'll keep trying to get a boot where the keys don't work.

[midiwall]

I got it - and I can get the keys to fail at will.

To get the keys to NOT work in the boot menu, hold down the [] center button while powering up. You can let go as soon as the blue led goes out. Doing this seems to generate the equivalent of a PC "keyboard error" and it looks like it hangs the input handler. Once the system comes up all the way it'll get reset, but until then you're hosed.

fwiw, here's the output from a boot where the keys didn't work:
Nokia-N800-51:~# cat /tmp/dmesg.txt

[ 2.944519] TCP reno registered
[ 2.945709] NetWinder Floating Point Emulator V0.97 (double precision)
[ 2.946197] dsp dsp: OMAP DSP driver initialization
[ 2.961334] JFFS2 version 2.2. (NAND) (SUMMARY) (C) 2001-2006 Red Hat, Inc.
[ 2.962493] lowmem: Module initialized.
[ 2.962585] io scheduler noop registered (default)
[ 2.963623] omapfb: ls041y3 rev 8f LCD detected
[ 2.963958] omapfb: configured for panel ls041y3
[ 2.978118] omapfb: DISPC version 2.0 initialized
[ 2.978302] omapfb: RFBI version 1.0 initialized
[ 2.997833] omapfb omapfb: can't determine maximum RFBI transfer rate
[ 2.997955] omapfb: s1d13745 LCD controller rev 1 initialized (CNF pins 3)
[ 2.998107] omapfb omapfb: s1d1374x: setting update mode to manual
[ 2.999633] omapfb: Framebuffer initialized. Total vram 2310144 planes 3
[ 2.999725] omapfb: Pixclock 21940 kHz hfreq 24.9 kHz vfreq 51.0 Hz
[ 3.024047] OMAP Watchdog Timer: initial timeout 60 sec
[ 3.024200] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
[ 3.035491] RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
[ 3.039031] loop: loaded (max 8 devices)
[ 3.040527] PPP generic driver version 2.4.2
[ 3.041076] PPP Deflate Compression module registered
[ 3.041137] PPP BSD Compression module registered
[ 3.041198] tun: Universal TUN/TAP device driver, 1.6
[ 3.041229] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 3.041625] Linux video capture interface: v2.00
[ 3.053314] FCLK = 96000000 [96000000], usecount = 1
[ 3.053894] omap24xxcam: registered device video0 [v4l2]
[ 3.059539] tea5761 0-0010: tea5761 (version 7) detected at 0-0010
[ 3.063232] Menelaus rev 2.2
[ 3.063751] menelaus: Setting VCORE FLOOR to 1050 mV and ROOF to 1400 mV
[ 3.076171] menelaus: regulator sleep configuration: ff
[ 3.076965] Retu power button driver initialized
[ 3.076995] retu: Registering interrupt 0 for device PwrOnX
[ 3.077728] input: retu-pwrbutton as /class/input/input0
[ 3.078735] retu: Registering interrupt 2 for device RTCS
[ 3.078948] retu: Registering interrupt 5 for device RTCA
[ 3.080047] Retu watchdog driver initialized
[ 3.080108] Retu/Vilma headset driver initializing
[ 3.081085] input: retu-headset as /class/input/input1
[ 3.081207] retu: Registering interrupt 6 for device hookdet
[ 3.082153] OMAP2 OneNAND driver initializing
[ 3.082855] omap2-onenand omap2-onenand: initializing on CS0, phys base 0x04000000, virtual base c8880000
[ 3.082977] OneNAND Manufacturer: Samsung (0xec)
[ 3.083038] Muxed OneNAND(DDP) 256MB 1.8V 16-bit (0x48)
[ 3.083068] OneNAND version = 0x0011
[ 3.102264] Scanning device for bad blocks
[ 3.123870] Bad eraseblock 808 at 0x06500000
[ 3.123962] Bad eraseblock 810 at 0x06540000
[ 3.124053] Bad eraseblock 812 at 0x06580000
[ 3.156768] Creating 5 MTD partitions on "omap2-onenand":
[ 3.156829] 0x00000000-0x00020000 : "bootloader"
[ 3.158020] 0x00020000-0x00080000 : "config"
[ 3.159210] 0x00080000-0x00280000 : "kernel"
[ 3.160400] 0x00280000-0x00480000 : "initfs"
[ 3.161865] 0x00480000-0x10000000 : "rootfs"
[ 3.164062] TSC2301 driver initializing
[ 3.166564] input: TSC2301 keypad as /class/input/input2
[ 3.167388] input: TSC2301 touchscreen as /class/input/input3
[ 3.168273] mice: PS/2 mouse device common for all mice
[ 3.170104] tmp105: initializing
[ 3.171051] menelaus: Setting voltage 'VAUX' to 2800 mV (reg 0x0a, val 0xb8)
[ 3.185760] tmp105: found at address 0x48
[ 3.225433] hci_h4p hci_h4p: Registering HCI H4P device
[ 3.454193] menelaus: Setting voltage 'VMMC' to 3100 mV (reg 0x0a, val 0xf8)
[ 3.467590] mmci-omap mmci-omap.1: cover is now closed
[ 3.467926] omap_pwm_led omap_pwm_led: OMAP PWM LED (keypad) at GP timer 10/9
[ 3.468383] Registered led device: keypad
[ 3.482666] Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).
[ 3.484191] omap24xx-eac omap24xx-eac: EAC version: 1.0
[ 3.532440] ALSA device list:
[ 3.532531] #0: OMAP24xx EAC with codec TSC2301
[ 3.532592] Netfilter messages via NETLINK v0.30.
[ 3.532714] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 3.545715] menelaus: Setting voltage 'VMMC' to 2800 mV (reg 0x0a, val 0x78)
[ 3.599304] TCP bic registered
[ 3.599456] NET: Registered protocol family 1
[ 3.599548] NET: Registered protocol family 17
[ 3.599609] Bluetooth: L2CAP ver 2.8
[ 3.599670] Bluetooth: L2CAP socket layer initialized
[ 3.599700] Bluetooth: SCO (Voice Link) ver 0.5
[ 3.599761] Bluetooth: SCO socket layer initialized
[ 3.599884] Bluetooth: RFCOMM socket layer initialized
[ 3.600006] Bluetooth: RFCOMM TTY layer initialized
[ 3.600067] Bluetooth: RFCOMM ver 1.8
[ 3.600097] Bluetooth: BNEP (Ethernet Emulation) ver 1.2
[ 3.600158] Bluetooth: HIDP (Human Interface Emulation) ver 1.1-mh1
[ 3.600219] Power Management for OMAP2 initializing
[ 3.600250] PRCM revision 1.0
[ 3.600402] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 2
[ 3.600524] Disabling unused clock "uart3_fck"
[ 3.600555] Disabling unused clock "uart3_ick"
[ 3.600585] Disabling unused clock "uart2_fck"
[ 3.600646] Disabling unused clock "uart2_ick"
[ 3.600677] Disabling unused clock "gpt12_fck"
[ 3.600738] Disabling unused clock "gpt12_ick"
[ 3.600769] Disabling unused clock "gpt11_fck"
[ 3.600830] Disabling unused clock "gpt11_ick"
[ 3.600860] Disabling unused clock "gpt8_fck"
[ 3.600891] Disabling unused clock "gpt8_ick"
[ 3.600952] Disabling unused clock "gpt7_fck"
[ 3.600982] Disabling unused clock "gpt7_ick"
[ 3.601043] Disabling unused clock "gpt6_fck"
[ 3.601074] Disabling unused clock "gpt6_ick"
[ 3.601104] Disabling unused clock "gpt5_fck"
[ 3.601165] Disabling unused clock "gpt5_ick"
[ 3.601196] Disabling unused clock "gpt4_fck"
[ 3.601257] Disabling unused clock "gpt4_ick"
[ 3.601287] Disabling unused clock "gpt3_fck"
[ 3.601318] Disabling unused clock "gpt3_ick"
[ 3.601379] Disabling unused clock "gpt2_fck"
[ 3.601409] Disabling unused clock "gpt2_ick"
[ 3.601470] Disabling unused clock "dss2_fck"
[ 3.602111] Bootup reason: pwr_key
[ 3.602203] OMAP GPIO switch handler initializing
[ 3.605102] headphone (GPIO 107) is now disconnected
[ 3.605194] cam_turn (GPIO 12) is now inactive
[ 3.605255] cam_act (GPIO 95) is now inactive
[ 3.605316] bat_cover (GPIO 110) is now closed
[ 3.605529] OMAP Random Number Generator ver. 40
[ 3.605834] 128 words of entropy generated
[ 3.605926] FCLK = 96000000 [96000000], usecount = 1
[ 3.606048] mmci-omap mmci-omap.1: cover is now closed
[ 3.606414] menelaus: Setting voltage 'VMEM' to 1500 mV (reg 0x0a, val 0x78)
[ 3.638763] menelaus: Setting voltage 'VIO' to 2500 mV (reg 0x0a, val 0x78)
[ 3.693145] mmcblk0: mmc0:e624 SD128 123008KiB
[ 3.693450] mmcblk0: p1
[ 3.697784] menelaus: Setting voltage 'VDCDC3' to 3300 mV (reg 0x07, val 0x39)
[ 3.780212] tcm825x_find_size(): size 3
[ 3.780242] tcm825xsensor_try_format(): isize = 3 num_capture = 2
[ 3.780273] tcm825xsensor_try_format(): format = 0x50424752
[ 3.780303] Sensor is TCM825x
[ 3.790588] menelaus: Setting voltage 'VDCDC3' to 0 mV (reg 0x07, val 0x01)
[ 3.810211] mmci-omap mmci-omap.1: card status error (CMD13)
[ 3.810729] menelaus: Setting voltage 'VIO' to 0 mV (reg 0x0a, val 0x70)
[ 3.841857] menelaus: Setting voltage 'VMEM' to 0 mV (reg 0x0a, val 0x70)
[ 3.947601] Empty flash at 0x00158f44 ends at 0x00159000
[ 3.951690] VFS: Mounted root (jffs2 filesystem).
[ 3.952026] Freeing init memory: 108K

[penguinbait]

Ah-HA

This is why it was only happening to me once and a while, its all about finger placement when turning on. I can confirm the same behavior, I can reproduce at will.

The nasty part is its not just that middle key, the zoom key closest to the power button will also cause this to happen. That is the one that would get me now and then, good find, it was driving me nuts, seemed like it was only happening to me when I actually wanted to choose.

OK - - So the bootmenu package is working then, I think its good right???:D

[midiwall]

OK - - So the bootmenu package is working then, I think its good right???:DYou betcha'! I think it RAWKZ! :)


THANK YOU FANOUSH!

[penguinbait]

Just watch the fat fingers on the power up!!! :D :D

Thanks Fanoush!

Now we need kbdd ;) working the pairing is done by OS now, how do I hook kbbd in? I tried installing it but it did not seem to work for me. Also I have an addition that I want to get added into kbbd. Its for the bgp100 bluetooth gamepad, mlvj (user here) made the changes, I have a copy of his source, I would like to pass along to you.

Here is a copy of his source and binary to get bgp100 gamepad working on 770. I loved using this with mame, I would love to get this working on the n800. I will test anything.

I dont want to sound pushy, I have no idea what you are working on or what your priorities are or even if you plan to keep supporting kbdd. That said I wanted to get you a copy of the source, and the rest of the world, so hopefully it can be incorporated into future releases. I also wanted to post the working bin, for any 770 users that may want to use a bgp100 gamepad. I am not sure if it was made available to anyone anywhere previously.

http://www.internettablettalk.com/forums/showthread.php?t=2666&highlight=bgp100

[penguinbait]

Thats right, we need uinput.ko, I used to compile directly on my 770, where can I download the kernel source, and make and gcc and everything else for n800, has it been released?

[penguinbait]

FYI
input 1 on the n800 is 169, for the button on the headphones/mic

[fanoush]

thanks guys, so it is #2 everytimes but pressed key makes in not working. But when you boot completely keys work in this case? If yes then there is a way to recover. Well, I hope I get the device soon.

As for kbdd, I have uinput.ko already but have not it included in kbdd yet. Will get to real computer tomorrow.I hope there won't be similar surprises with kbdd on N800.

[midiwall]

thanks guys, so it is #2 everytime but pressed key makes in not working. But when you boot completely keys work in this case?Yes, you have it right!

The pressed key at boot seems to hang up the controller, but once the machine comes up all the way, all of the keys are fine. So it could be as "easy" as finding a way to reset the key input controller and doing that before the bootmenu comes up.


Good luck!

[penguinbait]

Great, again I am happy to test anything. I am curious can you (fanoush) reproduce booting problem, while on the 770, with an additional key pressed during initial power up?

Are they getting you one from Nokia at a discount?? They should be!!!!!

Any chance at getting the bgp100 incorporated into new release???

Thanks a lot!!!

[fanoush]

Great, again I am happy to test anything. I am curious can you (fanoush) reproduce booting problem, while on the 770, with an additional key pressed during initial power up?

There is no such problem on N770 or I never noticed, pressing keys early in boot means they are ignored but later in menu they work fine.

Are they getting you one from Nokia at a discount??
We'll see. Criteria here http://maemo.org/maemowiki/N800DeveloperDeviceProgram look promising.


Any chance at getting the bgp100 incorporated into new release???

I have uploaded newer kbdd archive with added uinput.ko module for N800 kernel. I have no time for recompiling kbdd or extend README (already sumbitted to me by ascherjim long time ago, sorry Jim). If you have bt keyboard working with kbdd, please test input method switching (i.e. is vkbd disabled when bt kbd is connected?). I'm not sure this will work in IT2007. http://fanoush.wz.cz/maemo/#kbdd

[richie]

There is no such problem on N770 or I never noticed, pressing keys early in boot means they are ignored but later in menu they work fine.

Just remembered, didn't someone from Nokia mention on maemo developers list about having bootmenu installed by default on new devices or os releases. Obviously it is not preinstalled, but it would be nice.

Rich

[penguinbait]

Two Things -- Thanks Fanoush, I seem to be saying that alot lately. The kbdd package worked great, I just switched the binary with the bgp100 one and my gamepad is running. Thanks !!

[Arch]

Hi
I have just got an N800 and getting used to a linux environment so I'm sorry if I have made an elementary mistake but I get the following error message when trying to initiate the initfs_flash command. I have ITOS 2007 version 2.2006.51.6 but not sure if there are other prerequisites.


~/MyDocs/Install/initfs_flasher $ ./initfs_flash
cal_read_block(r&d_mode): size zero, block not found?
Enable RD mode if you want to break your device
~/MyDocs/Install/initfs_flasher $

Thanks for any assistance and apologise if the answer is as simple as reading another post that I have been unable to find.

Arch

[penguinbait]

First you need to become root

install becomeroot

then launch xterm

run

sudo gainroot

then use initfs

[fanoush]

run
sudo gainroot

This is not strictly needed, the initfs_flash script does it itself. But yes, you need 'sudo gainroot' method working. Installing becomeroot is the easiest way.

[Arch]

Thanks for the quick response guys I had a feeling I needed to install becomeroot but am following instructions verbatim until I am more comfortable in the environment, especially as you warn that these tools can be dangerous for your device.

The initfs_flash ran perfectly and I saved your example N800 Bootconf so it was included in the image. Now all I have to do is follow the instructions penguinbait has on creating a backup boot card and look into what Sardine/Herring are all about:).

Thanks again for your support.

Arch

[screener]

i was trying to install this software on my N800 so i can boot from the card inside the N800 i dont know if it was card1 or card2 any way this is what i did and what i got:

ds@Central:~/initfs_flasher$ sudo ./initfs_flash

=== Flasher for initfs with onscreen bootmenu ===

For safe flashing please do the following:

- close all aplications (to free available RAM and prevent system crash)
- disconnect from network (to prevent system crash)
- make sure you have at least 5MB free disk space in flasher directory
- make sure you know how to reflash device in usual way if this fails

Are you sure to continue? (yes/no) : yes

Create backup of current initfs (yes/no) : yes
mount: special device /dev/mtdblock3 does not exist
*** creating initfs.orig.jffs2 ...
/home/ds/initfs_flasher/mkfs.jffs2: 1: Syntax error: word unexpected (expecting ")")
umount: initfs: not mounted
ls: initfs.orig.jffs2: No such file or directory
Press enter to continue

Part 1 - Preparing initfs.bootmenu.jffs2 image
*** copying current initfs ...mount: special device /dev/mtdblock3 does not exist
umount: mnt: not mounted
done.
If you remove extra stuff you may write to initfs and customize bootmenu.
Remove unneeded extra (and factory testing) stuff? (yes/no) : yes
*** removing extra stuff ...
cut: initfs/etc/initfs_version: No such file or directory
!!! unknown initfs version , cannot install bootmenu
Cannot find initfs.bootmenu.jffs2, something failed, nothing flashed.
ds@Central:~/initfs_flasher$



sorry i dont know much about technical things . . . i'm just a normal user but looking forward to learn more and more

thanx

[fanoush]

see http://maemo.org/maemowiki/HowTo_EASILY_Boot_From_MMC_card

I think the problem is with using sudo
$ sudo ./initfs_flash
It is not supposed to be run like this.

Solution is to first get to the root shell (whatever way you prefer) an then run it directly as root. Preferred way is to install becomeroot as described in the guide (or try just clicking this http://eko.one.pl/maemo/dists/mistral/user/binary-armel/becomeroot_0.1-2_armel.deb ).

If you have becomeroot installed you can run the script directly, it runs 'sudo gainroot' for you automatically.

ds@Central:~/initfs_flasher$ ./initfs_flash
Root shell enabled
...
...

[screener]

i did what you told me but ?? in my computer it asks me for a password and when i put the root pass for my computer:
sudo: gainroot: command not found


i know that this is too much for you . . . and i'm sorry about it . . . and if you want know what i use . . it's ubuntu 6.10 if it would mater ?

thanx

[TA-t3]

You need the 'becomeroot' package installed, it contains gainroot.
Edit: And it's the Nokia device we talk about here.. I noticed you mentioned Ubuntu, that would be your PC and that's not it.

[screener]

i was thinking that you do the steps on the computer with the nokia pluged in using the usb. . . . oh thats really bad for me

sorry

very bad

any way i have gain root i will try again

thanks

but do i have to have the card ready from before ?

[fanoush]

Hell, I'm not going to install bootmenu yet, even with 15 years of Linux experience
It is good to be cautious but there is really nothing so dangerous about it. 15 years are not really needed :-)

[fpp]

Yup. I just did it following sebastian's Howto and it went just fine :-)

[screener]

well to say it out i used linux for 7 years but nothing extra here just a normal user thats way i wana do this to learn more . . . and thats way i got the n80 . . . to use it for work and to have fun with it and to learn more about linux in all shapes and sizes . . . any way thanks man for your advice ,but i think i will go ahead with doing it

So i have this 1G card that i wana use for boot i want to use it inside the device . . . how do i partition it from my computer and how much is every partition and what kind ??

thanx all for your help

[penguinbait]

I don't want to come across as patronizing or anything, but before you start changing your device in such a fundamental way you really really need to have a clear mental picture of exactly how things are working.. you need to know how it works currently, what the changes are doing, and how it's going to work afterwards. Until you know enough about these things I would stay clear and leave the tablet as it is, or you risk ending up with a useless device.

Hell, I'm not going to install bootmenu yet, even with 15 years of Linux experience.. from back when the official way to set up the hard disk boot config was to edit byte location 508 on the disk with a binary hex editor..! :D

cmon, don't be scared, it does not touch anything that can not be fixed by a reflash.

[screener]

i dont want to sound scared or anything but . . . . i got the flasher 3.0 but also dont know how to use it. ha ha

[screener]

can someone please help me with the card coz i just deleted the card and i just cant get it back coz every time i wana format it it automounts so i could not format it using gparted . . . help

[schmots]

You can format it from the device. Its not that hard. http://maemo.org/maemowiki/HowTo_EASILY_Partition_your_MMC_card

[screener]

yes i know but when i do this "apt-get install e2fsprogs"
nothing comes up . . . sorry . . . what i wanted to say is that the software is not there to be installed coz maybe i dont have the repo that has it and really i dont know which one is it . . .

[schmots]

That link also has a link to "get root" you have to add those repos first and install those apps.. as for becomeroot.. you can't pull from that repository in an n800 (at least I couldn't) for some reason, but you can use the browser to go there, download the deb and open it in application manager.

[screener]

Hey look what went wrong here ??

This is what i did to install:

~ $ cd MyDocs
~/MyDocs $ tar zxvf initfs_flasher.tgz
initfs_flasher
initfs_flasher/nanddump
initfs_flasher/nandwrite
initfs_flasher/to_remove.lst
initfs_flasher/initfs_flash
initfs_flasher/mkfs.jffs2
initfs_flasher/flash_eraseall
initfs_flasher/initfs.osso-n770.2006-25.tgz
initfs_flasher/initfs.osso-RX-34.2006-51.tgz
initfs_flasher/README.txt
initfs_flasher/bootmenu.sh
initfs_flasher/bootmenu.conf.n770.example
initfs_flasher/bootmenu.conf.n800.example
initfs_flasher/initfs.osso-n770.2006-38.tgz
initfs_flasher/initfs.osso-n770.2006-48.tgz
~/MyDocs $ cd initfs_flasher
~/MyDocs/initfs_flasher $ sudo gainroot
Root shell enabled


BusyBox v1.1.3 (Debian 3:1.1.3-3.osso17) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/home/user/MyDocs/initfs_flasher # ./initfs_flasher
/bin/sh: ./initfs_flasher: not found
/home/user/MyDocs/initfs_flasher #



?? What is going on??

[screener]

by the way i got my card back i stoped the automount on my pc and formated the card in fat16

[schmots]

try
sh initfs_flasher

[screener]

/home/user/MyDocs/initfs_flasher # sh initfs_flasher
sh: Can't open initfs_flasher


?? Do i need somthing other than this, like another software ??

[schmots]

only thing I can think of (I havn't tried this yet.. was planning on trying it tonight) Is to untar as root
maybe its a permission error.. now normally root should have full rights.. but only if it takes them.
second try chmod a+x initfs_flasher and see if that helps

[fanoush]

?? Do i need somthing other than this?
yes, brain and basic skills like reading ;-)
you got the script name wrong

[screener]

Name wrong ?? where ??

i have googled "brain" . . . but the thing is . . . i cant download the man-file for it . . . i have to learn reading first ;-)

man sorry i'm doing all this on the move with the N800 it's 2:19 AM here and i did not get any sleep from yesterday so sorry "knowing that i looked again but not find the wrong name" wait till i start asking you about gnokiirc and using the n80 with the n800 to connect to the net !!

i will go home now and try it from there

thanx man

[Milhouse]

Suggest you get some sleep before you continue - the answer to your problem can be found by looking at the list of files you gave in post #80 :)

[screener]

i got home :-)

and i found what went wrong it's initfs_flash not flasher

i told u i neeeeeed to sleep

[screener]

ok now i have installed the software

but i cant format the card i have the e2fsprogs but the umount mmc1 dose not work i hade to do mmc2, but then when i do sfdisk i get a sfdisk fatal error cannot find /dev/mmcb1k0
knowing that it worked last night but i was dead ?? i have a 1G card in the internal slot and thats where i wana boot from ??

thanx

[screener]

hey look at this i went to the installed applications and . . . i did not find e2fsprogs ?? do i gave to apt-get install every time i wana format a card ??
or is it there but i cant see it . . . ??

you know i really do have a reading problem

[screener]

Ok . . . Iwent to get it again and i got this
/home/user # apt-get install e2fsprogs
Reading package lists... Done
Building dependency tree... Done
e2fsprogs is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 0B of additional disk space will be used.
Setting up samba (3.0.22-3) ...
/var/lib/dpkg/info/samba.postinst: /var/lib/dpkg/info/samba.postinst: 123: update-inetd: not found
dpkg: error processing samba (--configure):
subprocess post-installation script returned error exit status 127
Errors were encountered while processing:
samba
E: Sub-process /usr/bin/dpkg returned an error code (1)

[schmots]

Samba shouldn't be keeping you from doing anything.

What do you get when you run

sfdisk --help

Also try
sfdisk /dev/mmc (but then hit tab the two arrors key) it will autocomplete up to where the devices differ which is the 0 and the 1, 0 internal, 1 external.. type a 0 and hit enter.

[screener]

when i do the other step's i get trailing junk after number what is that ??

i dont know but it dose not look like part of the proses and if not how do i get to bypass it

by the way the bootmenu is working i can scroll and every thing :-)

[screener]

Ok ok i got over this and made the thing work !!

but when i do this part # insmod /mnt/initfs/lib/modules/current/ext2.ko

it gives me this
insmod: cannot open module '/mnt/initfs/lib/modules/current/ext2.ko' No such file or directory

and yes i was root ??

i think i did not make ext2 partition

thanks again

[screener]

i made a ext2 partition with gparted with 487 mb's but again ??

insmod: cannot open module '/mnt/initfs/lib/modules/current/ext2.ko' No such file or directory

?? what am i doing ?? can some one help me :-(

>>>

i think when i'm done with this and the gnokiirc file and the dun thing to connect the n800 with bluetooth to a phone, i'm gona make the ultimate HowTo for noob's like me with a step by step all the way to the end

i have a server for hosting so i think i have to go and look for a domain

[Milhouse]

try


# insmod /mnt/initfs/lib/modules/2.6.18-omap1/ext2.ko


On my N800, /mnt/initfs/lib/modules/current is sym linked to /lib/modules/2.6.18-omap1 which doesn't exist.

[schmots]

yeah the current link doesn't work so good.. after you type out moduels/ just hit tab.. it will auto fill in the only option

[screener]

I did every thing from the start and did the tab thing but i got this

~ $ sudo gainroot
Root shell enabled


BusyBox v1.1.3 (Debian 3:1.1.3-3.osso17) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/home/user # insmod /mnt/initfs/lib/modules/2.6.18-omap1/
insmod: cannot mmap `/mnt/initfs/lib/modules/2.6.18-omap1/': No such device
/home/user # insmod /mnt/initfs/lib/modules/current/ext2.ko
insmod: cannot open module `/mnt/initfs/lib/modules/current/ext2.ko': No such file or directory
/home/user # insmod /mnt/initfs/lib/modules/2.6.18-omap1/ext2.ko
insmod: cannot insert `/mnt/initfs/lib/modules/2.6.18-omap1/ext2.ko': Unknown symbol in module (-1): No such file or directory

[lite]

You did not load the module mbcache before loading ext2 - try

insmod /mnt/initfs/lib/modules/2.6.18-omap1/mbcache.ko

first!

Did the same mistake just two minutes ago, oh dear! Now fs mounted
;)

[torx]

Is the bootmenu for the new firmware coming out soon?

[fanoush]

Hi, just to let you know that the initfs flasher now supports new 4.2007 firmware. http://fanoush.wz.cz/maemo/#initfs

Tried to boot old system on MMC, it works but touchscreen is off and cannot be calibrated properly. Probably the improved touchscreen sensitivity in newer linux kernel changed touchscreen driver protocol/data somehow so older rootfs cannot cope with it.

[fanoush]

huh, after few calibrations in older rootfs on mmc card and few reboots touchscreen works fine both in old and new rootfs, that's good :-)

[torx]

Hey the initfs works great. I noticed some improvements too, like the countdown timer.

Thanks alot!

[SeRi@lDiE]

Sweet!
Thanks!