Active Topics
-
Maemo 20th Anniversary (4)
to Brainstorm by teroyk - 2 hrs, 40 mins ago -
Nokia Booklet 3G (RX-75) Drivers (64)
to Alternatives by teroyk - 2 hrs, 56 mins ago -
Porting apps to Leste (46)
to Maemo 7 / Leste by teroyk - 2 days, 6 hrs ago -
Maemo repository (8)
to Community by Maemish - 6 days ago - more...
ascherjim |
2007-03-21
, 22:08
|
|
Posts: 450 |
Thanked: 16 times |
Joined on Mar 2006
|
#131
|
Fanoush: You are right (of course). The /mnt/initfs diectory was full. I have also (belatedly, of course) read the README file, and from what I have now learned I believe that, again, "discretion being the better part of valor," I'll not proceed any further with my experimentation in this regard with the 770. I take it that there is insufficient space in the /mnt/initfs directory for me to configure my own bootmenu.conf file to use in place of the bootmenu.sh file that's currently there. I am even more eagerly now looking forward to receipt of my N800, which I have regretted having to purchase. Regards, Jim
|
|
2007-03-21
, 22:08
|
|
Posts: 2,152 |
Thanked: 1,490 times |
Joined on Jan 2006
@ Czech Republic
|
#132
|
Also the README is not clear about it, for customization you need to copy example to file named bootmenu.conf
and then edit it to your liking (i.e add your own ID and other parameters). The ID you choose can be used as root device for cal-tool or nokia flasher so it is preselected as default choice.
initfs flashing script searches for bootmenu.conf in current directory. If found it asks you if it should be added to final initfs image.
Code:
cp bootmenu.conf.n800.example bootmenu.conf
initfs flashing script searches for bootmenu.conf in current directory. If found it asks you if it should be added to final initfs image.
|
|
2007-03-21
, 22:28
|
|
Posts: 2,152 |
Thanked: 1,490 times |
Joined on Jan 2006
@ Czech Republic
|
#133
|
Originally Posted by ascherjim
Yes if you opted to not to remove extra stuff. But still you can prepare the file and let the flasher script include it in final image. That way it should fit even when not removing the extra stuff. You just can't modify it later (without reflashing initfs again). If extra stuff it removed (and it really is not so important and you can get it back from backup image or original firmware) then you can edit it directly in /mnt/initfs couple of times. With editing bootmenu.sh inplace (which is much larger) I think I did it like 5 times until I saw error and got the file truncated, bootmenu.conf is smaller so it should be better. I can no longer test this limit since I enlarged initfs partition and shrinked rootfs in some experiment and don't know how to get back to smaller size. I like bigger initfs partition but cannot test this 'initfs almost full' situation with n770 properly anymore.
The /mnt/initfs diectory was full.
|
|
2007-03-22
, 00:04
|
|
Posts: 450 |
Thanked: 16 times |
Joined on Mar 2006
|
#134
|
Fanoush: Thanks for the excellent advice in this matter, which I will be following up on. Two other matters:
1) Your README has a slight but possibly misleading typographical error:
ROOT DEVICE
"root device can be set either by linux flasher on PC over USB cable"
Shouldn't that "on" be "or"?
2) In your instructions for booting from MMC, you state:
"The first time I tried this on my N800 it led to continuous reboots 30-90 seconds after booting. Trying it a second time on a clean install (directly after flashing and erasing everything already on the device) worked fine."
Does this mean that you don't recommend installing various applications on the flash operating system (i.e., kbdd, fbreader) prior to copying it to the MMC, which would be a means of saving having to reinstall such applications second times in both (or more) operating systems?
1) Your README has a slight but possibly misleading typographical error:
ROOT DEVICE
"root device can be set either by linux flasher on PC over USB cable"
Shouldn't that "on" be "or"?
2) In your instructions for booting from MMC, you state:
"The first time I tried this on my N800 it led to continuous reboots 30-90 seconds after booting. Trying it a second time on a clean install (directly after flashing and erasing everything already on the device) worked fine."
Does this mean that you don't recommend installing various applications on the flash operating system (i.e., kbdd, fbreader) prior to copying it to the MMC, which would be a means of saving having to reinstall such applications second times in both (or more) operating systems?
 |
|
2007-03-22
, 01:32
|
|
Posts: 919 |
Thanked: 37 times |
Joined on Aug 2006
@ /dev/null
|
#135
|
Originally Posted by ascherjim
Yea I wanted to ask the same question... I am sort of experiencing the same issue... So that means I am going to need to reflash my device and recopy my fs...
Fanoush:
2) In your instructions for booting from MMC, you state:
"The first time I tried this on my N800 it led to continuous reboots 30-90 seconds after booting. Trying it a second time on a clean install (directly after flashing and erasing everything already on the device) worked fine."
Does this mean that you don't recommend installing various applications on the flash operating system (i.e., kbdd, fbreader) prior to copying it to the MMC, which would be a means of saving having to reinstall such applications second times in both (or more) operating systems?
|
|
2007-03-22
, 01:56
|
|
Posts: 919 |
Thanked: 37 times |
Joined on Aug 2006
@ /dev/null
|
#136
|
I also try to install applications and I was unable to it keept giving me errors... I am going to try a fresh install later today..
|
|
2007-03-22
, 08:51
|
|
Posts: 2,152 |
Thanked: 1,490 times |
Joined on Jan 2006
@ Czech Republic
|
#137
|
Originally Posted by ascherjim
no, linux flasher runs on the PC and uses USB cable to communicate with the tablet. Second option is cal-tool which runs directly on the tablet. Is using 'on' OK in this context or is using 'in' or something else better?
1) Your README has a slight but possibly misleading typographical error:
ROOT DEVICE
"root device can be set either by linux flasher on PC over USB cable"
Shouldn't that "on" be "or"?
Originally Posted by ascherjim
In fact this sentence is not mine. This is Wiki, anyone can edit it including you. You can click 'Get Info' link on wiki page and then select versions and click 'Diff' to see who added what.
2) In your instructions for booting from MMC, you state:
"The first time I tried this on my N800 it led to continuous reboots 30-90 seconds after booting. Trying it a second time on a clean install (directly after flashing and erasing everything already on the device) worked fine."
Originally Posted by ascherjim
I haven't seen this issue on my device yet so I guess it is safe to clone the system anytime (and I do it like this). If the system boots OK from flash it should in theory boot also from mmc if the copy is exact (i.e. no mistake is made while cloning). This theory works for me on N770 both with IT2006 and also IT2007 (hacker edition) which is made from N800 firmware. I still don't have big card for my N800 so I'm not sure how cloned system works on real device. There may be differences due to two mmc slots (which is not same as N770 with IT2007).
Does this mean that you don't recommend installing various applications on the flash operating system (i.e., kbdd, fbreader) prior to copying it to the MMC, which would be a means of saving having to reinstall such applications second times in both (or more) operating systems?
I know some people reported this reboots after cloning but it can still be some mistake when doing it. Or it can be also some specific installed application which does this. I guess Canola does some funny things with the device but I never installed it so I don't know for sure. Maybe it is related to scanning mmc cards for media files after boot.
|
|
2007-03-22
, 13:15
|
|
Posts: 450 |
Thanked: 16 times |
Joined on Mar 2006
|
#138
|
Fanoush: You've provided us with lots of good information to think about, and act on as appropriate
1) "Is using 'on' OK in this context or is using 'in' or something else better?"
Thanks for the clarification here. Now that I understand it better, I believe that the issue does not concern whether "on", "or" or "in" would be better, but rather the use of the word "either." I assumed that you meant "or" because of the "either." Am I making myself sufficiently clear here?
2) "I haven't seen this issue on my device yet so I guess it is safe to clone the system anytime.... If the system boots OK from flash it should in theory boot also from mmc if the copy is exact (i.e. no mistake is made while cloning).... There may be differences due to two mmc slots...."
As you haven't had opportunity yet to pursue this issue of a large card and the N800's two slots, I will be experimenting with all this when I get my N800 and report back to you and the forum, and no doubt also seek further advice. From what I can make out from your README, I could possibly also have multi "distros" on just one card (if big enough) and boot to each of their separate ext2 partitions from your boot menu, and wouldn't even need to effect this with separate cards. Anyway, much to consider. Thanks again. Regards, Jim
1) "Is using 'on' OK in this context or is using 'in' or something else better?"
Thanks for the clarification here. Now that I understand it better, I believe that the issue does not concern whether "on", "or" or "in" would be better, but rather the use of the word "either." I assumed that you meant "or" because of the "either." Am I making myself sufficiently clear here?
2) "I haven't seen this issue on my device yet so I guess it is safe to clone the system anytime.... If the system boots OK from flash it should in theory boot also from mmc if the copy is exact (i.e. no mistake is made while cloning).... There may be differences due to two mmc slots...."
As you haven't had opportunity yet to pursue this issue of a large card and the N800's two slots, I will be experimenting with all this when I get my N800 and report back to you and the forum, and no doubt also seek further advice. From what I can make out from your README, I could possibly also have multi "distros" on just one card (if big enough) and boot to each of their separate ext2 partitions from your boot menu, and wouldn't even need to effect this with separate cards. Anyway, much to consider. Thanks again. Regards, Jim
|
|
2007-03-22
, 13:46
|
|
Posts: 2,152 |
Thanked: 1,490 times |
Joined on Jan 2006
@ Czech Republic
|
#139
|
Originally Posted by ascherjim
There is "or" . The full sentence is
Now that I understand it better, I believe that the issue does not concern whether "on", "or" or "in" would be better, but rather the use of the word "either." I assumed that you meant "or" because of the "either." Am I making myself sufficiently clear here?
"root device can be set either by linux flasher on PC over USB cable <step how to do it> or directly on device via cal-tool command <step how to do it>"
Maybe it is just too long and complex for one sentence.
|
|
2007-03-22
, 14:13
|
|
Posts: 450 |
Thanked: 16 times |
Joined on Mar 2006
|
#140
|
Fanoush: I've looked again at the README file and discovered the reason for my confusion regarding use of the word "either." You quote the sentence as:
"root device can be set either by linux flasher on PC over USB cable <step how to do it> or directly on device via cal-tool command <step how to do it>"
The fact that the <step how to do it> instructions occur on separate lines caused me to not read the ROOT DEVICE instruction as an intregal sentence. Sorry.
Also, presumably while you were sleeping last night (and I have to assume that you do sleep, though it's not always apparent from your prompt responses on the forum), I did try out your clarified instructions for copying the "bootmenu.conf.n770.example" file to "bootmenu.conf," which I then customized and reflashed, and the whole process worked fine on my 770. It was quite easy. Thanks again.
"root device can be set either by linux flasher on PC over USB cable <step how to do it> or directly on device via cal-tool command <step how to do it>"
The fact that the <step how to do it> instructions occur on separate lines caused me to not read the ROOT DEVICE instruction as an intregal sentence. Sorry.
Also, presumably while you were sleeping last night (and I have to assume that you do sleep, though it's not always apparent from your prompt responses on the forum), I did try out your clarified instructions for copying the "bootmenu.conf.n770.example" file to "bootmenu.conf," which I then customized and reflashed, and the whole process worked fine on my 770. It was quite easy. Thanks again.