[CentOS] yum update fails
Hi I have a system that I'm trying to run `yum update` on. It fails with the following error: Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Check Error: file /usr/share/man/man1/xdelta.1.gz from install of xdelta-1.1.4-1.el5.rf conflicts with file from package xdelta-1.1.3-20 file /usr/share/emacs/site-lisp/psvn.el from install of subversion-1.5.5-0.1.el5.rf conflicts with file from package subversion-1.4.2-2.el5 file /usr/share/man/man1/svn.1.gz from install of subversion-1.5.5-0.1.el5.rf conflicts with file from package subversion-1.4.2-2.el5 file /usr/share/man/man1/svnadmin.1.gz from install of subversion-1.5.5-0.1.el5.rf conflicts with file from package subversion-1.4.2-2.el5 file /usr/share/man/man1/svnlook.1.gz from install of subversion-1.5.5-0.1.el5.rf conflicts with file from package subversion-1.4.2-2.el5 file /usr/share/man/man5/svnserve.conf.5.gz from install of subversion-1.5.5-0.1.el5.rf conflicts with file from package subversion-1.4.2-2.el5 file /usr/share/man/man8/svnserve.8.gz from install of subversion-1.5.5-0.1.el5.rf conflicts with file from package subversion-1.4.2-2.el5 file /usr/share/xemacs/site-packages/lisp/psvn.el from install of subversion-1.5.5-0.1.el5.rf conflicts with file from package subversion-1.4.2-2.el5 Error Summary - How do I resolve this problem? -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] real SATA RAID
Hi Last week I had a lengthy thread in which someone indicated the my SIL card is a FRAID (don't know if F stands for the F word or Fake, though it doesn't really matter). I want to replace the controller with a controller that Linux will see the RAID1 group as a single HD and not multiple HDs as it happens with the SIL controller. Recommendations anyone? -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DG33BU motherboard
Hi Peter I tried that and it the result is the same: Linux only finds, initializes and uses only 1 core ... :-( Is there anything else I can try to have Linux initialize all 4 cores? -- TIA Paolo On Tue, Feb 3, 2009 at 12:44 PM, Peter Kjellstrom c...@nsc.liu.se wrote: On Tuesday 03 February 2009, Paolo Supino wrote: Hi I've installed CentOS 5.2 (i386) in a computer with a DG33BU motherboard ... When I installed it it crashed because of ACPI issues. Searching Google I found that I need to turn ACPI off in order to successfully install CentOS, which I did. After a while I noticed that because of ACPI is off the Linux kernel finds, initializes and uses only 1 CPU core in the Q6600 quad core CPU that is installed in this computer :-( How can I force it to find, initialize and use all the 4 cores in the computer even if ACPI is off? Try to leave ACPI on and boot with pci=nommconf instead. This works on my DG33 (mine is a TL not a BU though). /Peter ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DG33BU motherboard
Hi Agile There's no non SMP kernel in CentOS 5.x (check out: http://wiki.centos.org/FAQ/CentOS5#head-d70935212ce3b7b072b0075c1807a4bd3ea175b7). dmesg boot output (taken from /var/log/dmesg) shows the following lines: Linux version 2.6.18-92.1.22.el5 (mockbu...@builder16.centos.org) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Tue Dec 16 12:03:43 EST and ... found SMP MP-table at 000fe200 Memory for crash kernel (0x0 to 0x0) notwithin permissible range disabling kdump Using x86 segment limits to approximate NX protection On node 0 totalpages: 1048576 DMA zone: 4096 pages, LIFO batch:0 Normal zone: 225280 pages, LIFO batch:31 HighMem zone: 819200 pages, LIFO batch:31 DMI 2.4 present. Using APIC driver default Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: Product ID: APIC at: 0xFEE0 Processor #0 6:15 APIC version 20 Enabling APIC mode: Flat. Using 0 I/O APICs BIOS bug, no explicit IRQ entries, using default mptable. (tell your hw vendor) Processors: 1 Allocating PCI resources starting at d200 (gap: d000:2000) Detected 2400.268 MHz processor. Built 1 zonelists. Total pages: 1048576 Kernel command line: ro root=LABEL=/ acpi=off mapped APIC to d000 (fee0) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c074c000 soft=c072c000 PID hash table entries: 4096 (order: 12, 16384 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 3353184k/4194304k available (2097k kernel code, 40176k reserved, 877k data, 228k init, 2477052k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4802.07 BogoMIPS (lpj=2401035) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfebfbff 2000 e3bd 0001 CPU: After vendor identify, caps: bfebfbff 2000 e3bd 0001 monitor/mwait feature present. using mwait in idle threads. CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 CPU: After all inits, caps: bfebf3ff 2000 0940 e3bd 0001 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 14k freed CPU0: Intel(R) Core(TM)2 Quad CPUQ6600 @ 2.40GHz stepping 0b Total of 1 processors activated (4802.07 BogoMIPS). Brought up 1 CPUs . . . . . Unfortunately I still have only 1 core used ... -- TIA Paolo On Tue, Feb 3, 2009 at 1:12 PM, Agile Aspect agile.asp...@gmail.com wrote: Paolo Supino wrote: Hi Peter I tried that and it the result is the same: Linux only finds, initializes and uses only 1 core ... :-( Is there anything else I can try to have Linux initialize all 4 cores? You're probably booting the single CPU kernel. Try booting the kernel ending with -ELsmp. -- Article. VI. Clause 3 of the constitution of the United States states: The Senators and Representatives before mentioned, and the Members of the several State Legislatures, and all executive and judicial Officers, both of the United States and of the several States, shall be bound by Oath or Affirmation, to support this Constitution; but no religious Test shall ever be required as a Qualification to any Office or public Trust under the United States. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DG33BU motherboard
Hi Ralph Which brings me back to my original post: how do I enable multicore on a DG33BU motherboard, booting with pci=nommconf didn't change the situation :-( -- TIA Paolo On Tue, Feb 3, 2009 at 1:40 PM, Ralph Angenendt ra+cen...@br-online.dera%2bcen...@br-online.de wrote: Agile Aspect wrote: Paolo Supino wrote: Hi Peter I tried that and it the result is the same: Linux only finds, initializes and uses only 1 core ... :-( Is there anything else I can try to have Linux initialize all 4 cores? You're probably booting the single CPU kernel. Try booting the kernel ending with -ELsmp. All CentOS 5 kernels are SMP kernels, there is no ELsmp kernel anymore. Problem really seems to be missing ACPI functionality which leads to the problem that only one core is found. Ralph ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] sound problem
Hi I have CentOS 5.2 installed on a computer (the same one that I just posted a message on: Intel DG33BU motherboard) and for even though audio is reported to be found and working Linux just doesn't play anything through the speakers. The computer dual boots Linux/Windows and when in Windows sound works great, so it's strictly a Linux problem. Can anyone try and help me find out where the problem is and resolve it. -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DG33BU motherboard
Hi Ralph You're right and I'm partially wrong: I changed /boot/grub/menu.lst from acpi=off to pci=nommconf and rebooted the system expecting it to come up with the new command line parameters. As you've shown me in the paste of the dmesg output I posted this isn't the case. Which makes me wonder, and ask, where does it take the boot parameters from if not from /boot/grub/menu.lst? -- TIA Paolo On Tue, Feb 3, 2009 at 1:46 PM, Ralph Angenendt ra+cen...@br-online.dera%2bcen...@br-online.de wrote: Paolo Supino wrote: Kernel command line: ro root=LABEL=/ acpi=off Unfortunately I still have only 1 core used ... As said: Try with pci=nommconf only. And please trim your mails :) Cheers, Ralph ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DG33BU motherboard
Hi Here's my /boot/grub/grub.conf content: grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You do not have a /boot partition. This means that # all kernel and initrd paths are relative to /, eg. # root (hd0,0) # kernel /boot/vmlinuz-version ro root=/dev/mapper/sil_aibhcbccdhagp1 # initrd /boot/initrd-version.img #boot=/dev/mapper/sil_aibhcbccdhag default=0 timeout=10 splashimage=(hd0,0)/boot/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.18-92.1.22.el5) root (hd0,0) kernel /boot/vmlinuz-2.6.18-92.1.22.el5 ro root=LABEL=/ pci=nommconf initrd /boot/initrd-2.6.18-92.1.22.el5.img title CentOS (2.6.18-92.el5) root (hd0,0) kernel /boot/vmlinuz-2.6.18-92.el5 ro root=LABEL=/ pci=nommconf initrd /boot/initrd-2.6.18-92.el5.img As you can see there's no mentioning of acpi=off anywhere and unless I stop it and change the command line parameter from acpi=off to pci=nommconf it still boots with acpi=off ... :-( -- TIA Paolo On Tue, Feb 3, 2009 at 3:23 PM, Toby Bluhm t...@alltechmedusa.com wrote: Paolo Supino wrote: Hi Peter The symlinks aren't broken: the grub.conf file is located in /boot/grub/. /etc/grub/menu.lst points to it and so does /etc/grub.conf ... [r...@server grub]# ls -l /etc/grub.conf /boot/grub/menu.lst /boot/grub/grub.conf -rw--- 1 root root 974 Feb 3 13:59 /boot/grub/grub.conf lrwxrwxrwx 1 root root 11 Dec 15 10:04 /boot/grub/menu.lst - ./grub.conf lrwxrwxrwx 1 root root 22 Dec 15 10:04 /etc/grub.conf - ../boot/grub/grub.conf Typically there's more than one kernel version installed with corresponding lines in grub.conf. Perhaps you're not booting the kernel entry you think you are? Check your default= line. -- tkb ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DG33BU motherboard
Hi William You're right ... I do have 2 HDs and my root is not what I thought it is! Here is what is happening with this system: It has a SIL SATA RAID0/1 card installed with 2x 160GB SATA HDs connected to it. The card is configured to mirror between the HDs (RAID1). But as I saw now Linux actually sees both HDs twice as dmesg shows: SCSI subsystem initialized libata version 3.00 loaded. sata_sil :06:00.0: version 2.3 ACPI: PCI Interrupt :06:00.0[A] - GSI 21 (level, low) - IRQ 66 scsi0 : sata_sil scsi1 : sata_sil ata1: SATA max UDMA/100 mmio m...@0xe0004800 tf 0xe0004880 irq 66 ata2: SATA max UDMA/100 mmio m...@0xe0004800 tf 0xe00048c0 irq 66 ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) ata1.00: ATA-7: WDC WD1600AAJS-00PSA0, 05.06H05, max UDMA/133 ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32) ata1.00: configured for UDMA/100 ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) ata2.00: ATA-7: WDC WD1600AAJS-00PSA0, 05.06H05, max UDMA/133 ata2.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32) ata2.00: configured for UDMA/100 Vendor: ATA Model: WDC WD1600AAJS-0 Rev: 05.0 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: drive cache: write back SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: drive cache: write back sda: sda1 sda2 sda3 sda4 sd 0:0:0:0: Attached scsi disk sda Vendor: ATA Model: WDC WD1600AAJS-0 Rev: 05.0 Type: Direct-Access ANSI SCSI revision: 05 SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB) sdb: Write Protect is off sdb: Mode Sense: 00 3a 00 00 SCSI device sdb: drive cache: write back SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB) sdb: Write Protect is off sdb: Mode Sense: 00 3a 00 00 SCSI device sdb: drive cache: write back sdb: sdb1 sdb2 sdb3 sdb4 sd 1:0:0:0: Attached scsi disk sdb /etc/fstab looks for root on /dev/sdb1, while grub looks (and finds) it's configuration (hd0,0) which corresponds to sda1. The thing that strikes me is that the mirror works for grub (as it only sees 1 HD), but doesn't work for Linux. This defeats the purpose of having a RAID1 to begin with :-( Unlike your scenario this system was installed from scratch (CentOS is the only install) and it was done after the mirror was setup in SIL card bios. BTW: the SIL card boot messages claims that the mirror set is valid and active. I will hace to check into this. -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] sound problem
Hi I can't wait until CentOS 5.3 is released :-( The bigger issue is that I also have windows xp running as a guest inside a vmware server (version 2) and since vmware doesn't discover the audio devices properlly (because linux claims to not have them), there's no sound in Windows ... -- TIA Paolo On Tue, Feb 3, 2009 at 1:25 PM, Ned Slider n...@unixmail.co.uk wrote: Paolo Supino wrote: Hi I have CentOS 5.2 installed on a computer (the same one that I just posted a message on: Intel DG33BU motherboard) and for even though audio is reported to be found and working Linux just doesn't play anything through the speakers. The computer dual boots Linux/Windows and when in Windows sound works great, so it's strictly a Linux problem. Can anyone try and help me find out where the problem is and resolve it. Check your mixer settings aren't just muted. Otherwise you probably need updated alsa drivers. CentOS-5.3 will contain an updated alsa so if you can hold off for a few weeks until the release of 5.3 and see if it works once updated. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Intel DG33BU motherboard
Hi I've installed CentOS 5.2 (i386) in a computer with a DG33BU motherboard ... When I installed it it crashed because of ACPI issues. Searching Google I found that I need to turn ACPI off in order to successfully install CentOS, which I did. After a while I noticed that because of ACPI is off the Linux kernel finds, initializes and uses only 1 CPU core in the Q6600 quad core CPU that is installed in this computer :-( How can I force it to find, initialize and use all the 4 cores in the computer even if ACPI is off? -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DG33BU motherboard
Hi Peter The symlinks aren't broken: the grub.conf file is located in /boot/grub/. /etc/grub/menu.lst points to it and so does /etc/grub.conf ... [r...@server grub]# ls -l /etc/grub.conf /boot/grub/menu.lst /boot/grub/grub.conf -rw--- 1 root root 974 Feb 3 13:59 /boot/grub/grub.conf lrwxrwxrwx 1 root root 11 Dec 15 10:04 /boot/grub/menu.lst - ./grub.conf lrwxrwxrwx 1 root root 22 Dec 15 10:04 /etc/grub.conf - ../boot/grub/grub.conf -- TIA Paolo On Tue, Feb 3, 2009 at 3:07 PM, Peter Kjellstrom c...@nsc.liu.se wrote: On Tuesday 03 February 2009, Paolo Supino wrote: Hi Ralph You're right and I'm partially wrong: I changed /boot/grub/menu.lst from acpi=off to pci=nommconf and rebooted the system expecting it to come up with the new command line parameters. As you've shown me in the paste of the dmesg output I posted this isn't the case. Which makes me wonder, and ask, where does it take the boot parameters from if not from /boot/grub/menu.lst? On CentOS the grub config file is /boot/grub/grub.conf. There are normally two symlinks pointing to this, /etc/grub.conf and /boot/grub/menu.lst. If your /boot/grub/menu.lst is broken (now a file not a symlink) then this is expected behaviour. Check it out with the file command. /Peter ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Intel DG33BU motherboard
Hi William I didn't trun acpi back on (it's a sure way to freeze the computer). I did however find out that Linux ignores the RAID1 that is set by the SIL SATA card I have installed :-( See my last post (just a few minutes ago) with more details. -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Postfix problem
Hi I have a CentOS 4.2 server with postfix. The problem I'm having is that postfix insists on using $myhostname in the from field even if I instruct it to use $mydomain in /etc/postfix/main.cf or even if I hard code the domain name into $myorigin. What am I missing? BTW: postconf shows output shows that $myorigin is configured to use $mydomain, or the domain name itself ... -- ttyl Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Postfix problem
John Plemons wrote: Try installing WebMin and configure Postfix using their interface and see if that works for you... It is menu driven and a quick and easy way to configure your server... john Paolo Supino wrote: Hi I have a CentOS 4.2 server with postfix. The problem I'm having is that postfix insists on using $myhostname in the from field even if I instruct it to use $mydomain in /etc/postfix/main.cf or even if I hard code the domain name into $myorigin. What am I missing? BTW: postconf shows output shows that $myorigin is configured to use $mydomain, or the domain name itself ... -- ttyl Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.173 / Virus Database: 270.8.0/1726 - Release Date: 10/15/2008 7:29 AM ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Webmin is installed and the changes were initially carried out through webmin, but after I noticed that there is no change in the from field I checked to see if webmin changes the right file (it did) and also tried to set main.cf manually (which didn't help). -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Postfix problem
mouss wrote: Paolo Supino a écrit : Hi I have a CentOS 4.2 server with postfix. The problem I'm having is that postfix insists on using $myhostname in the from field even if I Prove that it is postfix that does so, and not Sendmail. show logs. instruct it to use $mydomain in /etc/postfix/main.cf or even if I hard code the domain name into $myorigin. What am I missing? BTW: postconf shows output shows that $myorigin is configured to use $mydomain, or the domain name itself ... ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi I didn't think of checking if Sendmail is the one sending the email or not. I will have to check this out. I will only have access to this server next Wednesday. So until then I can't check anything or post anything ... == TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] PVFS2 RPMs
Hi Where can I find PVFSv2 RPMs for CentOS 5? -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart problems
On Thu, Sep 4, 2008 at 9:52 AM, Romeo Ninov [EMAIL PROTECTED] wrote: Paolo, this problem occur only in RHEL/CentOS/other RH based distros and not in Slack, SuSE, Debian, etc. I was not going deeper in the problem, but that is the reality. BTW: You can play with MAC address in incfg files, but this is applicable only on already installed machine.About Your remarc for corporations and RH - you are right, but how often servers are restarted? :-) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Romeo Not often :-) but I know of thousand of multihomed systems that are installed via kickstart and never heard of issues like the ones you describe and if it was a problem Red Hat would have fixed it a long time ago because it would have seriously heart their bottom line ... -- ttyl Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart problems
On Tue, Sep 2, 2008 at 8:44 PM, Richard Karhuse [EMAIL PROTECTED] wrote: On 9/2/08, Paolo Supino [EMAIL PROTECTED] wrote: : Hi Joseph After sending the last reply I fixed the kickstart config files and added --boot=yes to the network statement of eth0, but going through the consoles of each of the systems to see if the installation completed successfully I found a few that got stuck on the network interface configuration screen (where it asks for IPv4 and IPv6 static/dynamic configuration information: Configure TCP/IP). I've only been half reading this thread, so feel free to ignore this interruption ... Just plug one and only one NIC into the switch Add ksdevice=link to your boot-up line (e.g. syslinux.cfg??). Configure network (if you must) or just let DHCP take over. Kickstart away (works for me on boxes where during anaconda installation the NICs are labeled one way, but CentOS running system does another). Just a thought ... -rak- ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Rak I don't ignore anyone :-) To be on topic: the kernel does receive the parameter ksdevice=bootif from the PXE bootloader. I tried to put eth0 instead of bootif, but it never worked (might be because of other configuration directives). I've pasted the configuration a couple of times in this thread so if you look back at one of the messages you will find the configurations I'm using ... -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart problems
On Wed, Sep 3, 2008 at 5:52 PM, Marco Fretz [EMAIL PROTECTED] wrote: hi, we had the same problem with newer HP pcs and servers (broadcom nics). pxe works well on broadcom, the install not. doesn't matter if you're using kickstart or manual install. the problem was in centos 4.2. after updating the install environment to 4.5 the problem was gone... so it was a driver issue! the install kernel is not exactly the normal linux kernel i think. if anaconda just says that it cannot find install image, etc. the system has no connectivity at this time. hope this is helpful... bests marco Paolo Supino wrote: On Tue, Sep 2, 2008 at 3:07 PM, Romeo Ninov [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Paolo Supino wrote / napísal(a): On Tue, Sep 2, 2008 at 2:17 PM, Romeo Ninov [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Paolo Supino wrote / napísal(a): On Tue, Sep 2, 2008 at 8:14 AM, nate [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Paolo Supino wrote: Hi Nate 3: After the error comes up I get the HTTP setup configuration screen with the source website (in IP) and CentOS directory as I entered them in the pxeconfiguration file and as it appears in the kickstart configuration file and all I have to do is press the 'OK' button to continue the installation to a successful completion. If that's the case the next most likely culprit is url --url http://192.168.11.1/source Just because the PXE boot loader can download the kickstart config does not mean that the installation process will work with that NIC. Also I've had lots of broadcom systems not work with kickstart over the years, it's not uncommon for newer systems to have newer revs of the chipsets and those revs not being supported by the installer. But it sounds like in your case it does work, so I would look at the url above, as it likely is the cause of the problem. Check the http access logs on the server for 404s and similar errors. nate ___ CentOS mailing list CentOS@centos.org mailto:CentOS@centos.org mailto:CentOS@centos.org mailto:CentOS@centos.org mailto:CentOS@centos.org mailto:CentOS@centos.org mailto:CentOS@centos.org mailto:CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Nate After figuring what I was doing wrong (see previous reply ...) I started going through each of my systems in order to boot them and install CentOS 5.2 on each. For the most part it works, but only for the most part? Because once in a few boots (not machine specific) anaconda stops and either asks me what interface it needs to configure or fails to load 'stage2.img' from the web server on 192.168.11.1 http://192.168.11.1 http://192.168.11.1 http://192.168.11.1 ... All cables are good cables. The network switch is a Cisco 3750G with no configuration) and all the NICs are broadcom with firmware 3.8.9. http://3.8.9. http://3.8.9. http://3.8.9. Can you throw a guess where the problem might be lying (I hate inconsistencies)? Have you check apache logs for something. Check also the server messages ___ CentOS mailing list CentOS@centos.org mailto:CentOS@centos.org mailto:CentOS@centos.org mailto:CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Romeo Yes I did, and nothing shows up in either access_log or error_log :-( I just had a node that stopped
Re: [CentOS] kickstart problems
On Wed, Sep 3, 2008 at 11:47 PM, nate [EMAIL PROTECTED] wrote: Paolo Supino wrote: The situation got me so aggravated that I was contemplating resurrecting my old private distro (not going to do that) that does things in a much simpler way. I'm virtually certain it's not using the NIC you think it is, try the other NICs, and find out which NIC maps to which ethernet device and adjust your configs accordingly. This is a VERY common problem. I see it all the time. But if you want to make things hard on yourself that's your choice... nate ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Nate I will check this out (I don't like to leave things hanging in the air) ... I still disagree with what your saying: if this was the case than Linux would (potentially) map ETH devices differently every time a multi NIC system boots. While I've been away from managing Linux systems for a good few years I'm sure this kind of unpredictable behavior would have caused Linux to be thrown out of the window on all multihomed configuration (i.e. firewalls, routers etc ...), and Microsoft to publisize and abuse it against Linux in any of their smear capaigns to the point that it would have been picked up by the leading tech media for me to hear about it. In addtion it would have been a known issue for developers to find work arounds to overcome this debilitating issue. Please don't get angry with me or my point of view. It's not anything personal. If I wrote anything that sounded offensive or personally directed in your direction I apologize. There was definitely no pun from my side. -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart problems
On Wed, Sep 3, 2008 at 11:49 PM, Joseph L. Casale [EMAIL PROTECTED] wrote: This is a VERY common problem. I see it all the time. I also can confirm this *very* typical behavior. Paolo, Remind me what the issue is that prevents you from working through this based on the known existence? Its been muddied somewhere through the thread... jlc ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Joseph Here is my original post: I'm having a problem with setting up a kickstart environment based on CentOS 5.2 x86_64, on a Sun X2200 M2 server (both the server and the client in the kickstart environment are Sun X2200 M2 systems): the first attempt to load stage2.img fails with the error screen: unable to retrieve http://192.168.11.1/source/images/stage2.imghttp://192.168.11.10/source/images/stage2.img. Pressing the OK button brings up the HTTP Setup screen with Website name: 192.168.11.1 http://192.168.11.10/ and CentOS directory: /source if I press OK it successfully loads stage2.img file and continues with the kickstart installation to a successful completion. I checked the apache logs on 192.168.11.1 http://192.168.11.10/ and there is no attempt by the client to even load stage2.img before it prompts for the error. Has anyone encounter this problem and has a solution for it? A few more things I learned since the post: sniffing the network showed that no traffic is received on the server from the requesting client prior to me pressing the 'OK' button in the HTTP setup window. What more I don't think that Linux (or in this case anaconda) will remap ETH devices to NICs on the same run (which is what is described above). 2 more things I found working on the problem during the thread exchange: 1 - eth0 network statement didn't have '--onboot yes' directive. 2 - While PXE was Telling the kernel to autoconfigure eth0. The kickstart configuration file was telling it configure eth0 statically. These 2 issues have been fixed but I still see this happening sporadically. In one of my attempts I did instruct PXE to pass static IP configuration to the kernel, but that worsened the problem and the clients failed to get the kickstart file altogether. My configuration files are as follows: pxe (for node3): default ks prompt 0 label ks kernel vmlinuz append initrd=initrd.img ramdisk_size=9216 ksdevice=bootif noapic acpi=off ks=http://192.168.11.1/kickstart/n03.ks ipappend 2 kickstart file (for node3): # Kickstart file automatically generated by anaconda. install lang en_US.UTF-8 keyboard us network --device eth0 --onboot yes --bootproto dhcp --hostname n003.example.com network --device eth1 --onboot no --bootproto dhcp --hostname n003.example.com network --device eth2 --onboot no --bootproto dhcp --hostname n003.example.com network --device eth3 --onboot no --bootproto dhcp --hostname n003.example.com url --url http://192.168.11.1/source rootpw --iscrypted ? firewall --disabled authconfig --enableshadow --enablemd5 selinux --disabled timezone --utc Asia/Jerusalem bootloader --location=mbr --driveorder=sda --append=noapic acpi=off # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work zerombr clearpart --all --drives=sda part /boot --fstype ext3 --size=100 --ondisk=sda part pv.2 --size=0 --grow --ondisk=sda volgroup VolGroup00 --pesize=32768 pv.2 . . . -- ttyl Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart problems
On Tue, Sep 2, 2008 at 8:14 AM, nate [EMAIL PROTECTED] wrote: Paolo Supino wrote: Hi Nate 3: After the error comes up I get the HTTP setup configuration screen with the source website (in IP) and CentOS directory as I entered them in the pxeconfiguration file and as it appears in the kickstart configuration file and all I have to do is press the 'OK' button to continue the installation to a successful completion. If that's the case the next most likely culprit is url --url http://192.168.11.1/source Just because the PXE boot loader can download the kickstart config does not mean that the installation process will work with that NIC. Also I've had lots of broadcom systems not work with kickstart over the years, it's not uncommon for newer systems to have newer revs of the chipsets and those revs not being supported by the installer. But it sounds like in your case it does work, so I would look at the url above, as it likely is the cause of the problem. Check the http access logs on the server for 404s and similar errors. nate ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Nate I found the problem and it was easier than expected ... The problem seems to be that anaconda has a problem with having a network card statically configured :-( All I had to do is change the bootproto for eth0 from 'static' to 'DHCP'. Now it successfully retrieves 'stage2.img' file from the web server and completes the installation with zero intervention. For the time being this will do, but I'd rather the clients have everything configured locally once when installing than accessing the network for any information they need (this configuration is for a HPC cluster and every network access decreases performance). -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart problems
On Tue, Sep 2, 2008 at 8:14 AM, nate [EMAIL PROTECTED] wrote: Paolo Supino wrote: Hi Nate 3: After the error comes up I get the HTTP setup configuration screen with the source website (in IP) and CentOS directory as I entered them in the pxeconfiguration file and as it appears in the kickstart configuration file and all I have to do is press the 'OK' button to continue the installation to a successful completion. If that's the case the next most likely culprit is url --url http://192.168.11.1/source Just because the PXE boot loader can download the kickstart config does not mean that the installation process will work with that NIC. Also I've had lots of broadcom systems not work with kickstart over the years, it's not uncommon for newer systems to have newer revs of the chipsets and those revs not being supported by the installer. But it sounds like in your case it does work, so I would look at the url above, as it likely is the cause of the problem. Check the http access logs on the server for 404s and similar errors. nate ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Nate After figuring what I was doing wrong (see previous reply ...) I started going through each of my systems in order to boot them and install CentOS 5.2 on each. For the most part it works, but only for the most part? Because once in a few boots (not machine specific) anaconda stops and either asks me what interface it needs to configure or fails to load 'stage2.img' from the web server on 192.168.11.1 ... All cables are good cables. The network switch is a Cisco 3750G with no configuration) and all the NICs are broadcom with firmware 3.8.9. Can you throw a guess where the problem might be lying (I hate inconsistencies)? -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart problems
On Tue, Sep 2, 2008 at 2:17 PM, Romeo Ninov [EMAIL PROTECTED] wrote: Paolo Supino wrote / napísal(a): On Tue, Sep 2, 2008 at 8:14 AM, nate [EMAIL PROTECTED] mailto: [EMAIL PROTECTED] wrote: Paolo Supino wrote: Hi Nate 3: After the error comes up I get the HTTP setup configuration screen with the source website (in IP) and CentOS directory as I entered them in the pxeconfiguration file and as it appears in the kickstart configuration file and all I have to do is press the 'OK' button to continue the installation to a successful completion. If that's the case the next most likely culprit is url --url http://192.168.11.1/source Just because the PXE boot loader can download the kickstart config does not mean that the installation process will work with that NIC. Also I've had lots of broadcom systems not work with kickstart over the years, it's not uncommon for newer systems to have newer revs of the chipsets and those revs not being supported by the installer. But it sounds like in your case it does work, so I would look at the url above, as it likely is the cause of the problem. Check the http access logs on the server for 404s and similar errors. nate ___ CentOS mailing list CentOS@centos.org mailto:CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Nate After figuring what I was doing wrong (see previous reply ...) I started going through each of my systems in order to boot them and install CentOS 5.2 on each. For the most part it works, but only for the most part? Because once in a few boots (not machine specific) anaconda stops and either asks me what interface it needs to configure or fails to load 'stage2.img' from the web server on 192.168.11.1 http://192.168.11.1 ... All cables are good cables. The network switch is a Cisco 3750G with no configuration) and all the NICs are broadcom with firmware 3.8.9. http://3.8.9. Can you throw a guess where the problem might be lying (I hate inconsistencies)? Have you check apache logs for something. Check also the server messages ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Romeo Yes I did, and nothing shows up in either access_log or error_log :-( I just had a node that stopped asking me for IP configuration (twice) and only on the second time (checked on the server using tcpdump) did it actually try to contact the server to retrieve network configuration continue and it successfully retrieved 'stage2.img' from the web server :-( -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart problems
On Tue, Sep 2, 2008 at 3:07 PM, Romeo Ninov [EMAIL PROTECTED] wrote: Paolo Supino wrote / napísal(a): On Tue, Sep 2, 2008 at 2:17 PM, Romeo Ninov [EMAIL PROTECTED] mailto: [EMAIL PROTECTED] wrote: Paolo Supino wrote / napísal(a): On Tue, Sep 2, 2008 at 8:14 AM, nate [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Paolo Supino wrote: Hi Nate 3: After the error comes up I get the HTTP setup configuration screen with the source website (in IP) and CentOS directory as I entered them in the pxeconfiguration file and as it appears in the kickstart configuration file and all I have to do is press the 'OK' button to continue the installation to a successful completion. If that's the case the next most likely culprit is url --url http://192.168.11.1/source Just because the PXE boot loader can download the kickstart config does not mean that the installation process will work with that NIC. Also I've had lots of broadcom systems not work with kickstart over the years, it's not uncommon for newer systems to have newer revs of the chipsets and those revs not being supported by the installer. But it sounds like in your case it does work, so I would look at the url above, as it likely is the cause of the problem. Check the http access logs on the server for 404s and similar errors. nate ___ CentOS mailing list CentOS@centos.org mailto:CentOS@centos.org mailto:CentOS@centos.org mailto:CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Nate After figuring what I was doing wrong (see previous reply ...) I started going through each of my systems in order to boot them and install CentOS 5.2 on each. For the most part it works, but only for the most part? Because once in a few boots (not machine specific) anaconda stops and either asks me what interface it needs to configure or fails to load 'stage2.img' from the web server on 192.168.11.1 http://192.168.11.1 http://192.168.11.1 ... All cables are good cables. The network switch is a Cisco 3750G with no configuration) and all the NICs are broadcom with firmware 3.8.9. http://3.8.9. http://3.8.9. Can you throw a guess where the problem might be lying (I hate inconsistencies)? Have you check apache logs for something. Check also the server messages ___ CentOS mailing list CentOS@centos.org mailto:CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Romeo Yes I did, and nothing shows up in either access_log or error_log :-( I just had a node that stopped asking me for IP configuration (twice) and only on the second time (checked on the server using tcpdump) did it actually try to contact the server to retrieve network configuration continue and it successfully retrieved 'stage2.img' from the web server :-( Paolo, what about DHCP or bootp servers. Check the logs, flush ARP cache from server(s) ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Romeo The more systems I boot the more I'm starting to feel that it's hardware problem related ... I just booted a system in which the ELOM says that NIC0 has 1 MAC address, but when I boot the system I saw on the network a different MAC address altogether ... I'm checking at the lowest level: on the wire (using tcpdump) so if nothing shows in the capture I'm sure I won't find anything in the logs :-( -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart problems
On Tue, Sep 2, 2008 at 4:01 PM, Joseph L. Casale [EMAIL PROTECTED]wrote: Network autoconfiguration failed, most likely there is not a compatible driver for the network card in your system. Paolo, You are using multihomed systems, I remember a problem with pxe booting whereby the install switched to the wrong nic and setup may fail as a result. How are you statring these installs? jlc ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Joseph WHat do you mean? -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart problems
On Tue, Sep 2, 2008 at 4:18 PM, Joseph L. Casale [EMAIL PROTECTED]wrote: WHat do you mean? Do you boot from one of the NICS, or a CD, or what? If you boot from a NIC via a TFTP server, you may be encountering the issue I describe which simply needs a kernel arg to fix you up. jlc ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Joseph I boot via NIC0 and my configurations are as follows: pxe (for node3): default ks prompt 0 label ks kernel vmlinuz append initrd=initrd.img ramdisk_size=9216 ksdevice=bootif noapic acpi=off ks=http://192.168.11.1/kickstart/n03.ks ipappend 2 kickstart file (for node3): # Kickstart file automatically generated by anaconda. install lang en_US.UTF-8 keyboard us network --device eth0 --bootproto dhcp --hostname n003.example.com network --device eth1 --onboot no --bootproto dhcp --hostname n003.example.com network --device eth2 --onboot no --bootproto dhcp --hostname n003.example.com network --device eth3 --onboot no --bootproto dhcp --hostname n003.example.com url --url http://192.168.11.1/source rootpw --iscrypted ? firewall --disabled authconfig --enableshadow --enablemd5 selinux --disabled timezone --utc Asia/Jerusalem bootloader --location=mbr --driveorder=sda --append=noapic acpi=off # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work zerombr clearpart --all --drives=sda part /boot --fstype ext3 --size=100 --ondisk=sda part pv.2 --size=0 --grow --ondisk=sda volgroup VolGroup00 --pesize=32768 pv.2 . . . If you made it all the way down here ... I did try to put ksdevice=eth0 in the PXE configuration file, but it only made things worse :-( -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart problems
On Tue, Sep 2, 2008 at 5:04 PM, nate [EMAIL PROTECTED] wrote: Paolo Supino wrote: I boot via NIC0 and my configurations are as follows: pxe (for node3): Just to rule it out try plugging in all NICs to the same switch/VLAN and kickstart again and see if it works better. Sometimes the NIC detected as eth0 at PXE time is not the same NIC as at installation time. My systems typically have both NICs connected to the same switch(for redundancy using bonding driver) so I often forget about this issue. If it works then you can adjust the kickstart config's ksdevice= option to point to the real NIC your system will use. nate ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Nate It's a nice thing and I thought of doing it, but it's impractical and here is why: I have 42 systems in this cabinet. Each system as 4 NICs and I only have 1 48 port switch. If I had the additional switches to stack I would have done it a long time ago (and I would have sniffed the network to see where the heck it sending the packets). I checked all the systems that did install successfully (right now stands at 29) and in all of them the MAC address of NIC0 matches the MAC address for eth0 in Linux (which makes sense otherwise the install would have hung up). -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart problems
On Tue, Sep 2, 2008 at 5:10 PM, Joseph L. Casale [EMAIL PROTECTED]wrote: I boot via NIC0 and my configurations are as follows: Yeah, that's what I thought. Have a look at: http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Installation_Guide/ch-pxe.html http://kbase.redhat.com/faq/FAQ_80_531.shtm The latter might shed some light. I am thinking you need tweak that a bit. jlc ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Joseph Since I have 4 NICs in each node the kickstart config file has 4 network statements (one for each of the NICs). The --device eth0 appears in the first network statement. The thing that I noticed that is missing in the eth0 network statement is --onboot=yes (in the others it's --onboot=no). Do you thing I should remove the other network statements from the kickstart configuration file? -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart problems
On Tue, Sep 2, 2008 at 5:10 PM, Joseph L. Casale [EMAIL PROTECTED]wrote: I boot via NIC0 and my configurations are as follows: Yeah, that's what I thought. Have a look at: http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Installation_Guide/ch-pxe.html http://kbase.redhat.com/faq/FAQ_80_531.shtm The latter might shed some light. I am thinking you need tweak that a bit. jlc ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos Hi Joseph After sending the last reply I fixed the kickstart config files and added --boot=yes to the network statement of eth0, but going through the consoles of each of the systems to see if the installation completed successfully I found a few that got stuck on the network interface configuration screen (where it asks for IPv4 and IPv6 static/dynamic configuration information: Configure TCP/IP). -- TIA Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] kickstart problems
Hi I'm having a problem with setting up a kickstart environment based on CentOS 5.2 x86_64, on a Sun X2200 M2 server (both the server and the client in the kickstart environment are Sun X2200 M2 systems): the first attempt to load stage2.img fails with the error screen: unable to retrieve http://192.168.11.10/source/images/stage2.img;. Pressing the OK button brings up the HTTP Setup screen with Website name: 192.168.11.10 and CentOS directory: /source if I press OK it successfully loads stage2.img file and continues with the kickstart installation to a successful completion. I checked the apache logs on 192.168.11.10 and there is no attempt by the client to even load stage2.img before it prompts for the error. Has anyone encounter this problem and has a solution for it? -- ttyl Paolo ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] kickstart problems
Hi Nate Autoconfiguration failure makes sense, but it's not a drivers issue: 1: It's a broadcom tg3 driver that is well supported in the kernel. 2: the kernel fetches successfully the kickstart configuration file I supply it in the command line and 3: After the error comes up I get the HTTP setup configuration screen with the source website (in IP) and CentOS directory as I entered them in the pxeconfiguration file and as it appears in the kickstart configuration file and all I have to do is press the 'OK' button to continue the installation to a successful completion. 4. Sniffing the network showed the following: the kernel fetches the kickstart file, fails to fetch 'product.img' file prints out the error message of being unable to fetch 'stage2.img' file and only when I press the 'OK' button in the HTTP setup window actually contacts the HTTP server and successfully fetches 'stage2.img' file. My guess is that my configuration isn't handled properlly by anaconda, I just need to find out where (or change my configuration so that anaconda will handle it properly). I (out of haste of getting this email out) omitted the configuration files I use in the kickstart configuration. So here they are ... pxelinux.cfg/C0A80B02: default ks prompt 0 label ks kernel vmlinuz append initrd=initrd.img ramdisk_size=9216 ksdevice=bootif noapic acpi=off ks=http://192.168.11.1/kickstart/n002.ks ipappend 2 kickstart configuration file: # Kickstart file automatically generated by anaconda. install lang en_US.UTF-8 keyboard us network --device eth0 --bootproto static --ip 192.168.11.2 --netmask 255.255.255.0 --gateway 192.168.11.1 --nameserver=192.168.11.1 --hostname n002.example.com network --device eth1 --onboot no --bootproto dhcp --hostname n002.example.com network --device eth2 --onboot no --bootproto dhcp --hostname n002.example.com network --device eth3 --onboot no --bootproto dhcp --hostname n002.example.com url --url http://192.168.11.1/source rootpw --iscrypted ? firewall --disabled authconfig --enableshadow --enablemd5 selinux --disabled timezone --utc Asia/Jerusalem bootloader --location=mbr --driveorder=sda --append=noapic acpi=off # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work zerombr clearpart --all --drives=sda part /boot --fstype ext3 --size=100 --ondisk=sda . . . On Mon, Sep 1, 2008 at 5:03 PM, nate [EMAIL PROTECTED] wrote: Paolo Supino wrote: Has anyone encounter this problem and has a solution for it? Network autoconfiguration failed, most likely there is not a compatible driver for the network card in your system. If there is a driver disk for that NIC you can use that, what I typically have done in the past is build an updated driver from source and insert it into the installation program which is a fairly complicated process involving extracting the initrd, the modules.cgz inside of it, putting the compatible driver built against the same kernel into the modules config and recompressing the modules file, updating the pci device table for the new device, and rebuilding the initrd. Also adding a step in the %post section to install a compatible driver with whatever kernel the installer ends up installing so when the system reboots it has network connectivity. I also repeat the first part of the process where I insert the kernel, again in the stage 2 netinst.img? file(forgot off hand exactly what the file is called), it may not be required for network drivers, but I think it is for storage drivers, I forget, been a while since I had to do it. nate ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS-virt] problems
Hi I've installed CentOS 5.2 as a guest OS inside VMWare server 1.0.6 running on a Windows XP SP3 (logged in as a local user belonging to the administrator's group). Networking is setup as bridge and the guest OS has it's own IP address (I'm also sitting on a public IP so there is no NAT between the CentOS installation and the Internet). I'm experiencing the following problems: 1. VMWare tools installation failed. First attempt was with the RPM and second attempt was with the tar.gz. In both attempts there were no errors in the installations. 2. I installed Eclipse CDT and it fails to start. It brings up a (what I guess is) alert window, but I can't see what is the warning inside the window because the window doesn't display any text. JRE version installed on the system is 1.6.0_07 installed via Sun's supplied RPM and replacing the Java link in /etc/alternatives 3. After installing VMWare tools I tried changing the screen size from 800x600 to 1024x768 (XP windows size is set to 1280x1024) and now X crashes when it attempts to start (easily fixed by putting screen size back to 800x600, but I don't want to do that). Has anyone encounter similar problems and can help me? -- TIA Paolo ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] 2 more problems
Hi I forgot to write 1 more problem I encountered: 1. I configured a network proxy, but except for Firefox all other applications don't use it (mainly the packager manager) 2. Root's gnome pull down menus (before I crashed X) freeze and can't be used. When tried to restart the session it informed me that there is already a one running and came up without the menus. Has anyone encounter a similar problem? -- TIA Paolo ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
