Difference between pages "Talk:Funtoo Linux Kernels" and "Installation Troubleshooting"

(Difference between pages)
(tuxonice-sources: new section)
 
 
Line 1: Line 1:
config-extract need update, doesn't work with recent debian-kernels. binary flag not working as there is no default .config generated by config-extract.
+
This page shows you how to troubleshoot issues with your Funtoo Linux installation.
http://kernel.alioth.debian.org/config/ providing kernel configs used in debian releases
+
  
== tuxonice-sources ==
+
== Boot failure ==
  
I am using my laptop for development and all desktop stuff. (LXDE with compiz - looks great, works fine, consumes few power)
+
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:
  
When I switch on my machine I see my funtoo grub theme. This is followed by my funtoo boottime splash. This is also schown when suspending, hibernating and waking up and shutdown.
+
<console>
This works great with tuxonice-sources and splashutils.
+
# ##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>
  
Each time "funtoo" starts, I feel save and home. This is my machine, it looks good and works even better.
+
Once you are done making changes, leave the chroot, unmount mounted filesystems, and reboot:
  
Maybe somebody else wants his/her machine to fit exactly his/her requirements. Then You may want to have a look at tuxonice-sources.
+
<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].
 +
 
 +
== Debugging system startup ==
 +
 
 +
<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 ==
 +
 
 +
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. Your <tt>/etc/boot.conf</tt> 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>:
 +
 
 +
<console>
 +
(chroot) # ##i##boot-update
 +
</console>
 +
 
 +
Now, exit the chroot, unmount filesystems and reboot following the [[#boot failure|boot failure]] instructions.
 +
 
 +
[[Category:HOWTO]]
 +
[[Category:Install]]
 +
[[Category:Official Documentation]]

Latest revision as of 00:26, 13 March 2014

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:

# mkdir /mnt/funtoo
# mount /dev/sda4 /mnt/funtoo
# mount /dev/sda1 /mnt/funtoo/boot
# cd /mnt/funtoo
# mount --bind /proc proc
# mount --bind /dev dev
# cp /etc/resolv.conf etc/
# 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
# umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo 
# reboot

If you continue to experience difficulties getting Funtoo Linux to boot properly, please ask for help in the forums.

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:

"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.