| 1 |
"Gordon Gallup" <gallup.gordon@×××××.com> posted |
| 2 |
d9edbc030605241309y34d1f12emeb80c7d726754fe2@××××××××××.com, excerpted |
| 3 |
below, on Wed, 24 May 2006 15:09:50 -0500: |
| 4 |
|
| 5 |
> Greetings again, Thanks to all who responded. I will now tell the |
| 6 |
> rest of the story: I would have no problem leaving the D-Link NIC in, |
| 7 |
> but the resulting system after compilation still does not like the |
| 8 |
> forcedeth, cannot seem to detect the D-Link as eth1, and, hence, does |
| 9 |
> not load its 'stge' driver (produced for Linux by D-Link). The |
| 10 |
> result---no network. Has anyone seen this? |
| 11 |
|
| 12 |
If it's not detecting the onboard, wouldn't the d-link be eth0? Or is it |
| 13 |
detecting it but it just won't work? In the latter case, perhaps disable |
| 14 |
it in BIOS, so the d-link is again the first one detected, eth0. |
| 15 |
|
| 16 |
BTW, if you have to use it I can't argue with that, but certainly I, and a |
| 17 |
number of others I've read, have a pretty low opinion of d-link, as their |
| 18 |
stuff seems to crap out pretty fast. They are fortunately cheap, so you |
| 19 |
don't spend much on them, but they seem to be worth even less than that. |
| 20 |
Based on my experience, I don't expect I'll ever have another d-link in my |
| 21 |
systems -- the experiences have been that bad. (I personally like |
| 22 |
Netgear, who seems to deliver consistently good quality at a mid-range |
| 23 |
price, but others may have other favorites. D-link... seems to have been |
| 24 |
bad for not just me, but at least you don't spend too much on them, and |
| 25 |
they usually work awhile anyway, so they'll do in a pinch, as seems to |
| 26 |
have been the case here.) |
| 27 |
|
| 28 |
|
| 29 |
|
| 30 |
-- |
| 31 |
Duncan - List replies preferred. No HTML msgs. |
| 32 |
"Every nonfree program has a lord, a master -- |
| 33 |
and if you use the program, he is your master." Richard Stallman |
| 34 |
|
| 35 |
-- |
| 36 |
gentoo-amd64@g.o mailing list |
Archives