On Wed, 23 Feb 2000, you wrote:
> What does USB have to do with this? I understand how diabling USB would free
> up an IRQ, but this Intel nic will always take IRQ11 unless I find a way to get
> the DOS setup program to run. It doesn't even run when I shutdown and reboot
> in MS-DOS Mode. (Intel is no help, BTW. I've had a message posted on their
> support forum for 2 weeks without a reply.)
Possibly dosemu could help you run the dos setup program? Mine came with the
computers (in which they didn't work) with no setup proggies at all.
>
> Lastly, someone suggested that I might have an el-cheapo motherboard that isn't
> handling PCI right. Possible, but shouldn't be. I have a Soyo 5EHM v1.1 with
> Award BIOS v4.51PG on a VIA MVP3 chipset. It is supposedly PCI2.1 compliant.
> But it does do some weird stuff with it's drivers. One of the Windows drivers
> that come on the installation disk with the mobo is a "IRQ Remapping utility",
> so maybe it's IRQ's are all messed up.
>
I have a Shuttle with a VIA MVP3 Chipset and I do recall having to DL and flash
the BIOS to get an intel i740 to run AGP video for me. Check into possible
BIOS upgrades at http://www.via.com.tw.
> Finally, before I go buy a 3com nic. Can I set the IRQ on a 3com PCI nic?
> Preferably from Linux or Windows (I am rarely not disappointed by DOS.) It
>will have to be able to use an IRQ other than the traditional IRQ10, because
>it's already taken (by some serial motherboard resource, I don't recall which
>one). If not, I'll buy a 10BaseT ISA nic and sacrifice 10/100 compatibility for
> one that I can set the IRQ on and actually use.
On that Shuttle HOT-591 which uses the same VIA Chipset, I am running a 3Com
Vortex 3C591 and interrupts shared never became an issue. It selected an
available interrupt itself. I did once have Windows running on that same
machine with the same cards, so I can state that windows settings, if it made
any, did not cause a problem. I suppose I had best bite the bullet and buy
another Windows distro since I don't have any and I am having difficulty
duplicating errors some of the dual-boot people are getting.
But before going further, make sure that your driver module is loading
properly. Use linuxconf->Networking->Adapters->[set IP addr, hostname, eth0,
and module (eepro100) then tick "enable"] and quit with the quit buttons or
modprobe eepro100
ifup xxx.xxx.xxx.xxx
where the xxx's are some IP address and see if you can ping something.
My shared interrupt problem appeared when I did the ping--my screen flickered
out and on and out and on and everything was unresponsive --couldn't ctrl-c
from the ping while the logic race was on, then the screen blanked and the
computer was in a coma. Kernel panic would have stopped things and made the
screen visible, so it was a lock-up but not a crash, and of course nothing from
outside could get through the busy eth0.
Definitely sharing ISR vectors between modems and something else is a poor
idea, and between ethernet and other things is ... less than efficient.... yet
why are we getting PCI interrupts on the same line giving us a total lockup?
Now you have picqued my interest.... If have time, I will examine the ISRs of
the two devices...
Civileme
> --
> Jeremy Kersenbrock
> [EMAIL PROTECTED]
