Difference between pages "Experimental branch" and "Installation Troubleshooting"

From Funtoo
(Difference between pages)
Jump to: navigation, search
 
 
Line 1: Line 1:
{{Note}}Funtoo Experimental is where we test bleeding-edge stuff. Don't use experimental unless you are helping us test new features.
+
This page shows you how to troubleshoot issues with your Funtoo Linux installation.
== Status ==
+
Future plans:
+
* funtoo profile integration
+
* udev and friends bump
+
  
== Introduction ==
+
== Boot failure ==
  
The Funtoo experimental branch is used by Funtoo Core Developers to try and test new features to be included in Funtoo stable and current branches when ready. Users that want to help the developers test those new features are welcome to switch to the experimental branch and report problems on IRC or the forum. However, problems may arise from using it and there is no guarantee that your system will stay usable.
+
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:
  
== Upgrading an existing Funtoo installation to experimental ==
 
 
<console>
 
<console>
###i## rm -rf /usr/portage
+
# ##i##mkdir /mnt/funtoo
###i## nano -w /etc/make.conf
+
# ##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>
 
</console>
Add the following line (or modify it if it's already there):
+
 
 +
Once you are done making changes, leave the chroot, unmount mounted filesystems, and reboot:
 +
 
 
<console>
 
<console>
SYNC="git://github.com/funtoo/experimental-mini-2011.git"
+
(chroot) # ##i##exit
 +
# ##i##umount /mnt/funtoo/boot /mnt/funtoo/dev /mnt/funtoo/proc /mnt/funtoo
 +
# ##i##reboot
 
</console>
 
</console>
  
=== First method ===
+
If you continue to experience difficulties getting Funtoo Linux to boot properly, please ask for help in the [http://forums.funtoo.org/ forums].
<pre>
+
# emerge --sync     
+
</pre>
+
  
Verify that the experimental tree has been properly installed:
+
== Debugging system startup ==
  
<pre>
+
<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>.
# cat /usr/portage/.git/config
+
...
+
[remote "origin"]
+
fetch = +refs/heads/*:refs/remotes/origin/*
+
url = git://github.com/funtoo/experimental-mini-2011.git
+
...
+
</pre>
+
  
You should see that the git repository is pointing to experimental-mini-2011.git.
+
== 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:
  
If for any reason this method did not work, use the second method to manually clone the experimental branch.
 
=== Second method ===
 
 
<pre>
 
<pre>
# rm -rf /usr/portage
+
"Funtoo Linux genkernel" {
# cd /usr
+
        kernel kernel[-v]
# git clone git://github.com/funtoo/experimental-mini-2011.git portage
+
        initrd initramfs[-v]
# emerge --sync
+
        params += real_root=auto
 +
        params += nomodeset
 +
}
 
</pre>
 
</pre>
  
== Installation from an experimental branch stage3 ==
+
Now, save your changes and run <tt>boot-update</tt>:
You can find some stage3s on the Funtoo mirror: [http://ftp.osuosl.org/pub/funtoo/funtoo-experimental/]. These stages are updated weekly, possibly more often during active experimental development.
+
  
== Building stage3s using Metro ==
+
<console>
You may build your own stages of the experimental branch using [[Metro]]. The stages from the Funtoo mirror ([http://ftp.osuosl.org/pub/funtoo/funtoo-experimental/]) can be used as a seed. A funtoo-experimental target is available.
+
(chroot) # ##i##boot-update
 
+
</console>
== History ==
+
 
+
=== Iteration 1 (Completed Dec 16, 2011) ===
+
 
+
Implementation and stabilization of a new set of toolchain packages:
+
 
+
* gcc-4.6.2
+
* binutils-2.21-r1
+
* linux-headers-2.6.39
+
* glibc-2.13-r4
+
* udev-171-r1
+
* patched lvm2-2.02.85
+
* Several patches to solve problems building with this toolchain
+
  
And some other features:
+
Now, exit the chroot, unmount filesystems and reboot following the [[#boot failure|boot failure]] instructions.
* [[Portage Dynamic Slot]]
+
* Modifications of Mesa, libdrm and radeon drivers to support each type of Radeon video card individually, as well as masked -9999 versions of those packages.
+
  
[[Category:Portage]]
 
 
[[Category:HOWTO]]
 
[[Category:HOWTO]]
[[Category:Featured]]
+
[[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.