On Monday 11 December 2017 18:50:06 Akemi Yagi wrote:
> As far as I know, the contents on the CentOS wiki are for CentOS 7.3 (or
> earlier) and a patch is needed to use the driver under 7.4.
>
> You may want to go to the ELRepo article that is referenced on that page (
> http://elrepo.org/tiki/wl-
After getting nowhere with the mokutil command I decided to use the other
option and turn off secure boot in the BIOS settings.
I had been loathed to do this because every time I do anything in the BIOS it
stuffs the boot order and reverts to booting straight into Win8. Guess what,
as soon as
On Thu, Dec 14, 2017 at 5:39 AM, Gary Stainburn wrote:
> After getting nowhere with the mokutil command I decided to use the other
> option and turn off secure boot in the BIOS settings.
>
> I had been loathed to do this because every time I do anything in the BIOS
> it
> stuffs the boot order an
On Thu, Dec 14, 2017 at 6:59 AM, Akemi Yagi wrote:
> On Thu, Dec 14, 2017 at 5:39 AM, Gary Stainburn
> wrote:
>
>> After getting nowhere with the mokutil command I decided to use the other
>> option and turn off secure boot in the BIOS settings.
>>
>> I had been loathed to do this because every
On Thu, Dec 14, 2017 at 6:59 AM, Akemi Yagi wrote:
>
> Just wanted to add a note that you can use ELRepo's drivers with
> SecureBoot enabled if you so wish.
> Here's how:
>
> http://elrepo.org/tiki/SecureBootKey
>
Yet another comment. Sorry, the above note is a general one. The
self-built
Le 12/12/2017 à 21:25, Gordon Messmer a écrit :
> You may have had a custom context set on /var/log/spamassassin or a
> sub-path in the past, overwritten by a recent update. That's a normal
> occurrence if you set context using chcon rather than "semanage
> fcontext". The latter is persistent; th
Can you give more information on the unbound setup? We use unbound in
Fedora Infrastructure on RHEL-7 servers. I know there is an selinux
dance we have to do to start it properly without a special policy...
but I don't know exactly the details on why.
On 11 December 2017 at 03:56, C. L. Martinez
On Dec 13, 2017, at 5:15 PM, J Martin Rushton
wrote:
>
> # dd if=/dev/sdc of=/home/dd-copy-of-sdc
Better, use ddrescue:
https://www.gnu.org/software/ddrescue/
dd will do unfortunate things like quit early on I/O errors, even if later
blocks would read just fine. ddrescue assumes the inpu
On 14/12/17 18:57, Warren Young wrote:
> On Dec 13, 2017, at 5:15 PM, J Martin Rushton
> wrote:
>>
>> # dd if=/dev/sdc of=/home/dd-copy-of-sdc
>
> Better, use ddrescue:
>
>https://www.gnu.org/software/ddrescue/
>
> dd will do unfortunate things like quit early on I/O errors, even if later
I installed the elrepo kmod-nvidia and also the nvidia-detect and modules
(see below).
I had X working with the 3.10 from Centos - but video was freezing. SO I
thought I would try the elrepo kernel. I installed that and X does not come
up?
How do I re-make the nvidia module for 4.14.5 kernel? I
Find the akmod-nvidia package. Last I bothered with this some years ago, the
akmod package was required to ensure the nvidia module would be rebuilt every
time a new kernel was booted into.
Mark
On Thu, 2017-12-14 at 16:51 -0500, Jerry Geis wrote:
> I installed the elrepo kmod-nvidia and also the
That's what I get too -
01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce
405] (rev a2)
It works fine for me with mate with this:
kernel-3.10.0-693.5.2.el7.x86_64
kmod-nvidia-340xx-340.102-4.el7_4.elrepo.x86_64
I've had problems with gnome 3 and nvidia before, but haven't
If the data is important to you, don't mess around and contact a
reputable professional data recovery expert or company.
If losing your data is a viable option, try to do it yourself.
Otherwise seek professional help, with the data recovery effort of
course.
On Fri, Dec 15, 2017 at 4:31 AM, J Mar
So I removed the nvidia items and reinstalled.
In /var/log/messages I saw dracut commands for every kernel EXCEPT the
4.14.5 elrepo kernel.
So I did it manually and I get an error.
/usr/bin/dracut --add-drivers nvidia -f
/boot/initramfs-4.14.5-1.el7.elrepo.x86_64.img 4.14.5-1.el7.elrepo.x86_64
Fa
It seems as though 4.14.5 elrepo kernel does not generate any initramfs. It
seems nvidia needs to be apart of that.
Is that correct ?
If so how do I tell it to actually generate the initramfs
Jerry
___
CentOS mailing list
CentOS@centos.org
https://lists.
I'm deploying a CentOS 7 box as a gateway and I'm trying to figure out how
to set up traffic shaping. Historically I've used the Wondershaper script
but apparently it's not deprecated in favor of superior queue management. I
haven't yet found a packaged solution and I'm wondering what others do
I came across this on the Fedora devel list. I added
/etc/sysctl.d/51-bufferbloat.conf containing the suggested line and it
installs the new codel qdisc as desired. There's probably more knobs that
might be useful to tweak but this makes a good start. More reading on the
bufferbloat site sugges
W dniu 14.12.2017 o 23:06, Nizar Armansyah pisze:
> If the data is important to you, don't mess around and contact a
> reputable professional data recovery expert or company.
If the data is important to you, you will get it back from your backups,
won't you?
--
Over And Out
MoonWolf
On 15/12/17 00:21, Jerry Geis wrote:
So I removed the nvidia items and reinstalled.
In /var/log/messages I saw dracut commands for every kernel EXCEPT the
4.14.5 elrepo kernel.
So I did it manually and I get an error.
/usr/bin/dracut --add-drivers nvidia -f
/boot/initramfs-4.14.5-1.el7.elrepo.x
19 matches
Mail list logo
