NIC not found during initial installation

[Derek DiCamillo]

I have a Broadcom netlink gigabit ethernet adapter not having any luck getting this installed. Error no network Interface devices found when trying to start the installation.

 

[wolfgang]

You have to be a bit more specific.
Broadcom has may NIC.

 

[Derek DiCamillo]

So I was able to install 4.4 then upgrade to the current version. is there a command line to list the specific device? I believe the driver was left out of the 5.x versions and that is the issue as another forum suggested to install the older version and upgrade.

 

[Derek DiCamillo]

I believe this is it. broadcom BCM577888

 

[wolfgang]

I find no information about this card and what driver it uses.

 

[Derek DiCamillo]

https://certification.ubuntu.com/catalog/component/pci/14e4:1691/

this is it.

 

[nbench]

I'm new to Proxmox and I am having the same issue: No Network Interface Found. I have a QLogic 2x25GE QL41262HMCU CNA NIC.

Any suggestions?

 

[wolfgang]

https://certification.ubuntu.com/catalog/component/pci/14e4:1691/

This Nic uses the tg3 driver which is included in PVE.
Normally it should work.
Do you try to install a Ubuntu and check if the nic is working there?

 

[wolfgang]

@nbench
Please open a new thread. This is not related to this thread.

 

[Colin 't Hart]

Was this ever resolved? Ubuntu 18.04 running fine on a Dell Vostro 460 with an on-board Broadcom BCM57788, but Proxmox 6.3-1 installer doesn't detect it -- even though it is listed in the output of lspci.

 

[Colin 't Hart]

I managed to work around this.

When the installer reported "No network interface device found", I switched to the shell on tty3 (Ctrl-Alt-F3) and removed the tg3 module from the running kernel using

rmmod tg3

I then loaded the broadcom module followed by the tg3 module again:

modprobe broadcom
modprobe tg3

Loading the tg3 module may have been unncessary but it's what I did based on the second response to this thread: https://bbs.archlinux.org/viewtopic.php?pid=865373

I found the process ID of the running installer

ps -ef | grep inst

and killed it (kill -9 <pid>)

Finally, I restarted the installer:

startx

Once the install completed and the machine rebooted the network came up as expected, so it was just an issue with the particular kernel used in the installer.