SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to talk to my digital camera with a 64 bit amd laptop on Slamd64-12.2. This mount command fails
mount -s -t vfat /dev/sdb1 /mnt
mount gives the usual(meaningless) error message. dmesg |tail tells me codepage 437 was not found. I should be on codepage 850, iso-8859-15, iso-8859-1, utf-8 or something. Where the hell is it getting cp 437?
/etc/environment doesn't exist and in fact the whole console environment is close to defaults. I rolled my own kernel and thought cp 437 went out with m$dos (Anyone old enough to remember that?). I rolled my own kernel some and never bothered with cp 437. Who'd need that, I thought? Waste of space. Hmmmm.
Using Slackware64 here "mount /dev/sdb1 /flash" works just fine.
But if you need it, it's in the Slackware64 kernel:
Code:
mingdao@jeremiah:~$ less /boot/config | grep -i 437
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_NLS_CODEPAGE_437=y
Maybe consider switch to Slackware64 now.
Thank you. I have actually worked around it. I rolled my own kernel some time back as I had trouble with every chip in this box. Distro kernels don't suit. Slamd64's original kernel (Modeled on slackware's) gave issues on acpi, compile times, disk speeds, and a whole bunch more. There has been a _long_ war to get this box behaving and will be another to refine it when I have the mental energy. I was hoping to mount fat drives without cp 437 by resetting locally. My fix was
sed 's/850/437/' < ./2.6.29.1-SD64/kernel/fs/nls/nls_cp850.ko >
./2.6.29.1-SD64/kernel/fs/nls/nls_cp437.ko
and roll myself one that way. The LAST thing I want to suffer is another kernel recompile.
I feel your pain. As good as the Slackware kernels are built, they
also usually require a recompile on most of my boxen. And remember,
that kernel .config you just made is portable. Save it and you can
use it compiling a kernel on any box, any distro. I always issue
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.