Re: cifs problem? was Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
On 10/1/23 13:05, Richard Kimberly Heck wrote: On 1/9/23 20:10, Stephen Morris wrote: I'm not sure if it is significant, but I am using gdm as my display manager even though I am booting into KDE. This is a (very nasty) kernel bug. It's been discussed quite a bit on this list, so you can have a look at the archives. It seems to have been fixed in 6.0.17, out now, or you can roll back to 6.0.15. I had already tried it on 6.0.17, and yes it is rectified. What is not rectified is 6.0.18 does not resolve the issue found in 6.0.17 (it may be in earlier kernels as well but I haven't tested those) of the system shutdown being hung for a minute and a half by the cifs unmount process if the device disappears underneath the running system. regards, Steve Riki ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: cifs problem? was Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
kernel-6.0.18-200.fc36 and kernel-6.0.18-399.fc37 were pushed to stable 6 hours ago. I installed for fc36 last night from the updates page. No problem in booting and none have been seen overnight. John P ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: cifs problem? was Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
On 10/1/23 11:29, Stephen Morris wrote:
On 10/1/23 11:20, Stephen Morris wrote:
On 9/1/23 21:26, John Pilkington wrote:
Maybe this is
https://bugzilla.kernel.org/show_bug.cgi?id=216895, referred to
in this current thread:
Re: Fedora 37 hangs after graphical login
I have two cifs mounting lines in /etc/fstab; only one has the
hardware connected.
I have cifs... vers=3.0,
//192.168.1.XX/Public /mnt/nas1a cifs
credentials=,iocharset=utf8,gid=1000,uid=1000,vers=3.0,file_mode=0777,dir_mode=0777
0 0
Here is a 'journalctl' output from, first, 6.0.16 (which hung) and
then 6.0.15, which completed. Maybe it will help. Or perhaps just
wait for 6.0.18...
nas1a is on the network, nas2a is not. The main difference here
appears to be that with 6.0.16 sddm is not being called.
{{{
[john@HPFed ~]$ sudo journalctl --since 2023-01-07 | grep -A 20 nas2a
Jan 07 10:04:44 HPFed systemd[1]: Mounting mnt-nas2a.mount -
/mnt/nas2a...
Jan 07 10:04:44 HPFed systemd[1]: Starting rpc-statd-notify.service
- Notify NFS peers of a restart...
Jan 07 10:04:44 HPFed systemd[1]: iscsi.service: Unit cannot be
reloaded because it is inactive.
Jan 07 10:04:45 HPFed sm-notify[1304]: Version 2.6.2 starting
Jan 07 10:04:45 HPFed systemd[1]: Started rpc-statd-notify.service -
Notify NFS peers of a restart.
Jan 07 10:04:45 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel
msg='unit=rpc-statd-notify comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Jan 07 10:04:45 HPFed kernel: FS-Cache: Loaded
Jan 07 10:04:45 HPFed kernel: Key type dns_resolver registered
Jan 07 10:04:46 HPFed kernel: Key type cifs.spnego registered
Jan 07 10:04:46 HPFed kernel: Key type cifs.idmap registered
Jan 07 10:04:46 HPFed kernel: CIFS: Attempting to mount
\\192.168.1.209\Public
Jan 07 10:04:51 HPFed chronyd[1041]: Selected source 83.151.207.133
(2.fedora.pool.ntp.org)
Jan 07 10:04:51 HPFed chronyd[1041]: System clock TAI offset set to
37 seconds
Jan 07 10:04:52 HPFed mount[1305]: mount error(113): could not
connect to 192.168.1.209Unable to find suitable address.
Jan 07 10:04:52 HPFed kernel: CIFS: VFS: Error connecting to socket.
Aborting operation.
Jan 07 10:04:52 HPFed kernel: CIFS: VFS: cifs_mount failed w/return
code = -113
Jan 07 10:04:52 HPFed kernel: CIFS: Attempting to mount
\\192.168.1.67\Public
Jan 07 10:04:52 HPFed systemd[1]: mnt-nas2a.mount: Mount process
exited, code=exited, status=32/n/a
Jan 07 10:04:52 HPFed systemd[1]: mnt-nas2a.mount: Failed with
result 'exit-code'.
Jan 07 10:04:52 HPFed systemd[1]: Failed to mount mnt-nas2a.mount -
/mnt/nas2a.
Jan 07 10:04:52 HPFed systemd[1]: Dependency failed for
remote-fs.target - Remote File Systems.
Jan 07 10:04:52 HPFed systemd[1]: remote-fs.target: Job
remote-fs.target/start failed with result 'dependency'.
Jan 07 10:04:52 HPFed systemd[1]: Starting
systemd-user-sessions.service - Permit User Sessions...
Jan 07 10:04:52 HPFed systemd[1]: Finished
systemd-user-sessions.service - Permit User Sessions.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel
msg='unit=systemd-user-sessions comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=atd
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:52 HPFed systemd[1]: Started atd.service - Deferred
execution scheduler.
Jan 07 10:04:52 HPFed systemd[1]: Started crond.service - Command
Scheduler.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=crond
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:52 HPFed systemd[1]: Starting
plymouth-quit-wait.service - Hold until boot process finishes up...
Jan 07 10:04:52 HPFed systemd[1]: Starting plymouth-quit.service -
Terminate Plymouth Boot Screen...
Jan 07 10:04:52 HPFed systemd[1]: Mounted mnt-nas1a.mount - /mnt/nas1a.
Jan 07 10:04:52 HPFed systemd[1]: Received SIGRTMIN+21 from PID 346
(plymouthd).
Jan 07 10:04:52 HPFed systemd[1]: Received SIGRTMIN+21 from PID 346
(plymouthd).
Jan 07 10:04:52 HPFed systemd[1]: Finished
plymouth-quit-wait.service - Hold until boot process finishes up.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel
msg='unit=plymouth-quit-wait comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
res=success'
Jan 07 10:04:52 HPFed systemd[1]: Finished plymouth-quit.service -
Terminate Plymouth Boot Screen.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymouth-quit
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:52
Re: cifs problem? was Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
On 10/1/23 11:20, Stephen Morris wrote:
On 9/1/23 21:26, John Pilkington wrote:
Maybe this is https://bugzilla.kernel.org/show_bug.cgi?id=216895,
referred to in this current thread:
Re: Fedora 37 hangs after graphical login
I have two cifs mounting lines in /etc/fstab; only one has the
hardware connected.
I have cifs... vers=3.0,
//192.168.1.XX/Public /mnt/nas1a cifs
credentials=,iocharset=utf8,gid=1000,uid=1000,vers=3.0,file_mode=0777,dir_mode=0777
0 0
Here is a 'journalctl' output from, first, 6.0.16 (which hung) and
then 6.0.15, which completed. Maybe it will help. Or perhaps just
wait for 6.0.18...
nas1a is on the network, nas2a is not. The main difference here
appears to be that with 6.0.16 sddm is not being called.
{{{
[john@HPFed ~]$ sudo journalctl --since 2023-01-07 | grep -A 20 nas2a
Jan 07 10:04:44 HPFed systemd[1]: Mounting mnt-nas2a.mount -
/mnt/nas2a...
Jan 07 10:04:44 HPFed systemd[1]: Starting rpc-statd-notify.service -
Notify NFS peers of a restart...
Jan 07 10:04:44 HPFed systemd[1]: iscsi.service: Unit cannot be
reloaded because it is inactive.
Jan 07 10:04:45 HPFed sm-notify[1304]: Version 2.6.2 starting
Jan 07 10:04:45 HPFed systemd[1]: Started rpc-statd-notify.service -
Notify NFS peers of a restart.
Jan 07 10:04:45 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=rpc-statd-notify
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:45 HPFed kernel: FS-Cache: Loaded
Jan 07 10:04:45 HPFed kernel: Key type dns_resolver registered
Jan 07 10:04:46 HPFed kernel: Key type cifs.spnego registered
Jan 07 10:04:46 HPFed kernel: Key type cifs.idmap registered
Jan 07 10:04:46 HPFed kernel: CIFS: Attempting to mount
\\192.168.1.209\Public
Jan 07 10:04:51 HPFed chronyd[1041]: Selected source 83.151.207.133
(2.fedora.pool.ntp.org)
Jan 07 10:04:51 HPFed chronyd[1041]: System clock TAI offset set to
37 seconds
Jan 07 10:04:52 HPFed mount[1305]: mount error(113): could not
connect to 192.168.1.209Unable to find suitable address.
Jan 07 10:04:52 HPFed kernel: CIFS: VFS: Error connecting to socket.
Aborting operation.
Jan 07 10:04:52 HPFed kernel: CIFS: VFS: cifs_mount failed w/return
code = -113
Jan 07 10:04:52 HPFed kernel: CIFS: Attempting to mount
\\192.168.1.67\Public
Jan 07 10:04:52 HPFed systemd[1]: mnt-nas2a.mount: Mount process
exited, code=exited, status=32/n/a
Jan 07 10:04:52 HPFed systemd[1]: mnt-nas2a.mount: Failed with result
'exit-code'.
Jan 07 10:04:52 HPFed systemd[1]: Failed to mount mnt-nas2a.mount -
/mnt/nas2a.
Jan 07 10:04:52 HPFed systemd[1]: Dependency failed for
remote-fs.target - Remote File Systems.
Jan 07 10:04:52 HPFed systemd[1]: remote-fs.target: Job
remote-fs.target/start failed with result 'dependency'.
Jan 07 10:04:52 HPFed systemd[1]: Starting
systemd-user-sessions.service - Permit User Sessions...
Jan 07 10:04:52 HPFed systemd[1]: Finished
systemd-user-sessions.service - Permit User Sessions.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel
msg='unit=systemd-user-sessions comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=atd
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:52 HPFed systemd[1]: Started atd.service - Deferred
execution scheduler.
Jan 07 10:04:52 HPFed systemd[1]: Started crond.service - Command
Scheduler.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=crond
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:52 HPFed systemd[1]: Starting plymouth-quit-wait.service
- Hold until boot process finishes up...
Jan 07 10:04:52 HPFed systemd[1]: Starting plymouth-quit.service -
Terminate Plymouth Boot Screen...
Jan 07 10:04:52 HPFed systemd[1]: Mounted mnt-nas1a.mount - /mnt/nas1a.
Jan 07 10:04:52 HPFed systemd[1]: Received SIGRTMIN+21 from PID 346
(plymouthd).
Jan 07 10:04:52 HPFed systemd[1]: Received SIGRTMIN+21 from PID 346
(plymouthd).
Jan 07 10:04:52 HPFed systemd[1]: Finished plymouth-quit-wait.service
- Hold until boot process finishes up.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel
msg='unit=plymouth-quit-wait comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 07 10:04:52 HPFed systemd[1]: Finished plymouth-quit.service -
Terminate Plymouth Boot Screen.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymouth-quit
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:52 HPFed crond[1357]: (CRON) STARTUP (1.5.7)
Jan 07
Re: cifs problem? was Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
On 9/1/23 21:26, John Pilkington wrote:
Maybe this is https://bugzilla.kernel.org/show_bug.cgi?id=216895,
referred to in this current thread:
Re: Fedora 37 hangs after graphical login
I have two cifs mounting lines in /etc/fstab; only one has the
hardware connected.
I have cifs... vers=3.0,
//192.168.1.XX/Public /mnt/nas1a cifs
credentials=,iocharset=utf8,gid=1000,uid=1000,vers=3.0,file_mode=0777,dir_mode=0777
0 0
Here is a 'journalctl' output from, first, 6.0.16 (which hung) and
then 6.0.15, which completed. Maybe it will help. Or perhaps just
wait for 6.0.18...
nas1a is on the network, nas2a is not. The main difference here
appears to be that with 6.0.16 sddm is not being called.
{{{
[john@HPFed ~]$ sudo journalctl --since 2023-01-07 | grep -A 20 nas2a
Jan 07 10:04:44 HPFed systemd[1]: Mounting mnt-nas2a.mount -
/mnt/nas2a...
Jan 07 10:04:44 HPFed systemd[1]: Starting rpc-statd-notify.service -
Notify NFS peers of a restart...
Jan 07 10:04:44 HPFed systemd[1]: iscsi.service: Unit cannot be
reloaded because it is inactive.
Jan 07 10:04:45 HPFed sm-notify[1304]: Version 2.6.2 starting
Jan 07 10:04:45 HPFed systemd[1]: Started rpc-statd-notify.service -
Notify NFS peers of a restart.
Jan 07 10:04:45 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=rpc-statd-notify
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:45 HPFed kernel: FS-Cache: Loaded
Jan 07 10:04:45 HPFed kernel: Key type dns_resolver registered
Jan 07 10:04:46 HPFed kernel: Key type cifs.spnego registered
Jan 07 10:04:46 HPFed kernel: Key type cifs.idmap registered
Jan 07 10:04:46 HPFed kernel: CIFS: Attempting to mount
\\192.168.1.209\Public
Jan 07 10:04:51 HPFed chronyd[1041]: Selected source 83.151.207.133
(2.fedora.pool.ntp.org)
Jan 07 10:04:51 HPFed chronyd[1041]: System clock TAI offset set to 37
seconds
Jan 07 10:04:52 HPFed mount[1305]: mount error(113): could not connect
to 192.168.1.209Unable to find suitable address.
Jan 07 10:04:52 HPFed kernel: CIFS: VFS: Error connecting to socket.
Aborting operation.
Jan 07 10:04:52 HPFed kernel: CIFS: VFS: cifs_mount failed w/return
code = -113
Jan 07 10:04:52 HPFed kernel: CIFS: Attempting to mount
\\192.168.1.67\Public
Jan 07 10:04:52 HPFed systemd[1]: mnt-nas2a.mount: Mount process
exited, code=exited, status=32/n/a
Jan 07 10:04:52 HPFed systemd[1]: mnt-nas2a.mount: Failed with result
'exit-code'.
Jan 07 10:04:52 HPFed systemd[1]: Failed to mount mnt-nas2a.mount -
/mnt/nas2a.
Jan 07 10:04:52 HPFed systemd[1]: Dependency failed for
remote-fs.target - Remote File Systems.
Jan 07 10:04:52 HPFed systemd[1]: remote-fs.target: Job
remote-fs.target/start failed with result 'dependency'.
Jan 07 10:04:52 HPFed systemd[1]: Starting
systemd-user-sessions.service - Permit User Sessions...
Jan 07 10:04:52 HPFed systemd[1]: Finished
systemd-user-sessions.service - Permit User Sessions.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel
msg='unit=systemd-user-sessions comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=atd
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:52 HPFed systemd[1]: Started atd.service - Deferred
execution scheduler.
Jan 07 10:04:52 HPFed systemd[1]: Started crond.service - Command
Scheduler.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=crond
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:52 HPFed systemd[1]: Starting plymouth-quit-wait.service
- Hold until boot process finishes up...
Jan 07 10:04:52 HPFed systemd[1]: Starting plymouth-quit.service -
Terminate Plymouth Boot Screen...
Jan 07 10:04:52 HPFed systemd[1]: Mounted mnt-nas1a.mount - /mnt/nas1a.
Jan 07 10:04:52 HPFed systemd[1]: Received SIGRTMIN+21 from PID 346
(plymouthd).
Jan 07 10:04:52 HPFed systemd[1]: Received SIGRTMIN+21 from PID 346
(plymouthd).
Jan 07 10:04:52 HPFed systemd[1]: Finished plymouth-quit-wait.service
- Hold until boot process finishes up.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel
msg='unit=plymouth-quit-wait comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 07 10:04:52 HPFed systemd[1]: Finished plymouth-quit.service -
Terminate Plymouth Boot Screen.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymouth-quit
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:52 HPFed crond[1357]: (CRON) STARTUP (1.5.7)
Jan 07 10:04:52 HPFed crond[1357]: (CRON) INFO
Re: cifs problem? was Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
Maybe this is https://bugzilla.kernel.org/show_bug.cgi?id=216895,
referred to in this current thread:
Re: Fedora 37 hangs after graphical login
I have two cifs mounting lines in /etc/fstab; only one has the
hardware connected.
I have cifs... vers=3.0,
//192.168.1.XX/Public /mnt/nas1a cifs
credentials=,iocharset=utf8,gid=1000,uid=1000,vers=3.0,file_mode=0777,dir_mode=0777 0 0
Here is a 'journalctl' output from, first, 6.0.16 (which hung) and then
6.0.15, which completed. Maybe it will help. Or perhaps just wait for
6.0.18...
nas1a is on the network, nas2a is not. The main difference here appears
to be that with 6.0.16 sddm is not being called.
{{{
[john@HPFed ~]$ sudo journalctl --since 2023-01-07 | grep -A 20 nas2a
Jan 07 10:04:44 HPFed systemd[1]: Mounting mnt-nas2a.mount - /mnt/nas2a...
Jan 07 10:04:44 HPFed systemd[1]: Starting rpc-statd-notify.service -
Notify NFS peers of a restart...
Jan 07 10:04:44 HPFed systemd[1]: iscsi.service: Unit cannot be reloaded
because it is inactive.
Jan 07 10:04:45 HPFed sm-notify[1304]: Version 2.6.2 starting
Jan 07 10:04:45 HPFed systemd[1]: Started rpc-statd-notify.service -
Notify NFS peers of a restart.
Jan 07 10:04:45 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=rpc-statd-notify
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:45 HPFed kernel: FS-Cache: Loaded
Jan 07 10:04:45 HPFed kernel: Key type dns_resolver registered
Jan 07 10:04:46 HPFed kernel: Key type cifs.spnego registered
Jan 07 10:04:46 HPFed kernel: Key type cifs.idmap registered
Jan 07 10:04:46 HPFed kernel: CIFS: Attempting to mount
\\192.168.1.209\Public
Jan 07 10:04:51 HPFed chronyd[1041]: Selected source 83.151.207.133
(2.fedora.pool.ntp.org)
Jan 07 10:04:51 HPFed chronyd[1041]: System clock TAI offset set to 37
seconds
Jan 07 10:04:52 HPFed mount[1305]: mount error(113): could not connect
to 192.168.1.209Unable to find suitable address.
Jan 07 10:04:52 HPFed kernel: CIFS: VFS: Error connecting to socket.
Aborting operation.
Jan 07 10:04:52 HPFed kernel: CIFS: VFS: cifs_mount failed w/return code
= -113
Jan 07 10:04:52 HPFed kernel: CIFS: Attempting to mount
\\192.168.1.67\Public
Jan 07 10:04:52 HPFed systemd[1]: mnt-nas2a.mount: Mount process exited,
code=exited, status=32/n/a
Jan 07 10:04:52 HPFed systemd[1]: mnt-nas2a.mount: Failed with result
'exit-code'.
Jan 07 10:04:52 HPFed systemd[1]: Failed to mount mnt-nas2a.mount -
/mnt/nas2a.
Jan 07 10:04:52 HPFed systemd[1]: Dependency failed for remote-fs.target
- Remote File Systems.
Jan 07 10:04:52 HPFed systemd[1]: remote-fs.target: Job
remote-fs.target/start failed with result 'dependency'.
Jan 07 10:04:52 HPFed systemd[1]: Starting systemd-user-sessions.service
- Permit User Sessions...
Jan 07 10:04:52 HPFed systemd[1]: Finished systemd-user-sessions.service
- Permit User Sessions.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel
msg='unit=systemd-user-sessions comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=atd comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jan 07 10:04:52 HPFed systemd[1]: Started atd.service - Deferred
execution scheduler.
Jan 07 10:04:52 HPFed systemd[1]: Started crond.service - Command Scheduler.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=crond
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:52 HPFed systemd[1]: Starting plymouth-quit-wait.service -
Hold until boot process finishes up...
Jan 07 10:04:52 HPFed systemd[1]: Starting plymouth-quit.service -
Terminate Plymouth Boot Screen...
Jan 07 10:04:52 HPFed systemd[1]: Mounted mnt-nas1a.mount - /mnt/nas1a.
Jan 07 10:04:52 HPFed systemd[1]: Received SIGRTMIN+21 from PID 346
(plymouthd).
Jan 07 10:04:52 HPFed systemd[1]: Received SIGRTMIN+21 from PID 346
(plymouthd).
Jan 07 10:04:52 HPFed systemd[1]: Finished plymouth-quit-wait.service -
Hold until boot process finishes up.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymouth-quit-wait
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:52 HPFed systemd[1]: Finished plymouth-quit.service -
Terminate Plymouth Boot Screen.
Jan 07 10:04:52 HPFed audit[1]: SERVICE_START pid=1 uid=0
auid=4294967295 ses=4294967295 subj=kernel msg='unit=plymouth-quit
comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=?
terminal=? res=success'
Jan 07 10:04:52 HPFed crond[1357]: (CRON) STARTUP (1.5.7)
Jan 07 10:04:52 HPFed crond[1357]: (CRON) INFO (RANDOM_DELAY will be
scaled with factor
Re: cifs problem? was Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
On 9/1/23 01:53, John Pilkington wrote: On 08/01/2023 13:58, Stephen Morris wrote: On 8/1/23 21:26, John Pilkington wrote: On 08/01/2023 02:10, Stephen Morris wrote: On 8/1/23 12:59, Samuel Sieb wrote: On 1/7/23 17:24, Stephen Morris wrote: I've attached ~/.local/share/xorg/Xorg.0.log (my Xorg doesn't write its log to /var/log) as the end of my log file is completely different to what you are showing. I also don't have an xorg.conf file as I can get the 4K resolution I run with without the need for any specific specifications. The only configuration file in xorg.conf.d is the one for the keyboard. By default, Xorg doesn't run as root any more, so it can only write logs to the user directory. I only included that specification for where my Xorg.0.log file is located because John was indicating that his Xorg.0.log is being written to /var/log. regards, Steve Maybe this is https://bugzilla.kernel.org/show_bug.cgi?id=216895, referred to in this current thread: Re: Fedora 37 hangs after graphical login I have two cifs mounting lines in /etc/fstab; only one has the hardware connected. I have a cifs mount and nfs mount in my /etc/fstab to the same network device that is not always accessible because of the power saving function in the device. In earlier versions of Fedora if the device was not accessible the boot process used to hang and I would have to boot into Windows (where I also had it mounted on a drive mapping) to get explorer to activate the device and then boot into Fedora to get a successful boot. So far I haven't had this issue occur, but this may be because I mount the nfs interface first, or because in the cifs definition I use the _netdev parameter which as I understand it is supposed to ignore the mount if the network device is unavailable. What I also haven't done yet is isolate the invalid parameter when I change the definition to use smb3 instead of cifs (smb3 supercedes cifs). regards, Steve I have cifs... vers=3.0, //192.168.1.XX/Public /mnt/nas1a cifs credentials=,iocharset=utf8,gid=1000,uid=1000,vers=3.0,file_mode=0777,dir_mode=0777 0 0 I have cifs... vers=1.0 because the nas device I am using it too old to support cifs version 3, as I understand it smb3 is version 3.0 or 3.1, but does support the vers=3.1.1 specification for Windows 10 or Windows 11. //192.168.1.12/Volume_1 /mnt/dlink cifs rw,_netdev,nofail,noatime,vers=1.0,credentials=/etc/dlinkcreds 0 0 I'm also interested in what environment the person in the bug report is using as in his cifs definition he had the USER parameter specified, as Fedora doesn't support that parameter for cifs mounts, and if you specify it the mount fails with the message "User mounts are not supported by cifs". I also have the _netdev parameter specified as that indicates the device is a network device and hence delays the mount until the network is available. The nofail parameter specifies to not produce errors if the device is unavailable, which may stop the hang if the device is not there. I also have mount entries for Windows 11 devices and for those I'm using the ntfs-3g driver rather than cifs or smb3. UUID=52F237FCF237E2C1 /mnt/wine ntfs-3g user,auto,noatime,nodiratime,exec,rw 0 0 regards, Steve Thanks, John P ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to
cifs problem? was Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
On 08/01/2023 13:58, Stephen Morris wrote: On 8/1/23 21:26, John Pilkington wrote: On 08/01/2023 02:10, Stephen Morris wrote: On 8/1/23 12:59, Samuel Sieb wrote: On 1/7/23 17:24, Stephen Morris wrote: I've attached ~/.local/share/xorg/Xorg.0.log (my Xorg doesn't write its log to /var/log) as the end of my log file is completely different to what you are showing. I also don't have an xorg.conf file as I can get the 4K resolution I run with without the need for any specific specifications. The only configuration file in xorg.conf.d is the one for the keyboard. By default, Xorg doesn't run as root any more, so it can only write logs to the user directory. I only included that specification for where my Xorg.0.log file is located because John was indicating that his Xorg.0.log is being written to /var/log. regards, Steve Maybe this is https://bugzilla.kernel.org/show_bug.cgi?id=216895, referred to in this current thread: Re: Fedora 37 hangs after graphical login I have two cifs mounting lines in /etc/fstab; only one has the hardware connected. I have a cifs mount and nfs mount in my /etc/fstab to the same network device that is not always accessible because of the power saving function in the device. In earlier versions of Fedora if the device was not accessible the boot process used to hang and I would have to boot into Windows (where I also had it mounted on a drive mapping) to get explorer to activate the device and then boot into Fedora to get a successful boot. So far I haven't had this issue occur, but this may be because I mount the nfs interface first, or because in the cifs definition I use the _netdev parameter which as I understand it is supposed to ignore the mount if the network device is unavailable. What I also haven't done yet is isolate the invalid parameter when I change the definition to use smb3 instead of cifs (smb3 supercedes cifs). regards, Steve I have cifs... vers=3.0, //192.168.1.XX/Public /mnt/nas1a cifs credentials=,iocharset=utf8,gid=1000,uid=1000,vers=3.0,file_mode=0777,dir_mode=0777 0 0 Thanks, John P ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
On 8/1/23 21:26, John Pilkington wrote: On 08/01/2023 02:10, Stephen Morris wrote: On 8/1/23 12:59, Samuel Sieb wrote: On 1/7/23 17:24, Stephen Morris wrote: I've attached ~/.local/share/xorg/Xorg.0.log (my Xorg doesn't write its log to /var/log) as the end of my log file is completely different to what you are showing. I also don't have an xorg.conf file as I can get the 4K resolution I run with without the need for any specific specifications. The only configuration file in xorg.conf.d is the one for the keyboard. By default, Xorg doesn't run as root any more, so it can only write logs to the user directory. I only included that specification for where my Xorg.0.log file is located because John was indicating that his Xorg.0.log is being written to /var/log. regards, Steve Maybe this is https://bugzilla.kernel.org/show_bug.cgi?id=216895, referred to in this current thread: Re: Fedora 37 hangs after graphical login I have two cifs mounting lines in /etc/fstab; only one has the hardware connected. I have a cifs mount and nfs mount in my /etc/fstab to the same network device that is not always accessible because of the power saving function in the device. In earlier versions of Fedora if the device was not accessible the boot process used to hang and I would have to boot into Windows (where I also had it mounted on a drive mapping) to get explorer to activate the device and then boot into Fedora to get a successful boot. So far I haven't had this issue occur, but this may be because I mount the nfs interface first, or because in the cifs definition I use the _netdev parameter which as I understand it is supposed to ignore the mount if the network device is unavailable. What I also haven't done yet is isolate the invalid parameter when I change the definition to use smb3 instead of cifs (smb3 supercedes cifs). regards, Steve Thanks, John P ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
On 08/01/2023 02:10, Stephen Morris wrote: On 8/1/23 12:59, Samuel Sieb wrote: On 1/7/23 17:24, Stephen Morris wrote: I've attached ~/.local/share/xorg/Xorg.0.log (my Xorg doesn't write its log to /var/log) as the end of my log file is completely different to what you are showing. I also don't have an xorg.conf file as I can get the 4K resolution I run with without the need for any specific specifications. The only configuration file in xorg.conf.d is the one for the keyboard. By default, Xorg doesn't run as root any more, so it can only write logs to the user directory. I only included that specification for where my Xorg.0.log file is located because John was indicating that his Xorg.0.log is being written to /var/log. regards, Steve Maybe this is https://bugzilla.kernel.org/show_bug.cgi?id=216895, referred to in this current thread: Re: Fedora 37 hangs after graphical login I have two cifs mounting lines in /etc/fstab; only one has the hardware connected. Thanks, John P ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
On 8/1/23 12:59, Samuel Sieb wrote: On 1/7/23 17:24, Stephen Morris wrote: I've attached ~/.local/share/xorg/Xorg.0.log (my Xorg doesn't write its log to /var/log) as the end of my log file is completely different to what you are showing. I also don't have an xorg.conf file as I can get the 4K resolution I run with without the need for any specific specifications. The only configuration file in xorg.conf.d is the one for the keyboard. By default, Xorg doesn't run as root any more, so it can only write logs to the user directory. I only included that specification for where my Xorg.0.log file is located because John was indicating that his Xorg.0.log is being written to /var/log. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
On 1/7/23 17:24, Stephen Morris wrote: I've attached ~/.local/share/xorg/Xorg.0.log (my Xorg doesn't write its log to /var/log) as the end of my log file is completely different to what you are showing. I also don't have an xorg.conf file as I can get the 4K resolution I run with without the need for any specific specifications. The only configuration file in xorg.conf.d is the one for the keyboard. By default, Xorg doesn't run as root any more, so it can only write logs to the user directory. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
On 7/1/23 22:06, John Pilkington wrote:
On 07/01/2023 03:30, Stephen Morris wrote:
On 6/1/23 22:22, John Pilkington wrote:
Heads up. After today's updates I get black unresponsive screens.
OK in 6.0.15
I'm using the nvidia 525.60.11 driver from
rpmfusion-nonfree-nvidia-driver and there is no issue with kernel
6.0.16.
regards,
Steve
Thanks. It's still the same for me after another dnf upgrade run.
Using KDE, it boots and continues for some time after password entry,
but then stays unresponsive. No light shows after Caps Lock key, and
no mouse pointer or action. 6.0.15 works.
/var/log/Xorg.0.log looks similar for both. For info, here's the end:
[ 201.742] (--) NVIDIA(GPU-0): DELL 2009W (CRT-0): connected
[ 201.742] (--) NVIDIA(GPU-0): DELL 2009W (CRT-0): 400.0 MHz maximum
pixel clock
[ 201.742] (--) NVIDIA(GPU-0):
[ 201.742] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 201.742] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 201.742] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[ 201.742] (--) NVIDIA(GPU-0):
[ 201.787] (--) NVIDIA(GPU-0): SONY TV (DFP-1): connected
[ 201.787] (--) NVIDIA(GPU-0): SONY TV (DFP-1): Internal TMDS
[ 201.787] (--) NVIDIA(GPU-0): SONY TV (DFP-1): 340.0 MHz maximum
pixel clock
[ 201.787] (--) NVIDIA(GPU-0):
[ 217.638] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select
@1360x768 +0+0 {ViewPortIn=1360x768, ViewPortOut=1360x768+0+0}"
[ 217.739] (II) NVIDIA(0): Setting mode "NULL"
[ 217.783] (II) NVIDIA(0): Setting mode "VGA-0: nvidia-auto-select
@1680x1050 +0+30 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0}"
[ 217.825] (II) NVIDIA(0): Setting mode "VGA-0: nvidia-auto-select
@1680x1050 +0+30 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0},
HDMI-0: 1920x1080_50 @1920x1080 +1680+0 {ViewPortIn=1920x1080,
ViewPortOut=1920x1080+0+0}"
I've attached ~/.local/share/xorg/Xorg.0.log (my Xorg doesn't write its
log to /var/log) as the end of my log file is completely different to
what you are showing. I also don't have an xorg.conf file as I can get
the 4K resolution I run with without the need for any specific
specifications. The only configuration file in xorg.conf.d is the one
for the keyboard.
regards,
Steve
John
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
[ 291.838] (--) Log file renamed from "/home/steve/.local/share/xorg/Xorg.pid-2449.log" to "/home/steve/.local/share/xorg/Xorg.0.log"
[ 291.838]
X.Org X Server 1.20.14
X Protocol Version 11, Revision 0
[ 291.838] Build Operating System: 6.0.9-300.fc37.x86_64
[ 291.838] Current Operating System: Linux fedora 6.0.16-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Dec 31 16:47:53 UTC 2022 x86_64
[ 291.838] Kernel command line: BOOT_IMAGE=/vmlinuz-6.0.16-300.fc37.x86_64 root=UUID=d22cf9df-0b3c-413a-a82f-b623c56c9841 ro rootflags=subvol=Fedora_Root rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1
[ 291.838] Build Date: 19 December 2022 12:00:00AM
[ 291.838] Build ID: xorg-x11-server 1.20.14-12.fc37
[ 291.838] Current version of pixman: 0.40.0
[ 291.838] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 291.838] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 291.838] (==) Log file: "/home/steve/.local/share/xorg/Xorg.0.log", Time: Sun Jan 8 09:07:59 2023
[ 291.842] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 291.842] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 291.849] (==) ServerLayout "layout"
[ 291.850] (==) No screen section available. Using defaults.
[ 291.850] (**) |-->Screen "Default Screen Section" (0)
[ 291.850] (**) | |-->Monitor ""
[ 291.850] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 291.850] (==) Automatically adding devices
[ 291.850] (==) Automatically enabling devices
[ 291.850] (==) Automatically adding GPU devices
[ 291.850] (==) Automatically binding GPU devices
[ 291.850] (==) Max clients allowed: 256, resource mask: 0x1f
[ 291.850] (==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins
[ 291.850] (==) ModulePath set to "/usr/lib64/xorg/modules"
[ 291.850] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[
Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
On 07/01/2023 03:30, Stephen Morris wrote:
On 6/1/23 22:22, John Pilkington wrote:
Heads up. After today's updates I get black unresponsive screens. OK
in 6.0.15
I'm using the nvidia 525.60.11 driver from
rpmfusion-nonfree-nvidia-driver and there is no issue with kernel 6.0.16.
regards,
Steve
Thanks. It's still the same for me after another dnf upgrade run.
Using KDE, it boots and continues for some time after password entry,
but then stays unresponsive. No light shows after Caps Lock key, and no
mouse pointer or action. 6.0.15 works.
/var/log/Xorg.0.log looks similar for both. For info, here's the end:
[ 201.742] (--) NVIDIA(GPU-0): DELL 2009W (CRT-0): connected
[ 201.742] (--) NVIDIA(GPU-0): DELL 2009W (CRT-0): 400.0 MHz maximum
pixel clock
[ 201.742] (--) NVIDIA(GPU-0):
[ 201.742] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 201.742] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 201.742] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[ 201.742] (--) NVIDIA(GPU-0):
[ 201.787] (--) NVIDIA(GPU-0): SONY TV (DFP-1): connected
[ 201.787] (--) NVIDIA(GPU-0): SONY TV (DFP-1): Internal TMDS
[ 201.787] (--) NVIDIA(GPU-0): SONY TV (DFP-1): 340.0 MHz maximum
pixel clock
[ 201.787] (--) NVIDIA(GPU-0):
[ 217.638] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select
@1360x768 +0+0 {ViewPortIn=1360x768, ViewPortOut=1360x768+0+0}"
[ 217.739] (II) NVIDIA(0): Setting mode "NULL"
[ 217.783] (II) NVIDIA(0): Setting mode "VGA-0: nvidia-auto-select
@1680x1050 +0+30 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0}"
[ 217.825] (II) NVIDIA(0): Setting mode "VGA-0: nvidia-auto-select
@1680x1050 +0+30 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0},
HDMI-0: 1920x1080_50 @1920x1080 +1680+0 {ViewPortIn=1920x1080,
ViewPortOut=1920x1080+0+0}"
John
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
On 6/1/23 22:22, John Pilkington wrote: Heads up. After today's updates I get black unresponsive screens. OK in 6.0.15 I'm using the nvidia 525.60.11 driver from rpmfusion-nonfree-nvidia-driver and there is no issue with kernel 6.0.16. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
