I performed a binary upgrade from 9.0-RELEASE and it went smoothly
When the machine came up with the new kernel, the interface previously known as em0 was no longer enumerated (pciconf -vl showed that it was now none0) and as far as I can tell, the interface that was em1 was now em0.
Side note: iWeb (previously a FreeBSD proponent) now refuses to support FreeBSD. The problem? They never told their customers. x( I found out the hard way. "Could you please swap the cable?" was responded with "As said earlier, we do not offer any support for FreeBSD. We can re-install your server and connect your old disk via USB to allow you to recover your data."
I checked UPDATING before upgrading and there was no mention of issues with Intel Pro/1000 drivers.
Has anyone else run into this?
This might be a clue:
THANK YOU freebsd-update rollback I'm back to 9.0 for now.
Code:
freebsd-update -r 9.1-RELEASE upgrade
freebsd-update install
(reboot)
freebsd-update install
When the machine came up with the new kernel, the interface previously known as em0 was no longer enumerated (pciconf -vl showed that it was now none0) and as far as I can tell, the interface that was em1 was now em0.
Side note: iWeb (previously a FreeBSD proponent) now refuses to support FreeBSD. The problem? They never told their customers. x( I found out the hard way. "Could you please swap the cable?" was responded with "As said earlier, we do not offer any support for FreeBSD. We can re-install your server and connect your old disk via USB to allow you to recover your data."
I checked UPDATING before upgrading and there was no mention of issues with Intel Pro/1000 drivers.
Has anyone else run into this?
This might be a clue:
Code:
em0: Setup of Shared code failed
device_attach: em0 attach returned 6
THANK YOU freebsd-update rollback I'm back to 9.0 for now.