flash-kernel-installer is not creating an initial preEnv.txt during installation
Bug #1037757 reported by
Jim Erickson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| flash-kernel (Ubuntu) |
Fix Released
|
High
|
Oliver Grawert | ||
| Quantal |
Fix Released
|
High
|
Oliver Grawert | ||
| ubiquity (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
| Quantal |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
using the daily image of quantal quetzal (august 16th) after initial install and restart there is a kernel panic. you have to hand edit preEnv.txt to get it to boot. my preEnv.txt reads as follows:
bootargs=ro root=UUID=xxx
there is a boot.scr present on the partition but preEnv.txt still needs edited.
| Changed in ubiquity (Ubuntu): | |
| status: | New → Invalid |
| Changed in flash-kernel (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → High |
| assignee: | nobody → Oliver Grawert (ogra) |
| summary: |
- have to edit preEnv.txt to get omap4+armhf to boot on pandaboard ES + flash-kernel-installer is not creating an initial preEnv.txt during + installation |
Revision history for this message
| Oliver Grawert (ogra) wrote | #1 |
| Changed in flash-kernel (Ubuntu Quantal): | |
| status: | Confirmed → Fix Released |
To post a comment you must log in.
this was fixed a while ago, flash-kernel-