paul- wrote:
> So this only affected pizero and pi1 boards.
>
> Please update filesystems-KERNEL.tcz
>
> You can remove, reboot then re-add the file systems extension, or update
> it from the Extension browser or from command line
>
> pcp-update filesystems-KERNEL.tcz
FIXED! Thank you!
It now connects with vers=2.0 or 2.1 or 3.0. (for me, no need for
sec=ntlm)
Great news, thanks for the fix.
================
Just for completeness (I am happy with using 3.0 with pcp; my windows
machine uses 3.1.1 to connect so I tried using that):
It fails with vers=3.11 or 3.1.1 or no "vers=x.x", with this in dmesg
Code:
--------------------
[ 49.125566] CIFS: Attempting to mount //192.168.5.163/pcp
[ 49.402963] CIFS: VFS: Could not allocate crypto sha512
[ 49.439679] CIFS: VFS: Could not allocate crypto sha512
[ 49.480112] CIFS: VFS: Could not allocate crypto sha512
[ 49.513449] CIFS: VFS: Could not allocate crypto sha512
[ 49.679813] CIFS: VFS: Could not allocate crypto sha512
[ 49.683325] CIFS: VFS: \\192.168.5.163 failed to connect to IPC (rc=-13)
[ 49.686112] CIFS: VFS: session 2815892e has no tcon available for a dfs
referral request
[ 49.695150] CIFS: VFS: cifs_mount failed w/return code = -13
--------------------
Thanks again for fixing. If you want me to test anything else to fix
the above, happy to do so.
Tom
SB3(1), Boom(2), Radio(3), piCorePlayer (1)
------------------------------------------------------------------------
TomS's Profile: http://forums.slimdevices.com/member.php?userid=12525
View this thread: http://forums.slimdevices.com/showthread.php?t=114828
_______________________________________________
unix mailing list
unix@lists.slimdevices.com
http://lists.slimdevices.com/mailman/listinfo/unix
