LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 12-07-2002, 11:15 AM   #1
poldervaart
LQ Newbie
 
Registered: Dec 2002
Distribution: RH 8.0 (Psyche)
Posts: 9

Rep: Reputation: 0
Ftape Install Help (MCONFIG)


Hello, I am once again querying the knowlege of this forum for some help.

PROBLEM: I am trying to install ftape-4.04. I have edited the MCONFIG file the best I know how, but get errors when running the "make" command. I know that I am overlooking something simple. I am almost positive I have no idea what I am doing with the MCONFIG file, and that is most likely where my problem is. I have been unable to locate any information that can help me. I have tried the HOWTO's and the ftape documentation, and lots of searches on this forum and Google. Thank You.

HARDWARE:
Athlon XP 1700+ CPU
512 MB DDR Ram
Iomega Ditto 2GB Internal (Floppy Controller)

SOFTWARE:
Red Hat 8.0
Kernel linux-2.4.18-18.8.0 (with NTFS RO Module )
modutils-2.4.18-2
kernel-source-2.4.18-18.8.0
gcc-3.2-7

MAKE OUTPUT:
[user@host ftape-4.04]$ make
for i in ftape ; do make -C $i all ; done
make[1]: Entering directory `/home/chris/.Trash/ftape-4 (copy).04/ftape'
for i in lowlevel internal parport zftape compressor; \
do \
make -C $i NODEP=true versions; \
done
make[2]: Entering directory `/home/chris/.Trash/ftape-4 (copy).04/ftape/lowlevel'
rm -f ../../include/linux/modules/ftape_syms.ver.tmp; gcc -D__KERNEL__ -I. -I../../include -I/usr/src/linux-2.4.18-18.8.0//include -E -D__GENKSYMS__ ftape_syms.c | /sbin/genksyms ../../include/linux/modules 2> /dev/null; rm -f ../../include/linux/modules/ftape_syms.ver.tmp
make[2]: *** [../../include/linux/modules/ftape_syms.ver] Error 1
make[2]: Leaving directory `/home/chris/.Trash/ftape-4 (copy).04/ftape/lowlevel'make[2]: Entering directory `/home/chris/.Trash/ftape-4 (copy).04/ftape/internal'
make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/home/chris/.Trash/ftape-4 (copy).04/ftape/internal'make[2]: Entering directory `/home/chris/.Trash/ftape-4 (copy).04/ftape/parport'make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/home/chris/.Trash/ftape-4 (copy).04/ftape/parport'
make[2]: Entering directory `/home/chris/.Trash/ftape-4 (copy).04/ftape/zftape'
rm -f ../../include/linux/modules/zftape_syms.ver.tmp; gcc -D__KERNEL__ -I. -I../../include -I/usr/src/linux-2.4.18-18.8.0//include -E -D__GENKSYMS__ zftape_syms.c | /sbin/genksyms ../../include/linux/modules 2> /dev/null; rm -f ../../include/linux/modules/zftape_syms.ver.tmp
make[2]: *** [../../include/linux/modules/zftape_syms.ver] Error 1
make[2]: Leaving directory `/home/chris/.Trash/ftape-4 (copy).04/ftape/zftape'
make[2]: Entering directory `/home/chris/.Trash/ftape-4 (copy).04/ftape/compressor'
make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/home/chris/.Trash/ftape-4 (copy).04/ftape/compressor'
set -e; for i in lowlevel internal parport zftape compressor; do make -C $i modules; done
make[2]: Entering directory `/home/chris/.Trash/ftape-4 (copy).04/ftape/lowlevel'
rm -f ../../include/linux/modules/ftape_syms.ver.tmp; gcc -D__KERNEL__ -I. -I../../include -I/usr/src/linux-2.4.18-18.8.0//include -E -D__GENKSYMS__ ftape_syms.c | /sbin/genksyms ../../include/linux/modules 2> /dev/null; rm -f ../../include/linux/modules/ftape_syms.ver.tmp
make[2]: *** [../../include/linux/modules/ftape_syms.ver] Error 1
make[2]: Leaving directory `/home/chris/.Trash/ftape-4 (copy).04/ftape/lowlevel'make[1]: *** [modules] Error 2
make[1]: Leaving directory `/home/chris/.Trash/ftape-4 (copy).04/ftape'
make: *** [all] Error 2


I will include the details of my MCONFIG file in the next post.
 
Old 12-07-2002, 11:15 AM   #2
poldervaart
LQ Newbie
 
Registered: Dec 2002
Distribution: RH 8.0 (Psyche)
Posts: 9

Original Poster
Rep: Reputation: 0
MCONFIG is too large to post, so I included the items that I made changes to or configured:
....

LINUX_LOCATION = /usr/src/linux-2.4.18-18.8.0/
....

# You should also set the CONFIG_M386/486/586/686 according to your
# processor type. When running an DEC alpha then comment out the
# CONFIG_M486=y line and uncomment the CONFIG_ALPHA=y line.
#

#CONFIG_M386=y
#CONFIG_M486=y
#CONFIG_M586=y
CONFIG_M686=y
#CONFIG_MAMDK6
#CONFIG_ALPHA=y
#CONFIG_MODVERSIONS=y
#CONFIG_SMP = 1
......

##################################################
#############################
# IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT #
##################################################
#############################
#
# Hardware configuration for the floppy tape drive.
#
# You need to take care of the following options if you didn't connect
# your floppy tape to the standard floppy controller, i.e. if you
# didn't plugged the floppy tape into the floppy controller already
# contained in your computer system.
#
# Short description of available options
# (`FDC' stands for `Floppy Disk Controller')
#
# PROBE_FC10 - if defined will look for a FC-10 (or FC-20)
# card.
# FDC_BASE - sets base address if using non-standard fdc
# FDC_IRQ - sets interrupt if FDC_BASE is defined
# FDC_DMA - sets dma channel if FDC_BASE is defined
# MACH2 - Support for Mountain MACH-2 controller. You
# have to specify its base address (either
# 0x1E0 or 0x3E0).
# CLK_48MHZ - must be defined and set to 0 if your 82078
# is _not_ being run from a 48 Mhz clock
# oscillator. Normally you don't need to worry
# about it.
#
#
#
# If you're using a non-standard floppy disk controller for the tape
# drive, enable one (only!) of the following lines and set the
# FDC_BASE, FDC_IRQ and FDC_DMA parameters to the actual values.
#
# `enable' means: `uncomment one of the lines starting with
# "FDC_OPT = ..."'. `uncomment' means: remove the leading `#'
#
# The following values hopefully reflect the default settings for
# those controllers.
#
# Note1: A FC-10/FC-20 controller must use either of DMA 1, 2, or 3.
# DMA 5 and 7 does NOT work!.
#
# Note2: IRQ 2 and IRQ 9 can be considered the same. When using IRQ 2
# on a controller you must specify IRQ 9 here!
#
# Note3: *_ALL_* parameters can as well be set as module parameters
# during module loading. This means that the following values
# only give the defaults in case you load the modules without
# any parameters.
#
# Note4: The "..._DEV=0" lines determine which device nodes to use
# with which floppy tape controller (/dev/qft0, ...,
# /dev/qft3). In case you have an internal floppy tape plugged
# into the standard floppy controller and a parallel port
# floppy tape drive, then leave the "STD_DEV=0" line as it is
# and uncomment either the option settings for the Trakker or
# the BackPack tape drive and set either "TRAKKER_DEV=1" or
# "BPCK_DEV=1" to use the parallel port tape drive using
# "/dev/qft1".
#
FDC_OPT :=
#
# For a standard floppy tape controller or automatic configuration of
# parallel port floppy tape drives uncomment the following line:
#
AUTO_DEV=0
FDC_OPT += -DCONFIG_FT_STD_FDC_$(AUTO_DEV) \
-DCONFIG_FT_AUTO_$(AUTO_DEV)=1
#
# For a standard floppy tape controller, uncomment the following line:
#
#STD_DEV=0
#FDC_OPT += -DCONFIG_FT_STD_FDC_$(STD_DEV) \
# -DCONFIG_FT_INT_$(STD_DEV)=1
#
# For a Mountain MACH-2 controller, try
#
#MACH2_DEV=0
#FDC_OPT += -DCONFIG_FT_MACH2_$(MACH2_DEV)=1 \
# -DCONFIG_FT_FDC_BASE_$(MACH2_DEV)=0x1E0 \
# -DCONFIG_FT_FDC_IRQ_$(MACH2_DEV)=6 \
# -DCONFIG_FT_FDC_DMA_$(MACH2_DEV)=2 \
# -DCONFIG_FT_NR_BUFFERS=3 \
# -DCONFIG_FT_INT_$(MACH2_DEV)=1
#
# For Colorado CMS FC-10 or FC-20 controllers:
#
#FC10_DEV=0
#FDC_OPT += -DCONFIG_FT_FC10_$(FC10_DEV)=1 \
# -DCONFIG_FT_FDC_BASE_$(FC10_DEV)=0x180 \
# -DCONFIG_FT_FDC_DMA_$(FC10_DEV)=3 \
# -DCONFIG_FT_NR_BUFFERS=3 \
# -DCONFIG_FT_INT_$(FC10_DEV)=1
#
# Secondary floppy disk controller:
# including Ditto Dash 2Mbps controller, ExaByte accelerator card,
# CTC-2Mb (Seagate) and hopefully any 82078 based FDC controller card.
#
#82078_DEV=0
#FDC_OPT = -DCONFIG_FT_FDC_BASE_$(82078_DEV)=0x370 \
# -DCONFIG_FT_FDC_IRQ_$(82078_DEV)=6 \
# -DCONFIG_FT_FDC_DMA_$(82078_DEV)=2 \
# -DCONFIG_FT_NR_BUFFERS=3 \
# -DCONFIG_FT_INT_$(82078_DEV)=1
#
# Maybe one of the following alternatives work if you have a Ditto
# Dash and the above setting doesn't work:
#
#FDC_OPT = -DCONFIG_FT_FDC_BASE_$(82078_DEV)=0x370 \
# -DCONFIG_FT_FDC_IRQ_$(82078_DEV)=5 \
# -DCONFIG_FT_FDC_DMA_$(82078_DEV)=3 \
# -DCONFIG_FT_NR_BUFFERS=3 \
# -DCONFIG_FT_INT_$(82078_DEV)=1
#FDC_OPT = -DCONFIG_FT_FDC_BASE_$(82078_DEV)=0x370 \
# -DCONFIG_FT_FDC_IRQ_$(82078_DEV)=2 \
# -DCONFIG_FT_FDC_DMA_$(82078_DEV)=3 \
# -DCONFIG_FT_NR_BUFFERS=3 \
# -DCONFIG_FT_INT_$(82078_DEV)=1
#
# For a HP Colorado Trakker parallel port drive, try
#
#TRAKKER_DEV=0
#FDC_OPT += -DCONFIG_FT_FDC_PARPORT_$(TRAKKER_DEV)=-1 \
# -DCONFIG_FT_PAR_$(TRAKKER_DEV)=1 \
# -DCONFIG_FT_TRAKKER_$(TRAKKER_DEV)=1
#
# For a Micro Solutions opispo "backpack" based parallel port drive, try
#
#BPCK_DEV=0
#FDC_OPT += -DCONFIG_FT_FDC_PARPORT_$(BPCK_DEV)=-1 \
# -DCONFIG_FT_PAR_$(BPCK_DEV)=1 \
# -DCONFIG_FT_BPCK_$(BPCK_DEV)=1
#
#
#
#
##################################################
#############################
 
Old 12-07-2002, 11:25 AM   #3
poldervaart
LQ Newbie
 
Registered: Dec 2002
Distribution: RH 8.0 (Psyche)
Posts: 9

Original Poster
Rep: Reputation: 0
I really hate to reply to myself, but in this case, I noticed something in the last make output that might raise some questions. For some reason there was some tie in to my .Trash folder. I went and deleted everything having to do with ftape in the trash, and tried it again. Here is what I got. No errors until the end.

$ make
for i in ftape ; do make -C $i all ; done
make[1]: Entering directory `/home/chris/ftape-4.04/ftape'
> ../include/linux/modftversions.h
for i in lowlevel internal parport zftape compressor; \
do \
make -C $i NODEP=true versions; \
done
make[2]: Entering directory `/home/chris/ftape-4.04/ftape/lowlevel'
rm -f ../../include/linux/modules/ftape_syms.ver.tmp; gcc -D__KERNEL__ -I. -I../../include -I/usr/src/linux-2.4.18-18.8.0/include -E -D__GENKSYMS__ ftape_syms.c | /sbin/genksyms ../../include/linux/modules 2> /dev/null; rm -f ../../include/linux/modules/ftape_syms.ver.tmp
make[2]: *** [../../include/linux/modules/ftape_syms.ver] Error 1
make[2]: Leaving directory `/home/chris/ftape-4.04/ftape/lowlevel'
make[2]: Entering directory `/home/chris/ftape-4.04/ftape/internal'
make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/home/chris/ftape-4.04/ftape/internal'
make[2]: Entering directory `/home/chris/ftape-4.04/ftape/parport'
make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/home/chris/ftape-4.04/ftape/parport'
make[2]: Entering directory `/home/chris/ftape-4.04/ftape/zftape'
rm -f ../../include/linux/modules/zftape_syms.ver.tmp; gcc -D__KERNEL__ -I. -I../../include -I/usr/src/linux-2.4.18-18.8.0/include -E -D__GENKSYMS__ zftape_syms.c | /sbin/genksyms ../../include/linux/modules 2> /dev/null; rm -f ../../include/linux/modules/zftape_syms.ver.tmp
make[2]: *** [../../include/linux/modules/zftape_syms.ver] Error 1
make[2]: Leaving directory `/home/chris/ftape-4.04/ftape/zftape'
make[2]: Entering directory `/home/chris/ftape-4.04/ftape/compressor'
make[2]: Nothing to be done for `versions'.
make[2]: Leaving directory `/home/chris/ftape-4.04/ftape/compressor'
set -e; for i in lowlevel internal parport zftape compressor; do make -C $i modules; done
make[2]: Entering directory `/home/chris/ftape-4.04/ftape/lowlevel'
rm -f ../../include/linux/modules/ftape_syms.ver.tmp; gcc -D__KERNEL__ -I. -I../../include -I/usr/src/linux-2.4.18-18.8.0/include -E -D__GENKSYMS__ ftape_syms.c | /sbin/genksyms ../../include/linux/modules 2> /dev/null; rm -f ../../include/linux/modules/ftape_syms.ver.tmp
make[2]: *** [../../include/linux/modules/ftape_syms.ver] Error 1
make[2]: Leaving directory `/home/chris/ftape-4.04/ftape/lowlevel'
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/home/chris/ftape-4.04/ftape'
make: *** [all] Error 2
 
  


Reply



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
ftape with 2.6.8-2-686 kernel RRolleston Debian 2 11-13-2005 09:45 PM
ftape and windows archive m_yates Linux - Software 0 05-07-2004 08:22 AM
Installing ftape RPM gw1500se Mandriva 2 03-28-2004 05:36 PM
ftape problems frieza Linux - Hardware 0 02-18-2004 11:51 AM
ftape how do i use it monkeymartin Slackware 2 05-20-2003 01:27 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 06:18 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