Hija,
I just bought a new motherboard "ECS L7VTA" sporting a VIA KT400 chipset
and found an annoying bug which took me quite some time to track down:
As soon as I enable the APIC mode in the BIOS the onboard PHY seems
to ignore any packets which are thrown at it *after* the kernel
initialised itself which is especially nasty since the system is booting
from network effectively stopping its boot when trying to get an IP
using DHCP or mounting a NFS volume in case the IP is fixed. The onboard
NIC is a VIA Rhine II (VT6102).
The startup process looks like:
- POST
- BIOS check
- PXE BIOS initialisation
- PXE boot into etherboot
- Correct detection and initialisation of the NIC in etherboot
- Boot of linux kernel
- Correct initialisation of system including NIC (via-rhine driver from
Donald Becker as in the standard kernels)
- Endless loop like the following:
-------->
eth0: Setting full-duplex based on MII #1 link partner capability of 41e1.
Sending DCHP requests ...... timed out!
<--------
The NIC initialised itself with the correct interrupt according to the
BIOS screen. As soon as I shut down the APIC mode, everything works as
expected.
Ideas?
--
Servus,
Daniel
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Mar 15 2003 - 22:00:36 EST