Linux-Hardware Digest #174, Volume #14           Sun, 14 Jan 01 03:13:04 EST

Contents:
  Re: Linksys Ethernet Card ("Zhadu")
  PnP monitors? (Harry George)
  Server Pro's/Con's Wanted (Ken McCord)
  Re: PnP monitors? (Dances With Crows)
  Re: PnP monitors? (Harry George)
  Re: Hardware detection sequence ("D. Stimits")
  Re: SCSI cabling problem ("D. Stimits")
  pci ethernet resource conflict: can't load module rtl8139 (Michael Isichenko)
  Scanjet 4200C (Andrew O'Brien)
  Using onboard IDE and PCI IDE at the same time (bjrosen)
  Re: RH 7 doesn't work with 3C905? (Raymond Toy)
  Re: RH 7 doesn't work with 3C905? (Vidar Skjelanger)
  hdparm for ATA/66 (VT82C686A) chipset (Eugene Grayver)
  Re: /dev/sequencer (Lew Pitcher)
  Re: Does kernel 2.2.18 need to be patched for raid??? (Tim Moore)

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

From: "Zhadu" <[EMAIL PROTECTED]>
Crossposted-To: 
comp.os.linux.redhat,comp.os.linux.questions,comp.os.linux.networking,comp.os.linux.admin
Subject: Re: Linksys Ethernet Card
Date: Sun, 14 Jan 2001 01:48:46 GMT

I recently installed one of this cards with Redhat 7.0. I am a total newbie,
been using Linux for three weeks, so getting the card to work must not be
that difficult. The card uses the tulip driver. Go to
http://www.scyld.com/network/updates.html and follow the directions of only
the section that says "Using the Source RPM". You may have to first download
ftp://ftp.scyld.com/pub/network/netdriver-2.1.src.rpm using Windows and then
change the ftp://ftp.scyld.com/pub/network/netdriver-2.1.src.rpm reference
in the instructions to the path of netdriver-2.1.src.rpm in your local drive
(maybe a diskette). Also make sure kernel source is installed (check/install
it with RPM or GnoRPM). E-mail me if you don't succeed.


"WB3KUM/9" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> I have Red Hat V7.0 Lynix installed on at Intel Pentium machine.  The
> installation does not recognize my Ethernet card.  As a post Red Hat
> installation exercise, I am unable to install a Linksys 10/100 Network
> card, Model NC 100, PCI interface.
>
> Has anyone been successful installing this card?  If so, please explain
> the procedure.
>
>
> Many Thanks In Advance!
>
> Please reply here or to this e-mail address
>
> [EMAIL PROTECTED]
>
>



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

From: Harry George <[EMAIL PROTECTED]>
Subject: PnP monitors?
Date: 13 Jan 2001 17:49:32 -0800

I went looking for a replacement monitor for a linux system.  Found a
lot of PlugNPlay monitors.  The one I happened to get was a NEC FE700,
which I could not configure above 800x600.  Was this just bad luck, or
are PnP monitors as bad for linux as PnP modems?

Specifically, any recommendations for 17" 1024x768x16bbp, .26mm, no
flicker?  Using an AOpen PT80 board, which I configure as PT75.

-- 
Harry George
[EMAIL PROTECTED]

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

From: Ken McCord <[EMAIL PROTECTED]>
Subject: Server Pro's/Con's Wanted
Date: Sat, 13 Jan 2001 20:56:27 -0500

Moving our existing Linux server to a new platform and wanted to get
people's opinions on the prospective new servers:  The new servers I'm
looking at are:

HP LH3000
IBM Netfinity 5600
Dell PowerEdge 4400
Gateway 8400
Compaq ML530

The new server is to be scaled to support approx. 180~210 Samba clients
and 40~60 Netatalk users.  

If VA Linux and some of the other Linux-only hardware companies offer
7x24,4 hr response, I'd include them in the mix.

Thanks,

Ken McCord

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

From: [EMAIL PROTECTED] (Dances With Crows)
Subject: Re: PnP monitors?
Date: 14 Jan 2001 04:09:05 GMT
Reply-To: [EMAIL PROTECTED]

On 13 Jan 2001 17:49:32 -0800, Harry George staggered into the Black Sun
and said:
>I went looking for a replacement monitor for a linux system.  Found a
>lot of PlugNPlay monitors.  The one I happened to get was a NEC FE700,
>which I could not configure above 800x600.  Was this just bad luck, or
>are PnP monitors as bad for linux as PnP modems?
>
>Specifically, any recommendations for 17" 1024x768x16bbp, .26mm, no
>flicker?  Using an AOpen PT80 board, which I configure as PT75.

Um, almost anything new that isn't bargin-basement should work for
1024x768@75Hz.  PnP has no relevance to monitors; the only data from a
monitor you need are the Hsync and Vsync ranges, which are in the
monitor's manual.  If you know those data, pull up the "advanced"
configuration dialog and enter the Hsync and Vsync ranges in the dialog
boxes that get displayed.  Or if you don't have the manual, go to the
manufacturer's website and find the specs, or try one of the preset
values ("Monitor that can do 1024x768 at 75Hz") in Xconfigurator/SaX/
XF86Setup.

Which distro and version of XFree86 are you using, and what's the
make+model of your video card?  If the above advice doesn't work for
you, there may be something about your software or hardware setup that's
causing problems, and this info will help anyone trying to diagnose the
problem.  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: Harry George <[EMAIL PROTECTED]>
Subject: Re: PnP monitors?
Date: 13 Jan 2001 20:45:26 -0800

Thanks.  I've searched further and it looks like, as you say, PnP is
not a problem.  But the NEC FE700 seems to be a trouble point (per
some deja postings) -- one person found modelines for 640x480 and
800x600 (which worked for me too) but not for 1024x768.  Maybe it was
the multisynching rather than the PnP which caused the problems.  So
I'll go get another make of monitor tomorrow and try again.

For what its worth:

AMD K6, 450MHz, 32MB, SUSE6.4. XFree 3.3.6.  Tried Sax, XF86Setup, and
modifying /etc/XF86config manually.  Also tried startx --probeonly.
Probing said it couldn't find any valid modelines, which is when I
went looking for FE700 modelines.  I even looked at the XFree HOWTO --
and quickly decided I'd rather get a different monitor than calculate
dot clocks...

[EMAIL PROTECTED] (Dances With Crows) writes:

> On 13 Jan 2001 17:49:32 -0800, Harry George staggered into the Black Sun
> and said:
> >I went looking for a replacement monitor for a linux system.  Found a
> >lot of PlugNPlay monitors.  The one I happened to get was a NEC FE700,
> >which I could not configure above 800x600.  Was this just bad luck, or
> >are PnP monitors as bad for linux as PnP modems?
> >
> >Specifically, any recommendations for 17" 1024x768x16bbp, .26mm, no
> >flicker?  Using an AOpen PT80 board, which I configure as PT75.
> 
> Um, almost anything new that isn't bargin-basement should work for
> 1024x768@75Hz.  PnP has no relevance to monitors; the only data from a
> monitor you need are the Hsync and Vsync ranges, which are in the
> monitor's manual.  If you know those data, pull up the "advanced"
> configuration dialog and enter the Hsync and Vsync ranges in the dialog
> boxes that get displayed.  Or if you don't have the manual, go to the
> manufacturer's website and find the specs, or try one of the preset
> values ("Monitor that can do 1024x768 at 75Hz") in Xconfigurator/SaX/
> XF86Setup.
> 
> Which distro and version of XFree86 are you using, and what's the
> make+model of your video card?  If the above advice doesn't work for
> you, there may be something about your software or hardware setup that's
> causing problems, and this info will help anyone trying to diagnose the
> problem.  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....

-- 
Harry George
[EMAIL PROTECTED]

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

Date: Sat, 13 Jan 2001 22:33:51 -0700
From: "D. Stimits" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: Hardware detection sequence

Ragnar Wisl�ff wrote:
> 
> D. Stimits wrote:
> 
> > Most bios setups for motherboards that have onboard devices have a
> > setting for "boot offboard devices first" or "reverse boot order" or
> > "reverse pci scan". Check the bios settings and reverse whatever it is
> > now.
> >
> 
> I've looked in vain for that. Nothing has been done to the BIOS on the m/b
> or any of the SCSI controllers since the kernel change. During POSTs the
> controllers come up in the order I want, it's when Linux starts they get
> swapped around. That's what puzzles me so, and keep the box from being
> useful.
> 
> Thanks for your response.
> 
> --
> Ragnar Wisl�ff
> ----------
> life is a reach. then you gybe.

I would wonder if, during the bootup of the different kernels, some
parameter is being supplied with a module or within the kernel
itself...differently between the two kernels. If some device is capable
of running at more than one setting, and it is set early on, then other
devices that would by default use that setting, would no longer have it
available...everything after that point would be shuffled around. Are
there any explicit hardware resource settings in the module setup or the
kernel compile itself that might cause the order to change due to
crowding out of other devices (or at least their default settings)?

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

Date: Sat, 13 Jan 2001 22:43:00 -0700
From: "D. Stimits" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: SCSI cabling problem

Steve Thompson wrote:
> 
> Here's the situation: I have a Supermicro 370DL3 motherboard, which has a
> 68-pin Ultra 160 SCSI connector on it. I also have a new IBM Ultrastar 160
> 10K rpm 36GB disk with an 80-pin SCA centronix connector. No other disks.
> I'd like to use the disk with this mobo. There will be several additional
> SCSI disks added later.
> 
> How to connect the two? Options are (1) return the disk and get one with a
> 68-pin connector: can't do this without a restocking fee of $75; (2) get a
> 68-pin to 80-pin converter: I've heard that these are unreliable for Ultra
> 160, but they are less than $75; (3) get a hot-swap kit for the disk which
> feeds 68 pins out the back: very expensive. I'd appreciate any advice on
> the best way to go here. TIA,
> 
> Steve

I'd highly recommend the hot swap ability. Supermicro even sells some
modular versions of this. Contact them to find out if it will work with
your cables. These hot swap bays add extra cooling support, and the
built-in termination, along with scsi ID, is more than convenient. I
think the backplanes improve their ability to transfer at rated spec.

I don't know if converters are good or not, but then you will have to
make a conversion choice every drive you add. Then there is the cable
mess. One cable, with built-in jumpers for ID and termination is worth a
lot...extra cooling for 10k rpm+ is also excellent.

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

From: Michael Isichenko <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: pci ethernet resource conflict: can't load module rtl8139
Date: Sun, 14 Jan 2001 06:34:40 GMT

I have a trouble installing the second pci ethernet card D-Link
DFE-530TX+ (to be used
for IP forw/masq).  The first pci card 3C900 works fine and connects me
to a cable modem.
I am running linux mandrake 7.2, kernel 2.2.17-21mdk on a 1.1 GHz
Athlon/EP-8KTA2
system.  Upgrading to D. Becker's latest ethernet driver set
netdriver-2.1 made no difference.

# cat /etc/modules.conf
alias net-pf-4 ipx
alias char-major-107 3dfx
pre-install pcmcia_core /etc/rc.d/init.d/pcmcia start
alias parport_lowlevel parport_pc
pre-install plip modprobe parport_pc ; echo 7 > /proc/parport/0/irq
alias scsi_hostadapter aic7xxx
alias usb-interface usb-uhci
alias eth0 3c59x #     3Com 3C900 10b Combo (rev 0).
alias eth1 rtl8139 #     D-Link
DFE-530TX+                                            

### Excerpt from /var/log/syslog

Jan 14 00:24:04 lelka kernel: rtl8139.c:v1.12 9/14/2000 Donald Becker,
[EMAIL PROTECTED]
Jan 14 00:24:04 lelka kernel:  http://www.scyld.com/network/rtl8139.html
Jan 14 00:24:04 lelka insmod: /lib/modules/2.2.17-21mdk/net/rtl8139.o:
init_module: Device or resource busy
Jan 14 00:24:04 lelka insmod: Hint: insmod errors can be caused by
incorrect module parameters, including invalid IO or IRQ parameters
Jan 14 00:24:04 lelka insmod: /lib/modules/2.2.17-21mdk/net/rtl8139.o:
insmod eth1 failed

Rebooting to win98 with pnp os temporarily enabled in bios and
installing D-Link driver
produced no device conflicts with the DFE-530TX+ card found at irq=5 and
io=E000-E0FF.
Using these numbers doesn't help, though: "modprobe rtl8139 io=0xe002
irq=5" results in
the following message: /lib/modules/2.2.17-21mdk/net/rtl8139.o: invalid
parameter parm_io.

I did read ethernet-HOWTO, but I am lost.  Any help in setting up the
second NIC will be
greatly appreciated.  I enclose my irq and pci information from /proc,
if it helps.  --Michael
==============================================================================================
# cat /proc/interrupts
           CPU0
  0:     295265          XT-PIC  timer
  1:       4471          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  8:          1          XT-PIC  rtc
 10:       5328          XT-PIC  eth0
 11:       3148          XT-PIC  aic7xxx
 12:     154615          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 14:      55113          XT-PIC  ide0
NMI:          0

# cat /proc/pci
PCI devices found:
  Bus  0, device   0, function  0:
    Host bridge: VIA Technologies Unknown device (rev 3).
      Vendor id=1106. Device id=305.
      Medium devsel.  Master Capable.  Latency=8.
      Prefetchable 32 bit memory at 0xd0000000 [0xd0000008].
  Bus  0, device   1, function  0:
    PCI bridge: VIA Technologies Unknown device (rev 0).
      Vendor id=1106. Device id=8305.
      Medium devsel.  Master Capable.  No bursts.  Min Gnt=4.
  Bus  0, device   7, function  0:
    ISA bridge: VIA Technologies VT 82C686 Apollo Super (rev 64).
      Medium devsel.  Master Capable.  No bursts.
  Bus  0, device   7, function  1:
    IDE interface: VIA Technologies VT 82C586 Apollo IDE (rev 6).
      Medium devsel.  Fast back-to-back capable.  Master Capable. 
Latency=32.
      I/O at 0xd000 [0xd001].
  Bus  0, device   7, function  2:
    USB Controller: VIA Technologies VT 82C586 Apollo USB (rev 22).
      Medium devsel.  IRQ 9.  Master Capable.  Latency=32.
      I/O at 0xd400 [0xd401].
  Bus  0, device   7, function  4:
    Bridge: VIA Technologies VT 82C686 Apollo Super ACPI (rev 64).
      Medium devsel.  Fast back-to-back capable.
  Bus  0, device   8, function  0:
    Ethernet controller: 3Com 3C900 10b Combo (rev 0).
      Medium devsel.  IRQ 10.  Master Capable.  Latency=32.  Min
Gnt=3.Max Lat=8.
      I/O at 0xdc00 [0xdc01].
  Bus  0, device   9, function  0:
    Ethernet controller: Unknown vendor Unknown device (rev 16).
      Vendor id=1186. Device id=1300.
      Medium devsel.  Fast back-to-back capable.  IRQ 5.  Master
Capable.  Latency=32.  Min Gnt=32.Max Lat=64.
      I/O at 0xe000 [0xe001].
      Non-prefetchable 32 bit memory at 0xd9000000 [0xd9000000].
  Bus  0, device  10, function  0:
    SCSI storage controller: Adaptec AIC-7881U (rev 0).
      Medium devsel.  Fast back-to-back capable.  IRQ 11.  Master
Capable.  Latency=32.  Min Gnt=8.Max Lat=8.
      I/O at 0xe400 [0xe401].
      Non-prefetchable 32 bit memory at 0xd9001000 [0xd9001000].
  Bus  0, device  11, function  0:
    VGA compatible controller: 3Dfx Unknown device (rev 1).
      Vendor id=121a. Device id=5.
      Fast devsel.  Fast back-to-back capable.  IRQ 9.
      Non-prefetchable 32 bit memory at 0xd4000000 [0xd4000000].
      Prefetchable 32 bit memory at 0xd6000000 [0xd6000008].
      I/O at 0xe800 [0xe801].

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

From: Andrew O'Brien <[EMAIL PROTECTED]>
Subject: Scanjet 4200C
Date: Sun, 14 Jan 2001 17:48:51 +1100



Someone pls point me in the right direction for getting a scanject 4200C 
working???

Also I have a Guillemot MaxiSound Fortissimo Sound card... has anybody had 
any luck in getting the digital out to work??



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

From: bjrosen <[EMAIL PROTECTED]>
Subject: Using onboard IDE and PCI IDE at the same time
Date: Sun, 14 Jan 2001 06:32:05 GMT

I'm looking for a mother board which will allow us to use the on board
IDE buses plus a couple of Promise ATA 100 cards at the same time. Is
this possible? and if so are there any recomendations? The application
is a high performance file server that uses six IDE buses.


Sent via Deja.com
http://www.deja.com/

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

From: Raymond Toy <[EMAIL PROTECTED]>
Subject: Re: RH 7 doesn't work with 3C905?
Date: 14 Jan 2001 01:41:34 -0500

>>>>> "Henrik" == Henrik Carlqvist <[EMAIL PROTECTED]> writes:

    Henrik> Raymond Toy wrote:
    >> I recently got a 3c905 ethernet card on a RH 7 system.  On
    >> installation of RH7, the card was correctly recognized etc.
    >> Everything was set up appropriately.
    >>
    >> However, if I try to ping anything, it always says network not
    >> reachable.

    Henrik> My guess is that your 3c905 is a 3c905C. Those cards are
    Henrik> not usable by the vortex driver in the 2.2.x
    Henrik> kernel. Somewhere on the web 3com has a driver called
    Henrik> something like 3c90x.c which can be compiled as a module
    Henrik> or into the kernel. With that driver your card will
    Henrik> probably work.

    Henrik> I think that support for 3c905C is added to the vortex
    Henrik> driver in kernel 2.4.0ac-something.

Thank you very much!  I just looked more closely at the card and
Windows does indeed say 3c905c-tx.  I'll go poke around for 3c90x.c or
maybe just grab 2.4.0ac-something as you suggest.

Thank you!

Ray

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

From: Vidar Skjelanger <[EMAIL PROTECTED]>
Subject: Re: RH 7 doesn't work with 3C905?
Date: 14 Jan 2001 08:02:44 +0100

Henrik Carlqvist <[EMAIL PROTECTED]> writes:

> My guess is that your 3c905 is a 3c905C. Those cards are not usable by
> the vortex driver in the 2.2.x kernel. Somewhere on the web 3com has a
> driver called something like 3c90x.c which can be compiled as a module
> or into the kernel. With that driver your card will probably work.
> 
> I think that support for 3c905C is added to the vortex driver in kernel
> 2.4.0ac-something.

My NIC works quite well, always has. Here are the relevant lines from
dmesg:

3c59x.c 16Aug00 Donald Becker and others http://www.scyld.com/network/vortex.html
eth0: 3Com 3c905C Tornado at 0x8800,  00:01:02:ab:b8:56, IRQ 5
  8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
  MII transceiver found at address 24, status 782d.
  Enabling bus-master transmits and whole-frame receives.

This is with my self-compiled 2.2.17 kernel. It also works perfectly with the
standard kernels in RedHat7.0 and 6.2.

Is my NIC not a 3c905C afterall?


-- 
mvh,
Vidar Skjelanger

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

From: Eugene Grayver <[EMAIL PROTECTED]>
Subject: hdparm for ATA/66 (VT82C686A) chipset
Date: Sat, 13 Jan 2001 23:22:47 -0800

Hi,

I have a dual CPU MSI-6321 motherboard and an IBM 40G 75GXP drive. 
Right now the drive is plugged into the ATA/66 ide slot (the ata/100
promise slots are also available).  I am using redhat 7.0 (kernel
2.2.xx).  What are the appropriate parameters for 'hdparm' to fully take
advantage of the drive.  Right now 
hdparm -tT /dev/hda gives just 3.85MB/sec, 150MB/sec.  Also, how much of
an improvement can I get by going to the ata/100?  Finally, I tried
booting with a 2.4.0 kernel, but the speed was the same.

Thanks.

P.S. (please reply via e-mail, if possible)

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

From: Lew Pitcher <[EMAIL PROTECTED]>
Subject: Re: /dev/sequencer
Date: Fri, 12 Jan 2001 21:59:10 -0500

"D. Stimits" wrote:
> 
> Not only do the device special files have to be there, your sound
> hardware that works with it must be initialized (which also implies it
> must have a driver). Some sound boards that have the hardware do not yet
> have the software for anything beyond basic audio.

Some sound cards don't even _have_ a midi synth chip (the SoundBlaster
PCI128 is one of them, btw). For those cards, software drivers that
convert midi to audio (wav) need to be installed.

-- 
Lew Pitcher

Master Codewright and JOAT-in-training
Registered Linux User #112576

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

From: Tim Moore <[EMAIL PROTECTED]>
Crossposted-To: 
alt.os.linux.mandrake,alt.os.linux.slackware,alt.uu.comp.os.linux.questions,comp.os.linux.development.system,comp.os.linux.misc,comp.os.linux.networking,comp.os.linux.setup,linux.dev.kernel
Subject: Re: Does kernel 2.2.18 need to be patched for raid???
Date: Sun, 14 Jan 2001 07:42:51 GMT

> Does mingo's raid patch raid-2.2.18-A2 get applied to kernel 2.2.18?

raid-2.2.18-B0 instead.

Also try to target a question rather than crossposting to 20 groups.
-- 
timothymoore
   bigfoot
     com

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


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