freebsd-current is your destination. Redirected properly
Regards
S.
On Tue, 21 Sep 2004 00:31:01 +0200, Huw Wynn-Jones [EMAIL PROTECTED] wrote:
Hello,
I'm posting to this list because I'm not sure who else I should send this info
to. I'd be grateful if someone would let me know the correct procedure.
I've got a new Dell 4700 with P4 2.8 chip on a motherboard with the new Intel
915G Express chipset. It has an intergrated network card, the Intel Pro 100
VE, but it didn't work straight out of the box when I installed Freebsd
5.2.1. I did loads of searches on google and eventually found a post
somewhere giving me an example of what to do. Now the card is detected at
boot and works just fine.
So below is the result. I have added a new line
to /usr/src/sys/dev/fxp/if_fxp.c
The new line is marked with +
/*
* Claim various Intel PCI device identifiers for this driver. The
* sub-vendor and sub-device field are extensively used to identify
* particular variants, but we don't currently differentiate between
* them.
*/
static struct fxp_ident fxp_ident_table[] = {
{ 0x1029, -1, Intel 82559 PCI/CardBus Pro/100 },
{ 0x1030, -1, Intel 82559 Pro/100 Ethernet },
{ 0x1031, -1, Intel 82801CAM (ICH3) Pro/100 VE Ethernet },
{ 0x1032, -1, Intel 82801CAM (ICH3) Pro/100 VE Ethernet },
{ 0x1033, -1, Intel 82801CAM (ICH3) Pro/100 VM Ethernet },
{ 0x1034, -1, Intel 82801CAM (ICH3) Pro/100 VM Ethernet },
{ 0x1035, -1, Intel 82801CAM (ICH3) Pro/100 Ethernet },
{ 0x1036, -1, Intel 82801CAM (ICH3) Pro/100 Ethernet },
{ 0x1037, -1, Intel 82801CAM (ICH3) Pro/100 Ethernet },
{ 0x1038, -1, Intel 82801CAM (ICH3) Pro/100 VM Ethernet },
{ 0x1039, -1, Intel 82801DB (ICH4) Pro/100 VE Ethernet },
{ 0x103A, -1, Intel 82801DB (ICH4) Pro/100 Ethernet },
{ 0x103B, -1, Intel 82801DB (ICH4) Pro/100 VM Ethernet },
{ 0x103C, -1, Intel 82801DB (ICH4) Pro/100 Ethernet },
{ 0x103D, -1, Intel 82801DB (ICH4) Pro/100 VE Ethernet },
{ 0x103E, -1, Intel 82801DB (ICH4) Pro/100 VM Ethernet },
{ 0x1050, -1, Intel 82801BA (D865) Pro/100 VE Ethernet },
{ 0x1059, -1, Intel 82551QM Pro/100 M Mobile Connection },
+ { 0x1064, -1, Intel Pro 100 VE Ethernet }, +This is new
{ 0x1209, -1, Intel 82559ER Embedded 10/100 Ethernet },
{ 0x1229, 0x01, Intel 82557 Pro/100 Ethernet },
{ 0x1229, 0x02, Intel 82557 Pro/100 Ethernet },
{ 0x1229, 0x03, Intel 82557 Pro/100 Ethernet },
{ 0x1229, 0x04, Intel 82558 Pro/100 Ethernet },
{ 0x1229, 0x05, Intel 82558 Pro/100 Ethernet },
{ 0x1229, 0x06, Intel 82559 Pro/100 Ethernet },
{ 0x1229, 0x07, Intel 82559 Pro/100 Ethernet },
{ 0x1229, 0x08, Intel 82559 Pro/100 Ethernet },
{ 0x1229, 0x09, Intel 82559ER Pro/100 Ethernet },
{ 0x1229, 0x0c, Intel 82550 Pro/100 Ethernet },
{ 0x1229, 0x0d, Intel 82550 Pro/100 Ethernet },
{ 0x1229, 0x0e, Intel 82550 Pro/100 Ethernet },
{ 0x1229, 0x0f, Intel 82551 Pro/100 Ethernet },
{ 0x1229, 0x10, Intel 82551 Pro/100 Ethernet },
{ 0x1229, -1, Intel 82557/8/9 Pro/100 Ethernet },
{ 0x2449, -1, Intel 82801BA/CAM (ICH2/3) Pro/100 Ethernet },
{ 0, -1, NULL },
};
I have named it rather generally because I couldn't find any other better
identifiers.
Once I recompiled a new kernel the card was detected and ifconfig confirmed
everything to be ok.
I hope this can be added to the source of CURRENT so that others with a new
computer like mine won't have the same weekend's worth of frustration. Still
I got there in the end...almost bought a new network card...persistance pays
off I suppose.
Long subject line I know, but the post should come straight up in google like
that for another lost soul like me.
Thanks
Huw
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
--
Subhro Sankha Kar
School of Information Technology
Block AQ-13/1 Sector V
ZIP 700091
India
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
