similar to: grub (?) issue on Optiplex 780 A15, 6.8 upgrade

Hi All, After updating to the latest kernel, I get subject error at grub. I have no idea as to how to fix this. Booting of the previous kernel is fine. Could someone please help sort this out? Thank you in advance!! Phil Relative info: grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You do not have a

Nope, it doesn't add it to the kernel boot parameters. That was the first thing I checked. As for the bootproto ... DUH. I didn't check that. :) That being solved, yeah it's not bringing up the add-in card now when it boots up. On Thu, Feb 26, 2015 at 12:50 PM, Jason Warr <jason at warr.net> wrote: > > > On Thu, 26 Feb 2015 13:42:57 -0600, Ashley M. Kirchner

On Thu, 26 Feb 2015 13:42:57 -0600, Ashley M. Kirchner <ashley at pcraft.com> wrote: > And after picking this back up this morning .... still no dice. I have > now > blacklisted the one module that would enumerate the add-in ethernet port > so > that is no longer an issue during the kickstart process, however the > following is now happening: > > - kickstart

hi, i upgraded my testsystem running on a Dell Optiplex 780 fine for the last five years from Debian 8 to Debian 9. It also crashes on boot, after complaining abount an errer for the mcelog (-16) mounting the root partition (/dev/md0) loading parport driver (?) afterwards my monitor is out of frequency was not able to run further tests right now. best regards Thomas --------------

Le 03/03/2015 19:25, Jonathan Billings a ?crit : > One of the things that the nvidia driver adds is "nouveau.modeset=0 > rdblacklist=nouveau" to the kernel arguments. Do you see them? I > know that we saw the kernel panic when the nouveau driver was loaded > on a el6.6 system with an NVidia K620, so perhaps when you brought in > X11 you also installed the nouveau

I have NOUVEAU driver disabled however its "showing" in my X log file. [ 140.086] (II) NVIDIA dlloader X Driver 390.59 Wed May 9 21:30:06 PDT 2018 [ 140.086] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 140.086] (II) NOUVEAU driver [ 140.087] (II) NOUVEAU driver for NVIDIA chipset families : [ 140.087] RIVA TNT (NV04) [ 140.087] RIVA TNT2

Or, another rant against systemd. Moderators, put up with it - this is an issue. I tried systemctl start multi-user.target. I tried systemctl stop graphical.target. I finally had to set the multi-user.target as the default, and reboot, to get rid of the nouveau drivers. Note that I tried to modprobe -r, and rmmod with all the modules using nouveau, and couldn't - I kept getting "in

On 05-08-15 10:01, Patrick Masotta wrote: >>>> > Okay, the code in efi/ uses Print() from gnu_efi, but generic code from > core/ like core/elflink/load_env32.c prints their messages and debugging > stuff using printf(). These messages end up nowhere. This may explain > why I never saw anything beyond a certain point, even with debugging > turned on. >

Add "rdblacklist=MODULE_NAME" to your append line in pxelinux.conf file. > Trying that next. It'll have to wait till tomorrow as we're under a serious blizzard/snow event right now and I'd like to get home before all of hell freezes over. However, question, if I blacklist the module, that means during kickstart it doesn't know it's there either, which would cause

On Tue, Mar 03, 2015 at 04:41:01PM +0100, info at microlinux.fr wrote: > Anyway, I rebooted, and then... nothing. System refused even to startup, and > systemd suggested to me that I open journalctl (which taught me nothing). This doesn't make any sense. You said 'nothing' but it also suggested you run journalctl? So it wasn't nothing. What exactly did it do? Did it drop

On Sep 16, 2015, at 5:21 PM, m.roth at 5-cent.us wrote: > I tried systemctl start multi-user.target. I tried systemctl stop > graphical.target. I finally had to set the multi-user.target as the > default, and reboot, to get rid of the nouveau drivers. > > Note that I tried to modprobe -r, and rmmod with all the modules using > nouveau, and couldn't - I kept getting "in

On 01/11/2016 03:52 PM, Wittner, Ben, Ph.D. wrote: > I started trying to do this, but I'm stuck. > I started with http://us.download.nvidia.com/XFree86/Linux-x86_64/340.96/README/installdriver.html , which led me to http://us.download.nvidia.com/XFree86/Linux-x86_64/340.96/README/commonproblems.html#nouveau . I created /etc/modprobe.d/disable-nouveau.conf as instructed then rebooted,

Tom, Bingo! I followed the instructions in the link below, which allowed me to install the nvidia driver, which fixed the original problem with rgl.snapshot. Thanks very much for all your help. I guess I'll file a bug in the CentOS Bug Tracker so that the nouveau driver might get fixed. I'll also post to R-help so someone with the same problem who only searches R-help and not this SIG

On Wed, 25 Feb 2015 17:11:02 -0600, Ashley M. Kirchner <ashley at pcraft.com> wrote: > Add "rdblacklist=MODULE_NAME" to your append line in pxelinux.conf file. >> > > Trying that next. It'll have to wait till tomorrow as we're under a > serious > blizzard/snow event right now and I'd like to get home before all of hell > freezes over.

On 09/16/15 19:50, Jonathan Billings wrote: > On Sep 16, 2015, at 5:21 PM, m.roth at 5-cent.us wrote: >> I tried systemctl start multi-user.target. I tried systemctl stop >> graphical.target. I finally had to set the multi-user.target as the >> default, and reboot, to get rid of the nouveau drivers. >> >> Note that I tried to modprobe -r, and rmmod with all the

I'm on a Supermicro server, X9DA7 motherboard, Intel C602 chipset, 2x 2.4GHz Intel Xeon E5-2665 8-core CPU, 96GB RAM, and I'm running CentOS 6.4. I just tried to use yum to upgrade the kernel from 2.6.32-358 to 2.6.32-431.29.2. However, I get a kernel panic on boot. The first kernel panic I got included stuff about acpi, so I tried adding noacpi noapic to the kernel boot parameters,

On Wed, 25 Feb 2015 16:45:04 -0600, Ashley M. Kirchner <ashley at pcraft.com> wrote: > Out of order meaning, it puts the additional ethernet card as eth0, with > the built-in ports as eth1 and eth2 respectively. WITHOUT the additional > card >installed, it puts the built-in ports as eth0 and eth1, which is > what I want it to do. The additional card should be eth2, at

Updating myself again: On 07-08-15 16:03, Oscar Roozen wrote: > e466d24 still has an issue with png's in vesalinux causing crashes I can confirm this remaining crash is caused by the line "MENU BACKGROUND bootlogo.png". The original bootlogo.png is 640x480. Forcing the videomode with "MENU RESOLUTION 640 480" did not resolve the crashes, nor did resizing the png

Since upgrading from Ubuntu 10.10 I have had problems with graphics. The problems started after I initially upgraded to Ubuntu 11.04 but then installed xubuntu-desktop over it, but I have had the same problem all my fresh installs of Xubuntu 11.04 too. FPS previously averaging about 30 or 35 FPS while playing an OpenGL game with WINE now starts at 20 FPS for 2 or 3 minutes and then slows down to

Good Day, I am not 100% certain if here is the right place to bring this up, however if this is the wrong place for this please redirect me to right place. A few weeks ago I was trying to install KVM on my laptop, I bought a new laptop and immediately after I install the nVidia drivers I receive the following error "libfcoe_device_notification: NETDEV_UNREGISTER lo" I spent several