buyinsurance

Thanks for your reply. nomodeset didn't work for me. Your advice was helpful and I made sure my settings were right, so thank you for that :).
 
Unfortunately, it still didn't work. So I decided to try something different.
 
I ended up finding a fix! I'm now able to boot in correctly. I believe this is a fix for someone that's exhausted all possible kernel trials. I'm assuming this is a funtoo grub packaging problem or something was wrong with my grub.cfg. It's just weird because grub was loading fine, that is why I assumed kernel error.
 
Here is what I did to fix it:
emerge --unmerge grub Added a local overlay, something like /usr/local/portage is good. Added gentoo's version of grub to the overlay. It was also a newer version than funtoo's. emerge -va grub grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda grub2-mkconfig -o /boot/grub/grub.cfg Restarted and was able to get into my system. If anyone has any idea why the funtoo grub didn't work for me, let me know.

Thanks for your reply. nomodeset didn't work for me. Your advice was helpful and I made sure my settings were right, so thank you for that :).
 
Unfortunately, it still didn't work. So I decided to try something different.
 
I ended up finding a fix! I'm now able to boot in correctly. I believe this is a fix for someone that's exhausted all possible kernel trials. I'm assuming this is a funtoo grub packaging problem or something was wrong with my grub.cfg. It's just weird because grub was loading fine, that is why I assumed kernel error.
 
Here is what I did to fix it:
emerge --unmerge grub Added a local overlay, something like /usr/local/portage is good. Added gentoo's version of grub to the overlay. It was also a newer version than funtoo's. emerge -va grub grub-install --target=x86_64-efi --efi-directory=/boot /dev/sda grub2-mkconfig -o /boot/grub/grub.cfg Restarted and was able to get into my system. If anyone has any idea why the funtoo grub didn't work for me, let me know.