Hi,
thanks for the response Tim.
sorry, should have been more clearer - that is exactly what i am trying to do but when running rpm -bb SPECS/bcm5700.spec i get "SPEC/bcm5700.spec: No such file or directory" same for running rpm -bb SPECS/basplnx.spec. i am running both of these commands from /usr/src/redhat and both .spec files exist under /usr/src/redhat/SPECS - even tried using the full path but still the same:
[root@LINAPPP01 redhat]# pwd
/usr/src/redhat
[root@LINAPPP01 redhat]# ls
SOURCES SPECS
[root@LINAPPP01 redhat]# ls SPECS/
basplnx.spec bcm5700.spec
[root@LINAPPP01 redhat]# rpm -bb SPECS/bcm5700.spec
SPECS/bcm5700.spec: No such file or directory
[root@LINAPPP01 redhat]# rpm -bb SPECS/basplnx.spec
SPECS/basplnx.spec: No such file or directory
[root@LINAPPP01 redhat]# rpm -bb /usr/src/redhat/SPECS/bcm5700.spec
/usr/src/redhat/SPECS/bcm5700.spec: No such file or directory
[root@LINAPPP01 redhat]# rpm -bb /usr/src/redhat/SPECS/basplnx.spec
/usr/src/redhat/SPECS/basplnx.spec: No such file or directory
[root@LINAPPP01 redhat]#
is it possible that there are some dependencies that are not installed causing this error - the docs do not indicate that there are any dependencies.
as an alternative i tried the bcm5700 driver that comes with the base OS - this driver is allready installed but fails insmod reporting "No such device".
have also read that with Redhat 8 the kudzu files containing PCI vendor and device info need to be patched - is this also true for RHEL ES 2.1? Is it possible that the NICs are'nt being detected as Broadcom NICs and therefore reporting "No such device". How can I find out what NICs the OS thinks are installed?
we were planning on running the updates at a later stage after some initial testing - think I'll do that now and then try again.
Message: 1
Date: Fri, 30 Apr 2004 09:10:46 -0400
From: Tim Pickard <tpickard@xxxxxxxxxxxx>
Subject: RE: bcm5700 and basp
To: "'General Red Hat Linux discussion list'" <redhat-list@xxxxxxxxxx>
Message-ID: <003a01c42eb4$8d91f380$d10114ac@TPICKARD>
Content-Type: text/plain; charset="us-ascii"
You need to download and install the src rpms from broadcom.com for the
BCM570x and BASP module. Then you can do the rpmbuild -bb. Then install
the RPM.
Once that is done, you can install the module and configure teaming.
Alternatively, you can upgrade the kernel to 2.4.2x and use the installed
TG3 drivers with "bonding".
Tim
Tim Pickard
Systems Support Analyst and Administrator
40 Salem Street
Lynnfield, MA 01940
p.781-295-0072
f.781-295-0077
tpickard@xxxxxxxxxxxx
-----Original Message-----
From: JSquire@xxxxxxxxxxxx [mailto:JSquire@xxxxxxxxxxxx]
Sent: Friday, April 30, 2004 12:35 AM
To: redhat-list@xxxxxxxxxx
Subject: bcm5700 and basp
Hi,
Still a bit of a newbie ....
I am trying to install BASP on an IBM HS20 Blade running RHEL ES 2.1 which
requires the bcm5700 driver.
Firstly, when running "rpm -bb SPEC/basplnx.spec" from /usr/src/redhat/ I
get "SPEC/basplnx.spec: No such file or directory". Is this because the
wrong drivers are installed? lsmod shows tg3 - not bcm5700.
Secondly, TG3 and bcm5700 comes with RHEL ES 2.1. I can rmmod tg3 but when
I insmod bcm5700 I get:
"/lib/modules/2.4.9-e.24/kernel/drivers/addon/bcm5700/bcm5700.o:
init_module : No such device" - and yes I have double checked the Broadcom
NIC's are installed ...... ;o)
I only have the base OS installed - no updates/patches yet (we do plan on
patching the OS later). I have seen some threads in this list about creating
a boot.img with bcm5700 for Redhat 9 but seeing that it comes with the RHEL
ES base and that it is allready installed assume this approach is redundant.
Would appreciate any help.
Thanks in advance.
-- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
