similar to: Probing EDD (edd=off to disable)

Note, first of all I haven't actually updated, I'm just running "yum update" to see what conflicts, if any, I get so I can be prepared when the final 7.7 release happens. I've traditionally used the nvidia packages from elrepo, but recently enabled rpmfusion (back when I started using 7.x, I disabled rpmfusion because it took them a looooong time to get a EL7 repository up).

Sorry if this has been dealt with, but I couldn't find it in a search. I updated Fedora to the new kernel build, and there are no current drivers for nvidia cards for that. That's fine, livna made a new neat thing called akmod-nvidia that appears to have built the drivers very nicely (quite pleased with that). All is happy and shiny from within Linux (compiz works and openGL games work

On Sat, Sep 14, 2019 at 07:20:35PM +0100, Phil Perry wrote: > On 14/09/2019 19:06, Fred Smith wrote: > >Note, first of all I haven't actually updated, I'm just running "yum update" > >to see what conflicts, if any, I get so I can be prepared when the final > >7.7 release happens. > > > >I've traditionally used the nvidia packages from elrepo,

Hi all! I'm running an up-to-date Centos-7 on an AMD Vishera 6300, 6 core CPU. I note that when I run the redhat script to test for spectre & meltdown I get this result for variant 2: Variant #2 (Spectre): Vulnerable CVE-2017-5715 - speculative execution branch target injection - Kernel with mitigation patches: OK - HW support / updated microcode: NO - IBRS: Not disabled on

I installed the elrepo kmod-nvidia and also the nvidia-detect and modules (see below). I had X working with the 3.10 from Centos - but video was freezing. SO I thought I would try the elrepo kernel. I installed that and X does not come up? How do I re-make the nvidia module for 4.14.5 kernel? I want to make sure the kmod kernel did it. I 'm thinking it did not. lspci | grep VGA says

https://bugs.freedesktop.org/show_bug.cgi?id=110797 Bug ID: 110797 Summary: No video if nomodeset is not set with GTX 460 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Hello, This is my first post on this list. I am experiencing very often hard-locks while using different wine versions (from wine 0.9.58 until 1.0-rc3). My OS is Fedora 9 x86_64 and I also compiled 1.0-rc3 how the wine wiki told me to do. I am also experiencing hard-locks just by using winetricks. The hard-locks appear not immediately but sporadically. But that's a kernel issue I guess,

EDD (https://en.wikipedia.org/wiki/Enhanced_Disk_Drive) is a BIOS INT 13h subcall for communicating the extended size of the boot disk over 8GB to the OS. Since libguestfs doesn't use a boot disk, and the appliance disk is limited to 4GB, and we use virtio-scsi, this is all useless. EDD is also broken currently on RHEL 7.3, see: https://bugzilla.redhat.com/show_bug.cgi?id=1404287 Also the

Last week we noticed that the default scheduler isn't being set properly in CentOS 7. I haven't checked this for CentOS 6, but it might be worth exploring. The TL;DR is unless you're running CentOS 7 on a laptop or as a virtual guest, you should probably run 'tuned-adm profile throughput-performance' I wrote up the full details here ->

On Sun, Jan 31, 2016 at 09:42:43PM -0500, Mark LaPierre wrote: > On 12/30/15 23:03, Mark LaPierre wrote: > > Hey Y'all, > > > > I have the Stanford University Folding At Home project running on three > > of my machines. I had them all set up so that I could control them all > > from my main machine, 192.168.15.101, but some time ago something > >

Hi, I got this from my digital camera with Syslinux compiled from source (yes, I've got a configuration file with a UI directive): SYSLINUX 4.02 pre-1-g0ee5047 CHS Copyright (C) 199... EDD: Error 0100 reading sector 0 EDD: Error 0100 reading sector 2252244088 EDD: Error 0100 reading sector 2252244089 EDD: Error 0100 reading sector 2252244090 EDD: Error 0100 reading sector 2252244091 EDD:

(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

>> Rebooted my home server into a new kernel and got a hard system lockup >> and a bunch of "kernel: BUG: scheduling while atomic" in >> /var/log/messages. The culprits seem to be nvidia-352.30 drivers from >> elrepo. Downgrading to 352.21 solved the problem. > > which centos version? > > which kernel? > > which nvidia card? > > what is

>The way the El Torito CD-ROM is going to look like to the program, is >that it looks like an additional hard disk which a very high drive >number (typically 9Fh or so); MS-DOS will normally ignore this since it >asks the BIOS how many drives there are and ignores the rest. >Does the error message come from UDMA2.SYS or...? > -hpa yes, it comes from UDMA2.SYS, it does 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 ->

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,

On 05/19/2014 11:20 AM, Anatol Pomozov wrote: > Hi > > I have a computer with BIOS and Linux Arch installed. > > Starting from a recent syslinux update (6.02->6.03pre9) I am not able > to use syslinux anymore. I try to boot my computer and the only thing > I see is "EDD Load error - Boot error" message. When I install 6.02 > back the system is completely

Op 2014-05-19 om 11:20 schreef Anatol Pomozov: > Hi > > I have a computer with BIOS and Linux Arch installed. > > Starting from a recent syslinux update (6.02->6.03pre9) I am not able > to use syslinux anymore. I try to boot my computer and the only thing > I see is "EDD Load error - Boot error" message. When I install 6.02 > back the system is completely

Some additional fields from the EDD-4 spec. draft for the Device Parameter Table have been added into the structure in setup.c and memdisk.inc. These were added in the hopes of resolving a FreeDOS MEMDISK bug on IBM ThinkPads. --- memdisk/memdisk.inc | 11 +++++++++++ memdisk/setup.c | 10 ++++++++++ 2 files changed, 21 insertions(+), 0 deletions(-) diff --git a/memdisk/memdisk.inc

Op 2014-02-20 om 13:23 schreef Andy Alex: > DL register is not set to drive number when detecting EDD for drive, so detection may fail. > > Signed-off-by: Andy Alex<andy at r-tt.com> > --- > diff -uprN syslinux-6.02.orig/core/fs/diskio_bios.c syslinux-6.02/core/fs/diskio_bios.c > --- syslinux-6.02.orig/core/fs/diskio_bios.c 2013-10-13 21:59:03.000000000 +0400 > +++