Originally Posted by Skry

@ArchiMark
Error you get clearly states that kernel is not found, meaning it's not present in the location where you have set u-boot to look for it.

@ whoever
Again, this has been covered many times before now, in this thread and others. If u-boot is (configured, and otherwise) OK, kernel will boot, that has been proven already. If it boots but does not run, rootfs can't be found.

So, there is always the chance that there is some problem that has not been manifested before, and in such case you're very welcome to call me an ***hole and advertise this all as non-working sh*t, but if you guys cant make it work, it's most likely because the simple fact that you have not done your reading and/or don't understand what you are doing. I've already provided all information that is needed for installation, including the suggestion to read about it first, then understand what you're doing and finally performing the simple task of installation.

I don't actually enjoy going over and over the same, off-topic issue, endlessly while I'm on my very limited free time. Would you believe it?

Originally Posted by ArchiMark

Installed u-boot-flasher via apt-get....as the versions listed on first page of this thread are not available now...Pali said it's OK to use the version he recently released.....

I created a new u-boot menu entry as follows:

Code:

ITEM_NAME="Arch Linux ARM (eMMC)"
ITEM_KERNEL="/boot/uImage"
ITEM_DEVICE="${INT_CARD}p5"
ITEM_FSTYPE="ext3"
ITEM_OMAPATAG="1"
ITEM_CMDLINE="root=/dev/mmcblk0p5 rootwait init=/bin/systemdomapfb.vram=0:3M,1:3M,2:3M quiet"

Then I did

Code:

# u-boot-update-bootmenu 

Adding entry for: 'Maemo 5 with attached kernel 2.6.28-omap1 (internal Nand)'

Configuration file: /etc/bootmenu/d/20-archlinux.item

Warning: Invalid file - missing kernel or script file - skipping...

Generating u-boot bootmenu script....

Any suggestions?

Thanks!

Originally Posted by mlwane

I have a suggestion for you. Try to remove "20-archlinux.item" from "/etc/bootmenu.d/", and then create a new, lets say "21-archlinux.item" file again. Also try to type the configuration manually, not just copy-paste, while paying attention there are no mistakes.

Originally Posted by ArchiMark

Thank you!

Did as you suggested and this time no error messages from u-boot-update-bootmenu!

btw, I did not copy-paste before, so, much have been a typo....

Well, just did reboot and I saw and selected Arch....Yeah!!!

Unfortunately, it does not boot up Arch though....get the following console error messages....

Code:

localhost login:   [   4.377685] omap_12c omap_12c.2: controller timed out
[    4.784729] bcm2048 3-0022:  BCM 12C error!
[    4.786285] bcm2048 3-0022:  Is Bluetooth up and running?
[    5.885070] tpa6130a2 2-0060: Write failed
[    5.885253] tpa6130a2 2-0060: Failed to initialize chip
[    5.932525] et8ek8 3-003e: read from offset 0x1263 error -121
[    5.933380] isp_register_subdev_group: Unable to register subdev et8e8
[    6.032714] EXT4-fs (mmcblk0p4): unable to read superblock
[    6.034698] smia-sensor 2-0010: read from offset 0x0 error -121
[    6.102020] EXT4-fs (mmcblk0p4): unable to read superblock
[    6.110565] EXT4-fs (mmcblk0p4): unable to read superblock
[    6.390136] rx51-audio rx51-audio: asoc: failed to init TLV320AIC34: -19
[   6.390411]  asoc: failed to instantiate card RX-51: -19
[   6.405364] rx-51-audio rx51-audio: snd_soc_register_card failed (-19)

I can take care of the error regarding formatting of mmcblk0p4....forgot about that partition....just formatted mmcblk0p5 to ext3 for Arch install....

Any suggestions now?

Thanks!

Originally Posted by caveman

I have been running alarm from the emmc for a while now. Yesterday I took the uSD from the N900, and to my surprise arch does not boot without it.

Originally Posted by Skry

this is actually pretty easy to explain and a known fact. When you have uSD card inserted, it becomes mmcblk0 and eMMC becomes mmcblk1. However, if there is no uSD card, eMMC (naturally) as an only drive is mmcblk0.

Originally Posted by mlwane

I believe Arch has booted just fine. Just ignore the messages and type "root" and press return, it should then ask you to enter the password which I believe is "root" as well.

Originally Posted by Skry

this is actually pretty easy to explain and a known fact. When you have uSD card inserted, it becomes mmcblk0 and eMMC becomes mmcblk1. However, if there is no uSD card, eMMC (naturally) as an only drive is mmcblk0.