Active Topics
-
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 1 day, 2 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 1 day, 15 hrs ago -
n770 youtube video (0)
to General by nmdv - 5 days, 14 hrs ago - more...
 |
int_ua |
2012-03-05
, 23:05
|
|
Posts: 676 |
Thanked: 1,067 times |
Joined on Jul 2010
@ Kyiv, Ukraine
|
#11
|
Originally Posted by freemangordon
Are you using 10.10? IIRC someone reported a problem with qemu version there. If that's 12.04 then it's a new bug. Anyway it definitely looks like qemu bug and I can't help except from advising search through existing bugs and/or using strace to try to find the reason.
| The Following User Says Thank You to int_ua For This Useful Post: | ||
|
|
2012-03-05
, 23:15
|
|
Posts: 3,074 |
Thanked: 12,960 times |
Joined on Mar 2010
@ Sofia,Bulgaria
|
#12
|
It happens in both 10.10 and 11.04 
. Anyway going to chroot on n900 itself. Hope it will continue.
EDIT:
Last edited by freemangordon; 2012-03-05 at 23:51.
. Anyway going to chroot on n900 itself. Hope it will continue.EDIT:
Code:
Nokia-N900:~# chroot $MOUNTPOINT_TARGET FATAL: kernel too old
Last edited by freemangordon; 2012-03-05 at 23:51.
|
|
2012-03-06
, 07:19
|
|
Posts: 72 |
Thanked: 157 times |
Joined on Oct 2011
@ Hungary
|
#13
|
Originally Posted by pali
I have made a photo of the boot process. I tried to boot 3.2.0 kernel. U-boot finds the boot.scr then it also finds the uImage and the uInitrd, but then it hangs. I think that it is important that the light stays on instead of switching off like in a succesfull boot process.
So there is no problem with my (last) U-Boot with SD card and eMMC? If yes, then it sounds good
Here is the photo of the 3.2.0 kernel booting with pali's U-boot:
With pali's U-boot I was unable to boot the 2.3 kernel and it ended up like the 3.2.0 kernel. Staying at the U-boot screen.
Last edited by PanzerSajt; 2012-03-06 at 08:58.
|
|
2012-03-06
, 08:18
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#14
|
Originally Posted by PanzerSajt
Did you reused nolo atags?
I have made a photo of the boot process. I tried to boot 3.2.0 kernel. U-boot finds the boot.scr then it also finds the uImage and the uInitrd, but then it hangs. I think that it is important that the light stays on instead of switching off like in a succesfull boot process.
Here is the photo of the 3.2.0 kernel booting:
I will later update this post with information about the 2.3 kernel booting.
|
|
2012-03-06
, 10:21
|
|
Posts: 676 |
Thanked: 1,067 times |
Joined on Jul 2010
@ Kyiv, Ukraine
|
#15
|
Originally Posted by freemangordon
I've read somewhere that it should chroot on N900 with KP. But I'm using stock kernel at the moment. Maybe try updating qemu from 11.10 repositories bt downloading .deb? Anyone else having similar issues?
Code:Nokia-N900:~# chroot $MOUNTPOINT_TARGET FATAL: kernel too old
Originally Posted by PanzerSajt
I haven't seen any kernel staying at U-Boot screen, they all clear the screen in my case. Do you mean 2.6.35 kernel? I was able to boot it as you can see on the screenshot. Did you copied new uImage and uInitrd from ext partition to fat partition? I've read somewhere yesterday about "debug" kernel parameter. But I don't have time to test it. Maybe some other parameters will help too.
With pali's U-boot I was unable to boot the 2.3 kernel and it ended up like the 3.2.0 kernel. Staying at the U-boot screen.
Related info: http://processors.wiki.ti.com/index....g_Kernel....22
UPDATE: Maybe the problem is in the console kernel parameter (see the link), try deleting it and recreating boot.scr. And don't forget to move all new boot.scr, uImage and uInitrd from ext partition to fat.
Originally Posted by pali
How should we do this?
Did you reused nolo atags?
Last edited by int_ua; 2012-03-06 at 10:36.
|
|
2012-03-06
, 10:35
|
|
Posts: 2,154 |
Thanked: 8,464 times |
Joined on May 2010
|
#16
|
Originally Posted by int_ua
ITEM_USEATAG=1
How should we do this?
See U-Boot thread: http://talk.maemo.org/showthread.php?t=81613
|
|
2012-03-06
, 10:41
|
|
Posts: 676 |
Thanked: 1,067 times |
Joined on Jul 2010
@ Kyiv, Ukraine
|
#17
|
Originally Posted by pali
Is it the default behaviour? I'm not using bootmenu, just boot.scr.
ITEM_USEATAG=1
Can we use both bootmenu and boot.scr? If so, I don't yet know how to do it and will have time to test it only tomorrow or the day after tomorrow.
| The Following User Says Thank You to int_ua For This Useful Post: | ||
|
|
2012-03-06
, 10:59
|
|
Posts: 676 |
Thanked: 1,067 times |
Joined on Jul 2010
@ Kyiv, Ukraine
|
#18
|
Please post if you successfully booted (see details in the first post).
|
|
2012-03-06
, 11:06
|
|
Posts: 676 |
Thanked: 1,067 times |
Joined on Jul 2010
@ Kyiv, Ukraine
|
#19
|
Template for reports:
STATUS: Booted, system lockups from time to time (~ every third boot)
REVISION: 43, unchanged
MICROSD: 16 Gb, class 6
BOOTLOADER: U-Boot pr13
OPTIONS:
And comments:
I will be updating options section with blank values when there will be more options available.
Use grep ^ * in the options/ folder to get them all at once. selected_microsd_device and fdisk_command_stack.file are irrelevant in most cases.
Last edited by int_ua; 2012-03-12 at 17:58.
STATUS: Booted, system lockups from time to time (~ every third boot)
REVISION: 43, unchanged
MICROSD: 16 Gb, class 6
BOOTLOADER: U-Boot pr13
OPTIONS:
selected_image_source: ubuntu-daily
selected_firmware_source: local
dist_upgrade:
selected_kernel:
boot_parameters:
additional_packages:
I will be updating options section with blank values when there will be more options available.
Use grep ^ * in the options/ folder to get them all at once. selected_microsd_device and fdisk_command_stack.file are irrelevant in most cases.
Last edited by int_ua; 2012-03-12 at 17:58.
| The Following User Says Thank You to int_ua For This Useful Post: | ||
|
|
2012-03-06
, 11:27
|
|
Posts: 3,074 |
Thanked: 12,960 times |
Joined on Mar 2010
@ Sofia,Bulgaria
|
#20
|
Originally Posted by int_ua
Guess which kernel I am using
I've read somewhere that it should chroot on N900 with KP.
. Anyway yesterday evening I've done dist-upgrade to from 11.04 to 11.10, will try again today when I am back home.