Linux-Hardware Digest #373, Volume #14 Tue, 20 Feb 01 02:13:05 EST
Contents:
4 speaker support for SBLive! (Mark)
How to test Connectivity? ("Hatem")
Re: ide-scsi problem after upgrade (Mark Bratcher)
Re: Tekram DC-390U3W isn't recognized at boot ("John Margaglione")
Re: Should I abandon SCSI? (Frank Pittel)
RH 7.0 with a 3Com 3c509 ISA network adapter. ("John Peterson")
Re: How to test Connectivity? (Eric P. McCoy)
Re: RH 7.0 with a 3Com 3c509 ISA network adapter. (Manfred Bartz)
Re: Flat Panel LCD Monitors
Help w/ CD-R/RW under Linux (David Herron)
Re: RH 7.0 with a 3Com 3c509 ISA network adapter. ("John Peterson")
Velocity 100 & Linux ("Konstantin Okounev")
Re: RH 7.0 with a 3Com 3c509 ISA network adapter. ("W. E. Coyote")
Re: RH 7.0 with a 3Com 3c509 ISA network adapter. (Manfred Bartz)
Re: RH 7.0 with a 3Com 3c509 ISA network adapter. ("John Peterson")
Re: Should I abandon SCSI? ("Bodo Mueller")
----------------------------------------------------------------------------
From: Mark <[EMAIL PROTECTED]>
Subject: 4 speaker support for SBLive!
Date: Tue, 20 Feb 2001 01:16:14 GMT
ok, XMMS and the other CD players aren't using the second speaker channel,
yet games are.
??
any ideas on how I can correct this.
I'm pretty sure that I used to get all 4 speakers going.
------------------------------
From: "Hatem" <[EMAIL PROTECTED]>
Subject: How to test Connectivity?
Date: Tue, 20 Feb 2001 01:42:04 GMT
I've setup two computers for linux..
and I've installed the network cards and they both are working fine!! (i
guess)
because I pinged each IP address on the same computer and the ping test was
successful,
but when I ping the two computers the ping fails.. (packets never recieved)
I am using IP address 10.0.0.1 and 10.0.0.2 for both and netmask 255.0.0.0
for both!!
I suspect the hardware isn't connected..
is there a definate test to make sure that the hardware is ok?
thanks.
------------------------------
From: [EMAIL PROTECTED] (Mark Bratcher)
Subject: Re: ide-scsi problem after upgrade
Date: Tue, 20 Feb 2001 01:41:09 GMT
In article <[EMAIL PROTECTED]>, David Tiselius wrote:
>After an upgrade from a RH6.2 system to the fisher beta (kernel 2.4) my
>IDE cdroms cant be mounted. I have one RO and one CD-R and they both
>worde fine under 6.2. I think scsi-emulation is compiled with the fisher
>kernel.
[snip]
Can you confirm this? I'm not sure what the upgrade will assume
about your devices.
--
Mark Bratcher
To reply direct, remove both underscores (_) from my email name
===============================================================
Escape from Microsoft's proprietary tentacles: use Linux!
------------------------------
From: "John Margaglione" <[EMAIL PROTECTED]>
Subject: Re: Tekram DC-390U3W isn't recognized at boot
Date: Mon, 19 Feb 2001 21:10:01 +0600
In article <[EMAIL PROTECTED]>, "Markus Kossmann"
<[EMAIL PROTECTED]> wrote:
> Either read about building a new initrd (= initial ramdisk). You will
> probably find a script called mk_initrd (or mkinitrd), which will build
> a new initrd for you. Read the documentation for that script about
> configuring it for a initrd, which loads the symbios driver module.
>
> Or build a new kernel and compile the symbios driver hard into the
> kernel.
>
>
I already tried both of those, to no avail. Any other ideas?
------------------------------
From: Frank Pittel <[EMAIL PROTECTED]>
Crossposted-To: comp.periphs.scsi
Subject: Re: Should I abandon SCSI?
Date: Tue, 20 Feb 2001 03:22:47 -0000
In comp.os.linux.hardware sad <[EMAIL PROTECTED]> wrote:
: "Bodo Mueller" <[EMAIL PROTECTED]> wrote in message
: news:96lu8i$lf9cj$[EMAIL PROTECTED]...
:>
:> "Ron Reaugh" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
:> news:tynj6.10682$[EMAIL PROTECTED]...
:> >
:> > Donovan Rebbechi wrote in message ...
:> > >
:> > >If you're willing to spend an awful lot of money on performance, then
:> SCSI
:> > >is worth considering.
: IDE ATA-100 puts SCSI into the dark ages....
I like what Alan Cox had to say. I can't remember the exact qoute but
it goes along the line of, ata100 proves that with enough thrust even
an anvil can fly.
Of course Ron is going to clain that Alan Cox is wrong and doesn't
know what he's talking about. :-)
--
Keep working millions on welfare depend on you
===================
[EMAIL PROTECTED]
------------------------------
From: "John Peterson" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: RH 7.0 with a 3Com 3c509 ISA network adapter.
Date: Mon, 19 Feb 2001 20:41:08 -0700
Hello, all!
Please forgive me if this is the wrong forum with which to post this
question, I'm new to Linux but hope to develop some proficiency over the
next year.
I am pulling my hair out trying to install Red Hat Linux 7.0 on a Dell
Dimension XPS P133c with 98MB RAM. (The processor is an "Overdrive" type,
yielding in a whopping 200MHz. ;-) I hope someone can shed some light on
this, as I've spend DAYS poring over Internet help files to no avail.
In this box is a 3Com EtherLink III ISA (3C509/3C509b) in ISA mode network
adapter. The card's pertinent settings are I/O: 300h and IRQ: 10 as
ascertained by the provided DOS-based floppy which has a configuration
program.
After performing a fresh "Workstation" installation of Red Hat Linux 7.0, I
run the "control-panel" program and choose the Kernel Configuration option.
It appears to me that the network adapter wasn't automatically detected.
So, I try to add it. I choose the "3c509" adapter, and set the IO value to
"0x300" and the IRQ value to "10". Since these parameters are merely text
boxes, I don't know if the format of the strings is appropriate, but I've
tried a number of combinations ("0x300", "300", "300h", etc.). I don't know
of any other configuration options, so I leave the "other parameters" field
blank.
Then I rebooted, even though it doesn't seem like that was a requirement.
Everything seemed fine on the reboot, so, once the system started again, I
added the Ethernet Interface (active at boot) with DHCP. I am trying to get
this to work with my Cisco 675 in PPP mode (it acts as the DHCP server, as
far as I can tell for my other Windows boxes, leasing out the NAT addresses
of 10.0.0.x) and my local ISP. There were only a couple of options that I
set (I didn't even try adding the DNS servers at this point). It seemed
very straightforward.
Then I rebooted again.
Ominously, on the ensuing shutdown, I got the following error:
insmod /lib/modules/2.2.16-22/net/3c509.o: insmod eth0 failed.
The subsequent startup yielded in the same error (and added "Delaying eth0
initialization.").
I'm at a loss for what to do. ANY suggestions, insight, ideas, etc. would
be MUCH appreciated!
John Peterson
------------------------------
Subject: Re: How to test Connectivity?
From: [EMAIL PROTECTED] (Eric P. McCoy)
Date: 19 Feb 2001 22:48:31 -0500
"Hatem" <[EMAIL PROTECTED]> writes:
> I've setup two computers for linux.. and I've installed the network
> cards and they both are working fine!! (i guess) because I pinged
> each IP address on the same computer and the ping test was
> successful, but when I ping the two computers the ping
> fails.. (packets never recieved)
Try `traceroute' instead. Likely it'll say "no route to host."
> I am using IP address 10.0.0.1 and 10.0.0.2 for both and netmask
> 255.0.0.0 for both!!
You'll need to choose different IP addresses for those two computers
if you ever want to use the Internet, unless you've actually been
assigned those numbers. 192.168.0.0/16 is a common choice.
> I suspect the hardware isn't connected..
> is there a definate test to make sure that the hardware is ok?
It doesn't sound like you're using a hub or switch. If that's the
case, make sure you're using the right type of cabling: I don't
believe (but am not positive) that you can use straight-through
cabling for this type of connection.
--
Eric McCoy <[EMAIL PROTECTED]>
"Knowing that a lot of people across the world with Geocities sites
absolutely despise me is about the only thing that can add a positive
spin to this situation." - Something Awful, 1/11/2001
------------------------------
Crossposted-To: comp.os.linux.networking
Subject: Re: RH 7.0 with a 3Com 3c509 ISA network adapter.
From: Manfred Bartz <[EMAIL PROTECTED]>
Date: Tue, 20 Feb 2001 04:10:52 GMT
"John Peterson" <[EMAIL PROTECTED]> writes:
> I am pulling my hair out trying to install Red Hat Linux 7.0
> on a Dell Dimension XPS P133c with 98MB RAM.
Which version of the kernel? I think there is a problem with
3c509 in 2.4.x
uname -r
> insmod /lib/modules/2.2.16-22/net/3c509.o: insmod eth0 failed.
Edit your ``/etc/lilo.conf'' and add this line near the top of the
file in the global section:
append = "ether=10,0x300,0,3c509,eth0"
Edit /etc/modules to include this line:
3c509
Run ``lilo'', then ``shutdown -r now''.
For kernel 2.4.x I noticed that cold-booting (after power had been
off) did not work. Cold-booting into a 2.2.x kernel first and then
warm-booting (power stays on) into 2.4.1 worked. IIRC, cold-booting
DOS, using the 3c509 config utility and then warm-booting worked too.
I have already reported this as a bug, but if you can confirm this
you might want to add you voice to it.
--
Manfred
===============================================================
ipchainsLogAnalyzer, NetCalc, whois at: <http://logi.cc/linux/>
------------------------------
From: <[EMAIL PROTECTED]>
Subject: Re: Flat Panel LCD Monitors
Date: 20 Feb 2001 13:16:42 +0900
>>>>> "yeah" == yeah <[EMAIL PROTECTED]> writes:
yeah> Does anyone have any recommendations on a moderately priced
yeah> flat panel LCD monitor that has linux support?
i don't see why you should have any difficulty with a moderately
priced lcd display in linux. something like the apple lcd monitors
might not work, what with the special cable and all, but then, they're
not exactly moderately priced. my advice would be to go check some
out with your own eyes and see which you prefer. after all, you're
the one who'll be staring it at day in and day out. i went for the
eizo l350, which i rather like with linux. haven't had much luck with
it on my sun or sgi, even if it's theoretically capable of dealing
with their video output.
ciao,
g.m.
--
[EMAIL PROTECTED]
The PILLSBURY DOUGHBOY is CRYING for an END to BURT REYNOLDS movies!!
------------------------------
From: David Herron <[EMAIL PROTECTED]>
Subject: Help w/ CD-R/RW under Linux
Date: Tue, 20 Feb 2001 05:07:20 GMT
Hi, I'm trying to wean myself completely off of Windows. One of the
features I'm wanting to keep is to be able to burn CD's.
I have an HP 8110i/IDE drive on my WinNT system. I started to move that
over (I have RedHat 6.1) .. but then I read the CD recording FAQ, and it
said I needed to install the ide-scsi driver and do some extra mumbo
jumbo waving of magic wands that I didn't feel like doing.
As a substitute .. I bought a Pacific Data Corp 8824 SCSI CD R/RW
drive. The labels on the drive actually read Yamaha 8824S .. and the
manual on the Yamaha web site perfectly reflects this drive (in fact the
manual PDC provided had xerox'd pages directly from the Yamaha
manual!!).
The CD Recording FAQ says that the Yamaha 8424 works. I also downloaded
a fresh copy of cdrecord (v1.9) and compiled/installed it. The
documentation there also says the 8424 works fine, as does the online
database referred to by the CD Recording FAQ. So... 8824 .. 8424 ..
what's a few numbers between friends?? The 8824 isn't listed anywhere,
but it "should" be the same as the 8424 but faster, right???
well ...
The trouble I'm running into is these three things:
1- If I have the termination jumper installed, when I boot the system
the keyboard works fine during the bootup, but once I get to the
xdm/Redhat login screen (X is started) nothin' typed on the keyboard or
moved on the mouse does anything on the screen. As soon as I take the
termination jumper out, the system behaves right. This drive is the
only one thing the internal cable. I have an Advansys
PCI SCSI controller.
2- I have an UMAX 2200 scanner on the external SCSI port. If the
scanner is turned on, then "cdrecord -scanbus" returns funky values. It
does see stuff at their proper (jumpered) ID numbers, but the
information printed is bad. It also takes a loooong time to scan the
bus.
3- With the scanner off, "cdrecord -scanbus" returns right away and
prints the right identifying string for the drive name etc. But it
identifies the drive merely as a "Removable CD-ROM". Also, if I try
"-prcap" or "-inq" there's a message indicating it's a generic CD-ROM
and "unsupported CD/DVD-Recorder".
=====================================================
[root@bessie david]# /opt/schily/bin/cdrecord -v -prcap dev=0,3,0
Cdrecord 1.9 (i586-pc-linux-gnu) Copyright (C) 1995-2000 J�rg Schilling
TOC Type: 1 = CD-ROM
scsidev: '0,3,0'
scsibus: 0 target: 3 lun: 0
Linux sg driver version: 2.1.34
Using libscg version 'schily-0.1'
atapi: 0
Device type : Removable CD-ROM
Version : 2
Response Format: 2
Capabilities : SYNC
Vendor_info : 'YAMAHA '
Identifikation : 'CRW8824S '
Revision : '1.00'
Device seems to be: Generic CD-ROM.
[root@bessie david]# /opt/schily/bin/cdrecord -scanbus -v
Cdrecord 1.9 (i586-pc-linux-gnu) Copyright (C) 1995-2000 J�rg Schilling
TOC Type: 1 = CD-ROM
Linux sg driver version: 2.1.34
Using libscg version 'schily-0.1'
scsibus0:
0,0,0 0) *
0,1,0 1) *
0,2,0 2) *
0,3,0 3) 'YAMAHA ' 'CRW8824S ' '1.00' Removable CD-ROM
0,4,0 4) *
0,5,0 5) *
0,6,0 6) *
0,7,0 7) *
===========================================================
Reading the cdrecord source code, I find where the "Generic
CD-ROM" message is printed. It's in a function printing information
from an inquiry ... and the code is switching directly to "Generic
CD-ROM" rather than "Generic CD-RW" like it should. That's screwy ...
The impression I get from the CD Recording FAQ is that it should be
plug-n-play with the modern CD-R/RW drives, and this one certainly is a
modern drive. Well... I am noticing this "MMC" tag that are on many
drives, and none of the literature on this drive says "MMC".
Please help ...
David
------------------------------
From: "John Peterson" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: RH 7.0 with a 3Com 3c509 ISA network adapter.
Date: Mon, 19 Feb 2001 22:11:52 -0700
Hello, Manfred!
Thank you for your help! Unfortunately, it didn't yield in a fix, but I'm
grateful nonetheless! Please see additional information inline:
"Manfred Bartz" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> "John Peterson" <[EMAIL PROTECTED]> writes:
>
> > I am pulling my hair out trying to install Red Hat Linux 7.0
> > on a Dell Dimension XPS P133c with 98MB RAM.
>
> Which version of the kernel? I think there is a problem with
> 3c509 in 2.4.x
>
> uname -r
I show: 2.2.16-22
> > insmod /lib/modules/2.2.16-22/net/3c509.o: insmod eth0 failed.
>
> Edit your ``/etc/lilo.conf'' and add this line near the top of the
> file in the global section:
>
> append = "ether=10,0x300,0,3c509,eth0"
>
> Edit /etc/modules to include this line:
>
> 3c509
>
> Run ``lilo'', then ``shutdown -r now''.
>
> For kernel 2.4.x I noticed that cold-booting (after power had been
> off) did not work. Cold-booting into a 2.2.x kernel first and then
> warm-booting (power stays on) into 2.4.1 worked. IIRC, cold-booting
> DOS, using the 3c509 config utility and then warm-booting worked too.
>
> I have already reported this as a bug, but if you can confirm this
> you might want to add you voice to it.
After the shutdown, I get exactly the same symptoms as I stated in my
original post. For what it's worth, I've verified the network card under
Windows 95. It seems to work just fine with an I/O address of 300h and IRQ
10. If you have any other ideas, I would be very grateful. Thank you again
for your help! :-)
John Peterson
------------------------------
From: "Konstantin Okounev" <[EMAIL PROTECTED]>
Subject: Velocity 100 & Linux
Date: Tue, 20 Feb 2001 12:33:22 +0600
Hello,
Could anybody provide any info regarding running Xfree86 X-server with video
card Velocity 100 ?
Is it possible to use for this card drivers targeted to Voodoo3 family ?
Regards,
Konstantin
[EMAIL PROTECTED]
------------------------------
From: "W. E. Coyote" <d>
Crossposted-To: comp.os.linux.networking
Subject: Re: RH 7.0 with a 3Com 3c509 ISA network adapter.
Date: Mon, 19 Feb 2001 23:30:39 -0600
I have read that lilo settings are ignored when you are using a loadable
module. The Lilo settings only work when the card code is compiled into the
kernel. I have dual nics and added the info into /etc/modules.conf. For my
dual 3c509b cards it was
(replace 3c509 with your module name)
/etc/modules.conf
alias eth0 3c509
alias eth1 3c509
options 3c509 irq=7,10
only the irq setting is needed/allowed for 3c509b
PatG
------------------------------
Crossposted-To: comp.os.linux.networking
Subject: Re: RH 7.0 with a 3Com 3c509 ISA network adapter.
From: Manfred Bartz <[EMAIL PROTECTED]>
Date: Tue, 20 Feb 2001 05:35:55 GMT
"John Peterson" <[EMAIL PROTECTED]> writes:
> I show: 2.2.16-22
Should work without problems then.
> > > insmod /lib/modules/2.2.16-22/net/3c509.o: insmod eth0 failed.
> After the shutdown, I get exactly the same symptoms as I stated in
> my original post. For what it's worth, I've verified the network
> card under Windows 95. It seems to work just fine with an I/O
> address of 300h and IRQ 10.
As root, you can inser and remove modules manually. This allows you
to play with options.
Refer to <http://www.scyld.com/network/3c509.html>
And try playing with the options, f.e.:
insmod 3c509 debug=1 irq=10 xcvr=0
check that it loaded with:
lsmod
remove the module with:
rmmod 3c509
Any messages on your screen? Any new messages when you run
``dmesg | tail''? While you experiment you may want to open
another xterm and run this command in it:
tail -f /var/log/debug
or
tail -f /var/log/syslog
or other log files. The 10 most recently written-to log-files are:
ls -lt /var/log/ | head
If you succeed in loading the module use those parameters in the
append line in lilo.conf, run lilo and reboot (as before).
Good luck.
--
Manfred
===============================================================
ipchainsLogAnalyzer, NetCalc, whois at: <http://logi.cc/linux/>
------------------------------
From: "John Peterson" <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.networking
Subject: Re: RH 7.0 with a 3Com 3c509 ISA network adapter.
Date: Mon, 19 Feb 2001 23:10:33 -0700
Hello, Pat!
Ah! You hit on it *exactly*! I had something like the following in my
/etc/modules.conf file:
alias eth0 3c509
options 3c509 io=0x300 irq=10
But, when I eliminated the "io" parameter, everything started working like a
CHAMP!
Thank you and Manfred for all of your help tonight! I'm a happy man to
finally get this network stuff working!
Thanks again! :-)
John Peterson
"W. E. Coyote" <d> wrote in message news:3a9200cb$[EMAIL PROTECTED]...
> I have read that lilo settings are ignored when you are using a loadable
> module. The Lilo settings only work when the card code is compiled into
the
> kernel. I have dual nics and added the info into /etc/modules.conf. For
my
> dual 3c509b cards it was
>
> (replace 3c509 with your module name)
> /etc/modules.conf
> alias eth0 3c509
> alias eth1 3c509
> options 3c509 irq=7,10
>
> only the irq setting is needed/allowed for 3c509b
>
> PatG
>
>
>
------------------------------
From: "Bodo Mueller" <[EMAIL PROTECTED]>
Crossposted-To: comp.periphs.scsi
Subject: Re: Should I abandon SCSI?
Date: Mon, 19 Feb 2001 21:09:34 +0100
"Eric P. McCoy" <[EMAIL PROTECTED]> schrieb im Newsbeitrag
news:[EMAIL PROTECTED]...
> "Ron Reaugh" <[EMAIL PROTECTED]> writes:
>
> > >For my personal situation, I am guaranteed to encounter a
> > >non-recoverable data error about every year, for each disk. With two
> > >disks in a RAID0 array, I'd get twice the number of errors in the same
> > >amount of time.
>
> > Well, the rate per terabyte read would still be the same. So twice as
fast
> > gets one to an error sooner but that's an advantage and not a
disadvantage.
> > Such errors can appear for both SCSI or EIDE single drives or RAID 0.
Now
> > what are the undetected and unrecoverable error rates for a RAID 1 array
or
> > RAID 5 array?
>
> For RAID1, presumably half as much. For RAID5, actually, wouldn't it
> be constant no matter the number of disks in the array?
No, Actualy this is more complex.
Raid mainly protects against the failure of disks (partly or complete).
But if the disk with the defective data can be identifyed ( i.e. Media
errors recognised by the HDs themselve), The data can be restored.
This is normaly the only error that the normal user recognises ( Due to
mrked defects on the disk or filesystem)
But it gets more difficult with errors during transmission ( These can be
partialy recognised in SCSI with Parity, and with the newer IDE ans SCSI??
Variants with the better CRC Code in Transmission??)
these errors should normaly scale to the numbrs of transmissions, but also
slightly with the number of atached devices ( due to degrades signal
quality).
If such an error is not recognised, there are two different situations:
read errors and write errors.
With write errors the actual data stored on the disks is corruped. This can
be solved by a veryfying read after each and any write,
but incures a heavy preformance penalty, therfore it is mostly not
implemented.
With read errors the OS gets corrupted data.
With an raid system this can be soved by allways reading from all the disks
and controlling the parity in reads too ( only works for raid 3, conflicts
with the raid 4 and 5 advantages).
This is not implemented in most raid solutions ( again due to preformance
penalties), because in most cases parity calculation is one of the mayor
bottlenecks in raid implementations.
In most cases this problem ( independent or Raid) is solved by some
checksums within the files or filesystem.
These failures strongly depend the signal quality of the bus ( cableing and
termination, cable length etc .) and the quality of the Interface on
controllers and Disks ( wich is difficult to estimate).
Because of these kinds of failures (that cannot be detected by the raid) it
is paramount (in enviroments were high reliablility is impotant) that any
method to check on the succesfull and correct transmission of the data
aviable is used!!! ( Parity, Checsums, etc)
> > >I have _already_ suffered data errors on _both_ disks in this
> > >computer, and one disk is less than a month old. While it seems like
> > >I've gotten some flakey hardware, I think it should still serve to
> > >show that the likelihood of failure is _not_ small.
>
> > No, it just shows that you should get a professional to configure your
> > machines next time.
>
> When you have some basis for insulting my technical abilities, I'd
> like to hear it.
>
> In the meantime, I've been doing this sort of thing for the past 12
> yeears, and have never had serious problems until now. I've gotten
> more data corruption in the past six months than I have in the
> previous 11.5 years. That doesn't suggest anything about flakey
> hardware to you, but instead suggests incompetence on my part?
flaky hardware is the most lickely cause,i.e. bad cableing, bad power
supply, bad lot of HDs, poor termination are the most likely causes
(Or even some other component within or in the sourounding of the computer
that is interfering with HF radiation )
But because ther can be so many causes, it is difficult to pin down.
>
> [...]
> > Every book an RAID says that striping is called RAID 0...get a clue.
>
> Let me see if I have our positions right:
>
> 1. I say that while RAID0 is certainly a RAID level, it should not,
> quite technically, be one, as it is not actually redundant.
> 2. You admit that this is the case, but point out that RAID0 is a RAID
> level.
That`s typical Ron ;-)
-Bodo
------------------------------
** 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
******************************
