Ubuntu 12.04 on N900 with U-Boot - Page 37 - maemo.org

Active Topics

Extra softwares in Sailfish using CLI, repositories, etc (117)
to SailfishOS by nieldk - 23 hrs, 18 mins ago
Firefox with Leste (6)
to Maemo 7 / Leste by teroyk - 1 day, 20 hrs ago
more...

Page 37 of 45

Thread Tools

caveman	2012-07-26 , 13:13
Posts: 191 \| Thanked: 415 times \| Joined on Jan 2012	#361

Originally Posted by agr0

My files are correct. I trying all methods :/ When i run script i have this:
All is good ?

You will have to check if your devices have all the listed items. Check that the corresponding packages are installed in the appropriate device.

Your error code is 126, which is listed in the manual as

Code:

126 if COMMAND is found but cannot be invoked

So begin checking if you have bash installed inside the chroot and that the directory and file permissions are correct.

Last edited by caveman; 2012-07-26 at 13:22. Reason: checked chroot error code in the docs

Quote & Reply |

The Following User Says Thank You to caveman For This Useful Post:
agr0

	Nobless	2012-07-26 , 13:44
	Posts: 101 \| Thanked: 73 times \| Joined on Oct 2011 @ Lithuania	#362

Originally Posted by caveman

Nothing stands out for me in your logs. Granted, however, that I can't read the language ;-)

Good, whops forgot about that

ok if everything fine, which kernel i should use ?

Quote & Reply |

agr0	2012-07-26 , 16:48
Posts: 22 \| Thanked: 12 times \| Joined on May 2012	#363

Is the problem may be that my memory card (mSDHC 32GB Sandisk) inserted in my phone, when I install this?

Quote & Reply |

The Following User Says Thank You to agr0 For This Useful Post:
Nobless

caveman	2012-07-26 , 18:48
Posts: 191 \| Thanked: 415 times \| Joined on Jan 2012	#364

Originally Posted by agr0

Is the problem may be that my memory card (mSDHC 32GB Sandisk) inserted in my phone, when I install this?

All my installs were made with the uSD on my linux box.

Quote & Reply |

The Following User Says Thank You to caveman For This Useful Post:
Nobless

agr0	2012-07-27 , 10:42
Posts: 22 \| Thanked: 12 times \| Joined on May 2012	#365

I found a solution to my problem. My card was formatted, but not in ext3 format. Now the script works, thanks for your help.

Quote & Reply |

The Following User Says Thank You to agr0 For This Useful Post:
int_ua

agr0	2012-07-27 , 17:02
Posts: 22 \| Thanked: 12 times \| Joined on May 2012	#366

Ok, im trying boot Ubuntu, but i have some problems. When i using ubuntu.item

Code:

ITEM_NAME="Ubuntu"
ITEM_KERNEL="uImage"
ITEM_INITRD="uInitrd"
ITEM_DEVICE="${EXT_CARD}p3"
ITEM_FSTYPE="ext4"
ITEM_CMDLINE="vram=12M omapfb.mode=dvi:1280x720MR-16@60 mpurate=\${mpurate} root=/dev/mmcblk1p3 fixrtc quiet splash"
ITEM_REUSEATAGS="1"

i have this:

Code:

mmc0 is current device
Loading file "uInitrd" from mmc device 0:3 xxa3
64 bytes read
Loading file "uImage" from mmc device 0:3 xxa3
1956720 bytes read
Booting uImage uInitrd from mmc 0:3 ...
## Booting kernel from Legacy Image at 82008000 ...
     Image Name:  Ubuntu
     Image Type:   ARM Linux Kernel Image (uncompressed)
     Data Size:       1956656 Bytes = 1.9 MiB
     Load Address:80008000
     Entry Point:     80008000
     Verifying Checksum ... OK
Wrong Ramdisk Image Format
Ramdisk Image is corrupt or invalid

Last edited by agr0; 2012-07-27 at 18:08.

Quote & Reply |

The Following User Says Thank You to agr0 For This Useful Post:
int_ua

pali	2012-07-27 , 18:10
Posts: 2,153 \| Thanked: 8,462 times \| Joined on May 2010	#367

Originally Posted by agr0

Code:

mmc0 is current device
Loading file "uInitrd" from mmc device 0:3 xxa3
64 bytes read

initrd is too small. check if you do not have corrupted initrd file.

Quote & Reply |

The Following 2 Users Say Thank You to pali For This Useful Post:
agr0, int_ua

agr0	2012-07-27 , 19:13
Posts: 22 \| Thanked: 12 times \| Joined on May 2012	#368

How to get/fix this file ?

When I installed Ubuntu, I had this:

Code:

Image Name:   Ubuntu
Created:      Fri Jul 27 19:00:49 2012
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    1956656 Bytes = 1910.80 kB = 1.87 MB
Load Address: 80008000
Entry Point:  80008000
/usr/bin/mkimage: Can't open /initrd.img: No such file or directory
Image Name:   Ubuntu boot script
Created:      Fri Jul 27 19:00:49 2012
Image Type:   ARM Linux Script (uncompressed)
Data Size:    308 Bytes = 0.30 kB = 0.00 MB
Load Address: 00000000
Entry Point:  00000000
Contents:
   Image 0: 300 Bytes = 0.29 kB = 0.00 MB

with this options:

Code:

Report template:
STATUS: _
REVISION: 132, 
MICROSD: _
BOOTLOADER: U-Boot _
OPTIONS:
additional_packages:acpid wireless-tools lubuntu-desktop openssh-server chromium-browser lxde xorg man-db
boot_parameters:root=/dev/mmcblk0p3 rootwait console=tty0 omapfb.vram=0:2M,1:2M,2:2M mtdoops.mtddev=2 nosplash elevator=noop panic=20
dist_upgrade:0
selected_firmware_source:meego
selected_image_source:ubuntu-core
selected_kernel:custom
selected_target:/dev/sdc3
selected_target_type:partition
target_partition_suffix_root:3
COMMENTS:

Last edited by agr0; 2012-07-27 at 19:19.

Quote & Reply |

iamsrp	2012-07-27 , 19:27
Posts: 24 \| Thanked: 28 times \| Joined on Jan 2010	#369

That's the same problem I witnessed. See my post a couple of pages back: http://talk.maemo.org/showpost.php?p...&postcount=347 (specifically the update at the bottom). You should make sure all the symlinks point to the right images and so forth (i.e. initrd.img points to the one which you create and /initrd.img points at boot/initrd.img).

Quote & Reply |

The Following 3 Users Say Thank You to iamsrp For This Useful Post:
agr0, int_ua, michaaa62

agr0	2012-07-28 , 08:32
Posts: 22 \| Thanked: 12 times \| Joined on May 2012	#370

Ok, I created this files, and now i have this, when i run ubuntu.item

Code:

[  2.321807] mtdoops: mtd device (mtddev=name/number) must be supplied
[  2.464996] twl4030_wdt: Failed to register misc device
[  2.487335] Power Mangement for TI OMAP3
[  2.607086] request_module: runaway loop modprobe binfmt-464c