hey all...i'm not really sure what's relevant and what's not, so i'm gonna post a lot of logs...but first some background

i'm dual booting windows and debian 3.1 on my machine, it's a amd duron...getting old but a trooper nonetheless. anyway, my old debian was running on the 2.4 kernel, and i recently formatted my debian partition in light of switching distros, but eventually decided to stick with debian, but use the 2.6 kernel instead (2.6.8-2 to be precise). everything went ok, except my dlink dfe 530 (note: not the 530+) doesn't work...or maybe the module isn't working(the chipset is VIA Rhine III, the module name is via-rhine..yes it shows up in lsmod)...or maybe something else...either way, when i run dhclient, it freaks out. (i elaborate on freaking out below, from syslog)


FROM DMESG**************
// heres where it figures out the IRQ or whatever
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 6
ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 6 (level, low) -> IRQ 6

//and here's the eth0 part
eth0: VIA Rhine III at 0x9400, 00:0d:88:f6:ac:cb, IRQ 6.
eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1.


SOME (POSSIBLY) RELEVANT BITS FROM FROM LSPCI**********
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP]
0000:00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40)


0000:00:04.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
0000:00:0a.0 Ethernet controller: VIA Technologies, Inc. VT6105 [Rhine-III] (rev 86)


ok now here's the juicy part from syslog, after i run dhclient.....
FROM SYSLOG***********
Jan 10 04:07:37 exmachina kernel: irq 6: nobody cared!
Jan 10 04:07:37 exmachina kernel: [__report_bad_irq+49/115] __report_bad_irq+0x31/0x73
Jan 10 04:07:37 exmachina kernel: [note_interrupt+76/111] note_interrupt+0x4c/0x6f
Jan 10 04:07:37 exmachina kernel: [do_IRQ+146/249] do_IRQ+0x92/0xf9
Jan 10 04:07:37 exmachina kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20
Jan 10 04:07:37 exmachina kernel: [__do_softirq+44/115] __do_softirq+0x2c/0x73
Jan 10 04:07:37 exmachina kernel: [do_softirq+34/38] do_softirq+0x22/0x26
Jan 10 04:07:37 exmachina kernel: [do_IRQ+229/249] do_IRQ+0xe5/0xf9
Jan 10 04:07:37 exmachina kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20
Jan 10 04:07:37 exmachina kernel: [setup_irq+168/205] setup_irq+0xa8/0xcd
Jan 10 04:07:37 exmachina kernel: [__crc_uts_sem+22934/1933892] rhine_interrupt+0x0/0x14e [via_rhine]
Jan 10 04:07:37 exmachina kernel: [request_irq+140/162] request_irq+0x8c/0xa2
Jan 10 04:07:37 exmachina kernel: [__crc_uts_sem+21465/1933892] rhine_open+0x3a/0x12d [via_rhine]
Jan 10 04:07:37 exmachina kernel: [__crc_uts_sem+22934/1933892] rhine_interrupt+0x0/0x14e [via_rhine]
Jan 10 04:07:37 exmachina kernel: [dev_open+96/197] dev_open+0x60/0xc5
Jan 10 04:07:37 exmachina kernel: [dev_change_flags+74/238] dev_change_flags+0x4a/0xee
Jan 10 04:07:37 exmachina kernel: [devinet_ioctl+591/1268] devinet_ioctl+0x24f/0x4f4
Jan 10 04:07:37 exmachina kernel: [inet_ioctl+69/111] inet_ioctl+0x45/0x6f
Jan 10 04:07:37 exmachina kernel: [sock_ioctl+575/611] sock_ioctl+0x23f/0x263
Jan 10 04:07:37 exmachina kernel: [sys_ioctl+461/532] sys_ioctl+0x1cd/0x214
Jan 10 04:07:37 exmachina kernel: [syscall_call+7/11] syscall_call+0x7/0xb
Jan 10 04:07:37 exmachina kernel: handlers:
Jan 10 04:07:37 exmachina kernel: [__crc_uts_sem+22934/1933892] (rhine_interrupt+0x0/0x14e [via_rhine])
Jan 10 04:07:37 exmachina kernel: Disabling IRQ #6
Jan 10 04:07:37 exmachina kernel: eth0: Setting full-duplex based on MII #1 link partner capability of 45e1.
Jan 10 04:07:47 exmachina kernel: eth0: no IPv6 routers present
Jan 10 04:08:18 exmachina kernel: Disabled Privacy Extensions on device c02cc960(lo)
Jan 10 04:10:34 exmachina kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jan 10 04:10:34 exmachina kernel: eth0: Transmit timed out, status 0003, PHY status 786d, resetting...
Jan 10 04:10:34 exmachina kernel: eth0: Setting full-duplex based on MII #1 link partner capability of 45e1.
************************************


just another couple notes on what i've tried....someone recommended i try booting with the noapci kernel option, but that didn't change anything...


"IPv6 over IPv4 tunneling driver" is at the end of my dmesg...add that to "no IPv6 routers present" from the dhclient output....i know nothing about the IP versions, but could that mean something?

anyway, i've been stuck for days now on windows, which i normally only use for gaming, and it's making me feel naseous.....so save a kitten and help a linux user with a problem instead!

well, IPv6 is something entirely different to the networking your used to. Its aimed at relpacing (IIRC) the current IP scheme - so likely you don't need that. That makes me think that something wasn't configured right. Did you compile and make this kernel yourself? If so, we may have something missing...

no i didn't, i just worked through the debian installer, and it never asked me anything about ipv6...i'm not even sure that's the problem, i just took a wild shot in the dark. someone on freenode told me that "no ipv6 routers found" is normal.

also, i was googling around and found something vaugely similar to my problem @ linux.derkeiler.com/Mailing-Lists/Debian/2003-11/0047.html

except like i said, i've already tried booting with noapic and it doesn't help...and his doesn't say anything about the eth0 irq - also, i'm using dhcp and he's just using ifconfig/route to set it up statically (which i tried, to no avail)

seems like this guy is having the same problem...same network card, same kernel, @ 216.239.51.104/linux?q=cache:AuUJBMeRQRYJ:transamrit.net/files/logsLinuxhelp/linuxhelp.log.20050608+kernel+2.6+dlink+via-rhine+dhclient&hl=en

blockquote----
spike, it's a dlink 530tx card, rev. a. [09:53] it uses a via chipset. via-rhine is the module. it's the same card that's in my server and it works fine. the only difference is the server is slackware.. this is debian. [09:53] spike, i don't even know.. force it to work.. hehe. meh. [09:54] nerd: same kernel? [09:54] the via driver might be buggy in that version [09:54] nerd: also, why do you see it doesn't work? what does it say when you do ifconfig eth0 up? [09:55] #linuxhelp (+ctrn) : [m/133 o/0 h/0 v/0 n/133 b/2 e/- I/-] [09:55] spike, actually, no, it's not. the server uses 2.4 and i selected 2.6 for debian. perhaps that's crap
-------------

so yea, he doesn't figure it out, and he seems much smarter than me.

ok i've got some shocking new developments...

first i yanked out my dlink and threw in a linksys network everywhere NIC, and threw in the ubuntu live cd. surprise surprise, the linksys card also didn't work....all that complaining about IRQ 6 from dhclient got me thinking, so i took out the linksys, and put the dlink in the only other pci slot i could....the BIOS immidiately complained that it was now sharing an irq with an ide controller, and to make sure the device supported irq sharing.

i ignored this, and booted ubuntu...surprise again, here i am typing this post on linux, kernel 2.6.

so what's going on? kernel 2.4 and windows is ok with the PCI slot i chose for my NIC, but kernel 2.6 isn't??

this is gonna sound weird...but could not having a module for my floppy drive loaded affect my network? my floppy drive is broken, and when auto-installers try probing it, my system usually hangs...so i usually specify to not load the floppy module....and look what i found at the end of my dmesg from ubuntu

[4294794.687000] floppy0: Unable to grab IRQ6 for the floppy driver

also, when detecting network hardware, the debian installer asks me to load the floppy module...

maybe the floppy and my nic are fighting for an irq? or something? anyway, i'm gonna rip out my floppy and play around a bit more and get back to you guys....anyone have any ideas, please share them i'm clueless

so yea i pulled out my floppy...everything seems to be working now. i don't understand, but i don't care...

cheers

that's really rather funny and odd at the same time. Thanks for sharing, hopefully that's something to look for in the future.