3c509b on up1000 (again!)

From: Martin Klang (mars@pingdynasty.com)
Date: Fri Jul 14 2000 - 14:37:14 PDT

  • Next message: Rich Payne: "Re: [suse-axp] 3c509b on up1000 (again!)"

    Date: Fri, 14 Jul 2000 22:37:14 +0100 (BST)
    From: Martin Klang <mars@pingdynasty.com>
    Message-ID: <Pine.LNX.4.21.0007142209370.31140-100000@martink>
    Subject: 3c509b on up1000 (again!)
    

    Hi all,

    a couple of weeks ago i posted the following on suse-axp ->

    <snip>
    > i've just installed a 3c509b on my up1000, ide hd, agp graphics, SuSE
    > 6.3 AXP, kernel 2.2.16.
    >
    > modprobe detects the device correctly, then i can configure it with
    > ifconfig and add a route w/o problems.
    >
    > though it doesn't send/receive any packets - can't even ping over it.
    >
    > i've not seen any indication - log output or similar - to why it's not
    > working.
    > i've tried the exact same configuration - even with the same card - on a
    > pc running RedHat and it works fine. and yes - i've triplechecked the
    > cables, twice.
    > dope:~ # ifconfig
    > eth0 Link encap:Ethernet HWaddr 00:20:AF:CC:DF:56
    > inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
    > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    > RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    > TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
    > collisions:0 txqueuelen:100
    > Interrupt:10 Base address:0x300
    > dope:~ # ping 192.168.0.5
    > PING 192.168.0.5 (192.168.0.5): 56 data bytes
    >
    > --- 192.168.0.5 ping statistics ---
    > 3 packets transmitted, 0 packets received, 100% packet loss
    </snip>

    i eventually checked the suse support db (which of course i should have
    done before posting.. ) and there was at least one mention of the 509 - to
    the effect that i have to switch off pnp and autoselect.
    so i downloaded the conf utility from 3Com, installed msdos(!) and the
    card in a pc and found that hey, both pnp and media autoselect were both
    already disabled.

    so i thought it could be an irq problem - although /proc/interrupts said
    the current irq (10) was free i changed it to 7 and put it back in the
    alpha. the module was correctly detected - irq and dma - and as usual no
    problem with setting up i/f and route.
    though when trying to ping, the machine locked up completely - not even
    SysRq worked.
    then i tried irq 11, with the exact same non-result as with 10 -
    everything seems to work, but no packets get across - incoming or
    outgoing.

    then i thought it could be suse-specific, so i got RedHat6.2 with kernel
    2.2.14 -> same result.

    i've also tried compiling the driver in the kernel, no difference.

    i'm getting really rather tired of not getting _anywhere_ on this - clues
    any one?
    has no-one ever used a 3c509 on the up1k - or similar - platform?

    oh and btw, AlphaBIOS does not detect the card at all, but that shouldn't
    be significant should it??

    any and all help appreciated, even if it's 'get rid of that pice of junk
    and by a xxx'!

    /martin



    This archive was generated by hypermail 2.1.0 : Mon Jun 04 2001 - 04:18:25 PDT