On Tue, 2009-07-21 at 10:32 -0700, Marcus Mae wrote:
> eth0 Link encap:Ethernet HWaddr 00:1D:92:59:27:95
> inet addr:192.168.0.103 Bcast:192.168.0.255 Mask:255.255.255.0
> inet6 addr: fe80::21d:92ff:fe59:2795/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:972845 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1716478 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:75305489 (71.8 MiB) TX bytes:2265463648 (2.1 GiB)
> Interrupt:26 Base address:0x2000
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:2282 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2282 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:257281 (251.2 KiB) TX bytes:257281 (251.2 KiB)
>
> lo no wireless extensions.
>
> eth0 no wireless extensions.
Hmm... I wonder if there is firmware needed for that device, and if
something was dropped from the associated firmware package. If the
driver doesn't find the firmware then its like you don't even have the
hardware installed (like what you are seeing above.)
If this is the case then usually there is an error message visible by
just calling 'dmesg'.
--rusty
_______________________________________________
Moblin dev Mailing List
dev@moblin.org
To manage or unsubscribe from this mailing list visit:
http://lists.moblin.org/listinfo/dev or your user account on http://moblin.org
once logged in.
For more information on the Moblin Developer Mailing lists visit:
http://moblin.org/community/mailing-lists
