Mailing List
Home
Linux - General Red Hat Linux discussion list
Enterprise Linux 3 - Discussion of Red Hat Enterprise Linux 3 (Taroon)
Red Hat Linux 9 - Discussion of Red Hat Linux 9 (Shrike)
Installation - Getting started with Red Hat Linux
Red Hat Linux 7.3 - Discussion of Red Hat Linux 7.3 (Valhalla)
Red Hat Linux 8.0 - Discussion of Red Hat Linux 8.0 (Psyche)
Red Hat Linux 7.2 - Discussion of Red Hat Linux 7.2 (Enigma)
Red Hat Linux 7.1 - Discussion of Red Hat Linux 7.1 (Seawolf)
Apache Web Server
Oracle database, Microsoft SQL server ...
Subjects
application/x mplayer2 plugin
RPM error: db4 error(16) from dbenv >remove: Device or resource
   busy
Command stream end of file while reading
X Windows problem (xauth)
Upgrading openoffice 1 1 rpm
FTP: connection refused
FTP: connection refused
mount: /dev/cdrom: is not a valid block device
Dell Precision 650, RedHat 9, no sound
how to trace the cause resulting in the crash of bind server
Virus on the list
UNINSTALL RPM MYSQL
usb pen drives: mounting as a user
broadcom network interface
make mrproper
sendmail configuration on redhat
Couldn 't open PID file /var/run/named/named pid Permission denied
Promise 378 controller
kernel 2 6 and /dev/sound/mixer not found
Problem using up2date
mrtg step by step howto/configuration for a newbie?
Compiling and Installing Kernel 2 6
Can 't locate module ppp0, can 't locate module ppp compress 21
HOW I CAN MAKE BOOTABLE FLOPPY DISKET
Lotus Notes under Wine
/etc/security/limits conf question
Intel E/1000 driver
Command stream end of file while reading
rpm database corrupt
qla2300 modules
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
Problems with SCSI support on Red Hat Work Station 3 Update 1

Problems with SCSI support on Red Hat Work Station 3 Update 1

2004-02-03       - By Rick Stevens

 Back
Reply:     1     2     3     4     5  

tomncc3 wrote:
> Stuart -
>
> Unfortunately, I reverted the box I installed RHWS 3 on back to Fedora,
> since that flavor of RH could detect the SCSI adapter on boot. I
> understand the suggestions you mentioned below, and have used variants
> of them on other occasions, such as to enable RHAS 2.1 to run on a SAN,
> from an HP blade.
>
> I will save your post so when I try RHWS on the server, again, I 'll see
> what happens. Thank you very much for your tech tips, I 'll tuck them
> away for a later date.
>
> This is not directed at you, but my main concern is /why/ would RH
> remove these modules from a standard installation? Certainly a lot of
> people are going to upgrade from Fedora and RH9 to RHWS 3, whom are
> running slightly older, but well known hardware, just to encounter
> issues. You should not have to take a step back on the installation
> when upgrading to an enterprise version of the operating system. I
> realize that Red Hat is striving for stability, and perhaps the older
> drivers could cause problems, as a guess, but the adapter I am using is
> pretty well known and I feel it should have its module available during
> installation. If it were an obscure adapter, that fell into the realm
> of the Beta Max VCR or something like that, I could understand and drive on.

Since you bought RHEL3WS, squawk this issue to Red Hat. They should pay
attention to you as you 're a paying customer now. The reason it was
backed out may be down to a copyright issue due to the nature of RHEL
being a "commercial " product.

> The SCSI adapter I am trying to use, I usually configure as a three disk
> RAID5 set for my root area, not as storage after the fact of the
> installation. This is why I want it available on installation. I
> really like Red Hat Linux, I think it 's a great operating system, and I
> am not trying to bash them, but I think they should at least give people
> the option of having the older modules around, in case they would like
> to use them during system installations.
>
> Thanks,
>
> TK
>
>
> Stuart Sears wrote:
> > On Sunday 01 February 2004 04:55, tomncc3 wrote:
> >
> > >How do you get SCSI support with Red Hat Work Station 3? This seems
> rather
> > > "odd " that the Enterprise version of the operating system couldn 't
> handle a
> > >fairly standard SCSI controller, where the other "free " versions
> could. I
> > >am looking through the docs to see what I might have done wrong, but I
> > >can 't see anything. Did RH drop support for this controller for the
> > >Enterprise version?
> >
> > no, but they have shifted a lot of kernel modules into a
> 'kernel-unsupported '
> > rpm. just install the one that matches your kernel
>
> Can you "modprobe " the device to get the driver to load? If so, and you
> want the card active at bootup, you MUST make sure the initrd image has
> the driver installed. Building a kernel (or installing one) will not
> force the driver to be loaded into the initrd image. To do this, two
> conditions must be met:
>
> 1) There must be an "alias scsi_hostadapter driver-name " in
> the /etc/modules.conf file
>
> 2a) You must have a filesystem from the SCSI drive in question
> in /etc/fstab that must be mounted at boot
>
> OR
>
> 2b) You must tell mkinitrd to force-load the driver by using the
> "--with=module-name " option.


--
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
- Rick Stevens, Senior Systems Engineer rstevens@(protected) -
- VitalStream, Inc. http://www.vitalstream.com -
- -
- Dyslexics of the world: UNTIE! -
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --


__ ____ ____ ____ ____ ____ ____ ____ ____ ____
Redhat-install-list mailing list
Redhat-install-list@(protected)
https://www.redhat.com/mailman/listinfo/redhat-install-list
To Unsubscribe Go To ABOVE URL or send a message to:
redhat-install-list-request@(protected)
Subject: unsubscribe