Linux-Hardware Digest #73, Volume #14            Fri, 22 Dec 00 00:13:07 EST

Contents:
  Seegate STT8000A ("Ross Crawford")
  Re: CD-Writer on RH6.0 (Dances With Crows)
  Re: HD tinkering advise (Dances With Crows)
  Re: dying courier modem? (nicholas)
  Re: dying courier modem? (Matt Garman)
  CDD2000 with 2.2.14 -> PC deadlock (Ekkard Gerlach)
  Re: Rage 128 Pro (ATI) ("Jason Byrne")
  3Com CC1560i PCMCIA Modem ("Joseph C. Kopec")
  Re: dying courier modem? (Matt Garman)
  Re: dying courier modem? (Matt Garman)
  Re: dying courier modem? (Matt Garman)

----------------------------------------------------------------------------

From: "Ross Crawford" <[EMAIL PROTECTED]>
Subject: Seegate STT8000A
Date: Fri, 22 Dec 2000 12:07:40 +1100

Hi, all.

Has anyone had any experiences using these tape drives? I have one that
works fine under NT, but the following comes up in dmesg, and similar errors
in /var/log/messages when I try to access it. Am I missing something?

I'm using RedHat 6.0, with a 2.2.5-15 kernel.

Thanks

ROSCO

hdd: Seagate STT8000A, ATAPI TAPE drive
....
ide-tape: hdd <-> ht0, 600KBps, 14*26kB buffer, 2600kB pipeline, 190ms tDSC
ide-tape: hdd: Unsupported command in request queue
end_request: I/O error, dev 16:40 (hdd), sector 0
ide-tape: hdd: Unsupported command in request queue
end_request: I/O error, dev 16:40 (hdd), sector 2
ide-tape: hdd: Unsupported command in request queue
end_request: I/O error, dev 16:40 (hdd), sector 4
ide-tape: hdd: Unsupported command in request queue
end_request: I/O error, dev 16:40 (hdd), sector 6
ide-tape: hdd: Unsupported command in request queue
end_request: I/O error, dev 16:40 (hdd), sector 8
ide-tape: hdd: Unsupported command in request queue
end_request: I/O error, dev 16:40 (hdd), sector 10
ide-tape: hdd: Unsupported command in request queue
end_request: I/O error, dev 16:40 (hdd), sector 12
ide-tape: hdd: Unsupported command in request queue
end_request: I/O error, dev 16:40 (hdd), sector 14
ide-tape: hdd: Unsupported command in request queue
end_request: I/O error, dev 16:40 (hdd), sector 16
ide-tape: hdd: Unsupported command in request queue
end_request: I/O error, dev 16:40 (hdd), sector 18




------------------------------

From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: CD-Writer on RH6.0
Date: 22 Dec 2000 01:18:20 GMT
Reply-To: [EMAIL PROTECTED]

On Thu, 21 Dec 2000 11:29:36 -0600, Yi Fang staggered into the Black Sun
and said:
>I have a Philips CDD4201 CD-Writer on my Gateway E-5200 desktop.
>I tried to get it running so I read the CD-writing-HOWTO on
>www.linuxdoc.org. and downloaded the latest cdrecord binary version 1.9.
>When I use "cdrecord -scanbus" to test the system, I was told it can not be
>performed unless I logged in as root.  Actually, I did it as root.

Post the exact error message, not a paraphrase.  There are a number of
things that could be going wrong, but without exact info, I'm shooting
in the dark.  Anyway:

Have you compiled IDE-SCSI Emulation, SCSI Support, and SCSI Generic
   Support as modules or directly into the kernel?
Are those modules loaded?  (if you made modules)  "modprobe ide-scsi sg"
Did you boot with "hdX=ide-scsi" as a kernel parameter?  If you don't do
   this and you have IDE CD-ROM support enabled, the IDE CD-ROM driver
   will grab your CD-RW and won't let go.

Try those things.  If still no luck, post again, giving the exact text
of the error messages you get, as well as your kernel version and the
distro you're using.  HTH,

-- 
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /  Workin' in a code mine, hittin' Ctrl-Alt
http://www.brainbench.com     /   Workin' in a code mine, whoops!
=============================/    I hit a seg fault....

------------------------------

From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: HD tinkering advise
Date: 22 Dec 2000 01:18:23 GMT
Reply-To: [EMAIL PROTECTED]

On Thu, 21 Dec 2000 09:54:45 -0500, Jason Stegman staggered into the
Black Sun and said:
>currently to set the dma flag.  I also used hdparm to print my IO bit 
>setting which it currently is set at 16-bit.  The following are some 
>question i have:
>
>1)  If I set the IO setting to 32-bit, could there be problems if the 
>machine can't handle this?  How would i know if the machine can or can't 
>handle this?

It can.  (If my ancient P-150 laptop can handle it, your machine can!)

>2) I understand that the IDE ribbon has a lot to do with the performance 
>when dealing with an UltraDMA.  How do I know if I have the right ribbon?

The shorter the better.  UDMA/66 operation requires the dark gray cable
with 80 wires and colored connectors (blue/gray/black).  Linux can do
UDMA/66 if your board can; you just need a recent kernel and you may
have to apply a patch + use -X68 as an argument to hdparm.

>3) Are there any other fun things that I could do with hdparm to squeeze 
>the performance out of my HD?  Maybe someone could direct me to a good HD 
>tweaking website?

hdparm -m16 -u1 -c1 /dev/hda works very well for me.  I noticed no
benefit to using -d1, but -m16 and -u1 speed things up by about 30%.
FWIW, the 2.4.x kernel speeds disk I/O up by even more than that, from
13.5 M/s to 18 M/s (hdparm -Tt benchcraft) on my system.

-- 
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /  Workin' in a code mine, hittin' Ctrl-Alt
http://www.brainbench.com     /   Workin' in a code mine, whoops!
=============================/    I hit a seg fault....

------------------------------

From: nicholas <[EMAIL PROTECTED]>
Crossposted-To: comp.dcom.modems
Subject: Re: dying courier modem?
Date: Thu, 21 Dec 2000 19:37:56 -0600

cs wrote:
> 
> > Unfortunately, the Courier firmware haven't been upgraded for a
> > long time.
> 
> So what do you think is better?
> 
> charles....

Courier can be a disappointment partly because USR has not kept this
great modem updated for late technology. As of today, it still has no
drivers that make it work properly with Win Me (per their tech support).
The price of this modem nowadays, does not equal it performance.
What are you people who have recently purchased Courier modems think?

-- 
Please address replies and comments to this newsgroup

Nicholas

------------------------------

From: [EMAIL PROTECTED] (Matt Garman)
Crossposted-To: comp.dcom.modems
Subject: Re: dying courier modem?
Reply-To: [EMAIL PROTECTED]
Date: Fri, 22 Dec 2000 02:36:12 GMT

On Thu, 21 Dec 2000 19:37:56 -0600, nicholas <[EMAIL PROTECTED]> wrote:
> > > Unfortunately, the Courier firmware haven't been upgraded for a
> > > long time.
> > So what do you think is better?
> 
> Courier can be a disappointment partly because USR has not kept this
> great modem updated for late technology. As of today, it still has no
> drivers that make it work properly with Win Me (per their tech support).
> The price of this modem nowadays, does not equal it performance.
> What are you people who have recently purchased Courier modems think?

If I had recently bought this Courier, I would be pretty darn upset,
because as I mentioned in my initial post, my dad's Sportster 56k beats my
Courier, no contest.

If they released new firmware for the modem, it might be pretty decent.

However, I can't complain too much---I got mine pretty cheap years ago
direct from USRobotics when they had their "SysOp deal."  Before the
internet took off, and Bulletin Board Systems (BBS) were huge, USRobotics
practically gave their Courier modems to legitimate BBS operators (the
price was less than half of retail I think... $200 maybe?)

Oh well.
Matt

-- 
Matt Garman, [EMAIL PROTECTED]
"I may make you feel, but I can't make you think."
        -- Jethro Tull, "Thick as a Brick"

------------------------------

From: Ekkard Gerlach <[EMAIL PROTECTED]>
Subject: CDD2000 with 2.2.14 -> PC deadlock
Date: Fri, 22 Dec 2000 03:15:24 +0100
Reply-To: [EMAIL PROTECTED]


Hello, 

since my last upgrade 2.2.5 (Suse 6.1) to 2.2.14 (Suse6.4)
I can't any longer burn CD's. cdrecord invokes a full 
linux-deadlock within about 25 seconds. After keyboard, 
mouse, remote login, .. all is dead! I have to turn off
my PC by electric current. 
In these 25 seconds I have the chance to logout
from KDE and reboot, that my hd won't 
damage. Its very funny: in this case I can reach the 
last message of linux shutdown "unmounting /proc" 
- an linux is completely locked. But very often 
the shutdown is stoped by the deadlock before unmounting
the HD  :((   - or I give up shutting down an join the freezing
PC ... 

I have tested cdrecord 1.6.1 from suse 6.1 in Suse 6.4. I have
tested the latest cdrecord (cdrecord-1.9a05) - but 
all was in vain: cdrecord locks linux totally after about 25 Seconds
I have tested a ATAPI-Writer (Freecom 32x8x4) and cdrecord (Suse 6.4)
works fine.

I use Adaptec-SCSI-Controller 1505. With Suse 6.1 (2.2.5)
all worked well (I just re-installed Suse 6.1 on another 
partition an on works well on the same PC).

I compiled SCSI-Support as module or added it directly to the 
kernel. Nothing changed. 

I can use the writer as CD-ROM by mounting the device. 

Okay, it seems to be a software bug within 2.2.14. But 
in other newsgroups an mailing-lists I got no help. 
I think there is a timout somewhere in the hardware, 
because Linux can shut down as fast as normal during
the 25 seconds after starting cdrecord.

Has somebody an idea why Linux locks totally?

Perhaps because of the very old AHA1505-Adapter ?

BTW: WinOnCD (Win95) works fine ...




The writer ist recognised correctly 

rex: # cat /proc/scsi/scsi 
Attached devices: 
Host: scsi0 Channel: 00 Id: 01 Lun: 00
  Vendor: IMS      Model: CDD2000/00       Rev: 1.26
  Type:   CD-ROM                           ANSI SCSI revision: 02


Here is a trial with cdrecord:

rex:~ # cdrecord -v -speed=1 -multi dev=0,1,0 /tmp/image
   Cdrecord 1.8 (i686-pc-linux-gnu) Copyright (C) 1995-2000 J�rg
Schilling
   TOC Type: 1 = CD-ROM
   scsidev: '0,1,0'
   scsibus: 0 target: 1 lun: 0
   Using libscg version 'schily-0.1'   
   atapi: 0
   Device type    : Removable CD-ROM
   Version        : 2
   Response Format: 2
   Capabilities   :
   Vendor_info    : 'IMS     '
   Identifikation : 'CDD2000/00      '
   Revision       : '1.26'
   Device seems to be: Philips CDD-2000.
   Using driver for Philips CDD-522 (philips_cdd522).
   Driver flags   :
   FIFO size      : 4194304 = 4096 KB 
   Track 01: data   58 MB
   Total size:      67 MB (06:38.85) = 29914 sectors
   Lout start:      67 MB (06:40/64) = 29914 sectors

After this output to terminal Linux locks after about 25 
seconds. 

rex:~ # cdrecord -atip dev=0,1,0
Cdrecord 1.8 (i686-pc-linux-gnu) Copyright (C) 1995-2000 J�rg
Schilling
scsidev: '0,1,0'
scsibus: 0 target: 1 lun: 0
Using libscg version 'schily-0.1'
Device type    : Removable CD-ROM
Version        : 2
Response Format: 2
Capabilities   :
Vendor_info    : 'IMS     '
Identifikation : 'CDD2000/00      '
Revision       : '1.26'
Device seems to be: Philips CDD-2000.
Using driver for Philips CDD-522 (philips_cdd522).
Driver flags   :

After this output to terminal Linux locks after about 25 
seconds.  (trial with cdrecord 1.9)


rex:~ # cdrecord -inq dev=0,1,0
Cdrecord 1.8 (i686-pc-linux-gnu) Copyright (C) 1995-2000 J�rg
Schilling
scsidev: '0,1,0'
scsibus: 0 target: 1 lun: 0
Using libscg version 'schily-0.1'
Device type    : Removable CD-ROM
Version        : 2
Response Format: 2
Capabilities   :
Vendor_info    : 'IMS     '
Identifikation : 'CDD2000/00      '
Revision       : '1.26'
Device seems to be: Philips CDD-2000.

the option "inq" comes to end, not deadlock!


any help will be appreciated
Ekkard



------------------------------

From: "Jason Byrne" <[EMAIL PROTECTED]>
Subject: Re: Rage 128 Pro (ATI)
Date: Thu, 21 Dec 2000 19:35:06 -0800

"Ron Grigg" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
>
> Yes, the ATI Rage 128 Pro TV card is supported under
> XFree86-4.0.x.
>
> XFree86 just release another version (XFree86-4.0.2) that also
> supports ATI's new Radeon card along with some more nice
> enhancements.
>
> I've been able to get the TV working on my Rage 128 Pro card
> using kernel 2.4.0-test13-pre3, xawtv-3.25, XFree86-4.0.1,
> and Gatos ati_xv drivers.

(check out http://linuxvideo.org for more details on xawtv, and the Gatos
drivers)




------------------------------

From: "Joseph C. Kopec" <[EMAIL PROTECTED]>
Subject: 3Com CC1560i PCMCIA Modem
Date: Fri, 22 Dec 2000 04:23:32 GMT

I just acquired one of these modem cards for a ThinkPad 600X on which I 
am running RedHat 6.2 with version2.4.0-test11 of the kernel.  The 
ThinkPad has a Lucent modem built in, but the binary only driver does 
not work in kernel versions about 2.2.14.  I am wondering whether anyone 
could provide me with any links or advice on configuring this card -- I 
have not come across much on the web.  Thanks in advance.


------------------------------

From: [EMAIL PROTECTED] (Matt Garman)
Crossposted-To: comp.dcom.modems
Subject: Re: dying courier modem?
Reply-To: [EMAIL PROTECTED]
Date: Fri, 22 Dec 2000 04:58:00 GMT

On Mon, 18 Dec 2000 08:30:10 -0500, Hooda Gest <[EMAIL PROTECTED]> wrote:
> Matt Garman <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]...
> > I am experiencing two rather strange behaviors with this modem.  This
> > first is it emitting a very high-pitched frequency when it connects to
> > another modem.  This frequency is emitted regardless of the modem's
> > volume.  It is not very loud, but definately audible.  (I've seen some
> > older TVs that make a similar noise.)
> I've heard similar reports but don't recall any resolution. This high pitch
> tone continues throughout the call, correct? Basic advice is to turn down
> the volume. You might try calling USR regarding this (Courier owners get
> toll free support in the US).

The modem's volume control does not have any effect on the volume of the
high pitched sound, unfortunately.  Another poster said the noise could be
a result of noisy phone lines.  We live out in the country, quite a ways
from the phone company, and our phone lines are horrendous.

However, since my dad's Sportster modem works okay, I am assuming the
phone lines are not the problem here.

> > The other problem is that it always drops carrier in the middle of file
> > transfers.  I could dial up to my ISP and leave the connection on all day,
> > and it wouldn't drop the connection.  However, if I try to download any
> ...
> I could tell more if you showed me the result of an ati6i11 after one of
> these disconnects.

Here's what I got:

ati6i11
USRobotics Courier V.Everything Link Diagnostics...

Chars sent               163206      Chars Received          6309705
Chars lost                    0
Octets sent               80772      Octets Received         6042456
Blocks sent               11581      Blocks Received           48985
Blocks resent                 6

Retrains Requested            0      Retrains Granted              1
Line Reversals                0      Blers                       945
Link Timeouts                 0      Link Naks                     1

Data Compression       V42BIS 2048/32
Equalization           Long
Fallback               Enabled
Protocol               LAPM 128/15
Speed                  38666/21600
Last Call              00:34:22

Disconnect Reason is DISC Received
USRobotics Courier V.Everything Link Diagnostics...

Modulation               V.90/V.34+
Carrier Freq    ( Hz )   NONE/1829
Symbol Rate              8000/3200
Trellis Code             NONE/64S-4D
Nonlinear Encoding       NONE/ON
Precoding                NONE/OFF
Shaping                  OFF/ON
Preemphasis Index        NONE/4
Recv/Xmit Level (-dBm)   31.7/16.9
SNR             ( dB )   38.3
Near Echo Loss  ( dB )   10.8
Far Echo Loss   ( dB )
Roundtrip Delay (msec)   6
Timing Offset   ( ppm)   -3851
Carrier Offset  ( ppm)   2
RX Upshifts              1
RX Downshifts            2
TX Speedshifts           1
V.90 Status              uu,5,12N,12.1,-3,1N,0,39.5,25.5

OK


Thanks for any further info!

Matt

-- 
Matt Garman, [EMAIL PROTECTED]
"I may make you feel, but I can't make you think."
        -- Jethro Tull, "Thick as a Brick"

------------------------------

From: [EMAIL PROTECTED] (Matt Garman)
Crossposted-To: comp.dcom.modems
Subject: Re: dying courier modem?
Reply-To: [EMAIL PROTECTED]
Date: Fri, 22 Dec 2000 05:02:38 GMT

On 18 Dec 2000 18:01:43 GMT, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> In comp.dcom.modems Matt Garman
> <[EMAIL PROTECTED]> wrote:
> > I am experiencing two rather strange behaviors with this modem.  This
> > first is it emitting a very high-pitched frequency when it connects to
> > another modem. 
> 
> This is typical on bad lines when the two modems can't sync. 
> It happens with me a lot after rain.  

We're rural, probably five or more miles from the phone company, and our
phone lines are awful.  Five or six years ago I was big into bulletin
board systems, and I was lucky if I could maintain a connection to half
the BBSes I called.

I used to call the phone company daily to complain... one day they
"teased" me by saying that they could install some coils or something to
improve the signal over long distances such as mine.  So later when I
asked if they would do that, they said, no, that's too much work, you're
out of luck.  Apparantly our phone lines meet the bare minimum quality
standards, i.e. they're good enough for voice conversations, but they
stink for modems and such.

> Do a postmortem with ATI6 and ATI11 -- that should tell you 
> what happened and probably why.

I put this in a previous post, hopefully it should provide some insight!

Thanks a million,
Matt

-- 
Matt Garman, [EMAIL PROTECTED]
"I may make you feel, but I can't make you think."
        -- Jethro Tull, "Thick as a Brick"

------------------------------

From: [EMAIL PROTECTED] (Matt Garman)
Crossposted-To: comp.dcom.modems
Subject: Re: dying courier modem?
Reply-To: [EMAIL PROTECTED]
Date: Fri, 22 Dec 2000 05:05:47 GMT

On Mon, 18 Dec 2000 10:59:35 GMT, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
> Matt Garman <[EMAIL PROTECTED]> wrote:
> : I have an external USRobotics Courier "Dual Standard" analog modem that's
> : about five or six years old (obviously it's a serial modem).  It's been
> : flash upgraded to the latest ROM available from
> : http://consumer.3com.com/couriera/upgrades/index.html.
> [snip]
> : and it wouldn't drop the connection.  However, if I try to download any
> : large file (mp3s for example), it will always lose the connection about
> : five minutes into the transfer.
> The disconnect is caused by too many errors and retransmissions.
> If the ARQ led will be going on and off frequently this is an 
> indication.

Yes!  I forgot to mention that in my original post.  The "ARQ" light does
in fact flicker quite a bit.  The flashing usually gets pretty intense,
with longer periods of off than on just before a disconnect.

> Try disabeling V90!!! The connection will become a little slower,
> but more reliable!
> Also find out if you ISP supports the X2 protocol. If so, use
> that. It's a lot better than V90.

I think that's what I'll end up doing, is disabling v90.  I just sent an
email to my ISP's tech support to see what kind of modems are stocked in
their dial-in pool.

Thanks for the info!
Matt

-- 
Matt Garman, [EMAIL PROTECTED]
"I may make you feel, but I can't make you think."
        -- Jethro Tull, "Thick as a Brick"

------------------------------


** 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
******************************

Reply via email to