Jump to content

Mandriva 2006, Suse 9.3/10 & a network issue


RiccardoPini
 Share

Recommended Posts

Nope but Mandriva stopped to see the eth0 after have disabled in the bios.

 

So what? That's natural: every onboard component disabled within BIOS does not exist for the OS!

HardDrake can be safely disabled, since other hardware detection scripts are present (hotplug, or in newest Linux revisions udev without hotplug- thank god for that!).

Link to comment
Share on other sites

  • Replies 92
  • Created
  • Last Reply

Top Posters In This Topic

Nope but Mandriva stopped to see the eth0 after have disabled in the bios.

 

So what? That's natural: every onboard component disabled within BIOS does not exist for the OS!

HardDrake can be safely disabled, since other hardware detection scripts are present (hotplug, or in newest Linux revisions udev without hotplug- thank god for that!).

 

Yep it's normal, nobody wants to see it. Please give a look to the whole post than the situation will be more clear to you.

Link to comment
Share on other sites

Hi to all! Speaking with my dad he gave an idea that if will turn out to be true would sound incredible...my motherboard is the Aopen one with the Tube sound, a thermoionic valve which is very close to the nic cards. All the behaviour makes think that this is the random external agent that prevents the nic to be brought up in the correct way. And this would explain why after a while the nic works properly: the valve when warming up crosses diff frequencies and a particular range could influence the nics.

 

Im doing tests and if so guys i think u can jump on your chairs for this!

Link to comment
Share on other sites

I'm not sure how it can happen. This is what I would do, before installing Linux on your system. If you have it now, erase it and start again, following this:

 

1. Make sure Plug and Play OS in the BIOS is set to disable. It should not be set to be controlled by the OS.

2. Disable the on-board Realtek card, so that you use the 3COM card. OR remove the 3COM card, and just use the Realtek with it enabled in the BIOS.

3. Install Mandriva 2006.

4. If using Realtek card, make sure APIC is disabled, as you might experience network connectivity problems otherwise.

5. Disable ipv6 by adding the following to /etc/modprobe.conf:

 

alias net-pf-10 off

 

and then reboot to disable it.

 

You need to stop the system from seeing two network cards. My preferred method would be to COMPLETELY remove the 3COM card and just use the Realtek. It cannot get confused if there is only one network card in the machine, therefore it will always be eth0 no matter what.

Link to comment
Share on other sites

If they are PCI, you should be perfectly fine to leave them as they are. I've never touched anything in my BIOS other than to look for this option and disable it. If I didn't find it, I left everything else as it was.

 

See how you get on, but you really need to make sure there is only one NIC in the machine, so remove that 3COM.

Link to comment
Share on other sites

Im taking away the 3com.

 

In my bios there is no entry PNP OS yes or no, but ive disabled the resource handling from auto to manual then leaving the choice of the IRQs to PnP. Then updated the ESCD. Im reading the plug-and-play HOWTO for Linux found online. I also set as enabled the wake up events related to pci and is set to S1.

 

Also adding in /etc/init.d/boot.local the modprobe eepro100 and disabling the ipv6.

 

Ill keep you posted,

Thanks,

Ric

Link to comment
Share on other sites

Hi!

 

My actual situation after some tests of yesterday eve are these: the Realtek nic which is the only nic in the comp behaves correctly, i can ping it and if i ask an ifup through console or using the tray icon i see it going up. I can ping it and i have a good feedback. When i try to ping the router i get an "host unreachable" mesage even if everything is well set up in the mcc: gateway ip, static ip for the nic, simply host name for my comp. What should i check or config now for override this problem? (I mean let's start from this point: nic ok, getting host unreachable message).

 

Also the router shows the connection led with the nic stable green while i get the host unreachable message.

Link to comment
Share on other sites

Is your router a firewall?  If so, ICMP might not be enabled, which is why the router isn't replying.

 

Yep it is: USR router/firewall/switch.

 

Being very stupid i didnt check if there is the gateway dev inside the /etc/sysconfig/network file, but having only one nic now i think mcc should have take care about it editing that file.

 

But how to enable it?

Link to comment
Share on other sites

To check you have configured the default gateway, type this at the prompt:

 

netstat -r

 

or

 

route

 

both will give the same results. You are looking for the line that shows "default".

Link to comment
Share on other sites

Finally im able from that comp to post some text file about some commands. Pls note that the first ifconfig was before the nic started to work in answer to some of my ifup and ifdown. Also ive found the nics works well it's their connection to the router that is lacking.

 

[root@SilicaMkV ri]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0A:5E:53:DF:7E
         inet addr:192.168.1.41  Bcast:192.168.1.255  Mask:255.255.255.0
         inet6 addr: fe80::20a:5eff:fe53:df7e/64 Scope:Link
         UP 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:10 Memory:e3000000-0

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:139 errors:0 dropped:0 overruns:0 frame:0
         TX packets:139 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:12112 (11.8 KiB)  TX bytes:12112 (11.8 KiB)

[root@SilicaMkV ri]# ifdown eth0
[root@SilicaMkV ri]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:0A:5E:53:DF:7E
         inet6 addr: fe80::20a:5eff:fe53:df7e/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:0 (0.0 B)  TX bytes:192 (192.0 B)
         Interrupt:10 Memory:e3000000-0

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:148 errors:0 dropped:0 overruns:0 frame:0
         TX packets:148 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:12922 (12.6 KiB)  TX bytes:12922 (12.6 KiB)

[root@SilicaMkV ri]#
[root@SilicaMkV ri]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:0A:5E:53:DF:7E
         inet addr:192.168.1.41  Bcast:192.168.1.255  Mask:255.255.255.0
         inet6 addr: fe80::20a:5eff:fe53:df7e/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:9538 errors:0 dropped:0 overruns:0 frame:0
         TX packets:6263 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:12595868 (12.0 MiB)  TX bytes:673125 (657.3 KiB)
         Interrupt:10 Memory:e3000000-0

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:148 errors:0 dropped:0 overruns:0 frame:0
         TX packets:148 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:12922 (12.6 KiB)  TX bytes:12922 (12.6 KiB)

sit0      Link encap:IPv6-in-IPv4
         NOARP  MTU:1480  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)

[root@SilicaMkV ri]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     10     0        0 eth0
default         192.168.1.1     0.0.0.0         UG    10     0        0 eth0
[root@SilicaMkV ri]# 

[root@SilicaMkV ri]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     10     0        0 eth0
0.0.0.0         192.168.1.1     0.0.0.0         UG    10     0        0 eth0
[root@SilicaMkV ri]#  

[root@SilicaMkV ri]# cat /etc/resolv.conf
nameserver 193.70.152.15
# nameserver 192.168.1.1

# ppp temp entry
[root@SilicaMkV ri]#

Link to comment
Share on other sites

Hi i also took away the sit0 adding the alias net-pf-10 off line to /etc/modrprobe.conf, forced no apic and no local apic, but at a reboot i got the usual situation im posting here the dump that maybe could help:

 

[root@SilicaMkV ri]# ifconfig

eth0 Link encap:Ethernet HWaddr 00:0A:5E:53:DF:7E

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets:20 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:18314 (17.8 KiB) TX bytes:0 (0.0 B)

Interrupt:10 Memory:e3000000-0

 

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:82 errors:0 dropped:0 overruns:0 frame:0

TX packets:82 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:6644 (6.4 KiB) TX bytes:6644 (6.4 KiB)

 

[root@SilicaMkV ri]# ifdown eth0

RTNETLINK answers: Network is unreachable

 

Also when i do the ruote command i get the list i posted here yesterday but it takes time for find the gateway address. This of course when i cannot connect to the router.

 

At this time after have received the RTNETLINK message i set up again the nic with mcc rebooted and the nic went up.

 

Any idea?

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share


×
×
  • Create New...