| 1 |
If there's an on-off option in the BIOS for the on board chip I can't |
| 2 |
find it. This is an e-Machine T-6420. This BIOS does not list the |
| 3 |
PCI devices connected. The on-board chip is always detected, assigned |
| 4 |
to eth0, and the forcedeth driver module is loaded. It just doesn't |
| 5 |
connect with DHCP. The D-Link is detected by the installation |
| 6 |
program, assigned to eth1, and uses this as is shown with |
| 7 |
/sbin/ifconfig. When one has the compiled system rebooted, eth0 is |
| 8 |
apparently assigned to the onboard chip, forcedeth is loaded, but |
| 9 |
there is no connection. The D-Link is not detected, so there is no |
| 10 |
eth1. I haven't tried the minimal installation disk. Can one |
| 11 |
eventually get a full system with it? |
| 12 |
GAG |
| 13 |
|
| 14 |
On 5/24/06, Duncan <1i5t5.duncan@×××.net> wrote: |
| 15 |
> "Gordon Gallup" <gallup.gordon@×××××.com> posted |
| 16 |
> d9edbc030605241309y34d1f12emeb80c7d726754fe2@××××××××××.com, excerpted |
| 17 |
> below, on Wed, 24 May 2006 15:09:50 -0500: |
| 18 |
> |
| 19 |
> > Greetings again, Thanks to all who responded. I will now tell the |
| 20 |
> > rest of the story: I would have no problem leaving the D-Link NIC in, |
| 21 |
> > but the resulting system after compilation still does not like the |
| 22 |
> > forcedeth, cannot seem to detect the D-Link as eth1, and, hence, does |
| 23 |
> > not load its 'stge' driver (produced for Linux by D-Link). The |
| 24 |
> > result---no network. Has anyone seen this? |
| 25 |
> |
| 26 |
> If it's not detecting the onboard, wouldn't the d-link be eth0? Or is it |
| 27 |
> detecting it but it just won't work? In the latter case, perhaps disable |
| 28 |
> it in BIOS, so the d-link is again the first one detected, eth0. |
| 29 |
> |
| 30 |
> BTW, if you have to use it I can't argue with that, but certainly I, and a |
| 31 |
> number of others I've read, have a pretty low opinion of d-link, as their |
| 32 |
> stuff seems to crap out pretty fast. They are fortunately cheap, so you |
| 33 |
> don't spend much on them, but they seem to be worth even less than that. |
| 34 |
> Based on my experience, I don't expect I'll ever have another d-link in my |
| 35 |
> systems -- the experiences have been that bad. (I personally like |
| 36 |
> Netgear, who seems to deliver consistently good quality at a mid-range |
| 37 |
> price, but others may have other favorites. D-link... seems to have been |
| 38 |
> bad for not just me, but at least you don't spend too much on them, and |
| 39 |
> they usually work awhile anyway, so they'll do in a pinch, as seems to |
| 40 |
> have been the case here.) |
| 41 |
> |
| 42 |
> |
| 43 |
> |
| 44 |
> -- |
| 45 |
> Duncan - List replies preferred. No HTML msgs. |
| 46 |
> "Every nonfree program has a lord, a master -- |
| 47 |
> and if you use the program, he is your master." Richard Stallman |
| 48 |
> |
| 49 |
> -- |
| 50 |
> gentoo-amd64@g.o mailing list |
| 51 |
> |
| 52 |
> |
| 53 |
|
| 54 |
-- |
| 55 |
gentoo-amd64@g.o mailing list |
Archives