pcnet32: eth0: transmit timed out, status 97fb, resetting - NIC card problem solution

I've encountered this problem before and I believe it  may affect other drivers (I could test but I don't have time).  This was happening on my custom Linux system with the pcnet32 driver.

pcnet32: eth0: transmit timed out, status 97fb, resetting (and some other kernel module tracing in dmesg)

Basically it means the card is connected (it shows connected in full duplex etc.. and recognized if the cable is disconnected too) but no packets can be sent or received.  I've read people say they think it's a bad card (I've actually threw some of these cards away in the past, thining the same thing!, others commented they believed the card was dead/bad or that it wasn't seated properly in their situation but I think it is likely the IOAPIC issue they found) but it's a driver/IOAPIC issue.

This was tested with a VBOX/Virtualbox machine but it seems to apply equally to physical machines (based on what I've read elsewhere).  If you have IOAPIC enabled, this driver won't work until it's disabled.

Now, the tricky thing is that with some computers and in VBOX, Centos 5 and possibly other Linux/OS won't boot successfully.

So here are the solutions for this issue:

1.) Disable IOAPIC in the motherboard (but some OS's won't boot without IOAPIC enabled).

2.) Specify the kernel option "pci=noapic" and it will work.

I hope this helps others out as I believe I've run into this issue unknowingly in many situations over the years.

One more comment is that on the very same system, I changed the NIC to an Intel and this issue did not happen with the Intel NIC (even with IOAPIC enabled), so this appears to mean that the pcnet32 driver is garbage/has an issue with IOAPIC on systems.


Tags:

pcnet, eth, transmit, timed, fb, resetting, nic, solutioni, ve, encountered, drivers, custom, linux, kernel, module, tracing, dmesg, duplex, etc, disconnected, packets, thining, commented, wasn, seated, ioapic, vbox, virtualbox, equally, elsewhere, enabled, disabled, tricky, centos, os, successfully, solutions, disable, motherboard, specify, quot, pci, noapic, unknowingly, intel,

Latest Articles

  • How to combine .txt ACLs without breaking things
  • How to ping all of Googlebot's IPs script
  • 'virtio0' uses a qcow2 feature which is not supported by this qemu version: QCOW version 3
  • Linux bash script to get the IP of a list of hostnames
  • How To Use Camera Webcam in Docker for OBS Studio etc...
  • Computer Server Won't Post Boot Or Enter BIOS Setup After Installing RAID SAS or GPU Card etc..
  • How To Test PHP Scripts from CLI with GET variables/query string
  • apt-cache how to see all available versions of a package in Debian Ubuntu Mint
  • Virtualbox VBox Guest-utils drag and drop files stops working with Windows VMs
  • How To Remove Ubuntu Netplan and Go Back to /etc/network/interfaces
  • How To Force Flash an AMD Instinct GPU To Another Model Using Debian Ubuntu Mint Linux
  • How To compile ollama from source to use unsupported AMD GPU with rocm in Ubuntu Debian
  • QEMU KVM Virtio GPU Windows Cannot Select 1080P
  • Linux Gnome Desktop Ubuntu Mint Debian Gets Slower After Weeks
  • Firefox How to Save Full Page As Screenshot/PDF
  • Nvidia Datacenter Driver Tesla Slow nvidia-smi response and high utilization with 0 usage
  • ffmpeg how to normalize / increase the volume of your audio
  • kdenlive audio blips pops cracks artifacts solution fix
  • haproxy / nginx certbot SSL issues
  • nginx how to see the real IP when behind a CDN