jethro Posted May 9, 2006 Report Share Posted May 9, 2006 Hi everybody, When I boot with the noapic boot option I can not connect to my network. I already tried putting "alias net-pf-10 off" in /etc/modprobe. Does anybody know how to solve this? Best regards, Jethro Quote Link to comment Share on other sites More sharing options...
scarecrow Posted May 9, 2006 Report Share Posted May 9, 2006 Netcard module gets loaded properly, or not? If lsmod doesn't show the module, load it maunually, or preload it. Quote Link to comment Share on other sites More sharing options...
jethro Posted May 9, 2006 Author Report Share Posted May 9, 2006 (edited) This is my netwerk card as seen from lspci: 02:07.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) lsmod does not show netcard when I boot without the noapic option, but in that case my netwerk card does work, so do I really need netcard? Edited May 11, 2006 by jethro Quote Link to comment Share on other sites More sharing options...
scarecrow Posted May 9, 2006 Report Share Posted May 9, 2006 There IS an issue with this particular network interface... please check if you have both "8139too" and "8139cp" loaded. If this is the case, one of them has to go- in most cases, "8139cp". You can either unload it, or prevent it being loaded at startup. Quote Link to comment Share on other sites More sharing options...
jethro Posted May 10, 2006 Author Report Share Posted May 10, 2006 Hi there, This is what I get when looking for the string "8139" in lsmod: [root@0a0d12f9a6a jethro]# lsmod | grep 8139 8139too 20640 0 mii 4448 1 8139too When I did this, I booted WITHOUT the noapic option. I will look what it says with the noapic boot option on. Beste regards, Jethro Quote Link to comment Share on other sites More sharing options...
jethro Posted May 11, 2006 Author Report Share Posted May 11, 2006 Hi all, When I boot WITH the noapic option, this is what I get from lsmod" [root@laptop jethro]# lsmod | grep 8139 8139too 20640 0 mii 4448 1 8139too So it is exactly the same, how is it then possible that the network card does not work with the noapic boot option on if the same module is loaded? Greetings, Jethri Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted May 11, 2006 Report Share Posted May 11, 2006 Can you post the output of: ifconfig -a when booted with apic enabled, and when booted with apic disabled. Quote Link to comment Share on other sites More sharing options...
jethro Posted May 11, 2006 Author Report Share Posted May 11, 2006 (edited) Alright, here is the data which I get with "ifconfig -a" in both cases: WITHOUT noapic: [root@dhcppc2 IsaViz]# ifconfig -a ath0 Link encap:Ethernet HWaddr 00:11:F5:E4:87:B0 UP BROADCAST RUNNING 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:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) eth0 Link encap:Ethernet HWaddr 00:A0:D1:2F:9A:6A inet addr:192.168.1.35 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:22728 errors:0 dropped:0 overruns:0 frame:0 TX packets:21075 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:21139613 (20.1 MiB) TX bytes:3268365 (3.1 MiB) Interrupt:20 Base address:0x4000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:64 errors:0 dropped:0 overruns:0 frame:0 TX packets:64 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8105 (7.9 KiB) TX bytes:8105 (7.9 KiB) wifi0 Link encap:UNSPEC HWaddr 00-11-F5-E4-87-B0-80-C8-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:11482 errors:0 dropped:0 overruns:0 frame:14174 TX packets:24374 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 RX bytes:1130874 (1.0 MiB) TX bytes:1194320 (1.1 MiB) Interrupt:20 Memory:f8f60000-f8f70000 WITH noapic: [root@laptop jethro]# ifconfig -a ath0 Link encap:Ethernet HWaddr 00:11:F5:E4:87:B0 UP BROADCAST RUNNING 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:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) eth0 Link encap:Ethernet HWaddr 00:A0:D1:2F:9A:6A UP BROADCAST RUNNING 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:10 Base address:0x4000 eth0:9 Link encap:Ethernet HWaddr 00:A0:D1:2F:9A:6A inet addr:127.255.255.255 Bcast:127.255.255.255 Mask:255.0.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:10 Base address:0x4000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:108 errors:0 dropped:0 overruns:0 frame:0 TX packets:108 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:13693 (13.3 KiB) TX bytes:13693 (13.3 KiB) wifi0 Link encap:UNSPEC HWaddr 00-11-F5-E4-87-B0-80-28-00-00-00-00-00-00-00-00 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3459 errors:0 dropped:0 overruns:0 frame:7081 TX packets:8047 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:199 RX bytes:349033 (340.8 KiB) TX bytes:394300 (385.0 KiB) Interrupt:11 Memory:f8f60000-f8f70000 I only use eth0 to connect to my network, not the wireless stuff. Edited May 11, 2006 by jethro Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted May 11, 2006 Report Share Posted May 11, 2006 OK, I'm trying to remember back as to why you are booting with noapic? Is there a particular reason for doing this? I've just forgotten from the previous posts that aren't in this topic as to why you choose to boot noapic. Quote Link to comment Share on other sites More sharing options...
jethro Posted May 11, 2006 Author Report Share Posted May 11, 2006 OK, I'm trying to remember back as to why you are booting with noapic? Is there a particular reason for doing this? I've just forgotten from the previous posts that aren't in this topic as to why you choose to boot noapic. I am trying to get noapic to work, because of a USB problem I have, the thread about that problem can be found here: https://mandrivausers.org/index.php?showtopic=31913. When I boot with noapic, I haven't had the USB problem yet, so that is why I would like to get noapic to work with my network card. Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted May 11, 2006 Report Share Posted May 11, 2006 Do you disable local apic as well? Or just apic? If you disable local apic, but leave apic enabled, does your network card work this way? Just seeing if disabling one instead of the other helps the situation. You can find the local apic option in same place under boot loader. Quote Link to comment Share on other sites More sharing options...
jethro Posted May 11, 2006 Author Report Share Posted May 11, 2006 I will try that right away, in the mean time: does this weird interface have anything to do with it?: eth0:9 Link encap:Ethernet HWaddr 00:A0:D1:2F:9A:6A inet addr:127.255.255.255 Bcast:127.255.255.255 Mask:255.0.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:10 Base address:0x4000 This one only shows up when I boot with the noapic option. I can not deleten it using MCC, because it crashs on displaying the network interfaces for removal. How can I remove it using the command line? Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted May 11, 2006 Report Share Posted May 11, 2006 To remove with command line, you'd have to take a look in /etc/sysconfig/network-scripts. This is where all the ifcfg-eth0, etc, etc, files exist. It's definitely strange that it comes up with the eth0:9, as if there are sub-devices for this card. I can only think it's misconfigured or something. If you can't find anything in the network-scripts directory that matches this, post a list of files in this directory, so I can see: ls -l /etc/sysconfig/network-scripts Quote Link to comment Share on other sites More sharing options...
jethro Posted May 13, 2006 Author Report Share Posted May 13, 2006 (edited) These are the files in /etc/sysconfig/network-scripts/: [root@laptop log]# cd /etc/sysconfig/network-scripts/ [root@laptop network-scripts]# ll totaal 216 drwxr-xr-x 2 root root 4096 mrt 2 18:35 hostname.d/ -rwx------ 1 root root 143 mei 5 18:27 ifcfg-ath0* -rwxr-xr-x 1 root root 324 mei 5 17:23 ifcfg-eth0* lrwxrwxrwx 1 root root 22 mrt 20 14:45 ifcfg-lo -> ../networking/ifcfg-lo -rwxr-xr-x 1 root root 207 mei 5 17:23 ifcfg-sit0* -rwxr-xr-x 1 root root 198 mei 5 17:23 ifcfg-wifi0* lrwxrwxrwx 1 root root 20 mrt 20 14:45 ifdown -> ../../../sbin/ifdown* -rwxr-xr-x 1 root root 1063 feb 24 19:44 ifdown-aliases* drwxr-xr-x 2 root root 4096 feb 24 19:44 ifdown.d/ -rwxr-xr-x 1 root root 886 sep 13 2004 ifdown-ippp* -rwxr-xr-x 1 root root 4133 feb 24 19:44 ifdown-ipv6* -rwxr-xr-x 1 root root 236 sep 13 2004 ifdown-isdn* -rwxr-xr-x 1 root root 1318 feb 24 19:44 ifdown-post* -rwxr-xr-x 1 root root 1153 feb 24 19:44 ifdown-ppp* -rwxr-xr-x 1 root root 1863 feb 24 19:44 ifdown-sit* -rwxr-xr-x 1 root root 902 jun 26 2002 ifdown-sl* lrwxrwxrwx 1 root root 18 mrt 20 14:45 ifup -> ../../../sbin/ifup* -rwxr-xr-x 1 root root 12867 feb 24 19:44 ifup-aliases* drwxr-xr-x 2 root root 4096 feb 24 19:44 ifup.d/ -rwxr-xr-x 1 root root 7226 sep 13 2004 ifup-ippp* -rwxr-xr-x 1 root root 9667 feb 24 19:44 ifup-ipv6* -rwxr-xr-x 1 root root 821 jun 26 2002 ifup-ipx* -rwxr-xr-x 1 root root 4451 sep 13 2004 ifup-isdn* -rwxr-xr-x 1 root root 689 jun 26 2002 ifup-plip* -rwxr-xr-x 1 root root 926 jun 26 2002 ifup-plusb* -rwxr-xr-x 1 root root 2695 feb 24 19:44 ifup-post* -rwxr-xr-x 1 root root 4083 feb 24 19:44 ifup-ppp* -rwxr-xr-x 1 root root 1197 aug 22 2003 ifup-routes* -rwxr-xr-x 1 root root 3545 feb 24 19:44 ifup-sit* -rwxr-xr-x 1 root root 1646 jun 26 2002 ifup-sl* -rwxr-xr-x 1 root root 5767 feb 24 19:44 ifup-wireless* -rwxr-xr-x 1 root root 5512 feb 24 19:44 init.ipv6-global* -rw-r--r-- 1 root root 9401 feb 24 19:44 network-functions -rw-r--r-- 1 root root 42332 feb 24 19:44 network-functions-ipv6 drwxr-xr-x 2 root root 4096 mei 5 18:27 wireless.d/ How can I now remove the network interface that I do not want? Edited May 13, 2006 by jethro Quote Link to comment Share on other sites More sharing options...
ianw1974 Posted May 13, 2006 Report Share Posted May 13, 2006 To make things simpler I would be tempted to delete: ifcfg-ath0 ifcfg-sit0 ifcfg-wifi0 since you're not using your wireless interfaces or ipv6. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.