search for: 20.0.1

A new kernel is available for CentOS-3 https://rhn.redhat.com/errata/RHSA-2004-549.html refers Updated files are :- updates/i386/RPMS/ kernel-2.4.21-20.0.1.EL.athlon.rpm kernel-2.4.21-20.0.1.EL.i686.rpm kernel-BOOT-2.4.21-20.0.1.EL.i386.rpm kernel-doc-2.4.21-20.0.1.EL.i386.rpm kernel-hugemem-2.4.21-20.0.1.EL.i686.rpm kernel-hugemem-unsupported-2.4.21-20.0.1.EL.i686.rpm

Hey all, I have a P4 2.4 GHz CPU (hyper threading) and have been using the 2.4.21-20.EL.c0smp kernel and it works perfectly. I installed the new kernel-smp (2.4.21-20.0.1.EL) kernel and it installed flawlessly. However, every time I boot I get a kernel panic and I must reboot to the older kernel. The error I am getting is: (it seems to be failing on jbd.o and ext3.o) Kernel

Greetings, 4 belated x86_64 updates here for CentOS-3 (I just got my 64-bit development boxes back from a show). They'll be hitting the mirrors eventually. Future updates will be much more timely. libxml2: https://rhn.redhat.com/errata/RHSA-2004-615.html RPMS/libxml2-2.5.10-7.x86_64.rpm RPMS/libxml2-devel-2.5.10-7.x86_64.rpm RPMS/libxml2-python-2.5.10-7.x86_64.rpm

Hi, I am trying to use SAY_DTMF_INTERRUPT with Asterisk 20.0.1. I see that I asked about it here https://www.spinics.net/lists/asterisk/msg174142.html and Sean was nice enough to create a patch. I am trying it on 20.0.1 by doing in the dial plan: CHANNEL(SAY_DTMF_INTERRUPT)=on and I get back: Unknown or unavailable item requested: 'SAY_DTMF_INTERRUPT' When I do: "core show function

Hi All, I wonder if someone can help. My rpm db was corrupted. So I ran rm -f __db* followed rpm rebuild db which ran OK. But I keep getting the following error. error: cannot open Packages database in /var/lib/rpm warning: kernel-source-2.4.21-20.0.1.EL.i386.rpm: V3 DSA signature: NOKEY, key ID 025e513b error: cannot open Packages database in /var/lib/rpm -- Regards JC

Hi people I am new to Xen and having some trouble getting it up and running. I am trying to install it on a Dell Poweredge SC420 that has CentOS (RHEL3 clone) installed. The error that I am getting when I first try to boot into the Xen kernel, after having installed the binary and adding the necessary lines to grub.conf is : ---snip--- md: Autodetecting RAID arrays md: autorun ... md: ...

Hi all, I am having problems to get the SeaLevel IO card to work with CentOS distro. Basically the card is being recognised and shown by lspci BUT /proc/devices file is not updated with the new devices does anyone know why. ? Could someone tell me what/where infos are needed to get /proc/devices to be updated. The reason I require the /proc/devices infos is because I want to run a mknod

Hi people I am new to this list - actually I am one of (probably) a few who are jumping ship from WBEL. I feel like a bit of a scab jumping over at this time - but we all make mistakes eh? I have installed CentOS and ran 'yum update' and installed everything it prompted me for. After a reboot, I realised I had booted into the same original kernel-2.4.21-20.EL.c0smp and not the updated

I've found a problem with CentOS 3 latest kernel (2.4.21-27.0.1.ELsmp) and megaraid2 driver. Hardware: Dell PE1600SC with CERC ATA100 RAID controller The problem is somewhat similar, but not identical as: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=123289 After updating new glibc and kernel packages the new kernel don't boot. Boot fails to mount root fs with "Cannot open

X server, that is (as opposed to my ex-spouse...) Anyway, I was loving life with my rebuilt 2.4.21-9.0.1.EL.c0custom041130a kernel, and then ran "yum update", which gave me a grub line for 2.4.21-20.0.1EL, but the 21-20 not only won't work with the old X settings, I can't get it to set up X at all. I tried running "yum update" from a console on this kernel, but yum