|
Raj Vardhan
|
Not Able to Start the Network
|
|
Raj Vardhan
06/15/2010 6:20 AM
post56824
|
Not Able to Start the Network
We are working on the porting of io-net driver. The earlier code used io-net and but since io-net is not available in
QNX 6.4.1 we are using io-pkt.
To start io-pkt we ran this command:
io-pkt-v4-hc -d /lib/dll/devnp-speedo.so -p tcpip
The above command ran without any error.
At This point I Checked the IFCONFIG I got the following result:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
inet 127.0.0.1 netmask 0xff000000
fxp0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
address: 00:11:22:33:aa:bb
media: Ethernet autoselct(none full-duplex)
status:active
Then I ran the dhcp.client
dhcp.client
Then I tried checking the IP address of the machine by typing IFCONFIG in the prompt.The output was:
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
inet 127.0.0.1 netmask 0xff000000
fxp0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
address: 00:11:22:33:aa:bb
media: Ethernet none
inet 0.0.0.0 netmask 0xff000000 broadcat 255.255.255.255
I then ran q conn in the prompt.
QCONN
Still I got the same result for IFCONFIG
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
inet 127.0.0.1 netmask 0xff000000
fxp0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
address: 00:11:22:33:aa:bb
media: Ethernet none
inet 0.0.0.0 netmask 0xff000000 broadcat 255.255.255.255
I even tried setting the IP address by running the command
IFCONFIG FXP0 <ip address>
An IP address gets assigned but media remains none and I m still not able to ping any other computer in the network.
Please help
|
|
|
|
|
|
Patrik Lahti
|
Re: Not Able to Start the Network
|
|
Patrik Lahti
06/15/2010 9:25 AM
post56838
|
Re: Not Able to Start the Network
Do you see any traffic using tcpdump?
/P
|
|
|
|
|
|
Raj Vardhan
|
Re: Not Able to Start the Network
|
|
Raj Vardhan
06/15/2010 10:21 AM
post56850
|
Re: Not Able to Start the Network
No.. I am not able to see any traffic using tcpdump.
|
|
|
|
|
|
Patrik Lahti
|
Re: Not Able to Start the Network
|
|
Patrik Lahti
06/15/2010 10:27 AM
post56853
|
Re: Not Able to Start the Network
So you're having a problem that the interface doesn't come up.
Have you checked the cabling?
What are you connected to?
Are you using a cross-over cable?
/P
On 10-06-15 10:21 AM, Raj Vardhan wrote:
> No.. I am not able to see any traffic using tcpdump.
|
|
|
|
|
|
Raj Vardhan
|
Re: Not Able to Start the Network
|
|
Raj Vardhan
06/16/2010 5:30 AM
post56935
|
Re: Not Able to Start the Network
Ya i have checked the cabling and all. Everything of fine.
My Network card details are:
CLASS =Network(Ethernet)
Vendor ID = 8086h , Intel Corporation
1209h, 8255xER/82551IT Fast Ethernet Controller
PCI index = 0h
PCI Mem Address = fcc20000h enabled
PCI I0 Address = 1000h enabled
PCI Mem Address = fcc 00000h enabled
PCI Expansion ROM 0h disaled
PCI Int Pin =INT A
Interrupt Line =11
CPU Inetrrupt = bh
I am using a dvnp-speedo driver? Is it correct or do i have to use devnp-e1000 driver
|
|
|
|
|
|
Patrik Lahti
|
Re: Not Able to Start the Network
|
|
Patrik Lahti
06/16/2010 9:39 AM
post56958
|
Re: Not Able to Start the Network
What are you connected to? A hub? A switch? A router? Another PC?
Do you see the lights go on on both ends?
On 10-06-16 05:31 AM, Raj Vardhan wrote:
> Ya i have checked the cabling and all. Everything of fine.
|
|
|
|
|
|
Raj Vardhan
|
Re: Not Able to Start the Network
|
|
Raj Vardhan
06/17/2010 5:44 AM
post57051
|
Re: Not Able to Start the Network
|
|
|
|
|
|
Raj Vardhan
|
Re: Not Able to Start the Network
|
|
Raj Vardhan
06/17/2010 5:45 AM
post57052
|
Re: Not Able to Start the Network
There is no light at any of the ends. but there is no problem with cabling because the old code in QNX 6.3.2 is working
fine.
|
|
|
|
|
|
Patrik Lahti
|
Re: Not Able to Start the Network
|
|
Patrik Lahti
06/17/2010 2:30 PM
post57104
|
Re: Not Able to Start the Network
Same setup, including same hub and cbles, same hardware, everything the
same... and it works in 6.3.2, but not 6.4.1? Very curious case... :-)
Because there's no light, doesn't that indicate the link isn't
establishing? Can you figure out what media the 6.3.2 negotiated and use
a driver option or ifconfig media to set the same in 6.4.1?
On 10-06-17 05:45 AM, Raj Vardhan wrote:
> There is no light at any of the ends. but there is no problem with cabling because the old code in QNX 6.3.2 is
working fine.
|
|
|
|
|
|
Raj Vardhan
|
Re: Not Able to Start the Network
|
|
Raj Vardhan
06/18/2010 6:14 AM
post57132
|
Re: Not Able to Start the Network
Today we changed the computer and tried running our code in it. The code worked perfectly fine and an IP address got
assigned to the computer. We were able to ping other systems on the network.
But the computer on which we were testing earlier is still not able get an IP address. Please note that the images
created on QNX 6.3.2 is working on both the computer.
I tried checking the SLOGGER file on both the computer.
SLOGGER result on first controller (On which the CONFIGDEBUG on QNX 6.4.1 is working fine):
Time Sev Major Minor Args
Jun18 12:32:26 5 14 0 tcpip starting
Jun18 12:32:26 5 14 0 Using pseudo random generator. See
“random” option
Jun18 12:32:27 5 14 0 Intel 82557
Jun18 12:32:27 5 14 0 Vendor …………………………..0x8086
Jun18 12:32:27 5 14 0 Device …………………………..0x1209
Jun18 12:32:27 5 14 0 Revision …………………………..0x10
Jun18 12:32:27 5 14 0 I/O port base ………………………….
.0x1000
Jun18 12:32:27 5 14 0 Memory base …………………………..
0xfcc20000
Jun18 12:32:27 5 14 0 Interrupt …………………………..0xb
Jun18 12:32:27 5 14 0 MAC address …………………………..
00e04b 0eb169
Jun18 12:33:00 5 14 0 devn-speedo: MII transceiver found
at address.
Jun18 12:33:02 5 14 0 devn-speedo: MII transceiver found
at address.
Jun18 12:33:02 5 14 0 devn-speedo: link up (100 base T
Full Duplex)
Jun18 12:33:05 2 14 0 devn-speedo:
speedo_MDI_MonitorPhy():Calling DI_monitorPhy()
While the SLOGGER file on the earlier computer says:
Time Sev Major Minor Args
Jun11 13:32:26 5 14 0 tcpip starting
Jun11 13:32:26 5 14 0 Using pseudo random generator. See
“random” option
Jun11 13:32:27 5 14 0 Unknown Chip ID
Jun11 13:32:27 5 14 0 Vendor …………………………..0x8086
Jun11 13:32:27 5 14 0 Device …………………………..0x1209
Jun11 13:32:27 5 14 0 Revision …………………………..0x10
Jun11 13:32:27 5 14 0 I/O port base ………………………….
.0x1000
Jun11 13:32:27 5 14 0 Memory base …………………………..
0xfcc20000
Jun11 13:32:27 5 14 0 Interrupt …………………………..0xb
Jun11 13:32:27 5 14 0 MAC address …………………………..
00e04b 0eb169
Jun11 13:33:00 5 14 0 devn-speedo: MII transceiver found
at address.
Jun11 13:33:02 5 14 0 devn-speedo: MII transceiver found
at address.
Jun11 13:33:05 2 14 0 devn-speedo:...
View Full Message
|
|
|
|
|
|
Andrew Boyd(deleted)
|
RE: Not Able to Start the Network
|
|
Andrew Boyd(deleted)
06/18/2010 9:14 AM
post57146
|
RE: Not Able to Start the Network
> we changed the computer ... worked perfectly fine
Sometimes when this happens, the problem might be with the
interrupt not firing for some reason. I haven't seen any
"nicinfo" or "ifconfig -v" output but a malfunctioning
interrupt looks like:
1) link is ok
2) packets are transmitted
3) no packets are received
Just a shot in the dark.
P.S. I really hate shared interrupts. Not as much as a trip to
the dentist, but they're still pretty evil:
http://community.qnx.com/sf/wiki/do/viewPage/projects.networking/wiki/Dr
ivers_wiki_page
-- cut --
Shared Interrupts - Problems?
Different devices sharing a hardware interrupt is kind of a neat idea,
but unless you really need to do it - because you've run out of hardware
interrupt lines - it generally doesn't help you much. In fact, it can
cause you trouble. For example, if your driver doesn't work - e.g. no
received packets - check and see if it is sharing an interrupt with
another device, and if so, re-configure your board so it does not.
Most of the times, when shared interrupts are configured, there is no
good reason for it - i.e. you haven't really run out of interrupts - and
this can decrease your performance, because when the interrupt fires,
ALL of the devices sharing the interrupt need to run and check and see
if it is for them. If you check the source, you can see that some
drivers do the "right thing" which is to read registers in their
interrupt handlers to see if the interrupt is really for them, and
ignore it if not. But many, many drivers do not - they schedule their
thread-level event handlers to check their hardware, which is
inefficient and reduces performance. If you are using PCI bus, use the
"pci -v" utility to check interrupt allocation. You may be surprised as
to what you see. Another point worth making is that sharing interrupts
can vastly increase interrupt latency, depending upon exactly what each
of the drivers do. Remember that after an interrupt fires, it will NOT
be re-enabled by the kernel until ALL driver handlers tell the kernel
that they have completed handling. So, if one driver takes a long, long
time servicing a shared interrupt which is masked, if another device on
the same interrupt causes an interrupt during that time period,
processing of that interrupt can be delayed for an unknown duration of
time. Bottom line is that interrupt sharing can cause problems, and
reduce performance, increase cpu consumption, and seriously increase
latency. Unless you really need to do it, don't. If you must share
interrupts, make sure your drivers are doing the "right thing". Face it
- shared interrupts are the new "trans fats" :)
-- cut --
--
aboyd www.pittspecials.com/movies/headon.wmv
|
|
|
|
|
|
Yao Zhao(deleted)
|
Re: Not Able to Start the Network
|
|
Yao Zhao(deleted)
06/15/2010 9:29 AM
post56839
|
Re: Not Able to Start the Network
> We are working on the porting of io-net driver. The earlier code used io-net
> and but since io-net is not available in QNX 6.4.1 we are using io-pkt.
>
> To start io-pkt we ran this command:
>
> io-pkt-v4-hc -d /lib/dll/devnp-speedo.so -p tcpip
>
> The above command ran without any error.
> At This point I Checked the IFCONFIG I got the following result:
>
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
> inet 127.0.0.1 netmask 0xff000000
> fxp0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
> address: 00:11:22:33:aa:bb
> media: Ethernet autoselct(none full-duplex)
> status:active
>
> Then I ran the dhcp.client
> dhcp.client
>
> Then I tried checking the IP address of the machine by typing IFCONFIG in the
> prompt.The output was:
>
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
> inet 127.0.0.1 netmask 0xff000000
> fxp0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
> address: 00:11:22:33:aa:bb
> media: Ethernet none
> inet 0.0.0.0 netmask 0xff000000 broadcat 255.255.255.255
>
> I then ran q conn in the prompt.
> QCONN
>
> Still I got the same result for IFCONFIG
>
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
> inet 127.0.0.1 netmask 0xff000000
> fxp0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
> address: 00:11:22:33:aa:bb
> media: Ethernet none
> inet 0.0.0.0 netmask 0xff000000 broadcat 255.255.255.255
>
> I even tried setting the IP address by running the command
> IFCONFIG FXP0 <ip address>
>
> An IP address gets assigned but media remains none and I m still not able to
> ping any other computer in the network.
> Please help
fxp0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
address: 00:11:22:33:aa:bb
media: Ethernet none
inet 0.0.0.0 netmask 0xff000000 broadcat 255.255.255.255
interface is not up even:(
|
|
|
|
|
|
