Difference between pages "X Window System" and "Package:Vanilla Sources"

(Difference between pages)
(correct xf86-input-evdev emerge)
 
m (linux torvalds to linus torvalds.)
 
Line 1: Line 1:
=== X.Org ===
+
{{Ebuild
 +
|Summary=The vanilla sources are the pure, unadulterated kernel sources as release by Linus Torvalds himself. No additional patches are applied.
 +
|CatPkg=sys-kernel/vanilla-sources
 +
|Maintainer=
 +
|Homepage=https://www.kernel.org/
 +
}}
 +
The vanilla sources supply the source code for the Linux kernel in an unadulterated form. Linux was ultimately created by Linus Torvalds, and the vanilla kernel is the result of what has been accepted by him into the kernel. There are no additional patches applied.
  
In order to use a graphical environment it's necessary to install X.Org, which is an implementation of the X Window system.  
+
Often, you'll point /usr/src/linux to the source code of the kernel you are currently using.
  
Before we start it's a good idea to make sure that your system is configured correctly. If you've installed your kernel using the <code>binary</code> USE flag, chances are that your video card is already supported.
+
To configure the kernel, you can do so with make menuconfig for a curses-based configuration menu, oldconfig for text only prompts. There is also an availability of building similar configuration menus for X windowing toolkits.
 
+
{{EbuildFooter}}
You should also find your IP address, because if X freezes and you need to get out of it, the safest way is to SSH in from another computer/smartphone/tablet and issue
+
<console>
+
# ##i##killall X
+
</console>
+
 
+
In order for Portage to know which [[Video | video]] card(s) you want to support, you'll need to add a line to your <code>[[make.conf | make.conf]]</code>.
+
<console>
+
# ##i##nano -w /etc/portage/make.conf
+
...
+
VIDEO_CARDS="intel"
+
</console>
+
 
+
In the example above we're using Intel integrated graphics drivers. Examples of valid entries include <code>radeon</code> for AMD Radeon cards, and <code>nouveau</code> or <code>nvidia</code> for NVIDIA cards. If you haven't yet switched to the <code>desktop</code> profile it's a good idea to do it now.
+
 
+
Next comes the actual installation:
+
<console>
+
# ##i##emerge xorg-x11
+
</console>
+
 
+
Now we need to test to make sure X.Org is working properly. To test it we will install twm, a simple window manager which has traditionally served as the standard window manager for X.Org. In Funtoo Linux it is included in the core X.Org meta-package <code>x11-apps/xinit</code>, but is not installed by default.
+
 
+
It is possible to install twm directly by merging <code>x11-wm/twm</code> but for the sake of this tutorial we will install the meta-package, which includes a few extra utilities which may come in handy. There are two ways to do this depending on whether you want it to be installed temporarily or permanently. If you just want it to test X.Org use the following command:
+
<console>
+
# ##i##USE="-minimal" emerge -1 xinit
+
</console>
+
 
+
The <code>minimal</code> USE flag is used in some ebuilds to install the bare minimum needed to get a working system. By passing <code>USE="-minimal"</code> to the command line before <code>emerge</code>, we are telling Portage to disable the flag and install the complete package. The <code>-1</code> (<code>--oneshot</code>) following <code>emerge</code> tells Portage not to add the package to [[#Updating your system|<code>world</code>]]. This is useful when installing packages which are automatically pulled in as dependencies by other packages.
+
 
+
If you want the package installed permanently you will need to add a line to <code>package.use</code>:
+
<console>
+
# ##i##echo 'x11-apps/xinit -minimal' >> /etc/portage/package.use
+
</console>
+
 
+
Next we reinstall <code>x11-apps/xinit</code>:
+
<console>
+
# ##i##emerge -1N xinit
+
</console>
+
 
+
Once that's done, we're able to finally test X.Org:
+
 
+
<console>
+
# ##i##startx
+
</console>
+
 
+
If everything is well, a simple GUI along with an analog clock and a terminal will appear.
+
 
+
====Keyboard/Mouse====
+
 
+
If you have no keyboard/mouse input in x11, check if your kernel supports dev
+
<console>
+
# ##i##zcat /proc/config.gz | grep EVDEV
+
</console>
+
if your output is:
+
<console>
+
CONFIG_INPUT_EVDEV=y
+
</console>
+
Install xf86-input-evdev
+
<console>
+
# ##i##emerge xf86-input-evdev
+
</console>
+
 
+
[[Category:First Steps]]
+

Latest revision as of 00:23, November 7, 2014

sys-kernel/vanilla-sources


Source Repository:Repository:Gentoo Portage Tree

https://www.kernel.org/

Summary: The vanilla sources are the pure, unadulterated kernel sources as release by Linus Torvalds himself. No additional patches are applied.

Use Flags

deblob
Remove binary blobs from kernel sources to provide libre license compliance.

News

Drobbins

IP Space Migration Continues

All Funtoo user containers in the 8.28 IP space will be moving into our new IP space (172.97) over the next few days. If you have DNS set up -- be sure to watch your container and update to the new IP! container.host.funtoo.org DNS will be updated after the move.
2015-08-27 by Drobbins
Drobbins

Funtoo Hosting IP Move

Funtoo user containers with IPs in the 72.18.x.x range will be gradually migrating to new IP addresses this week. If you have DNS entries for your containers, please be aware that your DNS will need to be updated.
2015-08-11 by Drobbins
Drobbins

New ARM Stages

New ARM Stages, built with a new toolchain, are now hitting mirrors. Existing ARM users should re-install using these stages (dated Aug 3, 2015 or later,) rather than upgrade using emerge.
2015-08-06 by Drobbins
More...

Vanilla Sources

Tip

We welcome improvements to this page. To edit this page, Create a Funtoo account. Then log in and then click here to edit this page. See our editing guidelines to becoming a wiki-editing pro.

The vanilla sources supply the source code for the Linux kernel in an unadulterated form. Linux was ultimately created by Linus Torvalds, and the vanilla kernel is the result of what has been accepted by him into the kernel. There are no additional patches applied.

Often, you'll point /usr/src/linux to the source code of the kernel you are currently using.

To configure the kernel, you can do so with make menuconfig for a curses-based configuration menu, oldconfig for text only prompts. There is also an availability of building similar configuration menus for X windowing toolkits.