jadonk / jadonk/rowboat

stucking at 'uncompressing linux....' on beagle c3 -- using pre built android

Open
#59 0 comments 0 reactions 0 assignees View on GitHub
auto-migrated Priority-Medium Type-Defect
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.my board is beagle c3 and i am using pre-built image of beagle XM

I tried as said in comment 2, issue 58(commented by batuoc...@gmail.com ), but
is stuck at 'uncompressing linux...........'
I tried all commands bootargs and bootcmd , saveenv and boot as specified in
comment 2

At one time I got some messages into the hyper-terminal and they are shown in
attatched file along with that environment.

But when I tried a reset then it is stuck at 'uncompressing linux......'

my present environment that is stucking at the 'uncompressing linux....' is
shown in another attatched file.
2.my present environment size is 1403/131068 bytes.
when i got some messages into the hyper-terminal,environment size at that time
is 1508/131068 bytes.
but both are looking same when printed with printenv.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?

Please provide any additional information below.

```

Original issue reported on code.google.com by `vmadhu...@gmail.com` on 9 Nov 2010 at 7:00

Attachments:
- [messages & env](https://storage.googleapis.com/google-code-attachments/rowboat/issue-59/comment-0/messages & env)
- [present env](https://storage.googleapis.com/google-code-attachments/rowboat/issue-59/comment-0/present env)

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the attached “messages & env” and “present env” files, then compare the bootargs, bootcmd, and saved environment described in issue 58 comment 2. Reproduce the Beagle C3 boot with the pre-built Beagle XM Android image and determine whether it progresses past “Uncompressing Linux”; document the working environment or the remaining failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, 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
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.