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

NOOBS v3.2.1->RaspbianFull - RPi4 Kernel panic not syncing. Attempted to kill init exit code 0x00007f00 #3349

Closed
slrslr opened this issue Nov 26, 2019 · 3 comments

Comments

@slrslr
Copy link

slrslr commented Nov 26, 2019

I have downloaded official torrent of the NOOBS v3.2.1 (magnet:?xt=urn:btih:0f816fa2bbad8358efd1ffe4abed11ee5fc7cb07&dn=NOOBS_v3_2_1.zip), (after download, the downloaded files are checked by the torrent client if are complete). I extracted .zip archive, formated the SDHC using SD Formatter and copied over the files. Inserted SDHC card into a RPi 4B 4GB RAM and ran. It shown NOOBS boot menu where i selected Raspbian FULL (it was 3 days back), it installed and i clicked OK button. It rebooted and ended with errors
Kernel panic not syncing. Attempted to kill init exit code 0x00007f00

NOOBS v3 2 1 RPi4 kernel panic

Sidenote: when i tried to flash Raspbian directly to SDHC, i had problem "Caught , core dump failed, Freezing execution". The first OS (LibreELEC) that i have installed when i received the RPi4 like 4 weeks ago and that i have on different SDHC card still working good. I am using TVhat.

Please let me know if i need to try anything (describe it exactly as i am a linux noob).

@XECDesign
Copy link
Contributor

This looks like an unreliable sd card or an issue with the power supply.

@slrslr
Copy link
Author

slrslr commented Dec 5, 2019

This looks like an unreliable sd card or an issue with the power supply.

it is possible, because this time i have used Windows 10 disk formating tool to quick format different SDHC card as FAT32 and copied over noobs v3.2.1 files, installed light weight raspbian buster desktop successfully. Should this be closed or i should try something?

@pelwell
Copy link
Contributor

pelwell commented Dec 5, 2019

If everything is working and we have a plausible explanation for the original problem then I would say close the issue. You can always reopen it later without losing the history if it recurs.

@slrslr slrslr closed this as completed Dec 5, 2019
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

3 participants