LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 08-25-2007, 06:28 AM   #1
tkmsr
Member
 
Registered: Oct 2006
Distribution: Ubuntu,Open Suse,Debian,Mac OS X
Posts: 798

Rep: Reputation: 38
modules conflicting each other


I installed new kernel 2.6.22.4 for making the intex lan card work for SC92031 chipset id did not worked insteag gave me errors now I used NDISWRAPPER and used
ndiswrapper -i slnt.inf slnt.sys
from the drivers directoty
the result was the PCI lan card which was not working started working but the onboard realtek lan card which was working previously stopped working


output of ifconfig is

# ifconfig -a
eth3 Link encap:Ethernet HWaddr 00:E0:20:80:0F:49
inet addr:192.168.0.45 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:210214 errors:0 dropped:0 overruns:0 frame:0
TX packets:6554 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:22781469 (21.7 Mb) TX bytes:857635 (837.5 Kb)
Interrupt:18 Memory:30000000-300000ff

eth4 Link encap:Ethernet HWaddr 00:191:3B:53:1B
inet addr:192.168.0.44 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:56980 errors:0 dropped:0 overruns:0 frame:0
TX packets:75 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5877708 (5.6 Mb) TX bytes:10772 (10.5 Kb)
Interrupt:21 Base address:0x6100

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:519482 errors:0 dropped:0 overruns:0 frame:0
TX packets:519482 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:44375408 (42.3 Mb) TX bytes:44375408 (42.3 Mb)



The strang behaviour here is that when I do

#ifup eth4 (which was my lan card on board that was working fine before new kernel and ndiswrapper isntallation)

and then
# ping 192.168.0.123
PING 192.168.0.123 (192.168.0.123) 56(84) bytes of data.
From 192.168.0.45 icmp_seq=1 Destination Host Unreachable
From 192.168.0.45 icmp_seq=2 Destination Host Unreachable
From 192.168.0.45 icmp_seq=3 Destination Host Unreachable



note here ping reply is coming from 192.168.0.45 machine which should not answer (I might be wrong) and I have unplugged the lan wire from the eth3 lan card
which files I should look in for this phenomenon is occuring in Open Suse 10.2


where as if I plug the lan wire in eth3 then

# ping 192.168.0.123
PING 192.168.0.123 (192.168.0.123) 56(84) bytes of data.
64 bytes from 192.168.0.123: icmp_seq=1 ttl=128 time=0.166 ms
64 bytes from 192.168.0.123: icmp_seq=2 ttl=128 time=0.137 ms




can some one help me to tell what log file should I check now after so many changes
I am totally confused what service is conflicting here

Last edited by tkmsr; 08-25-2007 at 06:44 AM.
 
Old 08-25-2007, 07:19 AM   #2
sundialsvcs
Guru
 
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 5,230

Rep: Reputation: 1071Reputation: 1071Reputation: 1071Reputation: 1071Reputation: 1071Reputation: 1071Reputation: 1071Reputation: 1071
There might not actually be a conflict here, just a confusing (to you) set of symptoms.

Code:
# ping 192.168.0.123
 PING 192.168.0.123 (192.168.0.123) 56(84) bytes of data.
 From 192.168.0.45 icmp_seq=1 Destination Host Unreachable
Most likely, 192.168.0.45 is your IP-address. (And so it is... ifconfig confirms that it's your eth3 device.)

If you can see the device, e.g. in ifconfig, then you do not have a driver problem. You might well have a routing-table problem. For example, the command /sbin/route (or somesuch, maybe /sbin/ip route) will show you where requests for particular IP-addresses will be sent. The phrase "host unreachable" could simply mean that the packets are being sent to a device whose cable isn't plugged in at the moment, even though another interface is.

Your computer must be told where to send packets. There are daemons that can watch for "cable inserted" events and (among other things) change the routing tables on-the-fly, but ultimately the computer must somehow be told which packets should be sent to which wire(less).

And now, "Wise man say..."

As you are working through changes like this, one of your trusty tools should be a three-ring binder (notebook) and a few sharp number-two pencils. Keep a diary in it. As you do things, print off pages and three-hole-punch them and add them, with today's date, to the notebook.

Writing things down long-hand in pencil, legibly ... not only is that impervious to a computer-crash (and to errant cups of coffee), but it also forces you to slow down and think. If you have a question along the way, write it down. And so on. When you have completed the change to your satisfaction, you can print a summary-page and add it to the log. This log becomes a permanent reference tool, and it's valuable "even if it's 'just you.'"
 
Old 08-25-2007, 09:06 AM   #3
tkmsr
Member
 
Registered: Oct 2006
Distribution: Ubuntu,Open Suse,Debian,Mac OS X
Posts: 798

Original Poster
Rep: Reputation: 38
The same lan card is working in my older kernel without any problem and I have seen the route -n before posting there was nothing unusual but when I boot from the new kernel the other card
eth3 works but in older kernel eth4 works and in older kernel the eth3 is not coming the output in older kernel is

# ifconfig -a
eth4 Link encap:Ethernet HWaddr 00:191:3B:53:1B
inet addr:192.168.0.44 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21965 errors:0 dropped:0 overruns:0 frame:0
TX packets:868 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2817469 (2.6 Mb) TX bytes:191399 (186.9 Kb)
Interrupt:169 Base address:0x4100


and
# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth4
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth4
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo




the above route is same on both the kernels


Note here in older kernel the card eth3 is not visible because of which I have done all this compilation etc
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
conflicting dependencies? doowttam Linux - Newbie 5 03-19-2006 02:52 AM
conflicting files mab_123 Linux - Software 2 01-30-2005 02:43 AM
Conflicting packages apokryphos Linux - Software 3 10-02-2004 03:20 AM
Re: modprobe: Note: /etc/modules.conf is more recent than lib/modules/2.4.9/modules.d Andy.M Linux - General 1 01-24-2002 01:50 AM
Re: modprobe: Note: /etc/modules.conf is more recent than lib/modules/2.4.9/modules.d Andy.M Linux - Newbie 2 01-24-2002 01:40 AM


All times are GMT -5. The time now is 08:50 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration