T.R | Title | User | Personal Name | Date | Lines |
---|
1285.1 | Don't use SCU | NETCAD::THOMPSON | | Wed Mar 19 1997 15:46 | 13 |
|
Why are you trying to change the interrupt on the second card?
You should not have to run a configuration utility for PCI cards.
What happens if you shutdown, pull the card out, reboot, shutdown,
and then re-install the card and boot without running the config
utility?
regards,
-Brenda
|
1285.2 | Try it again.... | NETCAD::HILLER | | Wed Mar 19 1997 21:29 | 6 |
| Try removing the adapter, rebooting the system, then try adding the
adapter in again. I'm not sure why it would load with no bindings. The
interrupt shouldn't have anything to do with your problem.
-Brent
|
1285.3 | What I did and the results... | NETRIX::"[email protected]" | Dwayne Zicolella | Thu Mar 20 1997 16:42 | 25 |
| Here is what I did:
Removed the adapter driver and shut the machine down.
Removed the de450 card.
Booted to the SCU and reset the PCI slot to the default setting
(NONE instead of ONE IRQ REQUIRED)
Rebooted to NT. Made sure DE435 was functioning properly.
Shutdown NT. Added DE450 card. Booted to NT.
Added DE450 driver in Control Panel > Network > Adapter > Add
NT said this driver was already loaded (Using the 21040 driver for DE435).
Said yes to load anyway.
Rebooted server. Checked Control Panel > Network > Bindings > to adapters
Only 21040 shows up. DE435 works fine. DE450 will not do ping or netbeui.
A piece of software I acquire from ZSO call PCI Configuration shows the DE435
at IRQ 5 and the DE450 at IRQ 0.
Have also tried 21041 driver in place of de450 driver.
[Posted by WWW Notes gateway]
|
1285.4 | | NETCAD::STEFANI | FDDI Adapters R Us | Thu Mar 20 1997 22:42 | 27 |
| >>Booted to the SCU and reset the PCI slot to the default setting
>>(NONE instead of ONE IRQ REQUIRED)
While it's true that many PCI BIOS's are "plug-and-play", it looks like yours
isn't. You must set "ONE IRQ REQUIRED" for the PCI slot containing the DE450,
else it won't have an IRQ assigned by the BIOS during boot.
Additionally, you should be able to select an advanced option (e.g. hitting the
F6 or F1 keys) and change the default IRQ assignment to something that you KNOW
is not being used by ANY other device in the system.
>>A piece of software I acquire from ZSO call PCI Configuration shows the DE435
>>at IRQ 5 and the DE450 at IRQ 0.
That behavior is certainly expected if the BIOS purposefully did not assign an
IRQ to the PCI slot containing the DE450.
Rerun the SCU, enable the DE450 PCI slot, select "ONE IRQ REQUIRED", and look
into any advanced SCU options which will allow you to select the precise IRQ
that will be assigned.
>>Have also tried 21041 driver in place of de450 driver.
Either driver won't make a difference in this case. The NT drivers are
"slaves" to the resource assignments made by the BIOS or OS.
- Larry
|
1285.5 | setting irq... | NETRIX::"[email protected]" | Dwayne Zicolella | Tue Mar 25 1997 14:10 | 19 |
| I have set the irq to 15 (SCU and NT show it as not in use) and rebooted.
There has been no change in network functionality.
Options to try are:
1) other irqs
2) other de450
3) other pci slots
4) other pci bus
5) eisa network card
6) third party network card
I will be giving some of these a try later this week.
My fear is that the problem has something to do with the same driver
being used for the entire family of network chips.
Any comments are welcomed.
[Posted by WWW Notes gateway]
|
1285.6 | | NETCAD::STEFANI | FDDI Adapters R Us | Tue Mar 25 1997 15:23 | 13 |
| >>My fear is that the problem has something to do with the same driver
>>being used for the entire family of network chips.
In general, that's not a problem. The DC21X4.SYS driver, for example, was
designed around supporting all of the DC21x4 10Mbps and 10/100Mbps Ethernet PCI
chips. However, it's certainly reasonable to expect a DC21X4.SYS driver built
today might not support an upcoming DC21x4 chip.
This is why driver updates become so important as you undergo system changes or
plug-in option changes. The latest DC21X4.SYS driver should be able to support
both of the interfaces you're dealing with.
- Larry
|