Linux-Hardware Digest #509, Volume #14 Wed, 21 Mar 01 13:13:09 EST
Contents:
PCMCIA on Thinkpad 770Z? ("Christopher Tucker")
Linux with Intel 815e chipset ([EMAIL PROTECTED])
Re: DMA 33 IDE controler can run DMA 100 Hard Disk? ("Denis")
Re: Help!!! ("cedric")
Re: Onstream S-50 (Michael Meissner)
No Sound With WinTV-PVR ("Fred Smirtz")
Re: Sound card config problems... ("Fred Smirtz")
Re: Linux with Intel 815e chipset (Patrick F Harris)
Re: TNT 2 or G-Force video card for Linux and Windows ?? (Patrick F Harris)
Ultra 160 SCSI on Redhat 5.2 (Donald Ellis)
----------------------------------------------------------------------------
From: "Christopher Tucker" <[EMAIL PROTECTED]>
Subject: PCMCIA on Thinkpad 770Z?
Date: Wed, 21 Mar 2001 11:55:00 -0000
Hi,
I am tring to get a IBM PCMCIA Turbo Token-Ring 16/4 card to work on a
Thinkpad 770Z using Redhat 7.0.
When the /etc/rc.d/init.d/pcmcia service inits I get the following in
/var/log/messages:
Mar 21 09:50:52 tp770z cardmgr[1141]: initializing socket 0
Mar 21 09:50:52 tp770z kernel: cs: memory probe 0x60000000-0x60ffffff:
clean.
Mar 21 09:50:52 tp770z cardmgr[1141]: socket 0: IBM Token Ring Adapter
Mar 21 09:50:52 tp770z cardmgr[1141]: executing: 'modprobe ibmtr_cs'
Mar 21 09:50:52 tp770z kernel: ibmtr_cs: MapMemPage: Bad offset
Mar 21 09:50:52 tp770z cardmgr[1141]: get dev info on socket 0 failed: No
such device
I have tried modifying some entries in /etc/pcmcia/config.opts, but still
have had no luck ... can anyone help ?
Thanks, Chris.
------------------------------
From: [EMAIL PROTECTED]
Subject: Linux with Intel 815e chipset
Date: Wed, 21 Mar 2001 10:20:34 -0500
Hi,
I want to build a system with Intel 815e "Solano" (82815 GMCH + 82801BA
ICH2) chipset: SUPER 370SSA motherboard with PIII processor. As far as I
understand this chipset provides built-in 2D/3D accelerated graphics and
supports OpenGL.
Does anyone has some experience whether the SUPER 370SSA works under
linux and if it does is there X-drivers for this chipset?
Thanks in advance,
Ted
------------------------------
From: "Denis" <[EMAIL PROTECTED]>
Subject: Re: DMA 33 IDE controler can run DMA 100 Hard Disk?
Date: Wed, 21 Mar 2001 13:42:18 GMT
Right
"Hun" <[EMAIL PROTECTED]> a �crit dans le message news:
[EMAIL PROTECTED]
> Thanks Denis,
>
> What is ATA 100 bus? Is it a UDMA 100 controller?
>
>
>
> On Mon, 12 Mar 2001 23:42:29 GMT, Denis <[EMAIL PROTECTED]>
wrote:
> >I plugged my ATA100 into the ATA33 controller of my K7 Asus A7V
motherboard
> >and it ran ok. At 33 speed though. (I now have it on the ATA100 bus
though
> >;-)
> >
> >Denis
> >
> >"Hun" <[EMAIL PROTECTED]> a �crit dans le message news:
> >[EMAIL PROTECTED]
> >> Hi~
> >>
> >> I got out of space yesterday while converting my music CDs to mp3
files.
> >:(
> >>
> >> I gonna buy a hard disk.
> >> I have two computers one only support UDMA 33, the other support
> >> UDMA 33/66.
> >>
> >> Can I use the UDMA 100 hard disk? Most hardware shops sell only UDMA
100
> >products.
> >>
> >>
> >>
> >>
> >
> >
------------------------------
From: "cedric" <[EMAIL PROTECTED]>
Subject: Re: Help!!!
Date: Wed, 21 Mar 2001 07:24:37 +0800
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] wrote:
> On Tue, 20 Mar 2001 11:52:22, "cedric" <[EMAIL PROTECTED]> wrote:
>
>> In article <[EMAIL PROTECTED]>,
>> [EMAIL PROTECTED] wrote:
>>
>> > On Tue, 20 Mar 2001 13:08:03, cedric <[EMAIL PROTECTED]> wrote:
>> >
>> >>
>> >> mount /dev/hdd give me an error message bad superblock or too many
>> >> files mounted.
>> >
>> > You're trying to mount the whole disk drive, not the partitions
>> > within it. Mount the correct partition and you might have some luck!
>> > Running fdisk -l /dev/hdd will list the partitions available.
>> >
>> fdisk -l /dev/hdd shows no partitions. The same with /dev/hdb. How do I
>> get them working?
>> /dev/hdb is empty but there is data on /dev/hdd that I would like to
>> try
>> and recover. All my writing is backed up on floppies, but there is gigs
>> of research material I'd like to get.
>
> If you know *exactly* where the partitions started and ended then you
> _might_ be able to recreate them. Unlike some FDISK's, Linux's doesn't
> appear to overwrite information when you delete/define partitions so
> it's possible to recover them *if* you know where they are! You might
> also look for a utility called gpart (I think) which tries to guess
> where partitions began and ended - I've never used it so don't know if
> it's easy or difficult to use.
>
> Until you get your partitions back then you are going nowhere. If the
> data on these disks is worth real money to you then you might be better
> off stopping now and sending them to one of the specialist data recovery
> people like OnTrack. They charge an arm and a leg but should get your
> data back.
>
Downloaded 'gpart.' Simple to use by the way.
gpart tells me there is one partition on /dev/hdd occupying the entire
5.7g HD.
When I partitioned it originaly, /dev/hdd1 started at the default 1 and
ended at the default end, whatever that was.
So, I might, underline might, be able to repartition /dev/hdd with
'fdisk' using the defaults again and save the data?
Thanks for helping.
cedric
------------------------------
Subject: Re: Onstream S-50
From: Michael Meissner <[EMAIL PROTECTED]>
Date: 21 Mar 2001 10:24:21 -0500
Fleury =?iso-8859-1?Q?S=E9bastien?= <[EMAIL PROTECTED]> writes:
> Hello,
> we have an Onstream tape based on a linux mandrake 7.2 server.
...
> if we try to watch what was stored with the same mandrake when the saved
> syteme was working
> since, we have had some problems and the system was installed again.
>
> [root@saturne cups]# tar tvf /dev/st0
> tar: /dev/st0: Cannot read: Erreur d'entr�e/sortie
> tar: Au d�but du ruban, fin pr�matur�e.
> tar: Error is not recoverable: exiting now
As a side note, given OnStream just went into Chapter 7 bankruptcy, you
probably want to buy as many tapes as you can while they are still available.
Quoting from the 2.4.2-ac13 kernel configuration support.
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.
Here is the README file mentioned above:
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: "Fred Smirtz" <[EMAIL PROTECTED]>
Subject: No Sound With WinTV-PVR
Date: Wed, 21 Mar 2001 10:50:36 -0500
I can't seem to get any sound out of my Hauppauge WinTV-PVR. I'm running
RedHat 7.0, 2.4.2 kernel, and latest stable bttv drivers. I'm pretty sure I
have all the necessary modules loaded with the right options. My current
guess is that the msp3400 module just doesn't handle the msp3435 chip that
the WinTV-PVR has. Does anybody know if this is true? If not true I will
gladly provide all details of what I have tried to date.
Thanks
p.s. The picture is fine.
------------------------------
From: "Fred Smirtz" <[EMAIL PROTECTED]>
Subject: Re: Sound card config problems...
Date: Wed, 21 Mar 2001 11:19:50 -0500
I couldn't get my Yamaha sound card to work with RH 7.0 until I tried the
OSS (www.opensound.com) sound drivers. They cost ~$20 but you can test drive
for free.
"Christian Garms" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> grausam <[EMAIL PROTECTED]> writes:
>
> > Board 1 has Identity 81 ff ff ff ff 20 00 a8 65: YMH0020 Serial No -1
> > [checksum 81]
> > Board 2 has Identity f6 5a 13 f2 81 95 50 6d 50: TCM5095 Serial No -1
> > [checksum f6]
> > YMH0020/-1[0]{OPL3-SAX Sound Board}: Ports 0x220 0x530 0x388 0x330
> > 0x370; IRQ5 DMA0 DMA1 --- Enabled OK
> > YMH0020/-1[1]{OPL3-SAX Sound Board}: Port 0x201; --- Enabled OK
> > /etc/isapnp.conf:268 -- Fatal -IO range check attempted while device
> > activated
> > /etc/isapnp.conf:268 -- Fatal - Error occurred executing request
> > '<IORESCHECK>' --- further action aborted
> >
> > Does anyone know what I can do to remedy this situation?
> > -John Andrews
>
> Your card seems to be a YAMAHA sound card. Look into your PC which card
> you have exactly (e.g. look at the chips) and then point your browser
> to www.linhardware.com or www.alsa.org to check out, if your card is
> supported.
>
> The Red Hat sndcfg you have may be too crappy.
>
> --
> regards,
> Christian mailto:[EMAIL PROTECTED]
------------------------------
From: Patrick F Harris <[EMAIL PROTECTED]>
Subject: Re: Linux with Intel 815e chipset
Date: Wed, 21 Mar 2001 11:10:56 -0600
>From the bench marks I have found, the built in graphics should only be used
if the board is going to be used as a server. Note that Intel bench marks
this card with am external AGP graphics card.
[EMAIL PROTECTED] wrote:
> Hi,
>
> I want to build a system with Intel 815e "Solano" (82815 GMCH + 82801BA
> ICH2) chipset: SUPER 370SSA motherboard with PIII processor. As far as I
> understand this chipset provides built-in 2D/3D accelerated graphics and
> supports OpenGL.
>
> Does anyone has some experience whether the SUPER 370SSA works under
> linux and if it does is there X-drivers for this chipset?
>
> Thanks in advance,
> Ted
------------------------------
From: Patrick F Harris <[EMAIL PROTECTED]>
Subject: Re: TNT 2 or G-Force video card for Linux and Windows ??
Date: Wed, 21 Mar 2001 11:18:01 -0600
I just put a TNT 2 on a Byte AX and it works fine.
mike wrote:
> Hi,
> I want to replace my old video card. A friend told me to
> look at the TNT 2 card. While I was on the internet, I noticed
> that a G-force card was just a little more money than the TNT
> card. Another friend told me that he heard that even though
> the G-Force card is faster, the TNT card has better video
> quality.
> I would like to use the card for Linux and Windows.
> Any thoughts on the two cards?
>
> Thanks
> Mike
------------------------------
From: Donald Ellis <[EMAIL PROTECTED]>
Subject: Ultra 160 SCSI on Redhat 5.2
Date: Wed, 21 Mar 2001 12:23:07 -0500
HELP
I need to still use Redhat 5.2 (Kernel 2.0.36) because of the ftp kluge.
Does any one know how to get 2.0.36 to run the sym53C8xx driver module
for the LSI Logic 53c1010 scsi chip? I know it works for later kernels,
but I can not use them until we rewrite some old client software.
How about the Adaptec driver module for the Ultra 160 to run on 2.0.36 ?
Thanks
Donald Ellis
------------------------------
** 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
******************************
