Bug 4224 - bootloader won't boot Mer (wrong devicename)
: bootloader won't boot Mer (wrong devicename)
Status: RESOLVED FIXED
Product: Mer
Core
: unspecified
: N810 Linux
: Unspecified normal (vote)
: ---
Assigned To: Carsten Munk
: general-bugs
:
:
:
:
  Show dependency tree
 
Reported: 2009-03-19 14:10 UTC by Jurgen Haan
Modified: 2009-04-05 20:27 UTC (History)
0 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Jurgen Haan (reporter) 2009-03-19 14:10:13 UTC
SOFTWARE VERSION:
(Control Panel > General > About product)
Mer 0.10internal

STEPS TO REPRODUCE THE PROBLEM:
Install mer on the internal Flash (/dev/mmcblk0) with the following partition
layout:
/dev/mmcblk0p1 256M vfat
/dev/mmcblk0p2 128M swap
/dev/mmcblk0p3 1.6G ext3 (boot flag)

EXPECTED OUTCOME:
A booted mer

ACTUAL OUTCOME:
The .item file generated tries to boot mer from mmcblk0p3 which causes a
powercycle upon selection.

REPRODUCIBILITY:
(always/sometimes/once)
once (did not try to reproduce)

EXTRA SOFTWARE INSTALLED:

OTHER COMMENTS:
Changing the mmcblk0 part in the .item file to ${INT_CARD} solves the problem.
Upon booting mer, it shows that instead of MMCBLK0 the card is now called
MMCBLK1. (Which would mean that if the bootloader tries to append that as root
filesystem, it makes sense the bootprocess dies).

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6)
Gecko/2009020911
Comment 1 Carsten Munk maemo.org 2009-04-05 20:27:02 UTC
Was fixed in 2.0.0-mer7 (i hope)