Architecture x86_64 with kernel 3.18.0-19274-ge8af1008445e is not supported
I am getting that this is unsupported, I just double checked and:
Kernel: 3.8.11 Arch: x86_64 says that it is supported.. does the .11 make the difference? Or have I done something wrong?
I need to build new modules and also make a change in the code. So it ignores the kernel id and only looks at the kernel version.
@brizzbane Sorry not so good news. This seems to be a pain in the ass issue. We need to checkout the correct version of the kernel, else the modules will not load.
cifs: version magic '3.18.0-19285-g9f6cff6be6b8-dirty SMP preempt mod_unload ' should be '3.18.0-19093-gcea381446944 SMP preempt mod_unload
That will be a real challenge... standard Integrated smb share mounting in chromeos is really slow in data transfer, so I will be motivated to get this working. See if we can somehow change the kernel version in the cifs module.
Let me know if I can be of any help.
Originally I was trying to get shares to work inside of a Debian Stretch chroot. I ran into issues with cifs-utilities, which I am pretty sure is related to kernel stuff.
I came across your solution here (3.):
https://github.com/dnschneid/crouton/wiki/How-to-mount-network-shares-on-Chromebook-(sshfs,-cifs,-nfs-etc)#browsing-smb-shares-in-the-file-app-from-chrome
Which looked like the simplest solution, and would make the shares faster in Chrome OS. The default implementation of SMB is slow as your mentioned...
I then started reading (because I was pretty sure that the reason cifs-utilities didn't work in Debian was kernel problems):
https://github.com/dnschneid/crouton/wiki/Build-chrome-os-kernel-and-kernel-modules
... but your solution looked like the simplest (i.e. less likely to run into problems making work).
Anyways, I appreciate you looking into it. If there is anything I can do on my end to test, or whatever, lmk.