I have an old server (old hardware) that's been running 6.4 with kernel
2.6.32-279.19.1.el6.i686, no problem. Except, any kernel update after that
causes it not to boot anymore. All I get is a blinking cursor on the
screen, nothing else.
Is this the end of this hardware, no more kernel updates after this?
For reference, these are all the options that kernel is booting up with
(lines wrapped on purpose):
title CentOS (2.6.32-279.19.1.el6.i686)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-279.19.1.el6.i686 ro \
root=UUID=3f79e6b6-7845-499f-b708-aef782602673 rd_NO_LUKS
rd_NO_LVM \
rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 \
KEYBOARDTYPE=pc KEYTABLE=us noapic apm=off ide=nodma acpi=off \
crashkernel=auto rhgb quiet selinux=0
initrd /boot/initramfs-2.6.32-279.19.1.el6.i686.img
Ashley M. Kirchner wrote:> I have an old server (old hardware) that's been running 6.4 with kernel > 2.6.32-279.19.1.el6.i686, no problem. Except, any kernel update after > that > causes it not to boot anymore. All I get is a blinking cursor on the > screen, nothing else. > > Is this the end of this hardware, no more kernel updates after this? >I *think* I remember that i386 hardware's no longer going to be supported, but I thought that was with a 3.x kernel. I could well be wrong. Do you see the grub line on reboot? If so, delete rhgb and quiet (I hate them, but they're ok for someone who has no clue...), and see what's happening. mark
On Thu, Sep 19, 2013 at 03:15:06PM -0600, Ashley M. Kirchner wrote:> I have an old server (old hardware) that's been running 6.4 with kernel > 2.6.32-279.19.1.el6.i686, no problem. Except, any kernel update after that > causes it not to boot anymore. All I get is a blinking cursor on the > screen, nothing else.Do these processors support PAE? All EL kernels now require PAE.> > Is this the end of this hardware, no more kernel updates after this? > > For reference, these are all the options that kernel is booting up with > (lines wrapped on purpose): > > title CentOS (2.6.32-279.19.1.el6.i686) > root (hd0,0) > kernel /boot/vmlinuz-2.6.32-279.19.1.el6.i686 ro \ > root=UUID=3f79e6b6-7845-499f-b708-aef782602673 rd_NO_LUKS > rd_NO_LVM \ > rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 \ > KEYBOARDTYPE=pc KEYTABLE=us noapic apm=off ide=nodma acpi=off \ > crashkernel=auto rhgb quiet selinux=0 > initrd /boot/initramfs-2.6.32-279.19.1.el6.i686.img > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos-- ---- Fred Smith -- fredex at fcshome.stoneham.ma.us ---------------------------- Do you not know? Have you not heard? The LORD is the everlasting God, the Creator of the ends of the earth. He will not grow tired or weary, and his understanding no one can fathom. ----------------------------- Isaiah 40:28 (niv) -----------------------------
Unless you are just running some home server or something the general idea of servers is to provide uptime. Servers usually start dying after about 3 to 6 years* and, if you are trying to provide uptime, searching around on ebay for someone that has a PATA hard drive, DDR memory or some ancient pcix controller will severely dent this objective. I agree that its a shame that so much of this ends up in landfill. The fact that chassis are not normally immediately reusable is a tragedy in my eyes but running old, junk equipment is even more of a tragedy when it breaks and people are relying on it. *I work a lot in HPC where servers are hammered to death. On 30 November 2013 14:33, Steve Clark <sclark at netwolves.com> wrote:> On 09/24/2013 03:55 PM, Lists wrote: >> On 09/19/2013 08:26 PM, Ashley M. Kirchner wrote: >>> It works for what it does. And I'm completely prepared to freeze it as far >>> as software goes. I was just curious what may have happened after that >>> particular version of the kernel, and whether there's something else I can >>> do, or call it done, slap a red sticker on it that read, "DON'T EVER >>> UPGRADE ANYMORE" and call it done. >>> >> For what it's worth, we have a single-core P3 running the latest >> Centos6/32 without issue. I realize that from a processing power stand >> point my SIP phone is probably faster, but like Ashley, it does a job >> and very well at that. (network monitor) >> >> [root at edison ~]# cat /proc/cpuinfo >> processor : 0 >> vendor_id : GenuineIntel >> cpu family : 6 >> model : 7 >> model name : Pentium III (Katmai) >> stepping : 3 >> cpu MHz : 498.456 >> cache size : 512 KB >> fdiv_bug : no >> hlt_bug : no >> f00f_bug : no >> coma_bug : no >> fpu : yes >> fpu_exception : yes >> cpuid level : 2 >> wp : yes >> flags : fpu vme de pse tsc msr pae mce cx8 mtrr pge mca cmov >> pse36 mmx fxsr sse up >> bogomips : 996.91 >> clflush size : 32 >> cache_alignment : 32 >> address sizes : 36 bits physical, 32 bits virtual >> power management: >> >> [root at edison ~]# cat /proc/version >> Linux version 2.6.32-358.18.1.el6.i686 >> (mockbuild at c6b10.bsys.dev.centos.org) (gcc version 4.4.7 20120313 (Red >> Hat 4.4.7-3) (GCC) ) #1 SMP Wed Aug 28 14:27:42 UTC 2013 >> >> _______________________________________________ >> CentOS mailing list >> CentOS at centos.org >> http://lists.centos.org/mailman/listinfo/centos >> > What is with people these days? Why if something works but it is old do people > want to say OMG you need new hardware? > > -- > Stephen Clark > *NetWolves* > Director of Technology > Phone: 813-579-3200 > Fax: 813-882-0209 > Email: steve.clark at netwolves.com > http://www.netwolves.com > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos
Maybe Matching Threads
- Drive recovery?
- CONFIG_ARPD turned on in centosplus kernel.
- createrepo command for 6.4 respin
- biosdevname
- Out of Office. (was: Out of Office. (was: Out of Office. (was: Out of Office. (was: Out of Office. (was: Out of Office. (was: Problems with scsi-target-utils when hosted on dom0 centos 7 xen box))))))