similar to: Centos 4.4 Problems not i586 compatible

Dear all, I was searching for a recent i586 for CentOS-5 in the CentOSPlus repository. Finding none, I decided to try my hands at building one. I have documented the changes made to the stock SRPM for building an i586 kernel on a temporary wiki page: * http://wiki.centos.org/TimothyLee/centos5_i586_patch These instructions have been successfully tested against the 2.6.18-164.10.1.el5

Arjen, Wow, that was quick... Thanks! (It was taking me a while to sort out all of the different CFLAGS settings; hence, the tracker item.) I would take issue with the following assertion in Makefile.am: "In any case, CFLAGS are only -I options, so there is no harm." since this is what got us into trouble in the first place... but I guess that was there before you edited it as

I've just attempted to reinstall my ancient laptop that has Pentium MMX processor. Since it is ancient, I've decided to go with CentOS 2.1. Got stuck, installer claims I need at least i686. Hmmm... I know that 3.8 and 4.4 work without a glitch on i586, so this came as surprise. I even thing original RHEL2.1 might had support for i586 too (but I might be wrong). Anyhow, what

Hi, I have a EPIA mini-itx board that I have been running Fedora 4 on. I want to install CentOS 4.4 on it since FC4 is no longer supported. The install goes fine but when I reboot the machine after the install I get errors like the following: hda:<4>hda: dma_timer_Expiry : dma status == 0x21 There are other errors about not being able to access the disk and eventually the kernel panics.

Hi, On the OpenMandriva side, x86_64 passes all checks. We're having some problems with other architectures though (see below): x86_64 succeeded, packages are here: https://abf.openmandriva.org/build_lists/76792 i586 fails to build, but this seems to be an issue with 3.8.1 (which we're using to build 3.9): /usr/bin/clang++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS

Johnny Hughes wrote in thread RE: [CentOS] install CentOS using an external USB cdrom Changing Subject to CentOS 4.3 i586 install option Last few post on the thread "install CentOS using an external USB cdrom" should have been "serial console install" or similar > instead of > linux your_options_here > use > i586 your_options_here > (that is w/ the 4.3

I created a i586 install image with qemu. I downloaded the SRPMS package for the kernel and installed it. I cd /usr/src/redhat/SPECS rpmbuild -bp --target i586 kernelXXX.spec I does a bunch of things but it did not build a new kernel and put it in /boot I think I am missing a command to actually BUILD the kernel. What is it? Thanks, Jerry

my poor little toshiba libretto (p-120) won't boot with the new 4.7 i586 kernel. i've reverted back to the previous kernel for now. anyone else using the new i586 kernel successfully on old hardware?

Please ignore (and excuse) my previous message - it is incomplete. I'm trying to get R and ESS to work with Xemacs on a newly installed SuSE 9.0 system. Is some setup required beyond installing the rpms? I've installed the Xemacs packages from SuSE xemacs-info-21.4.13-35 xemacs-packages-el-20030629-37 xemacs-21.4.13-35 xemacs-el-21.4.13-35 xemacs-packages-info-20030629-37

Are there plans to release kernel-2.6.9-67.0.15.plus.c4.i586.rpm ?? Thanks, Barry

I tried to install wine-1.3.7-mdv2010.1.i586 and I get: Some requested packages cannot be installed: wine32-1.2-3mdv2010.1.i586 (due to unsatisfied wine-bin [==1:1.2]) Got any ideas?

I have a strange situation. I am using centos 4.6 i586 with alsa 1.0.17 and asterisk 1.4.21.1 (only the console/dsp or soudn port). running centos 4.6 asterisk will seg fault after awhile. running debian edge with the same installed packages it does not seg fault. running x86_64 centos 4.6 and 5.2 asterisk does not seg fault. What might be going on with centos i586 that it is causing asterisk to

Hi all; Some of you may have seen on -devel that I've been playing with CentOS 5 on an i586 machine, and several people have displayed interest in the steps I've taken to compile a kernel and deploy it. I'm not quite sure where this would best go, so any guidance would be appreciated. I was guessing that http://wiki.centos.org/Projects/CentOS5PentiumSupport would be the best location

While I know that, technically, the only i586 machines are the Pentium and Pentium MMX, it is still nice that I can use some headless AMD K6/2 machines I have lying around for CentOS 4. Many thanks for the effort expended to get that working. -- Lamar Owen Director of Information Technology Pisgah Astronomical Research Institute 1 PARI Drive Rosman, NC 28772 (828)862-5554 www.pari.edu

I've updated CentOS 4.0 to 4.1 on several machines (some desktops, some servers). However on my laptop, update is failing with following error just after headers are downloaded: --> Running transaction check --> Processing Dependency: glibc-common = 2.3.4-2 for package: glibc --> Finished Dependency Resolution Error: Missing Dependency: glibc-common = 2.3.4-2 is needed by package

Hi, hpa wrote: > On PowerPC (I think) "unsigned char" is the default. In any case it seems a good idea to interpret the character more explicitely. To my experience, one signdness change causes a little tree of consequential signedness changes or questionable cast operations. How about the following instead ? if ((c >= 0 && c <= ' ') || c == '\x7f')

I plan to install CentOS 4.3 on some older IBM Netfinity which have Pentium III chips. I see that there is now a i586 pxeboot image for 4.3, I think that's new. Can I use that for Pentium III? Kai

My three basement machines got upgraded to 2.6.9-34.EL by nightly yum cron job. The two i686 seem to be fine. However, on the old i586 machine I got hole bunch of warnings. Haven't attempted rebooting it with new kernel yet. The warnings are: WARNING: /lib/modules/2.6.9-34.EL/kernel/drivers/edac/amd76x_edac.ko needs unknown symbol edac_mc_del_mc WARNING:

On 02.07.2015 23:12, Thomas Schmitt wrote: > Hi, > > hpa wrote: >> On PowerPC (I think) "unsigned char" is the default. > > In any case it seems a good idea to interpret the character > more explicitely. To my experience, one signdness change causes > a little tree of consequential signedness changes or questionable > cast operations. > How about the

Hi, 'exclude' option fails for yum on centos 5. I tried to yum install a group on a x86_64 machine, but it installs both ix86 version and x86_64 version. So I added the following line to /etc/yum.conf, clears /var/cache/yum/, then run 'yum groupinstall Ruby', but it reports that ix86 version packages will be installed still. Any one know what's the correct syntax to