1 |
normally, the latest livecd boot up the system, and everything works. |
2 |
if the livecd boot up and something is not working, i guess it must be |
3 |
a hardware issue. |
4 |
|
5 |
BTW, ifconfig -a does show my eth0 NIC, but ifconfig eth0 up cannot |
6 |
start my NIC. |
7 |
|
8 |
|
9 |
On Sat, Aug 7, 2010 at 12:01 AM, Mick <michaelkintzios@×××××.com> wrote: |
10 |
> On 6 August 2010 13:45, Xi Shen <davidshen84@××××××××××.com> wrote: |
11 |
>> i reboot the system, fresh start with livcd. all reports the same error. :( |
12 |
>> |
13 |
>> i noticed that the hardware address is 3a:3a:2d:6c:3a:3a, which is |
14 |
>> obviously an invalid one. i guess it is a hardware failure... |
15 |
> |
16 |
> Hmm ... if ifconfig -a does not show your device then this merits |
17 |
> further investigation. |
18 |
> |
19 |
> Does the LiveCD have the requisite driver for your eth0? |
20 |
> |
21 |
> In your normal OS the permanent udev rules could have messed up the |
22 |
> order of your devices (assuming that you have more than one network |
23 |
> interface) so that eth1 is now eth0. |
24 |
> |
25 |
> However, I am not sure that the LiveCD would show the same problem as |
26 |
> it would run its own udev daemon. Either way, ifconfig -a should show |
27 |
> all your interfaces and MAC numbers (as long as there is the |
28 |
> appropriate driver in the kernel). |
29 |
> |
30 |
> If it is a hardware failure it may be worth trying to reseat the card |
31 |
> if separate to the MoBo, or disable/enable in the BIOS to reset it. |
32 |
> -- |
33 |
> Regards, |
34 |
> Mick |
35 |
> |
36 |
> |
37 |
|
38 |
|
39 |
|
40 |
-- |
41 |
Best Regards, |
42 |
Xi Shen (David) |
43 |
|
44 |
http://twitter.com/davidshen84/ |