[CentOS] CentOS 2.6.9-42.0.8 issue - no keyboard after reboot

Mon Feb 12 23:30:38 UTC 2007
Jim Perrin <jperrin at gmail.com>

On 2/12/07, Mark Hull-Richter <mhull-richter at datallegro.com> wrote:
> I'm still new to CentOS/RHEL and rpm, so let me do this:

I'd like to take a moment to thank you for not top posting this time
around. Much easier to follow.

> How do I find this out?  If I do an rpm -q -a, I get 250+ lines of
> output, none of which appear to be specifically identified/identifiable
> as x86_64....

http://wiki.centos.org/TipsAndTricks/YumAndRPM
The first tip listed is pretty much mandatory for multi-arch systems,
although it is not the default. Hopefully upstream will see fit to fix
this in version 5.

> > You should either be building with plague and a full x86_64 tree ...
> or
> > a full tree as described in my first paragraph.
>
> Not sure what that means, per se.  I'm building with rpm.

Basically it means that you very likely don't have a proper build
environment to correctly build  working packages for the distribution.
There's much more to building packages than installing the development
libs and firing up rpmbuild.

Plague is a tool used by centos, fedora, etc to set up a proper
chrooted build environment using yum.

A basic x86_64 install has a fair amount of 'pollution' in the form of
x86 packages which are for compatibility with x86 software so that you
can run x86 junk on x86_64 junk. The problem is that when you build
x86_64 junk with x86 junk on the system, all you get is junk.

You need to set up a proper build environment (usually in a chroot)
free of pollution, or with only the minimal required pollution for a
given build. From the sounds of things, this is where your problem is.
Earlier, Johnny had laid out how to set up such a build area. It's
also documented a few other times in the mailing list, as multi-arch
pollution crops up every couple weeks or so with people using x86
build practices on x86_64 systems.

>
> > Now, as to whether the keyboard works, that could be an issue.  Did
> you
> > ever try to boot with my SMP kernel and see if there where also issues
> > with that.
>
> Which one is "your" SMP kernel?

The default centos x86_64 smp kernel is his, as well as the centosplus
kernel of the same arch flavor (as Johnny is one of the centos lead
developers :-P )



-- 
During times of universal deceit, telling the truth becomes a revolutionary act.
George Orwell