It looks like the general response was to boot up with the generic kernel
and then recompile the kernel. Thanks to:
Russel Morison <russel_at_maths.unsw.EDU.AU>
"Dr. Tom Blinn, 603-884-0646" <tpb_at_zk3.dec.com>
Bill Carlson <wcarlson_at_beasys.com>
Oisin McGuinness <oisin_at_sbcm.com>
Ultimately, I wasn't very clear in my original post. I wasn't necessarily
concerned about seeing the card at the OS level. This I would do later
on. I just wanted to put the cards in that morning and then later on
do all the software configuration. The mind boggling thing is that on
my AS4000 the new card prevented the old card from being configured properly.
Like I said, this didn't happen with my Alpha Station 200. Any clues to
why the second card caused the conflict in my AS4000? Is the built in
Ethernet port on the Alpha Station 200 on the PCI bus?
Thanks!
-Dan
ORIGINAL POST:
The other day I attempted to add a second PCI ethernet card (fast Etherworks
PCI 10/100 DE500-AA) to my Alpha Server 4000. I did the same with my
Alpha Station 200. Originally, I thought the 200 was going to give me
the most trouble because I had to move some devices around and I had to
modify some Avdfs domain links. That actually went a lot smoother than
expected. After putting the card in the 4000 I did a 'show config' and
'show dev'. Both commands show that the system can see both cards. But,
when I boot DU4.0b back up it can't seem to find both cards and the one
it does find isn't configured properly. Any hints on what I need to do...
my guess is that this is a simple one...
--
----------------------------------------------------------------------
Daniel David Benson bensond_at_ucdavis.edu
System Administrator http://wwwcsif.cs.ucdavis.edu/~bensond
Social Science Data Service pgp - finger bensond_at_aion.ucdavis.edu
University of California, Davis Linux User
----------------------------------------------------------------------
Received on Mon Mar 16 1998 - 17:27:18 NZST