Linux-Hardware Digest #866, Volume #10 Tue, 27 Jul 99 22:13:34 EDT
Contents:
Re: eth0 and 3Com 3c507 NIC card (Vidar Andresen)
Re: X and Asus V3800 - RH6 Was: Help With Configuring X-windows (Timothy Murphy)
Canon CanoScan620P parallel (Joshua Li)
Re: Toshiba DVD-RAM and Linux (Steve McIntyre)
Re: #@$%&%( WINMODEMS are a pain in the A#$^&
Scsi Tape: Input/Output Error (Eric)
Re: BP6 with Linux ([EMAIL PROTECTED])
Is there an EIDE ATA/66 controller supported by a recent linux distribution? (Adam
Connor)
Re: HP Colorado 5Gb tape backup (Ian Briggs)
Re: Linux and MCA busses..? ([EMAIL PROTECTED])
Does linux support Tekram U2W scsi (Marcin Romaszewicz)
Re: Linux SCSI Performance Issues (Dave Platt)
Re: RedHat 6.0 and Mylex Acceleraid SCSI (Bryan)
----------------------------------------------------------------------------
From: [EMAIL PROTECTED] (Vidar Andresen)
Crossposted-To:
comp.os.linux.networking,linux.redhat.install,linux.redhat.misc,comp.os.linux.misc
Subject: Re: eth0 and 3Com 3c507 NIC card
Date: Tue, 27 Jul 1999 23:09:45 GMT
In article <[EMAIL PROTECTED]>,
"J. Guy Stalnaker" <[EMAIL PROTECTED]> wrote:
>Here's the skinny:
>
>Have the 3c507 driver compiled into the kernel. On boot, card is
>detected correctly at IRQ 10, Mem 0300, etc. With the card's native
To set the IRQ 10 to 'legacy isa' in bios would prevent pci-whatever
from posing a treath. 'Just to be on the safe side..'
>state alterred by its DOS configurator app so that ZeroWaitStates are
>disabled and Turbo mode is set to Standard, dhcpcd now communicates with
>our dhcp server [when it before did not] and, viola, we have a working
>network. Sorta. What happens is that nominal net traffic produces no
>problems. If, however, I run a TCP/IP app (same results whether
>Netscape inside X or ncftp at the command prompt, for example),
>approximately 50-60 seconds after starting up and while the app is
>sending/retrieving data, this starts:
>
>eth0: Command unit stopped, status xxxx, restarting -OR-
>eth0: Rx unit stopped, status xxxx, restarting.
[...]
>Anyone have a clue what's going on?
Is there any help in the (/usr/doc/howto/) Ethernet-howto chapter:
4. Performance Tips
4.1 General Concepts
* 4.2 ISA Bus Speed
* 4.3 Setting the TCP Rx Window
4.4 Increasing NFS performance
4.3 Setting the TCP Rx Window
[...]
Recent versions of the route command have the ability to set
the size of this window on the fly. Usually it is only for
the local net that this window must be reduced, as computers
that are behind a couple of routers or gateways are `buffered'
enough to not pose a problem. An example usage would be:
______________________________________________________________
route add <whatever> ... window <win_size>
______________________________________________________________
where win_size is the size of the window you wish to use (in
bytes). An 8 bit 3c503 card on an ISA bus operating at a
speed of 8MHz or less would work well with a window size of
about 4kB. Too large a window will cause overruns and dropped
packets, and a drastic reduction in ethernet throughput. You
can check the operating status by doing a cat /proc/net/dev
which will display any dropped or overrun conditions that
occurred.
Mvh Vidar Andresen
------------------------------
From: [EMAIL PROTECTED] (Timothy Murphy)
Subject: Re: X and Asus V3800 - RH6 Was: Help With Configuring X-windows
Date: 27 Jul 1999 23:53:00 +0100
vhold@NO*SPAM.eclipse.net (Christopher Moore) writes:
>I have a similar problem with my Asus V3800TVR.
>I ran xf86config, and chose the "Riva TNT" chipset (it's actually a TNT 2)
>followed the directions NOT to pick a clock setting & not to probe, but I'm
>ending up in 320*200 or something close... making x virtualy useless.
>I've looked through my XF86Config file, but I don't know enough to see my
>mistake.... any suggestions?
Just try adding
Chipset "RIVATNT"
in the Device section of XF86Config .
Goodness knows why XConfigurator, etc, do not add this.
--
Timothy Murphy
e-mail: [EMAIL PROTECTED]
tel: +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
------------------------------
From: Joshua Li <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Canon CanoScan620P parallel
Date: Tue, 27 Jul 1999 22:32:02 GMT
Is anyone out there doing a parallel driver for the scanner mentioned
above? And it you know the webpage please point it out.
TIA
--
Joshua Li
[EMAIL PROTECTED]
=====
Nothing is impossible for a man who doesn't do it himself.
------------------------------
From: [EMAIL PROTECTED] (Steve McIntyre)
Crossposted-To: comp.os.linux.development.system
Subject: Re: Toshiba DVD-RAM and Linux
Date: 27 Jul 1999 20:09:36 GMT
In article <7njqok$ie4$[EMAIL PROTECTED]>,
Christian Mund <[EMAIL PROTECTED]> wrote:
>Hello,
>I am the proud owner of a TOSHIBA SD-W1101 DVD-RAM Drive and want to know,
>if there is anyone out there, who is able to use this Drive with Linux.
>
>The Drive works in a 2-LUN Mode, LUN0 = CDROM and LUN1 = Optical Device.
>Reading from a DVD-Media works fine, but when i try to write, the
>Drive hangs up the SCSI-Bus.
>I tried to track this problem a little bit, but i am not so familiar with
>debugging Kernels .
>dmesg says : "aborting command due to timeout : write(6)
> timed out: reset"
>Using the strace-command i can see, that thwe Device-Hang occurs, when the
>Kernel does an fsync.
In our experiments at work the Toshiba DVD-RAM drive does not appear to be
happy with 6-byte write commands. Changing them to 10-byte commands from
our application seemed to fix the similar problems we saw.
>On the Web, there are patches for other DVD-RAM Drives ( HITACHI GF-1050,
>PANASONIC LD-1001 ). These Drives had all the same problem :
>They work in a 1LUN Mode and the Kernel detects them as CD-ROMs and not as
>Devices with wite-access.The only change in the Kernel is, that these
>patches declare these devices as opticals or direct access devices (like
>Disks), nothing else.The patches work great with Linux.
>I got the Inquiry-Pages from these Drives and found out, that the TOSHIBA
>has write-cache and the PANASONIC,HITACHI donīt.
In fact the Panasonic and Hitachi drives both have write-caching; if you
don't enable it then performance really sucks.
--
Steve McIntyre, Cambridge, UK. [EMAIL PROTECTED]
Also available from [EMAIL PROTECTED]
"Can't keep my eyes from the circling sky, +------------------
"Tongue-tied & twisted, Just an earth-bound misfit, I..." |Finger for PGP key
------------------------------
From: [EMAIL PROTECTED] ()
Crossposted-To: alt.os.linux,comp.os.linux.setup
Subject: Re: #@$%&%( WINMODEMS are a pain in the A#$^&
Date: 27 Jul 1999 22:27:47 GMT
On Sun, 25 Jul 1999 11:08:20 -0600, Scott Marlowe <[EMAIL PROTECTED]> wrote:
>First, an apology to recross posting this across groups, but Little Fish, you
>need to take some responsibility here too. If I went down to my Local Chevy
>Dealer and ordered a 10 Ton moving truck and told him, yeah, but I'm gonna be
>using it to haul "Bananas in Brazil", I'm not sure he'd know the exact way to
>setup that truck for that, and would likely tell me so. I'd have to explain to
>him all the intricacies of hauling "Bananas in Brazil" (A musical group, by the
>way) he might have a better understand of what I need.
>
>It's your job to know which modems are and are not winmodems right now. Why?
>Because no sales people know, they don't care, and you and I are still a tiny
>blip on the Radar screen of their sales pie chart.
unfortunately, the mistake can be compounded even more... for example,
NOWHERE in Compaq's literature, web page, manuals, or brochures does it
state that the internal modems in their Presario (and others, presumably)
are 'winmodems.'
i'd be pissed too!
>If you go back and calmly explain why a Winmodem won't work for you, show him a
>list of the major modems that are compatible, and tell him, hey, no big deal,
>we all screw up every now and again, when the next Linux user walks through the
>door, he'll know the right answer, and will be happy to see him.
we all like to rant... i'll be the original post helped considerably...
>If you go back belching flame and screaming of retribution, he's gonna cringe
>everytime someone running Linux walks in, and you will be doing a disservice to
>your fellow Linux users.
i feel sorry for salespersons anyway... i think the only reason i'd work
at a computer shop is for a 50% discount on hardware/software...
>It's an easy problem, with an easy fix, stop looking for a war.
i'm sure calm minds will prevail, but that doesn't help too much if he was
assured that the modem was not a winmodem, and now has to pack the whole
computer back up into its original packaging, drive back to the store,
then stand in line to return it, because the modem is internal and there's
no way to swap parts short of returning it, getting credit, then waiting
two weeks for the check to be returned before being able to buy another
computer without a modem, 'cause all the internal modems that come with
the computers at the store are all winmodems, and boy wasn't that a run-on
sentence?
:-)
>Little Fish wrote:
>
>> There should be a separte HELL for Salespeople who sell Winmodems. I asked
>> for a REAL MODEM FOR LINUX!!! When I setup my Redhat 5.2 I couldn't get my
>> modem to work! When I purchased the computer, a PC100, with the
>> Instructions" THIS IS TO BE A LINUX MACHINE." I already had the software,
>> all that I needed was my new Celeron 300a/36X cdrom/1.44 Floppy/ Zip 100 and
>> a MODEM. This modem (?) wouldn't work so I decided to setup a duel OS just
>> to try out another familiar environment "WIND-CRASH-DOZE" . The modem(?)
>> worked! Now this was interesting indeed. I was now confronted with having to
>> open my tower too inspect the modem(?). The Answer, a WEB EXEL 52pt-3511
>> #$^&^%&^) )*(&&*(*(& WINMODEM. On Monday I am going to give this Sales
>> person a Technical lesson with a SIZE 9 boot. And boy-o-boy am I pissed.
>>
>
------------------------------
From: [EMAIL PROTECTED] (Eric)
Subject: Scsi Tape: Input/Output Error
Date: Wed, 28 Jul 1999 23:34:37 GMT
I have a scsi tape drive (Seagate Taperstor NS 8GB) and my scsi card
sees it fine but whenever I try to send commands to it (/dev/st0) with
mt or try to write to it with tar I get "Input/output error". Scsi
card is a Tekram DC390F. Tape drive is at ID 3. All other scsi
devices (3 drives) are working fine. Scsi and scsi tape support are
compiled into the kernel (2.2.10 monolithic). System is Redhat 6.0
Below is the scsi-related output from the kernel at boot time:
kernel: ncr53c8xx: at PCI bus 0, device 10, function 0
kernel: ncr53c8xx: 53c875 detected with Tekram NVRAM
kernel: ncr53c875-0: rev=0x03, base=0xe0902000, io_port=0x6200, irq=11
kernel: ncr53c875-0: Tekram format NVRAM, ID 7, Fast-20, Parity Jul 26
kernel: ncr53c875-0: on-chip RAM at 0xe0900000
kernel: ncr53c875-0: restart (scsi reset).
kernel: ncr53c875-0: Downloading SCSI SCRIPTS.
kernel: scsi0 : ncr53c8xx - version 3.2
kernel: scsi : 1 host.
kernel: Vendor: IBM Model: DCAS-34330W Rev: S65A
kernel: Type: Direct-Access ANSI SCSI
revisoin: 02
kernel: Detected scsi disk sda at scsi0, channel 0, id 0, lun 0
kernel: Vendor: IBM Model: DDRS-39130W Rev: S97B
kernel: Type: Direct-Access ANSI SCSI
revision: 02
kernel: Detected scsi disk sdb at scsi0, channel 0, id 1, lun 0
kernel: Vendor: QUANTUM Model: FIREBALL_TM2110S Rev: 300X
kernel: Type: Direct-Access ANSI SCSI
revision: 02
kernel: Detected scsi disk sdc at scsi0, channel 0, id 2, lun 0
synestheisa kernel: Vendor: Seagate Model: STT8000N Rev:
4.30
kernel: Type: Sequential-Access ANSI SCSI
revision: 02
kernel: Detected scsi tape st0 at scsi0, channel 0, id 3, lun 0
kernel: ncr53c875-0-<0,0>: tagged command queue depth set to 8
kernel: ncr53c875-0-<1,0>: tagged command queue depth set to 8
kernel: ncr53c875-0-<2,0>: tagged command queue depth set to 8
kernel: scsi : detected 1 SCSI tape 3 SCSI disks total.
kernel: ncr53c875-0-<0,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset
15)
-Eric
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: BP6 with Linux
Date: 27 Jul 1999 23:14:55 GMT
[EMAIL PROTECTED] wrote:
: So can anyone tell me how the BP6's DMA/66 controllers works w/ Linux?
Please follow the HPT366 thread also found in this news group.
-- Chuan-kai Lin
------------------------------
From: [EMAIL PROTECTED] (Adam Connor)
Subject: Is there an EIDE ATA/66 controller supported by a recent linux distribution?
Date: Wed, 28 Jul 1999 00:37:16 GMT
Is there an EIDE ATA/66 controller supported by a recent linux
distribution? And if so, which controller with which distribution?
I've already learned that my Promise Ultra/66 isn't currently
supported (except by experimental kernels, etc.).
Are ATA/33 controllers the only current option for the "standard"
kernels?
thanks in advance,
--
adam connor / remove "_nospam" and "spamlite." to email
------------------------------
From: [EMAIL PROTECTED] (Ian Briggs)
Crossposted-To: comp.os.linux.x,comp.os.linux.setup
Subject: Re: HP Colorado 5Gb tape backup
Date: Wed, 28 Jul 1999 01:11:53 GMT
Robert C. Paulsen, Jr. wrote:
:Richard McClary wrote:
:>
:> My boss & I just spent about an hour trying to set up backups on our new
:> linux box (RH 6). The tape device is an HP Colorado 5 Gb (Travan?),
:> internal EIDE.
:
:Do not mount the device. Tape drives are accessed directly as
:devices, not as mounted file systems. I don't know what the EIDE
:tape devices are called
I've just got my Colorado 8GB IDE to respond to /dev/ht0.
: tar cvf /dev/rmt0 /etc
Well, it made promising noises (using /dev/ht0). How do I check to see
what, if anything, got written to the tape?
Ian
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Linux and MCA busses..?
Date: 28 Jul 1999 00:43:04 +0100
"Gerwin" <[EMAIL PROTECTED]> writes:
> Is there anyone who has a working version of linux on a MCA bus ?
> This buss is used in a PS/2 from ibm wich we will use as a server..
>
> Please more info..
I thought that there already was MCA (aka Microchannel?)
support in the kernel. If I'm wrong, sorry for getting your hopes up.
--
Tim.
------------------------------
From: Marcin Romaszewicz <[EMAIL PROTECTED]>
Subject: Does linux support Tekram U2W scsi
Date: Tue, 27 Jul 1999 17:57:43 -0700
Hi all,
I was wondering how well linux supports the tekram ultra-2 scsi
controllers, specifically the DC-390U2W, which is a lot cheaper than
the adaptec version.
The hardware compatibility howto does not list this as supported or
unsupported, so I guess it's a little out of date.
Thanks in advance, and please email reply in addition to posting
-- Marcin
------------------------------
From: [EMAIL PROTECTED] (Dave Platt)
Crossposted-To:
linux.dev.c-programming,linux.dev.kernel,comp.os.linux.development.system,linux.dev.scsi
Subject: Re: Linux SCSI Performance Issues
Date: Wed, 28 Jul 1999 01:28:32 GMT
In article <[EMAIL PROTECTED]>,
Dimi Shahbaz <[EMAIL PROTECTED]> wrote:
>The test.ps shows the degredation in performance as the number of disks
>increases. This is using the regular
>linux system calls --open, read, write, etc--directly on the device
>/dev/sda, etc. The file
>all_disks_read_scsi_generic.ps is a similar test, except that this was
>performed by directly accessing the
>SCSI controller--/dev/sga, etc--and not the disk(s) itself. As you can
>see, the problem of slowing disks is
>eliminated. However, the problem now is that for 2 disks, the number of
>total reads remains the same as the
>total number of reads for 1 disk by itself. The same is the case for 3
>and 4 disks. This should not happen,
>instead we expected a small total read count decrease but not half (for
>2 disks), 2/3's (for 3 disks), 3/4's (for 4
>disks).
You are probably observing a known artifact of many versions of the
/dev/sg generic SCSI driver. This driver is, in effect,
single-threaded. It maintains a single kernel-memory command buffer,
and the various tasks using /dev/sd* end up contending for this buffer.
Once you start a command of any sort on /dev/sga (for example), no
other thread/task/process can start a command on /dev/sgb until the
first command continues. The fact that the lower-level SCSI-card
drivers are capable of handling multiple I/Os won't help. Nor will
trying to do I/O to two or more SCSI controllers.
There are enhancements to the SCSI generic driver which enable it to
allocate, and release multiple kernel-memory buffers (one per client).
Check the 2.3 kernel tree - it's possible that one of the multi-buffer
patches has been incorporated into the development kernel tree.
--
Dave Platt [EMAIL PROTECTED]
Visit the Jade Warrior home page: http://www.radagast.org/jade-warrior/
I do _not_ wish to receive unsolicited commercial email, and I will
boycott any company which has the gall to send me such ads!
------------------------------
From: Bryan <Bryan@[EMAIL PROTECTED]>
Subject: Re: RedHat 6.0 and Mylex Acceleraid SCSI
Date: Wed, 28 Jul 1999 01:47:34 GMT
firstly, make sure you don't confuse SOFTWARE raid (kernel stuff) with
HARDWARE raid (driver stuff). the mylex driver is located at
www.dandelion.com, follow the links and PATCH the kernel. OOTB the
driver is NOT there in rh6.0 (I don't think).
and yes, you CAN boot from the system disk even if its raid. I do
with my mylex controller and linux.
[EMAIL PROTECTED] wrote:
: Hi there,
: We have just bought a Pentium III Xeon with a Mylex Acceleraid SCSI
: RAID controller and intend to use it to run RedHat 6.0 Linux, 2.2.5
: kernel. I've been having some problems installing the OS on this box:
: at the end of the formatting of the partitions, this message appears:
: "mount: device/resource busy"
: and the install will go no further (it doesn't matter whether you opt
: to format the partitions/check for bad blocks or not)
: We have a second box with exactly the same spec which exhibits the same
: behaviour equally reliably, so a simple hardware fault seems unlikely.
: This other machine has successfully had NT4.0 installed previously (in
: as much as such an action can ever be described as successful; don't
: blame me, I have to make a living doing this)
: Does anyone have any experience of this controller with RH6 ? I read
: some info to the effect that you can't have a Linux boot partition on a
: RAID device, but I'm thinking that this restriction went away in RH6
: with 2.2 kernels, as they have built-in support for RAID (and this
: device in particular, I think).
: All information gratefully received
: Thanks in advance
: Andy McKibbin
: Sent via Deja.com http://www.deja.com/
: Share what you know. Learn what you don't.
--
Bryan, http://www.Grateful.Net - Linux/Web-based Network Management
->->-> to email me, you must hunt the WUMPUS and kill it.
------------------------------
** 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 (and comp.os.linux.hardware) via:
Internet: [EMAIL PROTECTED]
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
******************************
