Menu

Main Menu
Talk Get Daily Search

Member's Online

    User Name
    Password

    Help - how to get U-boot command to boot original kernel (as now stucked at loading v44 power-kernel)?

    Reply
    Page 4 of 10 | Prev |   2     3   4   5     6   | Next | Last
    Kenny1001 | # 31 | 2010-11-11, 12:34 | Report

    Originally Posted by RobbieThe1st View Post
    Look, guys. You generally -never- have to press U!

    All you have to do is:
    With your n900 OFF and unplugged, run the flasher command.
    With the flasher "waiting", plug your n900 into USB. It will automatically boot, then flash. NO U KEY NEEDED.
    doens't work here.
    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.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Matan | # 32 | 2010-11-11, 12:35 | Report

    Originally Posted by Stskeeps View Post
    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).
    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.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    009N | # 33 | 2010-11-11, 12:42 | Report

    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 )

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by 009N; 2010-11-11 at 12:45.

     
    vertyogo | # 34 | 2010-11-11, 12:50 | Report

    ERROR: can't get kernel image!

    Edit | Forward | Quote | Quick Reply | Thanks

     
    vertyogo | # 35 | 2010-11-11, 13:10 | Report

    "so let's see what happens when the battery is fully charged via PC USB (with no high hope though ... :-x )"

    nothing

    Edit | Forward | Quote | Quick Reply | Thanks

     
    009N | # 36 | 2010-11-11, 13:11 | Report

    Originally Posted by Matan View Post
    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
    ....
    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?

    Edit | Forward | Quote | Quick Reply | Thanks

     
    vertyogo | # 37 | 2010-11-11, 13:34 | Report

    n900 and should work without batteries, just connected to the charge? works for me .. actually it's the only plus

    Edit | Forward | Quote | Quick Reply | Thanks

     
    009N | # 38 | 2010-11-11, 13:35 | Report

    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 ....
    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?

    Edit | Forward | Quote | Quick Reply | Thanks

    Last edited by 009N; 2010-11-11 at 16:21. Reason: Correct the terminal output

     
    mankir | # 39 | 2010-11-11, 13:41 | Report

    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!

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Matan | # 40 | 2010-11-11, 13:49 | Report

    Originally Posted by 009N View Post
    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?
    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.

    It is better that the device is not plugged.

    Edit | Forward | Quote | Quick Reply | Thanks

     
    Page 4 of 10 | Prev |   2     3   4   5     6   | Next | Last
vBulletin® Version 3.8.8
Normal Logout