Linux-Hardware Digest #389, Volume #14 Fri, 23 Feb 01 17:13:09 EST
Contents:
Re: Help: OnStream Echo 30 SCSI External (Michael Meissner)
Re: NetGear FA310TX ("myself")
Re: NetGear FA310TX ("Monte Milanuk")
Re: Sound module or kernal? ("Peter T. Breuer")
SCSI IDE RAID Advices needed ("sancelot")
Re: Tweaking BIOS for no keyboard? (M. Buchenrieder)
Hewlett-Packard CD-Writer Plus 9300, which is an IDE device, and (Jeff Silverman)
Problem with Serial port if X is running (Sergey Gribov)
Re: Sound module or kernal? (Justin Moe)
----------------------------------------------------------------------------
Subject: Re: Help: OnStream Echo 30 SCSI External
From: Michael Meissner <[EMAIL PROTECTED]>
Date: 23 Feb 2001 15:40:44 -0500
Nicolas Neveur <[EMAIL PROTECTED]> writes:
> Hello to everyone,
> Anybody can give me tips or better to make work tape backup unit from
> OnStream model Echo 30 SCSI External
> There is no driver for it from the compagnie !!! not yet !!!
There is a configuration option for some models of the OnStream tape drives in
the 2.4.2 kernel. Obviously to run this, you will have to update to the 2.4
kernel, which may involve upgrading lots of other system utilities.
Here is the configuration help for the option:
OnStream SC-x0 SCSI tape support
CONFIG_CHR_DEV_OSST
The OnStream SC-x0 SCSI tape drives can not be driven by the
standard st driver, but instead need this special osst driver and
use the /dev/osstX char device nodes (major 206).
Via usb-storage and ide-scsi, you may be able to drive the USB-x0
and DI-x0 drives as well. Note that there is also a second generation
of OnStream tape drives (ADR-x0) that supports the standard SCSI-2
commands for tapes (QIC-157) and can be driven by the standard
driver st.
For more information, you may have a look at the SCSI-HOWTO
ftp://metalab.unc.edu/pub/Linux/docs/HOWTO and
drivers/scsi/README.osst in the kernel source.
More info on the OnStream driver may be found on
http://linux1.onstream.nl/test/
Please also have a look at the standard st docu, as most of it
applies to osst as well.
This driver is also available as a module ( = code which can be
inserted in and removed from the running kernel whenever you want).
The module will be called osst.o. If you want to compile it as a
module, say M here and read Documentation/modules.txt and
Documentation/scsi.txt .
and here is the contents of drivers/scsi/README.osst:
README file for the osst driver
===============================
(w) Kurt Garloff <[EMAIL PROTECTED]> 12/2000
This file describes the osst driver as of version 0.8.x/0.9.x, the released
version of the osst driver.
It is intended to help advanced users to understand the role of osst and to
get them started using (and maybe debugging) it.
It won't address issues like "How do I compile a kernel?" or "How do I load
a module?", as these are too basic.
Once the OnStream got merged into the official kernel, the distro makers
will provide the OnStream support for those who are not familiar with
hacking their kernels.
Purpose
=======
The osst driver was developed, because the standard SCSI tape driver in
Linux, st, does not support the OnStream SC-x0 SCSI tape. The st is not to
blame for that, as the OnStream tape drives do not support the standard SCSI
command set for Serial Access Storage Devices (SASDs), which basically
corresponds to the QIC-157 spec.
Nevertheless, the OnStream tapes are nice pieces of hardware and therefore
the osst driver has been written to make these tape devs supported by Linux.
The driver is free software. It's released under the GNU GPL and planned to
be integrated into the mainstream kernel.
Implementation
==============
The osst is a new high-level SCSI driver, just like st, sr, sd and sg. It
can be compiled into the kernel or loaded as a module.
As it represents a new device, it got assigned a new device node: /dev/osstX
are character devices with major no 206 and minor numbers like the /dev/stX
devices. If those are not present, you may create them by calling
Makedevs.sh as root (see below).
The driver started being a copy of st and as such, the osst devices'
behavior looks very much the same as st to the userspace applications.
History
=======
In the first place, osst shared it's identity very much with st. That meant
that it used the same kernel structures and the same device node as st.
So you could only have either of them being present in the kernel. This has
been fixed by registering an own device, now.
st and osst can coexist, each only accessing the devices it can support by
themselves.
Installation
============
osst got integrated into the linux kernel. Select it during kernel
configuration as module or compile statically into the kernel.
Compile your kernel and install the modules.
Now, your osst driver is inside the kernel or available as a module,
depending on your choice during kernel config. You may still need to create
the device nodes by calling the Makedevs.sh script (see below) manually,
unless you use a devfs kernel, where this won't be needed.
To load your module, you may use the command
modprobe osst
as root. dmesg should show you, whether your OnStream tapes have been
recognized.
If you want to have the module autoloaded on access to /dev/osst, you may
add something like
alias char-major-206 osst
to your /etc/modules.conf (old name: conf.modules).
You may find it convenient to create a symbolic link
ln -s nosst0 /dev/tape
to make programs assuming a default name of /dev/tape more convenient to
use.
The device nodes for osst have to be created. Use the Makedevs.sh script
attached to this file.
Using it
========
You may use the OnStream tape driver with your standard backup software,
which may be tar, cpio, amanda, arkeia, BRU, Lone Tar, ...
by specifying /dev/(n)osst0 as the tape device to use or using the above
symlink trick. The IOCTLs to control tape operation are also mostly
supported and you may try the mt (or mt_st) program to jump between
filemarks, eject the tape, ...
There's one limitation: You need to use a block size of 32kB.
(This limitation is worked on and will be fixed in version 0.8.8 of
this driver.)
If you just want to get started with standard software, here is an example
for creating and restoring a full backup:
# Backup
tar cvf - / --exclude /proc | buffer -s 32k -m 24M -B -t -o /dev/nosst0
# Restore
buffer -s 32k -m 8M -B -t -i /dev/osst0 | tar xvf - -C /
The buffer command has been used to buffer the data before it goes to the
tape (or the file system) in order to smooth out the data stream and prevent
the tape from needing to stop and rewind. The OnStream does have an internal
buffer and a variable speed which help this, but especially on writing, the
buffering still proves useful in most cases. It also pads the data to
guarantees the block size of 32k. (Otherwise you may pass the -b64 option to
tar.)
Expect something like 1.8MB/s for the SC-x0 drives and 0.9MB/s for the DI-30.
The USB drive will give you about 0.7MB/s.
On a fast machine, you may profit from software data compression (z flag for
tar).
USB and IDE
===========
Via the SCSI emulation layers usb-storage and ide-scsi, you can also use the
osst driver to drive the USB-30 and the DI-30 drives. (Unfortunately, there
is no such layer for the parallel port, otherwise the DP-30 would work as
well.) For the USB support, you need the latest 2.4.0-test kernels and the
latest usb-storage driver from
http://www.linux-usb.org/
http://sourceforge.net/cvs/?group_id=3581
Note that the ide-tape driver as of 1.16f uses a slightly outdated on-tape
format and therefore is not completely interoperable with osst tapes.
The ADR-x0 line is fully SCSI-2 compliant and is supported by st, not osst.
The on-tape format is supposed to be compatible with the one used by osst.
Feedback and updates
====================
The driver development is coordinated through a mailing list
<[EMAIL PROTECTED]>
a CVS repository and some web pages.
The tester's pages which contain recent news and updated drivers to download
can be found on
http://linux1.onstream.nl/test/
If you find any problems, please have a look at the tester's page in order
to see whether the problem is already known and solved. Otherwise, please
report it to the mailing list. Your feedback is welcome. (This holds also
for reports of successful usage, of course.)
In case of trouble, please do always provide the following info:
* driver and kernel version used (see syslog)
* driver messages (syslog)
* SCSI config and OnStream Firmware (/proc/scsi/scsi)
* description of error. Is it reproducible?
* software and commands used
You may subscribe to the mailing list, BTW, it's a majordomo list.
Status
======
0.8.0 was the first widespread BETA release. Since then a lot of reports
have been sent, but mostly reported success or only minor trouble.
All the issues have been addressed.
Check the web pages for more info about the current developments.
0.9.x is the tree for the 2.3/2.4 kernel.
Acknowledgments
================
The driver has been started by making a copy of Kai Makisara's st driver.
Most of the development has been done by Willem Riede. The presence of the
userspace program osg (onstreamsg) from Terry Hardie has been rather
helpful. The same holds for Gadi Oxman's ide-tape support for the DI-30.
I did add some patches to those drivers as well and coordinated things a
little bit.
Note that most of them did mostly spend their spare time for the creation of
this driver.
The people from OnStream, especially Jack Bombeeck did support this project
and always tried to answer HW or FW related questions. Furthermore, he
pushed the FW developers to do the right things.
SuSE did support this project by allowing me to work on it during my working
time for them and by integrating the driver into their distro.
More people did help by sending useful comments. Sorry to those who have
been forgotten. Thanks to all the GNU/FSF and Linux developers who made this
platform such an interesting, nice and stable platform.
Thanks go to those who tested the drivers and did send useful reports. Your
help is needed!
Makedevs.sh
===========
#!/bin/sh
# Script to create OnStream SC-x0 device nodes (major 206)
# Usage: Makedevs.sh [nos [path to dev]]
# $Id: README.osst.kernel,v 1.4 2000/12/20 14:13:15 garloff Exp $
major=206
nrs=4
dir=/dev
test -z "$1" || nrs=$1
test -z "$2" || dir=$2
declare -i nr
nr=0
test -d $dir || mkdir -p $dir
while test $nr -lt $nrs; do
mknod $dir/osst$nr c $major $nr
chown 0.disk $dir/osst$nr; chmod 660 $dir/osst$nr;
mknod $dir/nosst$nr c $major $[nr+128]
chown 0.disk $dir/nosst$nr; chmod 660 $dir/nosst$nr;
mknod $dir/osst${nr}l c $major $[nr+32]
chown 0.disk $dir/osst${nr}l; chmod 660 $dir/osst${nr}l;
mknod $dir/nosst${nr}l c $major $[nr+160]
chown 0.disk $dir/nosst${nr}l; chmod 660 $dir/nosst${nr}l;
mknod $dir/osst${nr}m c $major $[nr+64]
chown 0.disk $dir/osst${nr}m; chmod 660 $dir/osst${nr}m;
mknod $dir/nosst${nr}m c $major $[nr+192]
chown 0.disk $dir/nosst${nr}m; chmod 660 $dir/nosst${nr}m;
mknod $dir/osst${nr}a c $major $[nr+96]
chown 0.disk $dir/osst${nr}a; chmod 660 $dir/osst${nr}a;
mknod $dir/nosst${nr}a c $major $[nr+224]
chown 0.disk $dir/nosst${nr}a; chmod 660 $dir/nosst${nr}a;
let nr+=1
done
--
Michael Meissner, Red Hat, Inc. (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: [EMAIL PROTECTED] phone: +1 978-486-9304
Non-work: [EMAIL PROTECTED] fax: +1 978-692-4482
------------------------------
From: "myself" <[EMAIL PROTECTED]>
Subject: Re: NetGear FA310TX
Crossposted-To: comp.os.linux.networking
Date: Fri, 23 Feb 2001 20:25:55 GMT
In article <[EMAIL PROTECTED]>, "Tim Lyth"
<[EMAIL PROTECTED]> wrote:
using LM7.2, kern 2.2.17, but should be similar- for adaptor 1 tab:
enabled, dhcp, netmask(same as in W98-winipcfg iirc), net device = eth0
(1 nic for me), module = tulip, no IRQ or I/O specified. I specified IRQ
on one of my numerous installs, and it fscked up connection. Also, look
in /etc/conf.modules (or wherever RH puts it). The only network related
entry I have reads "alias eth0 tulip". At one time I had an entry
"options tulip irq=10" & got errors till I removed entry. AFAIK netconf
writes directly to conf.modules (was modules.conf) file, among others.
The only other entries I had to make were in DNS/resolver config, again
used entries as indicated in Win. (oops, host name+domain, in previous
tab). ifdown eth0, ifup eth0, ifconfig (should now show eth0 & lo).
Lm uses dhcpcd, afaik RH uses pump? for dhcp client- necessary if have
dynamic IP (same reason I enable dhcp as above). If all this doesn't
help, check for irq conflicts- this is first install where I had to
disable pnp in bios to get everything going.
not-an-expert-and-don't-claim-to-be-but-hope-this-helps<g>
> Hi.
>
> I was wondering if anyone has successfully install a NetGear FA310TX NIC
> on a computer running Redhat 7.0 with kernel 2.2.16? If so, could you
> please tell me how as I'm having difficulties.
>
> When I type 'lsmod' the tulip module is not on the list until I load it.
> But it isn't loaded when I boot up Redhat. When I use netconf to setup
> the NIC, if I specify an IRQ or an I/O port, both of which are optional
> I get an error message saying something about insmod and the tulip.o
> (the driver for this particular card) module. However, if I don't
> specify either an IRQ or I/O port, I get an IP initialisation failure.
> In either case, I can't access the internet.
>
> Fortunately (for me), I have not disposed of Windoze which is what's
> allowing me to write the post.
------------------------------
From: "Monte Milanuk" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: NetGear FA310TX
Date: Fri, 23 Feb 2001 14:14:23 -0700
Hmmm... I was going to say that I've used RH 7.0 w/ this card w/ no
problems, but now that I reflect on it more, I think the latest I have ever
put on a box that has a FA310TX in it is RH6.2. It loaded w/ no problems,
so I can't tell you much other than to try using either linuxconf or else as
root from a console window, type 'setup'. You may need to locate the exact
location and use the absolute path i.e. /sbin/setup or whatever it is. I
think there is a section in there for setting up networking, similar to the
text based install. Hopefully that will help some.
Monte
Tim Lyth <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> Hi.
>
> I was wondering if anyone has successfully install a NetGear FA310TX NIC
on a
> computer running Redhat 7.0 with kernel 2.2.16? If so, could you please
tell me
> how as I'm having difficulties.
>
> When I type 'lsmod' the tulip module is not on the list until I load it.
But it
> isn't loaded when I boot up Redhat.
> When I use netconf to setup the NIC, if I specify an IRQ or an I/O port,
both of
> which are optional I get an error message saying something about insmod
and the
> tulip.o (the driver for this particular card) module. However, if I don't
> specify either an IRQ or I/O port, I get an IP initialisation failure.
> In either case, I can't access the internet.
>
> Fortunately (for me), I have not disposed of Windoze which is what's
allowing me
> to write the post.
====== Posted via Newsfeeds.Com, Uncensored Usenet News ======
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
======= Over 80,000 Newsgroups = 16 Different Servers! ======
------------------------------
From: "Peter T. Breuer" <[EMAIL PROTECTED]>
Crossposted-To: alt.os.linux.slackware
Subject: Re: Sound module or kernal?
Date: Fri, 23 Feb 2001 22:03:07 +0100
In comp.os.linux.hardware Robert <[EMAIL PROTECTED]> wrote:
> I am using Slackware 7.1, win98 (sick) & Mandrake (some version) the big
> question is,
> Using a OLD sound blaster 16 non plug'n'play ISA it has a cdrom
> controler too(not used)
These are nice. I love these. I have plenty. Running mostly slackware
3.0, and some debian machines.
OSS/Free:3.8s2++-971130
Load type: Driver loaded as a module
Kernel: Linux oboe 2.2.15 #57 Sun May 21 16:16:05 MET DST 2000 i686
Config options: 0
Installed drivers:
Card config:
Audio devices:
0: Sound Blaster 16 (4.13) (DUPLEX)
Synth devices:
Midi devices:
0: Sound Blaster 16
Timers:
0: System clock
Mixers:
0: Sound Blaster
> I can get the sound card to function using a driver built into the
> kernal but the midi dont go the boot process seems to hang arround the
> time it is trying to use an irq for the MP401.I have never had the card
> working as a module without DOS booting first then soft booting slack
> this wont work for me at the moment this is for Slack7.1
It's nothing to do with slack. Only the kernel matters, and your
configuration of it. If you want the canonical incantations, here they
are:
alias char-major-14 sb
options sb io=0x220 irq=5 dma=1 dma16=5 type=0 mpu_io=0x330
Check where your dma channels are.
Oh .. maybe this one is pnp? Lesseee ... yes it is. Shucks, I could
have sworn I remembered that machine had a pre-pnp card. I recall
diddling the irq in the driver code aeons ago.
# Card 1: (serial identifier 01 10 14 de cd 28 00 8c 0e)
# CTL0028 Serial No 269803213 [checksum 01]
# Version 1.0, Vendor version 1.0
# ANSI string -->Creative SB16 PnP<--
#
# Logical device id CTL0031
#
Peter
------------------------------
From: "sancelot" <[EMAIL PROTECTED]>
Subject: SCSI IDE RAID Advices needed
Date: Fri, 23 Feb 2001 22:12:51 +0100
Hi,
I would like to buy an IDE - SCSI raid array from zero-d
www.zero-d.com
I would like to have some people experience with this product under linux
bye
steph
------------------------------
From: [EMAIL PROTECTED] (M. Buchenrieder)
Subject: Re: Tweaking BIOS for no keyboard?
Date: Fri, 23 Feb 2001 14:28:23 GMT
"Daniel Lenski" <[EMAIL PROTECTED]> writes:
[...]
>The trouble is that the BIOS (it's Award BIOS) demands that a keyboard be
>plugged in in order to boot.
[...]
Change the BIOS setting "Halt on all errors" appropriately.
Michael
--
Michael Buchenrieder * [EMAIL PROTECTED] * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.
------------------------------
From: Jeff Silverman <[EMAIL PROTECTED]>
Subject: Hewlett-Packard CD-Writer Plus 9300, which is an IDE device, and
Date: Fri, 23 Feb 2001 13:22:32 -0800
Hi.
I have an HP CD-Writer plus 9300, which is an IDE device, and I want to
record CDs with it, using cdrecord.
So I built a new 2.2.17 kernel with ide-scsi, sg, sr, and st modules.
The drive works fine as a CD player, but cdrecord can't seem to find it.
cowiche!root 438# mount /dev/hdc /mnt/t
mount: block device /dev/hdc is write-protected, mounting read-only
cowiche!root 439# ls /mnt/t
./ chs/ esp/ isu_deu.dll* isu_nld.dll*
music/ setup.ini*
../ cht/ fra/ isu_esp.dll* isu_ptb.dll*
nld/ sve/
autorun.inf* deu/ isu_chs.dll* isu_fra.dll* isu_sve.dll* ptb/
cdlabeler/ enu/ isu_cht.dll* isu_ita.dll* ita/ setup.exe*
cowiche!root 440# umount /dev/hdc
cowiche!root 441# cdrecord -scanbus
Cdrecord 1.8 (i686-pc-linux-gnu) Copyright (C) 1995-2000 J�rg Schilling
cdrecord: No such file or directory. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you
are root.
cowiche!root 442#
cowiche!root 444# /sbin/lsmod
Module Size Used by
st 25160 0 (unused)
sg 12628 0 (unused)
sr_mod 16144 0 (unused)
ide-scsi 7400 0
emu10k1 46372 0
soundcore 2532 4 [emu10k1]
cowiche!root 445#
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
linear
default=linux
The lilo.conf file contains:
image=/boot/vmlinuz
label=linux
read-only
root=/dev/hda5
append="hdc=ide-scsi"
image=/boot/vmlinuz
label=linux-up
read-only
root=/dev/hda5
cowiche!root 446#
Anybody have any advice?
--
Jeff Silverman, sysadmin for the Research Computing Systems (RCS)
University of Washington, School of Engineering, Electrical Engineering Dept.
Box 352500, Seattle, WA, 98125-2500 FAX: (206) 221-5264 Phone (206) 543-9378
[EMAIL PROTECTED] http://rcs.ee.washington.edu/~jeffs
------------------------------
From: Sergey Gribov <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.portable
Subject: Problem with Serial port if X is running
Date: Fri, 23 Feb 2001 21:42:37 GMT
Hi,
I have Dell Inspiron 8000 with Debian linux, kernel 2.4.2.
I have the following strange problem:
If I trying to synchronize Pilot using serial port (using pilot-xfer)
without X running it's working just fine, but if I run X it failes
in the middle with timeout and 'weird packets' problem.
It seems, that serial port working fine without X and having problems
when the X is running...
Any ideas?
Thanks in advance,
------------------------------
From: [EMAIL PROTECTED] (Justin Moe)
Crossposted-To: alt.os.linux.slackware
Subject: Re: Sound module or kernal?
Date: Fri, 23 Feb 2001 21:54:47 -0000
Reply-To: [EMAIL PROTECTED]
On Sat, 24 Feb 2001 08:06:15 +1300, Robert <[EMAIL PROTECTED]> wrote:
[snip]
->Using a OLD sound blaster 16 non plug'n'play ISA it has a cdrom
->controler too(not used)
Is it a _real_ Creative SB16? I have seen a few cards that claimed to be
'SB16 Compatible'...
->I can get the sound card to function using a driver built into the
->kernal but the midi dont go the boot process seems to hang arround the
->time it is trying to use an irq for the MP401.I have never had the card
If the above is true, there is your problem. If you had looked at the
kernel config, it says right on the line that the 401 IRQ setting is not
for the SB16. Don't use it/disable it/don't load the module for it and
see if that works.
--
"How can I speak to somebody that calls themselves a sys admin
and they have to ask me what the difference between
static IP's and Dynamic IP's." - Nkosika
* Justin The Cynical - [EMAIL PROTECTED]*
------------------------------
** 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
******************************
