Kali rolling 17.1 stauls during loading process after dist-upgrade

[E.T.II]

Got rolling 16 to work after some tweeks to GRUB but now after running dist-uprade, rolling 17 refuses to load.

Error message upon loading=
Loading, please wait ...
lvmetad is not active yet, using direct activation during s y s i n i t
"disk/by-uuid/843e046a-4e80-400c-bd85-d02b9014da62": Invalid path for Logical volume.
fsck from util-linux 2.27.1
/dev/sda6: clean, (more / numbers) files, (more / numbers) blocks
[ 14. a series of numbers] USB 2-4: firmware failed to load isight.fw (-2)
_ (<<< cursor but can't type)

After pressing e on grub menu and inserting rw nomodset after quiet, I get the same error message except the usb says 7-4 instead of 2-4 and the number series went from 14.&tc to 15.5515481

This screen comes on then flashes on and off maybe 4 or 5 times then it just stays that way. However, booting into recovery mode will allow terminal input for maintenance.

For what it's worth I'm running from an early (May) 2008 MacBook.

[_defalt]

That seems to be the problem with Nvidia graphic card drivers. When you launch grub menu press e and type nomodeset after quiet rw. Even if quiet rw was not written you can still add nomodset in the 3rd last or 2nd last line.

[E.T.II]

That seems to be the problem with Nvidia graphic card drivers. When you launch grub menu press e and type nomodset after quiet rw. Even if quiet rw was not written you can still add nomodset in the 3rd last or 2nd last line.

Quiet was written without rw. Tried what you said with nomodset with and without adding in rw and it gave the same response.

After pressing e on grub menu and inserting rw nomodset after quiet, I get the same error message except the usb says 7-4 instead of 2-4 and the number series went from 14.&tc to 15.5515481

For what it's worth I'm running from an early (May) 2008 MacBook.

[_defalt]

Replace quiet rw with nomodeset quiet spalsh. Spelling error corrected.

[E.T.II]

Replace quiet rw with nomodeset quiet spalsh. Spelling error corrected.

I had eventually given up and just reinstalled the Kali rolling 2016.1 but when they came out with Kali rolling 2017.2 I tried to update that and had the same issue that I had with Kali rolling 2017.1. So I tried what you stated above and I'm still having the same issue.