similar to: Shorewall and the latest kernel problem

On 01/18/18 09:01, Johnny Hughes wrote: > On 01/18/2018 07:51 AM, Phelps, Matthew wrote: >> On Thu, Jan 18, 2018 at 5:03 AM, Johnny Hughes <johnny at centos.org> wrote: >> >> So, if we applied the previous microcode update, and all our machines >> rebooted OK, then we don't need to fallback? >> >> Also, do we know if the updated CentOS microcode RPM

On 09/19/17 11:44, m.roth at 5-cent.us wrote: > Pete Geenhuizen wrote: >> I upgraded from 7.3 to 7.4 over the weekend.? Everything went well >> except that I can't login because the screen is black with a cursor. >> >> If reboot boot the 7.3 kernel 3.10.0-514.26.2.el7.x86_64 kernel >> everything works just fine, so my guess is that there's a kernel issue

I upgraded from 7.3 to 7.4 over the weekend.? Everything went well except that I can't login because the screen is black with a cursor. If reboot boot the 7.3 kernel 3.10.0-514.26.2.el7.x86_64 kernel everything works just fine, so my guess is that there's a kernel issue with the hardware, specifically the Skylake processor. Has anyone else run into this problem and if so can how I

I upgraded to C 7.4 from C 6.9 on my laptop and all was well.? As with C6 and the other C7 hosts that I have, if launch a terminal from the desktop it opens in [ user at host Desktop ]$ which is just fine. I restored parts of my C 6.9 home into C7.4 and now everything shows up on my desktop and when I open a terminal it now opens up in? [ user at host ~ ]$ Obviously I overwrote the setting,

On Mon, June 15, 2015 11:16 am, Pete Geenhuizen wrote: > Enable it in /usr/share/logwatch/default.conf/services/zz-runtime.conf Thanks a lot! Helps you to be aware that you definitely missed something important if you haven't the box rebooted during more than 45-60 days... Valeri > > Pete > > On 06/15/15 09:58, James B. Byrne wrote: >> CentOS-6.6 >> >> Can

I'm upgrading from CentOS6 to CentOS 7. I run 2 weather stations on C6 and have one of them attached to ttyS0 which is on the motherboard, and the other to ttyS2 which in on an add-on PCI serial card. I'm migrating the weather stations another host running C7 which has a similar hardware configuration.? When I connect the weather station to ttyS0 everything works fine, but when I try

On 01/28/18 20:15, Fred Smith wrote: > On Sun, Jan 28, 2018 at 12:10:29PM -0500, Pete Geenhuizen wrote: >> I'm upgrading from CentOS6 to CentOS 7. >> >> I run 2 weather stations on C6 and have one of them attached to >> ttyS0 which is on the motherboard, and the other to ttyS2 which in >> on an add-on PCI serial card. >> >> I'm migrating the

CentOS-6.6 Can logwatch be configured to display the system uptime as part of the reporting prologue? If not then what would be the recommended way of including this information in a daily logwatch report? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne

----- Original Message ----- | Not tried automount with Centos 7 nor with selinux. | | With that said autofs relies on nfs mounting to work, so have you | started there by attempting to manually mount /home? | | Another place to look is at the hostname. I've had problems where auto | mount doesn't like the short name and insists on using a FQDN, to get | around that you could try using

I'm migrating from C7 to C8.? I'm currently using autofs, but alas autofs has been dropped in C8 for the AMD automounter. I have some very ancient knowledge of AMD, I used it when it was first introduced many years ago on Solaris and moved to Sun's automounter when it was introduced. So now it's back to square one. I used automount2amd to convert one of my existing maps,

I don't see it either. On 07/09/16 08:36, Walter H. wrote: > On 07.07.2016 22:19, Helmut Drodofsky wrote: >> Helo, >> >> update is in EPEL repository. >> > strange, here it isn't ... > > > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos

On 08/02/15 12:33, Pete Geenhuizen wrote: > > On 02/08/15 06:12, Ned Slider wrote: >> >> On 08/02/15 05:09, S.Tindall wrote: >> Yes, just to reiterate: >> >> yum erase kmod-nvidia >> yum install kmod-nvidia-340xx >> reboot >> >> You will then be on the correct driver branch and will get the >> appropriate driver updates going

On 08/02/15 14:24, Pete Geenhuizen wrote: > > On 02/08/15 07:45, Ned Slider wrote: >> >> On 08/02/15 12:33, Pete Geenhuizen wrote: >> No, you don't have the package kmod-nvidia-340xx installed. You have >> kmod-nvidia VERSION 340.65. In the first example, the package NAME is >> kmod-nvidia-340xx (the -340xx is part of the package name, NOT the >>

On 06/03/2019 19:30, Pete Geenhuizen wrote: > > > On 03/06/2019 09:59 AM, Fred Smith wrote: >> >>> I tried to install this and ran into a conflict >>> >>> --> Processing Conflict: >>> nvidia-x11-drv-340xx-340.107-2.el7_6.elrepo.x86_64 conflicts ocl-icd >>> --> Finished Dependency Resolution >>> Error: nvidia-x11-drv-340xx

On 01/18/18 11:31, Matthew Miller wrote: > On Thu, Jan 18, 2018 at 11:01:18AM -0500, Pete Geenhuizen wrote: >> Do we update the microcode now or do we wait until the latest >> microcode_ctl rpm is available and then tackle this issue? > Check with your hardware vendor for BIOS/EFI firmware updates. Apply > those. > > > Thanks for the reply, but you missed what I was

On 09/07/2016 14:15, Walter H. wrote: > On 09.07.2016 14:39, Pete Geenhuizen wrote: >> I don't see it either. >> >> On 07/09/16 08:36, Walter H. wrote: >>> On 07.07.2016 22:19, Helmut Drodofsky wrote: >>>> Helo, >>>> >>>> update is in EPEL repository. >>>> >>> strange, here it isn't ... > the reason:

On 11/03/2019 12:41, Pete Geenhuizen wrote: > Hi Pete, > On 03/07/2019 01:56 AM, Phil Perry wrote: >> On 06/03/2019 23:03, Stephen John Smoogen wrote: >> >> Thank you Stephen. I assumed because they were pulling a dependency >> from epel that they were also from epel. >> > > Been out of town, yes I goofed vlc, smplayer, mplayer, and ffmpeg aren't

On 09/19/17 11:58, Richard wrote: > > >> Date: Tuesday, September 19, 2017 11:53:24 -0400 >> From: Pete Geenhuizen <pete at geenhuizen.net> >> >> On 09/19/17 11:44, m.roth at 5-cent.us wrote: >>> Pete Geenhuizen wrote: >>>> I upgraded from 7.3 to 7.4 over the weekend.? Everything went >>>> well except that I can't login

It was the mid/late-90s, but I seem to recall Bourne being the default shell, although sh/ksh/csh were all available with a typical install. On Fri, Apr 24, 2015 at 8:32 AM, Scott Robbins <scottro at nyc.rr.com> wrote: > On Fri, Apr 24, 2015 at 08:02:56AM -0400, mark wrote: > > On 04/24/15 06:57, Pete Geenhuizen wrote: > > > > > >On 04/24/15 06:07, E.B. wrote:

On 09/19/17 11:01, Pete Geenhuizen wrote: > I upgraded from 7.3 to 7.4 over the weekend.? Everything went well? > except that I can't login because the screen is black with a cursor. > > If reboot boot the 7.3 kernel 3.10.0-514.26.2.el7.x86_64 kernel? > everything works just fine, so my guess is that there's a kernel > issue? > with the hardware, specifically the