1 |
> |
2 |
>You can try issuing "ifconfig eth0 up" to make sure that the interface |
3 |
>is up and then run "dhcpcd -d eth0". |
4 |
I will test this when I get home. |
5 |
|
6 |
>You may not be connecting b/c the card isn't correctly auto-negotiating |
7 |
>with the switch/hub it's plugged into. Maybe you DHCP server has |
8 |
>tresholds or does expect a hostname or MAC address. Maybe the network |
9 |
>card is bad. Try swapping it with one of the working ones. |
10 |
This machine is currently dual boots windows/debian and is on the network. It can successfully connect to the network |
11 |
in either OS using the dhcp service. So I know that the problem is either software, or between the chair and the |
12 |
keyboard. I am currently attempting to determine if the I am the problem (i.e. dumb user skips step). |
13 |
|
14 |
Let me state again all that I have done. Please let me know if I skipped a step. |
15 |
|
16 |
1) Boot from build CD image (42MB size) |
17 |
|
18 |
2) Login as root |
19 |
|
20 |
3) modprobe tulip (activates network card) |
21 |
|
22 |
4) dhcpcd -d eth0 |
23 |
|
24 |
|
25 |
Am I missing a step?? |
26 |
|
27 |
>: Is there a rc4 iso image that I can get at? Maybe using a different |
28 |
>: image will be of help? |
29 |
> |
30 |
>I don't think it'll help. Right now we need to figure out what's hosing |
31 |
>your network. |
32 |
|
33 |
Okay. Thanks for the patient help by the way. |
34 |
|
35 |
Marcus |