similar to: network card / kudzu

Ulrik wrote: Message: 2 Date: Thu, 23 Sep 2004 14:59:14 +0200 (CEST) From: "Ulrik S. Kofod" <usk at cybersite.dk> To: centos at caosity.org Reply-To: usk at cybersite.dk Subject: [Centos] network card / kudzu When I have installed centOS, Kudzu says my network cards have been removed, and right after it finds them again and asks me to configure them? It looks like it is the

I installed CentOS 4 Beta on an ATA disk to have a look at it, and on the same computer I have a Windows installation on a SATA disk. In the CentOS installation process it could see the operatingsystem on the SATA and everything looked good, it said something like "Other... /dev/sda" (not quite sure, it looked right so I didn't really take note of it). Now when I want to boot the

I installed CentOS 3.3 some time ago and the first thing I did after the install was to run a little script that adds my user plus a few other things. The script adds my user like this USER="ulrik" PASSWD="<mypasswd>" /usr/sbin/adduser $USER -p $PASSWD It seemed to work fine except I couldn't login? I searched Google for reasons why I could only login via ssh as

Redhat has a 'Hardware Discovery Utility' called Kudzu. When I change cards, kudzu pops up and ask to remove/config the card. Most of the time kudzu has trouble recognizing the Digium Zaptel cards and calls them something wrong, like calling the TDM card a network card. I'm having a devil of a time getting 3 TE410P cards to come up with all green lights. For example one or two cards

CentOS Errata and Bugfix Advisory 2011:4813 Upstream details at : http://bugs.centos.org/view.php?id=4813 The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: dfee867bc7f156474437990063967ba5 kudzu-1.2.57.1.26-1.el5.centos.1.x86_64.rpm 9e02a6877840554864be3d404395777d kudzu-devel-1.2.57.1.26-1.el5.centos.1.i386.rpm

Hello I got a nice problem, i don''t know if the i''m put my question a the right place, but anyway.... I have 3 server LINUX with LVS (linux virtual server) I had to recompile my kernel cuz it was not supporting LVS. Since there, everything was going right. Then I''ve change the hard drive of the primairy LVS to an other computer, now i want KUDZU to detect my harware,

I can't choose LILO as boot loader anymore in the install process? And what is the advantages in GRUP vs. LILO that are so great that LILO has been deleted all together? One big disadvantages when forced to use GRUB is that it is a hassle to make the disks in a RAID1 bootable. https://www.redhat.com/archives/fedora-list/2005-March/msg05935.html and RAID1 seems pretty useless when it is the

CentOS Errata and Bugfix Advisory 2011:4813 Upstream details at : http://bugs.centos.org/view.php?id=4813 The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 108ab1d84f723ba8ed01c489b9d33df3 kudzu-1.2.57.1.26-1.el5.centos.1.i386.rpm 9d82d83151f2ca14dc44c06d0d79d4f5 kudzu-devel-1.2.57.1.26-1.el5.centos.1.i386.rpm Source:

How do I get kudzu to still look for new equipment but stop checking to see if some devices are present or not? For example. I have an ATEN USB keyboard/mouse adapter. Sometimes at boot, it is not ready? or something and then kudzu asks if I want that in or not. Of course I want it in!!! I may have to unplug and plug it back in, but don't bother me. I have a similar challenge with

Hi list!: A question about the refinement of the configuration: Always when I start a domain kudzu (hardware detection daemon) ask me for remove hardware. I answer yes, but in the next boot kudzu ask again. I''m guessing that kudzu is asking for remove the «real» drivers that are inside the domU because the domainU was created copying the dom0 system in the domU. How can I deal with

I took the dive and installed the CentosPlus kernel. I remembered that I could always boot with the old kernel if things went south. But on reboot, kudzu wanted to delete the Atheros config. I told it not to, but.... Would a simple 'freshen' of madwifi-0.9.1-24.el4.at.i386.rpm ? an rpm -qa |grep wifi returns: madwifi-kmdl-2.6.9-34.0.2.EL-0.9.1-24.el4.at madwifi-0.9.1-24.el4.at

I have 3 disks that I want to setup in a raid 1, my questions is should I setup the 3rd disk as a spare-disk or should I mirror all 3 disks all the time? Will it perform *much* better to only mirror two and have the 3rd as a spare. Is it not safer to mirror all 3 drives all the time ?

So I have a CentOS 5 machine, which I recently did a 'yum update' on. Everything went fine, but I rebooted as a precaution (just to confront any problems which might arise the first time after an update). And sure enough, when the machine came back up, the network didn't work. Luckilly, someone said (and I quote) 'mv /etc/sysconfig/networking-scripts/ifcfg-eth0.bak

Hallo, the device is working without problems in the dom0, found from parport_pc: dmesg small2 snip: parport_pc: ITE8875 found (1P) parport0: PC-style at 0xf000 [PCSPP,TRISTATE,EPP] parport0: Printer, Kyocera FS-1700+ parport_pc: ITE 8872 parallel port: io=0xF000 parport1: PC-style at 0x378 [PCSPP,TRISTATE] snap to assign this device to a domU I gave the boot-parmaters

I wanted to upgrade my ClamAV but ./configure gave this error checking for zlib installation... /usr configure: error: The installed zlib version may contain a security bug. Please upgrade to 1.2.2 or later: http://www.zlib.net. You can omit this check with --disable-zlib-vcheck but DO NOT REPORT any stablility issues then! but yum gave this message # yum install zlib Gathering header information

I have a CentOS 5.8 box that is dropping packets (just from ping). The network is 8139 RTL-8139/8139C/8139C+ Rev 10 Adding the parameters "pci=noacpi acpi=off " has helped but it still happens. Is there something else that helps the network not drop packets? Thanks, jerry

On my lex mainboard with a Via C3 cpu, xen 2.0(.1) reboots (nearly) immediately without any outputs. The same setup/version boots without problems on a via epia M board with a Via C3-2 cpu (Nehemia), having a rather different chipset. Starting with option noreboot, nobiostables doesn''t change anything visible. Is this a known problem? Or just a knowingly unsupported chipset? Have you

Hi I''ve got a (gentoo) box set up for xen, 2.6.21-xen kernel as per portage about 2 weeks ago. Already got all my guests set up and almost good to go, except for very erratic networking issues. Networking on the domU''s does not always work. I have set up two physical adapters, and bridged both (by use of the modified network-bridge script from the archives) adapters for use

Sorry if this is off topic, but the cpan mail list seems quite ded, and I was wondering if any of you have had the same problem. when ever I do a perl -MCPAN -e "install Bundle::CPAN" I get this error: ---------------------------------- Net::Telnet is up to date. Net::Cmd is up to date. Bundle summary: The following items in bundle Bundle::libnet had installation problems:

Hi Yum has just updated 5 of my Linux boxes running CentOS 4.3 to the 2.6.9-42 kernel. All is well on four of the boxes, but on the fifth the network card (eth0) will not work. I've downgraded the kernel to the previous version and the network card works fine again. I've tried removing and re-installing the new kernel, but the network card won't work with it. The details of the