I am helping a friend with his desktop. I installed Slackware 13 for him on his desktop (32 bit). Everything seems to be OK, except for his ethernet stuff (sorry, I don't know how to call it).
He has a LAN port onboard.
When I type
ifconfig
it only shows the loopback interface.
When I type
iwconfig
it shows both his wireless and his LAN card as wlan0 and wmaster0.
When I specificly type ifconfig wmaster0, it showed the information of his wired port.
Moreover, when connected to the router, the card doesn't seem to pick up the IP address.

The motherboard he use is and ECS P45T-A.
The LAN controller is: Gigabit LAN,Athlos L1 PCIe GigaLAN controller.

Please let me know what I can do?

Thanks,

Hi trainee,

maybe this gadgets vendor is Atheros and google may help.

First with /sbin/lspci check if the LAN-adapter is known by the system, then try lsmod to find out if the adequate kernelmodule is loaded.

And if the required module is loaded you may go on to configure the network.

Markus

Hi,

You can use the 'ifconfig -a' to see all the devices that are recognized at boot.

You did run 'netconfig'? When you create a user for the install be sure to include in groups;
Post the output of 'dmesg|grep -i eth' and/or 'lspci -vv|grep -i eth', 'ifconfig -a' and 'route -n' to aid in diagnosis of the problem. This request is based on your LAN. If you are wanting wireless then adjust the command(s).

BTW, don't forget to place your ISP DNS in 'etc/resolv.conf';

I second markush's thought: if you don't have the right kernel module, then your interfaces will not turn up in the output of ifconfig -a... you might have to rebuild your kernel and pay close call to the networking section to make sure that your Athlos Gigabit controller is enabled.

Thanks, everybody. Today, when I booted it up, everything just worked out mysteriously, without me having to do anything. I don't know if the udev took time to recognize the right module or something. Anyway, I'll bug you guys again if it causes trouble again.

Slackware works in mysterious ways!

But seriously, it'd be a good idea to learn what exactly made it work, vs what made it NOT work initially; this way, you can configure whatever may be necessary to KEEP it working, and not need to depend on 'magic' -- otherwise, if it decides to magically NOT work again one morning, you'll be back at square 1.

For now: congrats and happy Slacking.

Sasha

You're right. I would if it is my computer. But in this case, it's my friend's desktop and he is happy with it now, so, I can't poke my nose in there.