[rhn-users] New RHEL-AS-4

[Michael Weber]

Welcome to the wonderful world of Dell!

I have many Dell servers running Red Hat, and the problems you are
sharing aren't very unique, I'm afraid.  This is one of the reasons I
switched to buying IBM and HP servers for my production needs.  The Dell
hardware simply stinks.  Their Linux support is worse, and when you
finally get it running, you will discover that the speed of the Dell
RAID cards is 10% or less of what you expect.

Just wait until you need to know if one of your hard drives is about to
blow up.  Dell's Open Manage software is almost useless.  

</rant>  </rave>

The Dell servers we bought were a couple of hundred dollars cheaper
than the same specs on the IBM servers we replaced them with.  :-)

-Michael

>>> Geoff.Sweet at wildtangent.com 02/17 7:03 PM >>>
I am going to have to assume that there must be bigger problems with
the
aic79xx driver.  We are still waiting for a kernel fix that resolves a
kernel panic that occurs on our Dell servers.  It occurs when this
driver loads.  So far RH tech support can only tell us to build a
custom
ram image using older drivers and wait for the next kernel release. 
So
far 2 kernel releases have not resolved the issue (granted one of them
was a very minor release).  If there are going to continue to be
unexplainable issues with this driver, I am going to have to re-think
using RH.

What kills me, and no one can answer me this; two machines with
identical images (via ghost), one will have the kernel panic, the
other
won't.  It is very inconsistent.  

Geoff Sweet
Internet Operations Engineer
WildTangent Inc


-----Original Message-----
From: rhn-users-bounces at redhat.com
[mailto:rhn-users-bounces at redhat.com] 
On Behalf Of Richard Lefebvre
Sent: Thursday, February 17, 2005 1:51 PM
To: Red Hat Network Users List
Subject: Re: [rhn-users] New RHEL-AS-4

I had tried the "linux noprobe" already, it gets me a bit further, but
I
still need a the aic79xx driver at some point. So when I loaded later
it
got stuck again (without the IRQ message).

Richard

GREG WOJTAK wrote:
> I remember seeing something about this with RHEL 3, where you had to
> give the aic79xx driver a noprobe option otherwise it would hang. 
I'm
> sorry I can't remember the exact option, but maybe try Googling for
that
> and see if you can get that working.
> 
> 
> Greg Wojtak
> Unix Systems Administrator
> Sallie Mae
> (317) 598-4058
> 
> 
>>>>Richard.Lefebvre at rqchp.qc.ca 2/17/2005 4:26:57 PM >>>
> 
> Any one got the RHEL-AS-4 CD1 to work with a SCSI only for
harddrives.
> 
> Basically, the CD boots OK up to the point of loading the SCSI
drivers,
> 
> at which point I get:
> 
> Loading SCSI Driver
> Loading aic79xx driver... Disabling IRQ #5
> 
> The disabling message appears about 30 seconds later with out the 
> colored background (i.e. error message) Then nothing happens.
> 
> The computer is OK since I was able to install AS-3 (update 4) last
> week 
> with no problem. I wanted to install the new from scratch since the 
> setup of the server wasn't finished yet.
> 
> Richard

_______________________________________________
rhn-users mailing list
rhn-users at redhat.com 
https://www.redhat.com/mailman/listinfo/rhn-users 


_______________________________________________
rhn-users mailing list
rhn-users at redhat.com 
https://www.redhat.com/mailman/listinfo/rhn-users

CONFIDENTIALITY NOTICE:  This communication and any 
attached or enclosed files may contain information 
that is privileged, confidential, proprietary and/or 
otherwise protected from disclosure under applicable 
law ("Confidential Information").  Any review, 
retransmission, publication, dissemination, 
distribution, forwarding, printing, copying, storing, saving 
or other use or disclosure of this communication and/or the 
Confidential Information, or taking any action in reliance 
thereon, by an individual or entity other than the intended 
recipient(s) is strictly prohibited.  

This communication and the Confidential Information are 
intended solely for the use of the individual(s) and/or 
entity(ies) to which this communication is addressed. 
If you are not the intended recipient(s) (or responsible 
for delivery to said recipient(s)), please be advised 
that you have received this communication in error and 
have an obligation to promptly inform the sender by reply 
e-mail or facsimile and to permanently delete, shred or 
otherwise destroy, in its entirety, this original communication 
and all copies thereof, whether in electronic or hard copy format.