slackware 12: why i cant enable ethernet adapter

.id · 12-18-2007, 02:53 AM

Hi everybody, I'm having troubles with configuration of my network card in newly installed slackware 12. I have two installations, one as guest system in vmware player running on win xp, and other installed normally. The network adapter is driving me crazy in both cases, the situation is identical. After installation i wanted to enable ethernet adapter and I tried to do that with KDE Control Center -> Network settings. Firs annoyance was dialog with message that my platform is not supported and therefore I have to choose one of the proposed. I choose FreeBSD 6 and enabled my ethernet adapter and it worked. I was happy for that short period of time. After first reboot, I found out that my ethernet adapter was disabled. Again I choose platform (free BSD 6) and enabled my ethernet adapter. Everything was ok until I filled checkbox that say remember selected platform. After next reboot my ethernet is still disabled and I cant enable it (but message platform not supported is not shown anymore) it says: "There was an error changing the device's state. You will have to do it manually". Well I tried enabling it manually with

# /etc/rc.d/rc.inetd start

but without success.

I cant find solution anywhere (and beleive me i tried).

Please help me

bathory · 12-18-2007, 03:24 AM

You can run

Code:

netconfig

from CLI to configure your network

.id · 12-18-2007, 03:30 AM

Quote:

Originally Posted by bathory

You can run

Code:

netconfig

from CLI to configure your network

I alredy did that, but netconfig does not provide hardware configuration (I cant enable my ethernet adapter), in netconfig I can only select what I use dhcp, static ip...

bathory · 12-18-2007, 03:41 AM

What is your nic model? If it's recognized by the kernel, then the appropriate module is loaded into the kernel and netconfig can configure it for you and write the necessary info into /etc/rc.d/rc.inet1.conf.
If you don't know your nic's model, run

Code:

lspci

.id · 12-18-2007, 04:17 AM

Quote:

Originally Posted by bathory

What is your nic model? If it's recognized by the kernel, then the appropriate module is loaded into the kernel and netconfig can configure it for you and write the necessary info into /etc/rc.d/rc.inet1.conf.
If you don't know your nic's model, run

Code:

lspci

This is from my vmware virtual maschine:

bash-3.1# lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 01)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 01)
00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 08)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08)
00:0f.0 VGA compatible controller: VMware Inc [VMware SVGA II] PCI Display Adapter
00:10.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 10)

How can I found out if my module is supported or not? One more thing, I dont understand why my network adapter worked properly if my module is not loaded in kernel?

bathory · 12-18-2007, 04:25 AM

Quote:

How can I found out if my module is supported or not? One more thing, I dont understand why my network adapter worked properly if my module is not loaded in kernel?

According to http://www.faqs.org/docs/ethernet/Ethernet-HOWTO-4.html, your nic is supported by the stock linux kernel (using module pcnet32). You have to run (as root)

Code:

modprobe pcnet32

to load the kernel module into kernel. Then run netconfig to configure your network.
If your nic worked properly before, that means that the module was loaded automatically by the KDE network configuration tool.

.id · 12-18-2007, 04:43 AM

Quote:

Originally Posted by bathory

According to http://www.faqs.org/docs/ethernet/Ethernet-HOWTO-4.html, your nic is supported by the stock linux kernel (using module pcnet32). You have to run (as root)

Code:

modprobe pcnet32

to load the kernel module into kernel. Then run netconfig to configure your network.
If your nic worked properly before, that means that the module was loaded automatically by the KDE network configuration tool.

modprobe pcnet32 dont help, did following:

1. modprobe pcnet32 (as root)
2. reboot
3. logged in as root and run netconfig
4. tried to ping google, didnt work
5. tried again modprobe pcnet32, ping dont work again
6. starx
7. go to KDE control center - network settings, still same message.. it wont enable my network adapter

bathory · 12-18-2007, 04:54 AM

Your should run:
modprobe pcnet32
netconfig (to configure your network)

There is no need to reboot. It's not Window$. Just make sure the settings you put in netconfig are correct.

gopi.d · 12-18-2007, 06:09 AM

if you are able to see the ethernet interface then it's already done. just add the /sbin/modprobe pcnet32 to rc.modules to enable it automatically during booting. run netconfig eth0 and configure your ip configurations. now run ifconfig eth0 up to bring up your ethernet interface.

.id · 12-18-2007, 06:10 AM

Quote:

Originally Posted by bathory

Your should run:
modprobe pcnet32
netconfig (to configure your network)

There is no need to reboot. It's not Window$. Just make sure the settings you put in netconfig are correct.

I did everything as you suggested but it still dont work. The thing is that i doubt that netconfig can help me because everything is setup properly within it. Is there any way to enable/activate my network adapter from CLI?

bathory · 12-18-2007, 06:16 AM

Mind that ping may not work, so it's not a good tool to test connectivity. You can use your browser to try to connect.
Anyway after doing everything suggested, run:

Code:

lsmod
ifconfig
route -e

to verify the module is loaded, your nic is configured correctly and you have the correct gateway setup.

.id · 12-18-2007, 06:17 AM

Quote:

Originally Posted by gopi.d

if you are able to see the ethernet interface then it's already done. just add the /sbin/modprobe pcnet32 to rc.modules to enable it automatically during booting. run netconfig eth0 and configure your ip configurations. now run ifconfig eth0 up to bring up your ethernet interface.

This didnt help either:

Code:

bash-3.1# netconfig eth1 (i dont have eth0 is that ok?)

bash-3.1# ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:0C:29:B0:A1:2F  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:16 Base address:0x1080 

bash-3.1# ping www.google.com
ping: unknown host www.google.com

.id · 12-18-2007, 06:23 AM

Quote:

Originally Posted by bathory

Mind that ping may not work, so it's not a good tool to test connectivity. You can use your browser to try to connect.
Anyway after doing everything suggested, run:

Code:

lsmod
ifconfig
route -e

to verify the module is loaded, your nic is configured correctly and you have the correct gateway setup.

Is this ok?

bash-3.1# lsmod | grep pcnet32
pcnet32 33668 0
mii 8576 1 pcnet32

bash-3.1# ifconfig
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:352 errors:0 dropped:0 overruns:0 frame:0
TX packets:352 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:22228 (21.7 KiB) TX bytes:22228 (21.7 KiB)

bash-3.1# route -e
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
loopback * 255.0.0.0 U 0 0 0 lo

Tried browser but it still doesnt work

(bytheway i appreciate your effort very much)

bathory · 12-18-2007, 07:08 AM

So the module is loaded fine, but your network is not configured. Did you ran netconfig after loading the module?
If you have a static IP you can run:

Code:

ifconfig eth0 xx.xx.xx.xx netmask yy.yy.yy.yy up
route add default gw zz.zz.zz.zz

.id · 12-18-2007, 07:26 AM

Quote:

Originally Posted by bathory

So the module is loaded fine, but your network is not configured. Did you ran netconfig after loading the module?
If you have a static IP you can run:

Code:

ifconfig eth0 xx.xx.xx.xx netmask yy.yy.yy.yy up
route add default gw zz.zz.zz.zz

Yes, I did run netconfig after loading the module (few times actually). I'm not sure if static IP can help me because everything was fine before with DHCP. I didn't change anything in environment except the selection of checkbox "remember selected platform" in dialogbox during network configuration in kde control center.