Thanks for checking back with me. It seems to be solved...sort of. I found a friend who had a CentOS 7 appliance DVD and after 999 updates (must be older), it seems to run fine on both boxes that I have been trying. Interesting that you mention nfs 4. I noticed that the appliance installed with ext 3 and thought that was strange. Maybe ext 4 is a big part of the problem. Why haven't we heard about this?
All installs lately using the script method that Fred recommends have been troublesome - as if CentOS 7 is picky about the hardware configuration and Riv RDAlsaconfig from the menu is broken. With the appliance install, everything works so I am happy about that but would sure like to understand why we haven't gotten the script method working. It sounds like we need to manually format the partitions ext 3 where appropriate before installing 7. Thanks, Tom Van Gorkom Radio Esperanza Engineering, KRIO AM/FM, KOIR FM Office: 956-380-8150 Cell: 865-803-7427 Rio Grande Bible Institute 4300 S US Hwy 281 Edinburg, TX 78539 On Wed, Oct 11, 2017 at 8:13 PM, sjm <[email protected]> wrote: > On 09/15/2017 01:58 PM, Tom Van Gorkom wrote: > >> I have an Intel i5 box that after installing kernel 3.10.0-327 from a DVD >> iso and running updates would no longer boot.... on kernel >> 3.10.0-693.2.2.el7.x86_64 (Centos 7.4). It will still boot on the >> original >> version however. Upon removing the rhgb guiet options I see that it gets >> stuck after reporting that the Ethernet links were not ready, it failed to >> receive control response completion, then says it is polling.... After >> several minutes nothing happens. I am reading that this may be a bug for >> some boxes with 7.4. Anyone else run into this? Any fixes? Maybe just >> stick >> with the former version. >> > > Late to the party, but... > > Have you fixed this yet? I may have run into something similar. Are you > using nfs v4.1? I ran into something with an nfs connection in another > (non-Rivendell) scenario where we had to back off to nfs v4.0. There is a > bug, it seems, in some network code where it reports the nic up and ready > before it actually is and the nfs v4.1 connection would fail as it looked > for trunking on the connection. Dropping back to nfs v4.0 (that doesn't > use the trunking query) fixed our issue. > > sjm > > >
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
