13th November 2016, 13:36
The only option then left is removing the proprietary nvidia driver and remove the nomodeset parameter.
As the graphics initialization on a kernel level even fails it must be the nvidia driver being the culprit here again.
At least you should get boot messages again by removing the nvidia driver. However I am not sure why it works in recovery for you as you apparently are using nvidia here successfully.
Is the nomodeset parameter still used by your normal boot to disable nouveau?
Is nouveau maybe loaded as module even in recovery boot? lsmod shows you a list of loaded kernel modules.
Did you tried booting older kernels?
As the graphics initialization on a kernel level even fails it must be the nvidia driver being the culprit here again.
At least you should get boot messages again by removing the nvidia driver. However I am not sure why it works in recovery for you as you apparently are using nvidia here successfully.
Is the nomodeset parameter still used by your normal boot to disable nouveau?
Is nouveau maybe loaded as module even in recovery boot? lsmod shows you a list of loaded kernel modules.
Did you tried booting older kernels?