similar to: PnP OS

PnP BIOS for x86 is part of drivers, so I missed it in the initial GDT page alignment patch. Kudos to Andrew for fixing that. Unfortunately, fixing the build introduced a kernel panic when trying to setup the as of yet unallocated GDTs for the APs. This fixes the problem by setting only the BSP's GDT, then copying the PnP segments back to the cpu_gdt_table template. Signed-off-by: Zachary

PnP BIOS for x86 is part of drivers, so I missed it in the initial GDT page alignment patch. Kudos to Andrew for fixing that. Unfortunately, fixing the build introduced a kernel panic when trying to setup the as of yet unallocated GDTs for the APs. This fixes the problem by setting only the BSP's GDT, then copying the PnP segments back to the cpu_gdt_table template. Signed-off-by: Zachary

With the default settings in my Supermicro motherboard CentOS calls my SATA drive /dev/hda. If in bios setup I change 'Native Mode Operation' from auto to 'Serial ATA' it boots up calling the drive /dev/sda. I keep thinking its likely better under /dev/sda not? Any problem switching it to that after install? Matt

I have a server running CentOS 6.0. Last night I replaced the CPU and motherboard. Old hardware: Supermicro x8sil-f + x3440. New hardware: Supermicro x9scl+-f + E3-1230. This is a new Sandy Bridge Xeon. Everything else remained the same, including an IBM m1015 SAS HBA. This is just an IBM re-branded LSI 92xx-8i (9220-8i specifically I believe), which uses the LSI SAS2008 chipset and the

I've run into a rather odd problem. It seems that I can format and make bootable CF/SD cards and USB Flashdrives under Windows 98SE and MS-DOS 6.22 that will boot to a A: prompt on my system. But when I try making the same CF/SD cards and USB Flashdrives bootable under linux using syslinux I get nothing, not even a error message. It's like the syslinux bootloader doesn't even

I upgraded my Centos 4.7 server last night. Switched from a cheaper 50$ asus motherboard to a Supermicro motherboard. I also, using dd, copied entire 500g SATA seagate drive to new 500g SATA seagate drive so as to have two copies in case something went wrong. Anyway, now I keep getting this error: Nov 21 06:08:33 server kernel: hda: status timeout: status=0xd0 { Busy } Nov 21 06:08:33 server

Introduce the basic VMI sub-arch configuration dependencies. VMI kernels only are designed to run on modern hardware platforms. As such, they require a working APIC, and do not support some legacy functionality, including APM BIOS, ISA and MCA bus systems, PCI BIOS interfaces, or PnP BIOS (by implication of dropping ISA support). They also require a P6 series CPU. Signed-off-by: Zachary Amsden

Introduce the basic VMI sub-arch configuration dependencies. VMI kernels only are designed to run on modern hardware platforms. As such, they require a working APIC, and do not support some legacy functionality, including APM BIOS, ISA and MCA bus systems, PCI BIOS interfaces, or PnP BIOS (by implication of dropping ISA support). They also require a P6 series CPU. Signed-off-by: Zachary Amsden

I installed CentOS 4.4 32 bit on a dual core AMD64 motherboad. Its a Tyan Tomcat K8E motherboard with socket 939. The clock keeps drifting off like 5+ minutes an hour. Run ntpupdate hourly to compensate. Any ideas why or how to fix? Matt

Are there any plans for using serial PnP in NUT? I tried to implement this on the 'safenet' driver, but the support for this doesn't seem to be widespread among the UPSes compatible with this driver. So far, I have only managed to get one (a Sweex 1000) to output it, but unfortunately, it is probably too generic to be really useful for autodetection: PnP revision : 1.00 PnP EISA ID

Hi there, sorry for rather long mail. Two verbose dmesgs and `pciconf -vl` outputs attached. trying to set up new machine based on ASUS P4BGL-MX motherboard, I'd encountered hangs after detecting pcib1 (ICH2). MB has rl 8100 ethernet chip onboard. This is for 4.8-R; however, machine hangs in very similar way also with 4.4-R and 5.1-R. Matrix of hangs: Onboard Ether External Ether Result

Hi The setup, as in the subject, is supposed to boot a Winpe to install xp to a clean PC. I use the Ramdisk method (ie PXELinux pases the setup on to the M$ pxe loader and and boots WinPE) It works perfectly with evry other chipset, but Nvidias NForce 4. (tested 15 different) With NF4 it loads up well but the M$ PnP routine detects the Network management bus wrong (nvidia specific approach to

Move PnP BIOS segment definitions into segment.h; the segments are reserved here, so they might as well be defined here as well. Note I didn't do this for APM BIOS, as Macintosh and other systems use those values to emulate APM in some scary way I don't want to understand. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.14-zach-work/include/asm-i386/segment.h

Move PnP BIOS segment definitions into segment.h; the segments are reserved here, so they might as well be defined here as well. Note I didn't do this for APM BIOS, as Macintosh and other systems use those values to emulate APM in some scary way I don't want to understand. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.14-zach-work/include/asm-i386/segment.h

PnP BIOS data, code, and 32-bit entry segments all have fixed limits as well; set them in the GDT rather than adding more code. It would be nice to add these fixups to the boot GDT rather than setting the GDT for each CPU; perhaps I can wiggle this in later, but getting it in before the subsys init looks tricky. Also, make some progress on deprecating the ugly Q_SET_SEL macros. Signed-off-by:

PnP BIOS data, code, and 32-bit entry segments all have fixed limits as well; set them in the GDT rather than adding more code. It would be nice to add these fixups to the boot GDT rather than setting the GDT for each CPU; perhaps I can wiggle this in later, but getting it in before the subsys init looks tricky. Also, make some progress on deprecating the ugly Q_SET_SEL macros. Signed-off-by:

Hi, Am trying to build SMP kernel. Took kernel-2.6.18-194.src.rpm, extracted, rpmbuilded with SMP option. Successfully compile the new kernel and when using that kernel to boot up, following errors were shown up(highlighted in bold & red color): My kernel config file has ACPI and PCI configs enabled. Any pointers to what caused the problem are appreciated. ******************************

The one remaining caller of set_limit, the PnP BIOS code, calls into the PnP BIOS, passing kernel parameters in and out. These parameteres may be passed from arbitrary kernel virtual memory, so they deserve strict protection to stop a bad BIOS from smashing beyond the object size. Unfortunately, the use of set_limit was badly botching this by setting the limit in terms of pages, when it really

The one remaining caller of set_limit, the PnP BIOS code, calls into the PnP BIOS, passing kernel parameters in and out. These parameteres may be passed from arbitrary kernel virtual memory, so they deserve strict protection to stop a bad BIOS from smashing beyond the object size. Unfortunately, the use of set_limit was badly botching this by setting the limit in terms of pages, when it really

I have this ASUS M2NBP-VM motherboard http://tinyurl.com/3xby3h running CentOS 4.4 as a web/email server. It has a 500Gb SATA2 drive with about 32Gb in use. The motherboard supports hardware raid. Is there a way to switch to RAID1 without reinstalling or loosing any data? Also, if I am running raid how do I know if there is a failure on one of the drives anyway? Is hardware RAID1 a good idea?