[SOLVED] Problem rebooting into fresh gentoo install.

[stavross]

Following https://wiki.gentoo.org/wiki/Sakaki%27s_EFI_Install_Guide and I've hit a snag. Upon rebooting I briefly see some output before a solid pink screen is shown and the system hangs. Google hasn't been helpful with this, any advice? Should I disable KMS, if so how do I go about doing that?
Trying to install onto a i7-5820k and a gtx-970.
Output doesn't have anything particularly worrying in it. Last message before the pink screen is something about framebuffer.

[DONAHUE]

perhaps a problem in your kernel configuration?
suggest boot system rescue cd/usb, mount the gentoo partitions, run:

[stavross]

lspci -k | wgetpaste -t :
http://bpaste.net/show/4164c1e8dc76

wgetpaste -t /mnt/gentoo/usr/src/linux/.config
http://bpaste.net/show/76f414b021f5

wgetpaste -t /mnt/gentoo/var/log/dmesg

[NeddySeagoon]

stavross,

Welcome to Gentoo.

This sounds like several drivers fighting over the hardware. Its harmless but it won't work.
As well as the things DONAHUE has asked for, the output of

[stavross]

I'd prefer to use the nouveau drivers if possible. Thanks for the help guys.

Output of lspci -knn: http://bpaste.net/show/8d01cd4ae3d6

[NeddySeagoon]

stavross,

That the console goes pink tells that there is a problem with the console drivers.
That's not a big issue as most of the systems in the world are headless.
The boot should have continued normally, you just wouldn't see it.

That /mnt/gentoo/var/log/dmesg is missing tells that root failed to mount read/write, so the file could not be written.

I don't see anything in you kernel that accounts for the pink screen, so lets try to get root mounted read write to get some more diagnostics.

Please mount your gentoo but do not chroot, then post the following
the output of blkid
the content of grub.cfg
the content of /etc/fstab.
the output of df -Th

To get root mounted read write, the kernel needs to mount root (read only), the init system has to successfully run rootfsck, then root is remounted read write.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[stavross]

I've chroot'ed recently but these outputs are done from outside of chroot.
Outputs:
lsblk: http://bpaste.net/show/3ff42651ecfd
blkid: http://bpaste.net/show/aa81374791b1
Not using grub, trying to use efibootmgr
/mnt/gentoo/etc/fstab: http://bpaste.net/show/5a61b5b68fa7
df -Th: http://bpaste.net/show/b81524f64b22

[NeddySeagoon]

stavross,

Nothing like jumping in the deep end with everything encrypted and LVM :)

[stavross]

Kernel and ramdisk were made using this script: https://github.com/sakaki-/buildkernel
which is doing :https://wiki.gentoo.org/wiki/Sakaki%27s_EFI_Install_Guide/Configuring_and_Building_the_Kernel#What_the_buildkernel_Script_Does_.28Background_Reading.29
Dm-crypt is used (invoked via its cryptsetup interface by the initial, initramfs init script).

[stavross]

I think I may have found the problem: would forgetting to pass CRYPTO_AES option to the kernel config options produce this problem if AES is used as a cipher for the root partition?

[stavross]

Never mind CONFIG_CRYPTO_AES=y is in the .config file used to generate the kernel

[NeddySeagoon]

stavross,

Post something on the Discussion page of the Wiki link. Link this topic.
All the contributors to the page will get an email and Sakaki will be along in a wee while.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[stavross]

Cheers