On 6/1/22 23:40, Fabian Arrotin wrote:
> On 02/06/2022 00:22, Orion Poplawski wrote:
>> On 6/1/22 13:43, Fabian Arrotin wrote:
>>> On 01/06/2022 19:51, Orion Poplawski wrote:
Looks like the GPG key we use to sign our RPMs is not longer good with EL9:
# rpm --import RPM-GPG-KEY-nwra
>
On 02/06/2022 00:22, Orion Poplawski wrote:
On 6/1/22 13:43, Fabian Arrotin wrote:
On 01/06/2022 19:51, Orion Poplawski wrote:
Looks like the GPG key we use to sign our RPMs is not longer good with EL9:
# rpm --import RPM-GPG-KEY-nwra
error: RPM-GPG-KEY-nwra: key 1 import failed
gpg key info:
On 6/1/22 13:43, Fabian Arrotin wrote:
> On 01/06/2022 19:51, Orion Poplawski wrote:
>> Looks like the GPG key we use to sign our RPMs is not longer good with EL9:
>>
>> # rpm --import RPM-GPG-KEY-nwra
>> error: RPM-GPG-KEY-nwra: key 1 import failed
>>
>> gpg key info:
>>
>> sec rsa2048/35DDB0B862
On 01/06/2022 19:51, Orion Poplawski wrote:
Looks like the GPG key we use to sign our RPMs is not longer good with EL9:
# rpm --import RPM-GPG-KEY-nwra
error: RPM-GPG-KEY-nwra: key 1 import failed
gpg key info:
sec rsa2048/35DDB0B86218AC2F
created: 2017-08-16 expires: never usage
Looks like the GPG key we use to sign our RPMs is not longer good with EL9:
# rpm --import RPM-GPG-KEY-nwra
error: RPM-GPG-KEY-nwra: key 1 import failed
gpg key info:
sec rsa2048/35DDB0B86218AC2F
created: 2017-08-16 expires: never usage: SC
trust: ultimate validity: ultima
Il 2021-12-03 15:46 Johnny Hughes ha scritto:
sssd-client-1.16.5-10.el7_9.11.i686.rpm exists and is here:
http://mirror.centos.org/centos/7.9.2009/updates/x86_64/Packages/
Not sure why you are not seeing it in your update.
It is an Azure CentOS instance, which is pre-configured for using
ex-
On 12/3/21 02:52, Gionatan Danti wrote:
Dear list,
I have an issue updating a CentOS 7.9 machine.
A simple "yum update" exists with this error:
# yum update
--> Running transaction check
---> Package kernel.x86_64 0:3.10.0-1160.36.2.el7 will be erased
--> Finished Dependency Resolution
ERROR: u
Dear list,
I have an issue updating a CentOS 7.9 machine.
A simple "yum update" exists with this error:
# yum update
--> Running transaction check
---> Package kernel.x86_64 0:3.10.0-1160.36.2.el7 will be erased
--> Finished Dependency Resolution
ERROR: update failed. Check the log file for deta
Strahil Nikolov and I took this conversation off-line for a few days. The
thread of our discussion is below. Net result: No solution is yet found.
Strahil had some very good ideas, but they did not pan out in this case.
For archiving - and in hope that someone may have some other ideas! - I
Am 10.12.20 um 16:51 schrieb Pete Biggs:
when someone has installed a CentOS 7.1 in the past,
and did 'yum update' regularily, his/she got a CentOS 7.8 now without
any reinstallation procedure or other complications;
when the same wanted to update to CentOS 8 he/she had to do a new install;
> when someone has installed a CentOS 7.1 in the past,
>
> and did 'yum update' regularily, his/she got a CentOS 7.8 now without
> any reinstallation procedure or other complications;
>
> when the same wanted to update to CentOS 8 he/she had to do a new install;
>
> what happens to CentOS Str
Hello,
when someone has installed a CentOS 7.1 in the past,
and did 'yum update' regularily, his/she got a CentOS 7.8 now without
any reinstallation procedure or other complications;
when the same wanted to update to CentOS 8 he/she had to do a new install;
what happens to CentOS Stream?
wh
We resolved the issue by modifying the CentOS-Base.repo by adding the
appropriate URL's to the various sections,
for example: baseurl=http://vault.centos.org/6.10/os/$basearch/
Thank you,
Paul
On Tue, Dec 8, 2020 at 1:25 PM Paul Storck
wrote:
> Thank you for the response. I added (copied, edite
On 12/8/20 3:25 PM, Paul Storck via CentOS wrote:
> Thank you for the response. I added (copied, edited, pasted from the C6.9
> section) the following to the /etc/yum.repos.d/CentOS-Vault.repo file but
> I still get the same error message.
> I'm thinking the paths are incorrect in my file because
> Date: Tuesday, December 08, 2020 13:25:42 -0800
> From: Paul Storck via CentOS
>
>> On Tue, Dec 8, 2020 at 8:45 AM Subscriber
>> wrote:
>>
>> > - On Dec 8, 2020, at 6:31 PM, Paul Storck wrote:
>>
>> > Hello, is it possible to install the final updates for CentOS 6?
>> > I ran a yum up
Thank you for the response. I added (copied, edited, pasted from the C6.9
section) the following to the /etc/yum.repos.d/CentOS-Vault.repo file but
I still get the same error message.
I'm thinking the paths are incorrect in my file because when I try to go to
directly to the URL (http://vault.cent
On 12/8/20 10:31 AM, Paul Storck via CentOS wrote:
> Hello, is it possible to install the final updates for CentOS 6?
> I ran a yum update and I received this message "Error: Cannot find a valid
> baseurl for repo: base"
> I assume it's due to the EOL of CentOS 6?
>
Yes,
and archived version of
- On Dec 8, 2020, at 6:31 PM, Paul Storck via CentOS centos@centos.org
wrote:
> Hello, is it possible to install the final updates for CentOS 6?
> I ran a yum update and I received this message "Error: Cannot find a valid
> baseurl for repo: base"
> I assume it's due to the EOL of CentOS 6?
Hello, is it possible to install the final updates for CentOS 6?
I ran a yum update and I received this message "Error: Cannot find a valid
baseurl for repo: base"
I assume it's due to the EOL of CentOS 6?
Thank you,
Paul
___
CentOS mailing list
CentOS@
El 23/11/20 a las 16:44, Jerry Geis escribió:
I stumbled on this today.
https://www.hostwinds.com/guide/upgrading-from-centos-7-to-8/
I understand the best is always a re-install But are these steps the
next best thing to update from 7 to 8 ?
Thanks,
Jerry
On Mon, 2020-11-23 at 10:44 -0500, Jerry Geis wrote:
> I stumbled on this today.
> https://www.hostwinds.com/guide/upgrading-from-centos-7-to-8/
>
> I understand the best is always a re-install But are these steps
> the
> next best thing to update from 7 to 8 ?
>
Jerry,
There is a formally s
I stumbled on this today.
https://www.hostwinds.com/guide/upgrading-from-centos-7-to-8/
I understand the best is always a re-install But are these steps the
next best thing to update from 7 to 8 ?
Thanks,
Jerry
___
CentOS mailing list
CentOS@centos
the logs I have found where mentioned in the before message.
I found the surprising time idendity between yum update and the stop of
logging.
All other logfiles seem OK. e.g. wtmp.
rsyslog.conf is OK and same as in comparable servers.
The time gap (some 2 weeks) between loss of log content and
On Dec 1, 2019, at 6:05 PM, Helmut Drodofsky wrote:
> any help to have kernel logging again?
Have you done anything to resolve it? Restart rsyslog? Check the journal?
--
Jonathan Billings
___
CentOS mailing list
CentOS@centos.org
https://lists.ce
yum update was run
23.10.19 and then
05.11.19
to the beginning of the update 5.11.2019 kernel logging to
/var/log/messages was ok.
During the update at 5.11.2019 logging to /var/log/messages finished. I
persume, this bug began during processing updates. yum-log shows:
...
Nov 05 14:56:54
Hello Fabian,
On 26.09.19 09:46, Fabian Arrotin wrote:
On 25/09/2019 10:30, Ralf Aumüller wrote:
...
today I updated a CentOS 7.6 ppc64le machine to CentOS 7.7. After reboot
to the new kernel (4.18.0-80.7.2.el7.ppc64le) dkms could not build the
nvidia-module.
...>> Any comments?
thanks for Y
On 25/09/2019 10:30, Ralf Aumüller wrote:
> Hello,
>
> today I updated a CentOS 7.6 ppc64le machine to CentOS 7.7. After reboot
> to the new kernel (4.18.0-80.7.2.el7.ppc64le) dkms could not build the
> nvidia-module.
>
> Error-message from dkms:
>
> Compiler version check failed:
>
> The major
driver installer downloaded from the nvidia site.
Then a normal reboot and it worked.
cheers
mathy
From: CentOS on behalf of Ralf Aumüller
Sent: Wednesday, September 25, 2019 10:30
To: centos@centos.org
Subject: [CentOS] Update to Centos 7.7 / Arch
Hello,
today I updated a CentOS 7.6 ppc64le machine to CentOS 7.7. After reboot to the
new kernel (4.18.0-80.7.2.el7.ppc64le) dkms could not build the nvidia-module.
Error-message from dkms:
Compiler version check failed:
The major and minor number of the compiler used to
compile the kernel:
On 27/4/19 3:02 pm, Emmett Culley via CentOS wrote:
...
The upgrade succeeded after manually removing the older dupes.
Thanks for your suggestions.
Emmett
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Mi
On 4/22/19 10:45 AM, Ulf Volmer wrote:
On 22.04.19 18:12, Emmett Culley via CentOS wrote:
On 4/21/19 10:15 AM, Ulf Volmer wrote:
package-cleanup --dupes
will list the duplicate packages
package-cleanup --cleandupes
will remove the dupes. If I remember correctly, you have to add
--removenew
On 22.04.19 18:12, Emmett Culley via CentOS wrote:
> On 4/21/19 10:15 AM, Ulf Volmer wrote:
>> package-cleanup --dupes
>>
>> will list the duplicate packages
>>
>> package-cleanup --cleandupes
>>
>> will remove the dupes. If I remember correctly, you have to add
>> --removenewestdupes to the secon
On 4/21/19 10:15 AM, Ulf Volmer wrote:
On 21.04.19 16:14, Emmett Culley via CentOS wrote:
When I attempted to update a remote server via SSH last night the UPS on
my local workstations failed, causing the SSH session to get dropped in
the middle of the upgrade process. This morning I am not abl
On 21.04.19 16:14, Emmett Culley via CentOS wrote:
> When I attempted to update a remote server via SSH last night the UPS on
> my local workstations failed, causing the SSH session to get dropped in
> the middle of the upgrade process. This morning I am not able to
> complete the update. When it
When I attempted to update a remote server via SSH last night the UPS on my local workstations
failed, causing the SSH session to get dropped in the middle of the upgrade process. This morning
I am not able to complete the update. When it failed when I tried to run it again thins morning I
di
On Tue, Dec 04, 2018 at 08:59:22AM -0500, Jason Edgecombe wrote:
> In addition, there is a bugzilla report for this:
> https://bugzilla.redhat.com/show_bug.cgi?id=1644519
I think I'm going to just lie low for a while until the upgrade to
7.6 stabliizes a bit.
I have several machines, mostly perso
In addition, there is a bugzilla report for this:
https://bugzilla.redhat.com/show_bug.cgi?id=1644519
---
Jason Edgecombe | Linux Administrator
UNC Charlotte | The William States Lee College of Engineering
9201 University City
> Date: Monday, December 03, 2018 20:41:20 -0600
> From: Frank Cox
>
> I just tried updating this laptop to the shiny new Centos version
> and it appears that Mate doesn't like the new version of libgtop,
> as you can see here:
>
> Error: Package: marco-1.16.1-3.el7.x86_64 (@epel)
>
I just tried updating this laptop to the shiny new Centos version and it
appears that Mate doesn't like the new version of libgtop, as you can see here:
Error: Package: marco-1.16.1-3.el7.x86_64 (@epel)
Requires: libgtop-2.0.so.10()(64bit)
Removing: libgtop2-2.34.2-2.el7.x86
On 11/13/18 11:50 AM, Chris Johnson wrote:
I believe most of the images were originally built for Ubuntu.
Sounds like that you are trying to run some binaries that were built for
Ubuntu, and the Ubuntu version they used has a higher ABI version than
those in CentOS 7.
If these were software
On 11/13/2018 12:50 PM, Jonathan Billings wrote:
On Tue, Nov 13, 2018 at 12:10:22PM -0500, Chris Johnson wrote:
In a very recent update to CentOS 7 libstdc++ has been altered in a way that
has removed CXXABI_1.3.8 and GLIBCXX_3.4.20. I've noticed that this has
broken a number of executables lin
On Tue, Nov 13, 2018 at 12:10:22PM -0500, Chris Johnson wrote:
> In a very recent update to CentOS 7 libstdc++ has been altered in a way that
> has removed CXXABI_1.3.8 and GLIBCXX_3.4.20. I've noticed that this has
> broken a number of executables linked on other systems that used to run on
> Cen
Hi.
New to this list. If this has been answered/resolved already, please
point me to the solution.
In a very recent update to CentOS 7 libstdc++ has been altered in a way
that has removed CXXABI_1.3.8 and GLIBCXX_3.4.20. I've noticed that
this has broken a number of executables linked on o
> -Original Message-
> From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of Johnny Hughes
> Sent: Saturday, May 26, 2018 9:39 AM
> To: centos@centos.org
> Subject: Re: [CentOS] Update announcement request - correction...
>
> >> plus-3.10.0-862.2.3.el
On 05/25/2018 11:32 AM, Albert McCann wrote:
>> Related to that, a new kernel was released to the Centosplus repo, kernel-
>> plus-3.10.0-862.2.3.el7.centos.plus, but perf and python-perf were not
>> updated for the new kernel. Is this an oversight? perf doesn't complain
>> about mismatched version
On 05/25/2018 03:54 PM, Akemi Yagi wrote:
> On Fri, May 25, 2018 at 9:32 AM, Albert McCann
> wrote:
>>> Related to that, a new kernel was released to the Centosplus repo, kernel-
>>> plus-3.10.0-862.2.3.el7.centos.plus, but perf and python-perf were not
>>> updated for the new kernel. Is this an o
On Fri, May 25, 2018 at 9:32 AM, Albert McCann
wrote:
>> Related to that, a new kernel was released to the Centosplus repo, kernel-
>> plus-3.10.0-862.2.3.el7.centos.plus, but perf and python-perf were not
>> updated for the new kernel. Is this an oversight? perf doesn't complain
>> about mismatch
> Related to that, a new kernel was released to the Centosplus repo, kernel-
> plus-3.10.0-862.2.3.el7.centos.plus, but perf and python-perf were not
> updated for the new kernel. Is this an oversight? perf doesn't complain
> about mismatched versions though.
"kernel-plus-3.10.0-862.3.2.el7.centos
Hi,
Can the updated files added to the Centosplus repo be sent to the announcement
list please? I can't find them announced in any of the other lists.
Related to that, a new kernel was released to the Centosplus repo,
kernel-plus-3.10.0-862.2.3.el7.centos.plus, but perf and python-perf were not
On Fri, Feb 2, 2018 at 10:57 PM, Stephen Davies wrote:
> Where can I find a suitable module or even source code to build here?
>
> (Centos 7)
ELRepo used to provide the kmod-ath5k package. However, the module
does not compile under EL7.4 due to the change in the wireless stack.
If your device nee
Where can I find a suitable module or even source code to build here?
(Centos 7)
Cheers and thanks,
Stephen
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
On 01/12/2018 08:24 PM, johan.vermeul...@telenet.be wrote:
- Oorspronkelijk bericht -
Van: "Adrian Jenzer"
Aan: "CentOS mailing list"
Verzonden: Dinsdag 9 januari 2018 16:56:57
Onderwerp: Re: [CentOS] update to Centos7.4: Failed to open
\EFI\BOOT\gru
- Oorspronkelijk bericht -
Van: "Adrian Jenzer"
Aan: "CentOS mailing list"
Verzonden: Dinsdag 9 januari 2018 16:56:57
Onderwerp: Re: [CentOS] update to Centos7.4: Failed to open
\EFI\BOOT\grubx64.efi - Not Found
-Original Message-
From: CentOS
-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of
johan.vermeul...@telenet.be
Sent: Dienstag, 9. Januar 2018 16:34
To: CentOS mailing list
Subject: [CentOS] update to Centos7.4: Failed to open \EFI\BOOT\grubx64.efi -
Not Found
Hello All,
updating from
Hello All,
updating from Centos7.3 to Centos7.4 rendered one of our laptops unbootable.
EM:
Failed to open \EFI\BOOT\grubx64.efi - Not Found
Failed to load image \EFI\BOOT\grubx64.efi: Not Found
start_image() returned Not Found
How could this occur because of an update and how to fix this?
Thanks all for the thoughts. I have no issues with 7.4 - this was clearly
"freek" accident while updating, either internet connection closed on me or
something. I brought the unit back here, I tried a few of the suggestions -
wasn't really working for me. So I just re-installed 7.4 and all was fin
-Original Message-From: John Hodrien
Reply-to: CentOS mailing list
To: CentOS mailing list
Subject: Re: [CentOS] update to 7.4
Date: Wed, 20 Sep 2017 15:59:25 +0100 (BST)
On Wed, 20 Sep 2017, Gregory P. Ennis wrote:
> This happened to me on one of the units during a 7.4 upgrade,
Thanks all for the thoughts. I have no issues with 7.4 - this was clearly
"freek" accident while updating, either internet connection closed on me or
something. I brought the unit back here, I tried a few of the suggestions -
wasn't really working for me. So I just re-installed 7.4 and all was fine
On Wed, 20 Sep 2017, Gregory P. Ennis wrote:
This happened to me on one of the units during a 7.4 upgrade, and the only
way for the system to work for me was to use the previous os.
I tried to use the yum remove kernal 7.4 , but yum tried to remove all of
the kernels instead of just that last o
On 9/19/2017 9:51 AM, Jerry Geis wrote:
> I was doing an update to 7.4 and somewhere in middle the machine died.
>
> If I drop back to a previous kernel the machine is alive. So how do I say
> "forget the previous yum update" and start all over and do it again.
>
> Booting into the new kernel I g
On Sep 19, 2017, at 12:51 PM, Jerry Geis wrote:
> If I drop back to a previous kernel the machine is alive. So how do I say
> "forget the previous yum update" and start all over and do it again.
Since you are mid-transaction, you should at least try:
yum-complete-transaction
This is the safest
You'll want to look into 'yum history' with the 'info' and 'undo'
subcommands. Not sure how well it works for larger updates but I've had
success on broken packages.
On Tue, Sep 19, 2017 at 11:51 AM, Jerry Geis wrote:
> I was doing an update to 7.4 and somewhere in middle the machine died.
>
> I
On 9/19/2017 9:51 AM, Jerry Geis wrote:
I was doing an update to 7.4 and somewhere in middle the machine died.
If I drop back to a previous kernel the machine is alive. So how do I say
"forget the previous yum update" and start all over and do it again.
Booting into the new kernel I get a kerne
I was doing an update to 7.4 and somewhere in middle the machine died.
If I drop back to a previous kernel the machine is alive. So how do I say
"forget the previous yum update" and start all over and do it again.
Booting into the new kernel I get a kernel fault. So going back one level
on teh bo
On 09/18/2017 11:32 AM, Fabian Arrotin wrote:
> On 18/09/17 15:18, Armin Kunaschik wrote:
>> Hello,
>>
>> I'm having problems updating from 7.3 to 7.4 on my ppc64 (IBM Power7
>> p770) installation.
>> yum update stops with
>> Error: Multilib version problems found.
>> [..]
>> Protected multilib ve
On 18/09/17 15:18, Armin Kunaschik wrote:
> Hello,
>
> I'm having problems updating from 7.3 to 7.4 on my ppc64 (IBM Power7
> p770) installation.
> yum update stops with
> Error: Multilib version problems found.
> [..]
> Protected multilib versions: systemd-libs-219-42.el7.ppc !=
> systemd-libs-2
On 09/18/2017 10:30 AM, Johnny Hughes wrote:
> yum currently has issues with obsoletes .. especially when something
> like a noarch file gets obsoleted by an $arch type rpm and there are 2
> (multi) arches available to replace it. It pulls in BOTH, not just the
> one arch you have installed .. and
yum currently has issues with obsoletes .. especially when something
like a noarch file gets obsoleted by an $arch type rpm and there are 2
(multi) arches available to replace it. It pulls in BOTH, not just the
one arch you have installed .. and that then pulls in deps for the 2nd
arch that you do
Yep. This worked. Thanks!
Why yum can't figure this out itself?
On Mon, Sep 18, 2017 at 3:29 PM, Johnny Hughes wrote:
> On 09/18/2017 08:18 AM, Armin Kunaschik wrote:
>> Hello,
>>
>> I'm having problems updating from 7.3 to 7.4 on my ppc64 (IBM Power7
>> p770) installation.
>> yum update stops wi
On 09/18/2017 08:18 AM, Armin Kunaschik wrote:
> Hello,
>
> I'm having problems updating from 7.3 to 7.4 on my ppc64 (IBM Power7
> p770) installation.
> yum update stops with
> Error: Multilib version problems found.
> [..]
> Protected multilib versions: systemd-libs-219-42.el7.ppc !=
> systemd-l
Hello,
I'm having problems updating from 7.3 to 7.4 on my ppc64 (IBM Power7
p770) installation.
yum update stops with
Error: Multilib version problems found.
[..]
Protected multilib versions: systemd-libs-219-42.el7.ppc !=
systemd-libs-219-42.el7_4.1.ppc64
When I scroll back through the transact
Le 14/09/2017 à 03:02, Johnny Hughes a écrit :
> I have a test machine with an NVIDIA card .. let me see if the
> proprietary NVIDIA driver works on this for 7.4.
I have an NVidia GeForce GT218 card on my workstation, with a twin
monitor. Updated everything to CentOS 1708, and the kmod-nvidia-340x
On Wed, Sep 13, 2017 at 8:21 PM, Lamar Owen wrote:
> On 09/13/2017 04:40 PM, Jerry Geis wrote:
>
>> I am running the propriatry NVIDIA driver 384.69 for GT 720 support.
>>
> The ELrepo driver works very well for me with CentOS 7.4.1708 on a Dell
> Precision M6700. Here's what I have:
> ++
>
Hi Johnny
Thanks for the commands I think something was messed up as the yum
group install "Gnome Desktop" seems to do the trick.
I had all the other items setup, for disable nouveu and all that.for the
binary NVIDIA.
Anyway - my desktop is back up and running, thanks.
Jerry
> On 4 Aug 2017, at 16:41, Pierre Riteau wrote:
>
>> On 13 Jul 2017, at 11:07, Pierre Riteau wrote:
>>
>>> On 13 Jul 2017, at 01:55, Johnny Hughes wrote:
>>>
>>> On 07/12/2017 02:02 PM, Pierre Riteau wrote:
Hello,
The version of cloud-init packaged in CentOS 7 Extras is rather
On 09/13/2017 04:40 PM, Jerry Geis wrote:
I am running the propriatry NVIDIA driver 384.69 for GT 720 support.
The ELrepo driver works very well for me with CentOS 7.4.1708 on a Dell
Precision M6700. Here's what I have:
++
[lowen@localhost ~]$ nvidia-detect -v
Probing for supported NVIDIA
On 09/13/2017 08:46 PM, Johnny Hughes wrote:
> On 09/13/2017 04:12 PM, Jerry Geis wrote:
>> if I do "init 3" to exit graphics. then run startx - it does not start -
>> but the only message (no errors) is
>> Server terminated successfully.
>>
>
> In order to use the proprietary NVIDIA driver, you w
On 09/13/2017 04:12 PM, Jerry Geis wrote:
> if I do "init 3" to exit graphics. then run startx - it does not start -
> but the only message (no errors) is
> Server terminated successfully.
>
In order to use the proprietary NVIDIA driver, you will need to disable
the nouveau driver in the initrd.
On 09/13/2017 08:02 PM, Johnny Hughes wrote:
> On 09/13/2017 07:59 PM, Johnny Hughes wrote:
>> On 09/13/2017 04:12 PM, Jerry Geis wrote:
>>> if I do "init 3" to exit graphics. then run startx - it does not start -
>>> but the only message (no errors) is
>>> Server terminated successfully.
>>>
>>
>>
On 09/13/2017 07:59 PM, Johnny Hughes wrote:
> On 09/13/2017 04:12 PM, Jerry Geis wrote:
>> if I do "init 3" to exit graphics. then run startx - it does not start -
>> but the only message (no errors) is
>> Server terminated successfully.
>>
>
> You can check the /var/log/Xorg.0.log to get some cl
On 09/13/2017 04:12 PM, Jerry Geis wrote:
> if I do "init 3" to exit graphics. then run startx - it does not start -
> but the only message (no errors) is
> Server terminated successfully.
>
You can check the /var/log/Xorg.0.log to get some clues
signature.asc
Description: OpenPGP digital sign
On Wed, Sep 13, 2017 at 2:00 PM, Johnny Hughes wrote:
> On 09/13/2017 03:40 PM, Jerry Geis wrote:
> > I am running the propriatry NVIDIA driver 384.69 for GT 720 support.
>
> If you installed it directly from nvidia, you would need to boot to
> runlevel 3 and rerun the NVIDIA*.run script to build
On Wed, September 13, 2017 4:10 pm, Jerry Geis wrote:
> I have recompiled the NVIDIA binary driver.
That is like an oxymoron ;-) You can not recompile NVIDIA binary driver,
you don't have source code for it. All you have is a binary compiled at
NVIDIA, and small piece of code for interface betwee
if I do "init 3" to exit graphics. then run startx - it does not start -
but the only message (no errors) is
Server terminated successfully.
Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
I have recompiled the NVIDIA binary driver.
So graphics comes up - just when I click on the user - it restarts.
Jerry
On Wed, Sep 13, 2017 at 4:40 PM, Jerry Geis wrote:
> I am running the propriatry NVIDIA driver 384.69 for GT 720 support.
>
> Jerry
>
>
_
On 09/13/2017 03:40 PM, Jerry Geis wrote:
> I am running the propriatry NVIDIA driver 384.69 for GT 720 support.
Depending on how you installed the driver, it may need to be recompiled
for the new kernel.
If you installed it directly from nvidia, you would need to boot to
runlevel 3 and rerun the
I am running the propriatry NVIDIA driver 384.69 for GT 720 support.
Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
I continued to play to get this running. I am close.
When X comes up and I click on the user to login - It appears X restarts.
I do see a message that gdm was killed by SIGTRAP in the logs.
I may just have something not installed at this point. I had to "yum
remove" a couple things to allow the up
On 09/13/2017 10:08 AM, Johnny Hughes wrote:
> On 09/13/2017 09:14 AM, Jerry Geis wrote:
>> I am attempting to update to 7.4 using the DVD
>>
>> I get these errors(truncated list)
>> Error: Package: libgpod-0.8.3-14.el7.x86_64 (@epel)
>>Requires: libusbmuxd.so.2()(64bit)
>>R
On 09/13/2017 09:14 AM, Jerry Geis wrote:
> I am attempting to update to 7.4 using the DVD
>
> I get these errors(truncated list)
> Error: Package: libgpod-0.8.3-14.el7.x86_64 (@epel)
>Requires: libusbmuxd.so.2()(64bit)
>Removing: usbmuxd-1.0.8-11.el7.x86_64 (@anaconda)
>
I am attempting to update to 7.4 using the DVD
I get these errors(truncated list)
Error: Package: libgpod-0.8.3-14.el7.x86_64 (@epel)
Requires: libusbmuxd.so.2()(64bit)
Removing: usbmuxd-1.0.8-11.el7.x86_64 (@anaconda)
libusbmuxd.so.2()(64bit)
Obsole
> On 13 Jul 2017, at 11:07, Pierre Riteau wrote:
>
>> On 13 Jul 2017, at 01:55, Johnny Hughes wrote:
>>
>> On 07/12/2017 02:02 PM, Pierre Riteau wrote:
>>> Hello,
>>>
>>> The version of cloud-init packaged in CentOS 7 Extras is rather old (0.7.5,
>>> which was released in 2014). It is missing
On 07/13/2017 02:31 PM, Leonard den Ottolander wrote:
> Hi,
>
> On Wed, 2017-07-05 at 13:25 -0500, Johnny Hughes wrote:
>> We are changing the URLs for new CentOS updates from the current link
>> types (example):
>>
>> https://rhn.redhat.com/errata/RHSA-2017-1679.html
>>
>> to these type of links
Hi,
On Wed, 2017-07-05 at 13:25 -0500, Johnny Hughes wrote:
> We are changing the URLs for new CentOS updates from the current link
> types (example):
>
> https://rhn.redhat.com/errata/RHSA-2017-1679.html
>
> to these type of links instead (example):
>
> https://access.redhat.com/errata/RHSA-20
> On 13 Jul 2017, at 01:55, Johnny Hughes wrote:
>
> On 07/12/2017 02:02 PM, Pierre Riteau wrote:
>> Hello,
>>
>> The version of cloud-init packaged in CentOS 7 Extras is rather old (0.7.5,
>> which was released in 2014). It is missing some functionality that we would
>> like to use, as well a
On 07/12/2017 02:02 PM, Pierre Riteau wrote:
> Hello,
>
> The version of cloud-init packaged in CentOS 7 Extras is rather old (0.7.5,
> which was released in 2014). It is missing some functionality that we would
> like to use, as well as important bug fixes.
> Before I tackle rebuilding the pack
Hello,
The version of cloud-init packaged in CentOS 7 Extras is rather old (0.7.5,
which was released in 2014). It is missing some functionality that we would
like to use, as well as important bug fixes.
Before I tackle rebuilding the package myself, I would like to know if there is
a plan to u
I'm running 6.8 and now it all makes sense.
Thanks
On 07/09/16 09:17, Duncan Brown wrote:
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
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: at the moment clamav 0.99.2
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: at the moment clamav 0.99.2 is only EL7, EL6 ist at 0.99.1
https:/
1 - 100 of 422 matches
Mail list logo
