similar to: C7: kernel-3.10.0-693.2.2, huh?

Fred Smith wrote: > On Thu, Oct 05, 2017 at 09:56:57AM -0400, m.roth at 5-cent.us wrote: >> Ok, folks, >> >> I've identified what my problem is, trying to install the NVidia >> proprietary drivers: in kernel-devel-3.10.0-514.26.2.el7.x86_64, there >> is a file >> /usr/src/kernels/3.10.0-514.26.2.el7.x86_64/include/linux/fence.h >> >> It

Albert McCann wrote: >> -----Original Message----- >> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of m.roth at 5- >> cent.us >> Sent: Thursday, October 05, 2017 10:58 AM >> To: CentOS mailing list <centos at centos.org> >> Subject: Re: [CentOS] Missing file in current kernel-devel package >> >> Fred Smith wrote: >> >

Johnny Hughes wrote: > On 10/05/2017 10:17 AM, m.roth at 5-cent.us wrote: >> Albert McCann wrote: >>>> -----Original Message----- >>>> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of m.roth at 5- >>>> cent.us >>>> Sent: Thursday, October 05, 2017 10:58 AM >>>> To: CentOS mailing list <centos at centos.org>

-----Original Message----- From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of Noam Bernstein Sent: Sunday, October 22, 2017 8:54 AM To: CentOS mailing list <centos at centos.org> Subject: [CentOS] Areca RAID controller on latest CentOS 7 (1708 i.e. RHEL 7.4) kernel 3.10.0-693.2.2.el7.x86_64 > Is anyone running any Areca RAID controllers with the latest CentOS 7 kernel, >

Hi, folks, Well, still more fun (for values of fun approaching zero): 1. Went to install CUDA 9.0... well, gee, there is *no* CUDA 9.0. Even though I installed the 9 repo, all that I get is 8. I've used their webform, and an waiting on a reply. 2. I remove all nvidia packages. 3. It appears that the kmod-nvidia is what I need; that's what nvidia-detect

Folks I have two USB connected drives, configured as a mirrored-pair in ZFS. It's been working fine UNTIL I updated Centos from 3.10.0-862.14.4.el7.x86_64 to 3.10.0-957.1.3.el7.x86_64 The import of the pools didn't happen at boot. When I tried executing: zpool list I got the diagnostic suggesting I do /sbin/modprobe zfs And that command claimed the module didn't exist. YUM

Ok, folks, I've identified what my problem is, trying to install the NVidia proprietary drivers: in kernel-devel-3.10.0-514.26.2.el7.x86_64, there is a file /usr/src/kernels/3.10.0-514.26.2.el7.x86_64/include/linux/fence.h It does not exist in the kernel-devel-3.10.0-693.2.2.el7.x86_64 package. Is this something that got missed, or did HR drop it, or....? mark

Hi everyone, I updated the kernel from 3.10.0-514.16.1.el7.x86_64 to 3.10.0-693.2.2.el7.x86_64 . While I was following these steps https://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom (I knew that I needed to compile again everything) in order to activate WIFI, the laptop crashed doing # depmod -a # modprobe wl Noting that I replaced (naively) # depmod $(uname -r) from the guide (stupid

Everyone, I have two desktop units with : Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz that do not allow the login screen to appear after the update of : kernel-3.10.0-693.5.2.el7.x86_64 and kernel-3.10.0-693.2.2.el7.x86_64 Both of these units worked properly with kernel.x86_64 3.10.0-514.26.2.el7 I am not sufficiently familiar with grub to know if the problem is related to grub or related to the

Hi All After upgrading to 7.2, I'm getting an immediate kernel panic on boot Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots fine How can I go about diagnosing the problem here? thanks Duncan

Phil Perry wrote: > On 27/09/17 16:49, m.roth at 5-cent.us wrote: >> Hi, folks, >> >> Well, still more fun (for values of fun approaching zero): >> >> 1. Went to install CUDA 9.0... well, gee, there is *no* CUDA 9.0. >> Even though I installed the 9 repo, all that I get is 8. I've >> used their webform, and an waiting on a

Following the advice on this mailing list, I rebuilt (from scratch) Centos 7.8. I added the following line into /etc/yum.conf before the first update: exclude=grub2* shim* mokutil The system worked fine. I was able to do general updates yum -y update and all was well. HOWEVER, following Johnny Hughes' directions: a) remove the 'exclude' line from yum.conf b) perform update:

On Tue, Oct 24, 2017 at 3:36 AM, Akemi Yagi <amyagi at gmail.com> wrote: > On Mon, Oct 23, 2017 at 11:08 PM, Akemi Yagi <amyagi at gmail.com> wrote: > >> On Mon, Oct 23, 2017 at 12:57 PM, Karl Johnson <karljohnson.it at gmail.com> >> wrote: >> >>> On Sat, May 20, 2017 at 8:30 PM, Sarah Newman <srn at prgmr.com> wrote: >>>

Duncan Brown wrote: > On 03/12/2015 17:00, m.roth at 5-cent.us wrote: >> Duncan Brown wrote: >>> On 03/12/2015 14:29, Leon Fauster wrote: >>>> Am 03.12.2015 um 15:06 schrieb Duncan Brown <centos2 at duncb.co.uk>: >>>>> On 03/12/2015 13:54, Jonathan Billings wrote: >>>>>> On Thu, Dec 03, 2015 at 01:44:47PM +0000, Duncan Brown

------------ Original Message ------------ > Date: Sunday, March 01, 2015 20:06:26 -0500 > From: Fred Smith <fredex at fcshome.stoneham.ma.us> > To: centos at centos.org > Subject: [CentOS] installing C7 on a laptop with Win7, dual boot > > Hi all! > > I've just installed C7 on my netbook that already contained Win7 > (and also Fedora 19, which the C7 is

On 01/08/2018 02:10 PM, Shaun Reitan wrote: > While installing the experemental kernel on a CentOS 7 PV the following > happened. After a reboot of the PV the kernel looks to be installed but > there is no option for booting it in grub. ?I attempted to run yum > reinstall kernel-4.9.75-204.el7.centos.x86_64 and it installed fine but > still no entry in grub. No initramfs existed and

I dont see anything hfsplus in the modules area??? > uname -r > > 3.10.0-327.28.2.el7.x86_64 > > [root at nuc5i3 ~]# find /lib/modules/3.10.0-327.28.2.el7.x86_64/ |grep hfs > /lib/modules/3.10.0-327.28.2.el7.x86_64/kernel/fs/squashfs > /lib/modules/3.10.0-327.28.2.el7.x86_64/kernel/fs/squashfs/squashfs.ko >

Hello CentOS users, in the recent time I keep getting the logwatch warnings from my 2 dedicated servers running CentOS 7.4.1708. I guess because of the numerous kernel updates (because of Spectre+Meltdown) in the near past? Could someone please suggest me, which files in my /boot partition would be safe to delete? I would like to avoid the situation of having to boot the rescue partiton etc.

I experienced a bug that is likely the same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1350373 . Commit b7dd0e350e0bd4c0fddcc9b8958342700b00b168 , which is supposed to fix it, doesn't appear in this kernel and doesn't apply cleanly either. Is there any point in trying to backport the patch? The backtrace is as follows: [ 32.304666] ------------[ cut here ]------------ [

Il 07/08/19 20:15, Akemi Yagi ha scritto: > On Wed, Aug 7, 2019 at 9:00 AM Alessandro Baggi > <alessandro.baggi at gmail.com> wrote: >> >> Il 07/08/19 01:02, Phil Perry ha scritto: >>> On 06/08/2019 14:45, Alessandro Baggi wrote: > >>> Please post the actual error message in dmesg or /var/log/messages. >>> >>> It's likely that the