On Thu, Dec 4, 2014 at 12:32 PM, m.roth@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@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.
-
Jeremy Hoel -
Robert Nichols