[opensuse-arm] RPi zero unable to boot images
From that boot prompt, I can type "help" but if there is a command
Decided to take another look at trying to boot TW RPi 1 images on a RPi zero, hooked up to a monitor to see stdout. Have tried the following TW LXQT and JeOS images, the LXQT is the latest build and the JeOS is one release older. openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2016.09.27-Build1.8.raw.xz openSUSE-Tumbleweed-ARM-JeOS-raspberrypi.armv6l-2016.06.12-Build2.10.raw.xz Both have same results. The boot process proceeds until unable to find a "config.txt" file. Knowing the file should actually have a capital "C" I renamed the file to "Config.txt" But with no different result. The following is a link to a photo image of stdout when boot stops, is the same for both images https://goo.gl/photos/uV2FyFdwv2SkQToT8 that might continue while also referencing or injecting the Config.txt file, I don't know what that might be. I've waited over an hour each time in case the boot might just have taken longer than expected, but there's no difference. The display is the same (as the photo). Each time, when the boot has failed, I've inserted the card back in a big machine, and I can see that the boot process has at least created 3 partitions, EFI, boot and root. I didn't try to mount the card or partitions to inspect the contents of the partitions. Anything else to try? TIA, Tony -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 07.10.2016 um 03:37 schrieb Tony Su:
The boot process proceeds until unable to find a "config.txt" file. Knowing the file should actually have a capital "C" I renamed the file to "Config.txt" But with no different result.
FAT partitions ignore case, so both file names work.
The following is a link to a photo image of stdout when boot stops, is the same for both images
Thanks for this helpful info! First, the output is cut off on the left side. You should edit config.txt (the one on the FAT partition) to set the right overscan settings for your monitor. Check the links in the file or the mailing list archives. What you are showing there is actually U-Boot output, so config.txt was found just fine. U-Boot falls back to PXE booting for some reason and doesn't find a pxelinux.cfg/default file, which is _very_ different from a Raspberry Pi config.txt file. Please read carefully and always report exact output. What we really need to see is what it says earlier, before it attempts network booting. Do you have a TTL UART adapter? Otherwise you'll need to take some more pictures. Does it ever show a GRUB menu? Anything after the ~3 second U-Boot timeout can be relevant. I found a place that actually has Pi Zero on stock and hope to receive one soon. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Thx for the suggestions,
Will take a closer look at whether config.txt can fix the horizontal
alignment, the monitor itself has already been adjusted to its limits.
I think you are saying that the config.txt was found because it <has
to be read before> U-boot can execute but that the final error is an
attempt at a PXE boot?
At the moment, based on what I think you said that the kernel modules
for OTG have been added but disabled (That should be correct), then I
believe that leaves two possible points of failure...
- config.txt is read but the command to enable the OTG modules is not respected
- Although the OTG kernel modules are loaded by implementing the
command in config.txt, hardware support for OTG (specifically Ethernet
over USB) is still missing.
For now, if my analysis is accurate then I suspect the second issue,
although the first is still possible. I'll also be looking at
"ordinary" Ethernet over USB support even if OTG support might be
lacking.
At the moment, am waiting on delivery of necessary hardware to be able
to troubleshoot further... When I first planned on using the Pi Zero,
I assumed that things would run smoothly, so bought minimal hardware I
thought would be necessary. The whole idea of using a Pi Zero in the
first place is to not pay for unnecessary hardware, but that's
assuming no problems like what I've been encountering. To
troubleshoot, I've found that a substantial amount of additional
hardware is necessary to support different I/O configurations which
isn't necessary on any of the other Pi models. The hardware is all
coming, so sometime soon I'll be able to do the troubleshooting.
Tony
On Sat, Oct 15, 2016 at 11:21 AM, Andreas Färber
Am 07.10.2016 um 03:37 schrieb Tony Su:
The boot process proceeds until unable to find a "config.txt" file. Knowing the file should actually have a capital "C" I renamed the file to "Config.txt" But with no different result.
FAT partitions ignore case, so both file names work.
The following is a link to a photo image of stdout when boot stops, is the same for both images
Thanks for this helpful info!
First, the output is cut off on the left side. You should edit config.txt (the one on the FAT partition) to set the right overscan settings for your monitor. Check the links in the file or the mailing list archives.
What you are showing there is actually U-Boot output, so config.txt was found just fine. U-Boot falls back to PXE booting for some reason and doesn't find a pxelinux.cfg/default file, which is _very_ different from a Raspberry Pi config.txt file. Please read carefully and always report exact output.
What we really need to see is what it says earlier, before it attempts network booting. Do you have a TTL UART adapter? Otherwise you'll need to take some more pictures. Does it ever show a GRUB menu? Anything after the ~3 second U-Boot timeout can be relevant.
I found a place that actually has Pi Zero on stock and hope to receive one soon.
Regards, Andreas
-- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (2)
-
Andreas Färber -
Tony Su