11 p.m.
This is the same system that had nvidia problems during its fc22 > fc23
upgrade. That was reported here and solved on 30 June. Since then it
has been working well, but after installing the new packages today I get
black screens with kernels 4.7.3, 4.7.5 and 4.7.6
'dnf downgrade xorg-x11-drv-nvidia-304xx --allowerasing' apparently
completed but then akmods-shutdown errored. After re-upgrading,
akmods-shutdown completed, and the nvidia flash screen flashes, but then
all goes black again, for all installed kernels. I'm using tty2.
Xorg.0.log looks ok apart from 'ACPI: failed to connect to the ACPI
event daemon' and suggests looking at the ConnectToAcpid and
AcpidSocketPath options, which I have not yet done. I don't know if
this is likely to be the real problem.
John P
6:40 p.m.
No expert, and I don't run nvidia anymore, but I'll try to help.
On Tue, 11 Oct 2016 00:00:00 +0100
John Pilkington <J.Pilk(a)tesco.net> wrote:
This is the same system that had nvidia problems during its fc22
>
fc23 upgrade. That was reported here and solved on 30 June. Since
then it has been working well, but after installing the new packages
today I get black screens with kernels 4.7.3, 4.7.5 and 4.7.6
What new packages were installed?
'dnf downgrade xorg-x11-drv-nvidia-304xx --allowerasing'
apparently
completed but then akmods-shutdown errored. After re-upgrading,
akmods-shutdown completed, and the nvidia flash screen flashes, but
then all goes black again, for all installed kernels. I'm using tty2.
I'm not clear on what you are saying here. What does "nvidia flash
screen flashes" mean? And how are you using tty2? By default, Fedora
always uses tty1 during boot. Are you in multiuser, and running startx
to get to graphical?
Xorg.0.log looks ok apart from 'ACPI: failed to connect to the
ACPI
event daemon' and suggests looking at the ConnectToAcpid and
AcpidSocketPath options, which I have not yet done. I don't know if
this is likely to be the real problem.
Unlikely. ACPI is the power management daemon. It shouldn't prevent
the driver from working properly to access the monitors. You could
disable any screen savers you have enabled to be sure; if they are
taking effect immediately it might cause blank screens, even though the
driver is working.
9:40 p.m.
On 11/10/16 19:40, stan wrote:
No expert, and I don't run nvidia anymore, but I'll try to
help.
On Tue, 11 Oct 2016 00:00:00 +0100
John Pilkington <J.Pilk(a)tesco.net> wrote:
> This is the same system that had nvidia problems during its fc22 >
> fc23 upgrade. That was reported here and solved on 30 June. Since
> then it has been working well, but after installing the new packages
> today I get black screens with kernels 4.7.3, 4.7.5 and 4.7.6
What new packages were installed?
Thanks for coming back to me about this. Because I can't access the
usual desktop features I'm in unfamiliar ground. The system was updated
on 3 Oct and worked. The update on 10 Oct caused the problems from
which I have been trying to recover.
xorg-xll-drv-nvidia-304xx-304.131-3 was working; 304.132-1 did not. I
believe there was a kernel update too.
I have been through several cycles of 'dnf remove' and 'dnf install',
akmods-shutdown, akmods --force. I now have a mockuser defined. But
most recently the kmod builds were failing and the logs are
incomprehensible.
I have now removed all nvidia packages in the hope of getting a working
system with nouveau. There's a long thread now on fedora-users about
that, although it has wandered off course.
Currently (KDE) plasma login with nouveau appears normal for perhaps 10
seconds, then collapses to a featureless screen with a mouse cursor that
moves but seems to do nothing else. ctrl/alt/F2 brings up the tty2
screen as mentioned below, which, without an active window, is the only
way I know to access the file system; I haven't yet tried an emergency
boot.
startx from tty2 allows login but then collapses again. Doing it from
tty3-ish says 'Could not start ksmserver. Check your installation'
which prompts unfriendly feelings but does perhaps give some clue about
what has gone wrong. But maybe it's because too many screens are being
referenced. xrandr 'Can't open display'.
> 'dnf downgrade xorg-x11-drv-nvidia-304xx --allowerasing' apparently
> completed but then akmods-shutdown errored. After re-upgrading,
> akmods-shutdown completed, and the nvidia flash screen flashes, but
> then all goes black again, for all installed kernels. I'm using tty2.
I'm not clear on what you are saying here. What does "nvidia flash
screen flashes" mean?
the green nvidia logo appears briefly. I don't think it should do that
with nouveau. But there's a multi-screen factor here (VGA and HDMI
(TV)) and I saw it only on the HDMI.
And how are you using tty2? By default, Fedora
always uses tty1 during boot. Are you in multiuser, and running
startx
to get to graphical?
> Xorg.0.log looks ok apart from 'ACPI: failed to connect to the ACPI
> event daemon' and suggests looking at the ConnectToAcpid and
> AcpidSocketPath options, which I have not yet done. I don't know if
> this is likely to be the real problem.
Unlikely. ACPI is the power management daemon. It shouldn't prevent
the driver from working properly to access the monitors. You could
disable any screen savers you have enabled to be sure; if they are
taking effect immediately it might cause blank screens, even though the
driver is working.
Thanks,
John
1:40 a.m.
On Tue, 11 Oct 2016 22:40:28 +0100
John Pilkington <J.Pilk(a)tesco.net> wrote:
Thanks for coming back to me about this. Because I can't access
the
usual desktop features I'm in unfamiliar ground. The system was
updated on 3 Oct and worked. The update on 10 Oct caused the
problems from which I have been trying to recover.
xorg-xll-drv-nvidia-304xx-304.131-3 was working; 304.132-1 did not.
I believe there was a kernel update too.
From the other email (from Nicolas), it sounds like there might be a
problem with the nvidia driver.
I have been through several cycles of 'dnf remove' and
'dnf install',
akmods-shutdown, akmods --force. I now have a mockuser defined. But
most recently the kmod builds were failing and the logs are
incomprehensible.
If you get into multiuser (old runlevel 3) as described below, you
should be able to log in as root and view /var/log/dnf*.log to see
exactly which updates occurred, and any messages that dnf issued about
them.
I have now removed all nvidia packages in the hope of getting a
working system with nouveau. There's a long thread now on
fedora-users about that, although it has wandered off course.
I think getting nouveau working is a good idea. It's been a while, but
I remember that there were things hiding in unlikely places that had
to be removed on this switch. Try searching online to find recent
instructions for the best way to do this.
Currently (KDE) plasma login with nouveau appears normal for perhaps
10 seconds, then collapses to a featureless screen with a mouse
cursor that moves but seems to do nothing else. ctrl/alt/F2 brings
up the tty2 screen as mentioned below, which, without an active
window, is the only way I know to access the file system; I haven't
yet tried an emergency boot.
I'm not sure what boot process you are using, but can you edit the menu
during boot to boot to multiuser? If you have access to the system,
edit /boot/grub2/grub.cfg and make sure that you have set_timeout=10 or
some other number that gives you a chance to interact. Also check that
the linux16 line has no quiet on it. Be sure that nouveau isn't
blacklisted on that line as well. And put a 3 on the end of the
linux16 line, so you come up in multiuser instead of graphical. That
will give you a working system to look at the graphical setup. Or, the
10 second pause will give you a chance to put an e on the boot line,
hit enter, and use the arrow keys to go to that line, and add the 3
temporarily.
startx from tty2 allows login but then collapses again. Doing it
from tty3-ish says 'Could not start ksmserver. Check your
installation' which prompts unfriendly feelings but does perhaps give
some clue about what has gone wrong. But maybe it's because too many
screens are being referenced. xrandr 'Can't open display'.
Unless you are in X, xrandr isn't going to work, and it sounds like you
aren't able to bring up X.
the green nvidia logo appears briefly. I don't think it should
do
that with nouveau. But there's a multi-screen factor here (VGA and
HDMI (TV)) and I saw it only on the HDMI.
I agree that you shouldn't see the nvidia logo flash with nouveau.
Is it easy to move to a single display? That will remove a variable
from consideration.
Nasty problem.
8:21 p.m.
2016-10-11 1:00 GMT+02:00 John Pilkington <J.Pilk(a)tesco.net>:
This is the same system that had nvidia problems during its fc22 >
fc23
upgrade. That was reported here and solved on 30 June. Since then it has
been working well, but after installing the new packages today I get black
screens with kernels 4.7.3, 4.7.5 and 4.7.6
'dnf downgrade xorg-x11-drv-nvidia-304xx --allowerasing' apparently
completed but then akmods-shutdown errored. After re-upgrading,
akmods-shutdown completed, and the nvidia flash screen flashes, but then all
goes black again, for all installed kernels. I'm using tty2.
We have seen such error and have moved the update back into
updates-testing for now.
Best is to debug using ssh remotly we'd like to have a full
nvidia-bug-report.sh to send to nvidia support forum
Hopefully there will be a new updated package from nvidia, we will
need testers at that time..
Thx for your report.
--
-
Nicolas (kwizart)
11:05 p.m.
On 11/10/16 21:21, Nicolas Chauvet wrote:
2016-10-11 1:00 GMT+02:00 John Pilkington <J.Pilk(a)tesco.net>:
> This is the same system that had nvidia problems during its fc22 > fc23
> upgrade. That was reported here and solved on 30 June. Since then it has
> been working well, but after installing the new packages today I get black
> screens with kernels 4.7.3, 4.7.5 and 4.7.6
>
> 'dnf downgrade xorg-x11-drv-nvidia-304xx --allowerasing' apparently
> completed but then akmods-shutdown errored. After re-upgrading,
> akmods-shutdown completed, and the nvidia flash screen flashes, but then all
> goes black again, for all installed kernels. I'm using tty2.
We have seen such error and have moved the update back into
updates-testing for now.
Best is to debug using ssh remotly we'd like to have a full
nvidia-bug-report.sh to send to nvidia support forum
Hopefully there will be a new updated package from nvidia, we will
need testers at that time..
Thx for your report.
I have been trying to get nouveau working, so far without success. But
I've also looked at the builds from scrpms, in which dnf reports
conflicts between the libvdpau_nvidia.so and .so.1 files from the 304
and 340 lib packages, which are both required. ISTR something similar
in atrpms long ago.
10:32 a.m.
On 12/10/16 00:05, John Pilkington wrote:
On 11/10/16 21:21, Nicolas Chauvet wrote:
> 2016-10-11 1:00 GMT+02:00 John Pilkington <J.Pilk(a)tesco.net>:
>> This is the same system that had nvidia problems during its fc22 > fc23
>> upgrade. That was reported here and solved on 30 June. Since then
>> it has
>> been working well, but after installing the new packages today I get
>> black
>> screens with kernels 4.7.3, 4.7.5 and 4.7.6
>>
>> 'dnf downgrade xorg-x11-drv-nvidia-304xx --allowerasing' apparently
>> completed but then akmods-shutdown errored. After re-upgrading,
>> akmods-shutdown completed, and the nvidia flash screen flashes, but
>> then all
>> goes black again, for all installed kernels. I'm using tty2.
>
> We have seen such error and have moved the update back into
> updates-testing for now.
> Best is to debug using ssh remotly we'd like to have a full
> nvidia-bug-report.sh to send to nvidia support forum
>
> Hopefully there will be a new updated package from nvidia, we will
> need testers at that time..
>
> Thx for your report.
>
>
>
I have been trying to get nouveau working, so far without success. But
I've also looked at the builds from scrpms, in which dnf reports
conflicts between the libvdpau_nvidia.so and .so.1 files from the 304
and 340 lib packages, which are both required. ISTR something similar
in atrpms long ago.
I have just posted to the kde fedora list: dmesg shows plasmashell
segfault in nouveau_dri.so
11:32 a.m.
On 12/10/16 11:32, John Pilkington wrote:
On 12/10/16 00:05, John Pilkington wrote:
> On 11/10/16 21:21, Nicolas Chauvet wrote:
>> 2016-10-11 1:00 GMT+02:00 John Pilkington <J.Pilk(a)tesco.net>:
>>> This is the same system that had nvidia problems during its fc22 > fc23
>>> upgrade. That was reported here and solved on 30 June. Since then
>>> it has
>>> been working well, but after installing the new packages today I get
>>> black
>>> screens with kernels 4.7.3, 4.7.5 and 4.7.6
>>>
>>> 'dnf downgrade xorg-x11-drv-nvidia-304xx --allowerasing' apparently
>>> completed but then akmods-shutdown errored. After re-upgrading,
>>> akmods-shutdown completed, and the nvidia flash screen flashes, but
>>> then all
>>> goes black again, for all installed kernels. I'm using tty2.
>>
>> We have seen such error and have moved the update back into
>> updates-testing for now.
>> Best is to debug using ssh remotly we'd like to have a full
>> nvidia-bug-report.sh to send to nvidia support forum
>>
>> Hopefully there will be a new updated package from nvidia, we will
>> need testers at that time..
>>
>> Thx for your report.
>>
>>
>>
> I have been trying to get nouveau working, so far without success. But
> I've also looked at the builds from scrpms, in which dnf reports
> conflicts between the libvdpau_nvidia.so and .so.1 files from the 304
> and 340 lib packages, which are both required. ISTR something similar
> in atrpms long ago.
>
I have just posted to the kde fedora list: dmesg shows plasmashell
segfault in nouveau_dri.so
I have a working fc23/kde/plasma desktop once more.
xorg-x11-drv-nvidia-304xx still doesn't build the kmod, even with
'akmods --force', and I had no luck with both that and nouveau removed.
But after ensuring that 'rpm -qa | grep nvidia' returned nothing, 'dnf
install xorg-x11-drv-nouveau' did the trick. I'll try living without
hardware acceleration for the time being...
John P
John P
2750
days inactive
2753
days old
rpmfusion-users@lists.rpmfusion.org
7 comments
3 participants
participants (3)
-
John Pilkington -
Nicolas Chauvet -
stan