On Friday 29 January 2010 18:04:22 you wrote:
> On 01/28/2010 07:09 PM, Marko Vojinovic wrote:
> > On Thursday 28 January 2010 18:36:43 Jim wrote:
> >> Noveau is not changing the xorg.conf, it is hal or something like that
> >> in Fedora.
> > Nothing should be changing xorg.conf just out of the blue. And the
> > settings in there should be honored by X.
> > Couple of stupid questions: are you sure that you have saved your changes
> > to the file after editing? Are you sure you are editing the right file?
> > Maybe it is a ownership/permissions problem. Post the output of
> > ls -l /etc/X11/xorg.conf
> > Also, maybe there is some error in the file itself, and X falls back to
> > autoconfiguring. Post the output of
> > cat /etc/X11/xorg.conf
> > Maybe for some odd reason the xorg.conf file is not being used at all.
> > Post the output of
> > cat /var/log/Xorg.0.log
> > With all this info I guess we'll have a better idea on what is going on.
> $ ls -l /etc/X11/xorg.conf
> -rw-r--r--. 1 root root 1451 2010-01-28 12:22 /etc/X11/xorg.conf
Ok, the permissions look fine.
> [tom@gray ~]$ cat /etc/X11/xorg.conf
> # nvidia-xconfig: X configuration file generated by nvidia-xconfig
> # nvidia-xconfig: version 1.0 (mockbuild@) Sun Nov 22 21:04:19 EST 2009
> Section "ServerLayout"
> Identifier "Layout0"
> Screen 0 "Screen0"
> InputDevice "Keyboard0" "CoreKeyboard"
> InputDevice "Mouse0" "CorePointer"
> Section "Files"
> FontPath "/usr/share/fonts/default/Type1"
> Section "InputDevice"
> # generated from default
> Identifier "Mouse0"
> Driver "mouse"
> Option "Protocol" "auto"
> Option "Device" "/dev/input/mice"
> Option "Emulate3Buttons" "no"
> Option "ZAxisMapping" "4 5"
> Section "InputDevice"
> # generated from data in "/etc/sysconfig/keyboard"
> Identifier "Keyboard0"
> Driver "kbd"
> Option "XkbLayout" "us"
> Option "XkbModel" "pc105"
> Section "Monitor"
> Identifier "Monitor0"
> VendorName "Unknown"
> ModelName "Unknown"
> HorizSync 28.0 - 33.0
> VertRefresh 43.0 - 72.0
> Option "DPMS"
> Section "Device"
> Identifier "Device0"
> Driver "nvidia"
> VendorName "NVIDIA Corporation"
> Section "Screen"
> Identifier "Screen0"
> Device "Device0"
> Monitor "Monitor0"
> DefaultDepth 24
> SubSection "Display"
> Depth 24
Ok, in this place here you need to add the line:
Add it in precisely the above place (inside the "Display" subsection), save
the xorg.conf file and do a "cat /etc/X11/xorg.conf" again to make sure that
the added line is now really there.
Given that only root has permissions to write to the file, only a very limited
number of programs will be able to rewrite it. This will reduce the number of
possible suspects. :-)
Next, log out and log back in, *without* rebooting the computer. This will
restart only X and nothing else, and now the resolution should be 1024x768.
See below how to check. If it isn't, do a "cat /etc/X11/xorg.conf" to verify
that the "Modes" line is still there.
If this went well, do a full reboot and see if the new resolution sticks.
Check the "cat /etc..." thing again to see if anything has mangled the
Report your findings back to us. :-)
> [tom@gray ~]$ cat /var/log/Xorg.0.log
> X.Org X Server 1.7.4
> Release Date: 2010-01-08
> X Protocol Version 11, Revision 0
> Build Operating System: x86-01 2.6.18-164.6.1.el5
> Current Operating System: Linux gray 22.214.171.124-174.2.3.fc12.x86_64 #1
[I'm snipping irrelevant parts throughout the log]
> (==) Using config file: "/etc/X11/xorg.conf"
This is ok, X actually uses xorg.conf.
> (==) Jan 28 16:58:57 NVIDIA(0): No modes were requested; the default
> mode "nvidia-auto-select"
> (==) Jan 28 16:58:57 NVIDIA(0): will be used as the requested mode.
There was no "Modes" line in xorg.conf, so nvidia driver used the default
auto-select option to choose your resolution.
> (II) Jan 28 16:58:57 NVIDIA(0): Virtual screen size determined to be
> 1600 x 900
> (--) Jan 28 16:58:57 NVIDIA(0): DPI set to (92, 91); computed from
> "UseEdidDpi" X config
> (--) Jan 28 16:58:57 NVIDIA(0): option
> (II) Jan 28 16:59:57 NVIDIA(0): Setting mode "1152x864"
This is the resolution it chose, using the EDID data sent from the monitor. I
guess it picked the largest resolution available.
So, once you edit the /etc/X11/xorg.conf, add the "Modes" line, log out/in,
you can check the actual resolution used by (a) visual inspection of the
monitor, and (b) by reading the log and checking for the info like the above.
Somewhere you should be able to find the line that contains something like
NVIDIA(0): Setting mode "1024x768"
If you find this in the log, then it definitely works as expected.
Do a "cat /var/log/Xorg.0.log" again, and read it through, or post it again
When plugged in it knows what it is,
but cannot find a driver for it.
Any advice, Google sends me to Windows sites.
I just installed fedora 12 as an update of a fedore 11 system.
This morning I saw 683 updates proposed for my system.
I clicked on "Install Updates" button and had, some seconds after this
Error Type: <class 'yum.Errors.RepoError'>
Error Value: Error getting repository data for installed, repository not
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3125, in
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3122, in main
File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 710,
File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 657,
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1948, in
signed = self._is_package_repo_signed(pkg)
File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1437, in
repo = self.yumbase.repos.getRepo(pkg.repoid)
File : /usr/lib/python2.6/site-packages/yum/repos.py, line 121, in getRepo
'Error getting repository data for $s, repository not found' $ (repoid)
Cordialement / Best Regards
Géophysique Spatiale et Planétaire
Institut de Physique du Globe de Paris
4, avenue de Neptune - 94107 SAINT MAUR cedex - FRANCE
Tel +33 (0)1 45 11 41 49
Fax +33 (0)1 45 11 41 10
Here is a bit of a different question I think. I have an F-11 box I'm
setting up to let people access it for some file shares using samba. In
order to control the access I created a user for each person I want to allow
access. Each user was created without their own group or an account, file in
"/home", since none of them will be allowed to do anything except access
file shares. The above users were then assigned to several groups I created.
The problem is every one of the users I created shows up as an entry in the
main login screen on the locally attached display console. Is there anyway
to only display logins for those uses that have an account they can access
while not showing the others? Those that have an account will be accessing
their account by loging in, by attaching remotely, using Xrdp which by the
way is a slick way of handling multiple users on the machine at the same
time and letting them use their desktop.
Leland C. Scott
The sound on my Thinkpad T43 (model 1871-12G) sometimes works,
and sometimes does not work.
I think this has something to do with Suspend to Disk.
However, I'm not really asking about this,
but rather: Is there a simple way of testing if sound is working?
I'm running Fedora-12/KDE, and looked at System Settings=>
Look and Feel=>Notifications ,
but did not really understand how one is supposed to use this.
Is there a simple command-line test for sound?
Shouldn't there be a test somewhere in KMix
since there seem to be a billion choices there?
The only test I have found is to put in a CD and run Amarok,
but I am sure there is something simpler than that?
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
Hey all, I'm still new to Fedora in that I've never seen a new major
version of Firefox in this time.
Will Firefox 3.6 be pushed out as a system upgrade, or will Fedora
stick to the stable 3.5 series?
if so, any idea of eta? Would it be similiar to 3.5 series or take
longer cause it's a major upgrade?
Thanks a bunch.
When trying to do an /etc/init.d/proftpd start on my Fedora 11 box, I am
getting a return of Failed.
I can find no service which might be interfering and no log file
anywhere showing me an error.