Re: Internet setup backfired

["Brian chance" <nborman@chello.at>]

Heh, i tried 212.17.64.0 as a test - 212.17.64.1 is my gateway
(according to what i know, that is)
Ouchie... i thought 212.17.64.255 was the only broadcast address. I
understand that Windows isn't happy when PnP is turned off (I ran the
3com NIC installation for the 3c509b first - i mean, i might be
stupid.. but i'm not *dumb*). I didn't quite understand why you
therefore turn your card out of PnP before booting Windows... was that
a typing mistake or a technical preference?
   As for the problem with the IRQ conflict - i became aware of that
too when trying to install Slackware a while ago (atleast i think it
was Slackware =\) in which the kernel configuratoin reported
conflicting IRQs of the Bios and a network card. Heh, sorry you had to
sacrifice your "nice long message" but don't stress yourself too much
about this incase it never resolves anyway.

> Failing that, how about giving us the contents of the following
files:
> hostname.ep0
> mygate
> resolv.conf

The contents of those files i know by heart now, heh :
hostname.ep0:
inet 212.17.64.12 255.255.255.0 NONE
mygate:
212.17.64.1
(didn't i say the gateway before?)
resolv.conf:
search telekabel.at (i've also tried teleweb.at which is basically the
same thing)
nameserver 195.34.133.10
nameserver 195.34.133.11
lookup file bind



----- Original Message -----
From: Nick Holland <nick@holland-consulting.net>
To: Misc @OpenBSD <misc@openbsd.org>
Sent: Wednesday, January 10, 2001 7:42 PM
Subject: Re: Internet setup backfired


> 212.17.64.0 is a broadcast address, not a gateway.  I would expect
bad
> things to happen if you are using it as a default route.
>
> As I indicated, yes, Windows WILL choke once you turn the PNP off on
> the 3c509B.  Windows sees a 3c509B in PNP mode as a different card
> than a 3c509B in "hard set" mode. You will have to treat it as if
you
> installed a new card (i.e., reset things).  This is one of the
reasons
> I take 'em out of PNP before loading Windows.  It doesn't (by
itself)
> indicate a problem wiht the NIC.
>
> I had actually just wrote a nice long message about basic setup and
> troubleshooting, and thought I should go back and look through the
> dmesg.txt file again...  Found something, um, interesting:
>
> > pcibios0: PCI Exclusive IRQs: 5 10 11
> > pci_intr_fixup: no compatible PCI ICU found: ICU vendor 0x1106
product 0x0596
> > pcibios0: Warning, unable to fix up PCI interrupt routing
>
> Not entirely sure what that is meaning, but it seems to indicate
that
> pcibios thinks irq 10 is its to play with...  I also see your NIC is
> set to 300/10 -- this could be an issue!  You might want to verify
> that IRQ10 is reserved for a "Legacy/ISA" card in your BIOS, and
might
> also want to try the "disable pcibios" trick, see if that helps.
>     http://www.openbsd.org/errata.html#pcibios
>

>
> If you wish to obscure the IPs, I'd understand, but that means YOU
> have to make sure they are right. 8)
>
> Nick.
>
>--
> http://www.holland-consulting.net/
>