LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices


Reply
  Search this Thread
Old 03-26-2017, 02:19 PM   #1
GrumpyGnome
Member
 
Registered: May 2004
Location: El Sobrante, CA (the scraps)
Distribution: Fedora, RH, & Slack
Posts: 57

Rep: Reputation: 15
Slackware 14.2 Surface Pro 3 & exfat problem


I have a Surface Pro 3 with Slackware 14.2 running and have not been able to get the SlackBuild exfat to install and function. I'm hoping to use 64GB microSD cards in the card reader slot. I downloaded the fuse-exfat-1.2.6 and exfat-utils-1.2.6 SlackBuilds and source. When I ran the ./fuse-exfat.SlackBuild it failed with an error from SCons "SConstruct file not found". And when I looked there was no SConstruct file anywhere in the package. So then I did a manual ./configure, make, and 'make install' process. That all looked like it ran without errors. I also did that for the exfat-utils-
However after a cold boot I still did not have any exfat support for the microSD card slot.
This is over my head at this point as I have not written a C program for Linux in 20 years.
Is the exfat not intended for use with an mSD card?
Have I stumbled into a limitation of the Surface that can't use the exfat for an mSD card?
Any thoughts are appreciated.
Thank you.
 
Old 03-27-2017, 11:40 AM   #2
aaazen
Member
 
Registered: Dec 2009
Posts: 358

Rep: Reputation: Disabled
Quote:
Originally Posted by GrumpyGnome View Post
I have a Surface Pro 3 with Slackware 14.2 running and have not been able to get the SlackBuild exfat to install and function. I'm hoping to use 64GB microSD cards in the card reader slot. I downloaded the fuse-exfat-1.2.6 and exfat-utils-1.2.6 SlackBuilds and source. When I ran the ./fuse-exfat.SlackBuild it failed with an error from SCons "SConstruct file not found"...
Maybe SCons is an "undocumented" requirement?

It looks like the SCons package was not updated for Slackware 14.2, but there is a 14.1 package at https://slackbuilds.org/repository/1...lopment/scons/
 
Old 03-27-2017, 11:59 AM   #3
GrumpyGnome
Member
 
Registered: May 2004
Location: El Sobrante, CA (the scraps)
Distribution: Fedora, RH, & Slack
Posts: 57

Original Poster
Rep: Reputation: 15
Thanks for the reply aaazen,
I think the SCons I have is OK. SCons reports that it can't find the configure file in the SlackBuild.
That would mean that I need a SConfigure file for the SlackBuild.
But I will get the update.
I'll try to send some feedback to the fuse-exfat.SlacBuild maintainer regarding the SCons error message.
Happy Trails
 
Old 03-27-2017, 12:11 PM   #4
aaazen
Member
 
Registered: Dec 2009
Posts: 358

Rep: Reputation: Disabled
I now agree that SCons is not the issue. It comes with Slackware.

I can build fuse-exfat on both Slackware 14.2 and Slackware current with no errors.

What exact error do you get when you run the fuse-exfat.SlackBuild script as root?

Last edited by aaazen; 03-27-2017 at 12:12 PM. Reason: spelling
 
Old 03-27-2017, 12:36 PM   #5
aaazen
Member
 
Registered: Dec 2009
Posts: 358

Rep: Reputation: Disabled
I searched for SCons in the current fuse-exfat 1.2.6 directory and found this in the ChangeLog file:

Code:
...
1.2.0 (2015-08-26)

* Switched from SCons to autotools.
...
SCons should not show up as an issue unless you are using an old version of fuse-exfat...
 
1 members found this post helpful.
Old 03-28-2017, 06:02 PM   #6
GrumpyGnome
Member
 
Registered: May 2004
Location: El Sobrante, CA (the scraps)
Distribution: Fedora, RH, & Slack
Posts: 57

Original Poster
Rep: Reputation: 15
Hello aaazen,
First, thanks for the help it really is appreciated.
I am using the 1.2.6 version of fuse-exfat and exfat-utils. But reading what you found about the change from SCons to autotool gave me an idea.
First I had to change the version number in the fuse-exfat.SlackBuild file from 0.9.6 to 1.2.6. Humm...
I will comment out the SCons call in fuse-exfat.SlackBuild. Below are both the orig and changed build results.

Here is what I get running that file with just the version number change but with a reference to SCons:
Code:
./fuse-exfat.SlackBuild                                                                                 
fuse-exfat-1.2.6/
fuse-exfat-1.2.6/ChangeLog
fuse-exfat-1.2.6/depcomp
fuse-exfat-1.2.6/configure
fuse-exfat-1.2.6/configure.ac
fuse-exfat-1.2.6/Makefile.am
fuse-exfat-1.2.6/compile
fuse-exfat-1.2.6/install-sh
fuse-exfat-1.2.6/missing
fuse-exfat-1.2.6/libexfat/
fuse-exfat-1.2.6/libexfat/node.c
fuse-exfat-1.2.6/libexfat/exfatfs.h
fuse-exfat-1.2.6/libexfat/Makefile.am
fuse-exfat-1.2.6/libexfat/utf.c
fuse-exfat-1.2.6/libexfat/time.c
fuse-exfat-1.2.6/libexfat/byteorder.h
fuse-exfat-1.2.6/libexfat/utils.c
fuse-exfat-1.2.6/libexfat/compiler.h
fuse-exfat-1.2.6/libexfat/platform.h
fuse-exfat-1.2.6/libexfat/lookup.c
fuse-exfat-1.2.6/libexfat/log.c
fuse-exfat-1.2.6/libexfat/io.c
fuse-exfat-1.2.6/libexfat/config.h.in
fuse-exfat-1.2.6/libexfat/Makefile.in
fuse-exfat-1.2.6/libexfat/cluster.c
fuse-exfat-1.2.6/libexfat/exfat.h
fuse-exfat-1.2.6/libexfat/mount.c
fuse-exfat-1.2.6/aclocal.m4
fuse-exfat-1.2.6/Makefile.in
fuse-exfat-1.2.6/README
fuse-exfat-1.2.6/ar-lib
fuse-exfat-1.2.6/fuse/
fuse-exfat-1.2.6/fuse/Makefile.am
fuse-exfat-1.2.6/fuse/mount.exfat-fuse.8
fuse-exfat-1.2.6/fuse/Makefile.in
fuse-exfat-1.2.6/fuse/main.c
fuse-exfat-1.2.6/COPYING

scons: *** No SConstruct file found.
File "/usr/lib64/python2.7/site-packages/SCons/Script/Main.py", line 923, in _main
Now here is the log of running the build with the version change and the SCons line commented out:
Code:
bash-4.3# ./fuse-exfat.SlackBuild
fuse-exfat-1.2.6/
fuse-exfat-1.2.6/ChangeLog
fuse-exfat-1.2.6/depcomp
fuse-exfat-1.2.6/configure
fuse-exfat-1.2.6/configure.ac
fuse-exfat-1.2.6/Makefile.am
fuse-exfat-1.2.6/compile
fuse-exfat-1.2.6/install-sh
fuse-exfat-1.2.6/missing
fuse-exfat-1.2.6/libexfat/
fuse-exfat-1.2.6/libexfat/node.c
fuse-exfat-1.2.6/libexfat/exfatfs.h
fuse-exfat-1.2.6/libexfat/Makefile.am
fuse-exfat-1.2.6/libexfat/utf.c
fuse-exfat-1.2.6/libexfat/time.c
fuse-exfat-1.2.6/libexfat/byteorder.h
fuse-exfat-1.2.6/libexfat/utils.c
fuse-exfat-1.2.6/libexfat/compiler.h
fuse-exfat-1.2.6/libexfat/platform.h
fuse-exfat-1.2.6/libexfat/lookup.c
fuse-exfat-1.2.6/libexfat/log.c
fuse-exfat-1.2.6/libexfat/io.c
fuse-exfat-1.2.6/libexfat/config.h.in
fuse-exfat-1.2.6/libexfat/Makefile.in
fuse-exfat-1.2.6/libexfat/cluster.c
fuse-exfat-1.2.6/libexfat/exfat.h
fuse-exfat-1.2.6/libexfat/mount.c
fuse-exfat-1.2.6/aclocal.m4
fuse-exfat-1.2.6/Makefile.in
fuse-exfat-1.2.6/README
fuse-exfat-1.2.6/ar-lib
fuse-exfat-1.2.6/fuse/
fuse-exfat-1.2.6/fuse/Makefile.am
fuse-exfat-1.2.6/fuse/mount.exfat-fuse.8
fuse-exfat-1.2.6/fuse/Makefile.in
fuse-exfat-1.2.6/fuse/main.c
fuse-exfat-1.2.6/COPYING

Slackware package maker, version 3.141593.

Searching for symbolic links:

No symbolic links were found, so we won't make an installation script.
You can make your own later in ./install/doinst.sh and rebuild the
package if you like.

This next step is optional - you can set the directories in your package
to some sane permissions. If any of the directories in your package have
special permissions, then DO NOT reset them here!

Would you like to reset all directory permissions to 755 (drwxr-xr-x) and
directory ownerships to root.root ([y]es, [n]o)? n

Creating Slackware package:  /tmp/fuse-exfat-1.2.6-x86_64-1_SBo.tgz

./
install/
install/slack-desc
usr/
usr/doc/
usr/doc/fuse-exfat-1.2.6/
usr/doc/fuse-exfat-1.2.6/COPYING
usr/doc/fuse-exfat-1.2.6/ChangeLog
usr/doc/fuse-exfat-1.2.6/fuse-exfat.SlackBuild

Slackware package /tmp/fuse-exfat-1.2.6-x86_64-1_SBo.tgz created.
Now I have the following:
Code:
bash-4.3# ls -l /var/log/packages/*SBo
-rw-r--r-- 1 root root 1096 Mar 28 15:27 /var/log/packages/exfat-utils-1.2.6-x86_64-1_SBo
-rw-r--r-- 1 root root  822 Mar 28 15:27 /var/log/packages/fuse-exfat-1.2.6-x86_64-1_SBo
bash-4.3#
But still I get an error mounting my 64GB microSD card formatted as exfat.
It says:
Code:
An error occurred while accessing 'msd64', the system responded: The requested operation has failed: 
Error mounting /dev/sdb1 at /run/media/root/msd64: Command-line `mount -t "exfat" -o "uhelper=udisks2,nodev,nosuid,uid=0,gid=0,iocharset=utf8,namecase=0,errors=remount-ro,umask=0077" 
"/dev/sdb1" "/run/media/root/msd64"' exited with non-zero exit status 32: mount: unknown filesystem type 'exfat'
I must still be missing something. I wonder if the SlackBuild file needed to be a newer version and the old one was mistakenly added to the build.
Any thoughts are appreciated. I wonder if the exfat package is for USB and the microSD card slot is not USB based? I don't have a 64GB USB drive.
Happy Trails
 
Old 03-29-2017, 07:18 PM   #7
laprjns
Member
 
Registered: Oct 2005
Location: Connecticut USA
Distribution: SalixOS
Posts: 206

Rep: Reputation: 108Reputation: 108
Quote:
Originally Posted by GrumpyGnome View Post
First I had to change the version number in the fuse-exfat.SlackBuild file from 0.9.6 to 1.2.6. Humm...
If the default version of fuse-exfat in the Slackbuid script that you are using is 0.9.6 then you are using the slackbuild from 14.0. You should rebuild both packages using the slackbuilds from Slackbuilds.org 14.2 repo. The slackbuild from the 14.2 does not have any reference to scons and it may have other changes that could be resolve your problems.
Here's the file listing of a properly built fuse-exfat package.
Code:
Creating Slackware package:  /usr/src/slapt-src/system/fuse-exfat/fuse-exfat-1.2.6-x86_64-1_SBo.txz

./
usr/
usr/sbin/
usr/sbin/mount.exfat-fuse
usr/man/
usr/man/man8/
usr/man/man8/mount.exfat-fuse.8.gz
usr/doc/
usr/doc/fuse-exfat-1.2.6/
usr/doc/fuse-exfat-1.2.6/ChangeLog
usr/doc/fuse-exfat-1.2.6/COPYING
usr/doc/fuse-exfat-1.2.6/README
usr/doc/fuse-exfat-1.2.6/fuse-exfat.SlackBuild
install/
install/slack-desc
install/doinst.sh
Note the mount.exfat-fuse binary that will be installed in usr/sbin. The package that you built doesn't include this binary

Last edited by laprjns; 03-30-2017 at 09:52 AM.
 
1 members found this post helpful.
Old 04-02-2017, 03:11 PM   #8
GrumpyGnome
Member
 
Registered: May 2004
Location: El Sobrante, CA (the scraps)
Distribution: Fedora, RH, & Slack
Posts: 57

Original Poster
Rep: Reputation: 15
Thanks laprjns,

I re-downloaded the build and the resulting package is working.
I don't know how I got the other version. I've got no memory of poking around in the fuse-exfat files at SlackBuilds.org.
I will be less likely to just change a version number or other entries without a firm understanding of the process.
Happy Trails
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Using Linux on Surface Pro to study Networking with GNS3 Cytota Linux - Newbie 4 03-21-2017 10:07 PM
rEFInd issues on MS Surface Pro 3 with Secure Boot Rickkkk Linux - General 1 03-15-2017 05:20 PM
Fedora on Surface Pro 3 Timothy Miller Fedora 4 05-13-2016 02:18 PM
LXer: Surface Pro, Windows 8 Sales: Why It's Not 1995 All Over Again LXer Syndicated Linux News 0 03-14-2013 03:11 PM
Strange problem with Slackware & Intel Pro/Wireless 2200BG TADsince1995 Linux - Wireless Networking 2 04-25-2005 07:01 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation

All times are GMT -5. The time now is 12:25 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration