Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kernel_emergency usage with latest firmware binaries (18th April) #3

Closed
Hexxeh opened this issue Apr 17, 2012 · 2 comments
Closed

kernel_emergency usage with latest firmware binaries (18th April) #3

Hexxeh opened this issue Apr 17, 2012 · 2 comments

Comments

@Hexxeh
Copy link

Hexxeh commented Apr 17, 2012

Using the emergency kernel image with the latest firmware binaries results in corrupted graphical output for me.

I can get display out using the normal image by setting hdmi_mode=4, hdmi_drive=2, hdmi_force_hotplug=1, but those don't fix the display using the emergency kernel.

Is the emergency kernel just outdated compared to the firmware files?

@popcornmix
Copy link
Contributor

I wouldn't expect the kernel version to affect HDMI output (the hdmi_* options are processed by start.elf).

Can you clarify:
Do you get no HDMI output without a config.txt file? If so, then please post an edid dump
(#4 for instructions)
Are you saying "hdmi_mode=4, hdmi_drive=2, hdmi_force_hotplug=1" gives an image with kernel.img, but corrupt image with "kernel_emergency.img" (and no other changes) ?
Can you link to a photo of the corrupt display?

@Hexxeh
Copy link
Author

Hexxeh commented Apr 21, 2012

I've not been able to reproduce this since, so maybe my SD card was being very dodgy. Closing for now, I'll reopen if I can reproduce this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants