Hi,
I must admit I only thought I knew how things worked. I was under the
apprehension that as long as you had at least one instance of a particular
driver loaded then you could handle the situation where devices were located
in different slots. This logic appeared to work on the 500/400 where the
tulip ethernet driver was loaded via the following entry in the config file
controller tu0 at pci0 slot 6
and upon inserting the extra ethernet card and rebooting the tu1 card was
detected. This is all you need to then run doconfig to generate a specific
kernel.
However on the 500/333, even with the same firmware revision, and operating
system version, this procedure failed.
Dr Blinn's comment:
You didn't spell out the specific details of why you think the kernel you
are booting on each system should be able to find the card, but the tulip
driver in V4.0E is NOT, as far as I know, dynamic with regard to the number
of options it supports, and a kernel that is tailored to the system usually
can only support the options that were installed when it was built, and only
in the physical locations where they were found at build time.
Thanks to all the people who nailed it with the correct answer, that I
should have booted genvmunix.
The original question:
> I just put an ethernet SN-DE500-BA (ie a tulip 10/100mbs) into an
> AlphaStation 500/400 and everything worked fine, the card was recognised
at
> the console command level as ewb0, and uerf indicated that the device was
> detected during boot. I was able to configure the new card and swap the
> cable over from the 10mbs standard card to the 10/100mbs card.
>
> However when I added the same model card to an AlphaStation 500/333, I had
> no joy. The card was recognised at the console command level as ewb0, I
was
> able to set the ewb0_mode to auto-negotiate, but uerf indicated that the
> device was not detected during boot. This was confirmed by the fact that I
> had not seen any tu1 messages during boot. The operating system on both
the
> 500/400 and the 500/333 is v4.0E, and the firmware is also the same (the
> firmware that came with v4.0F).
>
> The 500/333 has 4 pci slots on a riser (similar to the 500/400), the first
> is a 64 bit slot and the rest are 32 bit slots. The original configuration
> had the video in the 1st slot (64 bit slot) and a scsi in the 4th slot
> (unlike the 500/400 where the scsi is in the 2nd slot). I tried the
ethernet
> card in both the 2nd and 3rd slots to no avail.
>
> If anyone knows the definitive answer as to whether the ethernet card
should
> or should not work I'd be interested.
Dennis
######################################
Dennis Macdonell
Systems Administrator
email: mcdonell_at_auslig.gov.au
ph: 61 2 6201 4326
######################################
Received on Mon Dec 13 1999 - 03:23:38 NZDT