The Funtoo Linux project has transitioned to "Hobby Mode" and this wiki is now read-only.
Difference between revisions of "Installation Troubleshooting"
| (3 intermediate revisions by the same user not shown) | |||
| Line 24: | Line 24: | ||
}} | }} | ||
If you continue to experience difficulties getting Funtoo Linux to boot properly, please ask for help in the [ | If you continue to experience difficulties getting Funtoo Linux to boot properly, please ask for help in the [https://forums.funtoo.org/ forums] or #funtoo IRC channel. | ||
== Debugging system startup == | == Debugging system startup == | ||
{{c|/etc/rc.conf}} contains system settings related to the system initialization scripts. If you are experiencing problems with the system startup scripts, you may find it beneficial to set {{c|rc_logger}} to {{c|YES}}. This will instruct OpenRC to launch a logging daemon to log the entire rc process to {{c|/var/log/rc.log}}. | |||
== Graphics Corruption at boot == | == Graphics Corruption at boot == | ||
If you experience graphics corruption issues at boot time, you may be experiencing an issue with the [http://fedoraproject.org/wiki/Features/KernelModesetting Kernel Mode Setting subsystem], known as KMS. To resolve this problem, boot from the live CD again [[#boot failure|following the steps above]]. Then, from within the chroot, edit | If you experience graphics corruption issues at boot time, you may be experiencing an issue with the [http://fedoraproject.org/wiki/Features/KernelModesetting Kernel Mode Setting subsystem], known as KMS. To resolve this problem, boot from the live CD again [[#boot failure|following the steps above]]. Then, from within the chroot, edit {{c|etc/boot.conf}} and add the line '''params += nomodeset''' to the "{{c|Funtoo Linux genkernel}}" section. Your {{c|/etc/boot.conf}} should now look like this: | ||
{{file|name=boot.conf|body= | |||
"Funtoo Linux genkernel" { | "Funtoo Linux genkernel" { | ||
kernel kernel[-v] | kernel kernel[-v] | ||
| Line 41: | Line 41: | ||
params += nomodeset | params += nomodeset | ||
} | } | ||
}} | |||
Now, save your changes and run <tt>boot-update</tt>: | Now, save your changes and run <tt>boot-update</tt>: | ||
{{console|body= | |||
(chroot) # ##i##boot-update | (chroot) # ##i##boot-update | ||
}} | |||
Now, exit the chroot, unmount filesystems and reboot following the [[#boot failure|boot failure]] instructions. | Now, exit the chroot, unmount filesystems and reboot following the [[#boot failure|boot failure]] instructions. | ||
Latest revision as of 07:58, August 29, 2018
This page shows you how to troubleshoot issues with your Funtoo Linux installation.
Boot failure
If you did not get a login: prompt, it's possible that your install was not successful. You can reboot from the live CD and bind-mount your existing installation without repartitioning or recreating filesystems, chroot inside, and then check your system to ensure everything is configured properly:
root # mkdir /mnt/funtoo root # mount /dev/sda4 /mnt/funtoo root # mount /dev/sda1 /mnt/funtoo/boot root # cd /mnt/funtoo root # mount --bind /proc proc root # mount --bind /dev dev root # cp /etc/resolv.conf etc/ root # env -i HOME=/root TERM=$TERM PATH='/bin:/sbin:/usr/bin:/usr/sbin' chroot /mnt/funtoo
Once you are done making changes, leave the chroot, unmount mounted filesystems, and reboot:
(chroot) # exit root # umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo root # reboot
If you continue to experience difficulties getting Funtoo Linux to boot properly, please ask for help in the forums or #funtoo IRC channel.
Debugging system startup
/etc/rc.conf contains system settings related to the system initialization scripts. If you are experiencing problems with the system startup scripts, you may find it beneficial to set rc_logger to YES. This will instruct OpenRC to launch a logging daemon to log the entire rc process to /var/log/rc.log.
Graphics Corruption at boot
If you experience graphics corruption issues at boot time, you may be experiencing an issue with the Kernel Mode Setting subsystem, known as KMS. To resolve this problem, boot from the live CD again following the steps above. Then, from within the chroot, edit etc/boot.conf and add the line params += nomodeset to the "Funtoo Linux genkernel" section. Your /etc/boot.conf should now look like this:
boot.conf "Funtoo Linux genkernel" {
kernel kernel[-v]
initrd initramfs[-v]
params += real_root=auto
params += nomodeset
}
Now, save your changes and run boot-update:
(chroot) # boot-update
Now, exit the chroot, unmount filesystems and reboot following the boot failure instructions.