similar to: EDD error RE: Re: SYSLINUX 2.12-pre7 released

I have an application/program which shows 'bios EDD error' when using Isolinux (with either loading an image directly through MEMDISK, or booting to A:), and not when using a bootdisk directly or booting a bootdisk directly which has SYSLINUX on it. configuration: bootable cdrom with Isolinux 2.11/2.12pre9 as bootloader. 1.44MB bootdisk with MSDOS.SYS/IO.SYS and the UDMA2 dos driver,

(Sorry, Outlook webmail prohibits me from proper replying/quoting) >it has the nice effect that you can load the El Torito >CD-ROM driver. Which seems logical if you boot a kernel (like Linux, or Memdisk with an imagefile), but not when doing a local boot (diskette/harddisk) In other words: boot from cdrom, and if you then load a disk-image, eltorito.sys should load. If not loading a

>information a bit closer; it'd find that it's marked accordingly. UDMA2.SYS author now worked around it, it seems you do something with "DPTE" in isolinux.asm but not using it (probably for memdisk or direct floppy/harddisk emulation?). also something about EDD v1.1 and v3.0 specifications and setting bits to 1. Anyway, the driver works now on: BIOS -> cdrom ->

We run several RH7.2/7.3 servers & recently 2 of them, although still working fine, have started to show kjournald as generally using over 50% cpu% on 'top' - virtually continuously. Free cpu% generally less than 25% now! Both machines are also using software RAID5 EIDE ....... otherwise are standard server installs. Any info on what kjournald is & why it should have recently

Morning All, I upgraded from 9.2-STABLE to 10.0-PRERELEASE #0 r259144 last night and I am now getting this every 2 seconds in /var/log/messages: Dec 10 07:54:31 Shop kernel: ata1: FAILURE - zero length DMA transfer attempted Dec 10 07:54:31 Shop kernel: ata1: setting up DMA failed cat /var/log/messages | grep ata1: cd0 at ata1 bus 0 scbus3 target 0 lun 0 cd0: <TSSTcorp DVD-ROM TS-H352C

>No, but you can write a comboot/com32 module to do it if you wish. I meant for syslinux.exe/com (the installer). that BIOS issue is now handled in the driver the author wrote. Unfortunately I can't find another cdrom which boots but lets me access A: to really demonstrate it's the BIOS which is doing this. Every non-emulation cdrom either uses isolinux (even ReactOS bootloader) or

Hello friends, I'm having a problem with my home server (ASUS A7V133 motherboard) which has a horrible performance with ATA disks connected to an integrated promise controller. Below you can see iozone results of the same disk connected to the primary/ secondary controller versus the promise one. Promise ATA100 controller: ========================= Version 1.02a ------Sequential

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

Hardware Supermicro X7DAE (AHCI BIOS) dual Intel Woodcrest processors, 6 x Western Digital Raptor SATA drives. I have installed b62 running 64 bit succesfully on a PATA drive. The BIOS is configured to access the SATA drives in native mode using hte AHCI Bios. I have 6 SATA II drives accessed via the Solaris AHCI driver. I have created a ZFS file system across all 6 drives. This works fine until

Okay, I've been chasing performance for a while now. I have no idea if I should be trying to get better performance or if I'm getting all I can out of my hardware. Here is the information: /sbin/hdparm -I /dev/hdd /dev/hdd: ATA device, with non-removable media Model Number: ST328040A Serial Number: 7BY034XB Firmware Revision: 3.07 Standards:

Hi... I have a Dell Latitute with an ATA/ATAPI-5 T13 1321D and it would seem that my disk access is extremely slow. I have the latest updated kernel from RedHat 8.0 kernel 2.4.18-27.8.0. Somehow I think it is related to the UDMA stuff (shows my level of understanding). I have run hdparm and although I think I should at least udma level 5, I have at most udma2 listed. Is this a kernel

Hello Folks, We have 2 (identical hardware) busy public 2U rack servers, both have several hundred users & peak email (for example) deliveries at 300/5min during the daytime. Both servers run RAID1 over 2 EIDE disk drives. One server is fine - it never has problems - it is running RH7.3 and CPU loads are normal. The other server has constant disk activity & kjournald at CPU load of

I have a brand new ASUS MB model M2N-MX which is giving me issues when installing Centos 4.4 64 bit I initially had problems with finding the SATA drives but I resolved that issue by simply selecting the NVIDIA SATA (sata_nv)driver from the list of drivers during the initial install. The install seemed to go fine after that as the installer uses the Generic VESA video driver during the install,

So I have attached to my system two 7-disk SCSI arrays, each of 18.2 GB disks. Each of them is a RAID-Z1 zpool. I had a disk I thought was a dud, so I pulled the fifth disk in my array and put the dud in. Sure enough, Solaris started spitting errors like there was no tomorrow in dmesg, and wouldn''t use the disk. Ah well. Remove it, put the original back in - hey, Solaris still thinks

Hi Gang, I recently rented a server at a datacenter with Centos 5.7 X64, Q9550 Processor, 8GB Ram, and dual 250GB SATA HDs (with 16mb cache). They had loaded it with KVM, and installed a 30-day trial of Virtualizor as the front-end for KVM. I was so impressed with how fasts the guests ran that I want to build a few of these machines for myself. I just installed one: same Q9550 processor, 4GB

Hi, I have installed b_78 on a Dell 2950 and booting to bare metal works fine but when I try to boot using the grub entry Solaris xVM it will boot to the point where it displays the uname info and then just stays there. It will not boot past that point. I have enabled VT technology in the BIOS (but only after the installation). Where/what can I look at to trouble shoot this? I am new to xen and

[This email is either empty or too large to be displayed at this time]

In my haste for help, I stupidly hit reply and changed the subject which I thought was enough for a new message, not giving much thought for the threading, etc. So apologies for the hijack, although I would think it fairly obvious that it wasn't deliberate or obvious to me... or a big deal really. My mail doesn't thread. Some further info for those actually interested in helping, I forgot

While investigating erratic performance on one our our servers, I'm getting some very odd performance stats coming from vmstat. What initially appeared to be happening is the machine goes into a hard loop in some mod_perl webserver code. Now there still may be an issue with the code, but my code examinations show no possible way this could be happening, but what I'm writing to you

I have just released SYSLINUX 3.00-pre9. The only change versus 3.00-pre8 is that the MEMDISK query API now reports the boot loader ID byte, per Bernd's suggestion. This is a release candidate, and I plan to release it as 3.00 *tomorrow*, unless I hear back anything bad. -hpa