| 1 |
my NIC magically recovered :) i did nothing. i just wake up today, and |
| 2 |
turn my computer on, and it is as good as new. |
| 3 |
|
| 4 |
|
| 5 |
On Sat, Aug 7, 2010 at 12:00 PM, William Kenworthy <billk@×××××××××.au> wrote: |
| 6 |
> try mii-tool if its compatible with the card |
| 7 |
> |
| 8 |
> sys-apps/net-tools-1.60_p20090728014017-r1 (/sbin/mii-tool) |
| 9 |
> |
| 10 |
> Add more "-v" to its command line and you get more info including a ROM |
| 11 |
> readout. |
| 12 |
> |
| 13 |
> BillK |
| 14 |
> |
| 15 |
> |
| 16 |
> On Sat, 2010-08-07 at 10:17 +0800, Xi Shen wrote: |
| 17 |
>> normally, the latest livecd boot up the system, and everything works. |
| 18 |
>> if the livecd boot up and something is not working, i guess it must be |
| 19 |
>> a hardware issue. |
| 20 |
>> |
| 21 |
>> BTW, ifconfig -a does show my eth0 NIC, but ifconfig eth0 up cannot |
| 22 |
>> start my NIC. |
| 23 |
>> |
| 24 |
>> |
| 25 |
>> On Sat, Aug 7, 2010 at 12:01 AM, Mick <michaelkintzios@×××××.com> wrote: |
| 26 |
>> > On 6 August 2010 13:45, Xi Shen <davidshen84@××××××××××.com> wrote: |
| 27 |
>> >> i reboot the system, fresh start with livcd. all reports the same error. :( |
| 28 |
>> >> |
| 29 |
>> >> i noticed that the hardware address is 3a:3a:2d:6c:3a:3a, which is |
| 30 |
>> >> obviously an invalid one. i guess it is a hardware failure... |
| 31 |
>> > |
| 32 |
>> > Hmm ... if ifconfig -a does not show your device then this merits |
| 33 |
>> > further investigation. |
| 34 |
>> > |
| 35 |
>> > Does the LiveCD have the requisite driver for your eth0? |
| 36 |
>> > |
| 37 |
>> > In your normal OS the permanent udev rules could have messed up the |
| 38 |
>> > order of your devices (assuming that you have more than one network |
| 39 |
>> > interface) so that eth1 is now eth0. |
| 40 |
>> > |
| 41 |
>> > However, I am not sure that the LiveCD would show the same problem as |
| 42 |
>> > it would run its own udev daemon. Either way, ifconfig -a should show |
| 43 |
>> > all your interfaces and MAC numbers (as long as there is the |
| 44 |
>> > appropriate driver in the kernel). |
| 45 |
>> > |
| 46 |
>> > If it is a hardware failure it may be worth trying to reseat the card |
| 47 |
>> > if separate to the MoBo, or disable/enable in the BIOS to reset it. |
| 48 |
>> > -- |
| 49 |
>> > Regards, |
| 50 |
>> > Mick |
| 51 |
>> > |
| 52 |
>> > |
| 53 |
>> |
| 54 |
>> |
| 55 |
>> |
| 56 |
> |
| 57 |
> -- |
| 58 |
> William Kenworthy <billk@×××××××××.au> |
| 59 |
> Home in Perth! |
| 60 |
> |
| 61 |
> |
| 62 |
> |
| 63 |
|
| 64 |
|
| 65 |
|
| 66 |
-- |
| 67 |
Best Regards, |
| 68 |
Xi Shen (David) |
| 69 |
|
| 70 |
http://twitter.com/davidshen84/ |
Archives