https://wiki.archlinux.org/api.php?action=feedcontributions&user=Davvil&feedformat=atomArchWiki - User contributions [en]2024-03-29T15:07:49ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:NVIDIA&diff=243177Talk:NVIDIA2013-01-07T19:10:05Z<p>Davvil: </p>
<hr />
<div>== (U)EFI support ==<br />
<br />
I was told in [https://bbs.archlinux.org/viewtopic.php?id=136807 this thread] that the proprietary nvidia drivers do not work with EFI (by what appeared to be a senior community member), and repeated attempts to install the drivers on a UEFI system have met with little success. As a result, I am placing the warning back. Apologies if this isn't in keeping with wiki etiquette!<br />
<br />
--[[User:Rsmb|Rsmb]] ([[User talk:Rsmb|talk]]) 02:59, 13 December 2012 (UTC)<br />
<br />
:I had success using the nvidia driver on a efi system by adding 'nomodeset' to the kernel parameters. This prevents kms from loading, which causes a blank screen and is probably the source of the problems most users are seeing. X afterwards works just fine. I was able to play Doom 3 with a high fps rate :)<br />
[[User:Davvil|Davvil]] ([[User talk:Davvil|talk]]) 10:59, 17 December 2012 (UTC)<br />
<br />
:I have also had no problems with the current proprietary drivers after I blacklisted the i915 module on an ASRock Z68 PRO3 GEN3 mobo and a Zotac 9600 GT 512MB video card.<br />
[[User:Polychoron|Polychoron]] ([[User talk:Polychoron|talk]]) 03:44, 27 December 2012 (UTC)<br />
<br />
:Blacklisting i915 also works for me<br />
[[User:Davvil|Davvil]] ([[User talk:Davvil|talk]]) 19:10, 7 January 2013 (UTC)<br />
<br />
== XRandR support ==<br />
As far as i understand it the recent drivers support XRANDR, which is probably much better than Xinerama/Twinview. Should we remove the Xinerame/Twinview instructions alltogether and just mention to use the standard XRandR methods for multiscreen setups?<br />
<br />
== NVoption Online ==<br />
<br />
NVoption Online Version - great tool to make tv-out easy and fast <br />
<br />
[I'm using gmplayer with gl and twinview]<br />
[http://www.sorgonet.com/linux/nv-online/]http://www.sorgonet.com/linux/nv-online/<br />
<br />
== Reword ==<br />
Maybe someone can put this in better words:<br />
Logging out, or switching to a different terminal using ctrl+alt+F<2-9> consistently resulted in a black screen, and killing Xorg with ctrl-alt-backspace resulted in a terminal screen with only the top line visible. It turned out that a 'vga=773' added to kernel line was the cause of this. After removing that the problem was solved. Probably something to do with KMS? B.t.w. I have only used x with 'startx', so possibly specific for that way of starting X.<br />
[[User:rwd|rwd]]<br />
<br />
:Was it with this driver or nouveau? The proprietary drivers don't have KMS. [[User:Thestinger|thestinger]] 17:42, 13 December 2010 (EST)<br />
<br />
This was with the proprietary driver. I originally had put vga=.. because it made gave the bootup screen a higher resolution, and because the beginners guide mentions it (https://wiki.archlinux.org/index.php/Beginners%27_Guide#GRUB). Apart from leaving out the vga option, I discovered that setting it to the native resolution as explained on https://wiki.archlinux.org/index.php/GRUB#Framebuffer_resolution fixes the black screens as well. Maybe a warning for using vga= option with with proprietary drivers would be useful.[[User:rwd|rwd]]<br />
<br />
Well the thing is that vga= is meant for the proprietary drivers only - open source drivers already set the native resolution without a vga command. It can be removed from the beginners' guide though, since it breaks open source drivers, and if the card doesn't support the vga command, it breaks the closed source ones too. [[User:Thestinger|thestinger]] 20:13, 13 December 2010 (EST)<br />
<br />
== Nvidia 173xx ==<br />
The nvidia-173xx package no longer exists (29 Oct 2011). <br />
<br />
Has it been replaced by nvidia-173xx-all? If so, this package hasn't been updated since Feb 2011.<br />
<br />
Will it need to be updated to be able to use the latest xorg 1.11? <br />
<br />
In the meantime, please include instructions for which xorg related packages pacman should ignore.<br />
:[http://mailman.archlinux.org/pipermail/arch-dev-public/2011-October/021764.html] -- [[User:Karol|Karol]] 21:14, 28 October 2011 (EDT)<br />
::I commented out the info about older drivers, since they're not compatible with Xorg 1.11. Maybe if someone create the appropriate packages for Xorg 1.10 in AUR, then we could add back some info, but until it's misleading I think. --[[User:City-busz|City-busz]] 23:32, 3 November 2011 (EDT)<br />
:::nvidia-96xx and nvidia-71xx are in the AUR, you can't use pacman to install them. -- [[User:Karol|Karol]] 00:03, 4 November 2011 (EDT)<br />
::::You can't install these packages from AUR, because they requires Xorg 1.10/1.7, which is not available in official repos, nor in AUR. Once NVidia make them compatible with Xorg 1.11, then someone should add them back to the official repos. Another option is to someone create xorg-server-1.10, xf86-input-evdev-1.10 etc. packages to support these drivers. --[[User:City-busz|City-busz]] 01:31, 4 November 2011 (EDT)<br />
:::::You can use [[Downgrading_Packages#ARM|ARM]] or some other mirror that holds old packages and still use nvidia-173xx and older drivers. My question is, why did you put {{ic|# pacman -S nvidia-96xx nvidia-96xx-utils}} instead of "install {{AUR|nvidia-96xx-all}} and {{AUR|nvidia-96xx-utils}} from the [[AUR]]."??<br />
:::::The latter still works with out of date packages while the former does not, because I'm not aware of any repo that has nvidia-96xx. -- [[User:Karol|Karol]] 09:06, 4 November 2011 (EDT)<br />
::::::It's possible, but it requires further explanation (maybe in a new section). Simply install nvidia-* packages from AUR is not work currently. --[[User:City-busz|City-busz]] 10:20, 4 November 2011 (EDT)<br />
:::::::And installing them with pacman does work? I still don't get this change. -- [[User:Karol|Karol]] 11:16, 4 November 2011 (EDT)<br />
<br />
The following section was commented in the article. I am moving it here instead:<br />
<br />
These drivers are not compatible with the latest Xorg release in the official repo.<br />
<br />
:Whereas users with older cards should install (GeForce 5 FX series cards [NV30-NV38]):<br />
:{{bc|# pacman -S nvidia-173xx nvidia-173xx-utils}}<br />
<br />
:or (GeForce2 MX, GeForce3 and GeForce4 series cards [NV11 and NV17-NV28]):<br />
:{{bc|# pacman -S nvidia-96xx nvidia-96xx-utils}}<br />
<br />
:or (Riva TNT, TNT2, GeForce and GeForce2 series cards [NV03-NV10 and NV15-NV16]):<br />
:{{bc|# pacman -S nvidia-71xx nvidia-71xx-utils}}<br />
<br />
-- [[User:Pointone|pointone]] 10:31, 4 April 2012 (EDT)<br />
<br />
== custom kernel ==<br />
<br />
The package changed for kernel 3.0 and the instructions no longer work. Please fix this. [[User:Z.T.|Z.T.]] 09:14, 23 November 2011 (EST)<br />
<br />
== '/dev/nvidia0' Input/Output error... suggested fixes ==<br />
<br />
Can anyone verify that the BIOS related suggestions work and are not coincidentally set (either automatically when changing the IRQ or turning off ACPI) while troubleshooting? I have found little information that confirms any of the suggestions would work. The file permissions thing seems to be completely unfounded and never works (as noted in the article) that I could find. It would probably be a good idea if we cleaned out items that have not been verified to work. For my setup I was having this error and none of the items in the wiki nor the many file permission search results worked. -- [[User:Clickthem|click, them so hard]] 19:16, 4 March 2012 (EST)<br />
:I've added an Accuracy template, please next time add it yourself so that discussions like this are more visible. -- [[User:Kynikos|Kynikos]] 05:40, 6 March 2012 (EST)<br />
<br />
== Rewrite ==<br />
I think the "Installing" section is a little ambiguous and could use a bit of rewording. Because the steps are numbered, and little indication is given otherwise, it is implied that you need both the packages named like nvidia-173xx, ''and'' the regular nvidia packages. I don't actually have my nvidia drivers working properly, so maybe I'm misinterpreting this, but if I'm right in assuming that you need ''either'' the specifically named drivers like nvidia-173xx ''or'' the plain ol' nvidia drivers, step 2 needs to be reworded. I would suggest displaying two separate [code] blocks, one with # pacman -S nvidia-173xx nvidia-173xx-utils, and the one that's there now. Then make it explicitly clear that you need to do one or the other, not both. --[[User:Sotanaht|Sotanaht]] 18:45, 17 May 2012 (EDT)<br />
<br />
Oh, I forgot that the nvidia-173xx drivers were not in the official repos. Scratch the part about including the command for installing that. I still think it's important to make clear that people using the nvidia-173xx drivers ''do not need'' the regular nvidia drivers. Also make it clear that people using the regular nvidia drivers do not need any nvidia-XXXxx drivers. --[[User:Sotanaht|Sotanaht]] 18:49, 17 May 2012 (EDT)<br />
<br />
:Well, I've never had to use the old Nvidia drivers, but the note says that the old modules don't support Xorg 1.11 (Arch provides 1.12 now). Unless the situation has changed, those drivers are useless unless you also write instructions on how to safely downgrade Xorg. Please correct me if I'm wrong. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 11:27, 19 May 2012 (UTC)<br />
<br />
== Bad performance, e.g. slow repaints when switching tabs in Chrome suggestion broke emerald/compiz ==<br />
Firefox performs quite poorly for me, so I tried this suggestion and it ended up breaking my WM. All new window borders changed to solid white and would not move around. Can someone else confirm? If so there should probably be a note or amendment to the suggestion. [[User:Biltong|Biltong]] ([[User talk:Biltong|talk]])<br />
<br />
== Run a test ==<br />
<br />
There is confusing paragraph saying ''You can run a test to see if the Xorg server will function correctly without a configuration file.''. IMHO, it should be clarified what kind of test the author has in mind, an exact command would be helpful. Currently, this suggestion is simply confusing, especially to less experienced users. --[[User:Mloskot|Mloskot]] ([[User talk:Mloskot|talk]]) 19:52, 26 November 2012 (UTC)</div>Davvilhttps://wiki.archlinux.org/index.php?title=Talk:NVIDIA&diff=240720Talk:NVIDIA2012-12-17T12:33:03Z<p>Davvil: /* (U)EFI support */</p>
<hr />
<div>== (U)EFI support ==<br />
<br />
I was told in [https://bbs.archlinux.org/viewtopic.php?id=136807 this thread] that the proprietary nvidia drivers do not work with EFI (by what appeared to be a senior community member), and repeated attempts to install the drivers on a UEFI system have met with little success. As a result, I am placing the warning back. Apologies if this isn't in keeping with wiki etiquette!<br />
<br />
--[[User:Rsmb|Rsmb]] ([[User talk:Rsmb|talk]]) 02:59, 13 December 2012 (UTC)<br />
<br />
:I had success using the nvidia driver on a efi system by adding 'nomodeset' to the kernel parameters. This prevents kms from loading, which causes a blank screen and is probably the source of the problems most users are seeing. X afterwards works just fine. I was able to play Doom 3 with a high fps rate :)<br />
[[User:Davvil|Davvil]] ([[User talk:Davvil|talk]]) 10:59, 17 December 2012 (UTC)<br />
<br />
== XRandR support ==<br />
As far as i understand it the recent drivers support XRANDR, which is probably much better than Xinerama/Twinview. Should we remove the Xinerame/Twinview instructions alltogether and just mention to use the standard XRandR methods for multiscreen setups?<br />
<br />
== NVoption Online ==<br />
<br />
NVoption Online Version - great tool to make tv-out easy and fast <br />
<br />
[I'm using gmplayer with gl and twinview]<br />
[http://www.sorgonet.com/linux/nv-online/]http://www.sorgonet.com/linux/nv-online/<br />
<br />
== Reword ==<br />
Maybe someone can put this in better words:<br />
Logging out, or switching to a different terminal using ctrl+alt+F<2-9> consistently resulted in a black screen, and killing Xorg with ctrl-alt-backspace resulted in a terminal screen with only the top line visible. It turned out that a 'vga=773' added to kernel line was the cause of this. After removing that the problem was solved. Probably something to do with KMS? B.t.w. I have only used x with 'startx', so possibly specific for that way of starting X.<br />
[[User:rwd|rwd]]<br />
<br />
:Was it with this driver or nouveau? The proprietary drivers don't have KMS. [[User:Thestinger|thestinger]] 17:42, 13 December 2010 (EST)<br />
<br />
This was with the proprietary driver. I originally had put vga=.. because it made gave the bootup screen a higher resolution, and because the beginners guide mentions it (https://wiki.archlinux.org/index.php/Beginners%27_Guide#GRUB). Apart from leaving out the vga option, I discovered that setting it to the native resolution as explained on https://wiki.archlinux.org/index.php/GRUB#Framebuffer_resolution fixes the black screens as well. Maybe a warning for using vga= option with with proprietary drivers would be useful.[[User:rwd|rwd]]<br />
<br />
Well the thing is that vga= is meant for the proprietary drivers only - open source drivers already set the native resolution without a vga command. It can be removed from the beginners' guide though, since it breaks open source drivers, and if the card doesn't support the vga command, it breaks the closed source ones too. [[User:Thestinger|thestinger]] 20:13, 13 December 2010 (EST)<br />
<br />
== Nvidia 173xx ==<br />
The nvidia-173xx package no longer exists (29 Oct 2011). <br />
<br />
Has it been replaced by nvidia-173xx-all? If so, this package hasn't been updated since Feb 2011.<br />
<br />
Will it need to be updated to be able to use the latest xorg 1.11? <br />
<br />
In the meantime, please include instructions for which xorg related packages pacman should ignore.<br />
:[http://mailman.archlinux.org/pipermail/arch-dev-public/2011-October/021764.html] -- [[User:Karol|Karol]] 21:14, 28 October 2011 (EDT)<br />
::I commented out the info about older drivers, since they're not compatible with Xorg 1.11. Maybe if someone create the appropriate packages for Xorg 1.10 in AUR, then we could add back some info, but until it's misleading I think. --[[User:City-busz|City-busz]] 23:32, 3 November 2011 (EDT)<br />
:::nvidia-96xx and nvidia-71xx are in the AUR, you can't use pacman to install them. -- [[User:Karol|Karol]] 00:03, 4 November 2011 (EDT)<br />
::::You can't install these packages from AUR, because they requires Xorg 1.10/1.7, which is not available in official repos, nor in AUR. Once NVidia make them compatible with Xorg 1.11, then someone should add them back to the official repos. Another option is to someone create xorg-server-1.10, xf86-input-evdev-1.10 etc. packages to support these drivers. --[[User:City-busz|City-busz]] 01:31, 4 November 2011 (EDT)<br />
:::::You can use [[Downgrading_Packages#ARM|ARM]] or some other mirror that holds old packages and still use nvidia-173xx and older drivers. My question is, why did you put {{ic|# pacman -S nvidia-96xx nvidia-96xx-utils}} instead of "install {{AUR|nvidia-96xx-all}} and {{AUR|nvidia-96xx-utils}} from the [[AUR]]."??<br />
:::::The latter still works with out of date packages while the former does not, because I'm not aware of any repo that has nvidia-96xx. -- [[User:Karol|Karol]] 09:06, 4 November 2011 (EDT)<br />
::::::It's possible, but it requires further explanation (maybe in a new section). Simply install nvidia-* packages from AUR is not work currently. --[[User:City-busz|City-busz]] 10:20, 4 November 2011 (EDT)<br />
:::::::And installing them with pacman does work? I still don't get this change. -- [[User:Karol|Karol]] 11:16, 4 November 2011 (EDT)<br />
<br />
The following section was commented in the article. I am moving it here instead:<br />
<br />
These drivers are not compatible with the latest Xorg release in the official repo.<br />
<br />
:Whereas users with older cards should install (GeForce 5 FX series cards [NV30-NV38]):<br />
:{{bc|# pacman -S nvidia-173xx nvidia-173xx-utils}}<br />
<br />
:or (GeForce2 MX, GeForce3 and GeForce4 series cards [NV11 and NV17-NV28]):<br />
:{{bc|# pacman -S nvidia-96xx nvidia-96xx-utils}}<br />
<br />
:or (Riva TNT, TNT2, GeForce and GeForce2 series cards [NV03-NV10 and NV15-NV16]):<br />
:{{bc|# pacman -S nvidia-71xx nvidia-71xx-utils}}<br />
<br />
-- [[User:Pointone|pointone]] 10:31, 4 April 2012 (EDT)<br />
<br />
== custom kernel ==<br />
<br />
The package changed for kernel 3.0 and the instructions no longer work. Please fix this. [[User:Z.T.|Z.T.]] 09:14, 23 November 2011 (EST)<br />
<br />
== '/dev/nvidia0' Input/Output error... suggested fixes ==<br />
<br />
Can anyone verify that the BIOS related suggestions work and are not coincidentally set (either automatically when changing the IRQ or turning off ACPI) while troubleshooting? I have found little information that confirms any of the suggestions would work. The file permissions thing seems to be completely unfounded and never works (as noted in the article) that I could find. It would probably be a good idea if we cleaned out items that have not been verified to work. For my setup I was having this error and none of the items in the wiki nor the many file permission search results worked. -- [[User:Clickthem|click, them so hard]] 19:16, 4 March 2012 (EST)<br />
:I've added an Accuracy template, please next time add it yourself so that discussions like this are more visible. -- [[User:Kynikos|Kynikos]] 05:40, 6 March 2012 (EST)<br />
<br />
== Rewrite ==<br />
I think the "Installing" section is a little ambiguous and could use a bit of rewording. Because the steps are numbered, and little indication is given otherwise, it is implied that you need both the packages named like nvidia-173xx, ''and'' the regular nvidia packages. I don't actually have my nvidia drivers working properly, so maybe I'm misinterpreting this, but if I'm right in assuming that you need ''either'' the specifically named drivers like nvidia-173xx ''or'' the plain ol' nvidia drivers, step 2 needs to be reworded. I would suggest displaying two separate [code] blocks, one with # pacman -S nvidia-173xx nvidia-173xx-utils, and the one that's there now. Then make it explicitly clear that you need to do one or the other, not both. --[[User:Sotanaht|Sotanaht]] 18:45, 17 May 2012 (EDT)<br />
<br />
Oh, I forgot that the nvidia-173xx drivers were not in the official repos. Scratch the part about including the command for installing that. I still think it's important to make clear that people using the nvidia-173xx drivers ''do not need'' the regular nvidia drivers. Also make it clear that people using the regular nvidia drivers do not need any nvidia-XXXxx drivers. --[[User:Sotanaht|Sotanaht]] 18:49, 17 May 2012 (EDT)<br />
<br />
:Well, I've never had to use the old Nvidia drivers, but the note says that the old modules don't support Xorg 1.11 (Arch provides 1.12 now). Unless the situation has changed, those drivers are useless unless you also write instructions on how to safely downgrade Xorg. Please correct me if I'm wrong. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 11:27, 19 May 2012 (UTC)<br />
<br />
== Bad performance, e.g. slow repaints when switching tabs in Chrome suggestion broke emerald/compiz ==<br />
Firefox performs quite poorly for me, so I tried this suggestion and it ended up breaking my WM. All new window borders changed to solid white and would not move around. Can someone else confirm? If so there should probably be a note or amendment to the suggestion. [[User:Biltong|Biltong]] ([[User talk:Biltong|talk]])<br />
<br />
== Run a test ==<br />
<br />
There is confusing paragraph saying ''You can run a test to see if the Xorg server will function correctly without a configuration file.''. IMHO, it should be clarified what kind of test the author has in mind, an exact command would be helpful. Currently, this suggestion is simply confusing, especially to less experienced users. --[[User:Mloskot|Mloskot]] ([[User talk:Mloskot|talk]]) 19:52, 26 November 2012 (UTC)</div>Davvilhttps://wiki.archlinux.org/index.php?title=Talk:NVIDIA&diff=240703Talk:NVIDIA2012-12-17T10:59:36Z<p>Davvil: /* (U)EFI support */</p>
<hr />
<div>== (U)EFI support ==<br />
<br />
I was told in [https://bbs.archlinux.org/viewtopic.php?id=136807 this thread] that the proprietary nvidia drivers do not work with EFI (by what appeared to be a senior community member), and repeated attempts to install the drivers on a UEFI system have met with little success. As a result, I am placing the warning back. Apologies if this isn't in keeping with wiki etiquette!<br />
<br />
--[[User:Rsmb|Rsmb]] ([[User talk:Rsmb|talk]]) 02:59, 13 December 2012 (UTC)<br />
<br />
:I had success using the nvidia driver on a efi system by adding 'nomodeset' to the kernel parameters. This prevents kms from loading, which causes a blank screen and is probably the source of the problems most users are seeing. X afterwards works just fine. I was able to play Doom 3 with a high fps rate :)<br />
[[User:Davvil|Davvil]] ([[User talk:Davvil|talk]]) 10:59, 17 December 2012 (UTC) davvil<br />
<br />
== XRandR support ==<br />
As far as i understand it the recent drivers support XRANDR, which is probably much better than Xinerama/Twinview. Should we remove the Xinerame/Twinview instructions alltogether and just mention to use the standard XRandR methods for multiscreen setups?<br />
<br />
== NVoption Online ==<br />
<br />
NVoption Online Version - great tool to make tv-out easy and fast <br />
<br />
[I'm using gmplayer with gl and twinview]<br />
[http://www.sorgonet.com/linux/nv-online/]http://www.sorgonet.com/linux/nv-online/<br />
<br />
== Reword ==<br />
Maybe someone can put this in better words:<br />
Logging out, or switching to a different terminal using ctrl+alt+F<2-9> consistently resulted in a black screen, and killing Xorg with ctrl-alt-backspace resulted in a terminal screen with only the top line visible. It turned out that a 'vga=773' added to kernel line was the cause of this. After removing that the problem was solved. Probably something to do with KMS? B.t.w. I have only used x with 'startx', so possibly specific for that way of starting X.<br />
[[User:rwd|rwd]]<br />
<br />
:Was it with this driver or nouveau? The proprietary drivers don't have KMS. [[User:Thestinger|thestinger]] 17:42, 13 December 2010 (EST)<br />
<br />
This was with the proprietary driver. I originally had put vga=.. because it made gave the bootup screen a higher resolution, and because the beginners guide mentions it (https://wiki.archlinux.org/index.php/Beginners%27_Guide#GRUB). Apart from leaving out the vga option, I discovered that setting it to the native resolution as explained on https://wiki.archlinux.org/index.php/GRUB#Framebuffer_resolution fixes the black screens as well. Maybe a warning for using vga= option with with proprietary drivers would be useful.[[User:rwd|rwd]]<br />
<br />
Well the thing is that vga= is meant for the proprietary drivers only - open source drivers already set the native resolution without a vga command. It can be removed from the beginners' guide though, since it breaks open source drivers, and if the card doesn't support the vga command, it breaks the closed source ones too. [[User:Thestinger|thestinger]] 20:13, 13 December 2010 (EST)<br />
<br />
== Nvidia 173xx ==<br />
The nvidia-173xx package no longer exists (29 Oct 2011). <br />
<br />
Has it been replaced by nvidia-173xx-all? If so, this package hasn't been updated since Feb 2011.<br />
<br />
Will it need to be updated to be able to use the latest xorg 1.11? <br />
<br />
In the meantime, please include instructions for which xorg related packages pacman should ignore.<br />
:[http://mailman.archlinux.org/pipermail/arch-dev-public/2011-October/021764.html] -- [[User:Karol|Karol]] 21:14, 28 October 2011 (EDT)<br />
::I commented out the info about older drivers, since they're not compatible with Xorg 1.11. Maybe if someone create the appropriate packages for Xorg 1.10 in AUR, then we could add back some info, but until it's misleading I think. --[[User:City-busz|City-busz]] 23:32, 3 November 2011 (EDT)<br />
:::nvidia-96xx and nvidia-71xx are in the AUR, you can't use pacman to install them. -- [[User:Karol|Karol]] 00:03, 4 November 2011 (EDT)<br />
::::You can't install these packages from AUR, because they requires Xorg 1.10/1.7, which is not available in official repos, nor in AUR. Once NVidia make them compatible with Xorg 1.11, then someone should add them back to the official repos. Another option is to someone create xorg-server-1.10, xf86-input-evdev-1.10 etc. packages to support these drivers. --[[User:City-busz|City-busz]] 01:31, 4 November 2011 (EDT)<br />
:::::You can use [[Downgrading_Packages#ARM|ARM]] or some other mirror that holds old packages and still use nvidia-173xx and older drivers. My question is, why did you put {{ic|# pacman -S nvidia-96xx nvidia-96xx-utils}} instead of "install {{AUR|nvidia-96xx-all}} and {{AUR|nvidia-96xx-utils}} from the [[AUR]]."??<br />
:::::The latter still works with out of date packages while the former does not, because I'm not aware of any repo that has nvidia-96xx. -- [[User:Karol|Karol]] 09:06, 4 November 2011 (EDT)<br />
::::::It's possible, but it requires further explanation (maybe in a new section). Simply install nvidia-* packages from AUR is not work currently. --[[User:City-busz|City-busz]] 10:20, 4 November 2011 (EDT)<br />
:::::::And installing them with pacman does work? I still don't get this change. -- [[User:Karol|Karol]] 11:16, 4 November 2011 (EDT)<br />
<br />
The following section was commented in the article. I am moving it here instead:<br />
<br />
These drivers are not compatible with the latest Xorg release in the official repo.<br />
<br />
:Whereas users with older cards should install (GeForce 5 FX series cards [NV30-NV38]):<br />
:{{bc|# pacman -S nvidia-173xx nvidia-173xx-utils}}<br />
<br />
:or (GeForce2 MX, GeForce3 and GeForce4 series cards [NV11 and NV17-NV28]):<br />
:{{bc|# pacman -S nvidia-96xx nvidia-96xx-utils}}<br />
<br />
:or (Riva TNT, TNT2, GeForce and GeForce2 series cards [NV03-NV10 and NV15-NV16]):<br />
:{{bc|# pacman -S nvidia-71xx nvidia-71xx-utils}}<br />
<br />
-- [[User:Pointone|pointone]] 10:31, 4 April 2012 (EDT)<br />
<br />
== custom kernel ==<br />
<br />
The package changed for kernel 3.0 and the instructions no longer work. Please fix this. [[User:Z.T.|Z.T.]] 09:14, 23 November 2011 (EST)<br />
<br />
== '/dev/nvidia0' Input/Output error... suggested fixes ==<br />
<br />
Can anyone verify that the BIOS related suggestions work and are not coincidentally set (either automatically when changing the IRQ or turning off ACPI) while troubleshooting? I have found little information that confirms any of the suggestions would work. The file permissions thing seems to be completely unfounded and never works (as noted in the article) that I could find. It would probably be a good idea if we cleaned out items that have not been verified to work. For my setup I was having this error and none of the items in the wiki nor the many file permission search results worked. -- [[User:Clickthem|click, them so hard]] 19:16, 4 March 2012 (EST)<br />
:I've added an Accuracy template, please next time add it yourself so that discussions like this are more visible. -- [[User:Kynikos|Kynikos]] 05:40, 6 March 2012 (EST)<br />
<br />
== Rewrite ==<br />
I think the "Installing" section is a little ambiguous and could use a bit of rewording. Because the steps are numbered, and little indication is given otherwise, it is implied that you need both the packages named like nvidia-173xx, ''and'' the regular nvidia packages. I don't actually have my nvidia drivers working properly, so maybe I'm misinterpreting this, but if I'm right in assuming that you need ''either'' the specifically named drivers like nvidia-173xx ''or'' the plain ol' nvidia drivers, step 2 needs to be reworded. I would suggest displaying two separate [code] blocks, one with # pacman -S nvidia-173xx nvidia-173xx-utils, and the one that's there now. Then make it explicitly clear that you need to do one or the other, not both. --[[User:Sotanaht|Sotanaht]] 18:45, 17 May 2012 (EDT)<br />
<br />
Oh, I forgot that the nvidia-173xx drivers were not in the official repos. Scratch the part about including the command for installing that. I still think it's important to make clear that people using the nvidia-173xx drivers ''do not need'' the regular nvidia drivers. Also make it clear that people using the regular nvidia drivers do not need any nvidia-XXXxx drivers. --[[User:Sotanaht|Sotanaht]] 18:49, 17 May 2012 (EDT)<br />
<br />
:Well, I've never had to use the old Nvidia drivers, but the note says that the old modules don't support Xorg 1.11 (Arch provides 1.12 now). Unless the situation has changed, those drivers are useless unless you also write instructions on how to safely downgrade Xorg. Please correct me if I'm wrong. -- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 11:27, 19 May 2012 (UTC)<br />
<br />
== Bad performance, e.g. slow repaints when switching tabs in Chrome suggestion broke emerald/compiz ==<br />
Firefox performs quite poorly for me, so I tried this suggestion and it ended up breaking my WM. All new window borders changed to solid white and would not move around. Can someone else confirm? If so there should probably be a note or amendment to the suggestion. [[User:Biltong|Biltong]] ([[User talk:Biltong|talk]])<br />
<br />
== Run a test ==<br />
<br />
There is confusing paragraph saying ''You can run a test to see if the Xorg server will function correctly without a configuration file.''. IMHO, it should be clarified what kind of test the author has in mind, an exact command would be helpful. Currently, this suggestion is simply confusing, especially to less experienced users. --[[User:Mloskot|Mloskot]] ([[User talk:Mloskot|talk]]) 19:52, 26 November 2012 (UTC)</div>Davvilhttps://wiki.archlinux.org/index.php?title=Lenovo_ThinkPad_T400&diff=105713Lenovo ThinkPad T4002010-05-05T16:53:33Z<p>Davvil: /* Switchable Graphics */</p>
<hr />
<div>[[Category:Lenovo (English)]]<br />
=System Sepcification=<br />
*CPU : Intel® Core™2 Duo Processor T9400 (6M Cache, 2.53 GHz, 1066 MHz FSB)<br />
*Memory : 3GB PC3-8500 DDR3<br />
*WiFi : Intel WiFi Link 5300<br />
*Hard-Drive : 160GB, 7200rpm<br />
*Optical Drive : DVD Recordable<br />
*Integrated Graphics : Intel 4500MHD<br />
*Discrete Graphics : AMD M82XT Hybrid 256 MB (ATI Mobility Radeon HD 3470)<br />
*Screen : 14.1" WXGA+ TFT with LED Backlit<br />
*Gigabit Ethernet, Modem<br />
*Express Card & PC Card Slots<br />
*Integrated Bluetooth PAN<br />
*No camera<br />
*No fingerprint reader<br />
*No Intel Turbo Memory<br />
<br />
=Network=<br />
==Ethernet Card==<br />
The kernel module to get the network card to work is '''e1000e'''. I had no problem getting it to work.<br />
<br />
==Wireless==<br />
Lenovo offers different options in paragraph wireless hardware:<br />
<br />
===Intel chipset===<br />
*Wifi link 5100 and 5300<br />
<br />
The drivers are included in the 2.6.27 kernel. However, it's important to make sure that you have the correct firmware. I installed the iwlwifi-5000-ucode. See [[Wireless#iwl3945.2C_iwl4965_and_iwl5000-series|this section]] for more details.<br />
<br />
===Realtek chipset===<br />
<br />
*Rtl8192SE<br />
11b/g/n Wireless Lan Mini-PCI Express Adapter II<br />
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8172 (rev 10)<br />
<br />
See http://www.thinkwiki.org/wiki/ThinkPad_11b/g/n_Wireless_LAN_Mini-PCI_Express_Adapter_II for more details.<br />
<br />
'''Realtek r8192se_pci Driver'''<br />
<br />
Finally came the expected driver (alpha? beta?), I think it's premature but it works perfectly.<br />
<br />
Here the driver (r8192se_pci):<br />
32 bits: http://launchpadlibrarian.net/33927923/rtl8192se_linux_2.6.0010.1012.2009.tar.gz<br />
64 bits: http://launchpadlibrarian.net/34090326/rtl8192se_linux_2.6.0010.1012.2009_64bit.tar.gz<br />
<br />
untar; make; make install; reboot and enjoy it<br />
<br />
I test it with:<br />
*netcfg<br />
*standar commands:<br />
ifconfig wlan0 up<br />
iwlist wlan0 scan<br />
iwconfig wlan0 essid MySsid<br />
wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf<br />
dhcpcd wlan0<br />
<br />
There is also a package available in the AUR: http://aur.archlinux.org/packages.php?ID=34281<br />
<br />
'''Ndiswrapper option:'''<br />
If you have a 32-bit version of arch, it should be possible to get it working with ndiswrapper: <br />
<br />
*Download this .exe file: http://www.station-drivers.com/telechargement/realtek/wifi/rtl-8191se_1080.7.0520%28www.station-drivers.com%29.exe<br />
*Install the '''extra/p7zip''' package and use the included utility '''7z''' to extract the contents of the .exe:<br />
<br />
7z x rtl-8191se_1080.7.0520(www.station-drivers.com).exe<br />
<br />
*Copy the files '''net8192se.inf''' and '''rtl8192se.sys''' from the '''91_92_SE_Driver/Win2K''' directory to a location of your choosing.<br />
*Proceed with the [[Wireless_Setup#ndiswrapper|normal ndiswrapper installation procedure]].<br />
<br />
Unfortunately, if you are running a 64-bit version of arch then it seems you are '''out of luck''' currently; the WinX64 drivers included in the above package do not work.<br />
<br />
For more information, see http://ubuntuforums.org/showthread.php?t=1182457 and http://forums.lenovo.com/lnv/board/message?board.id=Special_Interest_Linux&message.id=1196 .<br />
<br />
==Modem==<br />
There is a module "hsfmodem" provided by http://www.linuxant.com/.<br />
<br />
=Graphics/Xorg Configuration=<br />
Note that it's possible to switch the graphics adapter by only restarting X, but It's quite useless since you can't power up/down a graphic-card without rebooting. So it's either both graphic-card on at all times, or do the switching in the BIOS.<br />
<br />
So please press the ThinkVantag-button» during boot up and enable either the Integrated or the Discrete graphics cards in your BIOS's "Config->Display" menu.<br />
<br />
Note that I enabled the '''testing''' repository, which gave me access to :<br />
*xorg-server version 1.5.3<br />
*xf86-video-intel version 2.4.3<br />
*xf86-video-ati version 6.10.0<br />
*xf86-video-radeonhd 1.2.4<br />
*catalyst version 8.12<br />
<br />
==Integrated Graphics==<br />
After installing [[Xorg#Installing_Xorg|xorg]], I installed the [[Intel|xf86-video-intel drivers]]. As root, I then ran '''X -configure'''. The generated xorg.conf worked fine. I did apply the [[Intel#2D|2D]] and [[Intel#3D|3D]] optimization, and performances in compositing window managers (like compiz or kwin) seem to have increased. I have not made any scientific measurements though.<br />
<br />
'''Note : '''Some people have encountered problems with 3D on 2.6.28 kernels and xf86-video-intel version 2.4.3. <br />
<br />
The following xorg.conf file was tested on a T400 with an integrated card with the 1280x800 resolution provided by the default Intel Integrated Intel GMA 4500MHD (I included the Input devices for reference)<br />
<br />
Section "InputDevice"<br />
Identifier "Generic Keyboard"<br />
Driver "kbd"<br />
Option "XkbRules" "xorg"<br />
Option "XkbModel" "pc104"<br />
Option "XkbLayout" "us"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Configured Mouse"<br />
Driver "mouse"<br />
Option "SendCoreEvents"<br />
Option "Device" "/dev/input/mice"<br />
Option "Emulate3Buttons" "true"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Synaptics Touchpad"<br />
Driver "synaptics"<br />
Option "CorePointer"<br />
Option "Device" "/dev/psaux"<br />
Option "Protocol" "auto-dev"<br />
Option "Emulate3Buttons" "true"<br />
Option "HorizScrollDelta" "0"<br />
Option "Emulate3Buttons" "true"<br />
Option "LeftEdge" "1700"<br />
Option "RightEdge" "5300"<br />
Option "TopEdge" "1700"<br />
Option "BottomEdge" "4200"<br />
Option "FingerLow" "25"<br />
Option "FingerHigh" "30"<br />
Option "MaxTapTime" "180"<br />
Option "MaxTapMove" "220"<br />
Option "VertScrollDelta" "100"<br />
Option "MinSpeed" "0.06"<br />
Option "MaxSpeed" "0.10"<br />
Option "AccelFactor" "0.0010"<br />
#Option "SHMConfig" "1"<br />
Option "UpDownScrolling" "1"<br />
Option "CircularScrolling" "0"<br />
Option "LockedDrags" "0"<br />
Option "TouchpadOff" "0"<br />
#Option "Repeater" "/dev/ps2mouse"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "Configured Monitor"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "HDMI-1"<br />
Option "Ignore" "True"<br />
EndSection<br />
<br />
Section "Monitor"<br />
Identifier "HDMI-2"<br />
Option "Ignore" "True"<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Configured Video Device"<br />
Driver "intel"<br />
Option "monitor-HDMI-1" "HDMI-1"<br />
Option "monitor-HDMI-2" "HDMI-2"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Default Screen"<br />
Monitor "Configured Monitor"<br />
Device "Configured Video Device"<br />
DefaultDepth 24<br />
SubSection "Display"<br />
Modes "1280x800"<br />
EndSubSection<br />
EndSection<br />
<br />
Section "ServerLayout"<br />
Identifier "Default Layout"<br />
Screen "Default Screen"<br />
InputDevice "Synaptics Touchpad"<br />
InputDevice "Configured Mouse"<br />
EndSection<br />
<br />
'''NB''' Installing extra/libdrm and forcing discrete graphics in the bios fixed hanging problems when X quit.<br />
<br />
Here is a minimal xorg.conf in which the Virtual screen size is specified, so that one enables support for dual monitor.<br />
<br />
Section "Monitor"<br />
Identifier "Configured Monitor"<br />
EndSection<br />
<br />
Section "Screen"<br />
Identifier "Default Screen"<br />
Monitor "Configured Monitor"<br />
Device "Configured Video Device"<br />
SubSection "Display"<br />
Virtual 2464 1500<br />
EndSubSection<br />
EndSection<br />
<br />
Section "Device"<br />
Identifier "Configured Video Device"<br />
EndSection<br />
<br />
==Discrete Graphics==<br />
All 3 ATI drivers worked. That is both [[ATI#Open-Source_ATI_Drivers|open-source drivers]] (<code>xf86-video-ati</code> and <code>xf86-video-radeonhd</code>) and [[ATI#ATI_Catalyst_proprietary_driver|fglrx]] (the <code>catalyst</code> proprietary drivers).<br />
<br />
I could not get the <code>xf86-video-radeonhd</code> drivers to detect my external monitor, but <code>xf86-video-ati</code> worked fine. Remember to remove <code>catalyst</code> and <code>catalyst-utils</code> and reboot before using an [[ATI#Open-Source_ATI_Drivers|open source ATI drivers]]. ATI uses its own OpenGL library in its proprietary drivers, which is included in <code>catalyst-utils</code> and conflicts with libgl. As it did with the integrated graphics, running '''X -configure''' generated a working xorg.conf.<br />
<br />
To get the [[ATI#ATI_Catalyst_proprietary_driver|catalyst drivers]] working, you do have to [[ATI#Configuration|configure]] your xorg.conf properly. I used '''aticonfig --initial''' to generate a working xorg.conf. I did encounter a problem that I have not been able to solve yet : resizing a window in a compositing window manager takes 1-2 seconds. This makes the drivers pretty much unusable.<br />
<br />
==Switchable Graphics==<br />
Is currently not supported by the kernel. You can enable switchable-graphics in the BIOS and make Xorg do the switching, but then both cards will always use power and generate lots of heat. See the [http://en.gentoo-wiki.com/wiki/Lenovo_ThinkPad_T400#Getting_both_to_work| gentoo-wiki] to keep up too date on the issue.<br />
<br />
You can also try David Arlile's patch to power off the unused card. See http://airlied.livejournal.com/71434.html and http://linux-hybrid-graphics.blogspot.com/.<br />
<br />
==Hotplugging==<br />
If you want to enable [[Xorg_input_hotplugging|hotplugging]] you probably don't need a xorg.conf. But if you are using xf86-video-ati you might temporarely need to disable [[KMS]], by adding "nomodeset" to your kernel-line in "/boot/grub/menu.lst". If you don't want to disable KMS you can probably install some radeon firmware, see the [[Ati#Kernel_mode-setting_.28KMS.29|Ati-wiki]].<br />
<br />
Since all the mouse/keyboard configuration is taken care of by [[HAL]] you will need some config files in "/etc/hal/fdi/policy/"<br />
For instant "mouse-wheel.fdi" to enable TrackPoint-scrolling:<br />
<br />
<match key="info.product" string="TPPS/2 IBM TrackPoint"><br />
<merge key="input.x11_options.EmulateWheel" type="string">true</merge><br />
<merge key="input.x11_options.EmulateWheelButton" type="string">2</merge><br />
<merge key="input.x11_options.YAxisMapping" type="string">4 5</merge><br />
<merge key="input.x11_options.XAxisMapping" type="string">6 7</merge><br />
<merge key="input.x11_options.Emulate3Buttons" type="string">true</merge><br />
<merge key="input.x11_options.EmulateWheelTimeout" type="string">200</merge><br />
</match><br />
<br />
More information in the TrackPoint can be found here: http://www.thinkwiki.org/wiki/How_to_configure_the_TrackPoint.<br />
The Keyboard layout is controlled by "/etc/hal/fdi/policy/10-keymap.fdi" Modify it like [[Xorg_input_hotplugging#Modifying_hal_configuration|this]] to<br />
change your layout. If you have any more questions on hotplugging (like how to enable [[Touchpad_Synaptics#Configuration_via_HAL_policies_.28hotplugging_enabled.29|tapping]]), take a look at it's [[Xorg_input_hotplugging|wiki page]].<br />
<br />
== Synaptic, UltraNav ==<br />
If you want to be able to use horizontal and vertical scroll with your touchpad add this lines to your xorg.conf<br />
<br />
Section "Module"<br />
......<br />
Load "synaptics"<br />
EndSection<br />
<br />
Section "InputDevice"<br />
Identifier "Touchpad"<br />
Driver "synaptics"<br />
Option "AlwaysCore"<br />
Option "Device" "/dev/input/mouse1"<br />
Option "Protocol" "auto-dev"<br />
Option "SendCoreEvents" "true"<br />
Option "LeftEdge" "1632"<br />
Option "RightEdge" "5312"<br />
Option "TopEdge" "1575"<br />
Option "BottomEdge" "4281"<br />
Option "FingerLow" "25"<br />
Option "FingerHigh" "30"<br />
Option "MaxTapTime" "180"<br />
Option "MaxTapMove" "220"<br />
Option "VertScrollDelta" "100"<br />
Option "MinSpeed" "0.06"<br />
Option "MaxSpeed" "0.12"<br />
Option "AccelFactor" "0.0010"<br />
Option "VertEdgeScroll" "on"<br />
Option "HorizEdgeScroll" "on"<br />
# Option HorizScrollDelta""0" <br />
Option "SHMConfig" "on"<br />
EndSection <br />
<br />
for trakpoint with third button paste & scroll add this few lines to xorg.conf too<br />
<br />
Section "InputDevice"<br />
Identifier "Trackpoint"<br />
Driver "mouse"<br />
Option "CorePointer"<br />
Option "Device" "/dev/input/mice"<br />
Option "Protocol" "Auto"<br />
Option "Emulate3Buttons"<br />
Option "Emulate3Timeout" "50"<br />
Option "EmulateWheel" "on"<br />
Option "EmulateWheelTimeout" "200" # adjust third button paste timeout. <br />
Option "EmulateWheelButton" "2"<br />
Option "YAxisMapping" "4 5"<br />
Option "XAxisMapping" "6 7"<br />
Option "YAxisMapping" "4 5"<br />
EndSection<br />
<br />
finally update your layout<br />
<br />
Section "ServerLayout"<br />
InputDevice "Trackpoint" "CorePointer"<br />
InputDevice "Touchpad"<br />
InputDevice "Keyboard0" "CoreKeyboard"<br />
EndSection<br />
<br />
<br />
<br />
<br />
=Audio=<br />
Once you have [[ALSA]] installed, fire up alsamixer and make sure that sound is not muted. You might also want to press the Volume Up or Volume Down button. It seems than the Mute button mutes everything, even system beeps. Pressing the Volume Up or Volume Down button can unmute, but not pressing the Mute button again.<br />
<br />
Here's the modules I have loaded that are relevant to sound :<br />
$ lsmod | grep snd<br />
snd_seq_oss 35584 0<br />
snd_seq_midi_event 9344 1 snd_seq_oss<br />
snd_seq 58336 4 snd_seq_oss,snd_seq_midi_event<br />
snd_seq_device 9364 2 snd_seq_oss,snd_seq<br />
snd_hda_intel 474672 2<br />
snd_hwdep 10632 1 snd_hda_intel<br />
snd_pcm_oss 45568 0<br />
snd_pcm 82440 2 snd_hda_intel,snd_pcm_oss<br />
snd_timer 24720 2 snd_seq,snd_pcm<br />
snd_page_alloc 10640 2 snd_hda_intel,snd_pcm<br />
snd_mixer_oss 18944 1 snd_pcm_oss<br />
snd 64840 16 snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_hwdep,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss<br />
soundcore 9632 1 snd<br />
<br />
Additionally, there is a patch for the audio driver for conexant's chipsets provided by http://www.linuxant.com which can be downloaded at http://www.linuxant.com/alsa-driver/.<br />
<br />
<br />
=Multimedia Keys=<br />
The screen brightness controls and the flashlight work without any tweaking. The other keys can be mapped using [[Extra_Keyboard_Keys#Using_xev|xev]] and xbindkeys. By following [http://wiki.linuxquestions.org/wiki/Configuring_keyboards#Enabling_Keyboard_Multimedia_Keys this guide] you should be able to get everything working, but here's summary :<br />
<br />
*First, open a terminal and type <code>xev</code>. This starts the "Event tester".<br />
*Place your cursor on the "Event tester" window.<br />
*When you press a key on your keyboard or move your mouse, it should get displayed in a terminal. For instance, this is what shows up if you press Fn+F2 <br />
KeyRelease event, serial 33, synthetic NO, window 0x3000001,<br />
root 0x86, subw 0x0, time 5537544, (76,110), root:(81,938),<br />
state 0x0, '''keycode 146''' (keysym 0x0, '''NoSymbol'''), same_screen YES,<br />
XLookupString gives 0 bytes:<br />
XFilterEvent returns: False<br />
It basically says that '''keycode 146''' is not bound ('''NoSymbol''').<br />
Here are all the keycodes of all multimedia buttons:<br />
<br />
Volume Down : keycode 174<br />
Volume Up : keycode 176<br />
Fn+F2 : keycode 146<br />
Fn+F3 : keycode 241<br />
Fn+F4 : keycode 223<br />
Fn+F5 : Not responding to events ??<br />
Fn+F7 : keycode 214<br />
Fn+F8 : keycode 249<br />
Fn+F9 : keycode 207<br />
Fn+F12 : keycode 165<br />
Fn+Up : keycode 164<br />
Fn+Down : keycode 162<br />
Fn+Left : keycode 144<br />
Fn+Right : keycode 153<br />
Fn+Home : keycode 212<br />
Fn+End : keycode 101<br />
*Type <code>xmodmap -pke > ~/.Xmodmap</code> in a terminal. This creates a file, <code>.Xmodmap</code>, containing your current keyboard mapping.<br />
*Now open the file with a text editor and find the keycodes you're interested in. You can map any keycode with a symbol from [http://wiki.linuxquestions.org/wiki/XF86_keyboard_symbols this list].<br />
*To get your new <code>.Xmodmap</code> loaded when you start X, just add <code>xmodmap ~/.Xmodmap</code> to your .xinitrc.<br />
*To get your new <code>.Xmodmap</code> loaded immediately, type <code>xmodmap ~/.Xmodmap</code> in a terminal.<br />
<br />
You can now assign functions to your newly bound keys by using [[Extra_Keyboard_Keys_in_Xorg#Using_your_Desktop_Environment_tools|facilities provided by your window desktop environment]] or by using <code>xbindkeys</code>.<br />
<br />
To use <code>xbindkeys</code>,<br />
*Start by installing it<br />
pacman -S xbindkeys<br />
*Then add <code>xbindkeys &</code> to your .xinitrc.<br />
*And finally, in your home directory, create a file called <code>.xbindkeysrc.scm</code> with content that would look something like <br />
(xbindkey '("XF86Standby") "sudo killall dhcpcd && sudo pm-suspend")<br />
(xbindkey '("XF86AudioRaiseVolume") "amixer set Master 2dB+ unmute")<br />
(xbindkey '("XF86AudioLowerVolume") "amixer set Master 2dB- unmute")<br />
<br />
==Mute==<br />
<br />
To get the mute button to work, it is necessary to pass the string <code>acpi_osi="Linux"</code> to the kernel as a boot parameter. In GRUB2, add it to the "linux" line. See [http://www.thinkwiki.org/wiki/Mute_button here] for more details.<br />
<br />
With the 3.1 bios, it seems that the mute button works normally (set it up the same as the volume buttons with, for instance, "amixer set Master toggle").<br />
<br />
=ACPI=<br />
To enable the fan speed control, it's necessary to load the thinkpad_acpi with option fan_control=1. After the thinkpad_acpi module is loaded with this option, you can monitor and adjust the fan speed via /proc/acpi/ibm/fan.<br />
<br />
=SUSPEND-RESUME=<br />
People have been having issues with suspend resume with the current intel xf86-video-intel 2.4.3.1 drivers in combination with the 4500mhd chipset. This is apparently an issue with concurrency as adding the following script (with mod 755) in /etc/pm/sleep.d fixes things. to some extent...<br />
<br />
#!/bin/sh<br />
# Workaround for concurrency bug in xserver-xorg-video-intel 2:2.4.1-1ubuntu10.<br />
# Save this as /etc/pm/sleep.d/00CPU <br />
<br />
. "/usr/lib/pm-utils/functions"<br />
<br />
case "$1" in<br />
hibernate|suspend)<br />
for i in /sys/devices/system/cpu/cpu*/online ; do<br />
echo 0 >$i<br />
done<br />
;;<br />
thaw|resume) <br />
sleep 10 # run with one core for 10 secs<br />
for i in /sys/devices/system/cpu/cpu*/online ; do<br />
echo 1 >$i<br />
done<br />
;;<br />
*)<br />
;;<br />
esac<br />
<br />
<br />
From http://ubuntu-virginia.ubuntuforums.org/showpost.php?p=6105510&postcount=12 petri4 on the ubuntu forums.<br />
<br />
=7-1 Media Card Reader=<br />
Tested for SD cards only. Works after loading modules sdhci and ricoh_mmc in /etc/rc.conf. Sometimes there are problems initializing the SD card (check dmesg) after inserting it. In such cases, try re-inserting it again. <br />
<br />
TODO<br />
<br />
=Bluetooth=<br />
The procedure described in the [[Bluetooth]] section of the Arch Wiki worked perfectly for me.</div>Davvilhttps://wiki.archlinux.org/index.php?title=Splashy&diff=102689Splashy2010-04-10T14:25:47Z<p>Davvil: </p>
<hr />
<div>[[Category: Boot process (English)]]<br />
[[Category: Eye candy (English)]]<br />
{{i18n|Splashy}}<br />
<br />
==Introduction==<br />
[http://splashy.alioth.debian.org Splashy] is a userspace implementation of a splash screen for Linux systems. It provides a graphical environment during system boot using the Linux framebuffer layer via [http://www.directfb.org directfb].<br />
<br />
Please see [http://bbs.archlinux.org/viewtopic.php?id=48978 this post] on the Arch Linux forum for a repo you can add with working splashy packages. Splashy in AUR also works (see below).<br />
<br />
==Installation==<br />
<br />
# Grab the [http://aur.archlinux.org/packages.php?ID=27916 splashy-full package] in AUR, build it via makepkg (or whatever makepkg wrapper you like) and install via Pacman.<br />
<br />
==Configuration==<br />
=== Uvesafb Framebuffer (Preferred) ===<br />
It is recommended to use [[Uvesafb]] if your hardware supports it (unless your hardware also supports KMS, see below). This allows you to use the exact native resolution of your monitor. It also allows you a widescreen boot splash.<br />
<br />
# Follow the instructions on the [[Uvesafb]] page to install and configure.<br />
# Add <code>quiet splash</code> to your kernel command line in ''/boot/grub/menu.lst''. <br>Example: <code>kernel (hd0,6)/vmlinuz26 root=/dev/sda6 ro '''quiet splash'''</code><br />
<br />
=== Default Framebuffer ===<br />
You can also use the default kernel framebuffer if your hardware does not support Uvesafb. <br />
<br />
# [http://en.wikipedia.org/wiki/VESA_BIOS_Extensions#Linux_video_mode_numbers Find the kernel framebuffer mode number closest as possible to your monitor].<br />
# Add <code>quiet vga='''mode_number''' splash</code> to your kernel command line in ''/boot/grub/menu.lst''. <br>Example: <code>kernel (hd0,6)/vmlinuz26 root=/dev/sda6 ro '''quiet vga=791 splash'''</code><br />
<br />
=== Kernel Mode Setting ===<br />
If you have a chipset that supports kernel mode setting ([[KMS]]), this is preferable to using Uvesafb. Note that when KMS is enabled you should always disable Uvesafb, as well as any "vga=" and "video=" options in your bootloader as these will conflict with the native resolution enabled by KMS. You still have to add the <code>quiet splash</code> options in your grub config file.<br />
<br />
=== Other Configuration Files ===<br />
====/etc/rc.conf====<br />
Add <code>SPLASH="splashy"</code> in ''/etc/[[rc.conf]]'', e.g.:<br />
SPLASH="splashy"<br />
====/etc/mkinitcpio.conf====<br />
'''Remember to rebuild the initramfs image whenever Splashy's config changes.''' (E.g. Splashy theme was changed.)<br />
#Add '''<code>splashy</code>''' at the '''end''' of the HOOKS in ''/etc/mkinitcpio.conf'', e.g.:<pre>HOOKS="base udev autodetect ide sata filesystems ... splashy"</pre><br />
#Rebuild initramfs image<pre># mkinitcpio -p <kernel name></pre>E.g.<pre># mkinitcpio -p kernel26</pre><br />
<br />
===Upgrading===<br />
Don't forget to rebuild the initramfs image after upgrading Splashy.<br />
<br />
===Themes===<br />
You can install [http://aur.archlinux.org/packages.php?ID=19626 splashy-themes] in AUR to get a nice splashy theme. After installing, look at the available themes like so:<br />
$ ls /usr/share/splashy/themes<br />
The folder name is the theme name. Now edit '''/etc/splashy/config.xml''' and change the theme name to the want you want. Note that themes ending in 43 are 4:3 aspect ratio, and the others are widescreen. Try "archlinux-simplyblack" as a good first theme, e.g.:<br />
<current_theme>archlinux-simplyblack</current_theme><br />
After you set your theme (and any time you change your theme) you will need to again run<br />
# mkinitcpio -p kernel26<br />
<br />
==Known Problems==<br />
#Splashy doesn't terminate or automatically switch to verbose mode if an error occurs or when an init script fails. '''No longer true with splashy-full package.'''<br />
#Something goes "terribly wrong" when a forced filesystem check commences while Splashy is running. For some unknown reason (yet), the system reboots itself after the fsck.<br />
#X can show artefacts on the top of the screen, if splashy is activated during bootup. <br />
#Adding <code><autoverboseonerror>no</autoverboseonerror></code> in /etc/splashy/config.xml may solve problems when booting in battery mode on laptops<br />
#If you get a lot of directfb errors, change "1.2" to "1.4" in /lib/initcpio/install/splashy<br />
#If you get an error with libjpeg, try installing libjpeg6<br />
#If you use gsplashy and a theme does not appear on the list, make sure that config.xml in the folder of the theme is named theme.xml instead<br />
#If you get a libz.so.1 error, try either symlinking /lib/libz.so.1 to /usr/lib/libz.so.1 or changing /lib/libz.so.1 to /usr/libz.so.1 in /lib/initcpio/install/splashy<br />
<br />
==Links==<br />
* http://splashy.alioth.debian.org<br />
* http://www.directfb.org</div>Davvilhttps://wiki.archlinux.org/index.php?title=Laptop&diff=61245Laptop2009-02-11T09:26:50Z<p>Davvil: /* Hard drive spin down problem */</p>
<hr />
<div>[[Category:HOWTOs (English)]]<br />
[[Category:Laptops (English)]]<br />
<br />
= Setting Up For Laptops =<br />
This page should contain links to pages needed for configuring a laptop for the best experience. Setting up a laptop is in many was the same as setting up a desktop. However, there are a few key differences. When setting up a laptop with Arch Linux, the following points should be taken into consideration:<br />
<br />
* Power consumption (how do I make the battery last the longest per charge?). Which leads to power management:<br />
* Hard drive spindown. After how many minutes of inactivity should the hard drive be spun down?<br />
* Screen shut off. After how many minutes of inactivity should the screen be shut off? (Not just blanked with a screensaver but completely shut off).<br />
* CPU frequency scaling. How should the CPU's frequency change depending on load to minimize power usage?<br />
* Suspend and hibernate. How do I get suspend and hibernate to work with my laptop?<br />
* Screen brightness. How do I manage screen brightness in Linux?<br />
<br />
* Network and wireless. How do I get my wireless working?<br />
* Media buttons. How do I configure the function of those buttons on my laptop?<br />
* Touchpad. How do I configure the sensativity, acceleration, button function and scroll borders for my Synaptics or Alps touchpad?<br />
<br />
All of these points are important to take into consideration when getting a laptop set up the way you like. Fortunately, Arch Linux provides all the tools and programs necessary to take complete control of your laptop. These programs and utilities are highlighted below, with appropriate tips tutorials.<br />
<br />
<br />
Note: the following links may be useful:<br />
<br />
* [http://www.linux-on-laptops.com/ http://www.linux-on-laptops.com/]<br />
* [http://www.linlap.com/ http://www.linlap.com/]<br />
<br />
= Power Management =<br />
Power management is very important for anyone who wishes to make good use of their battery capacity. The following tools and programs help to increase battery life and keep your laptop cool and quiet.<br />
<br />
== Cpufrequtils ==<br />
<br />
[[Cpufrequtils]] provides CPU Frequency Scaling, a technology used primarily by notebooks which enables the OS to scale the CPU speed up or down, depending on the current system load and/or power scheme. For quick and easy installation and setup, please view the [[CPU Frequency Scaling]] article.<br />
<br />
== Pm-utils ==<br />
[[Pm-utils]] provides a suspend and powerstate setting framework. Pm-utils should be used with cpufrequtils to provide a complete power management solution.<br />
<br />
== Networkmanager ==<br />
[[Networkmanager]] provides automatic network detection and configuration for the system. Another clean and fast network manager is [[wicd]]. Wicd should be used when one does not want to install too many gnome dependencies or wants simplicity of setup and ease of use.<br />
<br />
Note: [[Networkmanager]] is being phased out in favor of [[network_profiles]]<br />
<br />
== Lapsus ==<br />
[[Asus_G1#The_Lapsus_daemon_.26_KDE_applet|Lapsus]] is a set of programs providing easy access to many features of various laptops. It currently supports most features provided by asus-laptop kernel module from ACPI4Asus project, such as additional LEDs, hotkeys, backlight control etc. It also has support for some IBM laptops features provided by IBM ThinkPad ACPI Extras Driver and NVRAM device.<br />
<br />
<br />
== Install powertop ==<br />
This handy util from Intel will tell you what hardware/processes are using the most power on your system, and provides instructions on how to stop/remove power-wasting services. Works great for mobile Intel CPUs; provides the current CPU state and suggestions for power saving. Also works on AMD systems, but does not provide as much information about the CPU state. Install with:<br />
<br />
# pacman -S powertop<br />
<br />
== Laptop mode tools ==<br />
Install laptop-mode-tools with:<br />
<br />
# pacman -S laptop-mode-tools<br />
<br />
* The configuration file can be found in /etc/laptop-mode/laptop-mode.conf.<br />
* Be sure to add ''laptop-mode'' to the DAEMONS line in /etc/rc.conf<br />
<br />
See [http://bbs.archlinux.org/viewtopic.php?id=39258 this thread] for more information.<br />
<br />
== Suggestions for saving power ==<br />
=== Disk-related tweaks ===<br />
Disable file access time: every time you access (read) a file the filesystem writes an access time to the file metadata. You can disable this on individual files by using the chattr command, or you can enable it on an entire disk by setting the ''noatime'' option in your fstab, as follows:<br />
<br />
/dev/sda1 / ext3 defaults,noatime 1 2<br />
<br />
[http://www.faqs.org/docs/securing/chap6sec73.html Source]<br />
<br />
<br />
To allow the CD/DVD rom to spin down after a while, run the following: <br />
<br />
/usr/bin/hal-disable-polling --device /dev/scd0<br />
<br />
=== Other tweaks ===<br />
These are some generic suggestions that will work with most laptops.<br />
<br />
Add the following to ''/etc/modprobe.d/options'':<br />
<br />
options usbcore autosuspend=1<br />
<br />
<br />
Add the following to ''/etc/sysctl.conf''<br />
<br />
vm.dirty_writeback_centisecs=1500<br />
vm.laptop_mode=5<br />
<br />
<br />
Add the following to ''/etc/rc.local'' (and make sure it gets executed at boot time)<br />
<br />
/usr/sbin/iwpriv eth1 set_power 5<br />
<br />
Source: [http://www.nervous.it/2007/11/linux-dell-xps-m1330/ here]<br />
<br />
=== Hard drive spin down problem ===<br />
Documented [https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/59695 here]<br />
<br />
To prevent your laptop hard drive from spinning down too often (result of too aggressive APM defaults) do the following:<br />
<br />
Add the following to ''/etc/rc.local''<br />
<br />
hdparm -B 255 /dev/sdX ''where X is your hard drive device''<br />
<br />
<br />
<br />
Add the following to ''/etc/pm/sleep.d/50-hdparm_pm''<br />
<br />
#!/bin/sh<br />
<br />
if [ -n "$1" ] && ([ "$1" = "resume" ] || [ "$1" = "thaw" ]); then<br />
hdparm -B 255 /dev/your-hard-drive > /dev/null<br />
fi<br />
<br />
and run "chmod +x /etc/pm/sleep.d/50-hdparm_pm" to make sure it resets after suspend.<br />
<br />
Now APM should be turned off for your hard drive.<br />
<br />
For some laptops, the option -S to hdparm can also be relevant (sets the spindown time for the drive). Note that all these options can also be configured using the laptop-mode tool.<br />
<br />
= Touchpad =<br />
To get your touchpad working properly, see the [[Touchpad Synaptics]] page.<br />
<br />
= Special Buttons =<br />
To configure any special keys or buttons on your laptop, please refer to the following article: [http://www.linux.com/feature/118179 Customize your laptop keyboard with X and KDE]. Note that KDE is not required.<br />
<br />
= HDAPS =<br />
To protect your hard drive from shocks, consider installing some form of [[HDAPS|Hard Disk Active Protection System]].</div>Davvil