- Discuss - lists.centos.org

Re: [CentOS] error creating Centos 5.1 x32 dum_U instance on CentOS5.1 x64
by Ross S. W. Walker 01 Mar '08

01 Mar '08

Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on 64-bit dom0. Actually RHEL Xen is 3.1 with the brain damaged 3.0 userland utilities. -Ross ----- Original Message ----- From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> To: CentOS mailing list <centos(a)centos.org> Sent: Fri Feb 29 04:46:42 2008 Subject: Re: [CentOS] error creating Centos 5.1 x32 dum_U instance on CentOS5.1 x64 Rudi Ahlers wrote: > Hi all > > This is the first time I try and get Xen working, and want to install > a few CentOS 5.1 32bit and FreeBSD 6.1 VM's on my CentOS 5.1 x64 server. > > Trying to get the first one to install is rather trivial, and I keep > on running into errors. At fist I wanted to install it fro the cdrom, > so I used "virt-install --cdrom=/dev/hdc" It booted up, and I could > choose my language, but then got an error saying I don't have the > right driver for the cdrom install. Odd. > > So, I copied the whole CD to my intranet server, to try a HTTP > installation, which got much further, but fails as soon as it starts > copying the files to the xvda partition. > > Here's what I've done: > virt-install -p > --location=http://intranet/kickstart/centos/5.1/32/os/i386 --ram=512 > --file=/vm/vm03.img --name=vm03 > > Probing for video card: Unable to probe > No video hardware found, assuming headless > Graphical installation not available... Starting text mode. > Welcome to CentOS > > +------------------+ Package Installation +------------------+ > | | > | Name : libXt-1.0.2-3.1.fc6-i386 | > | Size : 359k | > | Summary: X.Org X11 libXt runtime library | > | | > | | > | Status: | > | | > | 53% | > | | > | Packages Bytes Time | > | Total : 349 564M 0:02:30 | > | Completed: 123 200M 0:00:53 | > | Remaining: 226 364M 0:01:37 | > | | > | 35% > Guest installation complete... restarting guest. > libvir: Xen Daemon error : POST operation failed: (xend.err "Error > creating domain: Boot loader didn't return any data!") > exception was: virDomainCreate() failed POST operation failed: > (xend.err "Error creating domain: Boot loader didn't return any data!") > Domain installation may not have been > successful. If it was, you can restart your domain > by running 'virsh start vm03'; otherwise, pleasels | <F12> next > screen > restart your installation. > [root@gimbli ~]# virsh start vm03 > libvir: Xen Daemon error : POST operation failed: (xend.err "Error > creating domain: Boot loader didn't return any data!") > error: Failed to start domain vm03 > > > > /var/log/messages got filled with the following messages: > > stem_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 > tclass=capability > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2139): avc: > denied { sys_resource } for pid=2445 comm="xenstored" capability=24 > scontext=system_u:system_r:xenstored_t:s0 > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2140): avc: > denied { sys_resource } for pid=2445 comm="xenstored" capability=24 > scontext=system_u:system_r:xenstored_t:s0 > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2141): avc: > denied { sys_resource } for pid=2445 comm="xenstored" capability=24 > scontext=system_u:system_r:xenstored_t:s0 > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2142): avc: > denied { sys_resource } for pid=2445 comm="xenstored" capability=24 > scontext=system_u:system_r:xenstored_t:s0 > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability > > > > What am I doing wrong? > as far as i am aware on standard RHEL or CentOS 5 packages a 32bit domU on a 64bit dom0 is not supported and known to crash _______________________________________________ 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 9

CentOS-announce Digest, Vol 37, Issue 1
by centos-announce-request＠centos.org 01 Mar '08

01 Mar '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. CESA-2008:0155 Important CentOS 4 x86_64 ghostscript - security update (Johnny Hughes) 2. CESA-2008:0155 Important CentOS 4 i386 ghostscript - security update (Johnny Hughes) 3. CESA-2008:0146 Moderate CentOS 4 i386 gd - security update (Johnny Hughes) 4. CESA-2008:0146 Moderate CentOS 4 x86_64 gd - security update (Johnny Hughes) 5. CESA-2008:0131 Moderate CentOS 4 x86_64 netpbm - security update (Johnny Hughes) 6. CESA-2008:0131 Moderate CentOS 4 i386 netpbm - security update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 29 Feb 2008 06:48:49 -0600 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2008:0155 Important CentOS 4 x86_64 ghostscript - security update To: CentOS-Announce <centos-announce(a)centos.org> Message-ID: <47C7FF31.4080505(a)centos.org> Content-Type: text/plain; charset="iso-8859-1" CentOS Errata and Security Advisory 2009:0155 https://rhn.redhat.com/errata/RHSA-2008-0155.html The following updated files have been uploaded and are currently syncing to the mirrors: x86_64: ghostscript-7.07-33.2.el4_6.1.i386.rpm ghostscript-7.07-33.2.el4_6.1.x86_64.rpm ghostscript-devel-7.07-33.2.el4_6.1.x86_64.rpm ghostscript-gtk-7.07-33.2.el4_6.1.x86_64.rpm src: ghostscript-7.07-33.2.el4_6.1.src.rpm

1 0

question on how yum updates cache
by Rogelio 01 Mar '08

01 Mar '08

I'm trying to make sense of CentOS's package management based on what (little) I know about Debian's. When I do a "yum install program" and it takes forever, is it updating local cache to install the most up-to-date version of that program? When I do it in Debian, it seems to install whatever version is in the "apt-cache" (unless I "apt-get update").

1 0

Recommended software for mail greylist?
by Zhang Huangbin 01 Mar '08

01 Mar '08

Hi, all. I want to use grey list in mail server, currently, i use postgrey to implement it. Any other recommended software? Thanks very much. ----- Best Regards. Zhang Huangbin - OpenBSD 4.2 -release, i386. - RHEL 5.1

9 12

GRabbing MAC address
by Jerry Geis 01 Mar '08

01 Mar '08

I am trying to grab the mac address for eth0 on centos 5.1 with ifconfig | grep eth0 | cut -d ' ' -f 5 and I dont get anything. What am I not doing right? ifconfig | grep eth0 | cut -d ' ' -f 1 gives me eth0 but anything else like -f 2, -f 3 etc I get nothing. Jerry

14 14

Re: [CentOS] Send in your favorite CentOS slogan today
by Ross S. W. Walker 01 Mar '08

01 Mar '08

CentOS, It's all about the community. -Ross ----- Original Message ----- From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> To: centos(a)centos.org <centos(a)centos.org> Sent: Fri Feb 29 20:16:22 2008 Subject: [CentOS] Send in your favorite CentOS slogan today Hi everyone, The CentOS project is looking for more slogans that may end up on promotional material (eg media, flyers, posters or stickers). We already collected a few funny, ironic, sarcastic or even distasteful ones. Feel free to visit our Slogans wiki page for a good laugh or rude offenses and add your own slogan by sending them to this thread. See: http://wiki.centos.org/Promo/Slogans And who knows, yours may end up somewhere ? If it gets selected, you win free CentOS updates for a whole month !! So get started ;) Disclaimer: Ideas contributed to this thread are considered free to be reused. Otherwise do NOT submit them to a public mailinglist :) I will be adding them to the wiki. -- -- dag wieers, dag(a)wieers.com, http://dag.wieers.com/ -- [Any errors in spelling, tact or fact are transmission errors] _______________________________________________ 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.

3 4

Allocaation resource error (DELL Optiplex 755)...
by John.Giovannis＠csiro.au 01 Mar '08

01 Mar '08

Hi all, (My first time in seeking assistance via the CentOS mailing list ... Not sure if I should be submitting this as a possible kernel bug). I've successfully installed Cent OS 5.1 (kernel: 2.6.18-53.1.13.el5) on an Optiplex 755 (EM64T). However I'm not able to get a NVIDIA Gigabyte 8600GT (PCI-e) card to work with the system despite successfully installing the latest NVIDIA drivers (NVIDIA-Linux-x86_64-169.07-pkg2.run). I've tested the same configuration in Windows with no difficulties. I suspect the kernel is not able to allocate the appropriate hardware resources possibly resulting in the card failing to fire up properly: Some diagnostics: A snippet of the Xorg log file: # more /var/log/Xorg.0.log | grep -E 'WW|EE' (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (WW) ****INVALID MEM ALLOCATION**** b: 0x13a000000 e: 0x13affffff correcting (EE) Cannot find a replacement memory range (WW) ****INVALID MEM ALLOCATION**** b: 0x138000000 e: 0x139ffffff correcting (WW) ****INVALID IO ALLOCATION**** b: 0x13800dc80 e: 0x13800dcff correcting (EE) end of block range 0xffffffff < begin 0x138000000 (EE) Cannot find a replacement memory range (EE) NVIDIA(0): The NVIDIA GPU at PCI:1:0:0 is not supported by the 169.09 (EE) NVIDIA(0): NVIDIA driver. (EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device! (EE) Screen(s) found, but none have a usable configuration. # dmesg | grep Cannot PCI: Cannot allocate resource region 8 of bridge 0000:00:01.0 PCI: Cannot allocate resource region 8 of bridge 0000:00:1c.0 PCI: Cannot allocate resource region 1 of device 0000:00:03.3 PCI: Cannot allocate resource region 0 of device 0000:00:19.0 PCI: Cannot allocate resource region 1 of device 0000:00:19.0 PCI: Cannot allocate resource region 0 of device 0000:00:1a.7 PCI: Cannot allocate resource region 0 of device 0000:00:1b.0 PCI: Cannot allocate resource region 0 of device 0000:00:1f.3 PCI: Cannot allocate resource region 0 of device 0000:01:00.0 PCI: Cannot allocate resource region 3 of device 0000:01:00.0 # lsmod | grep nvidia nvidia 8885796 0 i2c_core 56129 3 i2c_ec,nvidia,i2c_i801 # lspci -v | grep -E '00:01.0|00:1c.0|00:03.3|00:19.0|00:1a.7|00:1b.0|00:1f.3|01:00.0' 00:01.0 PCI bridge: Intel Corporation 82Q35 Express PCI Express Root Port (rev 02) (prog-if 00 [Normal decode]) 00:03.3 Serial controller: Intel Corporation 82Q35 Express Serial KT Controller (rev 02) (prog-if 02 [16550]) 00:19.0 Ethernet controller: Intel Corporation 82566DM-2 Gigabit Network Connection (rev 02) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02) (prog-if 20 [EHCI]) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02) (prog-if 00 [Normal decode]) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600 GT (rev a1) (prog-if 00 [VGA]) Is it likely that I need to try an older kernel or attempt to patch the current one ? Any suggestions are appreciated, John

2 2

T43 wireless ipw2200 centos 4.4
by Primorec 01 Mar '08

01 Mar '08

Hi ALL, Short description of my problem: I am not able to make wireless network working on the IBM ThinkPad T43p. System: T43p OS: CentOS 4.4 kernel: 2.6.9-34.EL firmware: ipw2200-firmware-3.0-3.nodist.rf.noarch.rpm What did I do ? - installed firmware from RPM package - removed kernel driver (/sbin/rmmod ipw2200) - installed kernel module (/sbin/modprobe ipw2200) dmesg output: ================= Dec 24 16:45:43 localhost kernel: ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.0 Dec 24 16:45:43 localhost kernel: ipw2200: Copyright(c) 2003-2004 Intel Corporation Dec 24 16:45:43 localhost kernel: ACPI: PCI interrupt 0000:04:02.0[A] -> GSI 11 (level, low) -> IRQ 11 Dec 24 16:45:43 localhost kernel: ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection Dec 24 16:45:44 localhost hald[3408]: Timed out waiting for hotplug event 577. Rebasing to 578 Dec 24 16:45:44 localhost kernel: ip_tables: (C) 2000-2002 Netfilter core team Dec 24 16:46:00 localhost hald[3408]: Timed out waiting for hotplug event 580. Rebasing to 581 Dec 24 16:46:02 localhost hald[3408]: Timed out waiting for hotplug event 583. Rebasing to 584 Dec 24 16:46:04 localhost hald[3408]: Timed out waiting for hotplug event 587. Rebasing to 588 Dec 24 16:46:06 localhost hald[3408]: Timed out waiting for hotplug event 590. Rebasing to 591 Dec 24 16:46:08 localhost hald[3408]: Timed out waiting for hotplug event 593. Rebasing to 594 - started 'system-config-network' tool - checked eth1 (wireless) (aka enabled wireless) - edited (via edit buton ) eth1 configuration Mode: auto Network name (SSID): linksys Channel: 1 Transmit rate: auto Key: 0x????? (26 hex numbers) - clicked the Activate button Result: dmesg output: Dec 24 19:25:06 localhost kernel: ip_tables: (C) 2000-2002 Netfilter core team Dec 24 19:25:07 localhost hald[3408]: Timed out waiting for hotplug event 626. Rebasing to 627 Dec 24 19:25:21 localhost hald[3408]: Timed out waiting for hotplug event 629. Rebasing to 630 Dec 24 19:25:23 localhost hald[3408]: Timed out waiting for hotplug event 632. Rebasing to 633 terminal output: Error for wireless request "Set Bit Rate" (8B20) : SET failed on device eth1 ; Operation not supported. Determining IP information for eth1... failed; no link present. Check cable? Can some merciful soul give me a hint or/and solution or/and RTFM pointer for my problem ? Thanks in advance Igor -- Experience is what you get when you didn't get what you wanted. Randy Pausch

2 2

CentOS Email Wiki and/or mailing list
by John Hinton 29 Feb '08

29 Feb '08

As I hijacked a thread... I thought I'd start this new one. Yes, shame on me. Karanbir Singh wrote: > John Hinton wrote: >> As a side, I could see blossoming a Wiki area specific to email which might >> eventually fill out to an extremely robust set of how to's for installations >> of what amounts to being some of the very hardest things that I've >> accomplished with CentOS. Yes SpamAssassin is a powerful tool, but for >> instance the default setup that comes out of the box is fairly weak. A trip >> to the SpamAssassin site will just leave you mostly confused and reading for >> hours only to find out that what you think is good might not be applicable >> to your system. > Given that, I think it might be a good idea to tackle some of this on > the wiki itself rather than needing a list for it. One thing that we are > working on at the moment is to try and get a commenting system working > on the wiki - so if drive-by users have comments / issues / feedback or > even a contribution of some sort in content - they can drop that in > there with a near zero barrier to entry. The Editorial Team on the wiki > can then evaluate that for inclusion in the main article or leave it as > a comment. This would certainly be a great start. As I see it, a mailsystem Wiki should have some specific divisions itself. One would be 'General' and then it would likely need 'Sendmail', 'Postfix', 'Qmail' areas. I'm just thinking out loud here. I've never done anything on a Wiki. I think a good initial layout however would be important. I'm trying to think about the gotchas I discover when trying to search for things. It seems like it always comes up two out of three and therefore isn't relevant. Sounds like I've just volunteered myself to participate in this Wiki! And yes, I'd be thrilled to! >> I think a fair number of the members of this list and the users of CentOS >> are using it in a server environment and require email. And basically, if >> you require email that is not exclusively internal to a network, spam is a >> huge battle which requires constant time... and I mean hours and hours and >> hours and hours of time. I just spent about 4 days on this again this past >> week. > I am about to take the plunge into this area after about 2 years and > completely rework my own anti-spam system. Hope to take loads of notes > and get them onto the wiki. Pros and Cons would be another great area. Revisiting what I had been doing this past week took me down a few trails to not being satisfied with the end result. Hours spent to a dead end. There are many products out there and each seems to have some gotcha. It would be nice to know how well they get along with CentOS, how well they perform on various levels of load as well as results for accuracy in delivery. > We have plenty of resources within the CentOS setup. I dont see hosting > something of this nature being too hard. However, i think it might be > important to work out what we want to host. IMHO, email is too niche an > area to have a dedicated list for it. Something like NetworkServices > might be a better target. I would be happy with anything! I always feel like I am off topic when posting email system questions to the CentOS list and I do think it is. NetworkServices could be a good place. I'm not sure it's the place for network hardware discussions... but I don't know. I haven't looked lately at how the mailing list are advertised. A good name for the list would certainly help it become more robust or having more users specific to that or those topics. Best, John Hinton

2 1

ACPI reboot-issue (CentOS 4)
by Simen Thoresen 29 Feb '08

29 Feb '08

Hi all, I'm trying to troubleshoot my way thru a ACPI-issue on several machines with the Asus P5N32-E SLI motherboard (S775, Nvidia 680i chipset) http://www.asus.com/products.aspx?l1=3&l2=11&l3=397&l4=0&model=1459&modelme… This is CentOS 4 x86_64, and appears on all tested kernels, including kernel-smp-2.6.9-67.0.4.EL My symptoms are that the machine won't reboot on the reboot command. 'poweroff' does turn the power off and halt halts the system (without turning the power off), but reboot effectively does a 'halt'. I can 'fix' this by giving the 'acpi=off' parameter to the kernel in grub, but this causes other problems (some of these machines have quad-core CPUs, and these require ACPI to initialize 3 of the cores. The dual-core CPU-machines work with acpi=off. With acpi=off, reboot works as it is supposed to. I think the root of this issue is the Asus BIOS - we also have several Asus M2N-SLI Deluxe (Athlon64, Nvidia 570 chipset) systems that started exhibiting the same symptom after a BIOS upgrade. On these acpi=off does not cause other problems, so this is no issue for us now. Any suggestions? I think I understand that turning ACPI off basically turns APM on, and that APM reboot works. Is there a way to do reboot with APM instead of ACPI? Yours, -S -- Simen Thoresen - Dolphin ICS Systems Administrator

3 6

Kernel-upgrade breaks forcedeth-driver (CentOS 4)
by Simen Thoresen 29 Feb '08

29 Feb '08

Hi all, Same system as my previous mail - Asus P5N32-E SLI motherboards, CentOS 4 x86_64. The kernel-supplied forcedeth driver works in kernel-smp-2.6.9-55.0.9.EL (both with and without acpi=off), but after upgrading to kernel-smp-2.6.9-67.0.4.EL, networking does not start. After trying dhcp, ifconfig reports 17 dropped TX packets (all other counters are empty). Ethtool reports the same settings for working and non-working kernel, and both report the link arbitrated to 1000Mbps. Setting a manual address does not do anything useful either. When booting with 55.0.9, networking works again. This has also been confirmed on another system - 2.6.9-55.0.12.EL works, and 2.6.9-67.EL fails (but this system is not available for troubleshooting right now). Also, the above system was attempted installed with CentOS 5 (.0 and later with 5.1), but this was aborted due to 'networking problems', so I am thinking that the problem possibly persists at least as late as the CentOS 5.1 install-kernel. Any thoughts or suggestions? Yours, -S -- Simen Thoresen - Dolphin ICS Systems Administrator

2 1

Re: [CentOS] Recommended software for mail greylist?
by Brent L. Bates 29 Feb '08

29 Feb '08

We've been using milter-greylist: http://hcpnet.free.fr/milter-greylist/ ftp://ftp.espci.fr/pub/milter-greylist/ for almost a year now and it works great. I looked over a number of other options and I believe this was the only one that was a compiled executable. I think all the other ones I found were scripts and I wanted something faster. -- Brent L. Bates (UNIX Sys. Admin.) M.S. 912 Phone:(757) 865-1400, x204 NASA Langley Research Center FAX:(757) 865-8177 Hampton, Virginia 23681-0001 Email: B.L.BATES(a)larc.nasa.gov http://www.vigyan.com/~blbates/

2 1

Re: [CentOS] error creating Centos 5.1 x32 dum_U instance on CentOS5.1x64
by Ross S. W. Walker 29 Feb '08

29 Feb '08

Well, take it over to CentOS-virt, attach the config of the guest and I'm sure someone will spot the problem. -Ross ----- Original Message ----- From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> To: CentOS mailing list <centos(a)centos.org> Sent: Fri Feb 29 08:48:42 2008 Subject: Re: [CentOS] error creating Centos 5.1 x32 dum_U instance on CentOS5.1x64 Ross S. W. Walker wrote: > > Nah, RHEL 5.1+ supports 32-bit domU (PAE and non PAE) on 64-bit dom0. > > Actually RHEL Xen is 3.1 with the brain damaged 3.0 userland utilities. > > -Ross > > > ----- Original Message ----- > From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> > To: CentOS mailing list <centos(a)centos.org> > Sent: Fri Feb 29 04:46:42 2008 > Subject: Re: [CentOS] error creating Centos 5.1 x32 dum_U instance on > CentOS5.1 x64 > > Rudi Ahlers wrote: > > Hi all > > > > This is the first time I try and get Xen working, and want to install > > a few CentOS 5.1 32bit and FreeBSD 6.1 VM's on my CentOS 5.1 x64 server. > > > > Trying to get the first one to install is rather trivial, and I keep > > on running into errors. At fist I wanted to install it fro the cdrom, > > so I used "virt-install --cdrom=/dev/hdc" It booted up, and I could > > choose my language, but then got an error saying I don't have the > > right driver for the cdrom install. Odd. > > > > So, I copied the whole CD to my intranet server, to try a HTTP > > installation, which got much further, but fails as soon as it starts > > copying the files to the xvda partition. > > > > Here's what I've done: > > virt-install -p > > --location=http://intranet/kickstart/centos/5.1/32/os/i386 --ram=512 > > --file=/vm/vm03.img --name=vm03 > > > > Probing for video card: Unable to probe > > No video hardware found, assuming headless > > Graphical installation not available... Starting text mode. > > Welcome to CentOS > > > > +------------------+ Package Installation +------------------+ > > | | > > | Name : libXt-1.0.2-3.1.fc6-i386 | > > | Size : 359k | > > | Summary: X.Org X11 libXt runtime library | > > | | > > | | > > | Status: | > > | | > > | 53% | > > | | > > | Packages Bytes Time | > > | Total : 349 564M 0:02:30 | > > | Completed: 123 200M 0:00:53 | > > | Remaining: 226 364M 0:01:37 | > > | | > > | 35% > > Guest installation complete... restarting guest. > > libvir: Xen Daemon error : POST operation failed: (xend.err "Error > > creating domain: Boot loader didn't return any data!") > > exception was: virDomainCreate() failed POST operation failed: > > (xend.err "Error creating domain: Boot loader didn't return any data!") > > Domain installation may not have been > > successful. If it was, you can restart your domain > > by running 'virsh start vm03'; otherwise, pleasels | <F12> next > > screen > > restart your installation. > > [root@gimbli ~]# virsh start vm03 > > libvir: Xen Daemon error : POST operation failed: (xend.err "Error > > creating domain: Boot loader didn't return any data!") > > error: Failed to start domain vm03 > > > > > > > > /var/log/messages got filled with the following messages: > > > > stem_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 > > tclass=capability > > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2139): avc: > > denied { sys_resource } for pid=2445 comm="xenstored" capability=24 > > scontext=system_u:system_r:xenstored_t:s0 > > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability > > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2140): avc: > > denied { sys_resource } for pid=2445 comm="xenstored" capability=24 > > scontext=system_u:system_r:xenstored_t:s0 > > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability > > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2141): avc: > > denied { sys_resource } for pid=2445 comm="xenstored" capability=24 > > scontext=system_u:system_r:xenstored_t:s0 > > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability > > Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2142): avc: > > denied { sys_resource } for pid=2445 comm="xenstored" capability=24 > > scontext=system_u:system_r:xenstored_t:s0 > > tcontext=system_u:system_r:xenstored_t:s0 tclass=capability > > > > > > > > What am I doing wrong? > > > > as far as i am aware on standard RHEL or CentOS 5 packages a 32bit domU > on a 64bit dom0 is not supported and known to crash > > > _______________________________________________ > Ok, so what do I do if I want to have a 64bit Host XEN & 32guest's? I'd prefer to use CentOS for this purpose, if possible -- Kind Regards Rudi Ahlers CEO, SoftDux Web: http://www.SoftDux.com Check out my technical blog, http://blog.softdux.com for Linux or other technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stugg _______________________________________________ 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.

1 0

error creating Centos 5.1 x32 dum_U instance on CentOS 5.1 x64
by Rudi Ahlers 29 Feb '08

29 Feb '08

Hi all This is the first time I try and get Xen working, and want to install a few CentOS 5.1 32bit and FreeBSD 6.1 VM's on my CentOS 5.1 x64 server. Trying to get the first one to install is rather trivial, and I keep on running into errors. At fist I wanted to install it fro the cdrom, so I used "virt-install --cdrom=/dev/hdc" It booted up, and I could choose my language, but then got an error saying I don't have the right driver for the cdrom install. Odd. So, I copied the whole CD to my intranet server, to try a HTTP installation, which got much further, but fails as soon as it starts copying the files to the xvda partition. Here's what I've done: virt-install -p --location=http://intranet/kickstart/centos/5.1/32/os/i386 --ram=512 --file=/vm/vm03.img --name=vm03 Probing for video card: Unable to probe No video hardware found, assuming headless Graphical installation not available... Starting text mode. Welcome to CentOS +------------------+ Package Installation +------------------+ | | | Name : libXt-1.0.2-3.1.fc6-i386 | | Size : 359k | | Summary: X.Org X11 libXt runtime library | | | | | | Status: | | | | 53% | | | | Packages Bytes Time | | Total : 349 564M 0:02:30 | | Completed: 123 200M 0:00:53 | | Remaining: 226 364M 0:01:37 | | | | 35% Guest installation complete... restarting guest. libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") exception was: virDomainCreate() failed POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start vm03'; otherwise, pleasels | <F12> next screen restart your installation. [root@gimbli ~]# virsh start vm03 libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: Boot loader didn't return any data!") error: Failed to start domain vm03 /var/log/messages got filled with the following messages: stem_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2139): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2140): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2141): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability Feb 29 10:36:59 gimbli kernel: audit(1204274218.949:2142): avc: denied { sys_resource } for pid=2445 comm="xenstored" capability=24 scontext=system_u:system_r:xenstored_t:s0 tcontext=system_u:system_r:xenstored_t:s0 tclass=capability What am I doing wrong? -- Kind Regards Rudi Ahlers CEO, SoftDux Web: http://www.SoftDux.com Check out my technical blog, http://blog.softdux.com for Linux or other technical stuff, or visit http://www.WebHostingTalk.co.za for Web Hosting stugg

3 8

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

29 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. CESA-2008:0155 Important CentOS 3 ia64 ghostscript - security update (Pasi Pirhonen) 2. CESA-2008:0155 Important CentOS 4 ia64 ghostscript - security update (Pasi Pirhonen) 3. CESA-2008:0131 Moderate CentOS 3 ia64 netpbm - security update (Pasi Pirhonen) 4. CESA-2008:0131 Moderate CentOS 4 ia64 netpbm - security update (Pasi Pirhonen) 5. CESA-2008:0146 Moderate CentOS 4 ia64 gd - security update (Pasi Pirhonen) 6. CESA-2008:0155 Important CentOS 3 s390(x) ghostscript - security update (Pasi Pirhonen) 7. CESA-2008:0155 Important CentOS 4 s390(x) ghostscript - security update (Pasi Pirhonen) 8. CESA-2008:0131 Moderate CentOS 3 s390(x) netpbm - security update (Pasi Pirhonen) 9. CESA-2008:0131 Moderate CentOS 4 s390(x) netpbm - security update (Pasi Pirhonen) 10. CESA-2008:0146 Moderate CentOS 4 s390(x) gd - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Thu, 28 Feb 2008 21:19:56 +0200 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2008:0155 Important CentOS 3 ia64 ghostscript - security update To: centos-announce(a)centos.org Message-ID: <20080228191956.GU3950(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2009:0155 https://rhn.redhat.com/errata/RHSA-2008-0155.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/ghostscript-7.05-32.1.13.ia64.rpm updates/ia64/RPMS/ghostscript-devel-7.05-32.1.13.ia64.rpm updates/ia64/RPMS/hpijs-1.3-32.1.13.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

strange situation with dev sr0
by David Hláčik 29 Feb '08

29 Feb '08

Hi I have absolutely no idea what does it means : --------------------- Kernel Begin ------------------------ WARNING: Kernel Errors Present Buffer I/O error on device sr0, l ...: 16932 Time(s) end_request: I/O error, dev sr0, sector ...: 16962 Time(s) ---------------------- Kernel End ------------------------- I am getting this all the time a lot of times as you can see. Machine is running on Centos 5.1 x64 running vmware server , with 2 serial ata devices sda sdb connected into raid md0 md1 level 1. I have no device sr0 and I do not know what it is. I have DVDRW on /dev/hda I believe it all started once when I used cdrecord to burn image on cd and I've got error messages that device is not ready. Since I was not able to kill cdrecord propertly I did restarted system. Since then I am allways receiving this messages. Thanks a lot David

1 0

erroneous and irritating messages
by Phil Savoie 29 Feb '08

29 Feb '08

HI All, Keep getting the following in the messages file: Feb 28 21:24:43 hp kernel: ACPI: Unable to turn cooling device [f7d82dec] 'on' Feb 28 21:25:13 hp last message repeated 5 times Have hordes of these. All fans are working fine afaikt. Any idea how to make the beast stop reporting these messages? I am running kernel 2.6.18-53.1.13.el5 #1 SMP. Thanks in advance, Phil

3 3

MRTG question on CentOS
by Rogelio 29 Feb '08

29 Feb '08

I'm trying to get MRTG up and running on CentOS, but the displayed http page says that I don't have permission to access /mrtg/ on the server. Here are my commands yum install mrtg vim /etc/httpd/conf.d/mrtg.conf /etc/init.d/httpd restart cfgmaker --global 'WorkDir: /var/www/mrtg' --global 'Options[_]: bits,growright' --output /etc/mrtg/mrtg.cfg public(a)10.200.200.1 mrtg /etc/mrtg/mrtg.cfg env LANG=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg env LANG=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg (type again, per the MRTG instructions) For what it's worth, when I 'tail /etc/httpd/logs/error_logs", I get the following [Wed Feb 27 15:41:13 2008] [error] [client 10.200.200.58] Directory index forbidden by Options directive: /var/www/mrtg/ Any suggestions?

4 3

smtp mailer or SMART_HOST in sendmail.mc
by Jerry Geis 28 Feb '08

28 Feb '08

Is there a EASY way to change the SMART_HOST in sendmail.mc. Some command line that does it? Trying to explain to customers editor commands, etc... to edit this file, change the name, make and service sendmail restart is BIG for someone that doesnt know linux... Just wondering if something exists already before I make something. Dont wish to redo anything. Thanks, Jerry

7 8

installkernel
by Artie Ziff 28 Feb '08

28 Feb '08

Hi, I have a question about: /sbin/installkernel I believe this line: LINK_PATH=/boot and usage of this variable... is a bug. What do others say? Using this script, as-is, I would need to chroot to make it work properly for a alternative INSTALL_PATH, right? who the heck is tyson? why did he re-write this? # # /sbin/installkernel - written by tyson(a)rwii.com # Cheers, AZ

1 0

perl error on CentOS
by Rogelio 28 Feb '08

28 Feb '08

when i type 'perl perlscript.pl, I get the following error Can't locate version.pm in @INC (@INC contains: /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 .) at perlscript.pl line 29. What do I need to do to configure my perl environment? I typed in CPAN and "install Bundles::CPAN" and it seemed to install everything, but on line 29 of the perl script, it has a problem with the line use version; our $VERSION = '2.1.0';

3 4

Seelinux : Allow postfix to connect to MysQL
by Sudheer 28 Feb '08

28 Feb '08

Hello, I just configured postfix so that it uses MySQL database to store virtual domain and user info. When SELinux is enalbed, postfix fails to connect to MySQL. Below is an example error from the mailog file. postfix/trivial-rewrite[4753]: fatal: mysql:/etc/postfix/mysql_virtual_alias_maps.cf(0,lock|fold_fix): table lookup problem When I turn off Selinux, the problem does not appear. How can I configure Selinux to allow postfix to connect to MySQL? I am using CentOS release 5 (Final). I have installed the postfix and mysql-server packages from CentOSplus repository. The server is located in a remote location and GUI is not installed on it. I appreciate any help, Regards, Sudheer

1 0

xen domU shutdown and save
by gen2 28 Feb '08

28 Feb '08

Hi There, Having some trouble discovering how to shutdown domU's without saving them. I have some awful power from the grid causing the backup battery system to initiate shutdown's on dom0, which is the desired result, however domU's are saving (which I don't want) and this takes a very long time (for whatever reason). As they shutdown, console does this .................................on and on while it tries to save the domU's, past the point where the battery can sustain the dom0. So I need a way to consistently, gracefully deal with dom0 shutdowns (in a timely manner). I have the domU's in /etc/xen/auto. Thanks for any pointers! W

2 1

how to uninstall
by scaglietti amore 28 Feb '08

28 Feb '08

hello guys i have centos5.1, and my subject is : when i install a package without the rpm tool cause its not rpm package like configure , make , make install how can i uninstall it later ? thank u all for ur time _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

4 4

proliant ml370
by Hiep Nguyen 28 Feb '08

28 Feb '08

hi all, i just inherit a server: Compaq ProLiant ML370 Generation 2 Server with Smart Array 5300 Controller with 6x18.2GB hard drives. i want to install centos 5 on it with hardware raid 1. any idea how? it also has a build-in and add-on ethernet cards. how do i know which one is which to assign ip? thanks. t. hiep

4 6

Re: [CentOS] how to uninstall
by Ross S. W. Walker 28 Feb '08

28 Feb '08

Jim, Try out 'alternatives' for managing symlinks to prefixed installs, especially if you have multiple versions. Works like a charm and can be used to fix/remove links later. -Ross ----- Original Message ----- From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> To: CentOS mailing list <centos(a)centos.org> Sent: Thu Feb 28 04:13:35 2008 Subject: Re: [CentOS] how to uninstall > when i install a package without the rpm tool cause its not rpm > package like configure , make , make install > > how can i uninstall it later ? If possible, configure it using --prefix so that everything belonging to it gets installed in the same place, which will make removing it easy. I prefer to install into /usr/local/<application>/<version> so that I can retain old versions while installing a new one. There will be some work to do to make executables available in users' paths. I do it by creating a symbolic link 'current' pointing to the current version, and making links of the contents of current's bin (in terms of current so that they don't change when I switch versions) in /usr/local/bin. GNU Stow (http://www.gnu.org/software/stow/) not that I use it, has formalised this approach: GNU Stow helps the sysadmin organise files under /usr/local/ by allowing each piece of software to be installed in its own tree under /usr/local/stow/, and then using symlinks to create the illusion that all the software is installed in the same place. Jim _______________________________________________ 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.

1 0

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

28 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. CESA-2008:0153 Important CentOS 4 ia64 cups - security update (Pasi Pirhonen) 2. CESA-2008:0161 Important CentOS 4 ia64 cups - security update (Pasi Pirhonen) 3. CESA-2008:0153 Important CentOS 3 s390(x) cups - security update (Pasi Pirhonen) 4. CESA-2008:0161 Important CentOS 4 s390(x) cups - security update (Pasi Pirhonen) 5. CESA-2008:0155 Important CentOS 3 i386 ghostscript - security update (Tru Huynh) 6. CESA-2008:0155 Important CentOS 3 x86_64 ghostscript - security update (Tru Huynh) 7. CESA-2008:0131 Moderate CentOS 3 i386 netpbm - security update (Tru Huynh) 8. CESA-2008:0131 Moderate CentOS 3 x86_64 netpbm - security update (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Wed, 27 Feb 2008 20:57:36 +0200 From: Pasi Pirhonen <upi(a)centos.fi> Subject: [CentOS-announce] CESA-2008:0153 Important CentOS 4 ia64 cups - security update To: centos-announce(a)centos.org Message-ID: <20080227185736.GQ3950(a)centos.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2009:0153 https://rhn.redhat.com/errata/RHSA-2008-0153.html The following updated files have been uploaded and are currently syncing to the mirrors: ia64: updates/ia64/RPMS/cups-1.1.17-13.3.51.ia64.rpm updates/ia64/RPMS/cups-devel-1.1.17-13.3.51.ia64.rpm updates/ia64/RPMS/cups-libs-1.1.17-13.3.51.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://pasi.pirhonen.eu/ Top-postings silently ignored

1 0

Find user accounts with uid > 500
by Sean Carolan 28 Feb '08

28 Feb '08

Hi all: I'm doing an audit of some Linux machines, and have used this awk one-liner to find accounts with uid > 499: awk -F: '{if ($3 > 499) print $0}' < /etc/passwd It works great if you run it on a host directly, but if I try to ssh to a remote host and run the command it fails: mybox$ ssh servername awk -F: '{if ($3 > 499) print $0}' < /etc/passwd bash: -c: line 1: syntax error near unexpected token `(' bash: -c: line 1: `awk -F: {if ($3 > 499) print $0}' I tried wrapping the command in quotes but no luck. Any suggestions? I want to put this into a for loop so I can grab the info from multiple machines. thanks Sean

3 4

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

28 Feb '08

It seems everybody is out of ideas why yum is not updating the kernel. The following kernels are installed in /boot: vmlinuz-2.6.18-8.1.14.el5 vmlinuz-2.6.18-8.el5 I originally installed CentOS 5.0 via CD. Yum automatically updated to 5.1 including kernel-2.6.18-8.1.14.el5. I have traced the kernels from kernel-2.6.18-8.el5 to kernel-2.6.18-8.1.14.el5. Yum stopped updating at this point. kernel-2.6.18-8.1.14.el5 was installed Oct 10, 2007 according to yum.log. It seems I installed rpmforge.repo around October 13, 2007. The installation included two files. rpmforge.repo and mirrors-rpmforge. The contents of rpmforge.repo is: # Name: RPMforge RPM Repository for Red Hat Enterprise 5 - dag # URL: http://rpmforge.net/ [rpmforge] name = Red Hat Enterprise $releasever - RPMforge.net - dag #baseurl = http://apt.sw.be/redhat/el5/en/$basearch/dag mirrorlist = http://apt.sw.be/redhat/el5/en/mirrors-rpmforge #mirrorlist = file:///etc/yum.repos.d/mirrors-rpmforge enabled = 1 priority = 99 protect = 0 gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-rpmforge-dag gpgcheck = 1 Other than the priority is not needed, does any of the previous ring a bell? Still frustrated. I received the following this morning: /etc/cron.daily/yum.cron: Error: Cannot find a valid baseurl for repo: base Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=5&arch=i386&repo=os error was [Errno 14] HTTP Error 505: DNS lookup error Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=5&arch=i386&repo=os error was [Errno 14] HTTP Error 506: Failure To Connect To Web Server Has CentOS.org changed their url? -- Bob Taylor

15 77

smokeping on CentOS questions
by Rogelio 28 Feb '08

28 Feb '08

I'm having some problems getting CentOS to serve up my Smokeping pages ( http://oss.oetiker.ch/smokeping/) However, I'm having problems getting the pages to serve up correctly. Here is a quick run down of what I've done. (1) wget and untar to /usr/local/smokeping (2) chown -R root:root /usr/local/smokeping (3) modifying to the following files to reflect my environment (not sure if all my steps here were good) /usr/local/smokeping/bin/smokeping /usr/local/smokepoing/htdocs/smokeping.cfg (4) ln -s /usr/local/smokeping/htdocs /var/www/html/smokeping When I go to "www.mybox.com/smokeping", all I get is a list of files, not the webpage I would expect to get. What might I be doing wrong?

4 5

Networking problems with fresh install
by Chuck Campbell 28 Feb '08

28 Feb '08

I just did a fresh install of centos 5.0 from cd, followed by yum update which installed 399 packages. No failures or errors that I can see. I have three nics in the box, but am only setting up one at the moment. The box can ping others in my network, but if I try ssh, telnet, ftp, etc I get this: [root@cm network-scripts]# ftp watchdog ftp: connect: No route to host ftp> [root@cm sysconfig]# ftp 172.17.2.242 ftp: connect: No route to host root@cm network-scripts]# telnet watchdog Trying 172.17.2.242... telnet: connect to address 172.17.2.242: No route to host telnet: Unable to connect to remote host: No route to host [root@cm network-scripts]# ssh -l campbell watchdog ssh: connect to host watchdog port 22: No route to host The weird part is I can do this: [root@cm network-scripts]# ping watchdog PING watchdog (172.17.2.242) 56(84) bytes of data. 64 bytes from watchdog (172.17.2.242): icmp_seq=1 ttl=64 time=0.170 ms 64 bytes from watchdog (172.17.2.242): icmp_seq=2 ttl=64 time=0.145 ms 64 bytes from watchdog (172.17.2.242): icmp_seq=3 ttl=64 time=0.135 ms --- watchdog ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.135/0.150/0.170/0.014 ms [root@cm network-scripts]# arp watchdog Address HWtype HWaddress Flags Mask Iface watchdog ether 00:16:76:D1:67:F2 C eth0 and I can do this: [root@cm sysconfig]# ssh -l campbell cs1 campbell@cs1's password: .................... and it will connect fine. output of netstat -rn: [root@cm network-scripts]# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 172.17.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 172.17.2.1 0.0.0.0 UG 0 0 0 eth0 output of netstat -r: [root@cm network-scripts]# netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 172.17.2.0 * 255.255.255.0 U 0 0 0 eth0 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0 default gateway 0.0.0.0 UG 0 0 0 eth0 output of route: [root@cm network-scripts]# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.17.2.0 * 255.255.255.0 U 0 0 0 eth0 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0 default gateway 0.0.0.0 UG 0 0 0 eth0 here are the relevant files as far as I know: /etc/hosts [root@cm network-scripts]# more /etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 172.17.2.1 gateway gateway.inexs.com 172.17.2.50 cm cm.inexs.com #172.17.2.52 cm2 cm2.inexs.com 172.17.2.51 cs1 cs1.inexs.com #172.17.2.53 cs2 cs2.inexs.com 172.17.2.137 ingrid ingrid.inexs.com 172.17.2.161 vail vail.inexs.com 172.17.2.162 beaver beaver.inexs.com 172.17.2.175 plotting plotting.inexs.com 172.17.2.242 watchdog watchdog.inexs.com /etc/sysconfig/network-scripts/ifcfg-eth0 [root@cm network-scripts]# more ifcfg-eth0 # Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet DEVICE=eth0 BOOTPROTO=none BROADCAST=172.17.2.255 HWADDR=00:e0:81:2c:73:86 ONBOOT=yes DHCP_HOSTNAME=cm TYPE=Ethernet IPADDR=172.17.2.50 NETMASK=255.255.255.0 NETWORK=172.17.2.0 GATEWAY=172.17.2.1 USERCTL=yes IPV6INIT=no PEERDNS=no PEERNTP=no /etc/sysconfig/network-scripts/ifcfg-lo [root@cm network-scripts]# more ifcfg-lo DEVICE=lo IPADDR=127.0.0.1 NETMASK=255.0.0.0 NETWORK=127.0.0.0 # If you're having problems with gated making 127.0.0.0/8 a martian, # you can change this to something else (255.255.255.255, for example) #BROADCAST=127.255.255.255 BROADCAST=255.255.255.255 ONBOOT=yes NAME=loopback output of ifconfig -a: eth0 Link encap:Ethernet HWaddr 00:E0:81:2C:73:86 inet addr:172.17.2.50 Bcast:172.17.2.255 Mask:255.255.255.0 inet6 addr: fe80::2e0:81ff:fe2c:7386/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:27358 errors:0 dropped:0 overruns:0 frame:0 TX packets:4252 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2338646 (2.2 MiB) TX bytes:620434 (605.8 KiB) eth1 Link encap:Ethernet HWaddr 00:E0:81:2C:73:87 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Interrupt:19 eth2 Link encap:Ethernet HWaddr 00:E0:81:2C:74:33 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1828 errors:0 dropped:0 overruns:0 frame:0 TX packets:1828 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2737876 (2.6 MiB) TX bytes:2737876 (2.6 MiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:27358 errors:0 dropped:0 overruns:0 frame:0 TX packets:4255 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2448018 (2.3 MiB) TX bytes:640420 (625.4 KiB) Interrupt:18 sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:4252 errors:0 dropped:0 overruns:0 frame:0 TX packets:27358 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:620434 (605.8 KiB) TX bytes:2338646 (2.2 MiB) vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:4252 errors:0 dropped:0 overruns:0 frame:0 TX packets:27358 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:620434 (605.8 KiB) TX bytes:2338646 (2.2 MiB) vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:40 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:8674 (8.4 KiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:21327 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1523795 (1.4 MiB) TX bytes:0 (0.0 b) /etc/sysconfig/network [root@cm sysconfig]# more network NETWORKING=yes NETWORKING_IPV6=no HOSTNAME=cm /etc/resolv.conf [root@cm sysconfig]# more /etc/resolv.conf nameserver 216.201.128.10 nameserver 66.196.216.10 /etc/sysconfig/iptables [root@cm sysconfig]# more iptables # Firewall configuration written by system-config-securitylevel # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A FORWARD -j RH-Firewall-1-INPUT -A RH-Firewall-1-INPUT -i lo -j ACCEPT -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT -A RH-Firewall-1-INPUT -p 50 -j ACCEPT -A RH-Firewall-1-INPUT -p 51 -j ACCEPT -A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT -A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 21 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 25 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 2049 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m udp -p udp --dport 137 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m udp -p udp --dport 138 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 139 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 445 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 23 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited COMMIT -- ACCEL Services, Inc.| Specialists in Gravity, Magnetics | (713)993-0671 ph. | and Integrated Interpretation | (713)993-0608 fax 633 1/2 W. 21st St.| Since 1992 | (713)306-5794 cell Houston, TX, 77008 | Chuck Campbell | campbell(a)accelinc.com | President & Senior Geoscientist | "Integration means more than having all the maps at the same scale!"

2 1

NFSroot is acting strange in CentOS5
by vincenzo romero 27 Feb '08

27 Feb '08

Hello all, I have observed a problem with a diskless PXE client I am attempting to configure. PXE/NFS/DHCP/TFTPd server is running CentOS5.1 and the Diskless workstation's root and kernel was extracted from a CentOS5.1 (custom kernel due to setting to enable Root File System support). Problem: When the diskless client boots and logs in I notice that my root user is being squashed, even if I have exported the root with the "no_root_squash" option. The exports file contains this line: /export/images *(rw,no_root_squash,no_subtree_check) 1. Creating a file as root gives it nobody permission: rw-r--r-- 1 65534 65534 0 Feb 26 16:30 foo 2. When I explicitly mount the same export from the booted workstation and create another file; this time, it is created as root: -rw-r--r-- 1 root root 0 Feb 26 16:31 bar 3. I checked the /proc/mounts and notice there are differences in the NFS options it has accepted during mount: rootfs / rootfs rw 0 0 /dev/root / nfs rw,vers=2,rsize=4096,wsize=4096,hard,nolock,proto=udp,timeo=11,retrans=2,sec=null,addr=192.16.10.5 0 0 192.16.10.5:/tftpboot /mnt/test nfs rw,vers=3,rsize=32768,wsize=32768,hard,proto=tcp,timeo=600,retrans=2,sec=sys,addr=192.168.16.5 0 0 4. I try to append NFS options to my APPEND line to force: NFS version3, change r/wsize, use tcp protocol and change the sec from null to sys (null seems to be the parameter that affects the NFS ownership/permission). My /tftpboot/pxelinux.cfg/default file contains the following: nfsroot=192.168.16.5:/export/images/centos51_x86-64,nfsversvers=3,tcp,rsize=32768,wsize=32768,sec=sys ip=dhcp 5. All options are honored except for the "sec=sys" option. Below is the output of the /proc/cmdline: /proc/cmdline: root=/dev/nfs rw nfsroot=192.168.16.5:/export/images/centos51_x86-64,nfsvers=3,tcp,rsize=32768,wsize=32768,sec=sys ip=dhcp BOOT_IMAGE=vmlinuz-2.6.18-custom-2.6.18-53.el5 6. But the /proc/mounts shows that the "sec=" parameter is still set to NULL. /proc/mounts: rootfs / rootfs rw 0 0 /dev/root / nfs rw,vers=3,rsize=3278,wsize=3478,hard,nolock,proto=tcp,timeo=11,retrans=2,sec=null,addr=192.168.16.5 0 0 ............ Kernel versions: PXE server --> uname -a Linux qatest1 2.6.18-53.1.13.el5xen #1 SMP Tue Feb 12 13:33:07 EST 2008 x86_64 x86_64 x86_64 GNU/Linux Diskless Workstation's kernel and root are extracted from this: Linux localhost.localdomain 2.6.18-custom-2.6.18-53.el5 #1 SMP Wed Feb 20 08:45:23 PST 2008 x86_64 x86_64 x86_64 GNU/Linux Any help would be greatly appreciated. -- best, Vince

2 5

OT: Thunderbird2 for 64 bits
by carlopmart 27 Feb '08

27 Feb '08

Hi all, Somebody knows from where can I download 64 bits version of Thunderbird2?? In mozilla's website only 32 bits exists. Thanks. -- CL Martinez carlopmart {at} gmail {d0t} com

3 3

bash - safely pass untrusted strings?
by Benjamin Smith 27 Feb '08

27 Feb '08

In bash, given a string assignment as follows, how do I "add slashes" automagically, so that it can be safely passed to another program? Notice that the assignment contains spaces, single-quotes and double-quotes, maybe god-only-knows-what-else. It's untrusted data. Yet I need to pass it all *safely*. The appropriate function in PHP is addslashes(); but what is the bash equivalent? EG: #! /bin/sh A="This isn't a \"parameter\""; B=`/path/to/somecommand.sh $A`; exit 0; Thanks, -Ben -- Only those who reach toward a goal are likely to achieve it. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

12 40

Pointer to simple mail server setup?
by Steve Snyder 27 Feb '08

27 Feb '08

Hello. I need to set up a mail server for a small (~5 people) organization on CentOS 5.1. While I am very familiar with CentOS and Linux in general, I have zero experience in setting up a POP3(s)/SMTP mail server. I suppose eventually I'd like to do spam/virus filtering, but initially the simple sending/receiving of mail will be adequate. Can someone point me to a tutorial on setting up a mail server on CentOS 5? Thanks.

6 5

put command is not working in tftp server
by ankush grover 27 Feb '08

27 Feb '08

Hi Friends, I am trying to configure a tftp server on Centos 5.0. get command is working fine but not the put command. I searched on the google and tried few things like 777 on /tftpboot, changing ownership to nobody on /tftpboot and also in /etc/xinetd.d/tftp, adding -c as server_args but still the problem persists. tftp -v localhost Connected to localhost.localdomain (127.0.0.1), port 69 tftp> put wine-core-0.9.50-1.el5.rf.i386.rpm putting wine-core-0.9.50-1.el5.rf.i386.rpm to localhost.localdomain:wine-core-0.9.50-1.el5.rf.i386.rpm [netascii] Error code 1: File not found tftp localhost tftp> get wine-core-0.9.50-1.el5.rf.i386.rpm ls -la /etc/xinetd.d/tftp -rw-r--r-- 1 root root 509 Feb 28 03:09 /etc/xinetd.d/tftp cat /etc/xinetd.d/tftp | grep -v "#" service tftp { socket_type = dgram protocol = udp wait = yes user = root server = /usr/sbin/in.tftpd server_args = -s /tftpboot disable = no per_source = 11 cps = 100 2 flags = IPv4 } rpm -qa | grep tftp tftp-server-0.42-3.1.el5.centos tftp-0.42-3.1.el5.centos Please let me know if you need any further inputs. Thanks & Regards Ankush

3 3

Re: [CentOS] Xen or VMWARE on CentOS 5
by Ross S. W. Walker 27 Feb '08

27 Feb '08

I'm not a big fan of Redhat's version of Xen and use the Xen 3.2 packages from xen.org as it has better management features through 'xm'. You will need to compile your own for 64-bit though as they only provide 32-bit binaries by default and if you want to run Xen as a hosting server you really must use 64-bit, but thankfully they provide the SRPM for it which makes that trivial. As far as VMware goes. It works exactly as it does on Redhat Enterprise Linux, so if you go over to the VMware forums and search RHEL, those comments should apply equally well to CentOS. -Ross ----- Original Message ----- From: centos-bounces(a)centos.org <centos-bounces(a)centos.org> To: CentOS mailing list <centos(a)centos.org> Sent: Wed Feb 27 07:12:04 2008 Subject: [CentOS] Xen or VMWARE on CentOS 5 Does anyone out there have a comprehensive tutorial on installing VMware and successfully managing virtual machines with either xen or vmware? ______________________________________________________________________ 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 2

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

27 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. CESA-2008:0161 Important CentOS 5 x86_64 cups - security update (Johnny Hughes) 2. CESA-2008:0161 Important CentOS 5 i386 cups - security update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Tue, 26 Feb 2008 08:54:28 -0600 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2008:0161 Important CentOS 5 x86_64 cups - security update To: CentOS-Announce <centos-announce(a)centos.org> Message-ID: <47C42824.8080706(a)centos.org> Content-Type: text/plain; charset="iso-8859-1" CentOS Errata and Security Advisory 2009:0161 https://rhn.redhat.com/errata/RHSA-2008-0161.html The following updated files have been uploaded and are currently syncing to the mirrors: x86_64: cups-1.1.22-0.rc1.9.20.2.el4_6.5.x86_64.rpm cups-devel-1.1.22-0.rc1.9.20.2.el4_6.5.x86_64.rpm cups-libs-1.1.22-0.rc1.9.20.2.el4_6.5.i386.rpm cups-libs-1.1.22-0.rc1.9.20.2.el4_6.5.x86_64.rpm src: cups-1.1.22-0.rc1.9.20.2.el4_6.5.src.rpm

1 0

Mono installation
by Roilan Cardoso Sánchez 27 Feb '08

27 Feb '08

Hello everybody I´m trying to install mono and when i try to install the package libgdiplus throw the following error dependencies with libexif.so.9 and libungif.so.4. Im using local packages, i downloaded it from the redhat mono repository, I try with the bin installer in others distro mono repo and It throw the deps error with packages libgailutil.so.17 and libglitz.so.1 Finally I try with the centos extra respository and when i try to install libgdiplus it throw a dependecy error with lifgif.so.4 plaese can any body help me note: i need to install it from local rpms, not online regards Roilan ______________________________________________ ¿Con Mascota por primera vez? Sé un mejor Amigo. Entra en Yahoo! Respuestas http://es.answers.yahoo.com/info/welcome

4 4

Logwatch showing entries for non existent services
by Joseph L. Casale 27 Feb '08

27 Feb '08

I had removed Exim and installed Postfix yet Logwatch still shows an empty Exim section? Why is that still in the output? Thanks! jlc

3 5

SAMBA is driving me crazy
by scaglietti amore 26 Feb '08

26 Feb '08

hi guys i have CentOS-5.1 with samba-3.0.25b-0.el5.4 and i took this workin well smb.conf from slackware12 ( commands to be done befor this ): # useradd wbc -c /home/wbc -g users# smbpasswd -a wbc# mkdir /export# chmod u+rwx,g+rx,o+rx /export# chown wbc.users /export the conf file:[global]workgroup = WORKGROUPnetbios name = sanshirosecurity = share [share]comment = Datapath = /exportforce user = wbcforce group = usersread only = noguest ok = Yes _______ and it never worked and i tried to edit the original smb.conf like this: [global] workgroup = WORKGROUPserver string = storagenetbios name = sanshirointerfaces = lo eth2hosts allow = 127. 10.0.0. # logs split per machine log file = /var/log/samba/%m.log# max 50KB per log file, then rotate max log size = 50 security = share # A publicly accessible directory, but read only, except for people in# the "users" group [public] comment = Data path = /samba/Data/ #owened by wbc.users public = yes writable = yes read only = no printable = no write list = users_________ NOW my issue that whenever i try to copy something to the share folder i get "access denied" make sure OR sometimes when i modifie it a little i get things copied but with 0kB sized. i'v been trying for 2 weeks . i couldnt know whats missing. THANX for any help . _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

11 21

mapper device perms on reboot
by Scott Moseman 26 Feb '08

26 Feb '08

How can I get the mapper device permissions set on reboot? When I attempted to try this... # cat /etc/udev/permissions.d/50-udev.permissions | grep mapper mapper/mpath*:oracle:dba:0660 But it did not seem to work... # ls -l /dev/mapper/mpath* brw-rw---- 1 root disk 253, 2 Feb 26 20:56 /dev/mapper/mpath0 brw-rw---- 1 root disk 253, 5 Feb 26 20:56 /dev/mapper/mpath0p1 brw-rw---- 1 root disk 253, 3 Feb 26 20:56 /dev/mapper/mpath1 brw-rw---- 1 root disk 253, 4 Feb 26 20:56 /dev/mapper/mpath1p1 Am I doing something wrong? Is there another way to do this? Thanks, Scott

1 0

/etc/sysconfig/iptables on a stock CentOS 5 install
by Tom Laramee 26 Feb '08

26 Feb '08

Greetings: i have a pretty stock CentOS 5 machine with ports 80 and 22 exposed, so my /etc/sysconfig/iptables file is pretty standard/straightforward. my question is: how is this config file initially generated? i'd like to re-create it, and add a couple of rules .... so i don't want to lose what's in there already. i see that my /etc/sysconfig/system-config-securitylevel has three entries, which explains how the port 80 and 22 rules get into the config: --enabled --port=22:tcp --port=80:tcp ... and i see the basic /etc/sysconfig/iptables-config file, but i'm unclear as to how the rest of the stuff gets in there: e.g.: # Firewall configuration written by system-config-securitylevel # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A FORWARD -j RH-Firewall-1-INPUT -A RH-Firewall-1-INPUT -i lo -j ACCEPT -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT -A RH-Firewall-1-INPUT -p 50 -j ACCEPT -A RH-Firewall-1-INPUT -p 51 -j ACCEPT -A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT -A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT -A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 - j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 80 - j ACCEPT -A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited COMMIT

2 1

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

26 Feb '08

Ray Van Dolson please email me at bob8221(a)gmail.com. -- Bob Taylor

1 0

Re: [CentOS-announce] CESA-2008:0161 Important CentOS 5 i386 cups - security update
by William L. Maltby 26 Feb '08

26 Feb '08

On Tue, 2008-02-26 at 08:54 -0600, Johnny Hughes wrote: > CentOS Errata and Security Advisory 2009:0161 > > https://rhn.redhat.com/errata/RHSA-2008-0161.html > > The following updated files have been uploaded and are currently > syncing to the mirrors: > > i386: > cups-1.1.22-0.rc1.9.20.2.el4_6.5.i386.rpm > cups-devel-1.1.22-0.rc1.9.20.2.el4_6.5.i386.rpm > cups-libs-1.1.22-0.rc1.9.20.2.el4_6.5.i386.rpm Uh-oh! Looks like I messed up somewhere. $ yum list cups\* <snippity> Installed Packages cups.i386 1:1.2.4-11.14.el5_1.4 installed cups-libs.i386 1:1.2.4-11.14.el5_1.4 installed Available Packages cups-devel.i386 1:1.2.4-11.14.el5_1.4 updates cups-lpd.i386 1:1.2.4-11.14.el5_1.4 updates $ rpm -q cups cups-1.2.4-11.14.el5_1.4 Fully up-to-date CentOS5. AFAIR, I used what CentOS5 delivers. Oh wait! I just noticed the repo tag - el4! <*whew*> Subject line got me. > <snip> TIA -- Bill

2 1

auto seek a server
by Jerry Geis 26 Feb '08

26 Feb '08

Hi all, When putting multiple centos 5.1 boxes on a network (DHCP for network) and 1 centos 5.1 server is there a way that these clients can automatically "seek" the server. Is there something in centso 5.1 that an inquiry can be sent out that says: Is there a "Product XYZ" on this network? And the server - and not all the clients - can respond to this quiry. Just wondering, trying to reduce my setup time... Jerry

3 5

Re: [CentOS] Mono installation
by Roilan Cardoso Sánchez 26 Feb '08

26 Feb '08

I do it, but when i try to install gdiplus it thow and depes error with libgif.so.4 and i cant find it in centos extras ----- Mensaje original ---- De: Akemi Yagi <amyagi(a)gmail.com> Para: CentOS mailing list <centos(a)centos.org> Enviado: martes, 26 de febrero, 2008 13:19:18 Asunto: Re: [CentOS] Mono installation On Tue, Feb 26, 2008 at 9:29 AM, Roilan Cardoso Sánchez <neptuno_000(a)yahoo.es> wrote: > > Hello everybody > > I´m trying to install mono and when i try to install the package libgdiplus > throw the following error dependencies with libexif.so.9 and libungif.so.4. > Im using local packages, i downloaded it from the redhat mono repository, I > try with the bin installer in others distro mono repo and It throw the deps > error with packages libgailutil.so.17 and libglitz.so.1 > Finally I try with the centos extra respository and when i try to install > libgdiplus it throw a dependecy error with lifgif.so.4 > > plaese can any body help me > > note: i need to install it from local rpms, not online > > regards Roilan If you cannot install using yum from the CentOS repository, then go to: http://mirror.centos.org/centos/5/extras/ All mono-related rpms are in there. Akemi _______________________________________________ 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

1 0

Re: [CentOS] Lost my win dual boot
by David G. Miller 26 Feb '08

26 Feb '08

Stephen McManus <step77(a)f2s.com> wrote: > Finally got my install working, Centos didn't recognise my m/board NIC > so I had to install another NIC. Now, I've lost the windows install. I > need it for my Walkman and Palm. Never, ever got any distro to see the > Tunsgsten E. I can see the Win in Grub but it says there's a file > missing, insert system disk. Where have I seen that before? > Anyway, how do I get into Grub and what do I need to add to make win > bootable? Win is on sda2 amd Centos is on sda3 + 5. In the grub folder > all it says in the system map is (hd0) /dev/sda. > Nothing else. > Ta. > > Steve. Working grub.conf for dual boot (CentOS 5 and Windows XP Home): # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,2) # kernel /vmlinuz-version ro root=/dev/hda6 # initrd /initrd-version.img #boot=/dev/hda default=0 timeout=5 splashimage=(hd0,2)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-53.1.13.el5) root (hd0,2) kernel /vmlinuz-2.6.18-53.1.13.el5 ro root=LABEL=/ rhgb initrd /initrd-2.6.18-53.1.13.el5.img title CentOS (2.6.18-53.1.6.el5) root (hd0,2) kernel /vmlinuz-2.6.18-53.1.6.el5 ro root=LABEL=/ rhgb initrd /initrd-2.6.18-53.1.6.el5.img title Windoze rootnoverify (hd0,0) chainloader +1 with the following partition table (both Windoze and Linux on the same disk): [dave@spindle ~]# sudo fdisk -l /dev/hda Disk /dev/hda: 100.0 GB, 100030242816 bytes 255 heads, 63 sectors/track, 12161 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 1275 10241406 7 HPFS/NTFS /dev/hda2 1276 1530 2048287+ c W95 FAT32 (LBA) /dev/hda3 1531 1563 265072+ 83 Linux /dev/hda4 1564 12161 85128435 5 Extended /dev/hda5 1564 1824 2096451 82 Linux swap / Solaris /dev/hda6 1825 4435 20972826 83 Linux /dev/hda7 4436 12161 62059063+ 83 Linux Cheers, Dave -- Politics, n. Strife of interests masquerading as a contest of principles. -- Ambrose Bierce

1 0

Re: [CentOS] Squirrelmail Problem on CentOS 4.4
by MOSER, Wilhelm 26 Feb '08

26 Feb '08

Well, easy to solve for non-japaneses find /usr/share/squirremail/functions/mime.php if (!$charset_converted) {... <<< line 316 ... } <<< line 323 and do this (comment it out) /* if (!$charset_converted) {... <<< line 316 ... } <<< line 323 */ Dont know if we run in trouble if we get a japanese charset in a mail but I think the worst case is som char_scramble in the mail view. greez willi

1 0

centos 5.1 install , 3ware raid card...
by Tom Bishop 26 Feb '08

26 Feb '08

Installing a new system using a 3ware card, raid 5 across 4 disks, partition, format went smothly and loaded the apps that I need, but for some reason it appears grub was not installed, or not completely. I am wanting to boot from the array, when installing grub on the loader it asks whether to install MBR on the first partition. Should I use the partition instead of the MBR? When I boot up in rescue mode and go to /boot/grub all I see is splash....no other files. Any suggestions would be welcome...thanks.

4 4

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

26 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. CESA-2008:0153 Important CentOS 3 i386 cups - security update (Tru Huynh) 2. CESA-2008:0153 Important CentOS 3 x86_64 cups - security update (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Mon, 25 Feb 2008 15:49:28 +0100 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2008:0153 Important CentOS 3 i386 cups - security update To: centos-announce(a)centos.org Message-ID: <20080225144928.GA22284(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2008:0153 cups security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2008-0153.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/cups-1.1.17-13.3.51.i386.rpm updates/i386/RPMS/cups-devel-1.1.17-13.3.51.i386.rpm updates/i386/RPMS/cups-libs-1.1.17-13.3.51.i386.rpm source: updates/SRPMS/cups-1.1.17-13.3.51.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update cups\* Tru -- Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

(no subject)
by Ross S. W. Walker 26 Feb '08

26 Feb '08

______________________________________________________________________ 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.

1 0

RE: [CentOS] Huge mailq
by Jason Pyeron 26 Feb '08

26 Feb '08

Let's start with an oops, that messages was sent on Thursday. The queue spiked at 320k messages, then we discovered a name server was down, causing an nfs authentication problem, which caused homedirs to not be deliverable, causing the queue to reach DOS levels, causing the spamfilter to switch off, causing mail not to be delivered... With a little careful loading (beefed up the VM config) we were able to deliver all but 25k in 17 hours. I guess this request was one of the 25k. > -----Original Message----- > From: lists-centos > [mailto:replies-lists-a1z2-centos@listmail.innovate.net] > Sent: Monday, February 25, 2008 20:20 > To: Jason Pyeron > Subject: Re: [CentOS] Huge mailq > > you should start by looking at your maillog to see what's going on. > you should also check to see if you have a sendmail/postfix (whatever > your mta - i'm assuming sendmail because postfix holds its outbound > queue differently) queue process running. > sendmail > entries in the maillog will help you figure out if legit mail is > backing up, and hints as to why, or if you're a spam "gateway". if > the latter, you need to look into the source. e.g., are you an open > relay or do you have web pages that spammers are using. > > it's possible that you have a lot of orphaned df* (data) files, but a > rather large number. > > this is just a start ... > > [by the way, you don't need a "find" to feed to a "wc". a "wc -l qf*" > in the mqueue directory would do the trick.] > Too many thingies on the cmd line error. > - Rick > > > > ------------ Original Message ------------ > > Date: Thursday, February 21, 2008 11:05:45 AM -0500 > > From: Jason Pyeron <jpyeron(a)pdinc.us> > > To: 'CentOS mailing list' <centos(a)centos.org> > > Subject: [CentOS] Huge mailq > > > > Where should we start on preventing this type of problem? > > > > [root@server34 mqueue]# find | wc -l > > 185259 > > > > -jason > > > ---------- End Original Message ---------- > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited.

1 0

Yum-updatesd not functioning
by Damien Solodow 25 Feb '08

25 Feb '08

I have a couple of CentOS 5.1 boxes, mostly i386, but a couple x86_64, some real, some virtual. On all of them, I have yum-updatesd configured to emit via email to root. Here is a sample yum-updatesd.conf from one of them: [main] # how often to check for new updates (in seconds) run_interval = 14400 # how often to allow checking on request (in seconds) updaterefresh = 600 # how to send notifications (valid: dbus, email, syslog) emit_via = email email_from = root@FQDN (the real server FQDN is in the file) # should we listen via dbus to give out update information/check for # new updates dbus_listener = yes # automatically install updates do_update = no # automatically download updates do_download = no # automatically download deps of updates do_download_deps = no None of the servers notified me of the batch of updates that came out this weekend. Running 'service yum-updatesd status' on each of them showed it as running, yet a 'yum update' showed the available updates. I tried running yum-updatesd manually on each, and after loading the plugins (installonlyn and priorities) it appears to hang or pause but no messages were generated either on console, /var/log/messages or email. Any idea what gives? Damien Solodow Senior Network Administrator REVERSE 911(r) 6720 Parkdale Place Indianapolis, IN 46254 317-713-8602 Direct 317-631-6585 Fax www.reverse911.com <http://www.reverse911.com/> www.plantcml.com <http://www.plantcml.com/>

1 0

How to speed up Rsync transfers
by Dan Carl 25 Feb '08

25 Feb '08

Is there a way to speed up rsync transfers? I tested the bandwidth with iperf (recommended to me in an earlier post & worked well)its as advertised by my ISP's around 740KB/sec. When I manually run my rsync script with the --progress switch the transfers are around 100KB/sec. I googled this and the only thing I found had to do with the TCP window which I understand to be the limiting factor. But if this is true how can I ftp stuff at 300KB/sec? (someone please enlighten me) I'm backing up jpg files and some days they add 5+GB of images. My goal was to backup the images nightly, but at the 100KB/sec rate that's not possible. Dan

12 23

CentOS 5.1 - equivalent of xorg-x11 ?
by Tom Brown 25 Feb '08

25 Feb '08

Hi If i want to add X to a system after install on CentOS 4 that would be a yum install xorg-x11 etc This package seems to have been renamed in CentOS 5 and i wonder if anyone can tell me what that now is please thanks

4 5

Internet Load Balancing and Failover
by Shawn Everett 25 Feb '08

25 Feb '08

Hi All, Does anyone have any experience connecting two or more DSL/Cable modems to a Linux box to provide load balancing and failover? I've done some googling and found a few resources but very few solid experiences. I'm trying to optimize my LAN->Internet traffic for a bunch of workstations. Shawn

5 4

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

25 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. CESA-2008:0134 Moderate CentOS 3 i386 tcltk - security update (Tru Huynh) 2. CESA-2008:0134 Moderate CentOS 3 x86_64 tcltk - security update (Tru Huynh) ---------------------------------------------------------------------- Message: 1 Date: Sun, 24 Feb 2008 22:38:26 +0100 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2008:0134 Moderate CentOS 3 i386 tcltk - security update To: centos-announce(a)centos.org Message-ID: <20080224213826.GF23114(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2008:0134 tcltk security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2008-0134.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/expect-5.38.0-92.8.i386.rpm updates/i386/RPMS/expect-devel-5.38.0-92.8.i386.rpm updates/i386/RPMS/itcl-3.2-92.8.i386.rpm updates/i386/RPMS/tcl-8.3.5-92.8.i386.rpm updates/i386/RPMS/tcl-devel-8.3.5-92.8.i386.rpm updates/i386/RPMS/tclx-8.3-92.8.i386.rpm updates/i386/RPMS/tix-8.1.4-92.8.i386.rpm updates/i386/RPMS/tk-8.3.5-92.8.i386.rpm updates/i386/RPMS/tk-devel-8.3.5-92.8.i386.rpm addons/i386/RPMS/expectk-5.38.0-92.8.i386.rpm addons/i386/RPMS/tcl-html-8.3.5-92.8.i386.rpm addons/i386/RPMS/tcllib-1.3-92.8.i386.rpm source: updates/SRPMS/tcltk-8.3.5-92.8.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update Tru -- Tru Huynh (mirrors, CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

CentOS serial questions (Hyperterminal equiv and connecting to server via Hyperterminal)
by Rogelio 25 Feb '08

25 Feb '08

I have two serial-related questions (1) What is the CentOS (or *nix) equivalent of Hyperterminal in Windows? Sometimes I'm on a CentOS box and need to, say, console into a Cisco or something. and (2) I have a CentOS server that I may need to transport somewhere and will most likely *not* want to carry around the monitor. Where should I look in connecting to my server via a serial connection? (I'm more on the network end of things, and am hoping for a nudge in the right direction on these two questions)

5 4

About Mono installation
by Roilan Cardoso Sánchez 25 Feb '08

25 Feb '08

Hello everybody I'm trying to install MONO in my Centos 5, I try with the packages and it throw a dependency error, I try to install it with --nodeps and when i try to run MoMA it throw an error that cant find gdi...dll Please can anybody help me to install MONO regards Roilan ______________________________________________ ¿Con Mascota por primera vez? Sé un mejor Amigo. Entra en Yahoo! Respuestas http://es.answers.yahoo.com/info/welcome

7 7

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

24 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. CESA-2008:0157 Important CentOS 5 i386 cups - security update (Johnny Hughes) 2. CESA-2008:0157 Important CentOS 5 x86_64 cups - security update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Sat, 23 Feb 2008 06:03:27 -0600 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2008:0157 Important CentOS 5 i386 cups - security update To: CentOS-Announce <centos-announce(a)centos.org> Message-ID: <47C00B8F.9050301(a)centos.org> Content-Type: text/plain; charset="iso-8859-1" CentOS Errata and Security Advisory 2009:0157 https://rhn.redhat.com/errata/RHSA-2008-0157.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: cups-1.2.4-11.14.el5_1.4.i386.rpm cups-devel-1.2.4-11.14.el5_1.4.i386.rpm cups-libs-1.2.4-11.14.el5_1.4.i386.rpm cups-lpd-1.2.4-11.14.el5_1.4.i386.rpm src: cups-1.2.4-11.14.el5_1.4.src.rpm

1 0

popular open source forum software?
by Robinson Tiemuqinke 24 Feb '08

24 Feb '08

Hi, I plan to setup an forum for my friend and his friends shortly. But before I setup, I would like to know what are the popular open source forum software/packages to look at.. Please advise. Thanks. --Robinson ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

7 7

dovecot/procmail w/maildir format?
by Les Mikesell 23 Feb '08

23 Feb '08

Does anyone have a handy example or howto pointer for the matching config changes needed to make sendmail/procmail deliver in maildir format in home directories and for dovecot to access it there? -- Les Mikesell lesmikesell(a)gmail.com

5 8

Centos Guys: Any estimate of recent torrent savings?
by William L. Maltby 23 Feb '08

23 Feb '08

Just wondering if the community has any stats available from the tracker showing savings from torrent (up|down)loads. I'm seeing *lots* of activity on the live CD. Between that and the two CentOS releases I'm sharing (4 DVD & 1-4, 5 DVD & 1-6) my current session has sent out about 20.3GB. Since I started using it regularly, I think I've sent >= 0.4TB. If some really good numbers were available, it might encourage others when they realize that all this translates to faster syncing of mirrors, faster initial release downloads, reduced costs to the project, etc. I recently increased my cable modem speeds (U.S. $10/mo seemed worth it to me even though I don't get the benefits of the added download speed often - nature of what I do and all that) so I could upload appx. 60KB/s instead of the previous appx. 45KB/s. And the new {lib, r}torrent from rpmforge has DHT capability included, which I activated, and I think is increasing the number of peers/clients with which I see exchanges. I don't know how badly this might cause under-reporting of your stats. Just curious, no big need. -- Bill

2 1

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

23 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. CESA-2008:0110 Moderate CentOS 4 i386 openldap - security update (Johnny Hughes) 2. CESA-2008:0110 Moderate CentOS 4 x86_64 openldap - security update (Johnny Hughes) 3. CESA-2008:0134 Moderate CentOS 3 ia64 tcltk - security update (Pasi Pirhonen) 4. CESA-2008:0110 Moderate CentOS 4 ia64 openldap - security update (Pasi Pirhonen) 5. CESA-2008:0135 Moderate CentOS 4 ia64 tk - security update (Pasi Pirhonen) 6. CESA-2008:0134 Moderate CentOS 3 s390(x) tcltk - security update (Pasi Pirhonen) 7. CESA-2008:0110 Moderate CentOS 4 s390(x) openldap - security update (Pasi Pirhonen) 8. CESA-2008:0135 Moderate CentOS 4 s390(x) tk - security update (Pasi Pirhonen) 9. CESA-2008:0134-01: Moderate CentOS 2 i386 tcltk security update (John Newbigin) 10. CESA-2008:0135 Moderate CentOS 4 x86_64 tk - security update (Johnny Hughes) 11. CESA-2008:0135 Moderate CentOS 4 i386 tk - security update (Johnny Hughes) 12. CESA-2008:0136 Moderate CentOS 5 x86_64 tk - security update (Johnny Hughes) 13. CESA-2008:0136 Moderate CentOS 5 i386 tk - security update (Johnny Hughes) 14. CESA-2008:0110 Moderate CentOS 5 i386 openldap - security update (Johnny Hughes) 15. CESA-2008:0110 Moderate CentOS 5 x86_64 openldap - security update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Fri, 22 Feb 2008 07:54:12 -0600 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2008:0110 Moderate CentOS 4 i386 openldap - security update To: CentOS-Announce <centos-announce(a)centos.org> Message-ID: <47BED404.5060905(a)centos.org> Content-Type: text/plain; charset="iso-8859-1" CentOS Errata and Security Advisory 2009:0110 https://rhn.redhat.com/errata/RHSA-2008-0110.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: compat-openldap-2.1.30-8.el4_6.4.i386.rpm openldap-2.2.13-8.el4_6.4.i386.rpm openldap-clients-2.2.13-8.el4_6.4.i386.rpm openldap-devel-2.2.13-8.el4_6.4.i386.rpm openldap-servers-2.2.13-8.el4_6.4.i386.rpm openldap-servers-sql-2.2.13-8.el4_6.4.i386.rpm src: openldap-2.2.13-8.el4_6.4.src.rpm

1 0

Find files
by centos＠911networks.com 23 Feb '08

23 Feb '08

Hi, I am trying to delete files that are more than 7 days old. When I run it interactively it works, no problem, but it does not run from a file stored in cron.daily. The rest of that daily file runs properly. [The execute bit is on]. I don't see anything in the /var/log/messages. --------------------------------------- #!/bin/bash find /mnt/iog -type f -name '*.tar.gz' -mtime +7 | xarg rm --------------------------------------- Any idea what am I missing? -- Thanks http://www.911networks.com When the network has to work

5 4

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss