https://wiki.archlinux.org/api.php?action=feedcontributions&user=15274&feedformat=atomArchWiki - User contributions [en]2024-03-29T15:52:32ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_13&diff=415083Lenovo IdeaPad Yoga 132016-01-13T03:51:43Z<p>15274: /* Overall Status */ Card reader works fine for me</p>
<hr />
<div>[[Category:Lenovo]]<br />
{{Merge|Laptop/Lenovo}}<br />
{{Poor writing|See [[:Category:Laptops]]}}<br />
<br />
Models covered: <br />
Lenovo IdeaPad Yoga 13<br />
<br />
Sub-models options :<br />
{| class="wikitable sortable collapsible" style="text-align: left; "<br />
|-<br />
! Diffefenses<br />
! Value<br />
|-<br />
| CPU || Intel i3, i5, i7<br />
|-<br />
| RAM || 4GB, 8GB<br />
|-<br />
| SSD || 128 GB, 256 GB<br />
|}<br />
== Overall Status ==<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Feature<br />
! Status<br />
|-<br />
| Boot Standard Kernel || OK<br />
|-<br />
| Detect SSD || OK<br />
|-<br />
| CPU Frequency Scaling|| not tested<br />
|-<br />
| Hibernation || not tested<br />
|-<br />
| Sleep / Suspend || OK<br />
|-<br />
| Switch to External Screen || OK<br />
|-<br />
| Wireless/Bluetooth || with troubles<br />
|-<br />
| Wireless/Wifi || with troubles<br />
|-<br />
| Keyboard's Hotkeys || not all<br />
|-<br />
| Touch screen || works, but multitouch is a problem<br />
|-<br />
| Card reader || OK<br />
|}<br />
<br />
== Display ==<br />
Works out of the box. Intel HD 4000<br />
=== Backlight ===<br />
Control of brightness only works after suspend. After wake up, you can control brightness via f11 (less bright) and f12 (more bright).<br />
However, it is not brightnes problem, but keyboard buttons' problem. To control brightness while loaded from scratch, you can do the following command:<br />
<br />
# cat 4882 > /sys/class/backlight/intel_backlight/brightness<br />
<br />
This will change brightness value to 4882. It is maximum brightness level. You can choose some other value, of course.<br />
<br />
=== Touch Screen ===<br />
One touch works out of the box. But it works like a mouse.<br />
<br />
== Keyboard ==<br />
In addition to the keyboard, there are some extra Lenovo keys: <br />
<br />
*Volume + and - work as intended<br />
*Recovery button has no effect while computer is running<br />
*Screen rotation lock button simulates pressing Super + o<br />
*Windows button under the screen simulates pressing Super. Also gives haptic feedback, currently not controllable by software.<br />
<br />
Most media buttons work out of the box:<br />
*Mute on F1 works<br />
*Vol- on F2 works<br />
*Vol+ on F3 works<br />
*Close on F4 works<br />
*Refresh on F5 works<br />
*Disable touchpad on F6 works, but also types the ± symbol<br />
*Airplane mode on F7 does not work<br />
*Choose application on F8 simulates pressing ctrl+alt+tab. The keys are pressed and instantly released, which (depending on your DE) may not have the intended effect.<br />
*Disable display on F9 works<br />
*Change video output on F10 simulates pressing ctrl+p<br />
*Brightness- on F11 works<br />
*Brightness+ on F12 works<br />
<br />
== Configaration ==<br />
=== Wireless Fidelity ===<br />
Internal Wi-Fi driver (r8723au) is working with a huge troubles with current kernel (3.17.6-1-ARCH). So to get wifi work, [[Blacklisting#Blacklisting|blacklist]] r8723 module. Then you should install {{AUR|dkms-8723au-git}}{{Broken package link|{{aur-mirror|dkms-8723au-git}}}} package and insert 8723au module.<br />
<br />
=== Bluetooth ===<br />
???<br />
<br />
== Hardware ==<br />
<br />
=== PCI devices ===<br />
{{hc|lspci|<br />
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)<br />
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)<br />
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)<br />
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)<br />
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)<br />
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)<br />
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)<br />
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)<br />
00:1f.0 ISA bridge: Intel Corporation QS77 Express Chipset LPC Controller (rev 04)<br />
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)<br />
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)<br />
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)<br />
}}<br />
<br />
== See also ==<br />
* https://wiki.debian.org/InstallingDebianOn/Lenovo/IdeaPad_Yoga_13_(Wheezy)<br />
* [[wikipedia:Lenovo IdeaPad Yoga 13|Lenovo IdeaPad Yoga 13]]</div>15274https://wiki.archlinux.org/index.php?title=Lenovo_IdeaPad_Yoga_13&diff=415082Lenovo IdeaPad Yoga 132016-01-13T03:48:48Z<p>15274: /* Keyboard */ Added more detailed keycode information, improved formatting</p>
<hr />
<div>[[Category:Lenovo]]<br />
{{Merge|Laptop/Lenovo}}<br />
{{Poor writing|See [[:Category:Laptops]]}}<br />
<br />
Models covered: <br />
Lenovo IdeaPad Yoga 13<br />
<br />
Sub-models options :<br />
{| class="wikitable sortable collapsible" style="text-align: left; "<br />
|-<br />
! Diffefenses<br />
! Value<br />
|-<br />
| CPU || Intel i3, i5, i7<br />
|-<br />
| RAM || 4GB, 8GB<br />
|-<br />
| SSD || 128 GB, 256 GB<br />
|}<br />
== Overall Status ==<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Feature<br />
! Status<br />
|-<br />
| Boot Standard Kernel || OK<br />
|-<br />
| Detect SSD || OK<br />
|-<br />
| CPU Frequency Scaling|| not tested<br />
|-<br />
| Hibernation || not tested<br />
|-<br />
| Sleep / Suspend || OK<br />
|-<br />
| Switch to External Screen || OK<br />
|-<br />
| Wireless/Bluetooth || with troubles<br />
|-<br />
| Wireless/Wifi || with troubles<br />
|-<br />
| Keyboard's Hotkeys || not all<br />
|-<br />
| Touch screen || works, but multitouch is a problem<br />
|-<br />
| Card reader || not tested<br />
|}<br />
<br />
== Display ==<br />
Works out of the box. Intel HD 4000<br />
=== Backlight ===<br />
Control of brightness only works after suspend. After wake up, you can control brightness via f11 (less bright) and f12 (more bright).<br />
However, it is not brightnes problem, but keyboard buttons' problem. To control brightness while loaded from scratch, you can do the following command:<br />
<br />
# cat 4882 > /sys/class/backlight/intel_backlight/brightness<br />
<br />
This will change brightness value to 4882. It is maximum brightness level. You can choose some other value, of course.<br />
<br />
=== Touch Screen ===<br />
One touch works out of the box. But it works like a mouse.<br />
<br />
== Keyboard ==<br />
In addition to the keyboard, there are some extra Lenovo keys: <br />
<br />
*Volume + and - work as intended<br />
*Recovery button has no effect while computer is running<br />
*Screen rotation lock button simulates pressing Super + o<br />
*Windows button under the screen simulates pressing Super. Also gives haptic feedback, currently not controllable by software.<br />
<br />
Most media buttons work out of the box:<br />
*Mute on F1 works<br />
*Vol- on F2 works<br />
*Vol+ on F3 works<br />
*Close on F4 works<br />
*Refresh on F5 works<br />
*Disable touchpad on F6 works, but also types the ± symbol<br />
*Airplane mode on F7 does not work<br />
*Choose application on F8 simulates pressing ctrl+alt+tab. The keys are pressed and instantly released, which (depending on your DE) may not have the intended effect.<br />
*Disable display on F9 works<br />
*Change video output on F10 simulates pressing ctrl+p<br />
*Brightness- on F11 works<br />
*Brightness+ on F12 works<br />
<br />
== Configaration ==<br />
=== Wireless Fidelity ===<br />
Internal Wi-Fi driver (r8723au) is working with a huge troubles with current kernel (3.17.6-1-ARCH). So to get wifi work, [[Blacklisting#Blacklisting|blacklist]] r8723 module. Then you should install {{AUR|dkms-8723au-git}}{{Broken package link|{{aur-mirror|dkms-8723au-git}}}} package and insert 8723au module.<br />
<br />
=== Bluetooth ===<br />
???<br />
<br />
== Hardware ==<br />
<br />
=== PCI devices ===<br />
{{hc|lspci|<br />
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)<br />
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)<br />
00:04.0 Signal processing controller: Intel Corporation 3rd Gen Core Processor Thermal Subsystem (rev 09)<br />
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)<br />
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)<br />
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)<br />
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)<br />
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)<br />
00:1f.0 ISA bridge: Intel Corporation QS77 Express Chipset LPC Controller (rev 04)<br />
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)<br />
00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)<br />
00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series Chipset Family Thermal Management Controller (rev 04)<br />
}}<br />
<br />
== See also ==<br />
* https://wiki.debian.org/InstallingDebianOn/Lenovo/IdeaPad_Yoga_13_(Wheezy)<br />
* [[wikipedia:Lenovo IdeaPad Yoga 13|Lenovo IdeaPad Yoga 13]]</div>15274https://wiki.archlinux.org/index.php?title=Kernel_mode_setting&diff=278790Kernel mode setting2013-10-15T17:05:40Z<p>15274: /* Late KMS start */</p>
<hr />
<div>[[Category:Graphics]]<br />
[[Category:Kernel]]<br />
[[Category:X Server]]<br />
[[es:Kernel Mode Setting]]<br />
[[hu:Kernel Mode Setting]]<br />
[[ja:Kernel Mode Setting]]<br />
[[zh-CN:Kernel Mode Setting]]<br />
[[zh-TW:Kernel Mode Setting]]<br />
{{Article summary start|Summary}}<br />
{{Article summary text|Information about configuring the Kernel Mode Setting method.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|ATI}}<br />
{{Article summary wiki|Intel}}<br />
{{Article summary wiki|Nouveau}}<br />
{{Article summary end}}<br />
<br />
Kernel [[Wikipedia:Mode-setting|Mode Setting]] (KMS) is a method for setting display resolution and depth in the kernel space rather than user space.<br />
<br />
The Linux kernel's implementation of KMS enables native resolution in the framebuffer and allows for instant console (tty) switching. KMS also enables newer technologies (such as DRI2) which will help reduce artifacts and increase 3D performance, even kernel space power-saving.<br />
<br />
{{Note|The proprietary [[NVIDIA|nvidia]] and [[AMD Catalyst|catalyst]] drivers also implement kernel mode-setting, but as they do not use the built-in kernel implementation, they lack an fbdev driver for the high-resolution console.}}<br />
<br />
== Background ==<br />
Previously, setting up the video card was the job of the X server. Because of this, it was not easily possible to have fancy graphics in virtual consoles. Also, each time a switch from X to a virtual console was made ({{ic|Ctrl+Alt+F1}}), the server had to give control over the video card to the kernel, which was slow and caused flickering. The same "painful" process happened when the control was given back to the X server ({{ic|Ctrl+Alt+F7}}).<br />
<br />
With Kernel Mode Setting (KMS), the kernel is now able to set the mode of the video card. This makes fancy graphics during bootup, virtual console and X fast switching possible, among other things.<br />
== Installation ==<br />
At first, note that for ''any'' method you use, you should ''always'' disable:<br />
* Any "vga=" options in your bootloader as these will conflict with the native resolution enabled by KMS.<br />
* Any "video=" lines that enable a framebuffer that conflicts with the driver.<br />
* Any other framebuffer drivers (such as [[uvesafb]]).<br />
<br />
=== Late KMS start===<br />
[[Intel]], [[Nouveau]] and [[ATI]] drivers already enable KMS automatically for all chipsets, so you need not install it manually.<br />
<br />
The proprietary [[NVIDIA]] and [[AMD Catalyst]] drivers do not use the open driver stack. In order to use KMS you should replace them with open source drivers.<br />
<br />
=== Early KMS start ===<br />
<br />
To load KMS as early as possible in boot process, add the module [[radeon]] (for ATI/AMD cards), [[Intel|i915]] (for Intel integrated graphics) or [[nouveau]] (for Nvidia cards) to the {{ic|MODULES}} line in {{ic|/etc/mkinitcpio.conf}}. For example:<br />
{{hc|/etc/mkinitcpio.conf|2=MODULES="... i915 ..."}}<br />
If you are using a custom EDID file (not applicable for the built-in resolutions), you should embed it into initramfs as well:<br />
<br />
{{hc|/etc/mkinitcpio.conf|<br />
2=FILES="/lib/firmware/edid/your_edid.bin"}}<br />
<br />
Rebuild your kernel image (refer to the [[mkinitcpio]] article for more info):<br />
<br />
{{bc|# mkinitcpio -p <name of your kernel preset; e.g. ''linux''>}}<br />
<br />
==Troubleshooting==<br />
<br />
===My fonts are too tiny===<br />
See [[Fonts#Changing_the_default_font | changing the default font]] for how to change your console font to a large font. Terminus font in [community] is available in many sizes, including larger sizes.<br />
<br />
===Issue upon bootloading and dmesg===<br />
Polling for connected display devices on older systems can be quite expensive. Poll will happen periodically and can in worst cases take several hundred milliseconds, depending on the hardware. This will cause visible stalls, for example in video playback. These stalls might happen even when your video is on HDP output but you have other non HDP outputs in your hw configuration. If you experience stalls in display output occurring every 10 seconds, disabling polling might help.<br />
<br />
If you see an error code of 0x00000010 (2) while booting up, (You will get about 10 lines of text, the last part denoting that error code), then add the following line into {{ic|/etc/modprobe.d/modprobe.conf}}:<br />
options drm_kms_helper poll=0<br />
<br />
==Forcing modes and EDID==<br />
<br />
{{Note|This section is a WIP. Improvements and corrections are more than welcome}}<br />
<br />
In case that your monitor/TV is not sending the appropriate [[Wikipedia:EDID|EDID]] data or similar problems, you will notice that the native resolution is not automatically configured or no display at all. The kernel has a provision to load the binary EDID data, and provides as well data to set four of the most typical resolutions.<br />
<br />
If you have the EDID file for your monitor the process is easy. If you don't have, you can either use one of the built-in resolution-EDID binaries (or generate one during kernel compilation, [http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/Documentation/EDID/HOWTO.txt more info here]) or build your own EDID.<br />
<br />
In case you have an EDID file (e.g. extracted from Windows drivers for your monitor), create a dir {{ic|edid}} under {{ic|/lib/firmware}}:<br />
<br />
# mkdir /lib/firmware/edid<br />
<br />
and then copy your binary into the {{ic|/lib/firmware/edid}} directory.<br />
<br />
To load it at boot, specify the following in the kernel command line:<br />
<br />
{{bc|1=drm_kms_helper.edid_firmware=edid/your_edid.bin}}<br />
<br />
You can also specify it only for a specified connection:<br />
<br />
{{bc|1=drm_kms_helper.edid_firmware=VGA-1:edid/your_edid.bin}}<br />
<br />
For the four built-in resolutions, see table below for the name to specify:<br />
<br />
{| border="1" <br />
|-<br />
| '''Resolution''' || '''Name to specify''' <br />
|-<br />
| 1024x768 || edid/1024x768.bin <br />
|-<br />
| 1280x1024 || edid/1280x1024.bin <br />
|-<br />
| 1600x1200 (kernel 3.10 or higher) || edid/1600x1200.bin<br />
|-<br />
| 1680x1050 || edid/1680x1050.bin <br />
|-<br />
| 1920x1080 || edid/1920x1080.bin <br />
|}<br />
<br />
If you are doing early KMS, you must include the custom EDID file in the initramfs or you will run into problems.<br />
<br />
You can also construct your own EDID with the makefile included in the {{ic|Documentation/EDID}} sources of the kernel. The full information can be read [http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/EDID/HOWTO.txt here] and [https://www.osadl.org/Single-View.111+M591850c02b5.0.html there].<br />
<br />
{{Warning|The method described below is somehow incomplete because e.g. Xorg does not take into account the resolution specified, so users are encouraged to use the method described above; however, specifying resolution with {{ic|1=video=}} command line may be useful in some scenarios}}<br />
<br />
From [http://nouveau.freedesktop.org/wiki/KernelModeSetting the nouveau wiki]:<br />
<br />
A mode can be forced on the kernel command line. Unfortunately, the command line option video is poorly documented in the DRM case. Bit and pieces on how to use it can be found in<br />
<br />
*http://cgit.freedesktop.org/nouveau/linux-2.6/tree/Documentation/fb/modedb.txt<br />
*http://cgit.freedesktop.org/nouveau/linux-2.6/tree/drivers/gpu/drm/drm_fb_helper.c <br />
<br />
The format is: <br />
video=<conn>:<xres>x<yres>[M][R][-<bpp>][@<refresh>][i][m][eDd]<br />
<br />
*<conn>: Connector, e.g. DVI-I-1, see your kernel log.<br />
*<xres> x <yres>: resolution<br />
*M: compute a CVT mode?<br />
*R: reduced blanking?<br />
*-<bpp>: color depth<br />
*@<refresh>: refresh rate<br />
*i: interlaced (non-CVT mode)<br />
*m: margins?<br />
*e: output forced to on<br />
*d: output forced to off<br />
*D: digital output forced to on (e.g. DVI-I connector) <br />
<br />
You can override the modes of several outputs using "video" several times, for instance, to force DVI to 1024x768 at 85 Hz and TV-out off: <br />
video=DVI-I-1:1024x768@85 video=TV-1:d<br />
<br />
==Disabling modesetting==<br />
<br />
You may want to disable KMS for various reasons, such as getting a blank screen or a "no signal" error from the display, when using the Catalyst driver, etc. To disable KMS add {{ic|nomodeset}} as a kernel parameter. See [[Kernel parameters]] for more info.<br />
<br />
Along with {{ic|nomodeset}} kernel parameter, for Intel graphics card you need to add {{ic|1=i915.modeset=0}} and for Nvidia graphics card you need to add {{ic|1=nouveau.modeset=0}}. For Nvidia Optimus dual-graphics system, you need to add all the three kernel parameters (i.e. {{ic|1="nomodeset i915.modeset=0 nouveau.modeset=0"}}).<br />
<br />
{{Note|Some [[Xorg]] drivers will not work with KMS disabled. See the wiki page on your specific driver for details.}}</div>15274https://wiki.archlinux.org/index.php?title=Cinnamon&diff=272678Cinnamon2013-08-26T19:40:37Z<p>15274: /* Icons do not show on the desktop */</p>
<hr />
<div>[[Category:Desktop environments]]<br />
[[ja:Cinnamon]]<br />
[[ru:Cinnamon]]<br />
[[tr:Cinnamon_Masaüstü_Ortamı]]<br />
{{Article summary start}}<br />
{{Article summary text|This article covers basic installation procedures and configuration methods in Cinnamon.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|GNOME}}: GNOME is the framework that Cinnamon is based on.<br />
{{Article summary wiki|MATE}}: Another fork of GNOME that is geared towards a GNOME 2 experience.<br />
{{Article summary end}}<br />
<br />
[http://cinnamon.linuxmint.com/ Cinnamon] is a Linux desktop which provides advanced innovative features and a traditional user experience. <br />
The desktop layout is similar to GNOME 2; however, the underlying technology was forked from GNOME Shell.<br />
The emphasis is put on making users feel at home and providing them with an easy to use and comfortable desktop experience.<br />
<br />
==Installation==<br />
<br />
Cinnamon can be [[Pacman|installed]] with the package {{Pkg|cinnamon}}, available in the [[official repositories]].<br />
<br />
To get a complete desktop interface, install at least the following additional packages:<br />
* {{Pkg|cinnamon-control-center}}: provides access to various hardware and system settings within cinnamon-settings.<br />
* {{Pkg|cinnamon-screensaver}}: provides a lock screen functionality.<br />
* {{Pkg|nemo}}: Cinnamon's official file manager.<br />
<br />
=== Starting Cinnamon ===<br />
<br />
'''Graphical log-in'''<br />
<br />
Simply choose '''Cinnamon''' or '''Cinnamon (Software Rendering)''' session from your favourite [[display manager]]. Cinnamon is the 3D accelerated version, which should be normally used. If you experience problems with your video driver (e.g. artifacts or crashing), try the Cinnamon (Software Rendering) session, which disables 3D acceleration.<br />
<br />
'''Starting Cinnamon manually'''<br />
<br />
If you prefer to start Cinnamon manually from the console, add the following line to your {{ic|~/.xinitrc}} file:<br />
{{hc|~/.xinitrc|<nowiki><br />
exec gnome-session-cinnamon<br />
</nowiki>}}<br />
<br />
If the Cinnamon (Software Rendering) session is required, use {{ic|gnome-session-cinnamon2d}} instead of {{ic|gnome-session-cinnamon}}.<br />
<br />
After the {{ic|exec}} command is placed, Cinnamon can be launched by typing {{ic|startx}}. See [[xinitrc]] for details.<br />
<br />
==Configuration==<br />
<br />
Cinnamon is quite easy to configure - a lot of the configuration that most people will want can be done graphically. Its usability can be customized with [http://cinnamon-spices.linuxmint.com/applets applets] and [http://cinnamon-spices.linuxmint.com/extensions extensions], and also it supports [http://cinnamon-spices.linuxmint.com/themes theming]. <br />
<br />
===Cinnamon Settings===<br />
<br />
Simply run the following command:<br />
{{bc|cinnamon-settings}}<br />
<br />
Each settings panel can be accessed directly with the following commands:<br />
{{bc|cinnamon-settings panel<br />
cinnamon-settings calendar<br />
cinnamon-settings themes<br />
cinnamon-settings applets<br />
cinnamon-settings windows<br />
cinnamon-settings fonts<br />
cinnamon-settings hotcorner}} so on.<br />
<br />
===Installing applets/extensions===<br />
<br />
{{Note|Previously, {{AUR|cinnamon-extensions-git}} and {{AUR|cinnamon-themes-git}} were used to install some themes and extensions, but they are now deprecated (see [https://github.com/linuxmint/Cinnamon/issues/668 here]). Instead, visit http://cinnamon-spices.linuxmint.com/.}}<br />
<br />
The difference between an applet and an extension is that an '''applet''' is basically an addition to a panel, whereas an '''extension''' can completely change the Cinnamon experience and can do much more than an applet.<br />
<br />
There are quite a few packages in the [https://aur.archlinux.org/packages.php?O=0&K=cinnamon&do_Search=Go AUR] (AUR package search for cinnamon). The process described here is a generic installation process.<br />
<br />
Installing applets in Cinnamon is relatively easy. First visit [http://cinnamon-spices.linuxmint.com/applets Cinnamon Applets] to see all of the current applets.<br />
Download the zip file for the desired applet, and extract to {{ic|~/.local/share/cinnamon/applets/}} or {{ic|/usr/share/cinnamon/applets}}.<br />
Then run<br />
{{bc|cinnamon-settings applets}}<br />
to bring up the graphical applets manager. If the applet does not show up, press {{Keypress|Alt+F2}} and type {{ic|r}} and press {{keypress|Enter}}. This will restart gnome-shell and likely, the new applet.<br />
<br />
The process is analogous for extensions, with the only difference being that directories titled "applets" can be changed to "extensions".<br />
<br />
==Tips and tricks==<br />
<br />
===Creating custom applets/themes===<br />
The official tutorial on creating an '''applet''' can be found [http://cinnamon.linuxmint.com/?p=156 here], and on creating a '''custom theme''' can be found [http://cinnamon.linuxmint.com/?p=144 here].<br />
<br />
===Default desktop background wallpaper path===<br />
When you add a wallpaper from a custom path in Cinnamon Settings, Cinnamon copies it to {{ic|~/.cinnamon/background}}. Thus, with every change of your wallpaper you would have to add your updated wallpaper again from the settings menu or copy / symlink it manually to {{ic|~/.cinnamon/background}}.<br />
<br />
==Troubleshooting==<br />
<br />
===QGtkStyle unable to detect the current theme===<br />
Installing {{Pkg|libgnome-data}} solves the problem partially, and QGtkStyle will detect the current GTK+ theme. However, to set the same icon and cursor theme, users must specify them explicitly.<br />
<br />
The icon theme for Qt apps can be configured by the following command:<br />
<br />
$ gconftool-2 --set --type string /desktop/gnome/interface/icon_theme Faenza-Dark<br />
<br />
This sets the icon theme to Faenza-Dark located in {{ic|/usr/share/icons/Faenza-Dark}}. <br />
<br />
The cursor theme for Qt apps can be selected by creating a symbolic link:<br />
<br />
$ mkdir ~/.icons<br />
$ ln -s /usr/share/icons/Adwaita ~/.icons/default<br />
<br />
This sets the cursor theme to Adwaita located in {{ic|/usr/share/icons/Adwaita}}.<br />
<br />
===Pressing power buttons suspend the system===<br />
This is the default behaviour. To show the shutdown menu for example, change the setting for the respective button:<br />
<br />
$ gsettings set org.gnome.settings-daemon.plugins.power button-power 'interactive'<br />
<br />
===Icons do not show on the desktop===<br />
<br />
The desktop icons rendering feature is enabled in nemo, and disabled in nautilus by default. To enable this feature, change the setting for nemo: <br />
<br />
$ gsettings set org.nemo.desktop show-desktop-icons true<br />
<br />
Or for nautilus:<br />
<br />
$ gsettings set org.gnome.desktop.background show-desktop-icons true<br />
<br />
Make sure to '''not''' enable both settings, otherwise the desktop icons will be not rendered. The feature can be disabled by calling the commands above, but replace 'true' with 'false'.<br />
<br />
===Volume level is not saved===<br />
The volume level is not be saved after reboot. The volume will be at 0 but not muted. Installing {{Pkg|alsa-utils}} will solve the problem.<br />
<br />
===Applets not working===<br />
If audio or network applets don't work the user may be required to be added to the relevant groups (audio, network):<br />
<br />
$ gpasswd -a [user] [group]<br />
<br />
===Crashing/freezing with Intel graphics after GNOME Shell update===<br />
It is possible that the update to GNOME Shell 3.8 may be the cause of these issues. If Cinnamon worked prior to GNOME Shell 3.8, try creating {{ic|/etc/X11/xorg.conf.d/20-intel.conf}} and adding the following to it to enable SNA acceleration. More information about this can be found [https://wiki.archlinux.org/index.php/Intel_Graphics#Choose_acceleration_method here].<br />
<br />
{{hc|/etc/X11/xorg.conf.d/20-intel.conf|<br />
Section "Device"<br />
Identifier "Intel Graphics"<br />
Driver "intel"<br />
Option "AccelMethod" "sna"<br />
EndSection}}</div>15274https://wiki.archlinux.org/index.php?title=DSDT&diff=271612DSDT2013-08-18T17:52:25Z<p>15274: </p>
<hr />
<div>[[Category:Boot process]]<br />
[[Category:Kernel]]<br />
[[Category:Power management]]<br />
{{Article summary start}}<br />
{{Article summary text|Describes DSDT, part of ACPI specification.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|ACPI modules}}<br />
{{Article summary wiki|acpid}}<br />
{{Article summary end}}<br />
DSDT (Differentiated System Description Table) is a part of the [[Wikipedia:Advanced Configuration and Power Interface|ACPI]] specification. It supplies information about supported power events in a given system. ACPI tables are provided in firmware from the manufacturer. A common Linux problem is missing ACPI functionality, such as: fans not running, screens not turning off when the lid is closed, etc. This can stem from DSDTs made with Windows specifically in mind, which can be patched after installation. The goal of this article is to analyze and rebuild a faulty DSDT, so that the kernel can override the default one.<br />
<br />
Basically a DSDT table is the code run on ACPI (Power Management) events.<br />
<br />
{{Note|The goal of the [http://www.lesswatts.org/projects/acpi/ Linux ACPI] project is that Linux should work on unmodified firmware. If you still find this type of workaround necessary on modern kernels then you should consider [[Reporting Bug Guidelines|submiting a bug report]]. }}<br />
<br />
==Before you start...==<br />
* It is possible that the hardware manufacturer has released an updated firmware which fixes ACPI related problems. Installing an updated firmware is often preferred over this method because it would avoid duplication of effort.<br />
* This process does tamper with some fairly fundamental code on your installation. You will want to be absolutely sure of the changes you make. You might also wish to [[Disk cloning | clone your disk]] beforehand.<br />
* Even before attempting to fix your DSDT yourself, you can attempt a couple of different shortcuts: <br />
<br />
===Tell the kernel to report a version of Windows===<br />
<br />
Use the variable '''acpi_os_name''' as a kernel parameter. For example:<br />
<br />
acpi_os_name="Microsoft Windows NT"<br />
<br />
Or<br />
<br />
acpi_osi="!Windows2012"<br />
appended to the kernel line in grub legacy configuration<br />
<br />
other strings to test:<br />
* "Microsoft Windows XP"<br />
* "Microsoft Windows 2000"<br />
* "Microsoft Windows 2000.1"<br />
* "Microsoft Windows ME: Millennium Edition"<br />
* "Windows 2001"<br />
* "Windows 2006"<br />
* "Windows 2009"<br />
* "Windows 2012"<br />
* when all that fails, you can even try "Linux"<br />
<br />
Out of curiousity, you can follow the steps below to extract your DSDT and search the .dsl file. Just grep for "Windows" and see what pops up.<br />
<br />
===Find a fixed DSDT===<br />
A DSDT file is originally written in ACPI Source language (an .asl/.dsl file). Using a compiler this can produce an 'ACPI Machine Language' file (.aml) or a hex table (.hex). To incorporate the file in your Arch install, you will need to get hold of a compiled .aml file. - whether this means compiling it yourself or trusting some stranger on the Internet is at your discretion. If you do download a file from the world wide web, it will most likely be a compressed .asl file. So you will need to unzip it and compile it. The upside to this is that you won't have to research specific code fixes yourself.<br />
<br />
Arch users with the same laptop as you are: a minority of a minority of a minority. Try browsing other distro/linux forums for talk about the same model. Likelihood is that they have the same problems and either because there is a lot of them, or because they're tech savvy -- someone there has produced a working DSDT and maybe even provides a precompiled version (again, use at your own risk).<br />
Search engines are your best tools. Try keeping it short: 'model name' + 'dsdt' will probably produce results.<br />
<br />
== Recompiling it yourself ==<br />
Your best resources in this endeavor are going to be [http://en.gentoo-wiki.com/wiki/ACPI/Fix_common_problems The Gentoo wiki article], [http://www.acpi.info ACPI Spec homepage], and [http://www.lesswatts.org/projects/acpi/ Linux ACPI Project] which supercedes the activity that occurred at ''acpi.sourceforge.net''.<br />
In a nutshell, you can use Intel's ASL compiler to turn your systems DSDT table into source code, locate/fix the errors, and recompile. This process is detailed more comprehensively at the [http://en.gentoo-wiki.com/wiki/ACPI/Fix_common_problems Gentoo wiki].<br />
You'll need to install {{Pkg|iasl}} to modify code, and be familiar with [[Kernel_Compilation#Compilation]] to install it.<br />
<br />
'''What compiled the original code?'''<br />
Check if your system's DSDT was compiled using Intel or Microsoft compiler:<br />
{{hc|<nowiki> $ dmesg|grep DSDT</nowiki> |<br />
ACPI: DSDT 00000000bf7e5000 0A35F (v02 Intel CALPELLA 06040000 INTL 20060912)<br />
ACPI: EC: Look up EC in DSDT<br />
}}<br />
In case Microsoft's compiler had been used, abbreviation INTL would instead be MSFT.<br />
In the example, there were 5 errors on decompiling/recompiling the DSDT. Two of them were easy to fix after a bit of googling and delving into the ACPI specification. Three of them were due to different versions of compiler used and are, as later discovered, handled by the ACPICA at boot-time. The ACPICA component of the kernel can handle most of the trivial errors you get while compiling the DSDT. So do not fret yourself over compile errors if your system is ''working the way it should''.<br />
<br />
1.) Extract ACPI tables (as root): {{ic|# cat /sys/firmware/acpi/tables/DSDT > dsdt.dat}}<br />
<br />
2.) Decompile: {{ic|iasl -d dsdt.dat}}<br />
<br />
3.) Recompile: {{ic|iasl -tc dsdt.dsl}}<br />
<br />
4.) Examine errors and fix. e.g.:{{bc|<br />
dsdt.dsl 6727: Name (_PLD, Buffer (0x10) <br />
Error 4105 - Invalid object type for reserved name ^ (found BUFFER, requires Package) }}<br />
{{hc| nano +6727 dsdt.dsl|<br />
(_PLD, Package(1) {Buffer (0x10)...}}<br />
<br />
5.) Compile fixed code: {{ic|iasl -tc dsdt.dsl}} (Might want to try option -ic for C include file to insert into kernel source)<br />
<br />
If it says no errors and no warnings you should be good to go.<br />
<br />
== Using modified code ==<br />
{{Expansion| Detail each method}}<br />
<br />
There are 2 ways to use a custom DSDT Table:<br />
* compiling the custom DSDT into the kernel<br />
* loading the custom DSDT at runtime (not supported)<br />
<br />
=== Compile into kernel ===<br />
You'll want to be familiar with [[Kernels | compiling your own kernel]]. The most straightforward way is with the "traditional" approach.<br />
After compiling DSDT, iasl produce two files: {{ic|dsdt.hex}} and {{ic|dsdt.aml}}.<br />
<br />
'''Using {{ic|menuconfig}}:'''<br />
* Disable "Select only drivers that don't need compile-time external firmware". Located in "Device Drivers -> Generic Driver Options".<br />
* Enable "Include Custom DSDT" and specify the absolute path of your fixed DSDT file ({{ic|dsdt.hex}}, not {{ic|dsdt.aml}}). Located in "Power management and ACPI options -> ACPI (Advanced Configuration and Power Interface) Support".<br />
<br />
<br />
'''Check if you running custom DSDT'''<br />
<br />
Simply type<br />
{{ic|<nowiki>dmesg | grep DSDT</nowiki>}}<br />
<br />
You will see something like that:<br />
{{bc|<nowiki>[ 0.000000] ACPI: Override [DSDT- A M I], this is unsafe: tainting kernel<br />
[ 0.000000] ACPI: DSDT 00000000be9b1190 Logical table override, new table: ffffffff81865af0<br />
[ 0.000000] ACPI: DSDT ffffffff81865af0 0BBA3 (v02 ALASKA A M I 000000F3 INTL 20130517)</nowiki>}}<br />
If you see {{ic|...ACPI: Override...}}, you're running custom DSDT.<br />
<br />
<br />
=== Loading at runtime ===<br />
{{Warning|Loading at runtime don't supports. DSDT hook removed due to bug, see [https://bugs.archlinux.org/task/27906 FS#27906 bug]}}<br />
Luckily the Arch stock kernel supports using a custom DSDT so, first copy the '''.aml''' file compiled by iasl to:<br />
/boot/dsdt.aml<br />
<br />
The bootloader will replace the DSDT so we need a method to include our custom DSDT table into the bootloader image.<br />
Copy the following to '''/etc/grub.d/01_acpi'''<br />
<br />
#!/bin/sh<br />
set -e<br />
<br />
# Uncomment to load custom ACPI table<br />
GRUB_CUSTOM_ACPI="/boot/dsdt.aml"<br />
<br />
<br />
# DON'T MODIFY ANYTHING BELOW THIS LINE!<br />
<br />
<br />
prefix=/usr<br />
exec_prefix=${prefix}<br />
libdir=${exec_prefix}/lib<br />
<br />
<br />
. /usr/share/grub/grub-mkconfig_lib<br />
#. ${libdir}/grub/grub-mkconfig_lib<br />
<br />
<br />
# Load custom ACPI table<br />
if [ x${GRUB_CUSTOM_ACPI} != x ] && [ -f ${GRUB_CUSTOM_ACPI} ] \<br />
&& is_path_readable_by_grub ${GRUB_CUSTOM_ACPI}; then<br />
echo "Found custom ACPI table: ${GRUB_CUSTOM_ACPI}" >&2<br />
prepare_grub_to_access_device `${grub_probe} --target=device ${GRUB_CUSTOM_ACPI}` | sed -e "s/^/ /"<br />
cat << EOF<br />
acpi (\$root)`make_system_path_relative_to_its_root ${GRUB_CUSTOM_ACPI}`<br />
EOF<br />
fi<br />
<br />
Make sure to make this file executable, or it will be ignored by '''grub-mkconfig'''<br />
chmod +x /etc/grub.d/01_acpi<br />
<br />
This will tell GRUB to include the DSDT into its core.img (change GRUB_CUSTOM_ACPI to reflect the path to your .aml file).<br />
Next you will need a new boot image. If you use GRUB run:<br />
grub-mkconfig -o /boot/grub/grub.cfg<br />
<br />
Lastly, recreate your initrd<br />
mkinitcpio -p linux<br />
and reboot. Done!<br />
<br />
To check if you are really using your own DSDT read your table again {{ic|# cat /sys/firmware/acpi/tables/DSDT > dsdt.dat}}<br />
and decompile it with {{ic|iasl -d dsdt.dat}}</div>15274