I'm the guy who suggested perhaps a low-grade motherboard. Personally am not
impressed with Soyo. I have used Intel motherboards for 8 years without incident or
flakiness. (in some cases the =same=ones= for 8 years) But wouldn't buy their NIC,
now. Get some new parts, dead busted cheap, on eBay.
The reason you do not have the choice in BIOS to select PCI interrupt, is that yours
is in fact a =newer= motherboard and handles all PCI PnP. (PCI 2.1) You do not (and
should not) have control anywhere... with quality products, PCI PnP works. PCI
mapping results are passed along to the OS on boot. You can tell Linux (kudzu?) to
autoprobe, and it should easily find the NIC.
(Toss spitballs here)
Needless to say, PCI interrupts cannot be shared with ISA devices (I'm not accusing
you of this) and normally interrupts are only shared on PCI devices when the BIOS
has run out of assignable interrupts. If you are not out of interrupts, whether the
fault is with the MB or with the NIC is a question.
Anybody know why you can't add a new fonts path in M7.0-2?
Hey MandrakeSoft... what happened to my posting on setting up security additional to
MSEC?
--
Carl A. Cook
quantumATaugustmailDOTcom
Sign the petition at http://www.libranet.com/petition.html
Help bring us more Linux Drivers
Jeremy Kersenbrock 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.)
>
> Before I installed my problem eepro100, I installed another one in a machine
> withough AGP, and it worked fine. I started with several free IRQ's (7, 10, and
> 11 if I remember correctly), and it took 11.
>
> I cannot change the IRQ's in my BIOS. My only BIOS options are to select
> "Legacy ISA" or "PCI/ISA PnP" for each IRQ. Needless to say, changing IRQ11
> from "PCI/ISA PnP" to "Legacy ISA" will only result in the nic (and likely my
> AGP card also) not working 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.
>
> 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.
>
> Thanks for all the info.
> Jeremy
>
> On Wed, 23 Feb 2000, you wrote:
> > On Wed, 23 Feb 2000, Jean-Louis Debert wrote:
> >
> > > Rich Clark wrote:
> > > >
> > > > On Tue, 22 Feb 2000, Jean-Louis Debert wrote:
> > > > Re-read the thread *carefully*. He's already told us that it's not
> > > > jumpered and there's no software config available.
> > >
> > > Please read again yourself: what about this "DOS setup program"
> > > he talks about ???
> > >
> > >
> > >
> > >
> >
> > From my own re-read, Jeremy says the dos setup program won't run on his
> > computer, "... stupid DOS." Maybe I misspoke... it's there but won't
> > function for him. Without it being able to function, there's no way he
> > can set the io and irq manually. Again, there should be a way to setup in
> > BIOS which irq the bloody thing will grab at the very least or he could
> > disable the USB. I would think that will at least get the damned thing
> > up without too much problem, at least until 2.4 is released with the final
> > USB support.
> >
> > --
> > Rich Clark
> >
> > Sign the petition at http://www.libranet.com/petition.html
> > Help bring us more Linux Drivers
> --
> Jeremy Kersenbrock
> [EMAIL PROTECTED]
