Hi,
I know for a fact (learned the hard way) that if the server is not reachable (in your case 192.168.11.149), it will seem as if the thing does not boot. After over an hour, it might actually relent and boot ...
So, for some reason, the ZyXel does not just skip that part then, but hangs there seemingly forever. So try either setting the serverip to your router's address (probably 192.168.11.1) or just empty the preboot variable (in both cases, however, you will not be able to use netconsole, unless you have some way of opening a terminal and using netconsole on the router (e.g. with OpenWRT)).
Maybe this helps.
Cheers,
chessplayer
I know for a fact (learned the hard way) that if the server is not reachable (in your case 192.168.11.149), it will seem as if the thing does not boot. After over an hour, it might actually relent and boot ...
So, for some reason, the ZyXel does not just skip that part then, but hangs there seemingly forever. So try either setting the serverip to your router's address (probably 192.168.11.1) or just empty the preboot variable (in both cases, however, you will not be able to use netconsole, unless you have some way of opening a terminal and using netconsole on the router (e.g. with OpenWRT)).
Maybe this helps.
Cheers,
chessplayer