|Installation de Trixbox 2.0 sur Gygabyte P965|
|Article d'origine 'source : http://www.centos.org/modules/newbb/viewtopic.php?topic_id=6070&forum=29)|
|System: generic PC built around an Intel 965 express chipset motherboard, as follows:
Intel "Dg965ss" Mainboard
Core2 6400 CPU - 2.13ghz dual core
2 gigs Ram
320gig SATA2 Seagate HDD
IDE DVDBurner Drive
I bouight this system with the hope it would be an easier install than my last blackbox CentOS 4.4 install. This was sort-of-true, but not nearly what I expected.
Basic "problem issues" were:
* System fails to boot from installer media without appropriate flags passed to the kernel
* System fails to boot once CentOS is installed without appropriate flags passed to the kernel
* Network card (onboard e1000 gig-ether) works at time of install but breaks with subsequent kernel updates
* onboard video (Some form of 965 express) doesn't work correctly for me, despite using driver CD from intel that claims things should be OK
* VESA video works adequately for this context so is used as workaround for video issue.
* when booting the system from CentOS 4.4 Installer CD 1, be certain to pass appropriate flags to the kernel. Specifically, I used the boot command thus:
linux pci = nommconf acpi=off irqprobe all-generic-ide
* Proceed with default install and things go fine, reboot. Note to boot your fresh installed system you will need to add kernel flags NOT present by default in the grub boot loader, ie, as before you want flags present thus:
pci = nommconf acpi=off irqprobe all-generic-ide
* Once booted, manually install an SMP kernel using yum, because the system will have installed a non-SMP kernel at this point.
* Next, edit /boot/grub/grub.conf and update kernel parameters "temporarily" so that the machine will boot OK for duration of these tweaks.
* In anticipation of lost network access with your next reboot from the new kernel, get your hands on network driver source from URL:
(note that buld hints are visible at URL, http://www.intel.com/support/network/adapter/onlineguide/proinfo/pro1000/docs/linux/e1000.htm)
* Do NOT build the new network driver module yet. Just have the file on your system.
* Tweak yum repos as desired and roll a yum update on your system, which probably will pull a new kernel (among other things). Reboot when done and use the new desired kernel from the grub boot loader menu (presumably the most recent SMP kernel).
* While booting, you will probably note eth0 fails to startup with some errors indicating either (a) "device missing" or (b) "device eth0 has different MAC address than expected, ignoring". In either case, output from "ifstat -a" will typically confirm that the eth0 failed to initialize, even if the module tried to load, etc.
* Follow the hints from the URL above on building the e1000 module. note that you MUST be running the kernel intended for use with the module at the time of build (if you follow their directions, anyhow). Build was a process mainly of expanding a tarball, issuing "make" and "make install". If the make install failed, a lsmod / rmmod cycle might be required to remove an already-present e1000 module that is present but not working from previous kernel / etc. Alternately a reboot might work.
* Once you have the new e1000 module installed, you should be able to do /etc/init.d/network start and bring up eth0 successfully.
* Maybe reboot again, verify that network comes up on its own / correctly
* Finally, you want to tweak the boot parameters in /boot/grub/grub.conf so that we are not being quite so conservative. In particular, dual cores are not active until you setup thus:
linux pci = nommconf irqprobe all-generic-ide
After you reboot thus, you should have 2 cores online, ethernet working, and life is "OK if not perfect".