Installation Troubleshooting - Revision history

Drobbins at 03:31, 10 February 2012

2012-02-10T03:31:52Z

Drobbins at 03:31, 10 February 2012

2012-02-10T03:31:38Z

Drobbins at 03:01, 10 February 2012

2012-02-10T03:01:42Z

Drobbins at 03:01, 10 February 2012

2012-02-10T03:01:07Z

Drobbins at 02:57, 10 February 2012

2012-02-10T02:57:37Z

Drobbins: Created page with "==== Troubleshooting a failed install ==== ===== boot failure ===== If you did not get a `login:` prompt, it's possible that your install was not successful. You can ..."

2012-02-10T02:57:19Z

Created page with "==== Troubleshooting a failed install ==== ===== boot failure ===== If you did not get a <tt>login:</tt> prompt, it's possible that your install was not successful. You can ..."

New page

==== Troubleshooting a failed install ====

===== boot failure =====

If you did not get a <tt>login:</tt> 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:

<console>
# ##i##mkdir /mnt/funtoo
# ##i##mount /dev/sda4 /mnt/funtoo
# ##i##mount /dev/sda1 /mnt/funtoo/boot
# ##i##cd /mnt/funtoo
# ##i##mount --bind /proc proc
# ##i##mount --bind /dev dev
# ##i##cp /etc/resolv.conf etc/
# ##i##env -i HOME=/root TERM=$TERM PATH='/bin:/sbin:/usr/bin:/usr/sbin' chroot /mnt/funtoo
</console>

Once you are done making changes, leave the chroot, unmount mounted filesystems, and reboot:

<console>
(chroot) # ##i##exit
# ##i##umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo
# ##i##reboot
</console>

If you continue to experience difficulties getting Funtoo Linux to boot properly, please ask for help in the [http://forums.funtoo.org/ forums].

===== 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 <tt>/etc/boot.conf</tt> and add the line "<tt>params += nomodeset</tt>" to the "<tt>Funtoo Linux genkernel</tt>" section. It should now look like this:

<pre>
"Funtoo Linux genkernel" {
kernel kernel[-v]
initrd initramfs[-v]
params += real_root=auto
params += nomodeset
}
</pre>

Now, save your changes and run <tt>boot-update</tt>:

<pre>
(chroot) # boot-update
</pre>

Now, exit the chroot, unmount filesystems and reboot following the [[#boot failure|boot failure]] instructions.

@@ Line 30: / Line 30: @@
 <tt>/etc/rc.conf</tt> 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 <tt>rc_logger</tt> to <tt>YES</tt>. This will instruct OpenRC to launch a logging daemon to log the entire rc process to <tt>/var/log/rc.log</tt>.
-== 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 <tt>/etc/boot.conf</tt> and add the line "<tt>params += nomodeset</tt>" to the "<tt>Funtoo Linux genkernel</tt>" section. It should now look like this:

← Older revision		Revision as of 03:01, 10 February 2012
Line 1:		Line 1:
−	~~==== Troubleshooting a failed install ====~~	+	This page shows you how to troubleshoot issues with your Funtoo Linux installation.

	===== boot failure =====		===== boot failure =====

← Older revision		Revision as of 02:57, 10 February 2012
Line 46:		Line 46:

	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.
		+
		+	[[Category:HOWTO]]
		+	[[Category:Install]]

@@ Line 1: / Line 1: @@
 This page shows you how to troubleshoot issues with your Funtoo Linux installation.
-===== boot failure =====
+== boot failure ==
 If you did not get a <tt>login:</tt> 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:
@@ Line 26: / Line 26: @@
 If you continue to experience difficulties getting Funtoo Linux to boot properly, please ask for help in the [http://forums.funtoo.org/ forums].
-===== Graphics Corruption at Boot =====
+== Debugging system startup ==
 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 <tt>/etc/boot.conf</tt> and add the line "<tt>params += nomodeset</tt>" to the "<tt>Funtoo Linux genkernel</tt>" section. It should now look like this:

@@ Line 41: / Line 41: @@
 Now, save your changes and run <tt>boot-update</tt>:
-<pre>
+<console>
-(chroot) # boot-update
+(chroot) # ##i##boot-update
-</pre>
+</console>
 Now, exit the chroot, unmount filesystems and reboot following the [[#boot failure|boot failure]] instructions.

Installation Troubleshooting - Revision history

Drobbins at 03:31, 10 February 2012

Drobbins at 03:31, 10 February 2012

Drobbins at 03:01, 10 February 2012

Drobbins at 03:01, 10 February 2012

Drobbins at 02:57, 10 February 2012

Drobbins: Created page with "==== Troubleshooting a failed install ==== ===== boot failure ===== If you did not get a login: prompt, it's possible that your install was not successful. You can ..."

Drobbins: Created page with "==== Troubleshooting a failed install ==== ===== boot failure ===== If you did not get a `login:` prompt, it's possible that your install was not successful. You can ..."