Active Topics
-
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (841)
to Alternatives by omniteal@pm.me - 5 hrs, 10 mins ago -
List of well performing apps on Leste (34)
to Maemo 7 / Leste by biketool - 16 hrs, 7 mins ago -
Maemo repository (5)
to Community by dredlok706 - 2 days, 11 hrs ago -
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 2 days, 13 hrs ago -
Porting apps to Leste (41)
to Maemo 7 / Leste by Arno_11 - 3 days, 7 hrs ago -
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 4 days, 19 hrs ago - more...
|
2010-11-11
, 12:35
|
|
Posts: 1,224 |
Thanked: 1,763 times |
Joined on Jul 2007
|
#32
|
Originally Posted by Stskeeps
This should not really be a problem. kernel-power does not remove the modules of the stock kernel, and it uses a different uname, so its modules are in a different directory, not overwriting stock modules.
Generally:
* Installation of kernel-power -and then- install uboot-pr13 WILL cause a reboot loop (You're installing a kernel where the modules doesn't match).
__________________
My repository
"N900 community support for the MeeGo-Harmattan" Is the new "Mer is Fremantle for N810".
No more Nokia devices for me.
My repository
"N900 community support for the MeeGo-Harmattan" Is the new "Mer is Fremantle for N810".
No more Nokia devices for me.
|
|
2010-11-11
, 12:42
|
|
Posts: 152 |
Thanked: 58 times |
Joined on Oct 2010
@ void
|
#33
|
okay I've exhausted all combinations:
Command: flasher-3.5.exe -F RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin --flash-only=kernel -f -R
(Windows 7, cmd with administrator previlege)
#1
Battery out => battery back in => slide open keyboard => press "U" => start flasher on PC => plug n900 via usb => greetings, "starting kernel"
#2
Battery out => battery back in => keyboard not slide open => start flasher on PC => plug n900 via usb => greetings, "starting kernel"
#3
Battery out => battery back in => slide open keyboard => press "U" => plug n900 via usb => start flasher on PC => greetings, "starting kernel"
#4
Battery out => battery back in => keyboard not slide open => plug n900 via usb => start flasher on PC => greetings, "starting kernel"
so uboot loads no matter how.
as some hinted above perhaps it has to do with the battery and use PC usb to charge instead of the wall charger. hmm maybe. this is the last method I've seen so far. so let's see what happens when the battery is fully charged via PC USB (with no high hope though ... :-x )
Last edited by 009N; 2010-11-11 at 12:45.
Command: flasher-3.5.exe -F RX-51_2009SE_20.2010.36-2_PR_COMBINED_MR0_ARM.bin --flash-only=kernel -f -R
(Windows 7, cmd with administrator previlege)
#1
Battery out => battery back in => slide open keyboard => press "U" => start flasher on PC => plug n900 via usb => greetings, "starting kernel"
#2
Battery out => battery back in => keyboard not slide open => start flasher on PC => plug n900 via usb => greetings, "starting kernel"
#3
Battery out => battery back in => slide open keyboard => press "U" => plug n900 via usb => start flasher on PC => greetings, "starting kernel"
#4
Battery out => battery back in => keyboard not slide open => plug n900 via usb => start flasher on PC => greetings, "starting kernel"
so uboot loads no matter how.
as some hinted above perhaps it has to do with the battery and use PC usb to charge instead of the wall charger. hmm maybe. this is the last method I've seen so far. so let's see what happens when the battery is fully charged via PC USB (with no high hope though ... :-x )
Last edited by 009N; 2010-11-11 at 12:45.
|
|
2010-11-11
, 12:50
|
|
Posts: 10 |
Thanked: 0 times |
Joined on Nov 2010
@ Moscow is a big city you know, see you at the maemos.ru нам год
|
#34
|
ERROR: can't get kernel image!
|
|
2010-11-11
, 13:10
|
|
Posts: 10 |
Thanked: 0 times |
Joined on Nov 2010
@ Moscow is a big city you know, see you at the maemos.ru нам год
|
#35
|
"so let's see what happens when the battery is fully charged via PC USB (with no high hope though ... :-x )"
nothing
nothing
|
|
2010-11-11
, 13:11
|
|
Posts: 152 |
Thanked: 58 times |
Joined on Oct 2010
@ void
|
#36
|
Originally Posted by Matan
Now trying...
Here's a guide for people who got "starting kernel" heng with power44.
http://my.svgalib.org/770/n900/u-boot/u-boot-n900.zip
....
Matan, should the microsd be fat16 or fat32 and with or without boot flag? Thanks.
Also should the device be plugged into PC USB or charger or nothing?
|
|
2010-11-11
, 13:34
|
|
Posts: 10 |
Thanked: 0 times |
Joined on Nov 2010
@ Moscow is a big city you know, see you at the maemos.ru нам год
|
#37
|
n900 and should work without batteries, just connected to the charge? works for me .. actually it's the only plus
|
|
2010-11-11
, 13:35
|
|
Posts: 152 |
Thanked: 58 times |
Joined on Oct 2010
@ void
|
#38
|
okay here is my initial result.
microsd as mmc, fat 16@3rd partition, matan's stuff@3rd partition
open the keyboard
plug in the charger
device power up itself
press some key to intercept booting to get the prompt
Here is what I saw. It's dam painful to stare at those tiny prints, and without backlight ....
It's the same story. Still stuck at uboot. So what's next?
Last edited by 009N; 2010-11-11 at 16:21. Reason: Correct the terminal output
microsd as mmc, fat 16@3rd partition, matan's stuff@3rd partition
open the keyboard
plug in the charger
device power up itself
press some key to intercept booting to get the prompt
Here is what I saw. It's dam painful to stare at those tiny prints, and without backlight ....
Code:
MAP3 RX-51 # mmc init mmc1 is available MAP3 RX-51 # run loadbootscript reading boot.scr 133 bytes read MAP3 RX-51 # run bootscript Running bootscript from mmc ... Executing script at 82000000 mmc1 is available Loading uImage 1746752 bytes read ## Booting kernel from legacy Image at 82000000 Image name : Kernel PR1.3 Image type : ARM Linux Kernel Image (uncompressed) Data size : 1746688 bytes = 1.7 MiB Load address : 80008000 Entry point : 80008000 Verifying checksum : ok Loading kernel image : ok Image existing stage at 0x80000100 Starting kernel ...
It's the same story. Still stuck at uboot. So what's next?
Last edited by 009N; 2010-11-11 at 16:21. Reason: Correct the terminal output
 |
|
2010-11-11
, 13:41
|
|
Posts: 276 |
Thanked: 224 times |
Joined on Dec 2009
@ Frankfurt, Germany
|
#39
|
Followed this guide with no problems: http://talk.maemo.org/showpost.php?p...7&postcount=21
Also reinstalled uboot-pr13, as i got i kernel-panic message when i tried to boot without run noloboot command, but multiboot is working fine!
Also reinstalled uboot-pr13, as i got i kernel-panic message when i tried to boot without run noloboot command, but multiboot is working fine!
__________________
MOD-Package: http://talk.maemo.org/showthread.php?t=42415
MOD-Package: http://talk.maemo.org/showthread.php?t=42415
|
|
2010-11-11
, 13:49
|
|
Posts: 1,224 |
Thanked: 1,763 times |
Joined on Jul 2007
|
#40
|
Originally Posted by 009N
The files should be on a fat partition that is the third partition /dev/sdb3 in Linux if in usb SD card reader. This is how an SD prepared for meego boot is partitioned. You can use another partition, but then you need to run the commands manually.
Now trying...
Matan, should the microsd be fat16 or fat32 and with or without boot flag? Thanks.
Also should the device be plugged into PC USB or charger or nothing?
It is better that the device is not plugged.
__________________
My repository
"N900 community support for the MeeGo-Harmattan" Is the new "Mer is Fremantle for N810".
No more Nokia devices for me.
My repository
"N900 community support for the MeeGo-Harmattan" Is the new "Mer is Fremantle for N810".
No more Nokia devices for me.
actually nothing works...
for me the command
flasher-3.5.exe -F RX-51_2009SE_10.2010.13-2.VANILLA_PR_EMMC_MR0_ARM.bin -f -R also doesnt work.
I don't want to nag on dev to be clear.