tcpip problems

bridged with qdn.public.ddk.network
Post Reply
Viraj

tcpip problems

Post by Viraj » Mon Aug 11, 2003 5:33 pm

Hello,
Hoping for some help with the following:
I have a start-up script with the as follows:
io-net -dspeedo -ptcpip
ifconfig en0 192.168.0.11
route add default 192.168.0.1
I can 'Ping' myself (192.168.0.11) but I can't ping anything else.
192.168.0.1 is a netgear router. I have another PC is 192.168.0.2 neither
one can be reached. I get the error message "host is Down"
Any ideas/suggestions
Thanks
Viraj

Dmitri Poustovalov

Re: tcpip problems

Post by Dmitri Poustovalov » Tue Aug 12, 2003 11:55 am

Are netmasks the same? What nicinfo output says?

Viraj wrote:
Hello,
Hoping for some help with the following:
I have a start-up script with the as follows:
io-net -dspeedo -ptcpip
ifconfig en0 192.168.0.11
route add default 192.168.0.1
I can 'Ping' myself (192.168.0.11) but I can't ping anything else.
192.168.0.1 is a netgear router. I have another PC is 192.168.0.2 neither
one can be reached. I get the error message "host is Down"
Any ideas/suggestions
Thanks
Viraj

Viraj

Re: tcpip problems

Post by Viraj » Tue Aug 12, 2003 7:56 pm

# nicinfo

Intel 82557 Ethernet Controller
Physical Node ID ................. 0004BF 803841
Current Physical Node ID ......... 0004BF 803841
Media Rate ....................... 100Mb/s half-duplex UTP
Mtu .............................. 1514
Lan .............................. 0
I/O Port Range ................... 0xFD00 -> 0xFD3F
Hardware Interrupt ............... 0x2
Promiscuous....................... Disabled
Multicast......................... Enabled

Total Packets Txd OK ............. 3
Total Packets Txd Bad ............ 0
Total Packets Rxd OK ............. 3
Total Rx errors .................. 0
Total Bytes Txd....................166
Total Bytes Rxd....................0
Tx Collision Errors .............. 0
Tx Collisions Errors (aborted) ... 0
Carrier Sense Lost on Tx ......... 1
FIFO Underruns During Tx ......... 0
Tx defered ....................... 0
Out of Window Collisions ......... 0
FIFO Overruns During Rx .......... 0
Alignment errors ................. 0
CRC errors ....................... 0


All netmasks are set to 255.255.255.0


The actual netstat -r info is as followsnet
#netstat -r

Internet:
Destination Gateway Flags Ref Use MTU Interface
default 192.168.0.1 UGS 0 0 - en0
localhost localhost UH 0 0 - lo0
192.168 192.168.0.11 U 1 11 - en0
192.168.0.11 192.168.0.11 UH 0 0 - lo0

When I try to ping something on another subnet (not actually on the system
though the netstat looks as follows:

#netstat -r

Internet:
Destination Gateway Flags Ref Use MTU Interface
default 192.168.0.1 UGS 0 9 - en0
localhost localhost UH 0 0 - lo0
192.168 192.168.0.11 U 1 11 - en0
192.168.0.11 192.168.0.11 UH 0 0 - lo0

Yet there is no activity on the router What am I doing wrong?

Thanks
Viraj


Dmitri Poustovalov wrote:
Are netmasks the same? What nicinfo output says?

Viraj wrote:
Hello,
Hoping for some help with the following:
I have a start-up script with the as follows:
io-net -dspeedo -ptcpip
ifconfig en0 192.168.0.11
route add default 192.168.0.1
I can 'Ping' myself (192.168.0.11) but I can't ping anything else.
192.168.0.1 is a netgear router. I have another PC is 192.168.0.2 neither
one can be reached. I get the error message "host is Down"
Any ideas/suggestions
Thanks
Viraj

Sreekanth

Re: tcpip problems

Post by Sreekanth » Wed Aug 13, 2003 12:26 am

At the risk of being called a paranoid, i ask you..Can you ping 192.168.0.1
(Netgear Router) from 192.168.0.2 (Another PC) ? If yes..Swap the network
cables of 192.168.0.2 and your Qnx box.As far as i feel, there is no issue
with routing or netstat.One more thing you could is to delete the arp
entry( arp -d 192.168.0.1) and try again.

Hope it helps,

Sreekanth

"Viraj" <viraj982003@yahoo.com> wrote in message
news:bhbgon$u01$1@tiger.openqnx.com...
# nicinfo

Intel 82557 Ethernet Controller
Physical Node ID ................. 0004BF 803841
Current Physical Node ID ......... 0004BF 803841
Media Rate ....................... 100Mb/s half-duplex UTP
Mtu .............................. 1514
Lan .............................. 0
I/O Port Range ................... 0xFD00 -> 0xFD3F
Hardware Interrupt ............... 0x2
Promiscuous....................... Disabled
Multicast......................... Enabled

Total Packets Txd OK ............. 3
Total Packets Txd Bad ............ 0
Total Packets Rxd OK ............. 3
Total Rx errors .................. 0
Total Bytes Txd....................166
Total Bytes Rxd....................0
Tx Collision Errors .............. 0
Tx Collisions Errors (aborted) ... 0
Carrier Sense Lost on Tx ......... 1
FIFO Underruns During Tx ......... 0
Tx defered ....................... 0
Out of Window Collisions ......... 0
FIFO Overruns During Rx .......... 0
Alignment errors ................. 0
CRC errors ....................... 0


All netmasks are set to 255.255.255.0


The actual netstat -r info is as followsnet
#netstat -r

Internet:
Destination Gateway Flags Ref Use MTU Interface
default 192.168.0.1 UGS 0 0 - en0
localhost localhost UH 0 0 - lo0
192.168 192.168.0.11 U 1 11 - en0
192.168.0.11 192.168.0.11 UH 0 0 - lo0

When I try to ping something on another subnet (not actually on the system
though the netstat looks as follows:

#netstat -r

Internet:
Destination Gateway Flags Ref Use MTU Interface
default 192.168.0.1 UGS 0 9 - en0
localhost localhost UH 0 0 - lo0
192.168 192.168.0.11 U 1 11 - en0
192.168.0.11 192.168.0.11 UH 0 0 - lo0

Yet there is no activity on the router What am I doing wrong?

Thanks
Viraj


Dmitri Poustovalov wrote:

Are netmasks the same? What nicinfo output says?

Viraj wrote:
Hello,
Hoping for some help with the following:
I have a start-up script with the as follows:
io-net -dspeedo -ptcpip
ifconfig en0 192.168.0.11
route add default 192.168.0.1
I can 'Ping' myself (192.168.0.11) but I can't ping anything else.
192.168.0.1 is a netgear router. I have another PC is 192.168.0.2
neither
one can be reached. I get the error message "host is Down"
Any ideas/suggestions
Thanks
Viraj






Sreekanth

Re: tcpip problems

Post by Sreekanth » Wed Aug 13, 2003 12:36 am

One more thing i noticed that your netmask is 255.255 not 255.255.255.0 as
you mentioned.I could infer it from the netstat output
192.168 192.168.0.11 U 1 11 - en0
Could you also post the ifconfig -a output?
Sreekanth

"Viraj" <viraj982003@yahoo.com> wrote in message
news:bhbgon$u01$1@tiger.openqnx.com...
# nicinfo

Intel 82557 Ethernet Controller
Physical Node ID ................. 0004BF 803841
Current Physical Node ID ......... 0004BF 803841
Media Rate ....................... 100Mb/s half-duplex UTP
Mtu .............................. 1514
Lan .............................. 0
I/O Port Range ................... 0xFD00 -> 0xFD3F
Hardware Interrupt ............... 0x2
Promiscuous....................... Disabled
Multicast......................... Enabled

Total Packets Txd OK ............. 3
Total Packets Txd Bad ............ 0
Total Packets Rxd OK ............. 3
Total Rx errors .................. 0
Total Bytes Txd....................166
Total Bytes Rxd....................0
Tx Collision Errors .............. 0
Tx Collisions Errors (aborted) ... 0
Carrier Sense Lost on Tx ......... 1
FIFO Underruns During Tx ......... 0
Tx defered ....................... 0
Out of Window Collisions ......... 0
FIFO Overruns During Rx .......... 0
Alignment errors ................. 0
CRC errors ....................... 0


All netmasks are set to 255.255.255.0


The actual netstat -r info is as followsnet
#netstat -r

Internet:
Destination Gateway Flags Ref Use MTU Interface
default 192.168.0.1 UGS 0 0 - en0
localhost localhost UH 0 0 - lo0
192.168 192.168.0.11 U 1 11 - en0
192.168.0.11 192.168.0.11 UH 0 0 - lo0

When I try to ping something on another subnet (not actually on the system
though the netstat looks as follows:

#netstat -r

Internet:
Destination Gateway Flags Ref Use MTU Interface
default 192.168.0.1 UGS 0 9 - en0
localhost localhost UH 0 0 - lo0
192.168 192.168.0.11 U 1 11 - en0
192.168.0.11 192.168.0.11 UH 0 0 - lo0

Yet there is no activity on the router What am I doing wrong?

Thanks
Viraj


Dmitri Poustovalov wrote:

Are netmasks the same? What nicinfo output says?

Viraj wrote:
Hello,
Hoping for some help with the following:
I have a start-up script with the as follows:
io-net -dspeedo -ptcpip
ifconfig en0 192.168.0.11
route add default 192.168.0.1
I can 'Ping' myself (192.168.0.11) but I can't ping anything else.
192.168.0.1 is a netgear router. I have another PC is 192.168.0.2
neither
one can be reached. I get the error message "host is Down"
Any ideas/suggestions
Thanks
Viraj






Warren Deitch

Re: tcpip problems

Post by Warren Deitch » Wed Aug 13, 2003 1:29 am

IRQ 2 is not possible for a standard board ! IRQ 2 is usually
redirected to IRQ 9 ! Check your settings (may need to check BIOS irq
settings)


Sreekanth wrote:
One more thing i noticed that your netmask is 255.255 not 255.255.255.0 as
you mentioned.I could infer it from the netstat output

192.168 192.168.0.11 U 1 11 - en0

Could you also post the ifconfig -a output?

Sreekanth

"Viraj" <viraj982003@yahoo.com> wrote in message
news:bhbgon$u01$1@tiger.openqnx.com...

# nicinfo

Intel 82557 Ethernet Controller
Physical Node ID ................. 0004BF 803841
Current Physical Node ID ......... 0004BF 803841
Media Rate ....................... 100Mb/s half-duplex UTP
Mtu .............................. 1514
Lan .............................. 0
I/O Port Range ................... 0xFD00 -> 0xFD3F
Hardware Interrupt ............... 0x2
Promiscuous....................... Disabled
Multicast......................... Enabled

Total Packets Txd OK ............. 3
Total Packets Txd Bad ............ 0
Total Packets Rxd OK ............. 3
Total Rx errors .................. 0
Total Bytes Txd....................166
Total Bytes Rxd....................0
Tx Collision Errors .............. 0
Tx Collisions Errors (aborted) ... 0
Carrier Sense Lost on Tx ......... 1
FIFO Underruns During Tx ......... 0
Tx defered ....................... 0
Out of Window Collisions ......... 0
FIFO Overruns During Rx .......... 0
Alignment errors ................. 0
CRC errors ....................... 0


All netmasks are set to 255.255.255.0


The actual netstat -r info is as followsnet
#netstat -r

Internet:
Destination Gateway Flags Ref Use MTU Interface
default 192.168.0.1 UGS 0 0 - en0
localhost localhost UH 0 0 - lo0
192.168 192.168.0.11 U 1 11 - en0
192.168.0.11 192.168.0.11 UH 0 0 - lo0

When I try to ping something on another subnet (not actually on the system
though the netstat looks as follows:

#netstat -r

Internet:
Destination Gateway Flags Ref Use MTU Interface
default 192.168.0.1 UGS 0 9 - en0
localhost localhost UH 0 0 - lo0
192.168 192.168.0.11 U 1 11 - en0
192.168.0.11 192.168.0.11 UH 0 0 - lo0

Yet there is no activity on the router What am I doing wrong?

Thanks
Viraj


Dmitri Poustovalov wrote:


Are netmasks the same? What nicinfo output says?

Viraj wrote:

Hello,
Hoping for some help with the following:
I have a start-up script with the as follows:
io-net -dspeedo -ptcpip
ifconfig en0 192.168.0.11
route add default 192.168.0.1
I can 'Ping' myself (192.168.0.11) but I can't ping anything else.
192.168.0.1 is a netgear router. I have another PC is 192.168.0.2

neither

one can be reached. I get the error message "host is Down"
Any ideas/suggestions
Thanks
Viraj








David Gibbs

Re: tcpip problems

Post by David Gibbs » Wed Aug 13, 2003 3:48 pm

Warren Deitch <warren.deitch@transcore.com.au> wrote:
IRQ 2 is not possible for a standard board ! IRQ 2 is usually
redirected to IRQ 9 ! Check your settings (may need to check BIOS irq
settings)
And, an attempt to attach to irq 2 will fail under 6.2.1.

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

Viraj

Re: tcpip problems

Post by Viraj » Wed Aug 13, 2003 4:05 pm

The BIOS has PCI INT C (Ehternet) set to IRQ 11
I changed it to IRQ9 (no difference) There was no IRQ2 available
the ifconfig -a has the following:
lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 32976
inet 127.0.0.1 netmask 0xff000000
en0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>mtu 1500
address:00:04:bf:80:38:41
inet 192.168.0.11 netmask 0xffffff00 broadcast 192.168.0.255


-Viraj







Sreekanth wrote:
At the risk of being called a paranoid, i ask you..Can you ping 192.168.0.1
(Netgear Router) from 192.168.0.2 (Another PC) ? If yes..Swap the network
cables of 192.168.0.2 and your Qnx box.As far as i feel, there is no issue
with routing or netstat.One more thing you could is to delete the arp
entry( arp -d 192.168.0.1) and try again.

Hope it helps,

Sreekanth

"Viraj" <viraj982003@yahoo.com> wrote in message
news:bhbgon$u01$1@tiger.openqnx.com...
# nicinfo

Intel 82557 Ethernet Controller
Physical Node ID ................. 0004BF 803841
Current Physical Node ID ......... 0004BF 803841
Media Rate ....................... 100Mb/s half-duplex UTP
Mtu .............................. 1514
Lan .............................. 0
I/O Port Range ................... 0xFD00 -> 0xFD3F
Hardware Interrupt ............... 0x2
Promiscuous....................... Disabled
Multicast......................... Enabled

Total Packets Txd OK ............. 3
Total Packets Txd Bad ............ 0
Total Packets Rxd OK ............. 3
Total Rx errors .................. 0
Total Bytes Txd....................166
Total Bytes Rxd....................0
Tx Collision Errors .............. 0
Tx Collisions Errors (aborted) ... 0
Carrier Sense Lost on Tx ......... 1
FIFO Underruns During Tx ......... 0
Tx defered ....................... 0
Out of Window Collisions ......... 0
FIFO Overruns During Rx .......... 0
Alignment errors ................. 0
CRC errors ....................... 0


All netmasks are set to 255.255.255.0


The actual netstat -r info is as followsnet
#netstat -r

Internet:
Destination Gateway Flags Ref Use MTU Interface
default 192.168.0.1 UGS 0 0 - en0
localhost localhost UH 0 0 - lo0
192.168 192.168.0.11 U 1 11 - en0
192.168.0.11 192.168.0.11 UH 0 0 - lo0

When I try to ping something on another subnet (not actually on the system
though the netstat looks as follows:

#netstat -r

Internet:
Destination Gateway Flags Ref Use MTU Interface
default 192.168.0.1 UGS 0 9 - en0
localhost localhost UH 0 0 - lo0
192.168 192.168.0.11 U 1 11 - en0
192.168.0.11 192.168.0.11 UH 0 0 - lo0

Yet there is no activity on the router What am I doing wrong?

Thanks
Viraj


Dmitri Poustovalov wrote:

Are netmasks the same? What nicinfo output says?

Viraj wrote:
Hello,
Hoping for some help with the following:
I have a start-up script with the as follows:
io-net -dspeedo -ptcpip
ifconfig en0 192.168.0.11
route add default 192.168.0.1
I can 'Ping' myself (192.168.0.11) but I can't ping anything else.
192.168.0.1 is a netgear router. I have another PC is 192.168.0.2
neither
one can be reached. I get the error message "host is Down"
Any ideas/suggestions
Thanks
Viraj






Viraj

Re: tcpip problems

Post by Viraj » Mon Aug 18, 2003 7:39 pm

When performing the function, pci, it lists the intel 82559er chip as
being assigned to pci int A. The bios has the ethernet pci int C. is there
a way to change the speedo driver to look on int C?

This board has communicated from a DOS operating system, so I know the
hardware works fine.




David Gibbs wrote:
Warren Deitch <warren.deitch@transcore.com.au> wrote:
IRQ 2 is not possible for a standard board ! IRQ 2 is usually
redirected to IRQ 9 ! Check your settings (may need to check BIOS irq
settings)

And, an attempt to attach to irq 2 will fail under 6.2.1.

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

Hugh Brown

Re: tcpip problems

Post by Hugh Brown » Tue Aug 19, 2003 12:05 pm

This is a single function device, so it can only work on INT A. What
you have to worry about is which interrupt line it is connected to.
The interrupt PIN is fixed and cannot be moved, but the interrupt
LINE can be changed. If you post the output from 'pci -v' it would
be more helpful.

Previously, Viraj wrote in qdn.public.ddk.network:
When performing the function, pci, it lists the intel 82559er chip as
being assigned to pci int A. The bios has the ethernet pci int C. is there
a way to change the speedo driver to look on int C?

This board has communicated from a DOS operating system, so I know the
hardware works fine.




David Gibbs wrote:

Warren Deitch <warren.deitch@transcore.com.au> wrote:
IRQ 2 is not possible for a standard board ! IRQ 2 is usually
redirected to IRQ 9 ! Check your settings (may need to check BIOS irq
settings)

And, an attempt to attach to irq 2 will fail under 6.2.1.

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.



Viraj

Re: tcpip problems

Post by Viraj » Tue Aug 19, 2003 12:48 pm

PCI version = 2.10



Class = Bridge (Host/PCI)

Vendor ID = 1022h, Advanced Micro Devices

Device ID = 3000h, Unknown Unknown

PCI index = 0h

Class Codes = 060000h

Revision ID = 0h

Bus number = 0

Device number = 0

Function num = 0

Status Reg = 2280h

Command Reg = 6h

Header type = 0h Single-function

BIST = 0h Build-in-self-test not supported

Latency Timer = 0h

Cache Line Size= 0h

Max Lat = 0ns

Min Gnt = 0ns

PCI Int Pin = NC

Interrupt line = 0



Class = Network (Ethernet)

Vendor ID = 8086h, Intel Corporation

Device ID = 1209h, 82559ER

PCI index = 0h

Class Codes = 020000h

Revision ID = 9h

Bus number = 0

Device number = 16

Function num = 0

Status Reg = 290h

Command Reg = 7h

Header type = 0h Single-function

BIST = 0h Build-in-self-test not supported

Latency Timer = 40h

Cache Line Size= 8h un-cacheable

PCI Mem Address = c0000000h 32bit length 4096 enabled

PCI IO Address = fd00h length 64 enabled

PCI Mem Address = c0020000h 32bit length 131072 enabled

Max Lat = 56ns

Min Gnt = 8ns

PCI Int Pin = INT A

Interrupt line = 2

Capabilities Pointer = dch

Capability ID = 1h

Capabilities = 7e22h - 3c004000h



Class = Display (VGA)

Vendor ID = 102ch, Chips And Technologies

Device ID = e0h, 65550 LCD/CRT controller

PCI index = 0h

Class Codes = 030000h

Revision ID = c6h

Bus number = 0

Device number = 17

Function num = 0

Status Reg = 280h

Command Reg = 83h

Header type = 0h Single-function

BIST = 0h Build-in-self-test not supported

Latency Timer = 0h

Cache Line Size= 0h

PCI Mem Address = c1000000h 32bit length 16777216 enabled

PCI Expansion ROM = ff000000h length 262144 disabled

Max Lat = 0ns

Min Gnt = 0ns

PCI Int Pin = NC

Interrupt line = 0




Hugh Brown wrote:
This is a single function device, so it can only work on INT A. What
you have to worry about is which interrupt line it is connected to.
The interrupt PIN is fixed and cannot be moved, but the interrupt
LINE can be changed. If you post the output from 'pci -v' it would
be more helpful.

Previously, Viraj wrote in qdn.public.ddk.network:
When performing the function, pci, it lists the intel 82559er chip as
being assigned to pci int A. The bios has the ethernet pci int C. is there
a way to change the speedo driver to look on int C?

This board has communicated from a DOS operating system, so I know the
hardware works fine.




David Gibbs wrote:

Warren Deitch <warren.deitch@transcore.com.au> wrote:
IRQ 2 is not possible for a standard board ! IRQ 2 is usually
redirected to IRQ 9 ! Check your settings (may need to check BIOS irq
settings)

And, an attempt to attach to irq 2 will fail under 6.2.1.

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.



Hugh Brown

Re: tcpip problems

Post by Hugh Brown » Tue Aug 19, 2003 1:40 pm

Is this some type of embedded system? I see that the ethernet chip
is connect to IRQ2 which is normally a cascade interrupt from IRQ8.

Previously, Viraj wrote in qdn.public.ddk.network:
PCI version = 2.10



Class = Bridge (Host/PCI)

Vendor ID = 1022h, Advanced Micro Devices

Device ID = 3000h, Unknown Unknown

PCI index = 0h

Class Codes = 060000h

Revision ID = 0h

Bus number = 0

Device number = 0

Function num = 0

Status Reg = 2280h

Command Reg = 6h

Header type = 0h Single-function

BIST = 0h Build-in-self-test not supported

Latency Timer = 0h

Cache Line Size= 0h

Max Lat = 0ns

Min Gnt = 0ns

PCI Int Pin = NC

Interrupt line = 0



Class = Network (Ethernet)

Vendor ID = 8086h, Intel Corporation

Device ID = 1209h, 82559ER

PCI index = 0h

Class Codes = 020000h

Revision ID = 9h

Bus number = 0

Device number = 16

Function num = 0

Status Reg = 290h

Command Reg = 7h

Header type = 0h Single-function

BIST = 0h Build-in-self-test not supported

Latency Timer = 40h

Cache Line Size= 8h un-cacheable

PCI Mem Address = c0000000h 32bit length 4096 enabled

PCI IO Address = fd00h length 64 enabled

PCI Mem Address = c0020000h 32bit length 131072 enabled

Max Lat = 56ns

Min Gnt = 8ns

PCI Int Pin = INT A

Interrupt line = 2

Capabilities Pointer = dch

Capability ID = 1h

Capabilities = 7e22h - 3c004000h



Class = Display (VGA)

Vendor ID = 102ch, Chips And Technologies

Device ID = e0h, 65550 LCD/CRT controller

PCI index = 0h

Class Codes = 030000h

Revision ID = c6h

Bus number = 0

Device number = 17

Function num = 0

Status Reg = 280h

Command Reg = 83h

Header type = 0h Single-function

BIST = 0h Build-in-self-test not supported

Latency Timer = 0h

Cache Line Size= 0h

PCI Mem Address = c1000000h 32bit length 16777216 enabled

PCI Expansion ROM = ff000000h length 262144 disabled

Max Lat = 0ns

Min Gnt = 0ns

PCI Int Pin = NC

Interrupt line = 0




Hugh Brown wrote:

This is a single function device, so it can only work on INT A. What
you have to worry about is which interrupt line it is connected to.
The interrupt PIN is fixed and cannot be moved, but the interrupt
LINE can be changed. If you post the output from 'pci -v' it would
be more helpful.

Previously, Viraj wrote in qdn.public.ddk.network:
When performing the function, pci, it lists the intel 82559er chip as
being assigned to pci int A. The bios has the ethernet pci int C. is there
a way to change the speedo driver to look on int C?

This board has communicated from a DOS operating system, so I know the
hardware works fine.




David Gibbs wrote:

Warren Deitch <warren.deitch@transcore.com.au> wrote:
IRQ 2 is not possible for a standard board ! IRQ 2 is usually
redirected to IRQ 9 ! Check your settings (may need to check BIOS irq
settings)

And, an attempt to attach to irq 2 will fail under 6.2.1.

-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.








Post Reply

Return to “qdn.public.ddk.network”