]> git.proxmox.com Git - pve-kernel-2.6.32.git/blob - README
update megaraid_sas to 6.600.18.00
[pve-kernel-2.6.32.git] / README
1 KERNEL SOURCE:
2 ==============
3
4 We use the OpenVZ Kernel sources, available from:
5
6 http://download.openvz.org/kernel/branches/rhel6-2.6.32/
7
8
9 Additional/Updated Modules:
10 ---------------------------
11
12 - we use bootsplash to display the boot logo.
13
14 - include latest AoE driver (http://support.coraid.com/support/linux)
15
16 - include latest ixgbe driver from intel/sourceforge
17
18 - include latest igb driver from intel/sourceforge
19
20 - include latest e1000e driver from intel/sourceforge
21
22 - include latest Broadcom bnx2 drivers
23
24 * original file linux-7.4.27.zip contains
25 netxtreme2-7.4.27.tar.gz (added to repository)
26
27 - include latest Adaptec aacraid driver
28
29 * http://download.adaptec.com/raid/aac/linux/aacraid-linux-src-1.2.1-30200.tgz
30
31 - include latest megaraid_sas driver
32
33 * http://www.lsi.com/downloads/Public/MegaRAID%20Common%20Files/MR_Linux_Driver_6.600.18.00.tgz
34
35 (extract source file megaraid_sas-06.600.18.00-src.tar.gz)
36
37 FIRMWARE:
38 =========
39
40 We create our own firmware package, which includes the firmware for
41 all proxmox-ve kernels. So far this include
42
43 pve-kernel-2.6.18
44 pve-kernel-2.6.24
45 pve-kernel-2.6.32
46 pve-kernel-2.6.35
47
48 We use 'find-firmware.pl' to extract lists of required firmeware
49 files. The script 'assemble-firmware.pl' is used to read those lists
50 and copy the files from various source directory into a target
51 directory.
52
53 We do not include firmeware for some wireless HW when there is a
54 separate debian package for that, for example:
55
56 zd1211-firmware
57 atmel-firmware
58 bluez-firmware
59
60
61 PATCHES:
62 --------
63
64 bootsplash-3.1.9-2.6.31-rh.patch: bootsplash patch
65
66 bridge-patch.diff: Avoid bridge problems with changing MAC
67 see also: http://forum.openvz.org/index.php?t=msg&th=5291
68
69 Behaviour after 2.6.27 has changed slighly - after setting mac address
70 of bridge device, then address won't change. So we could omit
71 that patch, requiring to set hwaddress in /etc/network/interfaces.
72
73
74 Additional information
75 ----------------------
76
77 We use the default configuration provided by openvz, and apply
78 the following modification:
79
80 see config-2.6.32.diff
81
82 - enable bootsplash
83 CONFIG_FB_VESA=y
84 CONFIG_FRAMEBUFFER_CONSOLE=Y
85 CONFIG_BOOTSPLASH=y
86
87 - disable CONFIG_DEBUG_INFO
88
89 - disable CONFIG_PRINTK_TIME
90
91 - enable common CONFIG_BLK_DEV_XXX to avoid hardware detection
92 problems (udev, undate-initramfs hav serious problems without that)
93
94 CONFIG_BLK_DEV_SD=y
95 CONFIG_BLK_DEV_SR=y
96 CONFIG_BLK_DEV_DM=y
97
98 - disable module signatures (CONFIG_MODULE_SIG, CONFIG_CRYPTO_SIGNATURE)
99
100 - enable usbip (this is also enable on debian kernels)
101
102 CONFIG_USB_IP_COMMON=m
103 CONFIG_USB_IP_VHCI_HCD=m
104 CONFIG_USB_IP_HOST=m
105
106 - enable IBM JFS file system
107
108 This is disabled in RHEL kernel for no real reason, so we enable
109 it as requested by users (bug #64)
110
111 - enable apple HFS and HFSPLUS
112
113 This is disabled in RHEL kernel for no real reason, so we enable
114 it as requested by users
115
116 - enable CONFIG_BRIDGE=y
117
118 Else we get warnings on boot, that
119 net.bridge.bridge-nf-call-iptables is an unknown key
120
121 - disable CONFIG_BRIDGE_IGMP_SNOOPING
122
123 To avoid problems with multicasting. Various users reported
124 multipath problems, which can be avoided by turning off IGMP
125 snooping.
126
127 - use 'deadline' as default scheduler
128
129 This is the suggested setting for KVM. We also measure bad fsync
130 performance with ext4 and cfq.
131
132 Testing final kernel with kvm
133 -----------------------------
134
135 kvm -kernel data/boot/vmlinuz-2.6.32-6-pve -initrd initrd.img-2.6.32-6-pve -append "vga=791 video=vesafb:ywrap,mtrr splash=silent" /dev/zero
136