[tulip] Interrupt resources are pending! <- ?

Max Pakhutkin mpakhutkin@telocity.com
Sat, 30 Sep 2000 19:42:58 -0700


Ok, I've recompiled the kernel and now can boot to both versions. I used
kernel-source-2.2.17-pre6.1.deb for the source (the only one on the cd that
had 2.2.17, all the rest of the sources were older). Then I successfully
compiled all the drivers from netdrivers.tgz. Pci-scan.o gets loaded fine.
But modprob reports unresolved symbols for tulip.o under *both* kernels. I'm
lost. What could be wrong?

Max.


----- Original Message -----
From: <mpakhutkin@telocity.com>
To: Donald Becker <becker@scyld.com>; Max Pakhutkin
<mpakhutkin@telocity.com>; <tulip@scyld.com>
Sent: Wednesday, September 27, 2000 12:30 AM
Subject: Re: [tulip] Interrupt resources are pending! <- ?


> Thanks a lot. I made wrong assumptions due to lack of understanding of
issues involved.
>
> I'm still working on it. At least I got the new drivers to compile. As it
turned out I
> didn't have /usr/src/linux/. I'm a little puzzled by the fact that
compiling the drivers
> with the header files provided by kernel-source-2.2.17.deb AND compiling
them with the
> headers found in /usr/include produces the same result in 'insmod tulip',
which leads me
> to believe that the contents of /usr/include don't correspond to my
running kernel. Is
> that possible? Well, I'm getting unresolved symbols with insmod, so I'll
have to check the
> version of the kernel tonight and will probably recompile it, if only for
practice.
> Reinstalling Debian with dselect is not that much fun after all.
>
> Max.
>
>
> > On Mon, 25 Sep 2000, Max Pakhutkin wrote:
> >
> > > Card: Linksys LNE100TX
> > > Dist: Debian 2.2.17
> > > Problem: modprobe reports 'Device busy' while tulip-diag reports
'Interrupt
> > > resources are pending!'
> >
> > The "Device busy" message is a misleading way of reporting the driver
> > couldn't find a recognized device.
> > (Not my fault!  The driver returns ENODEV.)
> >
> > I suspect that you are using an old driver.  Get a recent driver from
> >    http://www.scyld.com/network/tulip.html
> >       ftp://www.scyld.com/pub/network/tulip.c
> > and follow the directions at
> >    http://www.scyld.com/network/updates.html
> >
> > > After two full days of intensively studying this site's resources I've
> > > finally managed to put my card into interrupt 7 (instead of 15, which
it
> > > used to hang out in, but tulip-diag was reporting Unknown Error: 7
which
> >
> > Ehh, I don't know that this is a problem.
> > Get the driver to recognize the card before you look for other problems.
> >
> > > tulip-diag.c:v2.03 7/31/2000 Donald Becker (becker@scyld.com)
> > >  http://www.scyld.com/diag/index.html
> > > Index #1: Found a ADMtek AL985 Centaur-P adapter at 0xf800.
> >
> > This chip will not be found by older drivers.
> >
> >
> > Donald Becker becker@scyld.com
> > Scyld Computing Corporation http://www.scyld.com
> > 410 Severn Ave. Suite 210 Beowulf-II Cluster Distribution
> > Annapolis MD 21403
> >
>
>