You can put Linux or freebsd on a new hardrive. Only format it withWould a Linux installation on another partition on the same computer be sufficient or does it have to be a live medium?
newfs
.You can put Linux or freebsd on a new hardrive. Only format it withWould a Linux installation on another partition on the same computer be sufficient or does it have to be a live medium?
newfs
.This device is supported in 14.0. My guess is may be some default settings are different between freebsd & linux. I suggest asking on the freebsd-net@freebsd.org mailing list.igc0@pci0:12:0:0: class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x15f3 subvendor=0x1043
sys/dev/igc/if_igc.c:53: PVID(0x8086, IGC_DEV_ID_I225_V, "Intel(R) Ethernet Controller I225-V"),
sys/dev/igc/igc_api.c:106: case IGC_DEV_ID_I225_V:
sys/dev/igc/igc_hw.h:17:#define IGC_DEV_ID_I225_V 0x15F3
# pciconf -lv | grep -B4 ethernet
igc0@pci0:1:0:0: class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x15f3 subvendor=0x8086 subdevice=0x0000
vendor = 'Intel Corporation'
device = 'Ethernet Controller I225-V'
class = network
subclass = ethernet
igc1@pci0:2:0:0: class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x15f3 subvendor=0x8086 subdevice=0x0000
vendor = 'Intel Corporation'
device = 'Ethernet Controller I225-V'
class = network
subclass = ethernet
igc2@pci0:3:0:0: class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x15f3 subvendor=0x8086 subdevice=0x0000
vendor = 'Intel Corporation'
device = 'Ethernet Controller I225-V'
class = network
subclass = ethernet
igc3@pci0:4:0:0: class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x15f3 subvendor=0x8086 subdevice=0x0000
vendor = 'Intel Corporation'
device = 'Ethernet Controller I225-V'
class = network
subclass = ethernet
# ifconfig igc0 up
# dhclient igc0
DHCPDISCOVER on igc0 to 255.255.255.255 port 67 interval 3
DHCPOFFER from 10.50.53.4
DHCPREQUEST on igc0 to 255.255.255.255 port 67
DHCPACK from 10.50.53.4
bound to 10.50.53.181 -- renewal in 300 seconds.
# ping 10.50.53.1
PING 10.50.53.1 (10.50.53.1): 56 data bytes
64 bytes from 10.50.53.1: icmp_seq=0 ttl=255 time=0.464 ms
64 bytes from 10.50.53.1: icmp_seq=1 ttl=255 time=0.418 ms
64 bytes from 10.50.53.1: icmp_seq=2 ttl=255 time=0.390 ms
^C
--- 10.50.53.1 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.390/0.424/0.464/0.030 ms
You keep coming back to the point that the I225-V NIC works with Windows and Linux -- which is completely unastonishing, since ASUS would have no market for their motherboard if they did not address those usage cases.It works wirh the open source kernel drivers from Linux.
Licensing reasons usually. Just because something is open source doesn't mean you can copy the code.why an open source driver in Linux works perfectly but cannot be adopted to FreeBSD.
You may wish to file a bug report with ASUS as well as FreeBSD. That may eventually help fix the driver or the bios. Complaining here won’t help you.But I still cannot understand, why an open source driver in Linux works perfectly but cannot be adopted to FreeBSD. I will not downgrade the BIOS.
It's not a NIC firmware issue, read the referenced PR in post #56The BIOS update could have included a update to the Intel Networking firmware found onboard.
The newer BIOS could have fixed an ACPI problem.
I don't think you can 'blame' anybody who fixes a problem. Did you read the BIOS release notes?
Usually they cover what was fixed and some add history of BIOS upgrades to top of file.