-
Notifications
You must be signed in to change notification settings - Fork 103
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
BeagleBone Black doesn't boot with 3.18.0-bone1 #5
Comments
Please pastebin.com your full serial bootup.. |
Here you go: https://gist.github.com/n-st/99dfdd8ebf3304f8f8d1 I should add that I can list both the FAT partition with the kernel image and the ext3/4 (not sure at the moment) rootfs from U-Boot using |
Thanks! So it is booting with the initrd... Using an secondary microSD card, do the uuid's match?
The uuid used is stored on the boot partition of the uEnv.txt.. |
I seem to have misplaced my spare SD card at the moment, but I went through this when the system became unbootable after installing the 3.17-bone kernel: A stock image booted from an external SD card was able to find the partitions on the internal MMC storage and the UUID of the rootfs matched the one expected by the kernel. |
Found the SD card, copied and booted this image.
|
Next test: Copied the contents of the internal MMC to the external SD card (bit-wise, with a few intermediate steps since it probably wouldn't be safe to overwrite the rootfs of a running system). |
Next test: Using the stock image from before, flashed the SD card again and installed 3.18.0-bone1 there (after running out of space on the first attempt and resizing the 1.8 GB root partition). The system boots flawlessly:
That most likely means that this isn't a kernel bug after all and that I've just screwed up my system in some obscure way that only clashes with kernels v3.17 onwards, right? In hindsight, that's really the very first test I should have run… Another observation: The stock image with the 3.18 kernel actually powers off the BeagleBone after a regular shutdown command — something which never worked for me since I started using your kernel builds… |
After installing 3.18.0-bone1 via the install-me script from https://rcn-ee.net/deb/wheezy-armhf/v3.18.0-bone1/, my BeagleBone Black no longer boots successfully.
U-Boot loads the new kernel from the internal MMC storage and runs it, but the kernel gets stuck at "Waiting for root device UUID=9c9c1270-ba24-41c3-abd1-3ce2336cc4dd...".
The only seemingly related issue I've been able to find so far doesn't apply here, since the required kernel options are set in the
defconfig
for 3.18.0-bone1.The same problem also occured when I installed one of the 3.17.?-bone? kernels a while ago, but I'm not sure which version that was…
3.16 and earlier version have always worked fine.
Any ideas what might be causing this?
I can also provide a full boot log if that helps.
The text was updated successfully, but these errors were encountered: