When the installer complains that it has detected unsupported hardware,
is there any way to tell just what it didn't like? Following the URL in
the message just ends up at the RHEL Hardware Certification page, which
isn't much help. The installer seemed quite willing to continue with
the installation, and poking around from the shell VT I didn't find
anything that didn't seem to be working. I also didn't see anything
relevant in any of the message VTs.
As it turns out this isn't a big deal for me, since this was the CentOS
6.5 installer and there was no such warning from the 6.6 installer.
I'm just wondering how I might go about tracking that down,
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
We noticed this when installing onto some new Dell R320's.. it might have something to do with hardware that the device had that the older kernel might not have known about. Nothing seemed wrong and everything seemed to install ok (we would also update the kernel in the install process, so that probably hid any further problems), but moving to a 6.6 install made the silly error message go away. On Thu, Dec 4, 2014 at 11:14 AM, Robert Nichols <rnicholsNOSPAM at comcast.net> wrote:> When the installer complains that it has detected unsupported hardware, > is there any way to tell just what it didn't like? Following the URL in > the message just ends up at the RHEL Hardware Certification page, which > isn't much help. The installer seemed quite willing to continue with > the installation, and poking around from the shell VT I didn't find > anything that didn't seem to be working. I also didn't see anything > relevant in any of the message VTs. > > As it turns out this isn't a big deal for me, since this was the CentOS > 6.5 installer and there was no such warning from the 6.6 installer. > I'm just wondering how I might go about tracking that down, > > -- > Bob Nichols "NOSPAM" is really part of my email address. > Do NOT delete it. > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >
On Thu, Dec 4, 2014 at 12:32 PM, <m.roth at 5-cent.us> wrote:> Jeremy Hoel wrote: > > We noticed this when installing onto some new Dell R320's.. it might have > > something to do with hardware that the device had that the older kernel > > might not have known about. Nothing seemed wrong and everything seemed > to > > install ok (we would also update the kernel in the install process, so > > that > > probably hid any further problems), but moving to a 6.6 install made the > > silly error message go away. > > > Please don't top post. > > Dumb question: *how* were you installing? Did you have a kickstart of your > very own? If so... could it have wanted eth0, and the installer called it > em1? > > mark > >Kickstart.. and we had already changed the interface to the new name. It's the same kickstart between the two versions, with just the nic name being different.
On Thu, Dec 4, 2014 at 12:32 PM, <m.roth at 5-cent.us> wrote:> Dumb question: *how* were you installing? Did you have a kickstart of your > very own? If so... could it have wanted eth0, and the installer called it > em1?In my case there was no kickstart -- just a plain install from the ISO image, and the complaint from the installer comes long before I get a chance to do any customizations. -- Bob Nichols "NOSPAM" is really part of my email address. Do NOT delete it.