pre-built images result in "Kernel panic - not syncing: No init found. Try passing init= option to "
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```
What steps will reproduce the problem?
1. sudo ./mkmmc-reflash.sh /dev/mmcblk0p beagleboard
2. sudo ./mkmmc-android.sh /dev/mmcblk0p beagleboard
~/rowboat-prebuilt/uImage
~/rowboat-prebuilt/beagleboard-donut-rootfs-2009-12-22.tar.bz2
3.power on board
What is the expected output? What do you see instead?
Expected it would work. Instead, get a kernal panic while trying to open
the console.
Here is what I see
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 168K
Warning: unable to open an initial console.
Failed to execute /init. Attempting defaults...
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
What version of the product are you using? On what operating system?
Tried builds from both 2009-12-22 & 2009-11-03.
Get same result.
Please provide any additional information below.
Tried changing the bootargs. Nothing helps. As best I can tell, the
pre-built kernal is not built with the right options for the BeagleBoard.
Has anyone gotten the pre-built image to work?
```
Original issue reported on code.google.com by `rtill...@gmail.com` on 29 Jan 2010 at 7:21
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with mkmmc-reflash.sh, mkmmc-android.sh, the listed uImage, and beagleboard-donut-rootfs-2009-12-22.tar.bz2; reproduce the boot on a BeagleBoard and review the reported bootargs and console output. Done means the pre-built image mounts its root filesystem, starts init, and reaches the console without a kernel panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, shell
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100