gnoboot-alpha9 hp nxx 系列的wol问题有望解决
本帖最后由 laoyangjp 于 2014-3-3 10:29 编辑Changelog:
[*]Kernel support for Centaur CPU
[*]Kernel max CPU support increase to 16 cores
[*]Kernel CONFIG_STRIP_ASM_SYSMS enabled
[*]Kernel CONFIG_DEBUG_STACKOVERFLOW enabled
[*]Xen and KVM paravirtualize guest support
[*]Enable High Precision Event Timer (HPET)
[*]Update e1000e (e.g. i217) driver to version 3.0.4
[*]Update igb (e.g. i210) driver to version 5.0.6
[*]Update intel_idle to support Ivy Bridge and Ivy Bridge Xeon, and other features as posted here
[*]New wireless drivers from backports-3.12.8-1 version
[*]Bluetooth driver support
[*]Remove wireless and multimedia kernel configuration, switch to backports (compat-drivers/compat-wireless)
[*]Add alx driver to support Atheros AR816x/AR817x
[*]Add pcc-cpufreq driver to support PCC interface implemented on certain HP Proliant platforms
[*]Add powernow-k8 driver for K8/K10 Opteron/Athlon64 processors
[*]Re-built flashcache driver
[*]Fixed rmmod and insmod GRUB option
[*]Fixed missing mpt2sas driver
[*]Fixed v5 installation
[*]Fixed I/O scheduler optimization
Known Issues:
[*]No multimedia drivers and missing legacy wireless drivers
[*]WOL is not supported by tg3 driver on some devices(e.g. NC107i)
[*]Possible volume1 (/dev/md2+) and iSCSI corruption due to kernel changes, got hit twice while running some test
[*]VM performance issues running on ESXi 5.5, need testers and more details
[*]Download access to follow, don't fucking play with the form!
Notes:
[*]To switch from older Intel drivers use the following GRUB option.
[*]rmmod=e1000e_new,igb_new insmod=e1000e,igb
[*]Manually insmod the new drivers using GRUB option or /etc/rc.local whatever fits your taste. There are some built-in drivers so don't report any issues when you get duplicate symbolmessages. But if you find unknown symbol then its probably missing dependency or feature not enabled in the kernel.
[*]Nuke /lib/modules and /.gnoboot if you are upgrading from alphaX to later versions.
[*]If ever you mirror the file, please ask them to visit this post. Thanks!
本帖最后由 laoyangjp 于 2014-3-3 10:36 编辑
ESXi 5.x tg3 driver and TSO enabled data corruption
I'm working on getting the latest tg3 driver to address a WOL issue. Someone at XPEnology forum also reported a network performance issues using ESXi 5.5 and gnoBoot VM. You might as well consider upgrading your ESXi tg3 driver to the latest version for a possible fix and avoid data corruption as mentioned in the KB article below.
"Broadcom NIC devices, such as the BCM5719, support LSO/TSO in hardware. An issue in this TSO hardware engine can cause data corruption when:
TSO is enabled
A TSO operation is being performed on TCP Payload data and the address of the host physical memory buffer of any of the segments corresponding to this crosses a 4 GB address threshold. Read more..."
http://kb.vmware.com/selfservice ... &externalId=2055140
hp 系列的wol问题有望解决？ 关注一下... 远端的WOL还是无解?
页:
[1]