- Discuss - lists.centos.org

PostgreSQL 8.3.0 rpm packages for RHEL5/CentOS5
by James B. Byrne 22 Feb '08

22 Feb '08

PostgreSQL 8.3.0 was released on February 4, 2008. There are a number of valuable enhancements in this version including Heap Only Tuples and integration of full text search. It is also reputed to provide a performance increase of at least 5% over 8.2.6. As usual, RHEL compatible RPMS are available at postgresql.org. However, there is a new (to me at least) project at http://yum.pgsqlrpms.org/ which provides a YUM repository for recent updates (actually everything from 7.4 to 8.3) to PostgreSQL suitable for RHEL 4.5 and 5 and Fedora 7 and 8. They also provide a YUM configuration RPM for each distro as well. Those who, like me, choose to judiciously update packages in advance of the upstream vendor and wish to employ postgrsql 8.3 may find this a much more convenient method than manually upgrading and updating via RPM. Note that a pgdump of all existing databases before upgrading, removal of the tablespace in /var/lib/pgsql/data, performing an initdb following the software upgrade and finally a restore from the backup are still (and painfully) required to upgrade from versions older than 8.3.0 Note as well that some the preset configuration values in postgres.conf have changed, that some options have been removed and new ones added so that a diff between the former conf file and the new one followed by some manual editing is required to preserve local customizations. I caution against simply copying the old postgres.conf file over into the upgraded installation. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 1

connect to novell 6.5 server
by Hiep Nguyen 22 Feb '08

22 Feb '08

Hi all, we have a centos box that run web server, but we also have novell 6.5 server that i want to read/write files to. is there anyway i can map novell's hard drive to centos box? thanks, t. hiep

2 1

How to Disable PAM in Centos 5.1
by vincenzo romero 22 Feb '08

22 Feb '08

Hello all I would like to disable PAM authentication in my test server running Centos5.1. Currently I get an error that states: "Feb 22 02:01:31 localhost login: pam_securetty(login:auth): access denied: tty 'tty1' is not secure !" I would like to DISABLE the PAM authentication; am unable to get the answer after googl'ing for hours; if anyone is familiar on how to do this: please advise. I am quite new to the intricacies of this OS; please bear the naive questions. -- best, Vince

4 9

sleepy disk drives
by Aleksandar Milivojevic 22 Feb '08

22 Feb '08

Hi, I'm having a grief with Seagate FreeAgent Pro drive connected to CentOS 4 box via USB. The problem is that drive is factory configured to take a nap (spin down) after some 15-20 minutes of inactivity, and there doesn't seem to be a way to disable it. Since it's USB connected, hdparm can't be used on it. Getting the drive out of the case is not an option either, since it would probably void the warranty (and there's still 4.5 years of it left). There's eSATA connector on the drive too, but I don't have anything on the PC side to connect it to. There's also FireWire connector, but somebody at big red company decided users don't need FireWire (and I'd probably have same problem if the drive was connected via FireWire too). The problem with the drive spinning down is that Linux doesn't really like when that happens. It reports that drive is not responding, spits bunch of I/O errors for the device in the logs, and refuses any operation on the file system(s) that are on that drive. In contrast, Windows, Mac OS X and some other boxes I tried to connect the drive to have no problem with it (drive simply spins up when accessed). There was a patch in relatively recent Linux kernels that adds allow_restart option (accessible from /sys), which apparently should solve the problem for Linux (described here: http://www.nslu2-linux.org/wiki/FAQ/DealWithAutoSpinDownOnSeagateFreeAgent) When allow_restart is set to 1 (default is 0), Linux will do what all other operating systems do by default, spin up the drive on access. However, kernel included with CentOS 4 is not recent enough, and doesn't have that option. Anyhow, my question is (after probably describing things a bit too much), does the kernel included with CentOS 5 supports allow_restart? Could somebody (anybody) running CentOS 5 could check if either of these paths exists on his/her system: /sys/block/sda/device/allow_restart or /sys/class/scsi_disk/0:0:0:0/allow_restart If they do exist, I'll be probably upgrading my box to CentOS 5 pronto... If they don't, well, might still upgrade but it won't solve the problem I'm having... Thanks, Alex

3 2

Dovecot on CentOS5 - (login) returned error 127
by Tim Alberts 22 Feb '08

22 Feb '08

Running CentOS Linux 5 with sendmail-procmail putting email in /var/spool/mail. I'm running pop3 only with the servers configured to authenticate with ldap (which is configured and running OK). I do have this same configuration on an older FC6 box and it works fine. I'm thinking I just need to upgrade dovecot given all the nss_ldap problems it has had, but I hate not using RPM packages and CentOS does not have upgraded packages. Hardware is Dell PowerEdge 1900 (64bit) with 2G RAM. Hopefully I'm doing something stupid and there's an easy fix for the packages and configuration I have. I'm seeing the following in the /var/log/maillog when I run dovecot. When I log in via telnet, I get the connection, but it never responds when I enter a user. Feb 21 15:41:20 cartman dovecot: Dovecot v1.0.rc15 starting up Feb 21 15:41:21 cartman dovecot: Temporary failure in creating login processes, slowing down for now Feb 21 15:41:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:41:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:41:21 cartman dovecot: child 4445 (login) returned error 127 Feb 21 15:41:21 cartman dovecot: child 4446 (login) returned error 127 Feb 21 15:41:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:41:21 cartman dovecot: child 4447 (login) returned error 127 Feb 21 15:42:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:42:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:42:21 cartman dovecot: child 4465 (login) returned error 127 Feb 21 15:42:21 cartman dovecot: child 4466 (login) returned error 127 Feb 21 15:42:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:42:21 cartman dovecot: child 4467 (login) returned error 127 Feb 21 15:43:21 cartman dovecot: pop3-login: pop3-login: error while loading shared libraries: libsepol.so.1: failed to map segment from shared object: Cannot allocate memory Feb 21 15:43:21 cartman last message repeated 2 times Feb 21 15:43:21 cartman dovecot: child 4469 (login) returned error 127 Feb 21 15:43:21 cartman dovecot: child 4470 (login) returned error 127 Feb 21 15:43:21 cartman dovecot: child 4471 (login) returned error 127 Feb 21 15:43:59 cartman dovecot: Killed with signal 15 Dovecot details are as follows: *> dovecot --version* 1.0.rc15 *> dovecot -n* # /etc/dovecot.conf protocols: pop3 listen: * login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib64/dovecot/pop3 pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam args: dovecot userdb: driver: passwd args: blocking=yes

4 4

yum-proxy?
by Niki Kovacs 22 Feb '08

22 Feb '08

Hi, I've been using Debian for a few years, and there was one nifty little app that made installing and updating so much easier: apt-proxy. Most of the time, I'm taking care of small LANs with an average of five client PCs. But this is a very remote place in South France, so most villages only have 512 kbps DSL. One major update for openoffice.org-*, and I have to wait the whole day for updating each machine (unless I scp -r /var/cache/yum from machine to machine, but that's another story). I'm currently testing an "intermediate" solution: creating a local Yum repository. I have [base], which consists of all the 5.1 RPMS copied over from the DVD. Then [updates], which I'm currently rsyncing from a remote mirror. And I think I'll do something similar with [extra], which only leaves [rpmforge] (but I won't cache that :oD). Not a very satisfying solution, since for example I'm currently installing XFCE as only desktop environment, and I have nevertheless to download every GNOME- and KDE-related update. A message to the developers: yum-proxy would be a much-needed addition to Yum, in my humble opinion. I don't have the technical skills to develop such a thing, but maybe one of you has (Daniel, do you read this? :oD) I'm curious about your comments on this. Cheers, Niki

4 4

Centos Livecd
by Sergio Belkin 22 Feb '08

22 Feb '08

Hi, I'd want to know if the new Centos LiveCd is installable, not only via network, but in a Fedora-Live fashion too. Thanks in advance. -- -- Open Kairos http://www.openkairos.com Watch More TV http://sebelk.blogspot.com Sergio Belkin -

8 18

Is Gnome in CentOS 5 ready for nfsv4?
by Olaf Mueller 22 Feb '08

22 Feb '08

Hello, all my data are hosted by a server and exported with nfsv4. For example if a user logs in on a client, /home and /data are exported with nfsv4 and autofs. Now if the user delete some files, the trashcan under gnome doesn't change its status nor doesn't show the deleted files if opening the trashcan window. Also the user isn't able to copy or move files between the exported directories with nautilus, the error message is talking about "different file systems". Is this a gnome-vfs2 bug in gnome-2.16? regards Olaf

1 1

How to mount 'virtual' file systems /proc and /sys ??
by Robinson Tiemuqinke 21 Feb '08

21 Feb '08

Hello, I am setting chrooted environments with Centos/Fedora Core distros recently. packages are installed in the chrooted environment without problems. Then when it comes to /proc and /sys 'virtual'(not real hardware) file systems I got confused -- some documents say I should run 'mount -t proc none /proc; mount -t sysfs none /sys' to mount /proc and /sys, while some others say commands 'mount -t proc proc /proc; mount -t sysfs sysfs /sys' instead. I don't know what is the difference between the source device name 'none' against 'proc' and 'sysfs'. Any one can shed a light onto this? In fact, I tried command 'mount -t proc kidding /proc; mount -t sysfs kiddingAgain /sys' to successfully mounted /proc and /sys without explicit problems; access to /proc/* and /sys/* worked fine as well. Then what are the purposes of the sourceDevice field for 'virtual' file systems? Thanks. Please help. ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

3 2

dinner saturday evening during fosdem 2008
by Dries Verachtert 21 Feb '08

21 Feb '08

Hello, Next weekend it's FOSDEM 2008 and Dag and i would like to propose to have a dinner Saturday evening in Leuven like quite some people did last year. This year we'll try to have a reservation :-) People willing to discuss/work on rpmrepo/centos/rpmforge during a nice meal should let me know as soon as possible so i can make the reservation at the restaurant! Lot's of info: http://rpmrepo.org/driesverachtert/Fosdem2008Dinner kind regards, Dries

1 0

Major update and again no new repodata
by Robert Moskowitz 21 Feb '08

21 Feb '08

Yesterday I pulled down a major update to OpenOffice. But no updates to repodata. I waited a day to see if there was some reason for the lag (like more rpms needed to complete the set), but still today, no repodata to pull down (my rsync looks for more recent file dates). Help?

5 6

FW: Memory Problem
by Van Staden, Allan 21 Feb '08

21 Feb '08

I am sure this has been covered before, but I can find it in my archives. I loaded up a new server IBM x3650, 2x Intel dual core cpu's I installed additional RAM to take it up to 7 gigs according to http://www.centos.org/product.html#seven CentOS 5 x86 which I am using supports up to 16gigs of RAM. Once I boot up CentOS only see's about 3.2Gigs of Ram. I installed the kernel-PAE package and upgraded my kernel to 2.6.18-53.1.13.el5. Searching on the web the suggestions are that I done the above, as I have done to sort out my problem buy nothing seems to work. Any help would be much appreciated Allan To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to firstrandbankdisclaimer(a)fnb.co.za and we will send you a copy of the Disclaimer.

4 3

Samba problem after Up2date
by Dago Pacheco 21 Feb '08

21 Feb '08

--

4 13

BIND.named failed to start
by محمد التلاوي 21 Feb '08

21 Feb '08

hi guys i have: CentOS_5.1 Linux 2.6.24 #2 SMP Fri Feb 15 20:03:34 AST 2008 i686 i686 i386 GNU/Linux with: bind-utils-9.3.3-10.el5ypbind-1.19-8.el5bind-9.3.3-10.el5bind-chroot-9.3.3-10.el5bind-libs-9.3.3-10.el5 when i try to start named i get this : Locating /var/named/chroot/etc/named.conf//etc/named.conf failed: [FAILED]i allready tried to link and copy named.conf to /var/named/chroot/etc/ but i still get the same result does anybody know how to organize named files under my CentOS? thanks all in advance _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

5 6

C5 64-bit on Dell not seeing 1 GB link
by Scott Ehrlich 21 Feb '08

21 Feb '08

I've got a Dell Precision Workstation 490 with 64-bit Centos 5, fully updated, with an on-board Broadcom 57xx gigabit Ethernet controller, updated BIOS, 1 GB switch, and /var/log/messages and dmesg both claim the link is 100 Mb, not 1 GB. I tried setting eth0 to mtu 9000 but got an error in going so. What do I need to do to have the card see 1 gb? Thanks. Scott

6 5

ls : not UTF-8 compliant?
by Mufit Eribol 21 Feb '08

21 Feb '08

Sorry bugging you for this simple command. ls command displays question marks for the local characters (ones not included in 8859-1 space) in filenames. ie. [root@server aa]# touch çarp [root@server aa]# ls ??arp [root@server aa]# ls -b #for octal escapes \303\247arp [root@server aa]# However, ls|less, ls|more or vi <directory name> all display filename correctly. Also, the <tab> completes such filenames in the correct way. Even, logsave command for the ls output prints the right characters. So, I assume the filesystem keeps the filenames in UTF-8 encoding, but somehow ls can not show them properly. Any workaround or a replacement for ls? BTW The system is Centos 5.1 and locale shows the encoding as UTF-8. Thank you.

3 4

Yum not updating kernel
by Bob Taylor 20 Feb '08

20 Feb '08

I'm having the same problem as Valent Turkovic. I have the following /etc/yum.repos.d/CentOS-Base.repo (mind the line-wraps): [base] name=CentOS-$releasever - Base mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch= $basearch&repo=os #baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5 #released updates [updates] name=CentOS-$releasever - Updates #mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch= $basearch&repo=updates baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5 #packages used/produced in the build but not released [addons] name=CentOS-$releasever - Addons mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch= $basearch&repo=addons #baseurl=http://mirror.centos.org/centos/$releasever/addons/$basearch/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5 #additional packages that may be useful [extras] name=CentOS-$releasever - Extras mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch= $basearch&repo=extras #baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/ gpgcheck=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5 #additional packages that extend functionality of existing packages [centosplus] name=CentOS-$releasever - Plus mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch= $basearch&repo=centosplus #baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/ gpgcheck=1 enabled=1 gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5 I have missed any fixes for this since the suggestion to comment the mirrorlist line and uncomment the baseurl line (which doesn't work. Thanks in advance. -- Bob Taylor

6 30

Raid controller issue under CentOS 5.1
by Joseph L. Casale 20 Feb '08

20 Feb '08

I have an LSI 8888ELP with an external enclosure and two arrays in it. I needed some quick storage so I put two drives in some open slots and created a span. One drive failed, but I have seen multiple failures on this port so I suspected either a bad controller port/cable/backplane. I offlined the remaining good drive and removed them both, I reinserted them to see if the bad drive was bad and it would seem that made the system unhappy. I attempted to reboot at which point it hung partially through the reboot. I attached the messages log, can anyone shed some light on what happened? Thanks for any guidance! jlc

1 0

Re: [CentOS] Yum not updating kernel
by Bob Taylor 20 Feb '08

20 Feb '08

Hm. I just noticed http://mirror.centos.org/centos/5/updates/i386/RPMS/ kernel listings are i686.rpm. Could my problem be this is confusing yum as I use i386 and this is the i386 directory? Doesn't make sense since no one else seems to have this. Of course their are most likely few running Pentium II's. Searching for answers in the dark. Shouldn't yum update kernel work update just the kernel* rpms? -- Bob Taylor

2 2

Is there a fix for the "sqlite cache needs updating" error?
by J. Potter 20 Feb '08

20 Feb '08

I've been seeing the below message from yum whenever the repo has an update (CentOS 5): > /etc/cron.daily/yum.cron: > > ** Message: sqlite cache needs updating, reading in metadata Googling a bit, it looks like others have seen this happen as well. The solutions, when I've found them, have been along the lines of "send output to /dev/null" or "edit this file", but nothing that feels like the "right" fix. Is there a general solution to this? Or should we just sit tight for redhat bug #429689 to be fixed (5.2?). -Jeff

4 4

Re: [CentOS] nss_ldap failed to bind to LDAP server 127.0.0.1
by Ross S. W. Walker 20 Feb '08

20 Feb '08

A short-cut to disable ldap name service: # authconfig --kickstart --disableldap And to disable ldap authentication: # authconfig --kickstart --disableldapauth Now I believe it only does something if /etc/sysconfig/authconfig has these marked =YES, but if they are turned on there they will automatically be turned on again during the next reboot, so check there too. -Ross ----- Original Message ----- From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> To: CentOS mailing list <centos(a)centos.org> Sent: Tue Feb 19 20:09:56 2008 Subject: RE: [CentOS] nss_ldap failed to bind to LDAP server 127.0.0.1 From: Stephen Harris Sent: February 19, 2008 16:56 > > In other words you _had_ the right answer already! > Thanks muchly for the confirmation. I have made the necessary changes and I am just in the process of kicking people off so that I can reboot. I know the reboot may not be entirely required but it will ensure that all services have been restart and now reflect the configuration changes. Thanks again for your assistance. Regards, Hugh -- Hugh E Cruickshank, Forward Software, www.forward-software.com _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos ______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.

2 1

nss_ldap failed to bind to LDAP server 127.0.0.1
by Hugh E Cruickshank 20 Feb '08

20 Feb '08

Hi All: Over the weekend I install all the outstanding updates for our CentOS 4 based server. Since I had been holding off on these until I had addressed some disk space issues there were a large number (300+). I know my bad! After installing the updates I rebooted the system and it took forever to boot and once up there were problems connecting to some of our SAMBA shares. I checked the messages log file and found a multitude of entries similar to: Feb 17 19:46:18 fisds0 named[23187]: nss_ldap: failed to bind to LDAP server 127.0.0.1: Can't contact LDAP server Feb 17 19:46:18 fisds0 named[23187]: nss_ldap: reconnecting to LDAP server... These were being reported for named, nscd, smbd, statd, rquotad, etc. I did some google searching and found some references to the change of the default value for the "bind_policy" parameter in the "ldap.conf" file from "soft" to "hard". I added and explicit "bind_policy soft" to the "/etc/ldap.conf" file and that has improved things dramatically. However the errors are still being reported in the messages log file. The errors are valid as we do not have and LDAP server (on my list for a future project). What I am trying to figure out is why it is looking for one. I have done some additional google searching but I have not found any definitive answers. From what I have seen I suspect that the problem lays with our /etc/nsswitch.conf file and that I need to change references to "file ldap" to just "files". I am loath to make such changes without something more definite then my personal suspicion. Can someone confirm that I am on the right track or, if not, point me in the right direction? TIA Regards, Hugh -- Hugh E Cruickshank, Forward Software, www.forward-software.com

6 11

acroread 8 on CentOS-4 (was for SL4)
by Akemi Yagi 19 Feb '08

19 Feb '08

I know acroread is not part of CentOS but many people use it. Thought forwarding this post on the SciLinux mailing list might help those who use acroread on CentOS-4. === excerpt === The "latest" version officially compatible with RHEL4 is acroread-7.0.9, but this currently has open security holes (CVE-2007-5663 et al). http://www.adobe.com/support/security/advisories/apsa08-01.html still says (as of today, i.e. 2 weeks after the initial announcement): > Acrobat and Adobe Reader 7.0.9 and earlier versions are also affected > by these vulnerabilities. Adobe will provide further information as > to the nature of the vulnerabilities via the company's Security > Bulletins and Advisories page once updates are available for all > affected versions of Acrobat and Adobe Reader. acoread-8.1.2 (which is patched) requires RHEL5 as per Adobe (libgtk+2.6 ?). It appears that despite this requirement, it happily runs under 4 as well.. at least for the limited use we foresee over here. === end === For the entire post, see: http://listserv.fnal.gov/scripts/wa.exe?A2=ind0802&L=scientific-linux-users… Akemi

3 2

named dead but subsys locked
by Paul A 19 Feb '08

19 Feb '08

Hi I recently compliled Bind 9.4.2 on CentOS release 5 (Final) 2.6.18-53.1.13.el5 #1 SMP I compiled named chroot, I have done this on several other centos 4 server with no issues however on this centos 5 server im seeing [root@testip1 named]# service named status named dead but subsys locked [root@testip1 named]# service named stop Shutting down named: [FAILED] It looks like service named stop isn't killing the name process either. Anyone know what im doing wrong? Also where can I find the named init script for centos 5. Thanks, Paul

3 5

discrepancy between what quota reports and what du reports (second time post)
by ankush grover 19 Feb '08

19 Feb '08

Hi Friends, I am running samba as domain member of AD 2k3 on Centos 4.4 . Quota of 2GB is set for each user but for 2-3 uers quota or edquota is showing wrong blocks even though disk space occupied by that user is very less than the quota specified for ex 810 MB. quota bhavesh.kumar Disk quotas for user bhavesh.kumar (uid 11254): Filesystem blocks quota limit grace files quota limit grace /dev/cciss/c0d0p5 2791832* 2000000 2000000 1595 0 0 # du -sh bhavesh.kumar 809M bhavesh.kumar dumpe2fs /dev/cciss/c0d0p3 |grep -i "block size" dumpe2fs 1.35 (28-Feb-2004) Block size: 4096 I tried quotaoff and quotaon on the /home partition and also mount -all command to remount the partitions but still the problem is persisting. Further diagnosing the problem there are double entries of the files in the directory kindly see entries 45-50 & 63-68 find . -uid 11254 -exec ls -l "{}" ";"|nl | more 45 -rwxr--r-- 1 bhavesh.kumar root 27136 Feb 7 15:44 Appraisal-ADP.xls 46 -rwxr--r-- 1 bhavesh.kumar root 24064 Feb 7 15:44 Appraisal-DAL.xls 47 -rwxr--r-- 1 bhavesh.kumar root 26112 Feb 7 15:44 Appraisal-Guidelines.xls 48 -rwxr--r-- 1 bhavesh.kumar root 55296 Feb 7 15:44 Appraisal-GUI.xls 49 -rwxr--r-- 1 bhavesh.kumar root 30208 Feb 7 15:44 AppraisalMaster.xls 50 -rwxr--r-- 1 bhavesh.kumar root 37376 Feb 7 15:44 Appraisal-QA.xls 51 drwxr-xr-x 2 bhavesh.kumar root 4096 Feb 7 15:44 Apr-Sep2006 52 drwxr-xr-x 2 bhavesh.kumar root 4096 Feb 7 15:44 Apr-sep-2007 53 -rwxr--r-- 1 bhavesh.kumar root 21504 Feb 7 15:44 Brabeion - Appraisal.xls 54 -rwxr--r-- 1 bhavesh.kumar root 19456 Feb 7 15:44 Guidelines.xls 55 drwxr-xr-x 2 bhavesh.kumar root 4096 Feb 7 15:44 Oct-Mar2007 56 -rwxr--r-- 1 bhavesh.kumar root 37376 Feb 7 15:44 ./Laptop Data/Brabeion/Appraisal/Appraisal-QA.xls 57 -rwxr--r-- 1 bhavesh.kumar root 24064 Feb 7 15:44 ./Laptop Data/Brabeion/Appraisal/Appraisal-DAL.xls 58 total 28 59 -rwxr--r-- 1 bhavesh.kumar root 26624 Feb 7 15:44 Team.xls 60 -rwxr--r-- 1 bhavesh.kumar root 26624 Feb 7 15:44 ./Laptop Data/Brabeion/Appraisal/Apr-sep-2007/Team.xls 61 -rwxr--r-- 1 bhavesh.kumar root 26112 Feb 7 15:44 ./Laptop Data/Brabeion/Appraisal/Appraisal-Guidelines.xls 62 total 256 63 -rwxr--r-- 1 bhavesh.kumar root 27136 Feb 7 15:44 Appraisal-ADP.xls 64 -rwxr--r-- 1 bhavesh.kumar root 24064 Feb 7 15:44 Appraisal-DAL.xls 65 -rwxr--r-- 1 bhavesh.kumar root 26112 Feb 7 15:44 Appraisal-Guidelines.xls 66 -rwxr--r-- 1 bhavesh.kumar root 55296 Feb 7 15:44 Appraisal-GUI.xls 67 -rwxr--r-- 1 bhavesh.kumar root 30208 Feb 7 15:44 AppraisalMaster.xls 68 -rwxr--r-- 1 bhavesh.kumar root 37376 Feb 7 15:44 Appraisal-QA.xls 69 -rwxr--r-- 1 bhavesh.kumar root 21504 Feb 7 15:44 Brabeion - Appraisal.xls 70 -rwxr--r-- 1 bhavesh.kumar root 19456 Feb 7 15:44 Guidelines.xls 71 -rwxr--r-- 1 bhavesh.kumar root 37376 Feb 7 15:44 ./Laptop Data/Brabeion/Appraisal/Apr-Sep2006/Appraisal-QA.xls 72 -rwxr--r-- 1 bhavesh.kumar root 24064 Feb 7 15:44 ./Laptop Data/Brabeion/Appraisal/Apr-Sep2006/Appraisal-DAL.xls 73 -rwxr--r-- 1 bhavesh.kumar root 26112 Feb 7 15:44 ./Laptop Data/Brabeion/Appraisal/Apr-Sep2006/Appraisal-Guidelines.xls 74 -rwxr--r-- 1 bhavesh.kumar root 30208 Feb 7 15:44 ./Laptop Data/Brabeion/Appraisal/Apr-Sep2006/AppraisalMaster.xls 75 -rwxr--r-- 1 bhavesh.kumar root 21504 Feb 7 15:44 ./Laptop Data/Brabeion/Appraisal/Apr-Sep2006/Brabeion - Appraisal.xls 76 -rwxr--r-- 1 bhavesh.kumar root 19456 Feb 7 15:44 ./Laptop Data/Brabeion/Appraisal/Apr-Sep2006/Guidelines.xls 77 -rwxr--r-- 1 bhavesh.kumar root 27136 Feb 7 15:44 ./Laptop Data/Brabeion/Appraisal/Apr-Sep2006/Appraisal-ADP.xls 78 -rwxr--r-- 1 bhavesh.kumar root 55296 Feb 7 15:44 ./Laptop Data/Brabeion/Appraisal/Apr-Sep2006/Appraisal-GUI.xls 79 total 200 I have rebooted the system but still the problem persists. Even I have recreated the users again but everytime it is taking up the old blocks. There is another person who faced the same problem with redhat 4.4 but the solution is not given. http://www.opensubscriber.com/message/centos@centos.org/8548096.html Thanks & Regards

2 1

CentOS-announce Digest, Vol 36, Issue 9
by centos-announce-request＠centos.org 19 Feb '08

19 Feb '08

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CentOS 5 i386 - The CentOS-5.1 i386 Live CD is released (Patrice Guay) ---------------------------------------------------------------------- Message: 1 Date: Mon, 18 Feb 2008 09:38:11 -0500 From: Patrice Guay <patrice(a)centos.org> Subject: [CentOS-announce] CentOS 5 i386 - The CentOS-5.1 i386 Live CD is released To: centos-announce(a)centos.org Cc: lwn(a)lwn.net, distro(a)distrowatch.org Message-ID: <47B99853.8010206(a)centos.org> Content-Type: text/plain; charset=ISO-8859-1 The CentOS Development team is pleased to announce the availability of the CentOS 5.1 i386 Live CD. This CD is based on our CentOS-5.1 i386 distribution. It can be used as a Workstation, with the following software: # openoffice.org 2.0.4 # firefox 1.5.0.12 # thunderbird 1.5.0.12 # pidgin 2.0.2 # scribus 1.3.3.2 # xchat 2.6.6 # k3b 0.12.17 # gimp 2.2.13 It can also be used as a rescue CD with the following tools: # memtest86+-1.65 # Full set of LVM and RAID command line tools # QTParted # Nmap and NMapFE # traceroute # samba-3.0.25b with cifs kernel support to connect to Windows file shares # System Log Viewer # GUI Hardware Device Manager ================================================================ The CentOS Live CD project home page is here: https://projects.centos.org/trac/livecd/ Live CD build scripts, screenshots, booting from a USB key, custom Live CD Creation and other information is available there. ================================================================ The CentOS 5.1 i386 Live CD is based on the Fedora livecd-tools project: http://fedoraproject.org/wiki/FedoraLiveCD ================================================================ You can get the CentOS 5.1 i386 Live CD from the CentOS mirrors: http://isoredirect.centos.org/centos/5/isos/i386/ * Filename: CentOS-5.1-i386-LiveCD.iso * Size: 720766976 * MD5Sum: 32de2ac951b3f50144d833241eaf0100 * SHA1Sum: 0912d455d0192fe3823bcb17795d2e0186a47d43 ================================================================ Release Notes: LiveCD Release Notes: http://wiki.centos.org/Manuals/ReleaseNotes/CentOSLiveCD5.1 CentOS-5.1 Release Notes: http://wiki.centos.org/Manuals/ReleaseNotes/CentOS5.1 upstream Release Notes here: http://www.centos.org/docs/5/html/release-notes/as-x86/index.html CentOS-5 Documentation is here: http://www.centos.org/docs/5/ ================================================================ The CentOS Project would like to thank Patrice Guay for the creation of this CD. Patrice did the Tao Linux live CDs in the past and also the CentOS-5.0 live CD and graciously donated his time and effort to make this one too. We would also like to thank the CentOS QA team for testing this LiveCD and their many suggestions to make it better ================================================================ To stay current with CentOS: Visit our website at http://www.centos.org/ Join the CentOS mailing list at: http://lists.centos.org/mailman/listinfo/centos Catch the Wiki at http://wiki.centos.org Join various team members on IRC at irc.freenode.net #centos ================================================================ Thanks, The CentOS Development Team ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 36, Issue 9 **********************************************

1 0

Best way to install non-official packages?
by Thorsten Kampe 19 Feb '08

19 Feb '08

Sooner or later everyone needs to install a package that is not included on the official installation CDs/DVD. Until now I just used rpmseek.com and Rpmfind.Net but of course this is far from optimal for security and compatibility to reasons. So what is the recommended way to get and install "non official" packages that are not part of the repository?! Thorsten

6 6

Segafault Apache 2.0.59 Release 1.el4s1.10.el4.centos anyone?
by Devraj Mukherjee 19 Feb '08

19 Feb '08

Hi everyone, I have this package installed, and Apache has been sefaulting randomly on my server. I have tried to locate the fault and believe the problem may be in mod_php. However there are various posts that say that HTTPD could have an issues as well. Is anyone else having similar issues? Any feedback is welcome thanks. If httpd crashes again I should have a segfault dump and I will make that available. Name : httpd Arch : x86_64 Version: 2.0.59 Release: 1.el4s1.10.el4.centos Size : 2.7 M Repo : installed Summary: Apache HTTP Server -- "I never look back darling, it distracts from the now", Edna Mode (The Incredibles)

1 0

Password Protecting a Root Directory
by John Hinton 19 Feb '08

19 Feb '08

I have apache running with virtual hosting. I have a customer who wants to password protect their /user/public_html directory using htaccess. I've done this many times on directories inside of that directory with positive results. However, I don't seem to be able to password protect the document root directory. Any ideas? John Hinton

2 3

kernel-devel: compile MPP/RDAC kernel module
by Simon Jolle 18 Feb '08

18 Feb '08

Hi Centos Users I am running Centos 4.6 wit latest updates. For I/O multipathing I need to use kernel 2.6.9-55 (IBM support matrix). Trying to compile Engenio Linux RDAC Driver[0] I fail to install kernel-devel for this exact kernel (with up2date). Up2date always installs the newest. # make clean make V=1 -C/lib/modules/2.6.9-55.ELsmp/build M=/root/tmp/linuxrdac-09.02.B5.15 MODVERDIR=/lib/modules/2.6.9-55.ELsmp/build/.tmp_versions SUBDIRS=/root/tmp/linuxrdac-09.02.B5.15 clean make: *** /lib/modules/2.6.9-55.ELsmp/build: No such file or directory. Stop. make: *** [clean] Error 2 # ls -al /lib/modules/2.6.9-55.ELsmp/build ls: /lib/modules/2.6.9-55.ELsmp/build: No such file or directory # uname -r 2.6.9-55.ELsmp # rpm -q kernel-devel kernel-devel-2.6.9-67.0.4.EL.x86_64 cheers Simon [0] http://www.lsi.com/rdac/ -- XMPP: sjolle(a)swissjabber.org

3 2

IA64 Installation oddities
by Michael Walston 18 Feb '08

18 Feb '08

I've installed CentOS 4.6 on a Celestica IYA210 1U server. Configuration is 2GB PC2100 ECC, dual 1.4GHz Itanium 2 cpus, and various hard drives. The installer works great on 18GB, 36GB, and 73GB drives, however when I install to a 73GB drive there seems to be no functional /boot/efi that the system can map. Is this a system specific issue that I should ask about somewhere else? I'm bringing it up here just in case it happens to be some sort of bug that someone knows about. I apologize if this is not the proper place to ask this. Thank you, Mike W

1 0

help with x config on centos 5.1
by Jerry Geis 18 Feb '08

18 Feb '08

Hi all, Typically I dont have issues with configuring X. However this time its an issue. I have an NVIDIA graphics card trying to do 1920x1080. If I configure the screen by hand with the nvidia config utility it works at 1920x1080. However when I reboot its 800x600. When I use the nvidia config utility to set 1920x1080 then save the xorg.conf file, and reboot (yes I copied /tmp/xorg.conf to /etc/X11/xorg.conf) and rebooted its back to 800x600. The startx verbose gives me the clocking information (see below) however its always 800x600. Any ideas? Jerry ---------------------- Section "Monitor" ### Comment all HorizSync and VertSync values to use DDC: ### Comment all HorizSync and VertSync values to use DDC: Identifier "Monitor0" VendorName "Unknown" ModelName "VIZIO GV47L" HorizSync 31.0 - 70.0 VertRefresh 50.0 - 85.0 ModeLine "1920x1080" 148.3 1920 2008 2056 2200 1080 1084 1089 1125 +hsync +vsync Option "UseEDID" "FALSE" Option "UseEDIDDpi" "FALSE" Option "ModeValidation" "NoEdidModes" EndSection Section "Device" Identifier "Videocard0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce 7100 GS" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 24 Option "TwinView" "0" Option "metamodes" "1920x1080 +0+0; 1024x768 +0+0; 800x600 +0+0; 640x480 +0+0" Option "noedidDFPmaxsizecheck" Option "exactmodetimingsDVI" Option "modevalidation" "nodfpnativeresolutioncheck" Option "UseEDID" "FALSE" Option "UseEDIDDpi" "FALSE" Option "UseEdidFreqs" "False" Option "AllowDDCCI" "True" SubSection "Display" Depth 24 EndSubSection EndSection ------------------------ X Window System Version 6.8.2 Release Date: 9 February 2005 X Protocol Version 11, Revision 0, Release 6.8.2 Build Operating System: Linux 2.6.9-42.0.3.ELsmp x86_64 [ELF] Current Operating System: Linux MMCafeteria.cami3.com 2.6.21.1 #1 SMP Fri Jul 20 21:46:36 EDT 2007 x86_64 Build Date: 19 September 2007 Build Host: builder6 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present OS Kernel: Linux version 2.6.21.1 (root(a)localhost.localdomain) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-8)) #1 SMP Fri Jul 20 21:46:36 EDT 2007 PF Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 15 17:03:33 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "single head configuration" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Videocard0" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/TTF/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/TTF/"). (WW) `fonts.dir' not found (or not valid) in "/usr/X11R6/lib/X11/fonts/CID/". Entry deleted from font path. (Run 'mkfontdir' on "/usr/X11R6/lib/X11/fonts/CID/"). (==) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/" (==) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib64/modules" (**) Option "BlankTime" "0" (**) Option "StandbyTime" "0" (**) Option "SuspendTime" "0" (**) Option "OffTime" "0" (**) Option "Xinerama" "0" (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.7 X.Org XInput driver : 0.4 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib64/modules/fonts/libbitmap.a (II) Module bitmap: vendor="X.Org Foundation" compiled for 6.8.2, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib64/modules/libpcidata.a (II) Module pcidata: vendor="X.Org Foundation" compiled for 6.8.2, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.7 (--) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 10de,03ea card 1458,5001 rev a1 class 05,00,00 hdr 00 (II) PCI: 00:01:0: chip 10de,03e0 card 1458,0c11 rev a2 class 06,01,00 hdr 80 (II) PCI: 00:01:1: chip 10de,03eb card 1458,0c11 rev a2 class 0c,05,00 hdr 80 (II) PCI: 00:01:2: chip 10de,03f5 card 1458,0c11 rev a2 class 05,00,00 hdr 80 (II) PCI: 00:02:0: chip 10de,03f1 card 1458,5004 rev a3 class 0c,03,10 hdr 80 (II) PCI: 00:02:1: chip 10de,03f2 card 1458,5004 rev a3 class 0c,03,20 hdr 80 (II) PCI: 00:04:0: chip 10de,03f3 card 0000,0000 rev a1 class 06,04,01 hdr 01 (II) PCI: 00:05:0: chip 10de,03f0 card 1458,a002 rev a2 class 04,03,00 hdr 80 (II) PCI: 00:06:0: chip 10de,03ec card 1458,5002 rev a2 class 01,01,8a hdr 00 (II) PCI: 00:07:0: chip 10de,03ef card 1458,e000 rev a2 class 06,80,00 hdr 00 (II) PCI: 00:08:0: chip 10de,03f6 card 1458,b002 rev a2 class 01,01,85 hdr 80 (II) PCI: 00:09:0: chip 10de,03e8 card 0000,0000 rev a2 class 06,04,00 hdr 01 (II) PCI: 00:18:0: chip 1022,1100 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:1: chip 1022,1101 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:2: chip 1022,1102 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 00:18:3: chip 1022,1103 card 0000,0000 rev 00 class 06,00,00 hdr 80 (II) PCI: 02:00:0: chip 10de,016a card 1682,2236 rev a1 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:1:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (II) Subtractive PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:4:0), (0,1,1), BCTRL: 0x0200 (VGA_EN is cleared) (II) Bus 1 I/O range: [0] -1 0 0x0000b000 - 0x0000bfff (0x1000) IX[B] (II) PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:9:0), (0,2,2), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 2 non-prefetchable memory range: [0] -1 0 0xf2000000 - 0xf4ffffff (0x3000000) MX[B] (II) Bus 2 prefetchable memory range: [0] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B] (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:24:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B] (--) PCI:*(2:0:0) nVidia Corporation unknown chipset (0x016a) rev 161, Mem @ 0xf2000000/24, 0xe0000000/28, 0xf3000000/24 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) Active PCI resource ranges: [0] -1 0 0xf5005000 - 0xf5005fff (0x1000) MX[B] [1] -1 0 0xf5004000 - 0xf5004fff (0x1000) MX[B] [2] -1 0 0xf5000000 - 0xf5003fff (0x4000) MX[B] [3] -1 0 0xf5006000 - 0xf50060ff (0x100) MX[B] [4] -1 0 0xf5007000 - 0xf5007fff (0x1000) MX[B] [5] -1 0 0xf3000000 - 0xf3ffffff (0x1000000) MX[B](B) [6] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [7] -1 0 0xf2000000 - 0xf2ffffff (0x1000000) MX[B](B) [8] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[B] [9] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B] [10] -1 0 0x00000970 - 0x00000977 (0x8) IX[B] [11] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B] [12] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B] [13] -1 0 0x0000cc00 - 0x0000cc07 (0x8) IX[B] [14] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B] [15] -1 0 0x0000c800 - 0x0000c83f (0x40) IX[B] [16] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B] [17] -1 0 0x0000c000 - 0x0000c03f (0x40) IX[B] (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xf5005000 - 0xf5005fff (0x1000) MX[B] [1] -1 0 0xf5004000 - 0xf5004fff (0x1000) MX[B] [2] -1 0 0xf5000000 - 0xf5003fff (0x4000) MX[B] [3] -1 0 0xf5006000 - 0xf50060ff (0x100) MX[B] [4] -1 0 0xf5007000 - 0xf5007fff (0x1000) MX[B] [5] -1 0 0xf3000000 - 0xf3ffffff (0x1000000) MX[B](B) [6] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [7] -1 0 0xf2000000 - 0xf2ffffff (0x1000000) MX[B](B) [8] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[B] [9] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B] [10] -1 0 0x00000970 - 0x00000977 (0x8) IX[B] [11] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B] [12] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B] [13] -1 0 0x0000cc00 - 0x0000cc07 (0x8) IX[B] [14] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B] [15] -1 0 0x0000c800 - 0x0000c83f (0x40) IX[B] [16] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B] [17] -1 0 0x0000c000 - 0x0000c03f (0x40) IX[B] (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xf5005000 - 0xf5005fff (0x1000) MX[B] [6] -1 0 0xf5004000 - 0xf5004fff (0x1000) MX[B] [7] -1 0 0xf5000000 - 0xf5003fff (0x4000) MX[B] [8] -1 0 0xf5006000 - 0xf50060ff (0x100) MX[B] [9] -1 0 0xf5007000 - 0xf5007fff (0x1000) MX[B] [10] -1 0 0xf3000000 - 0xf3ffffff (0x1000000) MX[B](B) [11] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [12] -1 0 0xf2000000 - 0xf2ffffff (0x1000000) MX[B](B) [13] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [14] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [15] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[B] [16] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B] [17] -1 0 0x00000970 - 0x00000977 (0x8) IX[B] [18] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B] [19] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B] [20] -1 0 0x0000cc00 - 0x0000cc07 (0x8) IX[B] [21] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B] [22] -1 0 0x0000c800 - 0x0000c83f (0x40) IX[B] [23] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B] [24] -1 0 0x0000c000 - 0x0000c03f (0x40) IX[B] (II) LoadModule: "glx" (II) Loading /usr/X11R6/lib64/modules/extensions/libglx.so (II) Module glx: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.1 (II) NVIDIA GLX Module 169.09 Fri Jan 11 14:46:52 PST 2008 (II) Loading extension GLX (II) LoadModule: "extmod" (II) Loading /usr/X11R6/lib64/modules/extensions/libextmod.a (II) Module extmod: vendor="X.Org Foundation" compiled for 6.8.2, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "nvidia" (II) Loading /usr/X11R6/lib64/modules/drivers/nvidia_drv.so (II) Module nvidia: vendor="NVIDIA Corporation" compiled for 4.0.2, module version = 1.0.0 Module class: X.Org Video Driver (II) LoadModule: "mouse" (II) Loading /usr/X11R6/lib64/modules/input/mouse_drv.o (II) Module mouse: vendor="X.Org Foundation" compiled for 6.8.2, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.4 (II) LoadModule: "kbd" (II) Loading /usr/X11R6/lib64/modules/input/kbd_drv.o (II) Module kbd: vendor="X.Org Foundation" compiled for 6.8.2, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.4 (II) NVIDIA dlloader X Driver 169.09 Fri Jan 11 14:07:11 PST 2008 (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs (II) Primary Device is: PCI 02:00:0 (--) Assigning device section with no busID to primary device (--) Chipset NVIDIA GPU found (II) NVIDIA(0): Found 1 NVIDIA X Screens (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/X11R6/lib64/modules/libfb.a (II) Module fb: vendor="X.Org Foundation" compiled for 6.8.2, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.2 (II) Loading sub module "wfb" (II) LoadModule: "wfb" (II) Loading /usr/X11R6/lib64/modules/libwfb.so (II) Module wfb: vendor="NVIDIA Corporation" compiled for 4.23.73Vz, module version = 1.0.0 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Loading /usr/X11R6/lib64/modules/libramdac.a (II) Module ramdac: vendor="X.Org Foundation" compiled for 6.8.2, module version = 0.1.0 ABI class: X.Org Video Driver, version 0.7 (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xf5005000 - 0xf5005fff (0x1000) MX[B] [6] -1 0 0xf5004000 - 0xf5004fff (0x1000) MX[B] [7] -1 0 0xf5000000 - 0xf5003fff (0x4000) MX[B] [8] -1 0 0xf5006000 - 0xf50060ff (0x100) MX[B] [9] -1 0 0xf5007000 - 0xf5007fff (0x1000) MX[B] [10] -1 0 0xf3000000 - 0xf3ffffff (0x1000000) MX[B](B) [11] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [12] -1 0 0xf2000000 - 0xf2ffffff (0x1000000) MX[B](B) [13] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [14] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [15] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[B] [16] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B] [17] -1 0 0x00000970 - 0x00000977 (0x8) IX[B] [18] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B] [19] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B] [20] -1 0 0x0000cc00 - 0x0000cc07 (0x8) IX[B] [21] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B] [22] -1 0 0x0000c800 - 0x0000c83f (0x40) IX[B] [23] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B] [24] -1 0 0x0000c000 - 0x0000c03f (0x40) IX[B] (II) resource ranges after probing: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xf5005000 - 0xf5005fff (0x1000) MX[B] [6] -1 0 0xf5004000 - 0xf5004fff (0x1000) MX[B] [7] -1 0 0xf5000000 - 0xf5003fff (0x4000) MX[B] [8] -1 0 0xf5006000 - 0xf50060ff (0x100) MX[B] [9] -1 0 0xf5007000 - 0xf5007fff (0x1000) MX[B] [10] -1 0 0xf3000000 - 0xf3ffffff (0x1000000) MX[B](B) [11] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [12] -1 0 0xf2000000 - 0xf2ffffff (0x1000000) MX[B](B) [13] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [14] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [15] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [17] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [18] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[B] [19] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B] [20] -1 0 0x00000970 - 0x00000977 (0x8) IX[B] [21] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B] [22] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B] [23] -1 0 0x0000cc00 - 0x0000cc07 (0x8) IX[B] [24] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B] [25] -1 0 0x0000c800 - 0x0000c83f (0x40) IX[B] [26] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B] [27] -1 0 0x0000c000 - 0x0000c03f (0x40) IX[B] [28] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [29] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32 (==) NVIDIA(0): RGB weight 888 (==) NVIDIA(0): Default visual is TrueColor (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0) (**) NVIDIA(0): Option "UseEDID" "FALSE" (**) NVIDIA(0): Option "UseEdidFreqs" "False" (**) NVIDIA(0): Option "TwinView" "0" (**) NVIDIA(0): Option "MetaModes" "1920x1080 +0+0; 1024x768 +0+0; 800x600 +0+0; 640x480 +0+0" (**) NVIDIA(0): Option "ExactModeTimingsDVI" (**) NVIDIA(0): Option "UseEdidDpi" "FALSE" (**) NVIDIA(0): Option "ModeValidation" "nodfpnativeresolutioncheck" (==) NVIDIA(0): Using HW cursor (**) NVIDIA(0): Enabling RENDER acceleration (==) NVIDIA(0): Video key set to default value of 0x101fe (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID has been (**) NVIDIA(0): disabled on all display devices. (**) NVIDIA(0): Ignoring EDIDs (II) NVIDIA(GPU-0): Not probing EDID on DFP-0. (II) NVIDIA(0): NVIDIA GPU GeForce 7100 GS (NV44) at PCI:2:0:0 (GPU-0) (--) NVIDIA(0): Memory: 524288 kBytes (II) NVIDIA(0): GPU RAM Type: DDR2 (--) NVIDIA(0): VideoBIOS: 05.44.02.67.20 (--) NVIDIA(0): Found 2 CRTCs on board (II) NVIDIA(0): Supported display device(s): CRT-0, CRT-1, DFP-0, TV-0 (II) NVIDIA(0): Bus detected as PCI Express (II) NVIDIA(0): Detected PCI Express Link width: 8X (--) NVIDIA(0): Interlaced video modes are supported on this GPU (II) NVIDIA(0): VPES : 3 (II) NVIDIA(0): SPS : 4 (II) NVIDIA(0): (II) NVIDIA(0): Mode timing constraints for : GeForce 7100 GS (II) NVIDIA(0): Maximum mode timing values : (II) NVIDIA(0): Horizontal Visible Width : 8192 (II) NVIDIA(0): Horizontal Blank Start : 8192 (II) NVIDIA(0): Horizontal Blank Width : 4096 (II) NVIDIA(0): Horizontal Sync Start : 8184 (II) NVIDIA(0): Horizontal Sync Width : 504 (II) NVIDIA(0): Horizontal Total Width : 8224 (II) NVIDIA(0): Vertical Visible Height : 8192 (II) NVIDIA(0): Vertical Blank Start : 8192 (II) NVIDIA(0): Vertical Blank Width : 256 (II) NVIDIA(0): Veritcal Sync Start : 8191 (II) NVIDIA(0): Vertical Sync Width : 15 (II) NVIDIA(0): Vertical Total Height : 8193 (II) NVIDIA(0): (II) NVIDIA(0): Minimum mode timing values : (II) NVIDIA(0): Horizontal Total Width : 40 (II) NVIDIA(0): Vertical Total Height : 2 (II) NVIDIA(0): (II) NVIDIA(0): Mode timing alignment : (II) NVIDIA(0): Horizontal Visible Width : multiples of 8 (II) NVIDIA(0): Horizontal Blank Start : multiples of 8 (II) NVIDIA(0): Horizontal Blank Width : multiples of 8 (II) NVIDIA(0): Horizontal Sync Start : multiples of 8 (II) NVIDIA(0): Horizontal Sync Width : multiples of 8 (II) NVIDIA(0): Horizontal Total Width : multiples of 8 (II) NVIDIA(0): (--) NVIDIA(0): Connected display device(s) on GeForce 7100 GS at PCI:2:0:0: (--) NVIDIA(0): DFP-0 (--) NVIDIA(0): DFP-0: 155.0 MHz maximum pixel clock (--) NVIDIA(0): DFP-0: Internal Single Link TMDS (--) NVIDIA(0): DFP-0: Native FlatPanel Scaling is not supported (--) NVIDIA(0): DFP-0: DFP modes are not limited to 60 Hz refresh rate (--) NVIDIA(0): DFP-0: DFP is not internal to notebook (--) NVIDIA(0): (--) NVIDIA(0): --- EDID for DFP-0 --- (--) NVIDIA(0): (--) NVIDIA(0): No EDID Available. (--) NVIDIA(0): (--) NVIDIA(0): --- End of EDID for DFP-0 --- (--) NVIDIA(0): (II) NVIDIA(0): Mode Validation Overrides for DFP-0: (II) NVIDIA(0): NoDFPNativeResolutionCheck (II) NVIDIA(0): Frequency information for DFP-0: (II) NVIDIA(0): HorizSync : 31.000-70.000 kHz (II) NVIDIA(0): VertRefresh : 50.000-85.000 Hz (II) NVIDIA(0): (HorizSync from HorizSync in X Config Monitor section) (II) NVIDIA(0): (VertRefresh from VertRefresh in X Config Monitor (II) NVIDIA(0): section) (II) NVIDIA(0): (II) NVIDIA(0): --- Building ModePool for DFP-0 --- (II) NVIDIA(0): (II) NVIDIA(0): Native backend timings for DFP-0: (II) NVIDIA(0): 640 x 480 @ 60 Hz (II) NVIDIA(0): Pixel Clock : 25.175 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 656 (II) NVIDIA(0): HSyncEnd, HTotal : 752, 800 (II) NVIDIA(0): VRes, VSyncStart : 480, 490 (II) NVIDIA(0): VSyncEnd, VTotal : 492, 525 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1920x1080": (II) NVIDIA(0): 1920 x 1080 @ 60 Hz (II) NVIDIA(0): Mode Source: X Configuration file ModeLine (II) NVIDIA(0): Pixel Clock : 148.300 MHz (II) NVIDIA(0): HRes, HSyncStart : 1920, 2008 (II) NVIDIA(0): HSyncEnd, HTotal : 2056, 2200 (II) NVIDIA(0): VRes, VSyncStart : 1080, 1084 (II) NVIDIA(0): VSyncEnd, VTotal : 1089, 1125 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x350": (II) NVIDIA(0): 640 x 350 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 31.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 672 (II) NVIDIA(0): HSyncEnd, HTotal : 736, 832 (II) NVIDIA(0): VRes, VSyncStart : 350, 382 (II) NVIDIA(0): VSyncEnd, VTotal : 385, 445 (II) NVIDIA(0): H/V Polarity : +/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "320x175": (II) NVIDIA(0): 320 x 175 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 15.750 MHz (II) NVIDIA(0): HRes, HSyncStart : 320, 336 (II) NVIDIA(0): HSyncEnd, HTotal : 368, 416 (II) NVIDIA(0): VRes, VSyncStart : 175, 191 (II) NVIDIA(0): VSyncEnd, VTotal : 192, 222 (II) NVIDIA(0): H/V Polarity : +/- (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x400": (II) NVIDIA(0): 640 x 400 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 31.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 672 (II) NVIDIA(0): HSyncEnd, HTotal : 736, 832 (II) NVIDIA(0): VRes, VSyncStart : 400, 401 (II) NVIDIA(0): VSyncEnd, VTotal : 404, 445 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "320x200": (II) NVIDIA(0): 320 x 200 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 15.750 MHz (II) NVIDIA(0): HRes, HSyncStart : 320, 336 (II) NVIDIA(0): HSyncEnd, HTotal : 368, 416 (II) NVIDIA(0): VRes, VSyncStart : 200, 200 (II) NVIDIA(0): VSyncEnd, VTotal : 202, 222 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "720x400": (II) NVIDIA(0): 720 x 400 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 35.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 720, 756 (II) NVIDIA(0): HSyncEnd, HTotal : 828, 936 (II) NVIDIA(0): VRes, VSyncStart : 400, 401 (II) NVIDIA(0): VSyncEnd, VTotal : 404, 446 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "360x200": (II) NVIDIA(0): 360 x 200 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 17.750 MHz (II) NVIDIA(0): HRes, HSyncStart : 360, 378 (II) NVIDIA(0): HSyncEnd, HTotal : 414, 468 (II) NVIDIA(0): VRes, VSyncStart : 200, 200 (II) NVIDIA(0): VSyncEnd, VTotal : 202, 223 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x480": (II) NVIDIA(0): 640 x 480 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 25.200 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 656 (II) NVIDIA(0): HSyncEnd, HTotal : 752, 800 (II) NVIDIA(0): VRes, VSyncStart : 480, 490 (II) NVIDIA(0): VSyncEnd, VTotal : 492, 525 (II) NVIDIA(0): H/V Polarity : -/- (WW) NVIDIA(0): Mode is rejected: Incorrect X server VESA mode. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "320x240": (II) NVIDIA(0): 320 x 240 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 12.600 MHz (II) NVIDIA(0): HRes, HSyncStart : 320, 328 (II) NVIDIA(0): HSyncEnd, HTotal : 376, 400 (II) NVIDIA(0): VRes, VSyncStart : 240, 245 (II) NVIDIA(0): VSyncEnd, VTotal : 246, 262 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x480": (II) NVIDIA(0): 640 x 480 @ 73 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 31.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 664 (II) NVIDIA(0): HSyncEnd, HTotal : 704, 832 (II) NVIDIA(0): VRes, VSyncStart : 480, 489 (II) NVIDIA(0): VSyncEnd, VTotal : 491, 520 (II) NVIDIA(0): H/V Polarity : -/- (WW) NVIDIA(0): Mode is rejected: Incorrect X server VESA mode. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "320x240": (II) NVIDIA(0): 320 x 240 @ 73 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 15.750 MHz (II) NVIDIA(0): HRes, HSyncStart : 320, 332 (II) NVIDIA(0): HSyncEnd, HTotal : 352, 416 (II) NVIDIA(0): VRes, VSyncStart : 240, 244 (II) NVIDIA(0): VSyncEnd, VTotal : 245, 260 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x480": (II) NVIDIA(0): 640 x 480 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 31.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 656 (II) NVIDIA(0): HSyncEnd, HTotal : 720, 840 (II) NVIDIA(0): VRes, VSyncStart : 480, 481 (II) NVIDIA(0): VSyncEnd, VTotal : 484, 500 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "320x240": (II) NVIDIA(0): 320 x 240 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 15.750 MHz (II) NVIDIA(0): HRes, HSyncStart : 320, 328 (II) NVIDIA(0): HSyncEnd, HTotal : 360, 420 (II) NVIDIA(0): VRes, VSyncStart : 240, 240 (II) NVIDIA(0): VSyncEnd, VTotal : 242, 250 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x480": (II) NVIDIA(0): 640 x 480 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 36.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 696 (II) NVIDIA(0): HSyncEnd, HTotal : 752, 832 (II) NVIDIA(0): VRes, VSyncStart : 480, 481 (II) NVIDIA(0): VSyncEnd, VTotal : 484, 509 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "320x240": (II) NVIDIA(0): 320 x 240 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 18.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 320, 348 (II) NVIDIA(0): HSyncEnd, HTotal : 376, 416 (II) NVIDIA(0): VRes, VSyncStart : 240, 240 (II) NVIDIA(0): VSyncEnd, VTotal : 242, 254 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 56 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 36.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 824 (II) NVIDIA(0): HSyncEnd, HTotal : 896, 1024 (II) NVIDIA(0): VRes, VSyncStart : 600, 601 (II) NVIDIA(0): VSyncEnd, VTotal : 603, 625 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "400x300": (II) NVIDIA(0): 400 x 300 @ 56 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 18.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 400, 412 (II) NVIDIA(0): HSyncEnd, HTotal : 448, 512 (II) NVIDIA(0): VRes, VSyncStart : 300, 300 (II) NVIDIA(0): VSyncEnd, VTotal : 301, 312 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 40.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 840 (II) NVIDIA(0): HSyncEnd, HTotal : 968, 1056 (II) NVIDIA(0): VRes, VSyncStart : 600, 601 (II) NVIDIA(0): VSyncEnd, VTotal : 605, 628 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "400x300": (II) NVIDIA(0): 400 x 300 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 20.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 400, 420 (II) NVIDIA(0): HSyncEnd, HTotal : 484, 528 (II) NVIDIA(0): VRes, VSyncStart : 300, 300 (II) NVIDIA(0): VSyncEnd, VTotal : 302, 314 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 72 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 50.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 856 (II) NVIDIA(0): HSyncEnd, HTotal : 976, 1040 (II) NVIDIA(0): VRes, VSyncStart : 600, 637 (II) NVIDIA(0): VSyncEnd, VTotal : 643, 666 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "400x300": (II) NVIDIA(0): 400 x 300 @ 72 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 25.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 400, 428 (II) NVIDIA(0): HSyncEnd, HTotal : 488, 520 (II) NVIDIA(0): VRes, VSyncStart : 300, 318 (II) NVIDIA(0): VSyncEnd, VTotal : 321, 333 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 49.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 816 (II) NVIDIA(0): HSyncEnd, HTotal : 896, 1056 (II) NVIDIA(0): VRes, VSyncStart : 600, 601 (II) NVIDIA(0): VSyncEnd, VTotal : 604, 625 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "400x300": (II) NVIDIA(0): 400 x 300 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 24.750 MHz (II) NVIDIA(0): HRes, HSyncStart : 400, 408 (II) NVIDIA(0): HSyncEnd, HTotal : 448, 528 (II) NVIDIA(0): VRes, VSyncStart : 300, 300 (II) NVIDIA(0): VSyncEnd, VTotal : 302, 312 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 56.300 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 832 (II) NVIDIA(0): HSyncEnd, HTotal : 896, 1048 (II) NVIDIA(0): VRes, VSyncStart : 600, 601 (II) NVIDIA(0): VSyncEnd, VTotal : 604, 631 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "400x300": (II) NVIDIA(0): 400 x 300 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 28.150 MHz (II) NVIDIA(0): HRes, HSyncStart : 400, 416 (II) NVIDIA(0): HSyncEnd, HTotal : 448, 524 (II) NVIDIA(0): VRes, VSyncStart : 300, 300 (II) NVIDIA(0): VSyncEnd, VTotal : 302, 315 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 87 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 44.900 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1032 (II) NVIDIA(0): HSyncEnd, HTotal : 1208, 1264 (II) NVIDIA(0): VRes, VSyncStart : 768, 768 (II) NVIDIA(0): VSyncEnd, VTotal : 776, 817 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : Interlace (WW) NVIDIA(0): Mode is rejected: VertRefresh (87.0 Hz) out of range (WW) NVIDIA(0): (50.000-85.000 Hz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "512x384": (II) NVIDIA(0): 512 x 384 @ 87 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 22.450 MHz (II) NVIDIA(0): HRes, HSyncStart : 512, 516 (II) NVIDIA(0): HSyncEnd, HTotal : 604, 632 (II) NVIDIA(0): VRes, VSyncStart : 384, 384 (II) NVIDIA(0): VSyncEnd, VTotal : 388, 408 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : Interlace DoubleScan (WW) NVIDIA(0): Mode is rejected: VertRefresh (87.1 Hz) out of range (WW) NVIDIA(0): (50.000-85.000 Hz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 65.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1048 (II) NVIDIA(0): HSyncEnd, HTotal : 1184, 1344 (II) NVIDIA(0): VRes, VSyncStart : 768, 771 (II) NVIDIA(0): VSyncEnd, VTotal : 777, 806 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "512x384": (II) NVIDIA(0): 512 x 384 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 32.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 512, 524 (II) NVIDIA(0): HSyncEnd, HTotal : 592, 672 (II) NVIDIA(0): VRes, VSyncStart : 384, 385 (II) NVIDIA(0): VSyncEnd, VTotal : 388, 403 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 70 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 75.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1048 (II) NVIDIA(0): HSyncEnd, HTotal : 1184, 1328 (II) NVIDIA(0): VRes, VSyncStart : 768, 771 (II) NVIDIA(0): VSyncEnd, VTotal : 777, 806 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "512x384": (II) NVIDIA(0): 512 x 384 @ 70 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 37.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 512, 524 (II) NVIDIA(0): HSyncEnd, HTotal : 592, 664 (II) NVIDIA(0): VRes, VSyncStart : 384, 385 (II) NVIDIA(0): VSyncEnd, VTotal : 388, 403 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 78.800 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1040 (II) NVIDIA(0): HSyncEnd, HTotal : 1136, 1312 (II) NVIDIA(0): VRes, VSyncStart : 768, 769 (II) NVIDIA(0): VSyncEnd, VTotal : 772, 800 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: Incorrect X server VESA mode. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "512x384": (II) NVIDIA(0): 512 x 384 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 39.400 MHz (II) NVIDIA(0): HRes, HSyncStart : 512, 520 (II) NVIDIA(0): HSyncEnd, HTotal : 568, 656 (II) NVIDIA(0): VRes, VSyncStart : 384, 384 (II) NVIDIA(0): VSyncEnd, VTotal : 386, 400 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 94.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1072 (II) NVIDIA(0): HSyncEnd, HTotal : 1168, 1376 (II) NVIDIA(0): VRes, VSyncStart : 768, 769 (II) NVIDIA(0): VSyncEnd, VTotal : 772, 808 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "512x384": (II) NVIDIA(0): 512 x 384 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 47.250 MHz (II) NVIDIA(0): HRes, HSyncStart : 512, 536 (II) NVIDIA(0): HSyncEnd, HTotal : 584, 688 (II) NVIDIA(0): VRes, VSyncStart : 384, 384 (II) NVIDIA(0): VSyncEnd, VTotal : 386, 404 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1152x864": (II) NVIDIA(0): 1152 x 864 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 108.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1152, 1216 (II) NVIDIA(0): HSyncEnd, HTotal : 1344, 1600 (II) NVIDIA(0): VRes, VSyncStart : 864, 865 (II) NVIDIA(0): VSyncEnd, VTotal : 868, 900 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "576x432": (II) NVIDIA(0): 576 x 432 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 54.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 576, 608 (II) NVIDIA(0): HSyncEnd, HTotal : 672, 800 (II) NVIDIA(0): VRes, VSyncStart : 432, 432 (II) NVIDIA(0): VSyncEnd, VTotal : 434, 450 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1280x960": (II) NVIDIA(0): 1280 x 960 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 108.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1280, 1376 (II) NVIDIA(0): HSyncEnd, HTotal : 1488, 1800 (II) NVIDIA(0): VRes, VSyncStart : 960, 961 (II) NVIDIA(0): VSyncEnd, VTotal : 964, 1000 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x480": (II) NVIDIA(0): 640 x 480 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 54.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 688 (II) NVIDIA(0): HSyncEnd, HTotal : 744, 900 (II) NVIDIA(0): VRes, VSyncStart : 480, 480 (II) NVIDIA(0): VSyncEnd, VTotal : 482, 500 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1280x960": (II) NVIDIA(0): 1280 x 960 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 148.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 1280, 1344 (II) NVIDIA(0): HSyncEnd, HTotal : 1504, 1728 (II) NVIDIA(0): VRes, VSyncStart : 960, 961 (II) NVIDIA(0): VSyncEnd, VTotal : 964, 1011 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: HorizSync (85.9 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x480": (II) NVIDIA(0): 640 x 480 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 74.250 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 672 (II) NVIDIA(0): HSyncEnd, HTotal : 752, 864 (II) NVIDIA(0): VRes, VSyncStart : 480, 480 (II) NVIDIA(0): VSyncEnd, VTotal : 482, 505 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (85.9 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1280x1024": (II) NVIDIA(0): 1280 x 1024 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 108.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1280, 1328 (II) NVIDIA(0): HSyncEnd, HTotal : 1440, 1688 (II) NVIDIA(0): VRes, VSyncStart : 1024, 1025 (II) NVIDIA(0): VSyncEnd, VTotal : 1028, 1066 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x512": (II) NVIDIA(0): 640 x 512 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 54.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 664 (II) NVIDIA(0): HSyncEnd, HTotal : 720, 844 (II) NVIDIA(0): VRes, VSyncStart : 512, 512 (II) NVIDIA(0): VSyncEnd, VTotal : 514, 533 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1280x1024": (II) NVIDIA(0): 1280 x 1024 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 135.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1280, 1296 (II) NVIDIA(0): HSyncEnd, HTotal : 1440, 1688 (II) NVIDIA(0): VRes, VSyncStart : 1024, 1025 (II) NVIDIA(0): VSyncEnd, VTotal : 1028, 1066 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: HorizSync (80.0 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x512": (II) NVIDIA(0): 640 x 512 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 67.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 648 (II) NVIDIA(0): HSyncEnd, HTotal : 720, 844 (II) NVIDIA(0): VRes, VSyncStart : 512, 512 (II) NVIDIA(0): VSyncEnd, VTotal : 514, 533 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (80.0 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1280x1024": (II) NVIDIA(0): 1280 x 1024 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 157.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 1280, 1344 (II) NVIDIA(0): HSyncEnd, HTotal : 1504, 1728 (II) NVIDIA(0): VRes, VSyncStart : 1024, 1025 (II) NVIDIA(0): VSyncEnd, VTotal : 1028, 1072 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (157.5 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x512": (II) NVIDIA(0): 640 x 512 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 78.750 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 672 (II) NVIDIA(0): HSyncEnd, HTotal : 752, 864 (II) NVIDIA(0): VRes, VSyncStart : 512, 512 (II) NVIDIA(0): VSyncEnd, VTotal : 514, 536 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (91.1 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1600x1200": (II) NVIDIA(0): 1600 x 1200 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 162.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1600, 1664 (II) NVIDIA(0): HSyncEnd, HTotal : 1856, 2160 (II) NVIDIA(0): VRes, VSyncStart : 1200, 1201 (II) NVIDIA(0): VSyncEnd, VTotal : 1204, 1250 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: HorizSync (75.0 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 81.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 832 (II) NVIDIA(0): HSyncEnd, HTotal : 928, 1080 (II) NVIDIA(0): VRes, VSyncStart : 600, 600 (II) NVIDIA(0): VSyncEnd, VTotal : 602, 625 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (75.0 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1600x1200": (II) NVIDIA(0): 1600 x 1200 @ 65 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 175.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 1600, 1664 (II) NVIDIA(0): HSyncEnd, HTotal : 1856, 2160 (II) NVIDIA(0): VRes, VSyncStart : 1200, 1201 (II) NVIDIA(0): VSyncEnd, VTotal : 1204, 1250 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (175.5 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 65 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 87.750 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 832 (II) NVIDIA(0): HSyncEnd, HTotal : 928, 1080 (II) NVIDIA(0): VRes, VSyncStart : 600, 600 (II) NVIDIA(0): VSyncEnd, VTotal : 602, 625 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (81.2 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1600x1200": (II) NVIDIA(0): 1600 x 1200 @ 70 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 189.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1600, 1664 (II) NVIDIA(0): HSyncEnd, HTotal : 1856, 2160 (II) NVIDIA(0): VRes, VSyncStart : 1200, 1201 (II) NVIDIA(0): VSyncEnd, VTotal : 1204, 1250 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (189.0 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 70 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 94.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 832 (II) NVIDIA(0): HSyncEnd, HTotal : 928, 1080 (II) NVIDIA(0): VRes, VSyncStart : 600, 600 (II) NVIDIA(0): VSyncEnd, VTotal : 602, 625 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (87.5 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1600x1200": (II) NVIDIA(0): 1600 x 1200 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 202.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 1600, 1664 (II) NVIDIA(0): HSyncEnd, HTotal : 1856, 2160 (II) NVIDIA(0): VRes, VSyncStart : 1200, 1201 (II) NVIDIA(0): VSyncEnd, VTotal : 1204, 1250 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (202.5 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 101.250 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 832 (II) NVIDIA(0): HSyncEnd, HTotal : 928, 1080 (II) NVIDIA(0): VRes, VSyncStart : 600, 600 (II) NVIDIA(0): VSyncEnd, VTotal : 602, 625 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (93.8 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1600x1200": (II) NVIDIA(0): 1600 x 1200 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 229.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 1600, 1664 (II) NVIDIA(0): HSyncEnd, HTotal : 1856, 2160 (II) NVIDIA(0): VRes, VSyncStart : 1200, 1201 (II) NVIDIA(0): VSyncEnd, VTotal : 1204, 1250 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (229.5 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 114.750 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 832 (II) NVIDIA(0): HSyncEnd, HTotal : 928, 1080 (II) NVIDIA(0): VRes, VSyncStart : 600, 600 (II) NVIDIA(0): VSyncEnd, VTotal : 602, 625 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (106.2 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1792x1344": (II) NVIDIA(0): 1792 x 1344 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 204.800 MHz (II) NVIDIA(0): HRes, HSyncStart : 1792, 1920 (II) NVIDIA(0): HSyncEnd, HTotal : 2120, 2448 (II) NVIDIA(0): VRes, VSyncStart : 1344, 1345 (II) NVIDIA(0): VSyncEnd, VTotal : 1348, 1394 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (204.8 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "896x672": (II) NVIDIA(0): 896 x 672 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 102.400 MHz (II) NVIDIA(0): HRes, HSyncStart : 896, 960 (II) NVIDIA(0): HSyncEnd, HTotal : 1060, 1224 (II) NVIDIA(0): VRes, VSyncStart : 672, 672 (II) NVIDIA(0): VSyncEnd, VTotal : 674, 697 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (83.7 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1792x1344": (II) NVIDIA(0): 1792 x 1344 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 261.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1792, 1888 (II) NVIDIA(0): HSyncEnd, HTotal : 2104, 2456 (II) NVIDIA(0): VRes, VSyncStart : 1344, 1345 (II) NVIDIA(0): VSyncEnd, VTotal : 1348, 1417 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (261.0 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "896x672": (II) NVIDIA(0): 896 x 672 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 130.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 896, 944 (II) NVIDIA(0): HSyncEnd, HTotal : 1052, 1228 (II) NVIDIA(0): VRes, VSyncStart : 672, 672 (II) NVIDIA(0): VSyncEnd, VTotal : 674, 708 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (106.3 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1856x1392": (II) NVIDIA(0): 1856 x 1392 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 218.300 MHz (II) NVIDIA(0): HRes, HSyncStart : 1856, 1952 (II) NVIDIA(0): HSyncEnd, HTotal : 2176, 2528 (II) NVIDIA(0): VRes, VSyncStart : 1392, 1393 (II) NVIDIA(0): VSyncEnd, VTotal : 1396, 1439 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (218.3 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "928x696": (II) NVIDIA(0): 928 x 696 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 109.150 MHz (II) NVIDIA(0): HRes, HSyncStart : 928, 976 (II) NVIDIA(0): HSyncEnd, HTotal : 1088, 1264 (II) NVIDIA(0): VRes, VSyncStart : 696, 696 (II) NVIDIA(0): VSyncEnd, VTotal : 698, 719 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (86.4 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1856x1392": (II) NVIDIA(0): 1856 x 1392 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 288.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1856, 1984 (II) NVIDIA(0): HSyncEnd, HTotal : 2208, 2560 (II) NVIDIA(0): VRes, VSyncStart : 1392, 1393 (II) NVIDIA(0): VSyncEnd, VTotal : 1396, 1500 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (288.0 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "928x696": (II) NVIDIA(0): 928 x 696 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 144.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 928, 992 (II) NVIDIA(0): HSyncEnd, HTotal : 1104, 1280 (II) NVIDIA(0): VRes, VSyncStart : 696, 696 (II) NVIDIA(0): VSyncEnd, VTotal : 698, 750 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (112.5 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1920x1440": (II) NVIDIA(0): 1920 x 1440 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 234.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1920, 2048 (II) NVIDIA(0): HSyncEnd, HTotal : 2256, 2600 (II) NVIDIA(0): VRes, VSyncStart : 1440, 1441 (II) NVIDIA(0): VSyncEnd, VTotal : 1444, 1500 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (234.0 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "960x720": (II) NVIDIA(0): 960 x 720 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 117.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 960, 1024 (II) NVIDIA(0): HSyncEnd, HTotal : 1128, 1300 (II) NVIDIA(0): VRes, VSyncStart : 720, 720 (II) NVIDIA(0): VSyncEnd, VTotal : 722, 750 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (90.0 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1920x1440": (II) NVIDIA(0): 1920 x 1440 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 297.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1920, 2064 (II) NVIDIA(0): HSyncEnd, HTotal : 2288, 2640 (II) NVIDIA(0): VRes, VSyncStart : 1440, 1441 (II) NVIDIA(0): VSyncEnd, VTotal : 1444, 1500 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (297.0 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "960x720": (II) NVIDIA(0): 960 x 720 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 148.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 960, 1032 (II) NVIDIA(0): HSyncEnd, HTotal : 1144, 1320 (II) NVIDIA(0): VRes, VSyncStart : 720, 720 (II) NVIDIA(0): VSyncEnd, VTotal : 722, 750 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (112.5 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "832x624": (II) NVIDIA(0): 832 x 624 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 57.284 MHz (II) NVIDIA(0): HRes, HSyncStart : 832, 864 (II) NVIDIA(0): HSyncEnd, HTotal : 928, 1152 (II) NVIDIA(0): VRes, VSyncStart : 624, 625 (II) NVIDIA(0): VSyncEnd, VTotal : 628, 667 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "416x312": (II) NVIDIA(0): 416 x 312 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 28.642 MHz (II) NVIDIA(0): HRes, HSyncStart : 416, 432 (II) NVIDIA(0): HSyncEnd, HTotal : 464, 576 (II) NVIDIA(0): VRes, VSyncStart : 312, 312 (II) NVIDIA(0): VSyncEnd, VTotal : 314, 333 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1152x768": (II) NVIDIA(0): 1152 x 768 @ 55 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 64.995 MHz (II) NVIDIA(0): HRes, HSyncStart : 1152, 1178 (II) NVIDIA(0): HSyncEnd, HTotal : 1314, 1472 (II) NVIDIA(0): VRes, VSyncStart : 768, 771 (II) NVIDIA(0): VSyncEnd, VTotal : 777, 806 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "576x384": (II) NVIDIA(0): 576 x 384 @ 55 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 32.497 MHz (II) NVIDIA(0): HRes, HSyncStart : 576, 589 (II) NVIDIA(0): HSyncEnd, HTotal : 657, 736 (II) NVIDIA(0): VRes, VSyncStart : 384, 385 (II) NVIDIA(0): VSyncEnd, VTotal : 388, 403 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1152x864": (II) NVIDIA(0): 1152 x 864 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 121.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 1152, 1216 (II) NVIDIA(0): HSyncEnd, HTotal : 1344, 1568 (II) NVIDIA(0): VRes, VSyncStart : 864, 865 (II) NVIDIA(0): VSyncEnd, VTotal : 868, 911 (II) NVIDIA(0): H/V Polarity : +/- (WW) NVIDIA(0): Mode is rejected: HorizSync (77.5 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "576x432": (II) NVIDIA(0): 576 x 432 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 60.750 MHz (II) NVIDIA(0): HRes, HSyncStart : 576, 608 (II) NVIDIA(0): HSyncEnd, HTotal : 672, 784 (II) NVIDIA(0): VRes, VSyncStart : 432, 432 (II) NVIDIA(0): VSyncEnd, VTotal : 434, 455 (II) NVIDIA(0): H/V Polarity : +/- (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (77.5 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1400x1050": (II) NVIDIA(0): 1400 x 1050 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 122.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1400, 1488 (II) NVIDIA(0): HSyncEnd, HTotal : 1640, 1880 (II) NVIDIA(0): VRes, VSyncStart : 1050, 1052 (II) NVIDIA(0): VSyncEnd, VTotal : 1064, 1082 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "700x525": (II) NVIDIA(0): 700 x 525 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 61.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 700, 744 (II) NVIDIA(0): HSyncEnd, HTotal : 820, 940 (II) NVIDIA(0): VRes, VSyncStart : 525, 526 (II) NVIDIA(0): VSyncEnd, VTotal : 532, 541 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: Mode's width (700) is not a multiple of (WW) NVIDIA(0): 8. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1400x1050": (II) NVIDIA(0): 1400 x 1050 @ 70 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 151.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1400, 1464 (II) NVIDIA(0): HSyncEnd, HTotal : 1656, 1960 (II) NVIDIA(0): VRes, VSyncStart : 1050, 1051 (II) NVIDIA(0): VSyncEnd, VTotal : 1054, 1100 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: HorizSync (77.0 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "700x525": (II) NVIDIA(0): 700 x 525 @ 70 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 75.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 700, 732 (II) NVIDIA(0): HSyncEnd, HTotal : 828, 980 (II) NVIDIA(0): VRes, VSyncStart : 525, 525 (II) NVIDIA(0): VSyncEnd, VTotal : 527, 550 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (77.0 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1400x1050": (II) NVIDIA(0): 1400 x 1050 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 155.800 MHz (II) NVIDIA(0): HRes, HSyncStart : 1400, 1464 (II) NVIDIA(0): HSyncEnd, HTotal : 1784, 1912 (II) NVIDIA(0): VRes, VSyncStart : 1050, 1052 (II) NVIDIA(0): VSyncEnd, VTotal : 1064, 1090 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (155.8 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "700x525": (II) NVIDIA(0): 700 x 525 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 77.900 MHz (II) NVIDIA(0): HRes, HSyncStart : 700, 732 (II) NVIDIA(0): HSyncEnd, HTotal : 892, 956 (II) NVIDIA(0): VRes, VSyncStart : 525, 526 (II) NVIDIA(0): VSyncEnd, VTotal : 532, 545 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (81.5 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1400x1050": (II) NVIDIA(0): 1400 x 1050 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 184.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1400, 1464 (II) NVIDIA(0): HSyncEnd, HTotal : 1656, 1960 (II) NVIDIA(0): VRes, VSyncStart : 1050, 1051 (II) NVIDIA(0): VSyncEnd, VTotal : 1054, 1100 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (184.0 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "700x525": (II) NVIDIA(0): 700 x 525 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 92.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 700, 732 (II) NVIDIA(0): HSyncEnd, HTotal : 828, 980 (II) NVIDIA(0): VRes, VSyncStart : 525, 525 (II) NVIDIA(0): VSyncEnd, VTotal : 527, 550 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (93.9 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1600x1024": (II) NVIDIA(0): 1600 x 1024 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 106.910 MHz (II) NVIDIA(0): HRes, HSyncStart : 1600, 1620 (II) NVIDIA(0): HSyncEnd, HTotal : 1640, 1670 (II) NVIDIA(0): VRes, VSyncStart : 1024, 1027 (II) NVIDIA(0): VSyncEnd, VTotal : 1030, 1067 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x512": (II) NVIDIA(0): 800 x 512 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 53.455 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 810 (II) NVIDIA(0): HSyncEnd, HTotal : 820, 835 (II) NVIDIA(0): VRes, VSyncStart : 512, 513 (II) NVIDIA(0): VSyncEnd, VTotal : 515, 533 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Extra : DoubleScan (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1920x1200": (II) NVIDIA(0): 1920 x 1200 @ 73 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 230.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1920, 1936 (II) NVIDIA(0): HSyncEnd, HTotal : 2096, 2528 (II) NVIDIA(0): VRes, VSyncStart : 1200, 1201 (II) NVIDIA(0): VSyncEnd, VTotal : 1204, 1250 (II) NVIDIA(0): H/V Polarity : -/- (WW) NVIDIA(0): Mode is rejected: PixelClock (230.0 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "960x600": (II) NVIDIA(0): 960 x 600 @ 73 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 115.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 960, 968 (II) NVIDIA(0): HSyncEnd, HTotal : 1048, 1264 (II) NVIDIA(0): VRes, VSyncStart : 600, 600 (II) NVIDIA(0): VSyncEnd, VTotal : 602, 625 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (91.0 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1920x1440": (II) NVIDIA(0): 1920 x 1440 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 341.350 MHz (II) NVIDIA(0): HRes, HSyncStart : 1920, 2072 (II) NVIDIA(0): HSyncEnd, HTotal : 2288, 2656 (II) NVIDIA(0): VRes, VSyncStart : 1440, 1441 (II) NVIDIA(0): VSyncEnd, VTotal : 1444, 1512 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (341.4 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "960x720": (II) NVIDIA(0): 960 x 720 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 170.675 MHz (II) NVIDIA(0): HRes, HSyncStart : 960, 1036 (II) NVIDIA(0): HSyncEnd, HTotal : 1144, 1328 (II) NVIDIA(0): VRes, VSyncStart : 720, 720 (II) NVIDIA(0): VSyncEnd, VTotal : 722, 756 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: PixelClock (170.7 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "2048x1536": (II) NVIDIA(0): 2048 x 1536 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 266.950 MHz (II) NVIDIA(0): HRes, HSyncStart : 2048, 2200 (II) NVIDIA(0): HSyncEnd, HTotal : 2424, 2800 (II) NVIDIA(0): VRes, VSyncStart : 1536, 1537 (II) NVIDIA(0): VSyncEnd, VTotal : 1540, 1589 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (266.9 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 60 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 133.475 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1100 (II) NVIDIA(0): HSyncEnd, HTotal : 1212, 1400 (II) NVIDIA(0): VRes, VSyncStart : 768, 768 (II) NVIDIA(0): VSyncEnd, VTotal : 770, 794 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: HorizSync (95.3 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "2048x1536": (II) NVIDIA(0): 2048 x 1536 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 340.480 MHz (II) NVIDIA(0): HRes, HSyncStart : 2048, 2216 (II) NVIDIA(0): HSyncEnd, HTotal : 2440, 2832 (II) NVIDIA(0): VRes, VSyncStart : 1536, 1537 (II) NVIDIA(0): VSyncEnd, VTotal : 1540, 1603 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (340.5 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 75 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 170.240 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1108 (II) NVIDIA(0): HSyncEnd, HTotal : 1220, 1416 (II) NVIDIA(0): VRes, VSyncStart : 768, 768 (II) NVIDIA(0): VSyncEnd, VTotal : 770, 801 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: PixelClock (170.2 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "2048x1536": (II) NVIDIA(0): 2048 x 1536 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 388.040 MHz (II) NVIDIA(0): HRes, HSyncStart : 2048, 2216 (II) NVIDIA(0): HSyncEnd, HTotal : 2440, 2832 (II) NVIDIA(0): VRes, VSyncStart : 1536, 1537 (II) NVIDIA(0): VSyncEnd, VTotal : 1540, 1612 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (388.0 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 85 Hz (II) NVIDIA(0): Mode Source: X Server (II) NVIDIA(0): Pixel Clock : 194.020 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1108 (II) NVIDIA(0): HSyncEnd, HTotal : 1220, 1416 (II) NVIDIA(0): VRes, VSyncStart : 768, 768 (II) NVIDIA(0): VSyncEnd, VTotal : 770, 806 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Extra : DoubleScan (WW) NVIDIA(0): Mode is rejected: PixelClock (194.0 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x350": (II) NVIDIA(0): 640 x 350 @ 85 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 31.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 672 (II) NVIDIA(0): HSyncEnd, HTotal : 736, 832 (II) NVIDIA(0): VRes, VSyncStart : 350, 382 (II) NVIDIA(0): VSyncEnd, VTotal : 385, 445 (II) NVIDIA(0): H/V Polarity : +/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x400": (II) NVIDIA(0): 640 x 400 @ 85 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 31.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 672 (II) NVIDIA(0): HSyncEnd, HTotal : 736, 832 (II) NVIDIA(0): VRes, VSyncStart : 400, 401 (II) NVIDIA(0): VSyncEnd, VTotal : 404, 445 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "720x400": (II) NVIDIA(0): 720 x 400 @ 85 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 35.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 720, 756 (II) NVIDIA(0): HSyncEnd, HTotal : 828, 936 (II) NVIDIA(0): VRes, VSyncStart : 400, 401 (II) NVIDIA(0): VSyncEnd, VTotal : 404, 446 (II) NVIDIA(0): H/V Polarity : -/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x480": (II) NVIDIA(0): 640 x 480 @ 60 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 25.175 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 656 (II) NVIDIA(0): HSyncEnd, HTotal : 752, 800 (II) NVIDIA(0): VRes, VSyncStart : 480, 490 (II) NVIDIA(0): VSyncEnd, VTotal : 492, 525 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x480": (II) NVIDIA(0): 640 x 480 @ 73 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 31.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 664 (II) NVIDIA(0): HSyncEnd, HTotal : 704, 832 (II) NVIDIA(0): VRes, VSyncStart : 480, 489 (II) NVIDIA(0): VSyncEnd, VTotal : 492, 520 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x480": (II) NVIDIA(0): 640 x 480 @ 75 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 31.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 656 (II) NVIDIA(0): HSyncEnd, HTotal : 720, 840 (II) NVIDIA(0): VRes, VSyncStart : 480, 481 (II) NVIDIA(0): VSyncEnd, VTotal : 484, 500 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "640x480": (II) NVIDIA(0): 640 x 480 @ 85 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 36.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 640, 696 (II) NVIDIA(0): HSyncEnd, HTotal : 752, 832 (II) NVIDIA(0): VRes, VSyncStart : 480, 481 (II) NVIDIA(0): VSyncEnd, VTotal : 484, 509 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 56 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 36.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 824 (II) NVIDIA(0): HSyncEnd, HTotal : 896, 1024 (II) NVIDIA(0): VRes, VSyncStart : 600, 601 (II) NVIDIA(0): VSyncEnd, VTotal : 603, 625 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 60 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 40.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 840 (II) NVIDIA(0): HSyncEnd, HTotal : 968, 1056 (II) NVIDIA(0): VRes, VSyncStart : 600, 601 (II) NVIDIA(0): VSyncEnd, VTotal : 605, 628 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 72 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 50.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 856 (II) NVIDIA(0): HSyncEnd, HTotal : 976, 1040 (II) NVIDIA(0): VRes, VSyncStart : 600, 637 (II) NVIDIA(0): VSyncEnd, VTotal : 643, 666 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 75 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 49.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 816 (II) NVIDIA(0): HSyncEnd, HTotal : 896, 1056 (II) NVIDIA(0): VRes, VSyncStart : 600, 601 (II) NVIDIA(0): VSyncEnd, VTotal : 604, 625 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "800x600": (II) NVIDIA(0): 800 x 600 @ 85 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 56.300 MHz (II) NVIDIA(0): HRes, HSyncStart : 800, 832 (II) NVIDIA(0): HSyncEnd, HTotal : 896, 1048 (II) NVIDIA(0): VRes, VSyncStart : 600, 601 (II) NVIDIA(0): VSyncEnd, VTotal : 604, 631 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 87 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 44.900 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1032 (II) NVIDIA(0): HSyncEnd, HTotal : 1208, 1264 (II) NVIDIA(0): VRes, VSyncStart : 768, 768 (II) NVIDIA(0): VSyncEnd, VTotal : 776, 817 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Extra : Interlace (WW) NVIDIA(0): Mode is rejected: VertRefresh (87.0 Hz) out of range (WW) NVIDIA(0): (50.000-85.000 Hz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 60 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 65.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1048 (II) NVIDIA(0): HSyncEnd, HTotal : 1184, 1344 (II) NVIDIA(0): VRes, VSyncStart : 768, 771 (II) NVIDIA(0): VSyncEnd, VTotal : 777, 806 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 70 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 75.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1048 (II) NVIDIA(0): HSyncEnd, HTotal : 1184, 1328 (II) NVIDIA(0): VRes, VSyncStart : 768, 771 (II) NVIDIA(0): VSyncEnd, VTotal : 777, 806 (II) NVIDIA(0): H/V Polarity : -/- (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 75 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 78.750 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1040 (II) NVIDIA(0): HSyncEnd, HTotal : 1136, 1312 (II) NVIDIA(0): VRes, VSyncStart : 768, 769 (II) NVIDIA(0): VSyncEnd, VTotal : 772, 800 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1024x768": (II) NVIDIA(0): 1024 x 768 @ 85 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 94.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 1024, 1072 (II) NVIDIA(0): HSyncEnd, HTotal : 1168, 1376 (II) NVIDIA(0): VRes, VSyncStart : 768, 769 (II) NVIDIA(0): VSyncEnd, VTotal : 772, 808 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1152x864": (II) NVIDIA(0): 1152 x 864 @ 75 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 108.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1152, 1216 (II) NVIDIA(0): HSyncEnd, HTotal : 1344, 1600 (II) NVIDIA(0): VRes, VSyncStart : 864, 865 (II) NVIDIA(0): VSyncEnd, VTotal : 868, 900 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1280x960": (II) NVIDIA(0): 1280 x 960 @ 60 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 108.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1280, 1376 (II) NVIDIA(0): HSyncEnd, HTotal : 1488, 1800 (II) NVIDIA(0): VRes, VSyncStart : 960, 961 (II) NVIDIA(0): VSyncEnd, VTotal : 964, 1000 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1280x960": (II) NVIDIA(0): 1280 x 960 @ 85 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 148.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 1280, 1344 (II) NVIDIA(0): HSyncEnd, HTotal : 1504, 1728 (II) NVIDIA(0): VRes, VSyncStart : 960, 961 (II) NVIDIA(0): VSyncEnd, VTotal : 964, 1011 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: HorizSync (85.9 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1280x1024": (II) NVIDIA(0): 1280 x 1024 @ 60 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 108.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1280, 1328 (II) NVIDIA(0): HSyncEnd, HTotal : 1440, 1688 (II) NVIDIA(0): VRes, VSyncStart : 1024, 1025 (II) NVIDIA(0): VSyncEnd, VTotal : 1028, 1066 (II) NVIDIA(0): H/V Polarity : +/+ (II) NVIDIA(0): Mode is valid. (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1280x1024": (II) NVIDIA(0): 1280 x 1024 @ 75 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 135.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1280, 1296 (II) NVIDIA(0): HSyncEnd, HTotal : 1440, 1688 (II) NVIDIA(0): VRes, VSyncStart : 1024, 1025 (II) NVIDIA(0): VSyncEnd, VTotal : 1028, 1066 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: HorizSync (80.0 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1280x1024": (II) NVIDIA(0): 1280 x 1024 @ 85 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 157.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 1280, 1344 (II) NVIDIA(0): HSyncEnd, HTotal : 1504, 1728 (II) NVIDIA(0): VRes, VSyncStart : 1024, 1025 (II) NVIDIA(0): VSyncEnd, VTotal : 1028, 1072 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (157.5 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1600x1200": (II) NVIDIA(0): 1600 x 1200 @ 60 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 162.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1600, 1664 (II) NVIDIA(0): HSyncEnd, HTotal : 1856, 2160 (II) NVIDIA(0): VRes, VSyncStart : 1200, 1201 (II) NVIDIA(0): VSyncEnd, VTotal : 1204, 1250 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: HorizSync (75.0 kHz) out of range (WW) NVIDIA(0): (31.000-70.000 kHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1600x1200": (II) NVIDIA(0): 1600 x 1200 @ 65 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 175.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 1600, 1664 (II) NVIDIA(0): HSyncEnd, HTotal : 1856, 2160 (II) NVIDIA(0): VRes, VSyncStart : 1200, 1201 (II) NVIDIA(0): VSyncEnd, VTotal : 1204, 1250 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (175.5 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1600x1200": (II) NVIDIA(0): 1600 x 1200 @ 70 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 189.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1600, 1664 (II) NVIDIA(0): HSyncEnd, HTotal : 1856, 2160 (II) NVIDIA(0): VRes, VSyncStart : 1200, 1201 (II) NVIDIA(0): VSyncEnd, VTotal : 1204, 1250 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (189.0 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1600x1200": (II) NVIDIA(0): 1600 x 1200 @ 75 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 202.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 1600, 1664 (II) NVIDIA(0): HSyncEnd, HTotal : 1856, 2160 (II) NVIDIA(0): VRes, VSyncStart : 1200, 1201 (II) NVIDIA(0): VSyncEnd, VTotal : 1204, 1250 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (202.5 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1600x1200": (II) NVIDIA(0): 1600 x 1200 @ 85 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 229.500 MHz (II) NVIDIA(0): HRes, HSyncStart : 1600, 1664 (II) NVIDIA(0): HSyncEnd, HTotal : 1856, 2160 (II) NVIDIA(0): VRes, VSyncStart : 1200, 1201 (II) NVIDIA(0): VSyncEnd, VTotal : 1204, 1250 (II) NVIDIA(0): H/V Polarity : +/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (229.5 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1792x1344": (II) NVIDIA(0): 1792 x 1344 @ 60 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 204.800 MHz (II) NVIDIA(0): HRes, HSyncStart : 1792, 1920 (II) NVIDIA(0): HSyncEnd, HTotal : 2120, 2448 (II) NVIDIA(0): VRes, VSyncStart : 1344, 1345 (II) NVIDIA(0): VSyncEnd, VTotal : 1348, 1394 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (204.8 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1792x1344": (II) NVIDIA(0): 1792 x 1344 @ 75 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 261.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1792, 1888 (II) NVIDIA(0): HSyncEnd, HTotal : 2104, 2456 (II) NVIDIA(0): VRes, VSyncStart : 1344, 1345 (II) NVIDIA(0): VSyncEnd, VTotal : 1348, 1417 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (261.0 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1856x1392": (II) NVIDIA(0): 1856 x 1392 @ 60 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 218.300 MHz (II) NVIDIA(0): HRes, HSyncStart : 1856, 1952 (II) NVIDIA(0): HSyncEnd, HTotal : 2176, 2528 (II) NVIDIA(0): VRes, VSyncStart : 1392, 1393 (II) NVIDIA(0): VSyncEnd, VTotal : 1396, 1439 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (218.3 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1856x1392": (II) NVIDIA(0): 1856 x 1392 @ 75 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 288.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1856, 1984 (II) NVIDIA(0): HSyncEnd, HTotal : 2208, 2560 (II) NVIDIA(0): VRes, VSyncStart : 1392, 1393 (II) NVIDIA(0): VSyncEnd, VTotal : 1396, 1500 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (288.0 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1920x1440": (II) NVIDIA(0): 1920 x 1440 @ 60 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 234.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1920, 2048 (II) NVIDIA(0): HSyncEnd, HTotal : 2256, 2600 (II) NVIDIA(0): VRes, VSyncStart : 1440, 1441 (II) NVIDIA(0): VSyncEnd, VTotal : 1444, 1500 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (234.0 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): Validating Mode "1920x1440": (II) NVIDIA(0): 1920 x 1440 @ 75 Hz (II) NVIDIA(0): Mode Source: VESA (II) NVIDIA(0): Pixel Clock : 297.000 MHz (II) NVIDIA(0): HRes, HSyncStart : 1920, 2064 (II) NVIDIA(0): HSyncEnd, HTotal : 2288, 2640 (II) NVIDIA(0): VRes, VSyncStart : 1440, 1441 (II) NVIDIA(0): VSyncEnd, VTotal : 1444, 1500 (II) NVIDIA(0): H/V Polarity : -/+ (WW) NVIDIA(0): Mode is rejected: PixelClock (297.0 MHz) too high for (WW) NVIDIA(0): Display Device (Max: 155.0 MHz). (II) NVIDIA(0): (II) NVIDIA(0): --- Done building ModePool for DFP-0 --- (II) NVIDIA(0): (II) NVIDIA(0): (II) NVIDIA(0): --- Modes in ModePool for DFP-0 --- (II) NVIDIA(0): "nvidia-auto-select" : 1024 x 768 @ 85.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "1920x1080" : 1920 x 1080 @ 59.9 Hz (from: X Configuration file ModeLine) (II) NVIDIA(0): "1920x1080_60" : 1920 x 1080 @ 59.9 Hz (from: X Configuration file ModeLine) (II) NVIDIA(0): "1600x1024" : 1600 x 1024 @ 60.0 Hz (from: X Server) (II) NVIDIA(0): "1600x1024_60" : 1600 x 1024 @ 60.0 Hz (from: X Server) (II) NVIDIA(0): "1400x1050" : 1400 x 1050 @ 60.0 Hz (from: X Server) (II) NVIDIA(0): "1400x1050_60" : 1400 x 1050 @ 60.0 Hz (from: X Server) (II) NVIDIA(0): "1280x1024" : 1280 x 1024 @ 60.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "1280x1024_60" : 1280 x 1024 @ 60.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "1280x960" : 1280 x 960 @ 60.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "1280x960_60" : 1280 x 960 @ 60.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "1152x864" : 1152 x 864 @ 75.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "1152x864_75" : 1152 x 864 @ 75.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "1152x768" : 1152 x 768 @ 54.8 Hz (from: X Server) (II) NVIDIA(0): "1152x768_55" : 1152 x 768 @ 54.8 Hz (from: X Server) (II) NVIDIA(0): "1024x768" : 1024 x 768 @ 85.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "1024x768_85" : 1024 x 768 @ 85.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "1024x768_75" : 1024 x 768 @ 75.0 Hz (from: VESA) (II) NVIDIA(0): "1024x768_70" : 1024 x 768 @ 70.1 Hz (from: X Server, VESA) (II) NVIDIA(0): "1024x768_60" : 1024 x 768 @ 60.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "832x624" : 832 x 624 @ 74.6 Hz (from: X Server) (II) NVIDIA(0): "832x624_75" : 832 x 624 @ 74.6 Hz (from: X Server) (II) NVIDIA(0): "800x600" : 800 x 600 @ 85.1 Hz (from: X Server, VESA) (II) NVIDIA(0): "800x600_85" : 800 x 600 @ 85.1 Hz (from: X Server, VESA) (II) NVIDIA(0): "800x600_75" : 800 x 600 @ 75.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "800x600_72" : 800 x 600 @ 72.2 Hz (from: X Server, VESA) (II) NVIDIA(0): "800x600_60" : 800 x 600 @ 60.3 Hz (from: X Server, VESA) (II) NVIDIA(0): "800x600_56" : 800 x 600 @ 56.2 Hz (from: X Server, VESA) (II) NVIDIA(0): "800x512" : 800 x 512 @ 60.1 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "800x512d60" : 800 x 512 @ 60.1 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "720x400" : 720 x 400 @ 85.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "720x400_85" : 720 x 400 @ 85.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "640x512" : 640 x 512 @ 60.0 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "640x512d60" : 640 x 512 @ 60.0 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "640x480" : 640 x 480 @ 60.0 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "640x480d60" : 640 x 480 @ 60.0 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "640x480_85" : 640 x 480 @ 85.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "640x480_75" : 640 x 480 @ 75.0 Hz (from: X Server, VESA) (II) NVIDIA(0): "640x480_73" : 640 x 480 @ 72.8 Hz (from: VESA) (II) NVIDIA(0): "640x480_60" : 640 x 480 @ 59.9 Hz (from: VESA) (II) NVIDIA(0): "640x400" : 640 x 400 @ 85.1 Hz (from: X Server, VESA) (II) NVIDIA(0): "640x400_85" : 640 x 400 @ 85.1 Hz (from: X Server, VESA) (II) NVIDIA(0): "640x350" : 640 x 350 @ 85.1 Hz (from: X Server, VESA) (II) NVIDIA(0): "640x350_85" : 640 x 350 @ 85.1 Hz (from: X Server, VESA) (II) NVIDIA(0): "576x432" : 576 x 432 @ 75.0 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "576x432d75" : 576 x 432 @ 75.0 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "576x384" : 576 x 384 @ 54.8 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "576x384d55" : 576 x 384 @ 54.8 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "512x384" : 512 x 384 @ 85.0 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "512x384d85" : 512 x 384 @ 85.0 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "512x384d75" : 512 x 384 @ 75.1 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "512x384d70" : 512 x 384 @ 70.1 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "512x384d60" : 512 x 384 @ 60.0 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "416x312" : 416 x 312 @ 74.7 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "416x312d75" : 416 x 312 @ 74.7 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "400x300" : 400 x 300 @ 85.3 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "400x300d85" : 400 x 300 @ 85.3 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "400x300d75" : 400 x 300 @ 75.1 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "400x300d72" : 400 x 300 @ 72.2 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "400x300d60" : 400 x 300 @ 60.3 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "400x300d56" : 400 x 300 @ 56.3 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "360x200" : 360 x 200 @ 85.0 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "360x200d85" : 360 x 200 @ 85.0 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "320x240" : 320 x 240 @ 85.2 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "320x240d85" : 320 x 240 @ 85.2 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "320x240d75" : 320 x 240 @ 75.0 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "320x240d73" : 320 x 240 @ 72.8 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "320x240d60" : 320 x 240 @ 60.1 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "320x200" : 320 x 200 @ 85.3 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "320x200d85" : 320 x 200 @ 85.3 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "320x175" : 320 x 175 @ 85.3 Hz DoubleScan (from: X Server) (II) NVIDIA(0): "320x175d85" : 320 x 175 @ 85.3 Hz DoubleScan (from: X Server) (II) NVIDIA(0): --- End of ModePool for DFP-0: --- (II) NVIDIA(0): (II) NVIDIA(0): Assigned Display Device: DFP-0 (II) NVIDIA(0): Using MetaMode string: "1920x1080 +0+0; 1024x768 +0+0; 800x600 (II) NVIDIA(0): +0+0; 640x480 +0+0" (II) NVIDIA(0): Requested modes: (II) NVIDIA(0): "1920x1080+0+0" (II) NVIDIA(0): "1024x768+0+0" (II) NVIDIA(0): "800x600+0+0" (II) NVIDIA(0): "640x480+0+0" (II) NVIDIA(0): Validated modes: (II) NVIDIA(0): MetaMode "1920x1080+0+0": (II) NVIDIA(0): Bounding Box: [0, 0, 1920, 1080] (II) NVIDIA(0): DFP-0: "1920x1080" (II) NVIDIA(0): Size : 1920 x 1080 (II) NVIDIA(0): Offset : +0 +0 (II) NVIDIA(0): Panning Domain: @ 1920 x 1080 (II) NVIDIA(0): Position : [0, 0, 1920, 1080] (II) NVIDIA(0): MetaMode "1024x768+0+0": (II) NVIDIA(0): Bounding Box: [0, 0, 1024, 768] (II) NVIDIA(0): DFP-0: "1024x768" (II) NVIDIA(0): Size : 1024 x 768 (II) NVIDIA(0): Offset : +0 +0 (II) NVIDIA(0): Panning Domain: @ 1024 x 768 (II) NVIDIA(0): Position : [0, 0, 1024, 768] (II) NVIDIA(0): MetaMode "800x600+0+0": (II) NVIDIA(0): Bounding Box: [0, 0, 800, 600] (II) NVIDIA(0): DFP-0: "800x600" (II) NVIDIA(0): Size : 800 x 600 (II) NVIDIA(0): Offset : +0 +0 (II) NVIDIA(0): Panning Domain: @ 800 x 600 (II) NVIDIA(0): Position : [0, 0, 800, 600] (II) NVIDIA(0): MetaMode "640x480+0+0": (II) NVIDIA(0): Bounding Box: [0, 0, 640, 480] (II) NVIDIA(0): DFP-0: "640x480" (II) NVIDIA(0): Size : 640 x 480 (II) NVIDIA(0): Offset : +0 +0 (II) NVIDIA(0): Panning Domain: @ 640 x 480 (II) NVIDIA(0): Position : [0, 0, 640, 480] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080 (II) NVIDIA(0): (II) NVIDIA(0): Implicitly adding the following modes to X Screen 0 (these (II) NVIDIA(0): will be available via XRandR and XF86VidMode): (II) NVIDIA(0): (II) NVIDIA(0): "1600x1024" : 1600 x 1024 @ 60.0 Hz (II) NVIDIA(0): "1400x1050" : 1400 x 1050 @ 60.0 Hz (II) NVIDIA(0): "1280x1024" : 1280 x 1024 @ 60.0 Hz (II) NVIDIA(0): "1280x960" : 1280 x 960 @ 60.0 Hz (II) NVIDIA(0): "1152x864" : 1152 x 864 @ 75.0 Hz (II) NVIDIA(0): "1152x768" : 1152 x 768 @ 54.8 Hz (II) NVIDIA(0): "1024x768_75" : 1024 x 768 @ 75.0 Hz (II) NVIDIA(0): "1024x768_70" : 1024 x 768 @ 70.1 Hz (II) NVIDIA(0): "1024x768_60" : 1024 x 768 @ 60.0 Hz (II) NVIDIA(0): "832x624" : 832 x 624 @ 74.6 Hz (II) NVIDIA(0): "800x600_75" : 800 x 600 @ 75.0 Hz (II) NVIDIA(0): "800x600_72" : 800 x 600 @ 72.2 Hz (II) NVIDIA(0): "800x600_60" : 800 x 600 @ 60.3 Hz (II) NVIDIA(0): "800x600_56" : 800 x 600 @ 56.2 Hz (II) NVIDIA(0): "800x512" : 800 x 512 @ 60.1 Hz DoubleScan (II) NVIDIA(0): "720x400" : 720 x 400 @ 85.0 Hz (II) NVIDIA(0): "640x512" : 640 x 512 @ 60.0 Hz DoubleScan (II) NVIDIA(0): "640x480_85" : 640 x 480 @ 85.0 Hz (II) NVIDIA(0): "640x480_75" : 640 x 480 @ 75.0 Hz (II) NVIDIA(0): "640x480_73" : 640 x 480 @ 72.8 Hz (II) NVIDIA(0): "640x480_60" : 640 x 480 @ 59.9 Hz (II) NVIDIA(0): "640x400" : 640 x 400 @ 85.1 Hz (II) NVIDIA(0): "640x350" : 640 x 350 @ 85.1 Hz (II) NVIDIA(0): "576x432" : 576 x 432 @ 75.0 Hz DoubleScan (II) NVIDIA(0): "576x384" : 576 x 384 @ 54.8 Hz DoubleScan (II) NVIDIA(0): "512x384" : 512 x 384 @ 85.0 Hz DoubleScan (II) NVIDIA(0): "512x384d75" : 512 x 384 @ 75.1 Hz DoubleScan (II) NVIDIA(0): "512x384d70" : 512 x 384 @ 70.1 Hz DoubleScan (II) NVIDIA(0): "512x384d60" : 512 x 384 @ 60.0 Hz DoubleScan (II) NVIDIA(0): "416x312" : 416 x 312 @ 74.7 Hz DoubleScan (II) NVIDIA(0): "400x300" : 400 x 300 @ 85.3 Hz DoubleScan (II) NVIDIA(0): "400x300d75" : 400 x 300 @ 75.1 Hz DoubleScan (II) NVIDIA(0): "400x300d72" : 400 x 300 @ 72.2 Hz DoubleScan (II) NVIDIA(0): "400x300d60" : 400 x 300 @ 60.3 Hz DoubleScan (II) NVIDIA(0): "400x300d56" : 400 x 300 @ 56.3 Hz DoubleScan (II) NVIDIA(0): "360x200" : 360 x 200 @ 85.0 Hz DoubleScan (II) NVIDIA(0): "320x240" : 320 x 240 @ 85.2 Hz DoubleScan (II) NVIDIA(0): "320x240d75" : 320 x 240 @ 75.0 Hz DoubleScan (II) NVIDIA(0): "320x240d73" : 320 x 240 @ 72.8 Hz DoubleScan (II) NVIDIA(0): "320x240d60" : 320 x 240 @ 60.1 Hz DoubleScan (II) NVIDIA(0): "320x200" : 320 x 200 @ 85.3 Hz DoubleScan (II) NVIDIA(0): "320x175" : 320 x 175 @ 85.3 Hz DoubleScan (II) NVIDIA(0): (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default (==) NVIDIA(0): Disabling 32-bit ARGB GLX visuals. (--) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xf5005000 - 0xf5005fff (0x1000) MX[B] [6] -1 0 0xf5004000 - 0xf5004fff (0x1000) MX[B] [7] -1 0 0xf5000000 - 0xf5003fff (0x4000) MX[B] [8] -1 0 0xf5006000 - 0xf50060ff (0x100) MX[B] [9] -1 0 0xf5007000 - 0xf5007fff (0x1000) MX[B] [10] -1 0 0xf3000000 - 0xf3ffffff (0x1000000) MX[B](B) [11] -1 0 0xe0000000 - 0xefffffff (0x10000000) MX[B](B) [12] -1 0 0xf2000000 - 0xf2ffffff (0x1000000) MX[B](B) [13] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [14] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [15] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [16] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [17] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [18] -1 0 0x0000e000 - 0x0000e00f (0x10) IX[B] [19] -1 0 0x00000b70 - 0x00000b73 (0x4) IX[B] [20] -1 0 0x00000970 - 0x00000977 (0x8) IX[B] [21] -1 0 0x00000bf0 - 0x00000bf3 (0x4) IX[B] [22] -1 0 0x000009f0 - 0x000009f7 (0x8) IX[B] [23] -1 0 0x0000cc00 - 0x0000cc07 (0x8) IX[B] [24] -1 0 0x0000f000 - 0x0000f00f (0x10) IX[B] [25] -1 0 0x0000c800 - 0x0000c83f (0x40) IX[B] [26] -1 0 0x00001c00 - 0x00001c3f (0x40) IX[B] [27] -1 0 0x0000c000 - 0x0000c03f (0x40) IX[B] [28] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [29] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) NVIDIA(0): Initialized GPU GART. (II) NVIDIA(0): kernel module enabled successfully (II) NVIDIA(0): GPU initialized (II) NVIDIA(0): Created acpid client socket 13. (II) NVIDIA(0): Interrupts enabled (II) NVIDIA(0): Setting mode "1920x1080+0+0" (II) NVIDIA(0): First mode initialized (II) NVIDIA(0): Using built-in logo image. (II) NVIDIA(0): Logo is 744x537 with depth 24. (II) Loading extension NV-GLX (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized (II) NVIDIA(0): Visuals set up (II) NVIDIA(0): Pixmap depths set up (II) NVIDIA(0): GLX visuals set up (II) NVIDIA(0): Framebuffer set up (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture (==) NVIDIA(0): Backing store disabled (==) NVIDIA(0): Silken mouse enabled (II) NVIDIA(0): Default colormap initialized. (II) NVIDIA(0): Palette loaded (II) Loading extension NV-CONTROL (WW) NVIDIA(0): Option "noedidDFPmaxsizecheck" is not used (II) NVIDIA(0): Screen initialization complete (==) RandR enabled (II) Setting vga for screen 0. (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE (II) Initializing extension GLX (**) Option "Protocol" "auto" (**) Mouse0: Device: "/dev/input/mice" (**) Mouse0: Protocol: "auto" (**) Option "CorePointer" (**) Mouse0: Core Pointer (**) Option "Device" "/dev/input/mice" (**) Option "Emulate3Buttons" "no" (**) Option "ZAxisMapping" "4 5" (**) Mouse0: ZAxisMapping: buttons 4 and 5 (**) Mouse0: Buttons: 5 (**) Option "CoreKeyboard" (**) Keyboard0: Core Keyboard (**) Option "Protocol" "standard" (**) Keyboard0: Protocol: standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xorg" (**) Keyboard0: XkbRules: "xorg" (**) Option "XkbModel" "pc105" (**) Keyboard0: XkbModel: "pc105" (**) Option "XkbLayout" "us" (**) Keyboard0: XkbLayout: "us" (**) Option "CustomKeycodes" "off" (**) Keyboard0: CustomKeycodes disabled (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD) (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) (**) Option "Device" "/dev/input/mice" (--) Mouse0: PnP-detected protocol: "ExplorerPS/2" (II) Mouse0: ps2EnableDataReporting: succeeded Could not init font path element /usr/X11R6/lib/X11/fonts/Type1/, removing from list! AUDIT: Fri Feb 15 17:03:37 2008: 6090 X: client 5 rejected from local host

5 4

How can I write Startup script...
by Tolun ARDAHANLI 18 Feb '08

18 Feb '08

Hi everybody; I want to know that how can I write a start-up script for Centos 5.1? Thanks a lot... sincerely yours... -- Tolun ARDAHANLI Bilgisayar Muhendisi E-posta:tolun.ardahanli@linux.org.tr Icq:326600 ---------------------------------------------------------------------------- Tolun ARDAHANLI Computer Engineer E-mail:tolun.ardahanli@linux.org.tr Icq:326600

2 1

What Fedora Version (for Repo use)
by Chris 18 Feb '08

18 Feb '08

What Fedora version equates to Cent 5? I would like to use the Fedora repos (if possible). Please advise. TIA -- Best regards, Chris bugs in the RAID

5 4

Network configuration question
by Niki Kovacs 18 Feb '08

18 Feb '08

Hi, My wife and I live in a two-storey flat, and we have a small home LAN (100% CentOS 5) with a "classical" configuration: On the ground floor, there is the telephone jack with the DSL modem router (192.168.1.254). This modem has a mini-switch with two Ethernet jacks to it, and the two are used by: - the server (192.168.1.1), a "black box" running in a cupboard 24/7 - the wireless AP (192.168.1.253) Then, on the first floor, everything is connected by wireless, and for the moment, configured statically: - my desktop PC (192.168.1.2) - my laptop (192.168.1.3) - my wife's laptop (192.168.1.4) I have an older laptop here, a Fujitsu Siemens Amilo D, that I'd like to use as a simple build box. It's physically installed next to my desktop PC. It doesn't have a wireless card, so I vaguely thought: is it somehow possible to connect this laptop with an Ethernet cable to my desktop PC's unused Ethernet card, and then connect it to the internet? In that case, I wonder if I have to bridge the desktop PC's network interfaces (wlan0 and eth0). That said, I don't even know if the driver for wlan0 (rt61) allows any bridging. Or maybe simply configure a different subnet, but then, what would the network configuration look like on the laptop and on the desktop PC? Any suggestions for that? Cheers, Niki

4 4

how to find it?
by Sobari Tanuwijaya 17 Feb '08

17 Feb '08

Dear All, How to find out that a certain lib place on which package? I prompted that a certain library is not exists on my system, but I don't know which package should I look for to install. Thanks. -- Tanu --

2 1

Re: [CentOS] Network configuration question
by David G. Miller 17 Feb '08

17 Feb '08

Niki Kovacs <contact(a)kikinovak.net> wrote: > I have an older laptop here, a Fujitsu Siemens Amilo D, that I'd like to > use as a simple build box. It's physically installed next to my desktop > PC. It doesn't have a wireless card, so I vaguely thought: is it somehow > possible to connect this laptop with an Ethernet cable to my desktop > PC's unused Ethernet card, and then connect it to the internet? In that > case, I wonder if I have to bridge the desktop PC's network interfaces > (wlan0 and eth0). That said, I don't even know if the driver for wlan0 > (rt61) allows any bridging. Or maybe simply configure a different > subnet, but then, what would the network configuration look like on the > laptop and on the desktop PC? You need what's called a crossover cable between the laptop and your desktop. Think of a crossover cable as being like a "null modem" built into the cable for networking. The tx wire at one end becomes the rx wire at the other for all wires in the cable. This will allow the two systems to "talk". The laptop's LAN settings should be set to have your desktop as it's gateway and I think you'll need to manually add a host route on the desktop for the laptop using the wired NIC as the interface. You'll have to Google or get more advice from the list if you want to have the laptop be able to get onto the internet. It should be possible to set up your desktop to route packets from the laptop through your wireless LAN. I just don't know how. If you can't get the wireless NIC to bridge with the regular NIC, it should be possible to do something with iptables rules to just forward packets that aren't for the desktop to your wireless modem/router. If you're trying to get this done over the weekend, respond to me directly if you have any questions. I get the CentOS list as a digest so I won't see any other questions until Monday. Cheers, Dave -- Politics, n. Strife of interests masquerading as a contest of principles. -- Ambrose Bierce

2 1

CentOS-announce Digest, Vol 36, Issue 8
by centos-announce-request＠centos.org 17 Feb '08

17 Feb '08

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CEBA-2008:0148 CentOS 5 x86_64 thunderbird Update (Karanbir Singh) 2. CEBA-2008:0148 CentOS 5 i386 thunderbird Update (Karanbir Singh) ---------------------------------------------------------------------- Message: 1 Date: Sat, 16 Feb 2008 14:31:00 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CEBA-2008:0148 CentOS 5 x86_64 thunderbird Update To: centos-announce(a)centos.org Message-ID: <20080216143100.GA5009(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2008:0148 Upstream details at : https://rhn.redhat.com/errata/RHBA-2008-0148.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 485802e57ae66eb6bfab52ed329bf39d thunderbird-1.5.0.12-9.el5.centos.x86_64.rpm Source: f63ab0ac6539a38cd2b06459e2412929 thunderbird-1.5.0.12-9.el5.centos.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ Message: 2 Date: Sat, 16 Feb 2008 14:31:00 +0000 From: Karanbir Singh <kbsingh(a)centos.org> Subject: [CentOS-announce] CEBA-2008:0148 CentOS 5 i386 thunderbird Update To: centos-announce(a)centos.org Message-ID: <20080216143100.GA4995(a)base.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2008:0148 Upstream details at : https://rhn.redhat.com/errata/RHBA-2008-0148.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: a6a38fc5bd2caaa1478097558fd61da2 thunderbird-1.5.0.12-9.el5.centos.i386.rpm Source: f63ab0ac6539a38cd2b06459e2412929 thunderbird-1.5.0.12-9.el5.centos.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos(a)irc.freenode.net ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 36, Issue 8 **********************************************

1 0

Gettiing the latest Firefox and Thunderbird for CentOS 5.1
by Edward Diener 17 Feb '08

17 Feb '08

Is there any 3rd party repository for which I can get the latest versions of Firefox and Thunderbird for CentOS 5.1 and install them using yum ?

4 4

Support Tools
by Thorsten Kampe 16 Feb '08

16 Feb '08

Hi, does something like the SUSE/Novell ntsutils (previously called "supportconfig") or Microsoft's MPS Reports exist for CentOS or Red Hat Enterprise Linux? I mean a program that reads and exports various configurations and parameters to facilitate technical support. Thorsten

3 4

New kernel (2.6.18-53.1.13) generates "unknown attribute" errors during boot
by MHR 16 Feb '08

16 Feb '08

I've seen this now a few times, but of course I didn't write them down, so I may have the wording a little off. The new kernel seems to contain something in udevd that is now generating a whole slew of unknown attribute(or something like that) errors during the boot, before the part where dmesg picks up. They don't seem to be causing any actual problems while the system is up and running, but.... Anyone know anything about this (and what)? Curious. mhr

2 2

problems with iscsiadm
by Maysara A. Abdulhaq 16 Feb '08

16 Feb '08

Hello, I'm fairly new to centos and to iscsi, I have installed a fresh copy of centos (CentOS release 5 (Final)) and installed iscsi-initator-utils, iscsiadm -V shows iscsiadm version 2.0-865 . when i try to connect to iscsi target it doesnt work ... it just stays idle , i try something like: iscsiadm -m discovery -t st -p 172.20.2.76 show or with -m node .... --login ...etc, none works. using the same configuration on ubuntu gutsy, same version things work! i also made both /etc/iscsi/iscsid.conf identical ... no luck :( i did tcpdump too (-vv -n ) and then grep the ip of the iscsi target, i see no traffic to the iscsi target at all on the centos machine, i tried it on the other machine it works :S Is there anything else to check? firewalls are all shutdown on all nodes ... i tried switching ips too .. any hint is greatly valued, thank you -- Maysara A. A.

1 1

Hardened PHP? Suhosin patch?
by Niki Kovacs 16 Feb '08

16 Feb '08

Hi, I'm running a few PHP-based apps on our server (PMB, SPIP, Joomla, PHPMyAdmin), and I'm not always comforted about security. I don't know the details, but many a security expert frowns when it comes to PHP. Now I just stumbled over this: http://www.hardened-php.net/suhosin.127.html Has anyone already tried this out? An opinion about it? Is it worth it? Since I have to rebuild PHP anyway (because I need some specific modules that can only be obtained by rebuilding it), it wouldn't be much of a hassle. But I'm curious about the experts' opinion here. Cheers, Niki

4 6

system-config-display problem
by Anne Wilson 16 Feb '08

16 Feb '08

I bought a Viewsonic VG730m monitor, analogue and digital. With a digital cable connected the screen keeps blanking for a second or so. system-config-display shows it configured as a CRT monitor, and refuses to accept that it is an LCD monitor. I've tried manually editing xorg.conf, putting in the manufacturer's values for horizontal and vertical refresh, but the problem remains. The Viewsonic website has lots of information for windows and some for mac, but nothing for linux. I need either to find how to make system-config-display keep the setting I'm giving it or to know what entry to put into xorg.conf to make it understand that it is an LCD display. Sorry if this sounds naive, but I've not had a digital monitor before. I could go back to using the analogue connection, which gave no problems, but you'll understand that I'm reluctant to do that. Anne

1 0

Re: [CentOS] Resize Logical Volume
by Max Hetrick 15 Feb '08

15 Feb '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ivan Arteaga wrote: > I tried the commands you sent me and i can extend the size to the new > value but can´t resize the file system: > [root@mail ~]# lvextend -L+30G /dev/VolGroup00/LogVol00 > Extending logical volume LogVol00 to 88.59 GB > Logical volume LogVol00 successfully resized > [root@mail ~]# resize2fs /dev/VolGroup00/LogVol00 > resize2fs 1.35 (28-Feb-2004) > /dev/VolGroup00/LogVol00 is mounted; can't resize a mounted filesystem! > [root@mail ~]# df -kh > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/VolGroup00-LogVol00 > 58G 49G 5.8G 90% / > /dev/sda1 99M 33M 62M 35% /boot > /dev/mapper/VolGroup00-LogVol03 > 20G 9.7G 8.6G 53% /cose > none 1013M 0 1013M 0% /dev/shm > [root@mail ~]# umount /dev/VolGroup00/LogVol00 > umount: /: device is busy > How can i umount the / filesystem? Boot CentOS using the install CD and type linux rescue. You can run the command there when / is unmounted. Don't mount the partitions if it asks you to. Max -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFHtgz7IXSX/6LmsXkRAgx4AJ9D807fOmixl2Jh848K2qp3WL5+VQCfXMvw rd2soCNIfbtYGBMkmoEP0bE= =IUvb -----END PGP SIGNATURE-----

1 0

OFF Topic: mysql installation problem
by Ed Morrison 15 Feb '08

15 Feb '08

Hi All: I'm trying to get mysql 5 installed on my CentOS 4.6 installation. I've installed mysql using yum: yum -y install perl-DBD-MySQL mysql-server mysql php-mysql mod_auth_mysql phpmyadmin mysqlclient Yum says it installed fine: Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package phpmyadmin.noarch 0:2.11.4-1.el4.rf set to be updated ---> Package perl-DBD-MySQL.x86_64 0:2.9004-3.1.centos4 set to be updated ---> Package php-mysql.x86_64 0:5.1.6-3.el4s1.8 set to be updated ---> Package mysql-server.x86_64 0:5.0.54-1.el4.centos set to be updated ---> Package mod_auth_mysql.x86_64 1:3.0.0-2.el4s1.3 set to be updated ---> Package mysql.x86_64 0:5.0.54-1.el4.centos set to be updated --> Running transaction check Dependencies Resolved ============================================================================= Package Arch Version Repository Size ============================================================================= Installing: mod_auth_mysql x86_64 1:3.0.0-2.el4s1.3 centosplus 22 k mysql x86_64 5.0.54-1.el4.centos centosplus 2.9 M mysql-server x86_64 5.0.54-1.el4.centos centosplus 10 M perl-DBD-MySQL x86_64 2.9004-3.1.centos4 base 112 k php-mysql x86_64 5.1.6-3.el4s1.8 centosplus 85 k phpmyadmin noarch 2.11.4-1.el4.rf dag 4.2 M Transaction Summary ============================================================================= Install 6 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 17 M Downloading Packages: Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing: mysql ######################### [1/6] Installing: php-mysql ######################### [2/6] Installing: perl-DBD-MySQL ######################### [3/6] Installing: phpmyadmin ######################### [4/6] Installing: mysql-server ######################### [5/6] Installing: mod_auth_mysql ######################### [6/6] Installed: mod_auth_mysql.x86_64 1:3.0.0-2.el4s1.3 mysql.x86_64 0:5.0.54-1.el4.centos mysql-server.x86_64 0:5.0.54-1.el4.centos perl-DBD-MySQL.x86_64 0:2.9004-3.1.centos4 php-mysql.x86_64 0:5.1.6-3.el4s1.8 phpmyadmin.noarch 0:2.11.4-1.el4.rf Complete! But there isn't a my.cnf file in /etc/ Nor are there any files in: [root@ftp ~]# ls /var/lib/mysql/ mysql test [root@ftp ~]# ls /var/lib/mysql/mysql/ An rpm query shows everything should be installed: [root@ftp ~]# rpm -qa mysql mysql-5.0.54-1.el4.centos [root@ftp ~]# rpm -qa mysql* mysqlclient14-4.1.22-1.el4s1.1 mysqlclient10-devel-3.23.58-9.2.c4 mysql-5.0.54-1.el4.centos mysqlclient10-3.23.58-4.RHEL4.1 mysql-server-5.0.54-1.el4.centos mysqlclient10-3.23.58-9.2.c4 mysql-libs-5.0.54-1.el4.centos Trying to start mysql results in: [root@ftp ~]# service mysqld start Timeout error occurred trying to start MySQL Daemon. Starting MySQL: [FAILED] Thoughts?

7 17

local root exploit
by Valent Turkovic 15 Feb '08

15 Feb '08

I saw that there is a local root exploit in the wild. http://blog.kagesenshi.org/2008/02/local-root-exploit-on-wild.html And I see my centos box still has: 2.6.18-53.1.4.el5 yum says there are no updates... am I safe? Valent.

17 37

Centos 5 and milter rpm's
by Tim Alberts 15 Feb '08

15 Feb '08

As I mentioned on this list before, I'm switching from Fedora 6 to Centos 5. I'm setting up the mail server and on Fedora I used the milter rpms for greylisting, spamassassin, mimedefant etc. However I don't see that those are included with Centos? Is this true, or do my yum repositories need to be changed to look in an 'extras' location? Or is there some other source for sendmail milter RPMS like on FC6?

2 1

Re: [CentOS] About postgresql tcpip connection
by Roilan Cardoso Sánchez 15 Feb '08

15 Feb '08

I add in pg_hba.conf host all all 192.168.0.0/24 ident sameuser I tryed to connect and it throw the same error ----- Mensaje original ---- De: Bill Campbell <centos(a)celestial.com> Para: centos(a)centos.org Enviado: viernes, 15 de febrero, 2008 12:28:44 Asunto: Re: [CentOS] About postgresql tcpip connection On Fri, Feb 15, 2008, Roilan Cardoso S?nchez wrote: > > hello everybody > > i´m trying to connect to my postgresql via tcpip and it thow an error > is not accepting tcp-ip connections > I ask to google but i dont find the solution, people said about the > prostgresql.conf enable tcpip, I try but when i start the service it > thow an error. > Other thing is add the option i to postmaster.opt but when i start the > service this file is redefined > > anybody can helpme You need to have the allowable networks specified in the postgresql pg_hba.conf file. Bill -- INTERNET: bill(a)celestial.com Bill Campbell; Celestial Software LLC URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 Cutting the space budget really restores my faith in humanity. It eliminates dreams, goals, and ideals and lets us get straight to the business of hate, debauchery, and self-annihilation. -- Johnny Hart _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos ______________________________________________ ¿Con Mascota por primera vez? Sé un mejor Amigo. Entra en Yahoo! Respuestas http://es.answers.yahoo.com/info/welcome

3 2

Modify kickstart initrd to add Buslogic driver
by Tom Brown 15 Feb '08

15 Feb '08

Hi I have a running kernel with the same kernel version of that in the kickstart that contains the Buslogic driver which would enable me to install a vmware client using kickstart. Is there an 'easy' way to take the initrd that contains the correct drivers and inject these into the initrd of the kickstart kernel? Or does anyone have a kickstart initrd available with the Buslogic drivers for an 2.6.9-55.ELsmp kernel? thanks Tom

1 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss