similar to: start network installation with HP 8530w with Intel ethernet card

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.

Here's some reminders for various branches that are pending. All branches are at my public repo at git://git.zytor.com/users/genec/syslinux.git ( http://git.zytor.com/?p=users/genec/syslinux.git;a=summary ) HPA, I'd appreciate a response in the direction of a status like on hold, under review, denied or to be completed soon. Branch win64-mingw32-ubuntu-for-hpa adds more prefixes in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I usually use DHCP to install CentOS boxes via kickstart. For a first install, I boot the machine on the CentOS first CD, I type "linux ks" at the prompt and the rest is automatic. I have already use USB pen to boot some servers that don't have CD-ROM drive and all went well with the diskboot.img of CentOS 5.1. But the

Hi, Is someone has an experience for adding a network driver when starting a network installation. My network internal card is : Intel 82567M Gigabit (laptop HP 8530w) This card is not recognized by my system : CentOS 5.2 x86_64 (kernel 2.6.9-92) How to add correctly this driver for a network installation ? I can add the Intel driver e1000e-0.5.11.2 after the installation and the network

On Sun, Oct 29, 2017 at 11:51:55PM +0100, Fengguang Wu wrote: >Hi Linus, > >Up to now we see the below boot error/warnings when testing v4.14-rc6. > >They hit the RC release mainly due to various imperfections in 0day's >auto bisection. So I manually list them here and CC the likely easy to >debug ones to the corresponding maintainers in the followup emails. >

On Sun, Oct 29, 2017 at 11:51:55PM +0100, Fengguang Wu wrote: >Hi Linus, > >Up to now we see the below boot error/warnings when testing v4.14-rc6. > >They hit the RC release mainly due to various imperfections in 0day's >auto bisection. So I manually list them here and CC the likely easy to >debug ones to the corresponding maintainers in the followup emails. >

On 01.07.2015 17:46, Ady via Syslinux wrote: > >> 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

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 lists so sorry about any faux pas I may have made. Also I apologize for the length, but I wanted to be sure I covered most of the details. I'm trying to do a PXE install on an Intel 1435VP2 server machine. The PXE install has worked on all the older machines in the cluster, so I know PXE is working. However, these new Intel server machines only support PXE booting from

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

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

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

> You are thinking GRUB-like, among (too) many others. Heh, at least I am in good company. > A "sector" is not necessarily 512-bytes long. Fair enough, e.g. Advanced Format 4k sector disks. > The VBR, or Volume Boot Record, is not necessarily 512-bytes long. > Also, the VBR doesn't need to be restricted to the first sector of the volume alone. The "Design"

Hello, I have a live-cd which has a syslinux on it and boots a linux kernel. It works ok and boots the kernel ok from a CD drive. Now,I need to add support for this live-cd so that it will boot from an external USB cdrom drive. My bios **DOES** support booting from USB; but when I try to boot it hangs in the middle while looking for usb-storage drivers. I can gunzip

Hello, you guys have helped me before. I am setting up a multiboot system on my usb stick. At one point, with syslinux, i had the two of the three systems working. However in a sucessful attempt to get the third working, i used that os'es instructions for usb installition, which included syslinux. After which, that system worked, with its syslinux.cfg being located in a non-root folder

On Fri, Mar 7, 2014 at 10:50 AM, Steven Shiau <steven at nchc.org.tw> wrote: > > 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,

Hi, I have built a Red Hat 7.2 system kernel 2.4.7-10 using pxelinux from syslinux-2.09 I have then installed the latest Broadcom BCM5700 Linux Driver Version 7.1.22 as per the README.TXT:- rpm -ivh bcm5700-7.1.22-1.src.rpm cd /usr/src/redhat rpm -bb SPECS/bcm5700.spec rpm -ivh --force RPMS/i386/bcm5700-7.1.22-1.i386.rpm The system reboots fine and is using the new driver I now want to update my

Greetings! I am currently building a PXE distro server for a company that I'm contracting for, but I'm having some problems. Here's the scoop: Some of the clients I want to install on are Angstrom blades with Intel e1000 NICs. Using the pxelinux.0 file on the FC6 distro, I can install FC6 just fine. However, FC4 bombs. The system pulls it's DHCP address just fine, and then

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