Discuss

discuss@lists.centos.org

34758 discussions

"near native" performance with xen?
by Johnn Tan 07 Aug '07

07 Aug '07

Just wondering if there was a howto or other URL that explains what is needed to achieve "near native" performance on a xen domU -- for this purpose, I am thinking about a single domU running on a physical server, in comparison to that same physical server running the same kernel but non-xenified. For instance, using a physical partition for VBD v. using a file-backed one is one of the more obvious ones. Assigning all the VCPUs. And as much RAM as you can get away with (maybe leaving the dom0 with 512MB). But are there others? Since I'm doing paravirtualization, I assume I don't need to turn on VT in the BIOS? What about 32-bit v. 64-bit OS, for the dom0 and for the domU? (I'll be using CentOS-5.) Anything else? johnn

4 9

Yum install preferred arch only
by Ross S. W. Walker 07 Aug '07

07 Aug '07

I have a couple 64-bit CentOS 5 installations here and was wondering if there was a yum option to have it install only x86_64 arch by default if no arch is specified. I tired of having to append .x86_64 on all package names I only want the x86_64 versions of, if I want the i386 versions too I would add the .i386 package to the list... Thanks All, Ross S. W. Walker Information Systems Manager Medallion Financial, Corp. 437 Madison Avenue 38th Floor New York, NY 10022 Tel: (212) 328-2165 Fax: (212) 328-2125 WWW: http://www.medallion.com <http://www.medallion.com/> ______________________________________________________________________ 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.

5 8

RE: [CentOS] Adaptec 39320A woes
by Michael St. Laurent 07 Aug '07

07 Aug '07

> Plant, Dean wrote: > > Simple fix, > > > > Adaptec & CentOS = :-( > > LSI & CentOS = :-) > > Which is why after a few hours of testing I decided to indeed buy a > couple of LSI cards to test with -- far better than a lot of > frustration. > > But, meanwhile, I decided to test one more thing: just > suppose that the > SCSI auto-negotiation, which worked fine before, had suddenly given up > in version 3.0 of the aic79xx driver? > > I forced the transfer rate in the Adaptec BIOS for those IDs to the > maximum that my Infortrend could support (U160) and for good measure > disabled "Disconnect" as well. Then, rebooted into 2.6.18-8.1.6&8, and > it worked: User==Goal==Curr==160.0 MB/s. > Apparently, the latest aic79xx driver V3.0 does no longer support > auto-negotiation, whereas all drivers <=1.3.11 did negotiate > correctly. > > Michael, maybe that works for you as well (unless your tapedrive > actually does do U320)? I did the same (changed the speed in the BIOS settings) and it's working. I tried it at 80 but I think I'm going to bump it to 160 and see if it works. I still wish I could figure out why the adaptec kernel driver won't install though. Maybe I'll try downloading the source and manually compiling the kernel module.

1 0

CENTOS 4 and mono
by Jaime Ventura 07 Aug '07

07 Aug '07

Hello, Im trying to configure my centos machine to run webservices. Im using the mono repo from www.*mono*-project.com, for rhel-4. After configuring every thing, it all seemed to work fine with a simple webservice for testing purposes. For that, a friendo of mine created a vb webservice on a windows machine and I copied the all resulting files(asmx, dll, etc). When I access the webservice via GET, every thing works just fine. But when I do a POST, the mod-mono-server2.exe goes away :( Does anyone can help me to debug the problem? The apache logs doesnt help much. Thanks

1 0

Killing a nohup process?
by aaron smith 07 Aug '07

07 Aug '07

Hey All, How can I find processes that were started with nohup and kill them? thanks all Also, is this the right list for that kind of question?

1 0

CentOS 4 vs 5 for VMware?
by Rogelio Bastardo 07 Aug '07

07 Aug '07

For stability reasons, I'm running CentOS 4 for VMware (it's the devil I know). Are there any compelling reasons to upgrade to CentOS 5 for it? I'm relatively new to the whole virtualisation scene and perhaps there are some updated packages that might be good for VMware?

8 17

RE: [CentOS] Adaptec 39320A woes
by Plant, Dean 07 Aug '07

07 Aug '07

Simple fix, Adaptec & CentOS = :-( LSI & CentOS = :-) We spent a few days trying to get Adaptec cards working with LTO-3 drives. It was suggested to me from this list to try an LSI, we bought one, it worked, problem solved. Dean David Groep wrote: > [sorry for breaking the threading, only joined after reading this on > the web] > > Michael St. Laurent wrote: >> I'm having speed problems with the SCSI card we're using to do tape >> backup. It seems to be functioning in 16 bit mode and the current >> thinking is that perhaps it's using a legacy driver instead of the >> correct one. The Adaptec site has a 'driver' for RHEL5 which I've >> downloaded and tried to install but it seems to have a problem >> installing on a CentOS-5 system. > > Hit this same issue with a slightly different configuration, and > although not able to offer a solution, I can at least give some more > boundary conditions. As I see it now, it starts to look like a driver > issue. > > - I found the issue with a 39320 controller on CentOS5/i386, > talking to an Infortrend IFT-7250F enclosure. It should be doing > U160 (Wide, 80 MHz synchonous), but it decays to 3.300 MB/s > transfers. The driver indeed even says the "Goal" is 3.300 MB/s ... > > It is confirmed by the infortrend: it shows asynchonous/narrow as > transfer settings for the SCSI channels after loading the aic79xx > driver. > > - Exchanging the 39320 for a 29320, still on the same machine with > CentOS5/i386, does not change it: still 3.300 MB/s (as confirmed > by the infortrend itself) > > - putting this same 29320, with the same IFT7250F and with the > same cabling, in another machine running CentOS3.7: presto, it > synchonizes again at 160 MB/s (Wide, 80 MHz)! > > - similar Adaptec 29320 and 39320's in a CentOS4/i386 box, connected > to similar Infortrends: work correctly at 160 and 320 MB/s > > - Booting into kernel 2.6.18-8.el5 or 2.6.18-8.1.8.el5 makes no > difference > > For CentOS5, the aic79xx driver is "Version: 3.0". For CentOS3 it's > using driver "1.3.10-RH1", and for the CentOS4 systems, it's "1.3.11". > What changed between 1.3.11 and 3.0? > > At least you're not alone ... > > Regards, > DavidG. > > PS: and indeed, the adaptec driver RPM does not install correctly, > with > the same errors you reported below. > >> [root <at> hcnas modules]# cd /proc/scsi >> [root <at> hcnas scsi]# cat scsi >> Attached devices: >> Host: scsi0 Channel: 00 Id: 08 Lun: 00 >> Vendor: DP Model: BACKPLANE Rev: 1.05 >> Type: Enclosure ANSI SCSI revision: 05 >> Host: scsi0 Channel: 02 Id: 00 Lun: 00 >> Vendor: DELL Model: PERC 5/i Rev: 1.03 >> Type: Direct-Access ANSI SCSI revision: 05 >> Host: scsi1 Channel: 00 Id: 06 Lun: 00 >> Vendor: CERTANCE Model: ULTRIUM 2 Rev: 1914 >> Type: Sequential-Access ANSI SCSI revision: 03 >> Host: scsi1 Channel: 00 Id: 06 Lun: 01 >> Vendor: DELL Model: PV-124T Rev: 0043 >> Type: Medium Changer ANSI SCSI revision: 02 >> Host: scsi3 Channel: 00 Id: 00 Lun: 00 >> Vendor: Dell Model: Virtual CDROM Rev: 123 >> Type: CD-ROM ANSI SCSI revision: 02 >> Host: scsi4 Channel: 00 Id: 00 Lun: 00 >> Vendor: Dell Model: Virtual Floppy Rev: 123 >> Type: Direct-Access ANSI SCSI revision: 02 >> [root <at> hcnas scsi]# ll total 0 >> dr-xr-xr-x 2 root root 0 Aug 3 13:21 aic79xx >> -r--r--r-- 1 root root 0 Aug 3 13:21 device_info >> -r--r--r-- 1 root root 0 Aug 3 13:21 scsi >> dr-xr-xr-x 2 root root 0 Aug 3 13:21 sg >> dr-xr-xr-x 2 root root 0 Aug 3 13:21 usb-storage >> [root <at> hcnas scsi]# cd aic79xx/ >> [root <at> hcnas aic79xx]# ll >> total 0 >> -rw-r--r-- 1 root root 0 Aug 3 13:09 1 >> -rw-r--r-- 1 root root 0 Aug 3 13:09 2 >> [root <at> hcnas aic79xx]# cat 1 >> Adaptec AIC79xx driver version: 3.0 >> Adaptec 39320A Ultra320 SCSI adapter >> aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 101-133Mhz, 512 >> SCBs Allocated SCBs: 4, SG List Length: 128 >> >> Serial EEPROM: >> 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 >> 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 >> 0x09f4 0x0142 0x2807 0x0010 0xffff 0xffff 0xffff 0xffff >> 0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0430 0xb3f3 >> >> Target 0 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Target 1 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Target 2 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Target 3 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Target 4 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Target 5 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Target 6 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Goal: 3.300MB/s transfers >> Curr: 3.300MB/s transfers >> Channel A Target 6 Lun 0 Settings >> Commands Queued 29 >> Commands Active 0 >> Command Openings 1 >> Max Tagged Openings 0 >> Device Queue Frozen Count 0 >> Channel A Target 6 Lun 1 Settings >> Commands Queued 20 >> Commands Active 0 >> Command Openings 1 >> Max Tagged Openings 0 >> Device Queue Frozen Count 0 >> Target 7 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Target 8 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Target 9 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Target 10 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Target 11 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Target 12 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Target 13 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Target 14 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) Target 15 Negotiation Settings >> User: 320.000MB/s transfers (160.000MHz >> RDSTRM|DT|IU|RTI|QAS, 16bit) [root <at> hcnas ~]# rpm -e >> a320raid-3.00.063.5.V580A1-1 [root <at> hcnas ~]# rpm -ivh >> a320raid.rhel5.i686.rpm >> Preparing... >> ########################################### [100%] 1:a320raid >> ########################################### [100%] >> >> Adaptec adp94xx driver installer - V1.2.5934.0-1 >> >> Backing up all modified files to /boot/adp94xx-backup-3 >> >> Using GRUB configuration >> If this is not what you want, rename your /boot/grub/grub.conf file >> /boot -rw------- 1 root root 2403411 Jul 27 14:47 >> initrd-2.6.18-8.1.8.el5.img >> >> /boot/vmlinuz-2.6.18-8.1.8.el5 /boot/initrd-2.6.18-8.1.8.el5.img >> CentOS (2.6.18-8.1.8.el5) Configuration [CentOS (2.6.18-8.1.8.el5)] >> /boot/vmlinuz-2.6.18-8.1.8.el5 -> 2.6.18-8.1.8.el5 >> >> ****** PROBLEM ******* >> No prebuilt module for 2.6.18-8.1.8.el5 i686 >> ********************** >> /boot >> -rw------- 1 root root 2403318 Jul 27 07:39 initrd-2.6.18-8.el5.img >> >> /boot/vmlinuz-2.6.18-8.el5 /boot/initrd-2.6.18-8.el5.img CentOS >> (2.6.18-8.el5) Configuration [CentOS (2.6.18-8.el5)] >> /boot/vmlinuz-2.6.18-8.el5 -> 2.6.18-8.el5 >> >> ****** PROBLEM ******* >> No prebuilt module for 2.6.18-8.el5 i686 >> ********************** >> >> *************************************** >> ******** NO MODULES INSTALLED ********* >> *************************************** >> >> Done. >> error: %post(a320raid-3.00.063.5.V580A1-1.i686) scriptlet failed, >> exit status 1 [root <at> hcnas ~]#

2 1

Re: [CentOS] ipw220 wireless firmware for CentOS 5
by andy.allen＠virgin.net 07 Aug '07

07 Aug '07

Thanks Fabian, There seem to be a number of different ways of installing the ipw2200 firmware and as I've said already I've tried puttting the .fw files into the firmware directory - why doesn't this work? What is actually the best/recommended way of installing the firmware in CentOS 5 please? - not too complicated please as I'm a linux enthusiast but not a great expert! Andy Original Message: ----------------- From: Fabian Arrotin fabian.arrotin(a)arrfab.net Date: Mon, 06 Aug 2007 12:57:28 +0200 To: centos(a)centos.org Subject: Re: [CentOS] ipw220 wireless firmware for CentOS 5 On Mon, 2007-08-06 at 05:33 -0400, andy.allen(a)virgin.net wrote: > OK, I've downloaded and unzipped the firmware files in > ipw2200-fw-3.0.tgz - so I have 4 files: ipw2200-bss.fw, ipw2200-ibss.fw, > ipw2200-sniffer.fw and LICENSE.ipw2200-fw, all of which I've placed in > the /lib/firmware directory. Unfortunately, the instructions in > README.ipw2200 and INSTALL are not clear as to what to do next. I'm > using CentOS 5 on my (Dell) laptop so setting-up wireless networking should > be > reasonably straightforward - shouldn't it? Any help much appreciated - > I'm a real linux fan, but it grieves me to say that, in this case, > "wireless works much > better in Windows XP!" Use the ipw2200-firmware rpm from the RPMForge repo (see http://wiki.centos.org/Repositories) .... Then you'll be able to use/configure the ipw2200 device . You can use for example NetworkManager to automatically configure your network if you have a laptop ... -- Fabian Arrotin <fabian.arrotin(a)arrfab.net> Solution ? echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc -------------------------------------------------------------------- mail2web.com Enhanced email for the mobile individual based on Microsoft® Exchange - http://link.mail2web.com/Personal/EnhancedEmail

2 1

Adaptec 39320A woes
by David Groep 07 Aug '07

07 Aug '07

[sorry for breaking the threading, only joined after reading this on the web] Michael St. Laurent wrote: > I'm having speed problems with the SCSI card we're using to do tape > backup. It seems to be functioning in 16 bit mode and the current > thinking is that perhaps it's using a legacy driver instead of the > correct one. The Adaptec site has a 'driver' for RHEL5 which I've > downloaded and tried to install but it seems to have a problem > installing on a CentOS-5 system. Hit this same issue with a slightly different configuration, and although not able to offer a solution, I can at least give some more boundary conditions. As I see it now, it starts to look like a driver issue. - I found the issue with a 39320 controller on CentOS5/i386, talking to an Infortrend IFT-7250F enclosure. It should be doing U160 (Wide, 80 MHz synchonous), but it decays to 3.300 MB/s transfers. The driver indeed even says the "Goal" is 3.300 MB/s ... It is confirmed by the infortrend: it shows asynchonous/narrow as transfer settings for the SCSI channels after loading the aic79xx driver. - Exchanging the 39320 for a 29320, still on the same machine with CentOS5/i386, does not change it: still 3.300 MB/s (as confirmed by the infortrend itself) - putting this same 29320, with the same IFT7250F and with the same cabling, in another machine running CentOS3.7: presto, it synchonizes again at 160 MB/s (Wide, 80 MHz)! - similar Adaptec 29320 and 39320's in a CentOS4/i386 box, connected to similar Infortrends: work correctly at 160 and 320 MB/s - Booting into kernel 2.6.18-8.el5 or 2.6.18-8.1.8.el5 makes no difference For CentOS5, the aic79xx driver is "Version: 3.0". For CentOS3 it's using driver "1.3.10-RH1", and for the CentOS4 systems, it's "1.3.11". What changed between 1.3.11 and 3.0? At least you're not alone ... Regards, DavidG. PS: and indeed, the adaptec driver RPM does not install correctly, with the same errors you reported below. > [root <at> hcnas modules]# cd /proc/scsi > [root <at> hcnas scsi]# cat scsi > Attached devices: > Host: scsi0 Channel: 00 Id: 08 Lun: 00 > Vendor: DP Model: BACKPLANE Rev: 1.05 > Type: Enclosure ANSI SCSI revision: 05 > Host: scsi0 Channel: 02 Id: 00 Lun: 00 > Vendor: DELL Model: PERC 5/i Rev: 1.03 > Type: Direct-Access ANSI SCSI revision: 05 > Host: scsi1 Channel: 00 Id: 06 Lun: 00 > Vendor: CERTANCE Model: ULTRIUM 2 Rev: 1914 > Type: Sequential-Access ANSI SCSI revision: 03 > Host: scsi1 Channel: 00 Id: 06 Lun: 01 > Vendor: DELL Model: PV-124T Rev: 0043 > Type: Medium Changer ANSI SCSI revision: 02 > Host: scsi3 Channel: 00 Id: 00 Lun: 00 > Vendor: Dell Model: Virtual CDROM Rev: 123 > Type: CD-ROM ANSI SCSI revision: 02 > Host: scsi4 Channel: 00 Id: 00 Lun: 00 > Vendor: Dell Model: Virtual Floppy Rev: 123 > Type: Direct-Access ANSI SCSI revision: 02 > [root <at> hcnas scsi]# ll > total 0 > dr-xr-xr-x 2 root root 0 Aug 3 13:21 aic79xx > -r--r--r-- 1 root root 0 Aug 3 13:21 device_info > -r--r--r-- 1 root root 0 Aug 3 13:21 scsi > dr-xr-xr-x 2 root root 0 Aug 3 13:21 sg > dr-xr-xr-x 2 root root 0 Aug 3 13:21 usb-storage > [root <at> hcnas scsi]# cd aic79xx/ > [root <at> hcnas aic79xx]# ll > total 0 > -rw-r--r-- 1 root root 0 Aug 3 13:09 1 > -rw-r--r-- 1 root root 0 Aug 3 13:09 2 > [root <at> hcnas aic79xx]# cat 1 > Adaptec AIC79xx driver version: 3.0 > Adaptec 39320A Ultra320 SCSI adapter > aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 101-133Mhz, 512 SCBs > Allocated SCBs: 4, SG List Length: 128 > > Serial EEPROM: > 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 > 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 > 0x09f4 0x0142 0x2807 0x0010 0xffff 0xffff 0xffff 0xffff > 0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0430 0xb3f3 > > Target 0 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Target 1 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Target 2 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Target 3 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Target 4 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Target 5 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Target 6 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Goal: 3.300MB/s transfers > Curr: 3.300MB/s transfers > Channel A Target 6 Lun 0 Settings > Commands Queued 29 > Commands Active 0 > Command Openings 1 > Max Tagged Openings 0 > Device Queue Frozen Count 0 > Channel A Target 6 Lun 1 Settings > Commands Queued 20 > Commands Active 0 > Command Openings 1 > Max Tagged Openings 0 > Device Queue Frozen Count 0 > Target 7 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Target 8 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Target 9 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Target 10 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Target 11 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Target 12 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Target 13 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Target 14 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > Target 15 Negotiation Settings > User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|RTI|QAS, > 16bit) > [root <at> hcnas ~]# rpm -e a320raid-3.00.063.5.V580A1-1 > [root <at> hcnas ~]# rpm -ivh a320raid.rhel5.i686.rpm > Preparing... ########################################### > [100%] > 1:a320raid ########################################### > [100%] > > Adaptec adp94xx driver installer - V1.2.5934.0-1 > > Backing up all modified files to /boot/adp94xx-backup-3 > > Using GRUB configuration > If this is not what you want, rename your /boot/grub/grub.conf file > /boot > -rw------- 1 root root 2403411 Jul 27 14:47 initrd-2.6.18-8.1.8.el5.img > > /boot/vmlinuz-2.6.18-8.1.8.el5 /boot/initrd-2.6.18-8.1.8.el5.img CentOS > (2.6.18-8.1.8.el5) > Configuration [CentOS (2.6.18-8.1.8.el5)] > /boot/vmlinuz-2.6.18-8.1.8.el5 -> 2.6.18-8.1.8.el5 > > ****** PROBLEM ******* > No prebuilt module for 2.6.18-8.1.8.el5 i686 > ********************** > /boot > -rw------- 1 root root 2403318 Jul 27 07:39 initrd-2.6.18-8.el5.img > > /boot/vmlinuz-2.6.18-8.el5 /boot/initrd-2.6.18-8.el5.img CentOS > (2.6.18-8.el5) > Configuration [CentOS (2.6.18-8.el5)] > /boot/vmlinuz-2.6.18-8.el5 -> 2.6.18-8.el5 > > ****** PROBLEM ******* > No prebuilt module for 2.6.18-8.el5 i686 > ********************** > > *************************************** > ******** NO MODULES INSTALLED ********* > *************************************** > > Done. > error: %post(a320raid-3.00.063.5.V580A1-1.i686) scriptlet failed, exit > status 1 > [root <at> hcnas ~]# > -- David Groep ** National Institute for Nuclear and High Energy Physics, PDP/Grid group ** ** Room: H1.56 Phone: +31 20 5922179, PObox 41882, NL-1009DB Amsterdam NL **

1 0

kmod-drbd-smp (2.6.9-55.0.2.EL) has unknown symbols (kmod-drbd not).
by Martin Hamant 07 Aug '07

07 Aug '07

Hi ! Not very blocking because the smp module loads perfectly. # yum --exclude=kmod-drbd*\plus\* install kmod-drbd Setting up Install Process Setting up repositories Reading repository metadata in from local files Excluding Packages in global exclude list Finished Reducing CentOS-4 - Plus to included packages only Finished Parsing package install arguments Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package kmod-drbd.i686 0:0.7.24-1.2.6.9_55.0.2.EL set to be updated --> Running transaction check Dependencies Resolved ============================================================================= Package Arch Version Repository Size ============================================================================= Installing: kmod-drbd i686 0.7.24-1.2.6.9_55.0.2.EL extras 472 k Transaction Summary ============================================================================= Install 1 Package(s) Update 0 Package(s) Remove 0 Package(s) Total download size: 472 k Is this ok [y/N]: y Downloading Packages: Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing: kmod-drbd ######################### [1/1] WARNING: /lib/modules/2.6.9-55.0.2.EL/extra/drbd.ko needs unknown symbol _spin_unlock_irq WARNING: /lib/modules/2.6.9-55.0.2.EL/extra/drbd.ko needs unknown symbol _spin_unlock WARNING: /lib/modules/2.6.9-55.0.2.EL/extra/drbd.ko needs unknown symbol _spin_unlock_irqrestore WARNING: /lib/modules/2.6.9-55.0.2.EL/extra/drbd.ko needs unknown symbol _spin_lock_irq WARNING: /lib/modules/2.6.9-55.0.2.EL/extra/drbd.ko needs unknown symbol del_timer_sync WARNING: /lib/modules/2.6.9-55.0.2.EL/extra/drbd.ko needs unknown symbol _spin_lock_irqsave WARNING: /lib/modules/2.6.9-55.0.2.EL/extra/drbd.ko needs unknown symbol _spin_lock Installed: kmod-drbd.i686 0:0.7.24-1.2.6.9_55.0.2.EL Complete! # uname -a Linux *** 2.6.9-55.0.2.EL #1 Tue Jun 26 14:08:18 EDT 2007 i686 i686 i386 GNU/Linux # modprobe drbd FATAL: Error inserting drbd (/lib/modules/2.6.9-55.0.2.EL/extra/drbd.ko): Invalid module format (PS: I think something really needs to be done with the --exclude / plus issue) -- Martin Hamant

5 10

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