Hello world, I'm experiencing a strange issue with 13.1s AutoYAST on IBX-530s [0]. Maybe some of you can help… We're using rules.xml to distinguish between a couple of machines, namely "real" servers, embedded devices (IBX) and more. The AutoYAST profiles for the real servers and the embedded devices have only trivial differences (re bootloader etc., nothing I'd suspect to have any relevance to the problem). The only other difference is that for real servers we use a static IP address (via hostip, nameserver, and gateway boot parameters), and for embedded devices we use DHCP. The real servers install and run just fine. With the embedded devices, stage 1 finishes just fine, AFAICT. After the reboot, stage 2 throws a few APCI errors (warnings?), then tells me systemd is about to flush the journal (we don't use a persistent journal), and then does nothing, YAST is never even displayed (textmode=1 on both servers and embedded). I have tried around 10 installs and waited for up to 90 minutes; my colleague who first experienced the problem said he waited for the journal for about five minutes and was then dropped to a non-functioning login prompt or shell, but I could not reproduce this. YAST is started seemingly started in the background according to the logs, and runs up to the first user prompt (we have to accept a GPG key because we manually-by-script add a custom add-on repo). Since I can't see YAST, I can't interact with it. I cannot find what is wrong, not even an error message; I am quite lost. I have attached some logs and command output. Can anybody shed some light on what is happening? I would really appreciate any kind of help, nudges in the right direction, or slaps in the back of the head to wake up my brain. (; [0]: http://www.ieiworld.com/search.aspx?keyword=ibx-530 -- Kind regards Christopher 'm4z' Holm / 686f6c6d "We must respect the other fellow's religion, but only in the sense and to the extent that we respect his theory that his wife is beautiful and his children smart." --H. L. Mencken