Well I don't think it has to do with the updates either. I think its an all together different problem. After trying various updates, I decided to install, not do any updates, and see what happened.
First of all, a few times I was able to set up wlan0 via ndiswrapper, install some packages, reboot, and all was fine until I tried the next few package updates (aka the 2nd reboot). It seemed like every time i did that, the next batch of packages i would try (after the successful ones + 1st reboot) would cause this hang after GDM login. Well this time, I decided to set up ndiswrapper and reboot to make sure the module loaded at boot + make sure this problem didn't occur even with no updates installed on the 1st reboot. I'm sure you can guess what happened: hang on the 1st reboot. I think the times I was able to reboot once after installing the drivers or the first batch of updates for testing was random. Whether its on the first or second reboot seems inconsistent to me because I've done the exact same sequence of things throughout these tests.
It always happens for sure though on or before the 2nd reboot, and always displays kinit trying to resume from /dev/disk/by-uuid/accdf387-111b-40fd-b1b8-5bf2a38f20d2 in tty1. Perhaps this would have something to do with it? It says no resume image, so it does normal boot. Thats the only thing I can find (with my novice linux knowledge
) that seems out of place.
Heres the only things I've done in all these installations (besides the first few tries described in my first post):
-open terminal, install wifi driver mrvk51.inf + ndiswrapper -m + depmod -a + modprobe ndiswrapper
-add "ndiswrapper" to /etc/modules
-either reboot or install some/all updates and then reboot