Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (3)
to SailfishOS by edp17 - 2 hrs, 23 mins ago -
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 6 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 1 day, 19 hrs ago -
n770 youtube video (0)
to General by nmdv - 5 days, 18 hrs ago - more...
|
2013-06-01
, 12:27
|
|
Posts: 7 |
Thanked: 17 times |
Joined on May 2013
@ Bremen, Germany
|
#12
|
If you can type in special characters you can redirect the output of dmesg to a file using this command:
The log.txt will be created in the directory you are in at the moment you execute the command. You'll somehow need to access the file of course afterwards and I'm not sure if this is possible. If there's no option to scroll like you said you can also try:
Code:
dmesg > log.txt
Code:
dmesg | more
|
|
2013-06-01
, 13:09
|
|
Posts: 25 |
Thanked: 4 times |
Joined on Jan 2009
|
#13
|
Thanks, this works good -> I have log. Nano function good on this file, so I check it. Because I didn't find a way how to transfer it from N900 before battery drained, I re-write lines, where was not "Done", "Ok" or memory adress as postive result as this:
(without "positive" lines)
(without "positive" lines)
Code:
IRQ: Found an INTC at 0xfa200000 (revision 4.) with 96 interrupts Total of 96 interrupts on 1 active controller omap_hwmod: sr1_fck: missing clockdomain for sr1_fck omap_hwmod: sr2_fck: missing clockdomain for sr2_fck rotfd image is not intramfs (junk in compressed archive): looks like an initrd onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400 Faild to add route TPA6130A2 Headphone Left->Headphone Jack more than 100x is in log mentioned: i2c_omap i2c_omap.2: controller timed out
|
|
2013-06-01
, 15:05
|
|
Posts: 25 |
Thanked: 4 times |
Joined on Jan 2009
|
#14
|
I have one new observation.
When I try to update Vanilla in Update mode, it find and refuese the device connection. - the USB symbol is shown, I press the Enter on keyboard with command on Terminal and symbol of USB on N900 display is gone.
So, cold flash it cannot do, because it cannot see the device. But Vanilla cannot do, because it refuse it. After 2 minutes the device (if is in R&D mode) change on the screen - some information about kernel, product, hw-build are added (green font) and flashing with Vanilla STARTS! And ends with success.
But, the problem is stil the same - cannot boot the device, only NOKIA is shown.
When I try to update Vanilla in Update mode, it find and refuese the device connection. - the USB symbol is shown, I press the Enter on keyboard with command on Terminal and symbol of USB on N900 display is gone.
So, cold flash it cannot do, because it cannot see the device. But Vanilla cannot do, because it refuse it. After 2 minutes the device (if is in R&D mode) change on the screen - some information about kernel, product, hw-build are added (green font) and flashing with Vanilla STARTS! And ends with success.
But, the problem is stil the same - cannot boot the device, only NOKIA is shown.
|
|
2013-06-01
, 15:35
|
|
Posts: 7 |
Thanked: 17 times |
Joined on May 2013
@ Bremen, Germany
|
#15
|
Sorry, it's probably a dumb question, but you did press "u" while plugging in your N900, right? Otherwise I would try a different usb cable and a debian live cd. Since you can't even install the temporary nolo bootloader (which should always work) I'd try looking for the error elsewhere.
|
|
2013-06-01
, 16:28
|
|
Posts: 25 |
Thanked: 4 times |
Joined on Jan 2009
|
#16
|
Yes, I always press "u" and check if it is in Update Mode. No question is dumb in these thread.
Ok, I will try the different cable. Debians I use are different, but the same situatuin everywhere (when need to Cold Flash, still "no suitable device").
In fact, I see the problem in something "third". The Vanilla and Fiasco can be done quite without problems. But reflashing these two doesn't help and the problem is like before - boot looping with no result, restart, boot, nothing, restart, boot, nothing....Moreover the Cold Flash telling "no suitable device" - on Windows, and also on Ubuntu. What's the difference, between Vanilla/Fiasco flash and Cold Flash using Fiasco bin file?
What next is important to boot OS, instead eMMC, kernel?
What could cause loop booting with no result to infinity?
Last edited by Jackeye; 2013-06-01 at 16:31.
Ok, I will try the different cable. Debians I use are different, but the same situatuin everywhere (when need to Cold Flash, still "no suitable device").
In fact, I see the problem in something "third". The Vanilla and Fiasco can be done quite without problems. But reflashing these two doesn't help and the problem is like before - boot looping with no result, restart, boot, nothing, restart, boot, nothing....Moreover the Cold Flash telling "no suitable device" - on Windows, and also on Ubuntu. What's the difference, between Vanilla/Fiasco flash and Cold Flash using Fiasco bin file?
What next is important to boot OS, instead eMMC, kernel?
What could cause loop booting with no result to infinity?
Last edited by Jackeye; 2013-06-01 at 16:31.
|
|
2013-06-01
, 17:09
|
|
Posts: 578 |
Thanked: 994 times |
Joined on Dec 2012
|
#17
|
Maybe try this:
flasher-3.5 --enable-rd-mode --set-rd-flags=no-lifeguard-reset --set-rd-flags=no-omap-wd --set-rd-flags=no-ext-wd
and flash latest image once again or/and flash fb kernel and watch logs:
flasher-3.5 -f -b -k zImage-2.6.28-omap1-fb
flasher-3.5 --enable-rd-mode --set-rd-flags=no-lifeguard-reset --set-rd-flags=no-omap-wd --set-rd-flags=no-ext-wd
and flash latest image once again or/and flash fb kernel and watch logs:
flasher-3.5 -f -b -k zImage-2.6.28-omap1-fb
|
|
2013-06-01
, 17:23
|
|
Posts: 25 |
Thanked: 4 times |
Joined on Jan 2009
|
#18
|
Ok. I tried this on Windows. I'm downloading image of Ubuntu, until now - if use linux - run from Virtual Box. Here's the result, no fault:
Code:
C:\Program Files (x86)\Maemo\flasher-3.5>flasher-3.5 --enable-rd-mode --set-rd-f
lags=no-lifeguard-reset --set-rd-flags=no-omap-wd --set-rd-flags=no-ext-wd
flasher v2.5.2 (Sep 24 2009)
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
105.
Found device RX-51, hardware revision 2101
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2.003_PR_003
The device is now in R&D mode
C:\Program Files (x86)\Maemo\flasher-3.5>flasher-3.5 -F RX-51_2009SE_20.2010.36-
2_PR_COMBINED_MR0_ARM.bin -f -R
flasher v2.5.2 (Sep 24 2009)
SW version in image: RX-51_2009SE_20.2010.36-2_PR_MR0
Image 'kernel', size 1705 kB
Version 2.6.28-20103103+0m5
Image 'rootfs', size 185728 kB
Version RX-51_2009SE_20.2010.36-2_PR_MR0
Image 'cmt-2nd', size 81408 bytes
Version BB5_09.36
Image 'cmt-algo', size 519808 bytes
Version BB5_09.36
Image 'cmt-mcusw', size 5826 kB
Version rx51_ICPR82_10w08
Image '2nd', size 14720 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2217, 2218, 2219, 2220, 2120
Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2101, 2102, 2103
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2307, 2308, 2309, 2310
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2407, 2408, 2409, 2410
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2301, 2302, 2303, 2304, 2305, 2306
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2401, 2402, 2403, 2404, 2405, 2406
Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2104, 2105, 2106, 2107, 2108, 2109, 2110, 2111, 2112, 2
113, 2114, 2115, 2116, 2117, 2118, 2119
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2501, 2502, 2503, 2504, 2505, 2506
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2607, 2608, 2609, 2610
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2507, 2508, 2509, 2510
Version 1.4.14.9+0m5
Image '2nd', size 14720 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2201, 2202, 2203, 2204, 2205, 2206, 2207, 2208, 2209, 2
210, 2211, 2212, 2213, 2214, 2215, 2216
Version 1.4.14.9+0m5
Image '2nd', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
Image 'xloader', size 14848 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
Image 'secondary', size 109440 bytes
Valid for RX-51: 2601, 2602, 2603, 2604, 2605, 2606
Version 1.4.14.9+0m5
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
105.
Found device RX-51, hardware revision 2101
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2.003_PR_003
Sending xloader image (14 kB)...
100% (14 of 14 kB, avg. 3625 kB/s)
Sending secondary image (106 kB)...
100% (106 of 106 kB, avg. 13359 kB/s)
Flashing bootloader... done.
Sending cmt-2nd image (79 kB)...
100% (79 of 79 kB, avg. 11357 kB/s)
Sending cmt-algo image (507 kB)...
100% (507 of 507 kB, avg. 8905 kB/s)
Sending cmt-mcusw image (5826 kB)...
100% (5826 of 5826 kB, avg. 25223 kB/s)
Flashing cmt-mcusw... done.
Sending kernel image (1705 kB)...
100% (1705 of 1705 kB, avg. 21321 kB/s)
Flashing kernel... done.
Sending and flashing rootfs image (185728 kB)...
100% (185728 of 185728 kB, avg. 13792 kB/s)
Finishing flashing... done
CMT flashed successfully
C:\Program Files (x86)\Maemo\flasher-3.5>flasher-3.5 -f -b -k zImage-2.6.28-omap
1-fb
flasher v2.5.2 (Sep 24 2009)
Suitable USB device not found, waiting.
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
105.
Found device RX-51, hardware revision 2101
NOLO version 1.4.14
Version of 'sw-release': RX-51_2009SE_20.2010.36-2_PR_MR0
Sending kernel image (1728 kB)...
100% (1728 of 1728 kB, avg. 27011 kB/s)
Flashing kernel... done.
C:\Program Files (x86)\Maemo\flasher-3.5>flasher-3.5 --disable-rd-mode
flasher v2.5.2 (Sep 24 2009)
Suitable USB device not found, waiting.
USB device found found at bus bus-0, device address \\.\libusb0-0001--0x0421-0x0
105.
Found device RX-51, hardware revision 2101
NOLO version 1.4.14
Version of 'sw-release': <no version>
The device is now in production mode
|
|
2013-06-01
, 17:26
|
|
Posts: 578 |
Thanked: 994 times |
Joined on Dec 2012
|
#19
|
please don't disable R&D mode. Now you have fb kernel. I know it's hard but did you see any errors on n900.
Last edited by elros34; 2013-06-01 at 17:29.
Last edited by elros34; 2013-06-01 at 17:29.
|
|
2013-06-01
, 17:30
|
|
Posts: 25 |
Thanked: 4 times |
Joined on Jan 2009
|
#20
|
So, the kernel don't start. After these three commands, N900 is still in R&D mode, and the NOKIA (with symbol of rd mode) is lighting.
EDIT:
fb kernel starts. The error messages I saw was something like before in RescueOS -
Also I see the: tpa6130az - read (and than also write) failed
Last edited by Jackeye; 2013-06-01 at 17:48.
EDIT:
fb kernel starts. The error messages I saw was something like before in RescueOS -
Code:
i2c_omap i2c_omap.2: controller timed out
Last edited by Jackeye; 2013-06-01 at 17:48.
 |
| Tags |
| boot error, flashing, nokia |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 15:25.
Thank you for link, I will try after this my run work will have no success. Thanks!
elros34
If I run dmesg, it should save somewhere some log, don't it? Because I see only the last few lines, which can be displayed - no scrolling. But what I saw even without scrolling is massage:
EDIT:
What lo9314 suggests doesn't function on my side. When try to use flasher, it cannot get n900 in update mode as suitable device and is still waiting.
Now I really don't know, what to do. Should I set N900 into storage mode and repatition eMMC? I definitely don't know, what part is bad, why cannot boot Maemo...Maybe that's the right time to offer half of kingdom for a solution!
Last edited by Jackeye; 2013-06-01 at 12:25.