Linux-Hardware Digest #729

2001-05-04 Thread Digestifier 

Linux-Hardware Digest #729, Volume #14Sat, 5 May 01 00:13:08 EDT

Contents:
  RH 7.1, kernel 2.4, and Adaptec 29160 (Shelby S. Evans)
  Re: linux machine croaked :( (John-Paul Stewart)
  Re: RH 7.1, kernel 2.4, and Adaptec 29160 (Peter T. Breuer)
  Re: linux machine croaked :( (Eric P. McCoy)
  Re: run two linuxes (Eric P. McCoy)
  Re: Gigabyte GA-6vxdr7 SMP barfs with 2.2.17 (Dean Carpenter)
  Re: insmod/modprobe not responding (Jonadab the Unsightly One)
  ftP?? (dubcaller)
  Re: RH 7.1, kernel 2.4, and Adaptec 29160 (Shelby S. Evans)
  Re: LC 2000 network problem. Please help (Jonadab the Unsightly One)
  Re: ftP?? (Ian Jones)
  Re: Newbie question (Jonadab the Unsightly One)
  Re: CONFIG_USB_UHCI vs. CONFIG_USB_UHCI_ALT (a.k.a JE) (Frank Hahn)
  Re: binding network cards under linux. (Jonadab the Unsightly One)
  Re: TV-out under Linux / ATI Expert PLay 2000 card (Jonadab the Unsightly One)
  Re: IS YOUR PC SPYING ON YOU  5766 (Jonadab the Unsightly One)
  Re: BP6 + Mandrake + reboot problem (Jonadab the Unsightly One)
  How do I enable eth0 from SuSE rescue system? (Sam Piper)
  How to do a compressed dump backup? (james montoya)
  Software RAID using the HPT370 under linux? (Peter R)
  HP 5200c (Micah Yoder)
  Re: Bad A7V133 MB (Giles Hjort-Tyson)



From: Shelby S. Evans [EMAIL PROTECTED]
Subject: RH 7.1, kernel 2.4, and Adaptec 29160
Date: Fri, 04 May 2001 23:21:27 GMT

I am trying to get RH7.1 working with an Adaptec 29160 SCSI controller,
which RedHat claims to support right on the outside of the boxed set I
have purchased.

I have not been able to get RH to install on the drive (Seagate
ST318417W), and RedHat tech support (both web-based and phone) have
failed to help me with the problem.  In fact, RedHat's phone support
technician just told me the RH hardware group plans to downgrade the
29160 to 'community support' !!!

The SCSI bus now only has one device, the Seagate drive.  The RH install
script manages to partition the drive (by any of the 3 methods
provided--auto, disk druid, or fdisk), but when it gets to the point of
actually formatting the drive and installing the packages, virtual
console #4 shows that either the SCSI bus/device is timing out, or that
the interrupt handler is not syncing (which results in a kernel panic).
The failure type seems to be a function of the parameters set in the
SCSI bios either for the adapter itself (ID 7) or for the drive (ID 1).
I have concentrated on various combinations of enabling/disabling wide
negotiation and max sync rate for those two devices.

Suggestions on how to get this controller and drive to work?

Thanks.  Please respond by email.

Chris Evans
[EMAIL PROTECTED]






--

From: John-Paul Stewart [EMAIL PROTECTED]
Subject: Re: linux machine croaked :(
Date: Fri, 04 May 2001 23:36:57 GMT

Dan Stromberg wrote:
 
 I have a machine at home with runs redhat 7.0.
 
 1) I opened the case to replace the dead cdrom drive, and when I tried
to power it back up, it wouldn't.  No PS fan, no LED's, no beeps,
nothing.

I've met some rather picky motherboards that have done this
to me.  

Check all of the ribbon cables inside.  Improperly seater or
unseated IDE ribbon cables have caused the above symptoms in
machines I've worked on.  Also make sure you've got your
master/slave jumpers correct on the new cd-rom.   

Check to make sure all of the add-in cards are properly
seated in their slots.  Again, I've seen an improperly
seated graphics card cause all of the above symptoms on an
ATX board (even the PS fan bit).  It doesn't really make
much sense to me, but give it a try.  

Some motherboards and BIOSes are great about beeping out
error codes.  Cheaper boards just play dead.

Good luck, and HTH.


J-P Stewart

--

From: Peter T. Breuer [EMAIL PROTECTED]
Subject: Re: RH 7.1, kernel 2.4, and Adaptec 29160
Date: Sat, 5 May 2001 01:38:41 +0200

Shelby S. Evans [EMAIL PROTECTED] wrote:
 console #4 shows that either the SCSI bus/device is timing out, or that
 the interrupt handler is not syncing (which results in a kernel panic).
 The failure type seems to be a function of the parameters set in the
 SCSI bios either for the adapter itself (ID 7) or for the drive (ID 1).
 I have concentrated on various combinations of enabling/disabling wide
 negotiation and max sync rate for those two devices.

 Suggestions on how to get this controller and drive to work?

Use a different kernel. Apparently RH fouled up on the adaptec scsi
support they compiled. I have seen references to a new install kernel
available on their website. Please check the bugfixes/errata.

Peter

--

Subject: Re: linux machine croaked :(
From: [EMAIL PROTECTED] (Eric P. McCoy)
Date: 04 May 2001 19:50:04 -0400

Ron Freidel [EMAIL PROTECTED] writes:

 The previous reply covered alot of detail but I would also like

Linux-Hardware Digest #729

1999-07-10 Thread Digestifier 

Linux-Hardware Digest #729, Volume #10   Sat, 10 Jul 99 22:13:26 EDT

Contents:
  Re: 3Com USR 56K FaxModem and RedHat 6.0 (Frank Roberts)



From: Frank Roberts [EMAIL PROTECTED]
Subject: Re: 3Com USR 56K FaxModem and RedHat 6.0
Date: Sun, 11 Jul 1999 01:49:58 GMT

This is a multi-part message in MIME format.
==133F7A6EB176A27FCB5695EE
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Please see the following 3 Com Data Sheets for operation and installation
instructions:

Andy wrote:

 I have the same modem and recently got it working under RH 5.2
 Breathe a sigh of relief, it is NOT a Winmodem.
 The board itself is set to IRQ 12 and Address 0x03e8.  Use these settings
 in isapnp.conf and configure your /dev/cua2 to these.  If you need further
 help doing this, just ask or e-mail me at [EMAIL PROTECTED]
Andy

 Jonathan Bruce wrote:

  Hi,
 
  Can any give me some tips as to how I get get this modem working with
  RedHat Linux 6.0. It's an internel ISA modem (product code 568702)- so
  is it a WinModem, thus rendering it useless for Linux ?? I can't seem
  to find this out from the 3Com site or the documentation :-(
 
  If anyone can give me a few pointers as to how I can setup this modem,
  I'd really appreciate it !
 
  Cheers
 
  -Jonathan
 
  Sent via Deja.com http://www.deja.com/
  Share what you know. Learn what you don't.



==133F7A6EB176A27FCB5695EE
Content-Type: text/plain; charset=us-ascii; name="US Robotics - 10550.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline; filename="US Robotics - 10550.txt"

Subject: Document Number 10550
Date: Wed, 7 Apr 1999 21:23:21 -0500
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]

  Optimizing the Windows Serial Interface for High Speed Connections

For optimal data throughput, we recommend setting you communications
software's serial port(baud) rate at the highest possible speed(i.e.
19,200, 38400, 57600, or 115200 bps). Take note, not all computers
have a serial interface that can support the higher connection speeds.
How fast your computer's serial interface can go, depends on what type
of UART chip and communications driver your computer uses. To optimize
your computer's serial interface, you will need to know the following:

  *  The COM Port your modem is attached to.
  *  What type of UART(see document 10589) chip is in your computer.
  *  The Port Address of the COM Port the modem is attached to.
  *  The IRQ of the COM Port the modem is attached to.

Using MSD
To locate the above information, you can use Microsoft's diagnostics
program included with most versions of MS-DOS. If you do not have
access to DOS, consult your operating system manual for information on
how to access this data. Use the following steps to access this
information in DOS:

  1.  Exit Windows completely. Do not open a DOS Window.
  2.  Turn on your modem.
  3.  At the DOS prompt, type MSD and hit ENTER.
  4.  Select C to view the serial device settings.
  5.  Find the line UART Chip Used, and cross over to the COM Port
  your modem is on(the COM Port that has both DSR and CTS marked
  with a "Yes" is your modem). Write down the UART type and the
  Port Address(e.g., 02F8H) on the worksheet below.
  6.  Press ENTER to exit the COM Ports Window, then press Q to
  enter IRQ Status.
  7.  Locate the line that contains your modem's COM Port(e.g.,
  COM2) and write down the IRQ number at the beginning of that
  line(i.e., "3").
  8.  Exit MSD and run Windows again.

 Worksheet
COM: ___ UART Type:  Port Address:__ IRQ: ___

After you have successfully determined what type of UART chip your COM
Port is using, run your communications program and set the serial
port(baud) rate according to the following guidelines:

UART 16550 or 16550AF  Set your communications software to the highest
   serial port rate it allows(up to 115200). If
   you encounter problems after changing the
   port rate, try lowering it one setting.

UART 16450 or 8250  Set your communications software's port rate to
19200.

Modifying your SYSTEM.INI File
Windows 3.1/3.11(not Workgroup), uses a communications driver called
COMM.DRV.  Your modem's performance can be improved by replacing this
default communications driver with a different driver, such as
WFXCOMM.DRV(download off our BBS at 847-982-5092 or FTP Site at
ftp.usr.com) or CYBERCOM.DRV(see document 10251). These files are
placed in your WINDOWS/SYSTEM directory.

Note:  Your communications software may have already replaced this
   driver. The examples below show you how to check if you are
   still using COMM.DRV.

Changing the Communications Driver
The following steps describe the process of replacing the COMM.DRV
setting in yo