Reply
Thread Tools Search this Thread
Posts: 124 | Thanked: 198 times | Joined on Jan 2012
#361
Originally Posted by agr0 View Post
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.
 

The Following User Says Thank You to caveman For This Useful Post:
Posts: 21 | Thanked: 11 times | Joined on May 2012
#362
I found a solution to my problem. My card was formatted, but not in ext3 format. Now the script works, thanks for your help.
 

The Following User Says Thank You to agr0 For This Useful Post:
Posts: 21 | Thanked: 11 times | Joined on May 2012
#363
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; 07-27-2012 at 02:08 PM.
 

The Following User Says Thank You to agr0 For This Useful Post:
Posts: 1,587 | Thanked: 6,077 times | Joined on May 2010
#364
Originally Posted by agr0 View Post
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.
 

The Following 2 Users Say Thank You to pali For This Useful Post:
Posts: 21 | Thanked: 11 times | Joined on May 2012
#365
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; 07-27-2012 at 03:19 PM.
 
Posts: 24 | Thanked: 27 times | Joined on Jan 2010
#366
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).
 

The Following 3 Users Say Thank You to iamsrp For This Useful Post:
Posts: 21 | Thanked: 11 times | Joined on May 2012
#367
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
 

The Following User Says Thank You to agr0 For This Useful Post:
Posts: 21 | Thanked: 11 times | Joined on May 2012
#368
I have a request. Can someone who has installed Ubuntu 12.04 on the N900 can write a tutorial, step by step how to install it? I mean is that someone has made specific parameters of formatting the memory card, installation options and the necessary changes, etc. Trying to install it but still there are some problems. Not only did I have such problems (including quite a few people from the Polish community in Maemo, and probably others). Read all about it, but in any post, there is no specific guidance on how to install Ubuntu to get started easily. Has any experienced user would take on this?
 
Posts: 124 | Thanked: 198 times | Joined on Jan 2012
#369
Originally Posted by agr0 View Post
I have a request. Can someone who has installed Ubuntu 12.04 on the N900 can write a tutorial, step by step how to install it?
Reset your expectations: this is by no means an easy task as of today. But imagine doing that *without* int_ua's script ;-)

I followed the instructions on the first post, running always on a debian notebook directly to the uSD. I had problems with stock qemu-static-arm, so I had to install a newer version from squeeze backports. This is all in previous posts, so search the thread.

My options files are attached for reference, but in summary: ubuntu core, no dist upgrade, nemo firmware, nemo kernel, no swap, no initrd, lxde, lxdm, xorg, etc.

Once your installations is done, create the item file for u-boot. The item file must direct u-boot to where your kernel is. If it sits on the 3rd partition of your uSD, point it to ${EXT_CARD}p3 with ext4. The kernel options must point to the root partition, but notice that mmc names are reversed. So if your root partitions is on mmcblk1p3 inside maemo, point the kernel root arg to mmcblk0p3. Notice that default kernel arguments in the script are fine, you only have to change them if you partition scheme is differente from the defaults (as in my case, as I chose no swap).

I still have problem with the kernel mounting my root partition; we can go back to this point if your kernel boots and ends with something like 'cannot access root partition.'

Good luck!
Attached Files
File Type: tar options.tar (20.0 KB, 55 views)
 

The Following 3 Users Say Thank You to caveman For This Useful Post:
tiempjuuh's Avatar
Posts: 92 | Thanked: 55 times | Joined on Jul 2012 @ Apeldoorn, Netherlands
#370
Wow! How nice! I've tried to install Kubuntu Mobile Daily but every time the image was corrupt. Now I read your post, and when I have found some spare time I will install it!!

Are you going to make a port for 12.10 as well?

Onfortunately I can not program, but when I can do something for this project, tell me

Last edited by tiempjuuh; 08-07-2012 at 03:01 PM.
 

The Following User Says Thank You to tiempjuuh For This Useful Post:
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search

 
Forum Jump


All times are GMT -4. The time now is 08:10 PM.