similar to: PXE, Intel, and FC4 problems

My goal is to be able to install to the drive array on the 3Ware controller card. 3Ware does provide a RH WS 3 driver that I've tried to use; however, the RH Enterprise 3 WS driver doesn't work since that kernel is older than the CentOS-3.1 install kernel. I'm trying to create a centOS-3.1 installation driver disk for the 3ware 9500S card; however, I'm not having much luck.

I would like to add a driver (bcm5700.ko) in modules.cgz. but there are several files modules.cgz . In which files I do have to add the drivers: - initrd.img ? - stage2.img ? - netstg2.img ? - hdstg2.img ? Denis -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070118/6af6402d/attachment.html>

I'm new to the ISOLINUX development cycle, and I've tried a few times to come up with a solution. I'm trying to recompile isolinux.bin to look for the config files in a directory other than root, /boot/isolinux, or /isolinux. Ideally, this directory would be /lpc/isolinux. I've tried changing the plain text values in isolinux.asm to reflect these changes and recompiling using

I will install CentOS 4.3 and downloaded the driver disk from Dell for RedHat Enterprise Linux 4: Description: Dell PowerEdge RAID Controller 5 Device Driver for Red Hat Enterprise Linux 4.0, X86 & X86_64 I saw a few minutes ago that the driver disk is extracted within /tmp/ramfs/DD-01. Therfore I know that the network is working correct. I will try to extract the module and insmod/modprobe

I'm trying to add XFS and ReiserFS to CentOS, integrating with Kickstart. I think I'm fairly close. I've added xfs.ko and reiserfs.ko to modules.cgz in initrd. Several of my partitions now specify --fstype=xfs. I can see tty5 mkfs.xfs is creating the XFS file systems. The system currently installs completely via kickstart, but it does not mount the XFS file systems while in the

On 2014?03?07? 23:05, Ady wrote: > I understand that these remarks might seem not the main issue, but I > tend to think that once you are successful while using only "default" > > values and in a minimalistic case, you could add complexity > (different paths, multiple firmwares, additional kernels, multiple > cfg files...). Ady, Thanks. I will follow your advice to

Hi, to install current PC models (with new Intel NICs) via Kickstart/PXE, I wanted to add the newest e1000e-Treiber to initrd.img. With this modified image, the Kickstart kernel crashes with the following error messages: [...] md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. RAMDISK: Compressed image found at block 0 RAMDISK: incomplete write (20480 != 32768) 6062080

Hi all, I've got a Centos 5.1 kickstart that I must continue to use. How can I update the kick start image so that it recognizes Intel gigabit 82576 nic? BTW, I compiled the driver I need and have this igb.ko file. How do I incorporate that into my initrd.img file that I see on the kickstart CD that is probably my kickstart boot OS. Thank you very much in advance. aurf -

On 01.07.2015 12:10, Gene Cumm wrote: > On Wed, Jul 1, 2015 at 4:35 AM, poma <pomidorabelisima at gmail.com> wrote: >> >> To remind you once again. >> ISOLINUX >= 6.00 built with GCC >= 5.0.0 causes a broken boot. >> This relates specifically to the use of the vesamenu.c32, >> menu.c32 works without problemos. > > isolinux-debug.bin is not for

Kickstart fails for statically built custom booting kernel, although the custom kernel is built form the same version stock kernel source. My anaconda and kernel source are both of stock versions on Centos 5. At the kickstart 'F3' screen, the following error messages appear: Modules to insert tg3 ... ... ERROR: no network devices in choose network device! ERROR: no network drivers

To remind you once again. ISOLINUX >= 6.00 built with GCC >= 5.0.0 causes a broken boot. This relates specifically to the use of the vesamenu.c32, menu.c32 works without problemos. This "code" is already in 6.03, therefore this is not a fix for it! Revert "SYSAPPEND: Fix space stripping" This reverts commit 3106dcd http://repo.or.cz/w/syslinux.git/commit/3106dcd Fixes

Quite simply, HOW? :) I have the pxeboot initrd.img from the RH 3.0 AS CD's. We need to put a new cciss.o driver from HP into this initrd.img. Unforunately, the modules in the pxeboot initrd.img we have are 2.4.21-4 and our new driver is compiled for 2.4.21-15, so we have to upgrade everything. I downloaded the kernel-BOOT-2.4.21-15 RPM and installed that, so I have all those drivers. My

3ware now provides driver disk for CentOS. A couple of months ago, I had to add support for the 3ware 9550sx. The driver disk provided for CentOS 4.1 work perfectly. I now need to add support for the 3ware 9550sx for CentOS 4.3 x64. Although the driver disk is available, it doesn't seem to work. Anaconda just can't find the 3w-9xxx module. This is the same seutp as CentOS 4.1 (which

Setting the IF flag can cause an VM exit. So we should avoid touching the IF flag until absolutely necessary. This patch change the way the paravirt arch_local_irq_restore() works by checking the previous flags value and call arch_local_irq_enable() only if the IF flag was set previously. On a 32 vCPUs KVM guest running the AIM7 five-sec workload, the performance increased slightly from 302136.32

Setting the IF flag can cause an VM exit. So we should avoid touching the IF flag until absolutely necessary. This patch change the way the paravirt arch_local_irq_restore() works by checking the previous flags value and call arch_local_irq_enable() only if the IF flag was set previously. On a 32 vCPUs KVM guest running the AIM7 five-sec workload, the performance increased slightly from 302136.32

Greetings, We have purchased an IBM BladeCenter and I am in the process of testing Linux installation on these things (boot off SAN i.e. qla2300 driver, not using internal drives). My distro of choice is Debian, however, since I'm really not interested in trying to hand compile all the drivers, I decided to try CentOS (which I'm so far very impressed with). On boot, as with the

R-helpers, I'm using system() to run a shell script that uses a library written in C++ to analyze natural language (FreeLing: http://nlp.lsi.upc.edu/freeling). When I run the following code in RStudio (0.97.248) and R.app (1.62) on Max OSX (10.7.5): > cmd <- "analyze -f /usr/local/share/freeling/config/es.cfg --lang es --outf tagged </Users/earlbrown/temp_input.txt" >

On Tue, Jun 30, 2015 at 4:29 PM, poma <pomidorabelisima at gmail.com> wrote: > "A real serial port that can reliably operate at 115200 8n1 may be > necessary." > > Gene, is there something special in "A real serial port" usage, compared to emulated? I should restate: A serial port that responds on BIOS IO port 3F8h that can reliably operate at 115200 8n1 may

Hi I'm having a problem with setting up a kickstart environment based on CentOS 5.2 x86_64, on a Sun X2200 M2 server (both the server and the client in the kickstart environment are Sun X2200 M2 systems): the first attempt to load stage2.img fails with the error screen: "unable to retrieve http://192.168.11.10/source/images/stage2.img". Pressing the "OK" button brings up

<br><font size=2 face="sans-serif">Has anyone &nbsp;compiled a viable driver for a 3ware 9000 Escalade controller on CentOS-2 from source?</font> <br> <br><font size=2 face="sans-serif">Appreciate tips on getting this to work.</font> <br> <br><font size=2 face="sans-serif">Ive already dealt with the