Linux-Hardware Digest #791, Volume #14 Fri, 18 May 01 17:13:09 EDT
Contents:
Re: PCMCIA / PS2 IRQ12 Conflict (2.4 kernel) ("David Hawkins")
Case badges with your own logo from under $0.50 each (SecurisysAgency)
Selecting from the crop of DSL hub/switch/firewall units (Harry Putnam)
IRQ conflict-- CMD 646 IDE and ESS Maestro 2E (Nicholas Weininger)
Re: Screen Size problem on Sony LCD screen (Kwan Lowe)
Re: yes, 2 SGI 1600sw LCD panels DO work in linux in dualhead mode! (The Linux
AntiChrist)
USB problem ("Linux Guerilla")
Re: Anyone selling basic cheap Linux boxes? (Kwan Lowe)
G400 + XFree 4.0 (Sebastian Bossung)
Re: G400 + XFree 4.0 ("Peter Riggs")
gravis stinger ("Chris Schadl")
USB problem ("Linux Guerilla")
Re: More Info - Problems with Adaptec 2930CU w/ BRU and SEAGATE Travan in RH6.2
(William N Moore)
----------------------------------------------------------------------------
From: "David Hawkins" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.portable,comp.os.linux.setup,alt.os.linux
Subject: Re: PCMCIA / PS2 IRQ12 Conflict (2.4 kernel)
Date: Fri, 18 May 2001 10:12:43 -0700
Thanks Len!
This works great. I really needed to have access to my serial
port, so this helps me a lot.
Where did you get info on the lilo boot parameter? I
had looked at 'man bootparam' and 'man lilo' and couldn't see how
to mask off the interrupts - I had assumed that this
should be possible, but couldn't work out how.
I had a look at the bug report in Bugzilla - interesting
discussion. Is the problem still there in 2.4.4?
Since you appear to have a similar machine, perhaps
you could tell me how you got the sound to work. Its
not really a high priority for me, so I gave up
when it didn't work initially. I suspect the OSS
sound drivers might work, and I did read some
info in the Documentation directory, but haven't
had a chance to play with it again. Perhaps you can
save me some time.
Again, this is great.
Thanks so much!
Dave Hawkins
Caltech.
"Leonard Evens" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> David Hawkins wrote:
> >
> > Thanks Clark,
> >
> > I'm not quite sure the problem is 100% related to the Yenta
> > driver though. Any idea why the mouse won't work if I uninstall
> > the PCMCIA drivers? If you stop the PCMCIA services, then
> > the interrupt is released. .... of course I haven't tried removing
> > the service on boot though.
> >
> > Thanks for the comments.
> >
> > Dave
> >
> > "clark tompsett" <[EMAIL PROTECTED]> wrote in message
> > news:[EMAIL PROTECTED]...
> > > I have posted a bug report with Redhat. I have a Winbook XL also.
The
> > > problem appears to be bios related. The 2.4.2 kernel used Yenta for
the
> > > socket driver and it looks at the bios and claims irq12. The only
> > > solution I have at present is to install RH7.1 and replace the kernel
and
> > > pcmcia back to 2.2.19. I don't know if this will be solved.
> > >
> > > Clark
> > >
> > > In article <9dffj7$[EMAIL PROTECTED]>, "David Hawkins"
> > > <[EMAIL PROTECTED]> wrote:
> > >
> > > > Hi,
> > > >
> > > > I'd like some suggestions as to the cause and fix of a problem I am
> > > > having with Linux 2.4 freezing up on me. My system is
> > > >
> > > > - Winbook XL
> > > > - Red Hat 7.1 (2.4.2-2 kernel)
> > > >
> > > > The mouse is a PS/2 device (the Winbook has a keyboard 'nipple' and
> > > > touchpad), and this is what Win95 sees it as. When installing RH, it
> > > > didn't recognize the mouse, so I used the text install. On first
boot,
> > > > the mouse was recognized by the hardware detection and assigned as a
> > > > generic ps/2 mouse. The first time I booted into X, the system
froze.
> > > >
> > > > Booting next time and staying in text mode, I tried gpm and mev, the
> > > > laptop froze both times. (/dev/mouse -> /dev/psaux so thats ok)
> > > >
> > > > Looking under /proc/interrupts I see that the PS/2 interrupt is
being
> > > > shared with the TI PCI1131 PCMCIA cardbus controller. Several
documents
> > > > indicate the the PS/2 must use IRQ12, so the 1131 IRQ may need to be
> > > > changed. However, looking at /etc/pcmcia/config.opts lists IRQ12 as
> > > > being excluded - so how come the controller claimed it? (perhaps the
> > > > exclude only applies to devices in the PCMCIA slots...?). Under
Win95
> > > > the 1131 uses IRQ15.
> > > >
> > > > Thinking that maybe the interrupts from the TI1131 were the cause of
the
> > > > problem I performed:
> > > >
> > > > /etc/init.d/pcmcia stop
> > > >
> > > > This removed PCMCIA services and /proc/interrupts shows only the
PS/2
> > > > mouse on IRQ12. However, booting into X still freezes and so does
mev.
> > > > Actually, I just ran mev (with PCMCIA services off), and could type
> > > > text, however, as soon as I touched the mouse, the system freezes.
> > > >
> > > > This system has had RH 6.2 working fine in the past, and booting
into
> > > > Win95 shows all is well there.
> > > >
> > > > dmesg and /var/log/messages don't contain any interesting info on
why
> > > > the system may be crashing. Although there is the comment that the
> > > > serial driver is 5.02 and that SHARE_IRQ is enabled.
> > > >
> > > > I deleted /etc/sysconfig/mouse and ran mouseconfig ... and receved a
> > > > segmentation fault while probing for the mouse, and then the system
was
> > > > frozen. Hmmm, is there a bug here? (or perhaps the missing file is
the
> > > > cause of that) I had to run 'mouseconfig --noprobe' to regenerate
the
> > > > /etc/sysconfig/mouse file. I selected the Generic PS/2 mouse, as
that
> > > > looked to be the only correct one. I did try the Microsoft
Intellimouse
> > > > (PS/2), however when the system was booted, I no longer had use of
the
> > > > keyboard and had to use the boot CD to rescue the system.
> > > >
> > > > Anyway, some suggestions would be helpful. If no one can think of a
> > > > cause for this problem, then I'll have a look at compiling a newer
> > > > version of the kernel.
> > > >
> > > > Please HELP!
> > > >
> > > > Regards,
> > > > Dave Hawkins
> > > > Caltech
> > > > [EMAIL PROTECTED]
> > > >
> > > >
> > > >
>
> I also encountered this problem. Go to the RedHat web site and
> see Bugzilla bug report number 37812. The problem definitely
> is from the kernel module yenta_socket. The point you raise
> about stopping pcmcia turns out to be confusing. If you
> never start pcmcia, the Texas Instruments pcmcia controller
> will not be using irq 12. But once you start it, even if
> you stop it afterwards, it keeps the interrupt at the hardware
> level. To see that, try lspci -vv both before and after running
> pcmcia.
>
> We managed to come up with two workarounds. The one I prefer
> is to pass the following to the kernel
> pci=irqmask=0xafff
> You can do this at the lilo prompt with
> linux pci=irqmask=0xafff
> or you can add to the linux image section in /etc/lilo.conf
> append="pci=irqmask=0xafff"
> and then rerun lilo.
>
> What this does is exclude irqs 12 and 14 from the list of irqs
> that pci devices can use. Then when you run pcmcia, it will
> take irq 15.
>
> In the bugzilla discussion there is also another method which
> requires changing the penalties for different irqs in
> a certain file in the kernel source and then making a new
> kernel or perhaps just new modules, I'm not sure which.
>
> This problem, by the way, does not arise in Windows 98,
> nor did it in RH 5.1 through 7.0. The difference for the
> RH7.1 is that the code was rewritten to incorporate the support
> in the kernel whereas previous it was standalone.
>
> --
>
> Leonard Evens [EMAIL PROTECTED] 847-491-5537
> Dept. of Mathematics, Northwestern Univ., Evanston, IL 60208
------------------------------
Subject: Case badges with your own logo from under $0.50 each
From: SecurisysAgency <[EMAIL PROTECTED]>
Date: Fri, 18 May 2001 17:45:28 GMT
Computer case badges with 3D effect with your own logo. Order securely
Online for FAST delivery:
http://www.securisysagency.com/shop/shop.html
We are offering quality custom PC badges printed your own design or choose
from our range of "off-shelf" labels, tamper-proof warranty labels, domed
labels, Linux, BSD badges and merchandize.
Online ordering. Stock orders are normally despatched within 48-hours to
anywhere in the world.
FREE shipping to anywhere in the world!
www.securisysagency.com
Disclaimer:
This posting is made in understanding that this newsgroup allowes
advertising material.
If you are a moderator of the channel and you believe that posting of this
nature doesn't comply with the one of the channel, please write to:
[EMAIL PROTECTED] and subsequent postings will stop.
------------------------------
From: Harry Putnam <[EMAIL PROTECTED]>
Subject: Selecting from the crop of DSL hub/switch/firewall units
Date: 18 May 2001 08:45:26 -0700
Group,
I'm looking for advice on selecting from the large number of
DSL router/switch/hub/firewall things that are coming out now.
Hoping some of you will have personal experience with some of them.
My setup: Home operation, with 3-4 machines. Currently
Masquerading/firewalling the lot with my personal Linux box (RH 7.1).
OS's range from FreeBSD-4.3 Redhat Linux, win2000 and win98.
I want to put one of the new DSL router/switch things in front and
have all machines independantly connected to it.
Currently I firewall with ipchains (Not using the iptables capability
as yet). And have worked out a fairly comprehensive firewall for a
home setup.
Some of the new DSL router/switch/firewall hardware advertises as
having `Sophisticated' firewall capability, maintained thru choice
of net browser. I also understand some of these hardware packages are
running some kind tailored linux. Those would be most interesting.
I guess my needs could be described briefly as:
1) DSL capable
2) Serious (for home use) programmable firewall protection
3) Capable of routing/hubbing up to 5 machines
4) Low profile, small and quiet.
5) Maximum price of $350
------------------------------
From: Nicholas Weininger <[EMAIL PROTECTED]>
Subject: IRQ conflict-- CMD 646 IDE and ESS Maestro 2E
Date: Fri, 18 May 2001 14:04:46 -0400
Hi,
I've got an HP OmniBook 900B running Debian potato 2.2r3, kernel 2.2.19.
My machine has an ESS Maestro 2E sound chip (in the notebook itself) and
a CMD 646 secondary IDE controller (in the docking station). They both,
by default, use IRQ 10. This causes no problems in Windows NT 4.0, where
they appear to coexist peacefully on that IRQ. However, under Linux, if
I include the Maestro driver in the kernel then the system refuses to
initialize the CD-R attached to the IDE controller-- at boot time, after
several minutes' pause, it says something to the effect of "drive not
responding, code 0xd1". If I build the Maestro driver as a module, then
the drive is detected properly, but insmod fails with:
maestro: unable to allocate irq 10,
maestro: no devices found.
I've tried including or excluding the "experimental" CMD646 kernel
driver, with no effect.
According to the Maestro driver author, the Maestro should be able to
share an IRQ properly. So my questions are:
-- is there some known bug/feature that would cause the IDE controller
driver not to share the IRQ properly with the sound driver?
-- is there any way to get either the sound card or the IDE controller
to use a different IRQ (the BIOS doesn't seem to have it in the options
list)?
-- is there a reasonable chance that upgrading to kernel 2.4.x will fix
this problem?
Thanks,
Nick Weininger
[EMAIL PROTECTED]
------------------------------
From: Kwan Lowe <[EMAIL PROTECTED]>
Subject: Re: Screen Size problem on Sony LCD screen
Crossposted-To: uk.comp.os.linux
Date: Fri, 18 May 2001 18:06:37 GMT
In comp.os.linux.hardware Lea Anthony <[EMAIL PROTECTED]> wrote:
> Hi,
> I have a Vaio FX101 and it would seem that the maximum res it'll display
> under linux is 1024x768, it will go upto 1400x<whatever> under windows.
> If I change XF86Config-4 to go higher it crashes.
What do you mean by crashes? Does the machine actually lock up or does it just
give errors about "No screens found" or similar?
> Another thing, when I go to console or a different mode, instead of the
> mode changing to fill the screen area, it uses a small section in the
> center of the screen. Is that normal laptop behaviour (this is my
> first)?
You need to setup the framebuffer console to use more of the screen real estate.
Try adding a vga=791 line to your /etc/lilo.conf. I don't remember the modes
off the top, but check out the documentation in the kernel sources under
./Documentation/fb.
> Thanks,
> -Lea.
------------------------------
From: The Linux AntiChrist <[EMAIL PROTECTED]>
Crossposted-To: comp.sys.sgi.graphics,comp.os.linux.x
Subject: Re: yes, 2 SGI 1600sw LCD panels DO work in linux in dualhead mode!
Date: 18 May 2001 18:17:52 GMT
you think the freeloading linux kiddies understand this? of course not.
just wasted breath explaining rocket science to monkeys.
cheers.
In comp.sys.sgi.graphics Jon Leech <[EMAIL PROTECTED]> wrote:
> In article <[EMAIL PROTECTED]>,
> Bryan <[EMAIL PROTECTED]> wrote:
>>just got my 2nd 1600sw lcd display, and with the help of the author of
>>the xfree86 driver, I got both working in xinerama mode (single
>>logical display, 3200x1024).
>>
>>the key is to use both agp and a pci cards, both from #9. too bad
>>that company is out of business - I sure hope I never need service on
>>those cards...
>>
>>but at any rate, I'm a happy camper with 2 of these displays on one pc
>>system. its quite amazing to be able to drag a window opaquely across
>>from one screen to another; I've been doing that for a while on a pair
>>of CRTs and matrox cards, but this is my first time with a pair of
>>pure digital lcd's. all I can say is ... wow!
>>
>>since I was never able to get a confirmation from anyone in SGI (hmmm...)
>>that this will, in fact, work; I figured I'd post here and go on record
>>saying that it DOES work, if you are so inclined to buy and try this.
>>
>>(now, if the brightness/contrast utility would only exist in opensource for
>>linux... still not sure why SGI is keeping this proprietary; especially on
>>monitors they're discontinuing. harumph!)
> I can't speak specifically to "why" on this issue, but here are a
> couple of likely reasons (note that I am not trying to argue a point - I
> have nothing to do with the flat panels, and no influence over or
> visibility into their engineering/product team. I am simply trying to
> provide some context from my own experiences that may help you
> understand why desirable things may not happen):
> First, it takes many lawyer and management cycles to open source
> code, or release corporate IP. Lawyers and managers are typically
> overburdened with things that directly affect revenue generation;
> products that are on the way out are unlikely to generate further
> revenue.
> Second, there is often IP owned by *other* companies involved in
> products, and sorting out which IP can safely be released, and which
> can't, takes both engineering and legal cycles. See above re revenue
> issues.
> Third, even identifying the IP and getting it into releasable form
> usually takes considerable engineering effort. See above re revenue
> issues...
> The bottom line is that there are very real, bottom-line costs
> associated with doing this sort of stuff, at a time when SGI is fighting
> hard to turn a profit. We have been generous to the open source and
> Linux communities, but it's just not realistic to expect all the details
> of old products to become available.
> Jon
------------------------------
From: "Linux Guerilla" <[EMAIL PROTECTED]>
Subject: USB problem
Date: Fri, 18 May 2001 18:19:28 GMT
I just upgraded me y kernel so I'm runing Redhat 7.1, 2.4.4-XFS. I had no
problem using my USB mouse ns Wacom tablet when I was running 2.4.2-XFS
kernel. During the boot-up phase it sees both of my USB devices including my
Setiek Flying stick. But they are not usuable. I notice one diffrerence with
the 2.4.2-XFS kernel during boot-up it Mounted the USB filesystem. But my
new Kernel Settings it don't. Where do I enable USB filesystem mounting or
how do I set the USB devices to work.
guerilla
------------------------------
From: Kwan Lowe <[EMAIL PROTECTED]>
Subject: Re: Anyone selling basic cheap Linux boxes?
Date: Fri, 18 May 2001 18:20:45 GMT
the softrat <[EMAIL PROTECTED]> wrote:
> Please drop me a line if you are.
I recently put together a cheap Microstar machine with the following:
AMD Duron 750 w/MicroStar MB (integrated video, sound, USB) - $150 (local vendor)
128 Meg PC/133 $55 (local vendor, same prices on Ebay)
Case - 300W, ATX, 3 full height bays $40 (cheaper locally, but less rugged)
Maxtor 30G HD - $100 (CompUSA)
Creative 52X CDROM - $40 (local vendor)
Floppy $20 (new in box, local vendor)
Sound card $25 (Creative PCI)
I added the sound card because I was unable to get the built in AC97 sound to
work correctly. The built in video works fine, but is not appropriate for games
or anything video intensive. Everything works otherwise. All prices include the
6.5% Florida tax.
> --
> the softrat
> mailto:[EMAIL PROTECTED]
> ---
> (A Funny Line)
------------------------------
From: Sebastian Bossung <[EMAIL PROTECTED]>
Subject: G400 + XFree 4.0
Date: Fri, 18 May 2001 20:24:35 +0200
Hi,
does anybody have a Matrox G400 card working with XFree 4.0.x? I am
thinking about buying the card, but know some people who have a major pain
with it (especially too high frequencies).
Sebastian
------------------------------
From: "Peter Riggs" <[EMAIL PROTECTED]>
Subject: Re: G400 + XFree 4.0
Date: Fri, 18 May 2001 19:01:13 GMT
In article <9e3pe4$2ko$06$[EMAIL PROTECTED]>, "Sebastian Bossung"
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> does anybody have a Matrox G400 card working with XFree 4.0.x? I am
> thinking about buying the card, but know some people who have a major
> pain with it (especially too high frequencies).
>
> Sebastian
I have a Matrox G400 (16Mbyte) card and XFree 4.0.3 (Mandrake 8.0) running
on this system at 1600x1200 resolution. It is rock steady and has been
all through past upgrades (3.3.5 - 4.0.1 - 4.0.3). I don't know why you
say people have a major pain with it, I have always gone for Matrox cards
because of the lack of pain.
Regards,
Peter.
------------------------------
From: "Chris Schadl" <[EMAIL PROTECTED]>
Subject: gravis stinger
Date: Fri, 18 May 2001 15:00:34 -0500
Apperently as of kernel 2.4.3-ac3, there is now support for the gravis
stinger serial gamepad. I've complied support for it as a module under
2.4.4, however while I am able to load the module without any problems,
programs which try to use the joystick report that /dev/js0 does not
exist. As far as I know, /dev/js0 does exist, as a symlink to
/dev/input/js0. Since the gamepad connects to the serial port, is there
anything special that I need to do to get it running?
------------------------------
From: "Linux Guerilla" <[EMAIL PROTECTED]>
Subject: USB problem
Date: Fri, 18 May 2001 20:17:52 GMT
I just upgraded me y kernel so I'm runing Redhat 7.1, 2.4.4-XFS. I had no
problem using my USB mouse ns Wacom tablet when I was running 2.4.2-XFS
kernel. During the boot-up phase it sees both of my USB devices including my
Setiek Flying stick. But they are not usuable. I notice one diffrerence with
the 2.4.2-XFS kernel during boot-up it Mounted the USB filesystem. But my
new Kernel Settings it don't. Where do I enable USB filesystem mounting or
how do I set the USB devices to work.
guerilla
------------------------------
Subject: Re: More Info - Problems with Adaptec 2930CU w/ BRU and SEAGATE Travan in
RH6.2
From: [EMAIL PROTECTED] (William N Moore)
Date: Fri, 18 May 2001 20:38:58 GMT
Ok, I went through everything I remember pulling off the server when these
errors occurred. Since we haven't run the backup in a while. We were
researching online and such for some answers first. Here is everything I
can dig up, and hopefully it will answer your questions. Since we are
baffled.
Here's the info:
SCSI IDs, Other devices:
>From /proc/scsi/scsi
>Attached devices:
>Host: scsi0 Channel: 00 Id: 04 Lun: 00
> Vendor: Seagate Model: STT20000N Rev: 7A51
> Type: Sequential-Access ANSI SCSI revision: 02
>Host: scsi1 Channel: 00 Id: 00 Lun: 00
> Vendor: QUANTUM Model: ATLAS V 9 WLS Rev: 0201
> Type: Direct-Access ANSI SCSI revision: 03
So the tape drive is on ID 4
The hard drive is on 0 is seems. Maybe that's not such a good idea?
I think we'd have to check the motherboard manual to find out about what
ID it is or can be.
In /proc/scsi/aic7xxx these is
>total 0
> 0 -rw-r--r-- 1 root root 0 May 18 15:04 0
> 0 -rw-r--r-- 1 root root 0 May 18 15:04 1
>
Length of cable - I'd guess it was a run of the mill cable, 18 to 24"
maybe.
dmesg capture 1
>st0: Error with sense data: Info fld=0xa3, Current st09:00: sense key
>Hardware Error
>st0: Error with sense data: [valid=0] Info fld=0x0, Current st09:00: sense
>key Hardware Error
>st0: Error on write filemark.
>scsi : aborting command due to timeout : pid 13079942, scsi0, channel 0,
>id 4, lun 0 Rezero Unit 00 00 00 00 00
>SCSI host 0 abort (pid 13079942) timed out - resetting
>SCSI bus is being reset for host 0 channel 0.
>(scsi0:0:4:0) Synchronous at 10.0 Mbyte/sec, offset 15.
>st0: Error with sense data: [valid=0] Info fld=0x0, Current st09:00: sense
>key Unit Attention
>Additional sense indicates Power on, reset, or bus device reset occurred
dmesg capture 2
>st0: Error with sense data: Info fld=0xc82, Current st09:00: sense key
>Medium Error
>Additional sense indicates Write error
>st0: Error with sense data: [valid=0] Info fld=0x0, Current st09:00: sense
>key Medium Error
>Additional sense indicates Write error
>st0: Error on write filemark.
The two dmesg captures where done at different times, I not totally sure
from when though.
mt -f /dev/st0 status
>SCSI 2 tape drive:
>File number=0, block number=0, partition=0.
>Tape block size 512 bytes. Density code 0x47 (unknown to this mt).
>Soft error count since last status=0
>General status bits on (41010000):
> BOT ONLINE IM_REP_EN
Ran the status today, but it's the same as what I save off before.
BRU errors 1
>From BRUEXECLOG:
>
> Loading tape into drive
> 20001108 17:35:20|11433|root|[L163] START (r 15.1.1.1.26), CMD = 'bru
>-cvAGVX -L
> IntranetFullBackup-Wednesday -f /dev/st0 /'
> 20001108 17:35:36|11433|root|[L167] device = /dev/st0, buffer = 32K
>bytes, media
> size = 9765600K bytes, archive id = 3a09d5282ca9, (Op)
> 20001108 17:35:59|11433|root|[W067] warning - media write protected or
>wrong density
> 20001108 17:35:59|11433|root|[E154] error - timed out trying to write
> 20001108 17:35:59|11433|root|[L165] FINISH - 1 warnings, 1 errors, exit
>code = 2
BRU errors 2
>Loading tape into drive
>20001113 17:09:38|25548|root|[L163] START (r 15.1.1.1.26), CMD = 'bru
>-cvAGVX -L IntranetFullBackup-Monday -f /dev/st0 /'
>20001113 17:10:10|25548|root|[L167] device = /dev/st0, buffer = 32K bytes,
>media size = <unknown>, archive id = 3a1066a263cc, (Op)
>20001113 17:14:01|25548|root|[W109] warning - assuming end of volume 1
>(unknown size)
>20001113 17:14:01|25548|root|[L182] wrote 90240 blocks (180480 KBytes) on
>volume [1], 0:03:51, 781 Kb/sec
>20001113 17:14:14|25548|root|[W003] "/dev/st0": warning - close error on
>archive: errno = 5, Input/output error
>20001113 17:14:14|25548|root|[W131] warning - archive device may need
>"ignoreclose" flag set in brutab entry
>20001113 17:19:50|25548|root|[E157] error - received terminate signal
>(SIGTERM)
>20001113 17:19:50|25548|root|[L165] FINISH - 3 warnings, 1 errors, exit
>code = 2
I edited these a little to take out some identifying information.
Termination - active or not. Honestly I'm not sure. I think I would have
made sure it was terminated correctly when we put the server together.
Plus it was working for a while so I don't think it would be the
termination. We'd probably have to open things up an check.
The script is run in a Bash shell. Here's some parts of the script that
are using the tape drive. $DEV, $WHATTOBACKUP, and $LOGFILE are all
variables defined earlier in the script and they work fine.
# Load the tape if it isn't loaded
mt -f $DEV load
# Get the tape status to do checks on it
STATUS=`mt -f $DEV status`
# Erase the tape before doing the backup
mt -f $DEV erase
# If not do autoscan
bru -cvAGVX -L $VOLNAME -f $DEV $WHATBACKUP >> $LOGFILE
# if do an autoscan
bru -cvGVX -L $VOLNAME -f $DEV $WHATBACKUP >> $LOGFILE
The two BRU commands are in an 'if' statement and only one of them is run
on any given day. Also we're not doing any compression because the tapes
are bigger then the hard drive.
Hopefully this will answer your questions and help you along with us out.
If I can provide you with any other information, please let me know
Thanks,
Nick Moore
Literati Information Technology
------------------------------
** FOR YOUR REFERENCE **
The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:
Internet: [EMAIL PROTECTED]
You can send mail to the entire list by posting to comp.os.linux.hardware.
Linux may be obtained via one of these FTP sites:
ftp.funet.fi pub/Linux
tsx-11.mit.edu pub/linux
sunsite.unc.edu pub/Linux
End of Linux-Hardware Digest
******************************
