https://wiki.archlinux.org/api.php?action=feedcontributions&user=Scr&feedformat=atomArchWiki - User contributions [en]2024-03-28T12:20:19ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:NVIDIA&diff=252980Talk:NVIDIA2013-04-05T10:45:18Z<p>Scr: </p>
<hr />
<div>== NVidia Quadro NVS Series (Notebooks) work with nvidia package ==<br />
<br />
All cards up from Quadro NVS 130M the NVidia Quadro NVS Series (Notebooks) work with the NVidia package (Linux Display Driver - x86 310.44 2.4.20, the nvidia package in pacman, https://www.archlinux.org/packages/?name=nvidia , as confirmed by the nvidia website: http://www.nvidia.de/Download/Find.aspx?lang=en&QNF=1 )<br />
<br />
The 130M was issued in 2007, the 140M was build into the popular ThinkPad T61, so there will be quite a lot of people who have one of those.<br />
<br />
All other cards in this series (110M and 120M) work with the nvidia-304xx package from the official repositories.<br />
<br />
== (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>Scrhttps://wiki.archlinux.org/index.php?title=Talk:Network_configuration/Wireless&diff=252977Talk:Network configuration/Wireless2013-04-05T10:26:49Z<p>Scr: </p>
<hr />
<div>== iwlist wlan0 scanning syntax ==<br />
<br />
In section "https://wiki.archlinux.org/index.php/Wireless_Setup#Access_point_discovery" is the shell command "iwlist wlan0 scanning" mentioned. "iwlist scan" will do in most cases, and is even without system dependent interface names. (Also, its at least 4 characters shorter, depending on system configuration, and in this respect more according to the arch way than the current version.)<br />
<br />
== wpa_supplicant.conf ==<br />
<br />
I installed Arch Linux in December 2012 and my wpa_supplicant.conf file is at /etc/wpa_supplicant/wpa_supplicant.conf , so I would suggest updating this page to reflect that. [[User:DavidEGrayson|DavidEGrayson]] ([[User talk:DavidEGrayson|talk]]) 23:17, 16 December 2012 (UTC)<br />
:That is intentional in order not to change the original .conf which is really good reference documentation in itself. Explanation for it you find in the wpa_supplicant wiki here. The idea is you create a new /etc/wpa_supplicant.conf and work with that. Since all wpa_supplicant calls mentioned in the wiki address the /etc version, its fine in my view. --[[User:Indigo|Indigo]] ([[User talk:Indigo|talk]]) 18:27, 17 December 2012 (UTC)<br />
<br />
==Mention modprobe -l==<br />
Does anybody else besides me think that it would be helpful to mention modprobe -l to get a list of loaded modules/drivers and that ath9k is already included in the kernel at the beginning of ''First steps'' or ''Drivers and Firmware'' section? In my case (I have a Thinkpad x61) I didn't have to install any additional drivers, so I could proceed immediately to Manual setup and everything worked perfectly.<br />
<br>--[[User:Bhobbit|Bhobbit]] 01:03, 7 June 2009 (EDT)<br />
<br />
== Overall article readability (notes and split) ==<br />
There is no doubt this article is very rich, but I find it a bit messy overall.<br />
At first sight, the newcomer may think managing wireless is a real odyssey, whereas it may be 2 simple steps for most users.<br />
* More than 50% of the article is dedicated to specific drivers installation. Perhaps it would be worth moving the whole section to a dedicated page, leaving only generic install guidelines here.<br />
* I've found 21 ''Note'' templates. Too much imho, it makes different sections and code lines harder to distinguish, and thus diminishes article's overall readability. Some of them definitely do not deserve a template, they should be written as is.<br />
<br />
Still I won't say there is no doubt these 2 changes would make the article really better. So feel free to discuss!<br />
<br />
-- [[User:Ambrevar|Ambrevar]] ([[User talk:Ambrevar|talk]]) 10:27, 6 July 2012 (UTC)<br />
<br />
== Auto-connect if dropped or changed location Wicd ==<br />
<br />
I tested this with wicd and this didn't work (with my raspberry pi and an ASUS USB-N10 adaptor). Once the connection was dropped the device didn't even search for other networks (the light at the adaptor didn't blink).<br />
<br />
I now tried again with netcfg and that works like a charm, so it has nothing to do with my hardware. Are there others who are experiencing the same problem?<br />
<br>-- [[User:Warddr|Warddr]] ([[User talk:Warddr|talk]]) 15:17, 22 August 2012 (UTC)</div>Scr