Discuss

discuss@lists.centos.org

2 participants
34758 discussions

x86_64 Question
by Alex White 12 Sep '05

12 Sep '05

Hello All, It's time for my stupid question of the year. I just swapped over to an Athlon64 proc. I went to compile a src rpm and it bombs out. Now, rather than have anyone troubleshoot this and add noise to the list, I'm fairly certain what it's been answered before by someone. I tried google and never did see a true answer. what I do see is stuff about mozilla mostly and associated plugins. This isn't solving my problem. Is there some linkage anyone can pass to me that tells me (not necessarily step by step) what options to pass to rpmbuild if I want to build a 32-bit app on the athlon64? I assumed it was --target i686 or somethin' similar but all of the options I've tried with target result in the same failure. Namely: checking for C compiler default output... configure: error: C compiler cannot create executables Or I get the following when passing no options to rpmbuild at all other than building the binary: Invalid configuration `x86_64-unknown-linux-gnu': machine `x86_64-unknown' not recognized I've already managed to build gaim 1.5.0 (as a test) and it builds and installs fine. So I'm confuzzled. I'm sure it's something hugenormously ignorant and dumb on my part. Englighten me please. CentOS-4 (current on all updates) Sincerely, Alex White

2 2

snmp interface values on x86_64?
by Les Mikesell 12 Sep '05

12 Sep '05

I'm trying to graph the interface traffic from centos 3.5 x86_64 boxes using snmp and cacti (running on an x86 box). Everything starts out OK after a reboot, but it looks like after the total traffic out passes 2^32 bytes the values returned in snmp 5-minute rates go crazy. Is this a known bug, and if not, where should it be reported? -- Les Mikesell lesmikesell(a)gmail.com

1 0

One day left to vote for CentOS
by lance＠uklinux.net 12 Sep '05

12 Sep '05

CentOS has been nominated for an award in the Linux User awards. Please vote for CentOS !! Voting finishes tomorrow - 13th September. Please vote at :- http://www.linuxawards.co.uk/index.php You will need to vote for all categories otherwise the vote wont count. Thanks Lance -- uklinux.net - The ISP of choice for the discerning Linux user.

2 1

Re: [Cantos] Boot process slow with RGB quiet on
by Brian T. Brunner 12 Sep '05

12 Sep '05

[quote]"microcode device doesn't exist?"[/quote] Try grepping for 'microcode' in /var/log/messages, try dmesg | grep microcode, either or both may give you the exact text. chkconfig --list | grep microcode may also give you a hit, if yes, the problem is easy to cure: turn off the service (man chkconfig). If these don't give hits, then it's time to build a kernel for your hardware and desires, switching 'microcode' stuff off. Brian Brunner brian.t.brunner(a)gai-tronics.com (610)796-5838 >>> dave(a)tokyocomedy.com 09/12/05 09:31AM >>> If I boot with "rhgb quiet" off, my computer boots in 1 minute and 30 seconds. If I boot with "rhgb quiet" on, my computer boots in 3m11s. That's a long time to wait. Significantly, when booting with "rhgb quiet", right at the moment X takes over, there is a 1m36s pause where the screen is blank except for the hourglass cursor turning around and around. Of course, if my main priority was to simply boot quickly, I would simply remove the "rhgb quiet" option from the boot process. And I'm not opposed to doing that. However, this pause only started happening recently, so I wonder why it exists at all. When booting with "rhgb quiet" off, I tried to look for any errors or indications of a problem, but it seemed to boot mostly without pause or error. There was one message which was like an error warning, which said something about a "microcode device doesn't exist?". But text was moving across the screen quickly and I couldn't write down exactly what it said. Before I give in and remove the "rhgb quiet" option permanently, is there any way I might be able to diagnose and fix this delay problem? I'd rather be telling the computer how to boot, instead of it telling me. Dave _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos ******************************************************************* This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.hubbell.com - Hubbell Incorporated

3 2

CentOS-announce Digest, Vol 7, Issue 9
by centos-announce-request＠centos.org 12 Sep '05

12 Sep '05

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-2005:769-01: Critical CentOS 2 i386 mozilla security update (John Newbigin) ---------------------------------------------------------------------- Message: 1 Date: Mon, 12 Sep 2005 09:22:26 +1000 From: John Newbigin <jnewbigin(a)ict.swin.edu.au> Subject: [CentOS-announce] CESA-2005:769-01: Critical CentOS 2 i386 mozilla security update To: centos-announce(a)centos.org Message-ID: <4324BC32.1060601(a)ict.swin.edu.au> Content-Type: text/plain; charset=us-ascii; format=flowed The following errata for CentOS-2 have been built and uploaded to the centos mirror: RHSA-2005:769-01 Critical: mozilla security update Files available: mozilla-1.7.10-1.1.2.2.i386.rpm mozilla-chat-1.7.10-1.1.2.2.i386.rpm mozilla-devel-1.7.10-1.1.2.2.i386.rpm mozilla-dom-inspector-1.7.10-1.1.2.2.i386.rpm mozilla-js-debugger-1.7.10-1.1.2.2.i386.rpm mozilla-mail-1.7.10-1.1.2.2.i386.rpm mozilla-nspr-1.7.10-1.1.2.2.i386.rpm mozilla-nspr-devel-1.7.10-1.1.2.2.i386.rpm mozilla-nss-1.7.10-1.1.2.2.i386.rpm mozilla-nss-devel-1.7.10-1.1.2.2.i386.rpm More details are available from the RedHat web site at https://rhn.redhat.com/errata/rh21as-errata.html The easy way to make sure you are up to date with all the latest patches is to run: # yum update -- John Newbigin Computer Systems Officer Faculty of Information and Communication Technologies Swinburne University of Technology Melbourne, Australia http://www.ict.swin.edu.au/staff/jnewbigin ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org http://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 7, Issue 9 *********************************************

1 0

CentOS-announce Digest, Vol 7, Issue 8
by centos-announce-request＠centos.org 12 Sep '05

12 Sep '05

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-2005:769 Critical CentOS 4 i386 mozilla - security update (Johnny Hughes) 2. CESA-2005:769 Critical CentOS 4 x86_64 mozilla - security update (Johnny Hughes) 3. CESA-2005:768 Critical CentOS 4 i386 firefox - security update (Johnny Hughes) 4. CESA-2005:768 Critical CentOS 4 x86_64 firefox - security update (Johnny Hughes) 5. CESA-2005:768 Critical CentOS 4 s390(x) firefox - security update (Pasi Pirhonen) 6. CESA-2005:769 Critical CentOS 3 s390(x) mozilla - security update (Pasi Pirhonen) 7. CESA-2005:769 Critical CentOS 3 i386 mozilla - security update (Tru Huynh) 8. CESA-2005:768 Critical CentOS 3 i386 firefox - security update (CENTOSPLUS only) (Tru Huynh) 9. CESA-2005:769 Critical CentOS 3 x86_64 mozilla - security update (Tru Huynh) 10. CESA-2005:768 Critical CentOS 3 x86_64 firefox - security update (CENTOSPLUS only) (Tru Huynh) 11. CESA-2005:769 Critical CentOS 4 s390(x) mozilla - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Sat, 10 Sep 2005 09:04:06 -0500 From: Johnny Hughes <johnny(a)centos.org> Subject: [CentOS-announce] CESA-2005:769 Critical CentOS 4 i386 mozilla - security update To: CentOS-Announce <centos-announce(a)centos.org> Message-ID: <1126361046.3560.9.camel(a)myth.home.local> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2005:769 https://rhn.redhat.com/errata/RHSA-2005-769.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: mozilla-1.7.10-1.4.2.centos4.i386.rpm mozilla-chat-1.7.10-1.4.2.centos4.i386.rpm mozilla-devel-1.7.10-1.4.2.centos4.i386.rpm mozilla-dom-inspector-1.7.10-1.4.2.centos4.i386.rpm mozilla-js-debugger-1.7.10-1.4.2.centos4.i386.rpm mozilla-mail-1.7.10-1.4.2.centos4.i386.rpm mozilla-nspr-1.7.10-1.4.2.centos4.i386.rpm mozilla-nspr-devel-1.7.10-1.4.2.centos4.i386.rpm mozilla-nss-1.7.10-1.4.2.centos4.i386.rpm mozilla-nss-devel-1.7.10-1.4.2.centos4.i386.rpm src: mozilla-1.7.10-1.4.2.centos4.src.rpm

7 7

mounting nfs partition at boot.
by Ajay Sharma 12 Sep '05

12 Sep '05

This seems like another basic question because I always assumed that if I threw something in my /etc/fstab then it will be automatically mounted at boot time (unless I put in the 'noauto' option). But my NFS partition isn't getting mounted, here's the excerpt from my /etc/fstab file, split on the whitespace so it's easier to read: nfs_server:/exports/var/www /var/www nfs rsize=8192,wsize=8192,timeo=14,intr After the server comes up, I can do a simple, 'mount -a' and the partition is alive. Do I need to use something like autofs? I figured I wouldn't need that since there's no reason to unmount this partition. Thanks, Ajay

3 2

is there a utility to tell if the monitor is on or off in CentOS?
by Jerry Geis 12 Sep '05

12 Sep '05

Is am trying to find a utility to tell me if the monitor is physically on or off? DPMS is turn off so the monitor will not be automatically turning off - I just need to know if someone has turned off the monitor in an automated way? I thought the VESA standard would have something like that but I have not found it. Does anyone know a way to do this? Thanks. Jerry

3 2

Installation problem, possibly RAID
by Edward Diener 11 Sep '05

11 Sep '05

I burned a DVD for CentOS 4.1. I booted from it and everything went fine for the graphical screen installation. I choose separate partitions for my /boot (hde6), / (hde9), and swap (hde12) areas. My /boot partition was ext2 and my / partition was ext3. I installed grub in my /boot partition successfully. I have a Boot Loader, System Commander 8.13 which controls the MBR. The installation then nicely ejected my DVD disk, told me to remove any other installation media, and rebooted my machine. It rebooted into System Commander, I chose the CentOS boot partition, and this rebooted me to CentOS without a problem. CentOS now finished its installation steps, among which was setting up a user account, and attempted to bring up the login screen. My screen went dark, the icon went to a waiting/turning icon for a long time, and I said to myself uh-oh. Finally with most of the screen still dark a small message box appeared with an OK button which said: "Can not start the greeter program, you will not be able to log in. This display will be disabled. Try logging in by other means and editing the configuration file." I pressed OK, my screen went into text mode, and repeated lines of: ext3-fs error (device hde9) in start transaction, Journal has aborted. continued to fill the screen. The only way to proceed was to hit the restart button of my computer. My thoughts of possible reasons for the failure are these. My hard drive is off of an HPT 374 Raid controller, without Raid being actually used on it, and is a 160 GB hard drive, 147 GB formatted. The /boot (hde6) partition starts at approximately the 56 GB boundary, the / (hde9) partition starts at approximately the 76 GB, and the swap drive starts at approximately the 106 GB boundary. Is it possible that I needed to turn on LBA32 as an install option, since there was a screen where I could have checked it but did not ? Is it possible that I needed to tell the install, when choosing my partitions for /boot,/, and swap that this was a Raid controller, event though I am not using Raid with it, since I noticed a Raid button on the Disk Druid graphical screen but used Edit instead to set up my partitions ? Is it possible that CentOS either does not support my Raid controller or supports it in some earlier release which does not work properly even when not using Raid, so that I need to install the proper release of it somehow during the installation process ? I am groping for answers but am really hoping that someone has some knowledge of this problem so that I can use CentOS. Everything went well until the final disaster, and I was keen on getting CentOS to install on my computer. I had previously tried FC4 previously but that wouldn't even get past my graphical screen, failing because I have a Matrox P650 video adapter, but CentOS handled it with aplomb. I am a relatively Linux newbie although an experienced software developer and computer user, so if someone could help me get CentOS running it would really be appreciated. Thank you !

5 22

/etc/rc.d/init.d/xfs freezes during boot up
by Ryan Lum 11 Sep '05

11 Sep '05

I have another problem, but I have found a work around. However, I don't know why it works. I was hoping someone could help. With some help from some previous people on the list, I have my CentOS 4 install to work. I had some previous problems with PCMCIA freezing which was caused by my video card. The next thing to freeze was /etc/rc.d/init.d/xfs. My first work around was to linux rescue and remove from the directory which allow me to startup. Although, I executed the script with "xfs start" and it started fine. So, I recopied the script back into the proper directory but added a "sleep 5" at the beginning. The trick worked, but my question is why does it prevent it from hanging.

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss