Hi All, OMV is looking good and at least seemed to install OK.
Strangely, although the install process found a mirror and downloaded some files, the system boots up and has blanks for 'the admin screen is at' because it says there is no network interface. The NIC is a Realtek 8111F (yes I know Realtek have a bad rep for older models but it's built into the mb so there it is) on an Asus F1A75-M PRO R2. Any suggestions greatly appreciated!
Alas I have no other NICs since they're all built in, except for a USB one that the system also didn't recognize.
It's the latest OMV from the download link: 4.1.22
magarity
Installed fine, even got files from mirror, then no NIC present??
-
-
Read problem #7 - https://forum.openmediavault.o…tions-to-common-problems/
-
@ryecoaaron This won't help him, because the Thread-Opener has an Realtek 8111 NIC, that is not recognized out-of-box, because it relies on the rtl8169 Kernel Driver instead of facing the rtl8168 that has to be downloaded and compiled.
-
@magarity For the moment, please use an USB3-to-GBit Ethernet-Dongle, newer UGREEN Models, for example, use the widely spread ASIX-AX88772A Fast-Ethernet Chipset that works out-of-box.
I am using an ASROCK J3455B with similar NIC chipset and still trying to investigate in a proper solution. Neither Debian 10.2 nor OMV 5.0.5 enables the rtl8111 chipset, where I got stuck, too, by using latest OMV 5.2.1-1 and Kernel 5.3.0.0.bpo.2-amd64.
NIC-enabling will not succeed, as the latest rtl8168 driver (v8.0.47.05) got limited to be compiled only up to Kernel version 4.15, but OMV 5 actually demands for newer Kernel Releases.
-
This won't help him, because the Thread-Opener has an Realtek 8111 NIC, that is not recognized out-of-box, because it relies on the rtl8169 Kernel Driver instead of facing the rtl8168 that has to be downloaded and compiled.
This isn't completely true. If the device id is in the kernel driver, it will work. There are so many versions of the 8111 that have different device ids that it is confusing.
-
OK, thanks, I was able to get to the machine by waiting a few more seconds then using ifconfig.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!