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

  • QEMU-KVM soundhw deprecated how to enable sound in QEMU 4.x series
  • Virtualbox Error Cannot register the hard disk because a hard disk with UUID already exists solution
  • kernel: [549267.368859] mate-terminal[7871]: segfault at 2000000101 ip 00007f5d0a9548f0 sp 00007fff7012c610 error 4 in libgobject-2.0.so.0.4800.2[7f5d0a920000+52000]
  • apcupsd how to setup and monitor APC UPS units
  • How To Password Reset, Recover, Bypass, Remove and Unlock on Windows 10,8,7,Vista,XP,NT,2000,2003,2008,2012,2016,2019 Administrative Login Programs
  • Nvidia Ubuntu Linux Screentearing Video with solution driver
  • ?? Question Marks for time, permissions and size of a file?
  • mdadm how to stop a check
  • access denied by acl file qemu-kvm: bridge helper failed
  • Linux NIC connecting at 100M instead of 1000M gigabit speeds? It could be overheating
  • "This kernel requires the following features not present on the CPU: cmov Unable to boot - please use a kernel appropriate for your CPU.
  • http://vault.centos.org/5.9/os/i386/repodata/filelists.xml.gz: [Errno -1] Metadata file does not match checksum solution
  • Linux Ubuntu Wifi Disabled Only Works When Laptop Plugged Into Wall AC Power
  • CentOS 6 impossible to compile a newer libguestfs
  • chroot
  • How To Get Started on Ubuntu with gpt-2 OpenAI Text Prediction
  • Remove cloud-init in your VM
  • QEMU-KVM KVM Command Line Practical Guide
  • Linux How To Change NIC Name to eth0 instead of enps33 or enp0s25
  • virt-resize: error: libguestfs error: could not create appliance through libvirt.