CentOS

Hi guys I have an i686 development environment with 100% i386 RPMs including glibc. If I make a simple livecd based on an init script that contains bash it will run fine on any i686. On any i586 it just doesn't I have no idea why because the bash binary is from the i386 RPM. Is this a bug or oversig...

Hi guys Here's what I normally do. I love CentOS and create basic LiveCD's from it, that is not the important part. My Centos is 4.4 i386 version running on an i686 AMD 2600. I have i386 binaries installed but they don't end up being i386 compatible. Eg. if I copy the bash binary and all the require...

Thanks Lenard awesome !

Hi Lenard, I'm familiar with installing kernels so it was no problem. Actually this new kernel works perfectly! Searching with yum with the base repo it still never found that kernel. I can get the same numbers but plus isn't shown if I search. I just wish the RPM manager would make it easier to tel...

Thanks Lenard I will try that!
What is the difference between the plus and do you have any idea why yum doesn't seem to be good at showing it as an option when doing yum search kernel or yum install kernel or yum update kernel?

Here is my original thread and so far no one has been able to figure it out :(
http://www.centos.org/modules/newbb/viewtopic.php?topic_id=5676&forum=27&post_id=16880#forumpost16880

I don't have the error line at the moment but I'll try and dig through my old posts and find it. I'm wondering if anyone using the same or similar setup is having this issue and got around it? Thanks Ever since this kernel "kernel-2.6.9-42.0.2.EL" I haven't been able to boot. So I'm using Centos 4.4...

I get this error when plugging in any USB mass storage device: usb 1-8: new high speed USB device using address 2 usb 1-8: control timeout on ep0out usb 1-8: control timeout on ep0out usb 1-8: device not accepting address 2, error -110 But if I run: rmmod ehci_hcd modprobe ehci_hcd Everything works ...

I'm running AMD64 and have the same problem.
It hangs with "PCI: Probing PCI hardware (bus 00)"

Also note it will seemingly skip the whole APIC-TIMER thing even if the BIOS APIC is enabled and "noapic" is added to the kernel line. The only problem is that it still probes the PCI bus! Oh and if you have APIC enabled in BIOS and don't use "noapic" you'll still get the IO-APIC timer kernel panic....