At 03:27 PM 1/17/2020, Akemi Yagi wrote: >On Fri, Jan 17, 2020 at 3:16 PM david <david at daku.org> wrote: > > > > Folks > > > > I know that support for the network adaptors supported by the 'e1000' > > driver have been removed from the base distribution. However, I have > > exactly that controller (Broadcom Gigabit Ethernet PCI, not > > PCIe). Is there a way for me to add support for that on Centos > > 8.1? Perhaps a driver in an RPM package? > > > > Thanks > > > > David > >The e1000 driver should be in the 8.1 kernel: > >$ modinfo e1000 >filename: >/lib/modules/4.18.0-147.3.1.el8_1.x86_64/kernel/drivers/net/ethernet/intel/e1000/e1000.ko.xz >version: 7.3.21-k8-NAPI >license: GPL >description: Intel(R) PRO/1000 Network Driver >author: Intel Corporation, <linux.nics at intel.com> >rhelversion: 8.1 > >Akemi >_________ Akemi Thanks for the suggestion. Modinfo does produce that result. But "the network doesn't work". My environment is a VirtualBox VM of Centos 8 on top of Windows 10. I've defined a bridged adaptor. The hardware is the Broadcom adaptor, using DHCP. No firewall is running in Centos 8 yet. This exact configuration works fine with Centos 7. The symptom I see is that DHCP, Ping, DNS Lookup all work, but no data transfer seems to work. I tried a CURL command to a local web machine (works with Centos 7), and it just hangs. The web server does not see the request. When I switch the network adaptor (in the VM) to NAT, everything works, probably indicating that the selection of the adaptor is the problem. I used the NAT interface to complete the install. Do you have any ideas? David *********** WHOA *************** It appears that this is not a Centos issue. My other VM's have stopped working also. The common factor is the use of a Bridged Network in VirtualBox on Windows 10 updated last week. Based upon prior similar events, I'd guess it's a Windows screw-up. Oh well. David