On Sun, Feb 04, 2001 at 09:20:53PM -0500, Jonathan D. Proulx wrote:
> Damn! I should have that tatooed on my eyelids. Now that you mention it
> I've had the same problem (twice), both times it took days of hair pulling
> to finally flip the right setting, and here I was cruising for a third...
On Sun, Feb 04, 2001 at 09:00:29PM -0500, Michael P. Soulier wrote:
:Ok, after pouring over news postings, we managed to find someone with a
:similar problem. Apparently having the BIOS set to support PNP isn't always a
:good thing when it comes to tulip. I disabled PNP in the BIOS, and magicka
Ok, after pouring over news postings, we managed to find someone with a
similar problem. Apparently having the BIOS set to support PNP isn't always a
good thing when it comes to tulip. I disabled PNP in the BIOS, and magickally
it came up on irq 10 and it works!
Cheers,
Mike
--
Mich
On Sun, Feb 04, 2001 at 05:27:24PM -0500, Jonathan D. Proulx wrote:
> This means you did a "modprobe tulip" and it went OK? does "lsmod" show it
> as listed?
Yes, it's loaded.
> you'll need to add "up" to the end of ifconfig line, though with that error
> it won't help yet.
I've never
On Sun, Feb 04, 2001 at 01:53:40PM -0500, Michael P. Soulier wrote:
:Hey again people. Well, I still couldn't get the damn tulip module loaded
:if I compiled it on the target platform, version information complaint again.
:I downgraded to the 2.2.12 kernel which is running on my gateway/firewal
Hey again people. Well, I still couldn't get the damn tulip module loaded
if I compiled it on the target platform, version information complaint again.
I downgraded to the 2.2.12 kernel which is running on my gateway/firewall
where it's working fine. Same kernel, makefile, sourcecode, everythin
6 matches
Mail list logo
