via-rhine problems with dlink DFE-530TX

From: ScruLoose (scruloose+debuser_at_eastlink.ca)
Date: 10/30/03

  • Next message: Pigeon: "Re: Simple little basic config questions"
    Date: Thu, 30 Oct 2003 16:16:36 -0500
    To: Debian User <debian-user@lists.debian.org>
    
    
    

    Hi again, folks,

    I have this kind of ongoing issue with a machine that's got a
    pretty-much clean install of woody, and has a D-Link DFE-530TX NIC in it
    that doesn't want to play nice with Debian.

    When I configure it all up manually (specifying an IP and netmask on the
    ifconfig command-line and doing a route add for my default gw) and then
    ping my gateway, it lags for a while and then spits out this:
      PING 192.168.1.1 (192.168.1.1): 56 data bytes
      NETDEV WATCHDOG: eth0: transmit timed out
      eth0: Transmit timed out, status 0000, PHY status 786d, resetting...
      eth0: Reset not complete yet. Trying harder.
      eth0: Setting full-duplex based on MII #1 link partner capability of 45e1.
      
      --- 192.168.1.1 ping statistics ---
      17 packets transmitted, 0 packets received, 100% packet loss

    As I mentioned in an earlier post, I _know_ the hardware is good,
    because under Knoppix it works like a charm. And I'm _pretty_ sure that
    I've ironed out the wrinkles that were due to my (mis)configuration...
    Knoppix is using a 2.4.21 kernel. My woody install is currently using
    2.4.22 from kernel.org source, though I've also tried the bf24 kernel
    and 2.4.21 from debian source.

    At this point, I can only think of three things it might be:
     - Knoppix using some patches to the kernel or driver
     - My custom kernel has some option that conflicts with via-rhine
     - Knoppix is passing some arguments to the module

    So now I'm trying to dismantle the process to see if I can figure out
    which it is. Starting with arguments passed to the module, 'cause it
    seems easiest (and maybe most likely?)...

    dmesg under knoppix (where the card works) shows this:
      via-rhine.c:v1.10-LK1.1.17 March-1-2003 Written by Donald Becker
        http://www.scyld.com/network/via-rhine.html
      PCI: Found IRQ 11 for device 00:0b.0
      eth0: VIA VT6105 Rhine-III at 0xe8000000, 00:05:5d:75:3c:e1, IRQ 11.
      eth0: MII PHY found at address 1, status 0x7869 advertising 05e1 Link 45e1.

    dmesg under woody (where I get the error shown above) shows this:
      via-rhine.c:v1.10-LK1.1.19 July-12-2003 Written by Donald Becker
        http://www.scyld.com/network/via-rhine.html
      PCI: Found IRQ 11 for device 00:0b.0
      eth0: VIA VT6105 Rhine-III at 0x6800, 00:05:5d:75:3c:e1, IRQ 11.
      eth0: MII PHY found at address 1, status 0x7869 advertising 05e1 Link 45e1.

    Now, I'm noticing it says "VIA VT6105 Rhine-III at" different values...
    I dunno what that means but it kinda doesn't smell right.

    Is that value something I can/should be passing as an argument to the
    module? Is it the io argument? Does it look like a plausible cause for
    my problem?

    Oh, and is it possible to pass arguments to a compiled-in driver, or do
    I have to go back and compile again with via-rhine as a module?

    Other suggestions? Ideas?

            Thanks!

    -- 
    ,-------------------------------------------------------------------------.
    >   -ScruLoose-   |     I don't want to start any blasphemous rumours     <
    >  Please do not  |   but I think that God's got a sick sense of humour   <
    > reply off-list. |                     - Depeche Mode                    <
    `-------------------------------------------------------------------------'
    
    

    -- 
    To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
    


  • Next message: Pigeon: "Re: Simple little basic config questions"

    Relevant Pages

    • Re: Kernel installation woes on Athlon 1100: "hda: lost interrupt".
      ... > to see any Linux boot without noapic. ... Including Knoppix, and Woody on ... kernel that worked without it was the 386 version, ...
      (Debian-User)
    • bug in kernel (I think): 2.6.15 to 2.6.17 and 3c59x driver
      ... I'm unsure whether this is kernel or driver? ... I've been using Knoppix for some time and they have worked great. ... kernel issue, so I installed Debian 3.0 on machine from the Woody DVD ... Should I report it as kernel or driver? ...
      (Debian-User)
    • Re: booting from ISO image on HD?
      ... You still have to boot your kernel or its bootloader, ... I get the idea - your boss wants you to package a knoppix image for ... booting from harddisk as a single drop-in lump/package on disk. ...
      (comp.os.linux.misc)
    • Re: 2.4.30 & 2.4.32 kernel comple error
      ... Or is trying to compile for an older machine on a newer ... Age of the box is one thing: Age of the gcc, glibc, existing kernel ... I'm running debian 3.1 on the pentium machine, and DSL (knoppix) on ...
      (comp.os.linux.setup)
    • Re: messed up mbr- unable to boot
      ... > set root to my Woody partition. ... > grub, reset the MBR with the 'update-grub' command, and rebooted. ... Woody to Sarge and forgot to run lilo. ... right kernel etc. and run lilo as root. ...
      (Debian-User)