On 08/01/2023 13:58, Stephen Morris wrote: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.
On 8/1/23 21:26, John Pilkington wrote:
On 08/01/2023 02:10, Stephen Morris wrote: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).
On 8/1/23 12:59, Samuel Sieb wrote:
On 1/7/23 17:24, Stephen Morris wrote: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.
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.
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.
regards,
Steve
I have cifs... vers=3.0,
//192.168.1.XX/Public /mnt/nas1a cifs credentials=<pathtocredfile>,iocharset=utf8,gid=1000,uid=1000,vers=3.0,file_mode=0777,dir_mode=0777 0 0
//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@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
