Manfred Spraul schrieb:
> Very interesting. The message itself is not fatal: It merely means that
> there was no link during ifup. This typically happens when the hardware
> initialization was not yet finished during ifup. Theoretically, an
> interrupt should happen when the hardware initialization is completed
> and that interrupt then sets up the link.
> Somehow it doesn't work for you.
could be the hardware's fault too? it's an onboard NIC on an nforce
chipset and the lspci i attached in the last mail looks rather strange
(compared to the r8169 (eth1) entry).
> Could you try the attached patch? It polls for link changes instead of
> relying on the irq. Additionally, I have enabled some debug output.
off to reboot in a second...
thanks,
Christian.
PS: on a side note, did you get my "other" mail concerning your mail address?
--
BOFH excuse #122:
because Bill Gates is a Jehovah's witness and so nothing can work on St.
Swithin's day.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
