On Thursday 22 July 2004 12:02, Gene Heskett wrote: >On Thursday 22 July 2004 08:22, James Wilkinson wrote: [...] >>That's the way I understand it. The forcedeth driver is listed in >> the 2.6.7 tree as "Reverse Engineered nForce Ethernet support >>(EXPERIMENTAL)" under the "Ethernet (10 or 100Mbit)" menu, about >> nine up from the RealTek 8139 driver. So make sure you select >> "Prompt for development and/or incomplete code/drivers". > >Good grief James, I must be going blind, and the optometrist says I >check at 20/10, but you are correct. I have a kernel building with >that in it now. I blew it all away and re-unpacked as I'd tried to >apply those patches from the developers website and they mostly blew >up. > >I have both the 8139too and forcedeth in the build, so I'd assume my >modprobe.conf is going to need an "alias eth0 8139too", and an > "alias eth1 forcedeth" in it? and reverseing those assignments to > test. Humm, wonder if I have a second cat5 jumper (I have 5 ports > empty on a netgear 8 port switch yet :) Humm, when builtin, that > isn't going to effect it. Anyway, time to hit send and reboot. :-) > >>HTH, >> >>James. Which, when done, did not manage to elicit any responses whatsoever in /var/log/dmesg referencing any ethernet but the 8139too. This strikes me as rather odd, so a rebuild as a module is underway. I'd say this thing is being perverse, but it doesn't have the equipment to be. :-) -- Cheers, Gene There are 4 boxes to be used in defense of liberty. Soap, ballot, jury, and ammo. Please use in that order, starting now. -Ed Howdershelt, Author Additions to this message made by Gene Heskett are Copyright 2004, Maurice E. Heskett, all rights reserved.
