Re: [CentOS] nvidia on 7.6

2019-03-06 Thread Phil Perry

On 06/03/2019 23:03, Stephen John Smoogen wrote:

On Wed, 6 Mar 2019 at 17:50, Phil Perry  wrote:


On 06/03/2019 21:53, Pete Geenhuizen wrote:



On 03/06/2019 04:21 PM, Phil Perry wrote:

On 06/03/2019 19:30, Pete Geenhuizen wrote:


That is all good and well, but my problem is that I now can't install

vlc smplayer mplayer, or  ffmpeg-libs because they need
ocl-icd-2.2.12-1.el7.x86_64from epel.
I tried to roll back to the previous version via yum history undo but
previous versions are no longer avaialble.



Do they have a hard coded Requires for the ocl-icd package or just an
auto-generated Requires for the libOpenCL.so lib?

If it's the former then the packages in epel need fixing. If it's the
latter then the nvidia package will meet that requirement. You can
either force uninstall ocl-icd, or uninstall ocl-icd and any
dependencies, install/update the nvidia packages and then reinstall
the package you require that depend on libOpenCL.so

Phil,
I don't know if it's a hard coded requires ot auto-generated.
Right now I've removed the rpms that need ocl-icd, updated nvidia but
when I attempt to install vlc smplayer mplayer, or  ffmpeg-libs it fails
because it wants to install ocl-icd-2.2.12-1.el7.x86_64 from epel.
I guess that that means that its a hard coded requirement, is that correct?
Pete



I guess so. Running 'rpm -q --requires ' would tell you.

I only have vlc and ffmpeg-libs installed, and both are installed from
the Nux repo. Neither are built against libOpenCL.so so I'm not able to
comment on what epel have done with their packages.



As far as I can tell the packages vlc, smplayer, mplayer, and ffmpeg
aren't in EPEL. I am guessing they are from rpmfusion but could be
from some other repository.



Thank you Stephen. I assumed because they were pulling a dependency from 
epel that they were also from epel.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Network Bridge - error

2019-03-06 Thread Larry Sevilla
Hi Andrija,

Got the same error message, but different details.

systemctl status network.service
https://pastebin.com/NjtXUwci

journalctl -xe
https://pastebin.com/Kn0Dggmm

My network settings:
https://pastebin.com/JDGJJYVc


On Wed, Mar 6, 2019 at 4:57 PM Andrija Panic 
wrote:

> Hi Larry,
>
> Log says: Bridge support not available: brctl not found
>
> Fix with: yum install bridge-utils
>
> Let me know once you are finished with guide - you are perfect for testing
> this guide (since new to CentOS completely)
>
> I will update the guide once you are done with it - let me know please!
>
> Kind regards,
> Andrija
>
> andrija.pa...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London  WC2E 9DPUK
> @shapeblue
>
>
>
>
> -Original Message-
> From: Larry Sevilla 
> Sent: 06 March 2019 09:45
> To: us...@cloudstack.apache.org; CentOS@centos.org
> Subject: Network Bridge - error
>
> Hi,
>
> I'm new to CentOS. (I have tried Debian, Ubuntu, Devuan & Gentoo).
> And also new to CloudStack.
>
> I'm trying the Quick Installation Guide of CloudStack as pointed by
> Andrija Panic of ShapeBlue
> https://github.com/apache/cloudstack-documentation/blob/master/source/quickinstallationguide/qig.rst
>
> At Configuring the Network topic, I got an error:
>
> [root@localhost ~]# systemctl restart network Job for network.service
> failed because the control process exited with error code.  See "systemctl
> status network.service" and "journalctl -xe"
> for details.
>
> systemctl status network.service
> https://pastebin.com/KzBqJN65
>
> journalctl -xe
> https://pastebin.com/PLQGuLeR
>
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 7.6 kickstart error

2019-03-06 Thread Young, Gregory
At least for debugging, try adding "inst.graphical" to the "append initrd=" 
line in your isolinux.cfg on the .iso image (grub.cfg and the "linuxefi" line 
if you are booting UEFI). Remove "inst.cmdline" and "inst.text", as well as any 
entries of " inst.noninteractive", " inst.noshell" and " inst.headless" from 
the same "append" line, as they will make troubleshooting more 
difficult/impossible. Once you are in the graphical Anaconda, it will take a 
few seconds to check the settings from the kickstart file (you will see 
"warning" bars on various config sections while it verifies the settings). When 
only the Packages section still has a warning bar, click on it and see if that 
helps identify the missing dependencies. I could be wrong, but you might also 
find a yum.log in the /tmp/ folder of the LiveOS image while Anaconda is still 
running (I think it's  to switch to the second console in Anaconda, but 
I could have the wrong key-combo).


Gregory

-Original Message-
From: CentOS  On Behalf Of Steve Clark
Sent: March 6, 2019 7:48 AM
To: centos@centos.org
Subject: Re: [CentOS] CentOS 7.6 kickstart error

On 03/06/2019 07:12 AM, isdtor wrote:
> I am testing a CentOS 7.6 kickstart installation. After kickstart was 
> initiated, the installation stops at some point where a sort of table 
> is printed under "Installation", and the item that fails is 4 - 
> Software selection, Error checking software selection.
>
> I have checked /tmp/packaging.log and /tmp/anaconda.log, but cannot 
> find any errors here that would prevent installation.
>
> Poor error messages, no usable lead for debug.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
Hi,

I have run into this - in my experience it means there is some dependency 
missing.
And you are correct trying to find the error is a PITA.

Steve


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] nvidia on 7.6

2019-03-06 Thread Stephen John Smoogen
On Wed, 6 Mar 2019 at 17:50, Phil Perry  wrote:
>
> On 06/03/2019 21:53, Pete Geenhuizen wrote:
> >
> >
> > On 03/06/2019 04:21 PM, Phil Perry wrote:
> >> On 06/03/2019 19:30, Pete Geenhuizen wrote:
> >>>
> >>> That is all good and well, but my problem is that I now can't install
> >>>
> >>> vlc smplayer mplayer, or  ffmpeg-libs because they need
> >>> ocl-icd-2.2.12-1.el7.x86_64from epel.
> >>> I tried to roll back to the previous version via yum history undo but
> >>> previous versions are no longer avaialble.
> >>>
> >>
> >> Do they have a hard coded Requires for the ocl-icd package or just an
> >> auto-generated Requires for the libOpenCL.so lib?
> >>
> >> If it's the former then the packages in epel need fixing. If it's the
> >> latter then the nvidia package will meet that requirement. You can
> >> either force uninstall ocl-icd, or uninstall ocl-icd and any
> >> dependencies, install/update the nvidia packages and then reinstall
> >> the package you require that depend on libOpenCL.so
> > Phil,
> > I don't know if it's a hard coded requires ot auto-generated.
> > Right now I've removed the rpms that need ocl-icd, updated nvidia but
> > when I attempt to install vlc smplayer mplayer, or  ffmpeg-libs it fails
> > because it wants to install ocl-icd-2.2.12-1.el7.x86_64 from epel.
> > I guess that that means that its a hard coded requirement, is that correct?
> > Pete
> >
>
> I guess so. Running 'rpm -q --requires ' would tell you.
>
> I only have vlc and ffmpeg-libs installed, and both are installed from
> the Nux repo. Neither are built against libOpenCL.so so I'm not able to
> comment on what epel have done with their packages.
>

As far as I can tell the packages vlc, smplayer, mplayer, and ffmpeg
aren't in EPEL. I am guessing they are from rpmfusion but could be
from some other repository.





-- 
Stephen J Smoogen.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] nvidia on 7.6

2019-03-06 Thread Phil Perry

On 06/03/2019 21:53, Pete Geenhuizen wrote:



On 03/06/2019 04:21 PM, Phil Perry wrote:

On 06/03/2019 19:30, Pete Geenhuizen wrote:


That is all good and well, but my problem is that I now can't install

vlc smplayer mplayer, or  ffmpeg-libs because they need 
ocl-icd-2.2.12-1.el7.x86_64from epel.
I tried to roll back to the previous version via yum history undo but 
previous versions are no longer avaialble.




Do they have a hard coded Requires for the ocl-icd package or just an 
auto-generated Requires for the libOpenCL.so lib?


If it's the former then the packages in epel need fixing. If it's the 
latter then the nvidia package will meet that requirement. You can 
either force uninstall ocl-icd, or uninstall ocl-icd and any 
dependencies, install/update the nvidia packages and then reinstall 
the package you require that depend on libOpenCL.so

Phil,
I don't know if it's a hard coded requires ot auto-generated.
Right now I've removed the rpms that need ocl-icd, updated nvidia but 
when I attempt to install vlc smplayer mplayer, or  ffmpeg-libs it fails 
because it wants to install ocl-icd-2.2.12-1.el7.x86_64 from epel.

I guess that that means that its a hard coded requirement, is that correct?
Pete



I guess so. Running 'rpm -q --requires ' would tell you.

I only have vlc and ffmpeg-libs installed, and both are installed from 
the Nux repo. Neither are built against libOpenCL.so so I'm not able to 
comment on what epel have done with their packages.


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] nvidia on 7.6

2019-03-06 Thread Pete Geenhuizen



On 03/06/2019 04:21 PM, Phil Perry wrote:

On 06/03/2019 19:30, Pete Geenhuizen wrote:


That is all good and well, but my problem is that I now can't install

vlc smplayer mplayer, or  ffmpeg-libs because they need 
ocl-icd-2.2.12-1.el7.x86_64from epel.
I tried to roll back to the previous version via yum history undo but 
previous versions are no longer avaialble.




Do they have a hard coded Requires for the ocl-icd package or just an 
auto-generated Requires for the libOpenCL.so lib?


If it's the former then the packages in epel need fixing. If it's the 
latter then the nvidia package will meet that requirement. You can 
either force uninstall ocl-icd, or uninstall ocl-icd and any 
dependencies, install/update the nvidia packages and then reinstall 
the package you require that depend on libOpenCL.so

Phil,
I don't know if it's a hard coded requires ot auto-generated.
Right now I've removed the rpms that need ocl-icd, updated nvidia but 
when I attempt to install vlc smplayer mplayer, or  ffmpeg-libs it fails 
because it wants to install ocl-icd-2.2.12-1.el7.x86_64 from epel.

I guess that that means that its a hard coded requirement, is that correct?
Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] nvidia on 7.6

2019-03-06 Thread Phil Perry

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 conflicts with ocl-icd-2.2.12-1.el7.x86_64

I removed ocl-icd and installed the package, but needless to say I
can't get ocl-icd to install which means that I cant install video
players, vlc smplayer mplayer, or  ffmpeg-libs.

I asked the same question recently and Phil informed me that the
ocl-icd now comes in one of the nvidia  packages, so you no longer
need the one from epel.

That is all good and well, but my problem is that I now can't install

vlc smplayer mplayer, or  ffmpeg-libs because they need 
ocl-icd-2.2.12-1.el7.x86_64from epel.
I tried to roll back to the previous version via yum history undo but 
previous versions are no longer avaialble.




Do they have a hard coded Requires for the ocl-icd package or just an 
auto-generated Requires for the libOpenCL.so lib?


If it's the former then the packages in epel need fixing. If it's the 
latter then the nvidia package will meet that requirement. You can 
either force uninstall ocl-icd, or uninstall ocl-icd and any 
dependencies, install/update the nvidia packages and then reinstall the 
package you require that depend on libOpenCL.so



___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] C 7 anacron issue

2019-03-06 Thread Ulf Volmer
On 04.03.19 23:27, mark wrote:
> Has anyone else seen a problem recently (like, the last few weeks) with
> anacron? We've got a couple of recently-built systems and we're seeing
> Mar  4 17:20:01  crond[25767]: (root) PAM ERROR (Failure setting
> user credentials)
> Mar  4 17:20:01  crond[25767]: (root) FAILED to authorize user
> with PAM (Failure setting user credentials)

My first guess is /etc/security/access.conf.

Best regards
Ulf
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] nvidia on 7.6

2019-03-06 Thread Pete Geenhuizen



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 conflicts with ocl-icd-2.2.12-1.el7.x86_64

I removed ocl-icd and installed the package, but needless to say I
can't get ocl-icd to install which means that I cant install video
players, vlc smplayer mplayer, or  ffmpeg-libs.

I asked the same question recently and Phil informed me that the
ocl-icd now comes in one of the nvidia  packages, so you no longer
need the one from epel.

That is all good and well, but my problem is that I now can't install

vlc smplayer mplayer, or  ffmpeg-libs because they need 
ocl-icd-2.2.12-1.el7.x86_64from epel.
I tried to roll back to the previous version via yum history undo but previous 
versions are no longer avaialble.

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOs 7 i386 & PAE Kernel

2019-03-06 Thread Akemi Yagi
On Wed, Mar 6, 2019 at 7:23 AM Mike McTernan (wavemobile)
 wrote:
>
> On 3/6/19 1:28 PM,  Johnny Hughes wrote:
> > On 3/6/19 6:26 AM, Mike McTernan (wavemobile) wrote:
> > > On 3/5/19 5:48 PM,  Johnny Hughes wrote:
>
> 
>
> > > Last question, if I may - Is there any specific reason why an i686 PAE
> > > kernel built from the main RHEL sources isn't in the AltArch i386 os- 
> > > repo?
> > >
> > > Notably CentOS 6 provided both non-PAE and PAE 32-bit kernels, and
> > > it's that step from CentOS 6 32-bit PAE onto CentOS 7 32-bit which
> > > made me stumble, but okay now.
> >
> > The only reason is .. it is not included in the mainline RHEL 7 kernel 
> > source
> > code.
>
> Ah - I guess since mainline RHEL 7 is only 64-bit on x86 now, it doesn't have 
> to worry about PAE vs non-PAE kernels.
>
> ...
> > I have no objections trying to make PAE work with that kernel .. Patches
> > accepted :D
> >
> > https://bugs.centos.org/view.php?id=6828
>
> So with what I know now (thank you!) I recon the mainline 4.14 is probably a 
> better tested path for a 32-bit x86 PAE kernel, rather than starting at RHEL 
> 7.  And since you are already building that kernel it's good news all round 
> :-)
>
> Kind Regards,
>
> Mike

Going for the 4.14 kernel is absolutely a better choice. The i686 plus
kernel is just lucky to be existing. It would not have been possible
to maintain it without great support from people like Pablo and @kabe.
We initially got the 32-bit version from Springdale (formerly Puias).
Then they stopped building at some point. Building it becomes harder
and harder with each release, it seems. So, there is no guarantee that
there is another update to the i686 plus kernel.

Akemi



Akemi
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOs 7 i386 & PAE Kernel

2019-03-06 Thread Mike McTernan (wavemobile)
On 3/6/19 1:28 PM,  Johnny Hughes wrote:
> On 3/6/19 6:26 AM, Mike McTernan (wavemobile) wrote:
> > On 3/5/19 5:48 PM,  Johnny Hughes wrote:


 
> > Last question, if I may - Is there any specific reason why an i686 PAE
> > kernel built from the main RHEL sources isn't in the AltArch i386 os- repo?
> >
> > Notably CentOS 6 provided both non-PAE and PAE 32-bit kernels, and
> > it's that step from CentOS 6 32-bit PAE onto CentOS 7 32-bit which
> > made me stumble, but okay now.
> 
> The only reason is .. it is not included in the mainline RHEL 7 kernel source
> code.

Ah - I guess since mainline RHEL 7 is only 64-bit on x86 now, it doesn't have 
to worry about PAE vs non-PAE kernels.

...
> I have no objections trying to make PAE work with that kernel .. Patches
> accepted :D
> 
> https://bugs.centos.org/view.php?id=6828

So with what I know now (thank you!) I recon the mainline 4.14 is probably a 
better tested path for a 32-bit x86 PAE kernel, rather than starting at RHEL 7. 
 And since you are already building that kernel it's good news all round :-)

Kind Regards,

Mike
--


wavemobile
Warning: The information transmitted is intended only for the person or entity 
to which it is addressed and may contain confidential and/or privileged 
material. Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon, this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender immediately and delete the material from any computer.
wavemobile Ltd is registered in England and Wales, Registration Number: 
04780898.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] nvidia on 7.6

2019-03-06 Thread Fred Smith
On Wed, Mar 06, 2019 at 07:26:42AM -0500, Pete Geenhuizen wrote:
> 
> On 03/02/2019 05:41 AM, Phil Perry wrote:
> >
> >Hi Gerry,
> >
> >I've updated the nvidia 340xx legacy package set for el7.6, and
> >released the packages to the elrepo testing repository.
> >
> >Please could you test them and let me know if they work as
> >expected. To install:
> >
> >yum --enablerepo=elrepo-testing install kmod-nvidia-340xx
> >nvidia-x11-drv-340xx nvidia-x11-drv-340xx-libs
> >
> >if you need 32-bit support then you will also need to install the
> >corresponding
> >nvidia-x11-drv-340xx-libs-340.107-2.el7_6.elrepo.i686.rpm package.
> >
> >Thinking about it, I'm not sure these packages are going to work
> >as the 340 series NVIDIA driver predates the conversion to GLVND
> >(support was added in version 361), see here:
> >
> >https://devtalk.nvidia.com/default/topic/915640/multiple-glx-client-libraries-in-the-nvidia-linux-driver-installer-package/
> >
> >
> >but I have no way to test them so I'll leave that to you.
> >
> >Phil
> >
> >___
> >CentOS mailing list
> >CentOS@centos.org
> >https://lists.centos.org/mailman/listinfo/centos
> >
> Phil,
> 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 conflicts with ocl-icd-2.2.12-1.el7.x86_64
> 
> I removed ocl-icd and installed the package, but needless to say I
> can't get ocl-icd to install which means that I cant install video
> players, vlc smplayer mplayer, or  ffmpeg-libs.

I asked the same question recently and Phil informed me that the
ocl-icd now comes in one of the nvidia  packages, so you no longer
need the one from epel.


-- 
 Fred Smith -- fre...@fcshome.stoneham.ma.us -
  "For him who is able to keep you from falling and to present you before his 
 glorious presence without fault and with great joy--to the only God our Savior
 be glory, majesty, power and authority, through Jesus Christ our Lord, before
 all ages, now and forevermore! Amen."
- Jude 1:24,25 (niv) -
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Network Bridge - error

2019-03-06 Thread Warren Young
On Mar 6, 2019, at 1:44 AM, Larry Sevilla  wrote:
> 
> systemctl status network.service
> https://pastebin.com/KzBqJN65

…which says brctl doesn’t exist, so if you go searching for it, you find that 
it’s in the bridge-utils package.  So, your next step is:

$ sudo yum install bridge-utils

I have no idea whether that solves your entire problem, having never done 
anything with CloudStack, but it’ll at least get you one more step down the 
path.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOs 7 i386 & PAE Kernel

2019-03-06 Thread Johnny Hughes
On 3/6/19 6:26 AM, Mike McTernan (wavemobile) wrote:
> On 3/5/19 5:48 PM,  Johnny Hughes wrote:
>> On 3/4/19 3:39 PM, Mike McTernan (wavemobile) wrote:



> Last question, if I may - Is there any specific reason why an i686 PAE kernel 
> built from the main RHEL sources isn't in the AltArch i386 os- repo?  
> 
> Notably CentOS 6 provided both non-PAE and PAE 32-bit kernels, and it's 
> that step from CentOS 6 32-bit PAE onto CentOS 7 32-bit which made me 
> stumble, but okay now.
> 

The only reason is .. it is not included in the mainline RHEL 7 kernel
source code.

The kernel we are using there is our CentOS Plus kernel.  The reason it
is the CentOS Plus kernel is that the RHEL 7 kernel SPEC does not build
anything on i386 except the kernel-headers rpm.  We already make
modifications to produce a CentOS Plus kernel for x86_64 .. so we also
rolled in changes for making that kernel build on i386.  Since it does
not do PAE by default, we don't do it.

CentOS QA team member Akemi Yagi maintains the plus kernels for both
CentOS-6 and CentOS-7 and QA team member (and armhfp AltArch maintainer)
Pablo Greco also helps her frequently to make changes to that kernel to
make it work with i386.

I have no objections trying to make PAE work with that kernel .. Patches
accepted :D

https://bugs.centos.org/view.php?id=6828



signature.asc
Description: OpenPGP digital signature
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOS 7.6 kickstart error

2019-03-06 Thread Steve Clark
On 03/06/2019 07:12 AM, isdtor wrote:
> I am testing a CentOS 7.6 kickstart installation. After kickstart was 
> initiated,
> the installation stops at some point where a sort of table is printed under
> "Installation", and the item that fails is 4 - Software selection, Error
> checking software selection.
>
> I have checked /tmp/packaging.log and /tmp/anaconda.log, but cannot find any
> errors here that would prevent installation.
>
> Poor error messages, no usable lead for debug.
>
> ___
> CentOS mailing list
> CentOS@centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
Hi,

I have run into this - in my experience it means there is some dependency 
missing.
And you are correct trying to find the error is a PITA.

Steve


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] nvidia on 7.6

2019-03-06 Thread Pete Geenhuizen


On 03/02/2019 05:41 AM, Phil Perry wrote:


Hi Gerry,

I've updated the nvidia 340xx legacy package set for el7.6, and 
released the packages to the elrepo testing repository.


Please could you test them and let me know if they work as expected. 
To install:


yum --enablerepo=elrepo-testing install kmod-nvidia-340xx 
nvidia-x11-drv-340xx nvidia-x11-drv-340xx-libs


if you need 32-bit support then you will also need to install the 
corresponding 
nvidia-x11-drv-340xx-libs-340.107-2.el7_6.elrepo.i686.rpm package.


Thinking about it, I'm not sure these packages are going to work as 
the 340 series NVIDIA driver predates the conversion to GLVND (support 
was added in version 361), see here:


https://devtalk.nvidia.com/default/topic/915640/multiple-glx-client-libraries-in-the-nvidia-linux-driver-installer-package/ 



but I have no way to test them so I'll leave that to you.

Phil

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Phil,
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 conflicts with ocl-icd-2.2.12-1.el7.x86_64

I removed ocl-icd and installed the package, but needless to say I can't 
get ocl-icd to install which means that I cant install video players, 
vlc smplayer mplayer, or  ffmpeg-libs.


Pete

--
Unencumbered by the thought process.
 -- Click and Clack the Tappet brothers


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] CentOs 7 i386 & PAE Kernel

2019-03-06 Thread Mike McTernan (wavemobile)
On 3/5/19 5:48 PM,  Johnny Hughes wrote:
> On 3/4/19 3:39 PM, Mike McTernan (wavemobile) wrote:
> > Looking around, I found the following repo:
> > https://mirrors.dotsrc.org/centos-altarch/7/kernel/i386/
...
> That directory (kernel/ under altarch) is basically for the armhfp main 
> kernel,
> but we are building also for aarch64, i386 and even x86_64.  Its purpose
> (other than armhfp, where it is the main kernel) is mainly for IoT type
> hardware (think hobby boards, embedded systems, etc that need newer
> kernels for hardware support .. think things like this:
> 
> https://www.intel.com/content/www/us/en/products/solutions/iot.html
> 
> or
> 
> 64 bit aarch64 bit type IoT boards, etc.
> 
> You certainly CAN use them on anything you want and it will be maintained
> as it is the main kernel for armhfp.

That’s excellent, and most helpful.  So that brings support for newer
hardware, AND provides a PAE version which works on all my hardware 
nicely.

This might be useful to a number of people, and it was only through looking
around CentOS 7 on Raspberry Pi that I happened across the kernel repo.  
Might it be worth linking to the repo from the AltArch/i386 page:

https://wiki.centos.org/SpecialInterestGroup/AltArch/i386

> Both of these branches / repos are NOT designed to run Enterprise type
> workloads (that is why we have the main RH kernel from RHEL sources) ..

Yep - wise words and duly noted, thank you.  My application is small scale,
so should be fine.  Software is only as good as the testing anyway :-)

Last question, if I may - Is there any specific reason why an i686 PAE kernel 
built from the main RHEL sources isn't in the AltArch i386 os- repo?  

Notably CentOS 6 provided both non-PAE and PAE 32-bit kernels, and it's 
that step from CentOS 6 32-bit PAE onto CentOS 7 32-bit which made me 
stumble, but okay now.

Many Thanks again,

Mike
--


wavemobile
Warning: The information transmitted is intended only for the person or entity 
to which it is addressed and may contain confidential and/or privileged 
material. Any review, retransmission, dissemination or other use of, or taking 
of any action in reliance upon, this information by persons or entities other 
than the intended recipient is prohibited. If you received this in error, 
please contact the sender immediately and delete the material from any computer.
wavemobile Ltd is registered in England and Wales, Registration Number: 
04780898.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] CentOS 7.6 kickstart error

2019-03-06 Thread isdtor
I am testing a CentOS 7.6 kickstart installation. After kickstart was initiated,
the installation stops at some point where a sort of table is printed under
"Installation", and the item that fails is 4 - Software selection, Error
checking software selection.

I have checked /tmp/packaging.log and /tmp/anaconda.log, but cannot find any
errors here that would prevent installation.

Poor error messages, no usable lead for debug.

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos


[CentOS] CentOS-announce Digest, Vol 169, Issue 2

2019-03-06 Thread centos-announce-request
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CESA-2019:0436 Moderate CentOS 7 java-11-openjdk  Security
  Update (Johnny Hughes)
   2. CEBA-2019:0452 CentOS 7 java-1.8.0-openjdk BugFix Update
  (Johnny Hughes)
   3. CESA-2019:0464 Moderate CentOS 7  java-1.7.0-openjdk Security
  Update (Johnny Hughes)


--

Message: 1
Date: Wed, 6 Mar 2019 00:33:04 +
From: Johnny Hughes 
To: centos-annou...@centos.org
Subject: [CentOS-announce] CESA-2019:0436 Moderate CentOS 7
java-11-openjdk Security Update
Message-ID: <20190306003304.ga19...@bstore1.rdu2.centos.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Security Advisory 2019:0436 Moderate

Upstream details at : https://access.redhat.com/errata/RHSA-2019:0436

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 

x86_64:
455611eda46b23a443562b371b11031c0c7cd755fa461d36c1265aa5ff0581b7  
java-11-openjdk-11.0.2.7-0.el7_6.i686.rpm
2d04a5ed238be61cc3eca8bb760e36ba730bb97a4948d93f8cb1abb23c2efdec  
java-11-openjdk-11.0.2.7-0.el7_6.x86_64.rpm
9382cbbb2e508d3c9af6c2dd464f6a2a54b8f7c4c42abc5a8a5e8afc2c9d1b18  
java-11-openjdk-debug-11.0.2.7-0.el7_6.i686.rpm
3bcbcc3a783c4c9b0ccf5dace193f834657c724d89effeb69ef920b41fb33b93  
java-11-openjdk-debug-11.0.2.7-0.el7_6.x86_64.rpm
31723eed1292300403a09ff8ad95550bbf37c29a6868a1ad5d911ef711dd50b7  
java-11-openjdk-demo-11.0.2.7-0.el7_6.i686.rpm
b5a6567ecfe5a58f01f53ac30c2eb2c11575efcd17cae90582a51176e4db2498  
java-11-openjdk-demo-11.0.2.7-0.el7_6.x86_64.rpm
7818ee07653a778293818a02c86eb6a946b7bb826978e243e526fc85340e3dc5  
java-11-openjdk-demo-debug-11.0.2.7-0.el7_6.i686.rpm
979689c0138cce99224c77370217d07a8504b57b25d054987931ff24b6ad5b09  
java-11-openjdk-demo-debug-11.0.2.7-0.el7_6.x86_64.rpm
1573dc9a08c6d3a39c6cd2f303f0228e498f281f05d7f91692eddeb8bbe19f28  
java-11-openjdk-devel-11.0.2.7-0.el7_6.i686.rpm
18f3a3ac00fbbcb2228d97592fab9d420b1ce0717e7f7aaa4e99dff2794bb9d7  
java-11-openjdk-devel-11.0.2.7-0.el7_6.x86_64.rpm
86032a3878de01037dcbe81c1d2360a59cbf7db7ec54a9cad9f58eec4c2c6e6b  
java-11-openjdk-devel-debug-11.0.2.7-0.el7_6.i686.rpm
f734df7c461a3b68202d0075e3d0089e2d93287e6d0b9679a136534eec1ae77d  
java-11-openjdk-devel-debug-11.0.2.7-0.el7_6.x86_64.rpm
6d5ee0ce4a9537a6066e0dff983969a265946965887b45709490daa08409a4de  
java-11-openjdk-headless-11.0.2.7-0.el7_6.i686.rpm
88e6bd393337cd85c421c0ab6c9f2bdb1846344fe4db8ee38dec4b688bf528cb  
java-11-openjdk-headless-11.0.2.7-0.el7_6.x86_64.rpm
758e1a74d5fb435c5ccc0f4307cc0d2a6112eb242da3da7a86294ae4386b9f88  
java-11-openjdk-headless-debug-11.0.2.7-0.el7_6.i686.rpm
50036b97862857f7f0d60569043bfc762c5eb4ddf7069cbfa8e9bdb56d841166  
java-11-openjdk-headless-debug-11.0.2.7-0.el7_6.x86_64.rpm
6c6a3d3380df1c070dc230788e25eb50b54f81ffa834d36ce2bf88e38edcf6eb  
java-11-openjdk-javadoc-11.0.2.7-0.el7_6.i686.rpm
4e3821a2bba3cfd3dd947359b8cc396e5868bf52946d99f44ea81b9dd825e3b4  
java-11-openjdk-javadoc-11.0.2.7-0.el7_6.x86_64.rpm
6c881d9c081be6182e821ec3d956f342054201db468abdd87123c1b23495389a  
java-11-openjdk-javadoc-debug-11.0.2.7-0.el7_6.i686.rpm
65c8d2eb44491647569d6a37f335e49e941e4bb6f910cb5171bb819194585189  
java-11-openjdk-javadoc-debug-11.0.2.7-0.el7_6.x86_64.rpm
64050c25f1ea9eca22505264d5b49a3de521f0ca2b82f1dadb8f58f909a74f1e  
java-11-openjdk-javadoc-zip-11.0.2.7-0.el7_6.i686.rpm
e9d529169e11e3456e6d989385396839301203a1cedf4a7191073d944d015759  
java-11-openjdk-javadoc-zip-11.0.2.7-0.el7_6.x86_64.rpm
14d42846b958e0a458bc47d602817baf8e5e0718cd37b5ede4c19a6b4241ab9d  
java-11-openjdk-javadoc-zip-debug-11.0.2.7-0.el7_6.i686.rpm
84a5c81828b2e2169f5ab56b13cf9a87ccfa87b17e12c988bf49b60f6e8bd384  
java-11-openjdk-javadoc-zip-debug-11.0.2.7-0.el7_6.x86_64.rpm
2ea9aa835b7f1da2c775da64c8feb4cc373c795bb06613c76f3284a566a804d4  
java-11-openjdk-jmods-11.0.2.7-0.el7_6.i686.rpm
0719378192a36086f445ae451c6345d018aec419a4f2bbb8744dda201086e524  
java-11-openjdk-jmods-11.0.2.7-0.el7_6.x86_64.rpm
9a75948d5575123c33ec0186b4b23f99384a3c6e83a1b95139ed0a23cff3c396  
java-11-openjdk-jmods-debug-11.0.2.7-0.el7_6.i686.rpm
1bf9787d5c284f5156206ea8ca3fbfdb93a516d1d75b008d52c15d97520c3776  
java-11-openjdk-jmods-debug-11.0.2.7-0.el7_6.x86_64.rpm
cc12b310883fa4d93a221810e81493b96fba379d16c0b1fb6bf7b234df06cebc  
java-11-openjdk-src-11.0.2.7-0.el7_6.i686.rpm
d084163ae25b8e7aa8342bfc8cdbf401c69cae016c9c8e4196dc0f195ef3b297  
java-11-openjdk-src-11.0.2.

[CentOS] Network Bridge - error

2019-03-06 Thread Larry Sevilla
Hi,

I'm new to CentOS. (I have tried Debian, Ubuntu, Devuan & Gentoo).
And also new to CloudStack.

I'm trying the Quick Installation Guide of CloudStack as pointed by Andrija
Panic of ShapeBlue
https://github.com/apache/cloudstack-documentation/blob/master/source/quickinstallationguide/qig.rst

At Configuring the Network topic, I got an error:

[root@localhost ~]# systemctl restart network
Job for network.service failed because the control process exited with
error code.  See "systemctl status network.service" and "journalctl -xe"
for details.

systemctl status network.service
https://pastebin.com/KzBqJN65

journalctl -xe
https://pastebin.com/PLQGuLeR
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos