<div dir="ltr"><div>Thanks all, I'm still playing with it and will try all of your suggestions, then report back.</div><div><br></div><div>The thing that complicates this is that I'm trying all of this from the CentOS (minimal) installer environment loaded from a USB drive, rather than the actual OS installed on the disk, as I can't actually get the installed OS to load after installation (keeps falling into the emergency environment). I'm thinking a lot of my challenges may have something to do with that? However, I have had a lot of luck with loading other KMODs on other systems that have out-of-support hardware (megaraid_sas) in this fashion (loading the RPM from a DUD using the "inst.dd" kernel parameter).<br></div><div><br></div><div>I'm not exactly sure how to use `yum` in the installer environment yet (looks like there is `anaconda-yum`, so I could possibly experiment with that). I'm doing another fresh install of CentOS (it takes a while) and then I'll try to `chroot` into that environment from the installer environment, and install the RPM with `yum`. If that doesn't work, I'll do a `yum upgrade` and try again. I don't know if that is really helpful or not, but I'm curious to see what happens.<br></div><div><br></div><div>To shed a little light around my main goal is that I have a LOT of these systems with this chipset that I'm trying to get onto CentOS 7 using Foreman, so it is ultimately important for me to be able to get the CentOS installer environment to load the KMOD RPM via a DUD, which would ensure that the OS installs at a non-glacial pace and actually loads during boot :)<br></div><div><br></div><div>Apologies if I'm making this overly complicated!</div><div><br></div><div>Tristan</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 20, 2021 at 11:49 AM Manuel Wolfshant <<a href="mailto:wolfy@nobugconsulting.ro">wolfy@nobugconsulting.ro</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<div>On 7/20/21 6:34 PM, Trevor Hemsley
wrote:<br>
</div>
<blockquote type="cite">
<div>On 20/07/2021 16:19, Tristan Evans
wrote:<br>
</div>
<blockquote type="cite">[anaconda
root@localhost ~]# uname -a<br>
Linux <a href="http://unknown001a6443e48f.attlocal.net" target="_blank">unknown001a6443e48f.attlocal.net</a>
3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux</blockquote>
<br>
yum update <br>
<br>
Get yourself to the latest kernel, the one the kmod was built
against.<br>
<br>
yum install kmod-sata_via-2.6-1.el7_9.elrepo.x86_64<br>
<br>
Work any better now?<br>
<br>
Trevor</blockquote>
<p><br>
</p>
<p>Thing is that I verified half a dozen of the failed dependencies
( randomly picked from the list ) and all of them are provided by
all the kernels available in C7.9.</p>
<p>And I am very puzzled by the presence of the folders
/usr/lib/modules/3.10.0-1160.el7.x86_64/extra/sata_via and
/usr/share/doc/kmod-sata_via-2.6 in the absence of the files that
should exist over there. Both these folders belong the ElRepo rpm
... which allegedly was not installed.<br>
</p>
<p>OTOH the package installed just fine on my fully updated C7.9 so
there is that.</p>
<p><br>
</p>
<p>wolfy</p>
<p><br>
</p>
<p>PS: Tristan, as a matter of habit, I suggest to use "yum install"
rather than "rpm -i". Saves time when the package you want to
install needs others as dependencies.<br>
</p>
</div>
_______________________________________________<br>
elrepo mailing list<br>
<a href="mailto:elrepo@lists.elrepo.org" target="_blank">elrepo@lists.elrepo.org</a><br>
<a href="http://lists.elrepo.org/mailman/listinfo/elrepo" rel="noreferrer" target="_blank">http://lists.elrepo.org/mailman/listinfo/elrepo</a><br>
</blockquote></div>