Alan Cox wrote:
It is not recognised by 2.6.24-rc1. I'm guessing it's because the
vendor ID is 0001 rather than something sensible. I patched the kernel
as follows:
A vendor ID of 1 is very very very broken. Do all boards have this or do
you have a faulty box (perhaps a misprogrammed EEPROM somewhere)
--- drivers/net/r8169.c.orig 2007-10-29 05:37:02.000000000 +0000
+++ drivers/net/r8169.c 2007-10-29 05:54:30.000000000 +0000
@@ -165,6 +165,7 @@
{ PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8136), 0, 0, RTL_CFG_2 },
{ PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8167), 0, 0, RTL_CFG_0 },
{ PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8168), 0, 0, RTL_CFG_1 },
+ { PCI_DEVICE(PCI_ANY_ID, 0x8168), 0, 0, RTL_CFG_2 },
That will match any device 0x8168 not just a realtek one. I'd use 0x0001,
0x8168 for the match. However I'd seriously consider checking another
board as I suspect you simply have a return candidate.
I have had this board for a few months as well and I have needed to
patch the driver to use 0x0001 as well.
Later, JOSH
-
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/
