On 02/28/17 15:39, Frédéric Bron wrote:
>> So, you've said you are using the nVidia driver. How did you install it?
> dnf install kernel-devel kernel-headers gcc dkms acpid
> dnf install akmod-nvidia xorg-x11-drv-nvidia "kernel-devel-uname-r ==
> $(uname -r)"
Well, the nvidia modules should be in
On 02/28/17 15:40, Frédéric Bron wrote:
>>> modprobe nvidia?
>> modprobe: FATAL: Module nvidia not found in directory
>> /lib/modules/4.9.11-200.fc25.x86_64
> sorry, I was on the wrong computer. This is the right output:
>
> modprobe: ERROR: could not insert 'nvidia': Permission denied
OK
Tha
>> modprobe nvidia?
>
> modprobe: FATAL: Module nvidia not found in directory
> /lib/modules/4.9.11-200.fc25.x86_64
sorry, I was on the wrong computer. This is the right output:
modprobe: ERROR: could not insert 'nvidia': Permission denied
___
users mai
> So, you've said you are using the nVidia driver. How did you install it?
dnf install kernel-devel kernel-headers gcc dkms acpid
dnf install akmod-nvidia xorg-x11-drv-nvidia "kernel-devel-uname-r ==
$(uname -r)"
___
users mailing list -- users@lists.fe
> modprobe nvidia?
modprobe: FATAL: Module nvidia not found in directory
/lib/modules/4.9.11-200.fc25.x86_64
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
On 02/28/17 15:10, Frédéric Bron wrote:
>> If you do "ausearch -c 'modprobe' --raw" you would see something
>> *similar* to this
> ausearch -c 'modprobe' --raw
>
> outputs nothing.
>
OK
So, you've said you are using the nVidia driver. How did you install it?
And you've said "lsmod | gre
> If you do "ausearch -c 'modprobe' --raw" you would see something
> *similar* to this
ausearch -c 'modprobe' --raw
outputs nothing.
Frédéric
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.
On 02/28/17 14:12, Frédéric Bron wrote:
>> Updates to plasma 5.8.6-2 and 5.8.6-3 as well as kf5 16.12.2-1 has
>> cleared up the problem for most, if not all, who have run into it.
> How do I get those from -testing?
> When everything will be cleaned, how will I switch back to standard
> repositor
On 02/28/17 14:02, Frédéric Bron wrote:
>>> I am using the nvidia driver.
>> You also may have been bitten by an selinux bug. Check to see if the
>> nvidia module has been loaded...
>>
>> lsmod | grep nvidia
> lsmod | grep nvidia
> gives nothing...
> ___
On 02/28/17 14:06, Frédéric Bron wrote:
>> Are these the versions you have installed?
>> selinux-policy-devel-3.13.1-225.11.fc25.noarch
>> selinux-policy-targeted-3.13.1-225.11.fc25.noarch
>> selinux-policy-doc-3.13.1-225.11.fc25.noarch
>> selinux-policy-sandbox-3.13.1-225.11.fc25.noarch
>> selinux
> Updates to plasma 5.8.6-2 and 5.8.6-3 as well as kf5 16.12.2-1 has
> cleared up the problem for most, if not all, who have run into it.
How do I get those from -testing?
When everything will be cleaned, how will I switch back to standard repository?
Regards,
Frédéric
__
> Are these the versions you have installed?
> selinux-policy-devel-3.13.1-225.11.fc25.noarch
> selinux-policy-targeted-3.13.1-225.11.fc25.noarch
> selinux-policy-doc-3.13.1-225.11.fc25.noarch
> selinux-policy-sandbox-3.13.1-225.11.fc25.noarch
> selinux-policy-3.13.1-225.11.fc25.noarch
not exactly
>> I am using the nvidia driver.
> You also may have been bitten by an selinux bug. Check to see if the
> nvidia module has been loaded...
>
> lsmod | grep nvidia
lsmod | grep nvidia
gives nothing...
___
users mailing list -- users@lists.fedoraproject.o
On 02/28/17 13:52, Alex Gurenko wrote:
> I have similar issues, with all latest packages selinux still gives
> all kind of errors including error in building module, modprobe and
> switching to nvidia graphics with bumblebee.
> setenforce 0 allows to do all these things, but when I set it back,
>
I have similar issues, with all latest packages selinux still gives all
kind of errors including error in building module, modprobe and switching
to nvidia graphics with bumblebee.
setenforce 0 allows to do all these things, but when I set it back, it
unloads module...
*---*
*Yours truly, Alex*
On Mon, Feb 27, 2017 at 2:56 PM, Rick Stevens wrote:
> On 02/27/2017 11:35 AM, Jon LaBadie wrote:
>> On Mon, Feb 27, 2017 at 09:41:11AM -0800, Rick Stevens wrote:
>>> On 02/26/2017 12:34 PM, bruce wrote:
Hey Jon...
You are absolutely correct.. if the parent ssh terminates.. the remo
On 02/28/17 01:00, Frédéric Bron wrote:
> I am using the nvidia driver.
You also may have been bitten by an selinux bug. Check to see if the
nvidia module has been loaded...
lsmod | grep nvidia
If not...see https://bugzilla.redhat.com/show_bug.cgi?id=1426906 and get
the latest selinux policy p
On 02/28/17 01:00, Frédéric Bron wrote:
> I am using a fresh updated install with kernel 4.9.11.
> The system starts but comes to a black screen. I am only able to login
> in text mode with Ctrl+Alt+F2.
>
> I tried to start with older kernels since I started to have some
> issues with 4.9.9 but I h
On 02/27/2017 11:35 AM, Jon LaBadie wrote:
> On Mon, Feb 27, 2017 at 09:41:11AM -0800, Rick Stevens wrote:
>> On 02/26/2017 12:34 PM, bruce wrote:
>>> Hey Jon...
>>>
>>> You are absolutely correct.. if the parent ssh terminates.. the remote
> ...
>>
>> Jon, we try not to top-post here. Just a nudge
On Mon, Feb 27, 2017 at 09:41:11AM -0800, Rick Stevens wrote:
> On 02/26/2017 12:34 PM, bruce wrote:
> > Hey Jon...
> >
> > You are absolutely correct.. if the parent ssh terminates.. the remote
...
>
> Jon, we try not to top-post here. Just a nudge.
I didn't Rick, you attributed the above incor
On Mon, 27 Feb 2017 09:41:11 -0800
Rick Stevens wrote:
> If you are using ssh to spawn a remote screen session that runs a
> command in the background it should work just fine
Unless, of course, your ssh agent is being forwarded from way back
on the host system and you need the agent to be active
> Did you blacklist the nouveau drivers from the kernel argument?
I do not know how to do that.
Frédéric
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
>
>
>
> I am using the nvidia driver.
>
>
Did you blacklist the nouveau drivers from the kernel argument?
--
Kind Regards
Earl Ramirez
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject
On 02/27/2017 08:01 AM, Gary Stainburn wrote:
> On Friday 24 February 2017 18:51:54 Rick Stevens wrote:
>> The most common issue with this sort of thing is ARP and/or route
>> confusion. You have a machine with two interfaces on the same network.
>> Try doing this as root on zeppo (the machine with
On 02/26/2017 12:34 PM, bruce wrote:
> Hey Jon...
>
> You are absolutely correct.. if the parent ssh terminates.. the remote
> process would "die".. In my use case, the remote process being fired
> off is actually being run under a remote "Screen" session, so it had
> better survive the ssh termin
On Sun, Feb 26, 2017 at 11:13 PM, Ed Greshko wrote:
>
>>> Let me add that I am using Oracle VirtualBox (from
>>> http://www.virtualbox.org/):
>>>
>>> VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64
>> As am I
>>
>> The procedure I gave you will get you going as I did me.
>>
>> I'll report this
Hi,
I am using a fresh updated install with kernel 4.9.11.
The system starts but comes to a black screen. I am only able to login
in text mode with Ctrl+Alt+F2.
I tried to start with older kernels since I started to have some
issues with 4.9.9 but I have now only 4.9.9, 4.9.10 and 4.9.11 and all
On Friday 24 February 2017 18:51:54 Rick Stevens wrote:
> The most common issue with this sort of thing is ARP and/or route
> confusion. You have a machine with two interfaces on the same network.
> Try doing this as root on zeppo (the machine with two interfaces):
>
> echo "1" >/proc/sys/net
From: Greg Woods [mailto:wo...@ucar.edu]
Sent: zaterdag 25 februari 2017 20:45
To: Community support for Fedora users
Subject: Re: automatically restart ethernet ?
On Sat, Feb 25, 2017 at 11:39 AM, fred roller
mailto:fredrolle...@gmail.com>> wrote:
Look into "heartbeat".
"heartbeat" has been
29 matches
Mail list logo
