http://bugzilla.opensuse.org/show_bug.cgi?id=1207562 http://bugzilla.opensuse.org/show_bug.cgi?id=1207562#c17 --- Comment #17 from Stefan Seyfried <seife@novell.slipkontur.de> --- I can try different things, but I'd need instructions what to do where and when. My U-boot knowledge is from embedded systems that do not use UEFI stuff at all ;-) and from a time when there were no such things as "device trees" but instead separate kernels for different hardware configurations were built :-) So what I wanted to say... I don't even know what a "runtime FDT" is, much less how I would check if it declares reserved memory ;-) The bdinfo would need to come from the "broken" U-boot? or can I use a "good", working version? The problem with the broken one is that it is already in the TFTP BOOTP stage once the HDMI output stabilizes and once it is there, no keyboard input seems to do anything at all. So I'd need to set up a serial console etc and since this would be possible, it's quite some effort here and I'd leave that experiment to someone else experiencing this issue who already might have everything set up. -- You are receiving this mail because: You are on the CC list for the bug.