Linux-2.6.37 Kernel in gingerbread tree does not boot on Beagleboard C4
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
```
What steps will reproduce the problem?
1. Download source code with: repo init -u
git://gitorious.org/rowboat/manifest.git -m gingerbread.xml ;repo sync
2. Build with: make TARGET_PRODUCT=beagleboard -j8 OMAPES=3.x
3. Create SDCARD and boot per
http://code.google.com/p/rowboat/wiki/ConfigureAndBuild
What is the expected output? What do you see instead?
Expect to see kernel boot messages after uImage is uncompressed. Also expect to
see more dots printed during uncompression. Instead I get:
mmc0 is available
reading uImage
2743276 bytes read
## Booting kernel from Legacy Image at 84000000 ...
Image Name: Linux-2.6.37-g02ca7dc
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2743212 Bytes = 2.6 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
>>> console hangs here. No further output. Does not echo typed characters <<<
What version of the product are you using? On what operating system?
gingerbread on Ubuntu 10.10
Please provide any additional information below.
This all works fine if I start with froyo.xml
```
Original issue reported on code.google.com by `rea.cale...@gmail.com` on 25 Jun 2011 at 12:19
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the Beagleboard C4 boot using the gingerbread.xml manifest, the listed make command, and the ConfigureAndBuild instructions, then compare it with the working froyo.xml build. Start from the boot output after “Uncompressing Linux... done” and identify the configuration or kernel difference; done means gingerbread boots past the hang and produces further console output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100