Linux-Hardware Digest #644, Volume #13 Thu, 28 Sep 00 13:13:05 EDT
Contents:
Re: sym8751SPE - low performance (Johan Kullstam)
Re: Diamond MonsterSound/original drivers? (Stanislav Kogan)
Re: Linux WILL boot with T-Bird (Stanislav Kogan)
Re: Canon BJC-2100 (Ville Huuskonen)
Q: VIA-KT133 VGA interrupt not listed (Bernhard =?iso-8859-1?Q?K=FCpper?=)
promise 100 (Timo =?iso-8859-1?Q?L=F6bbel?=)
Oxygen VX1 AGP graphics car question. (Robert Sand)
Kernel hangs while accessing IDE disk (Pierre Habraken)
Eicon Diva 2.0 ISDN (Christian)
_Help needed_ with COM5 modem ("Natalia Sarv")
----------------------------------------------------------------------------
Subject: Re: sym8751SPE - low performance
From: Johan Kullstam <[EMAIL PROTECTED]>
Date: 28 Sep 2000 11:02:20 -0400
Tom Assmuth <[EMAIL PROTECTED]> writes:
> Hallo,
>
> I tried now several day but I've run out of ideas to get my
> Symbios Logic scsi board work in a adequate speed.
>
>
> Hardware:
> sym8751SPE (pci to ultra SCSI Host adapter ; with NVRAM and
> SYM53C875-chip)
> it has a normal 50-pin and a 68-pin connector internally
i have this card too.
> Im using Athlon 650 with an ASUS K7M board
>
> i upgradet from suse 6.3 (kernel (linux-2.2.13.SuSE)) to 6.4 (kernel:
> linux-2.2.14.SuSE)
> in the old system i compiled a Kernel with the following adjustments in
> the .config:
>
>
> CONFIG_SCSI_SYM53C8XX=y
> CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
> CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32
> CONFIG_SCSI_NCR53C8XX_SYNC=40
ok this looks good.
> this invoked a rather good performance (especialy to set _SYNC from 20
> to 40):
> I have 2 raid0 devices in the system with 2 hard-drives each.
>
> a copy from md0 to md1 was then performed with 14MB/s (before it only
> was 4,5 MB/s)
>
> for the new kernel i took the followng switches:
>
>
> CONFIG_SCSI_GENERIC_NCR5380=m
> CONFIG_SCSI_GENERIC_NCR53C400=y
> CONFIG_SCSI_G_NCR5380_PORT=y
> # CONFIG_SCSI_G_NCR5380_MEM is not set
> CONFIG_SCSI_INITIO=m
> CONFIG_SCSI_INIA100=m
> CONFIG_SCSI_PPA=m
> CONFIG_SCSI_IMM=m
> # CONFIG_SCSI_IZIP_EPP16 is not set
> # CONFIG_SCSI_IZIP_SLOW_CTR is not set
> CONFIG_SCSI_NCR53C406A=m
> CONFIG_SCSI_SYM53C416=m
> CONFIG_SCSI_SIM710=m
> CONFIG_SCSI_NCR53C7xx=m
> CONFIG_SCSI_NCR53C7xx_sync=y
> # CONFIG_SCSI_NCR53C7xx_FAST is not set
> CONFIG_SCSI_NCR53C7xx_DISCONNECT=y
> # CONFIG_SCSI_NCR53C8XX is not set
> CONFIG_SCSI_SYM53C8XX=y
> CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8
> CONFIG_SCSI_NCR53C8XX_MAX_TAGS=64
> CONFIG_SCSI_NCR53C8XX_SYNC=40
> # CONFIG_SCSI_NCR53C8XX_PROFILE is not set
> # CONFIG_SCSI_NCR53C8XX_IOMAPPED is not set
> # CONFIG_SCSI_NCR53C8XX_PQS_PDS is not set
> # CONFIG_SCSI_NCR53C8XX_SYMBIOS_COMPAT is not set
why are you building modules for every ncr/symbios chipset under the
sun?
> and i even activated the switch
> ] allow FAST-SCSI [10MHz] (CONFIG_SCSI_NCR53C7xx_FAST)
>
> I gave the kernel following parameters at boot-time:
> append="sym53c8xx=tags:8/t8t9t10t11q16,sync:40"
>
> (the md-devices are id 8, 9, 10, 11 and the doubling of tags increases
> performance a bit indeed)
>
> But regardless of the sync:40 and stuff transfer-rates are only about 5
> MB/s
> no matter wether copying within or between the md-devices.
>
> also led - activity of the devices is low. especially those 2 where Data
> are written to.
> (in the last working system all led lightend continously while copying)
>
>
> (i did not change /etc/mdtab at all because it worked at once)
>
> The scsi - part of dmesg I added in the end
>
> I do not really understand the messages, but the DNES drives are
> correctly
> recognized whith their 40MB/s - capability
> but I have the impression, that the controller is initialized wrong.
>
> should not ther be fast-40 in this line?
> sym53c875-0: Symbios format NVRAM, ID 7, Fast-20, Parity Checking
no. 40 MB/sec is FAST-20 plus 16 bit WIDE transfers. FAST-40 is the
newer LVD standard. afaik there are no 8 bit LVD FAST-40 devices.
hence FAST-40 in practice implies WIDE and thus 80 MB/sec.
> and should not be said something of at least Fast-20 for devices 8 to 11
> in the following context???
>
> sym53c875-0-<4,*>: FAST-20 SCSI 20.0 MB/s (50 ns, offset 15)
> sym53c875-0-<1,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 15)
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 2109840 [1030 MB] [1.0
> GB]
> sym53c875-0-<2,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 15)
> -------------
>
> I WOULD BE VERY GLAD IF SOME OF YOU COULD MAKE SUGGESTIONS OR SHARE
> SOME EXPERIENCE.
>
> would you try another kernel (generic 2.2.14 (not from Suse)) or
> use the SCSI_NCR53C8XX and not the SCSI_SYM53C8XX?
no. by all means use SYM53C8XX.
btw are you using RAID5? RAID5 involves a fair amount of traffic on
the SCSI bus since it's sending/reading stuff from many disks at
once. that's why hardware raid controllers have multiple scsi
channels.
> thanks Tom
>
>
>
>
> lvm -- Driver successfully initialized
> md driver 0.36.6 MAX_MD_DEV=4, MAX_REAL=8
> linear personality registered
> raid0 personality registered
> raid1 personality registered
> raid5 personality registered
> sym53c8xx: at PCI bus 0, device 15, function 0
> sym53c8xx: setting PCI_COMMAND_PARITY...(fix-up)
> sym53c8xx: 53c875 detected with Symbios NVRAM
> sym53c875-0: rev=0x04, base=0xefffff00, io_port=0xd800, irq=10
> sym53c875-0: Symbios format NVRAM, ID 7, Fast-20, Parity Checking
> sym53c875-0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex)
> 05/4e/80/01/00/24
> sym53c875-0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex)
> 05/46/80/00/08/24
> sym53c875-0: on-chip RAM at 0xefffe000
> sym53c875-0: resetting, command processing suspended for 2 seconds
> sym53c875-0: restart (scsi reset).
> sym53c875-0: enabling clock multiplier
> sym53c875-0: Downloading SCSI SCRIPTS.
> scsi0 : sym53c8xx - version 1.3g
> scsi : 1 host.
> sym53c875-0: command processing resumed
> Vendor: SEAGATE Model: ST51080N Rev: 1144
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sda at scsi0, channel 0, id 1, lun 0
> Vendor: SEAGATE Model: ST32430N Rev: 0510
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sdb at scsi0, channel 0, id 2, lun 0
> sym53c875-0-<3,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 16)
> Vendor: IBM OEM Model: 0662S12 Rev: 2 23
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sdc at scsi0, channel 0, id 3, lun 0
> Vendor: PLEXTOR Model: CD-ROM PX-40TS Rev: 1.00
> Type: CD-ROM ANSI SCSI revision: 02
> Detected scsi CD-ROM sr0 at scsi0, channel 0, id 4, lun 0
> Vendor: HP Model: C1533A Rev: 9503
> Type: Sequential-Access ANSI SCSI revision: 02
> Detected scsi tape st0 at scsi0, channel 0, id 5, lun 0
> Vendor: ARCHIVE Model: VIPER 150 21247 Rev: -011
> Type: Sequential-Access ANSI SCSI revision: 01
> Detected scsi tape st1 at scsi0, channel 0, id 6, lun 0
> sym53c875-0-<8,*>: WIDE SCSI (16 bit) enabled.
> sym53c875-0-<8,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16)
> Vendor: IBM Model: DNES-309170W Rev: SA30
> Type: Direct-Access ANSI SCSI revision: 03
> Detected scsi disk sdd at scsi0, channel 0, id 8, lun 0
> sym53c875-0-<9,*>: WIDE SCSI (16 bit) enabled.
> sym53c875-0-<9,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16)
> Vendor: IBM Model: DNES-309170W Rev: SA30
> Type: Direct-Access ANSI SCSI revision: 03
> Detected scsi disk sde at scsi0, channel 0, id 9, lun 0
> sym53c875-0-<10,*>: WIDE SCSI (16 bit) enabled.
> sym53c875-0-<10,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16)
> Vendor: IBM Model: DNES-318350W Rev: SA30
> Type: Direct-Access ANSI SCSI revision: 03
> Detected scsi disk sdf at scsi0, channel 0, id 10, lun 0
> sym53c875-0-<11,*>: WIDE SCSI (16 bit) enabled.
> sym53c875-0-<11,*>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 16)
> Vendor: IBM Model: DNES-318350W Rev: SA30
> Type: Direct-Access ANSI SCSI revision: 03
> Detected scsi disk sdg at scsi0, channel 0, id 11, lun 0
see all these FAST-20 WIDE devices are going at 40 MB/sec.
> sym53c875-0-<1,0>: tagged command queue depth set to 8
> sym53c875-0-<2,0>: tagged command queue depth set to 8
> sym53c875-0-<3,0>: tagged command queue depth set to 8
> sym53c875-0-<8,0>: tagged command queue depth set to 16
> sym53c875-0-<9,0>: tagged command queue depth set to 16
> sym53c875-0-<10,0>: tagged command queue depth set to 16
> sym53c875-0-<11,0>: tagged command queue depth set to 16
> scsi : detected 10 SCSI generics 2 SCSI tapes 1 SCSI cdrom 7 SCSI disks
> total.
> sym53c875-0-<4,*>: FAST-20 SCSI 20.0 MB/s (50 ns, offset 15)
> sym53c875-0-<1,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 15)
> SCSI device sda: hdwr sector= 512 bytes. Sectors= 2109840 [1030 MB] [1.0
> GB]
> sym53c875-0-<2,*>: FAST-10 SCSI 10.0 MB/s (100 ns, offset 15)
> SCSI device sdb: hdwr sector= 512 bytes. Sectors= 4197405 [2049 MB] [2.0
> GB]
> SCSI device sdc: hdwr sector= 512 bytes. Sectors= 2055035 [1003 MB] [1.0
> GB]
> SCSI device sdd: hdwr sector= 512 bytes. Sectors= 17916240 [8748 MB]
> [8.7 GB]
> SCSI device sde: hdwr sector= 512 bytes. Sectors= 17916240 [8748 MB]
> [8.7 GB]
> SCSI device sdf: hdwr sector= 512 bytes. Sectors= 35843670 [17501 MB]
> [17.5 GB]
> SCSI device sdg: hdwr sector= 512 bytes. Sectors= 35843670 [17501 MB]
> [17.5 GB]
> Partition check:
> sda: sda1
> sdb: sdb1
> sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 >
> sdd: sdd1 sdd2
> sde: sde1 sde2
> sdf: sdf1 sdf2
> sdg: sdg1 sdg2
> hda: hda1 hda2 hda3 hda4 < hda5 hda6 >
> VFS: Mounted root (ext2 filesystem) readonly.
> --
> ___________ __ ____ ___ _____________________________
> / _ __ /_/ ( ( /|/| / / / /_/ __o
> / (_) /// / / __)_) / |/_/ / / / _`\<,_
> _________ [EMAIL PROTECTED] ______________(_)/ (_)
--
J o h a n K u l l s t a m
[[EMAIL PROTECTED]]
sysengr
------------------------------
From: Stanislav Kogan <[EMAIL PROTECTED]>
Subject: Re: Diamond MonsterSound/original drivers?
Date: Thu, 28 Sep 2000 11:10:10 -0400
Hi.
Steve Bradley wrote:
>
> Don Johnson wrote:
>
> >
> > careful there--i think Steve mistyped something---the MX300 has the
> > Aureal Vortex chipset, with the good drivers. Everything else(including
> > what I have), is not from Aureal necessarily, and won't work. So, if i'm
> > not terribly mistaken, the MX300 works.
>
> Don,
> Not sure what you mean - "with the good drivers"? My soundcard definately
> didn't come with Linux drivers from aureal, and I was unable to get them
> from aureal (their site was down every time I tried - possible related to
> their going out of business).
If you REALLY want the aureal drivers then try http://linux.aureal.com
It's up all the time. But you are better off with the sourceforge
project. This project is essentially based on the original aureal
drivers.
> The MX300 is not supported by the kernel, and the only other drivers I
> have found are the VERY beta ones from Opensound (they sound like sh*t) and
> the aureal project on sourceforge (they sound GREAT but, as I noted, they
> have some problems with system lockups using certain videocards and
> mainboards).
> If you could elaborate a little bit....I'd love to get my MX300 working,
> but I worked the problem for almost 2 months w/out success.
Well, the only viable choice right now are the sourceforge drivers. So,
if you were unable to get them working, then you can't get them working.
The main problem is, that Aureal didn't release the chip's
documentation, and the drivers are forst to use a binary hardware
interface provided by Aureal (Which is extremely buggy). Now that
Creative has killed Aureal (see http:// www.vortexofsound.com) It would
seem, that we'll NEVER get the documentation. So, essentially, we are
screwed.
BTW, did you try moving your card around? I personally found out that
Vortex2 (same chip) didn't like some of the IRQ's
Best regards.
------------------------------
From: Stanislav Kogan <[EMAIL PROTECTED]>
Subject: Re: Linux WILL boot with T-Bird
Date: Thu, 28 Sep 2000 11:23:31 -0400
Lou Grinzo wrote:
>
> Someone else pointed out that the solution to the
> "Linux won't boot with an Athlon/T-Bird chip" mess
> was to use the Linux boot parameter "x86_serial_nr=0".
>
> This does indeed work, but who wants to type that
> in at every boot? The solution is to add this
> to your lilo.conf file. Edit that file, and
> add the following line in the "stanza" for every
> Linux boot image. (Meaning once per kernel, NOT
> at the common section at the beginning of lilo,conf.)
>
> append="x86_srial_nr=0"
No, the best solution is to recompile the kernel. Personally I don't
understand the people that don't do that. How can they work with the
precompiled kernel?
>
> After you save the file, you run the lilo command
> (normally /sbin/lilo), and you should be set, and
> Linux will use the parameter automagically on
> ensuing boots.
>
> Lou
------------------------------
From: [EMAIL PROTECTED] (Ville Huuskonen)
Subject: Re: Canon BJC-2100
Date: 28 Sep 2000 15:33:10 GMT
In article <[EMAIL PROTECTED]>, John wrote:
>Ville Huuskonen <[EMAIL PROTECTED]> wrote:
>> My printer doesn't work.
>> I did
>> #insmod parport
>> #insmod parport_pc io=0x3bc,0x378,0x278 irq=none,7,auto
>> #insmod parport_probe
and insmod lp
>And what, might I ask, does your computer say about what you did?
It stayed quiet.
>What do you mean, "doesn't work?" It's so vague a term as to be almost
without meaning.
Sorry, it slipt.
--
Wille <[EMAIL PROTECTED]>
------------------------------
From: Bernhard =?iso-8859-1?Q?K=FCpper?= <[EMAIL PROTECTED]>
Subject: Q: VIA-KT133 VGA interrupt not listed
Date: Thu, 28 Sep 2000 17:44:06 +0200
Mainboard MSI K7T-Pro (VIA KT133 chipset)
AMD Thunderbird 800 MHz
Graphiccard ELSA GloriaII (nVidia Quadro)
SuSE Linux 7.0 Prof. (kernel 2.2.16)
The output from 'cat /proc/pci' shows that the VGA card has
the IRQ 11. But 'cat /proc/interrupts' does not show IRQ 11
at all. I'm not sure if this can lead to a problem but I
like to exclude any configuration error before complaining
the brand new EIZO F980 monitor.
VIAs driver set inludes an IRQ routing miniport driver, is
this something I need for Linux too or is it already in the
kernel?
Thanks for any hint.
--
Bernhard K�pper |Tel.: (49)-(30)-20192310
AGr Quantenchemie |Fax.: (49)-(30)-20192302
Humboldt-Universit�t |Mail: [EMAIL PROTECTED]
J�gerstr. 10/11, D-10117 Berlin|WWW: http://www.chemie.hu-berlin.de
------------------------------
From: Timo =?iso-8859-1?Q?L=F6bbel?= <[EMAIL PROTECTED]>
Subject: promise 100
Date: Thu, 28 Sep 2000 17:52:13 +0200
hi
how can i get a onboard promise chip to work? (pdc20265 chip on asus a7v
motherboard)
i am using suse 7.0 with kernel 2.2.16
------------------------------
From: Robert Sand <[EMAIL PROTECTED]>
Subject: Oxygen VX1 AGP graphics car question.
Date: Thu, 28 Sep 2000 10:52:24 -0500
Hello all,
I am installing RedHat 6.2 on a client workstation that has one of these AGP
graphics cards. Is there a driver I can use for this card, and where can I find
it? If not does anyone know how I can get X started up without the correct
driver?
--
Robert Sand.
mailto:[EMAIL PROTECTED] US Mail
University of Minnesota Duluth 10 University Dr.
Information Technology Systems and Services MWAH 176
144 MWAH Duluth, MN 55812
Phone 218-726-6122 fax 218-726-7674
"Walk behind me I may not lead, Walk in front of me I may not follow,
Walk beside me and we walk together" UTE Tribal proverb.
------------------------------
From: Pierre Habraken <[EMAIL PROTECTED]>
Subject: Kernel hangs while accessing IDE disk
Date: Thu, 28 Sep 2000 18:10:08 +0200
Since I have upgraded my linux box with RH 6.2 and kernel update
2.2.16-3 (compiled for i686), I get errors from the ide driver which
make the kernel freeze.
This happens after having worked one hour or less. I then have to turn
off and on the power switch. During the next boot sequence, fsck detects
some errors which it can't fix every times.
I don't know if there is some relation, but this began after I tried to
turn on dma using hdparm -d 1.
When the error happens, all processes look blocked and the kernel
displays endless messages onto the console :
========================================================================
ide0: reset timed-out, status=0x80
hda: status timeout: status=0x80 { Busy }
hda: drive not ready for command
ide0: reset timed-out, status=0x80
hda: status timeout: status=0x80 { Busy }
end_request: I/O error, dev 03:0b (hda), sector 4408
...
========================================================================
The main board is an Asus P2BF with Bios # 1010.
hparm returns the following information about the drive:
========================================================================
# hdparm -i /dev/hda
/dev/hda:
Model=ST38421A, FwRev=6.01, SerialNo=3BD096JA
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=16368/16/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=0(?), BuffSize=256kB, MaxMultSect=16, MultSect=off
DblWordIO=no, OldPIO=2, DMA=yes, OldDMA=2
CurCHS=16368/16/63, CurSects=-1056964357, LBA=yes, LBAsects=16498944
tDMA={min:120,rec:120}, DMA modes: mword0 mword1 mword2
IORDY=on/off, tPIO={min:240,w/IORDY:120}, PIO modes: mode3 mode4
UDMA modes: mode0 mode1 *mode2
#
========================================================================
I can't tell if these errors come from the software or the hardware (ide
controller or ide drive) because I have no spare drive for testing.
I already lost some data and a lot of time. I can't use the machine
anymore as long as the problem has not been fixed.
Obviously the reseller who sold me the main board and the drive can't
help because I am not using them with windows...
I would really appreciate any help or advice.
Pierre
--
________________________________________________________________________
Pierre HABRAKEN - mailto:[EMAIL PROTECTED]
T�l: 04 76 82 72 48 - Fax: 04 76 82 72 87
IMAG-LSR BP72 38402 SAINT MARTIN D'HERES Cedex
________________________________________________________________________
------------------------------
From: Christian <[EMAIL PROTECTED]>
Subject: Eicon Diva 2.0 ISDN
Date: Thu, 28 Sep 2000 18:30:07 +0200
Hi,
Did somebody install properly an Eicon Diva 2.0 internal ISDN card and could tell me
his kisdn
settings?
I'm using Mandrake 7.1. I installed kisdn and isdn4linux.
I can open kcmkisdn for configuring my acconut. It dials correctly but I cannot surf,
even if my
resolf.conf file is correct.
Maybe is just matter of protocols.
Thanks for any help
Chris
------------------------------
From: "Natalia Sarv" <[EMAIL PROTECTED]>
Subject: _Help needed_ with COM5 modem
Date: Thu, 28 Sep 2000 21:02:00 +0400
Hi,
I've got a US Robotics 56k modem which *is* hardware. The problem is that
Windoz98 defined that it's set up on COM5 (?) and uses IRQ12. And I've got
no way to change it (CMOS setup, hardware settings, ...) My Linux RH6.2 has
no more than 4 ports as usually and can't see COM5.
How could I get COM5 and make it work properly? Will be grateful much for
your help.
thanks,
Natalia
------------------------------
** 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
******************************