Help Configuring Cable Modem for QNX Needed

Heyla all, I’m Stormis, and I was wondering…

I’m just getting started with QNX again, now that I have a non-proprietary
connection to the internet, and I’ve run into a problem, it seems.

I haven’t the foggiest clue as to how to set up my Ericsson PipeRider
cablemodem (and anything else that is needed) on my box.
I tried reading the manual… I looked up an article in the self help
area…
…and it makes no sense to me - it seems to be written for the more
tech-savvy user.

If anyone is willing to help me, I would be graeful. ^^

the NIC is a CNET PRO200WL PCI Fast Ethernet Adapter, and i’m connected via
RoadRunner.
If i need more info, please, tell me. :slight_smile:

SDEdgecrusher

At http://www.linuxdoc.org/HOWTO/Cable-Modem/index.html you will find the
Linux Cable modem HOWTO. This has specific notes for various providers
(including RoadRunner). Now things will be a little different with QNX but
the principles will be the same. You’ll need to bring the interface up
with DHCP to obtain your IP. Some providers require additional stuff - for
instance, I’m with rogers@home and they give you a special hostname that
needs to be set for dhcp to work. For starters I’d probably just hook it up
and see if it comes up automatically. The default configuration for a
network card in RTP is DHCP.

cheers,

Kris

Stormis Edgecrusher <qdn.inn.qnx.com@stormis.org> wrote:

Heyla all, I’m Stormis, and I was wondering…

I’m just getting started with QNX again, now that I have a non-proprietary
connection to the internet, and I’ve run into a problem, it seems.

I haven’t the foggiest clue as to how to set up my Ericsson PipeRider
cablemodem (and anything else that is needed) on my box.
I tried reading the manual… I looked up an article in the self help
area…
…and it makes no sense to me - it seems to be written for the more
tech-savvy user.

If anyone is willing to help me, I would be graeful. ^^

the NIC is a CNET PRO200WL PCI Fast Ethernet Adapter, and i’m connected via
RoadRunner.
If i need more info, please, tell me. > :slight_smile:

SDEdgecrusher


Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“I love deadlines. I like the whooshing sound they make as they fly by.”
– Douglas Adams

O_O
okay…
I couldn’t make sense of that at all.
all this typethis, poke that, dhcp left, turn the knob one-half circle…
;;
I couldn’t make heads or tails of any of it. :frowning:
-
-; i guess i should just stick to windows for the 'net.
Thanks, anyway.

SDEdgecrusher

“Kris Eric Warkentin” <kewarken@qnx.com> wrote in message
news:9pcc8e$ds9$1@nntp.qnx.com

At > http://www.linuxdoc.org/HOWTO/Cable-Modem/index.html > you will find the
Linux Cable modem HOWTO. This has specific notes for various providers
(including RoadRunner). Now things will be a little different with QNX
but
the principles will be the same. You’ll need to bring the interface up
with DHCP to obtain your IP. Some providers require additional stuff -
for
instance, I’m with rogers@home and they give you a special hostname that
needs to be set for dhcp to work. For starters I’d probably just hook it
up
and see if it comes up automatically. The default configuration for a
network card in RTP is DHCP.

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
Heyla all, I’m Stormis, and I was wondering…

I’m just getting started with QNX again, now that I have a
non-proprietary
connection to the internet, and I’ve run into a problem, it seems.

I haven’t the foggiest clue as to how to set up my Ericsson PipeRider
cablemodem (and anything else that is needed) on my box.
I tried reading the manual… I looked up an article in the self help
area…
…and it makes no sense to me - it seems to be written for the more
tech-savvy user.

If anyone is willing to help me, I would be graeful. ^^

the NIC is a CNET PRO200WL PCI Fast Ethernet Adapter, and i’m connected
via
RoadRunner.
If i need more info, please, tell me. > :slight_smile:

SDEdgecrusher


\

Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“I love deadlines. I like the whooshing sound they make as they fly by.”
– Douglas Adams

Well, it might not be that bad…if your ethernet card works under RTP,
we should be able to get the cable modem up and running.

Try going into the network configuration menu. It’s the little network
icon on the shelf or you can run ‘phlip’ at the command line. You’ll need
to be root. Under the ‘devices’ tab you should have a network card ‘en0’,
assuming that your card has been autodetected. If you set the connection
type to “DHCP”, you may get an IP from your cable modem. If nothing else,
you should see some ‘blinkenlights’ on the modem showing that the network
card is trying to talk to it. If it works, the ‘network’ tab should show
you some information about the IP, etc.

Now I’m still working on the assumption that your ethernet card is working
properly. If it isn’t, you have to solve that problem first. The next thing
to try if the interface failed to come up in the last step is to enter an ID.

I don’t know how RoadRunner works but when you get setup for Rogers@home, they
give you a weird hostname like crd-10382 that you have to set in windows. It
would be under ‘My Computer’/properties/network identification (or something
like that) If there is something special that needs to be set, then you might
want to try putting that into the ID field in the devices tab of phlip.

Give it a try…you might get lucky. :wink:

cheers,

Kris

Stormis Edgecrusher <qdn.inn.qnx.com@stormis.org> wrote:

O_O
okay…
I couldn’t make sense of that at all.
all this typethis, poke that, dhcp left, turn the knob one-half circle…
;;
I couldn’t make heads or tails of any of it. > :frowning:
-
-; i guess i should just stick to windows for the 'net.
Thanks, anyway.

SDEdgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pcc8e$ds9$> 1@nntp.qnx.com> …

At > http://www.linuxdoc.org/HOWTO/Cable-Modem/index.html > you will find the
Linux Cable modem HOWTO. This has specific notes for various providers
(including RoadRunner). Now things will be a little different with QNX
but
the principles will be the same. You’ll need to bring the interface up
with DHCP to obtain your IP. Some providers require additional stuff -
for
instance, I’m with rogers@home and they give you a special hostname that
needs to be set for dhcp to work. For starters I’d probably just hook it
up
and see if it comes up automatically. The default configuration for a
network card in RTP is DHCP.

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
Heyla all, I’m Stormis, and I was wondering…

I’m just getting started with QNX again, now that I have a
non-proprietary
connection to the internet, and I’ve run into a problem, it seems.

I haven’t the foggiest clue as to how to set up my Ericsson PipeRider
cablemodem (and anything else that is needed) on my box.
I tried reading the manual… I looked up an article in the self help
area…
…and it makes no sense to me - it seems to be written for the more
tech-savvy user.

If anyone is willing to help me, I would be graeful. ^^

the NIC is a CNET PRO200WL PCI Fast Ethernet Adapter, and i’m connected
via
RoadRunner.
If i need more info, please, tell me. > :slight_smile:

SDEdgecrusher


\

Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“I love deadlines. I like the whooshing sound they make as they fly by.”
– Douglas Adams


Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“I love deadlines. I like the whooshing sound they make as they fly by.”
– Douglas Adams

Okay, trying this, It seems that my card is not autodetected by QNX.
I assume this means that i get to play with that techno-mambo from earlier,
then…
mmh, i guess i’ll give it a go. even tho i still think it makes no sense.
o.o;;

SDEdgecrusher

“Kris Eric Warkentin” <kewarken@qnx.com> wrote in message
news:9pf5p5$7l3$1@nntp.qnx.com

Well, it might not be that bad…if your ethernet card works under RTP,
we should be able to get the cable modem up and running.

Try going into the network configuration menu. It’s the little network
icon on the shelf or you can run ‘phlip’ at the command line. You’ll need
to be root. Under the ‘devices’ tab you should have a network card ‘en0’,
assuming that your card has been autodetected. If you set the connection
type to “DHCP”, you may get an IP from your cable modem. If nothing else,
you should see some ‘blinkenlights’ on the modem showing that the network
card is trying to talk to it. If it works, the ‘network’ tab should show
you some information about the IP, etc.

Now I’m still working on the assumption that your ethernet card is working
properly. If it isn’t, you have to solve that problem first. The next
thing
to try if the interface failed to come up in the last step is to enter an
ID.

I don’t know how RoadRunner works but when you get setup for Rogers@home,
they
give you a weird hostname like crd-10382 that you have to set in windows.
It
would be under ‘My Computer’/properties/network identification (or
something
like that) If there is something special that needs to be set, then you
might
want to try putting that into the ID field in the devices tab of phlip.

Give it a try…you might get lucky. > :wink:

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
O_O
okay…
I couldn’t make sense of that at all.
all this typethis, poke that, dhcp left, turn the knob one-half
circle…
;;
I couldn’t make heads or tails of any of it. > :frowning:
-
-; i guess i should just stick to windows for the 'net.
Thanks, anyway.

SDEdgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pcc8e$ds9$> 1@nntp.qnx.com> …

At > http://www.linuxdoc.org/HOWTO/Cable-Modem/index.html > you will find
the
Linux Cable modem HOWTO. This has specific notes for various providers
(including RoadRunner). Now things will be a little different with QNX
but
the principles will be the same. You’ll need to bring the interface up
with DHCP to obtain your IP. Some providers require additional stuff -
for
instance, I’m with rogers@home and they give you a special hostname
that
needs to be set for dhcp to work. For starters I’d probably just hook
it
up
and see if it comes up automatically. The default configuration for a
network card in RTP is DHCP.

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
Heyla all, I’m Stormis, and I was wondering…

I’m just getting started with QNX again, now that I have a
non-proprietary
connection to the internet, and I’ve run into a problem, it seems.

I haven’t the foggiest clue as to how to set up my Ericsson PipeRider
cablemodem (and anything else that is needed) on my box.
I tried reading the manual… I looked up an article in the self
help
area…
…and it makes no sense to me - it seems to be written for the more
tech-savvy user.

If anyone is willing to help me, I would be graeful. ^^

the NIC is a CNET PRO200WL PCI Fast Ethernet Adapter, and i’m
connected
via
RoadRunner.
If i need more info, please, tell me. > :slight_smile:

SDEdgecrusher


\

Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“I love deadlines. I like the whooshing sound they make as they fly
by.”
– Douglas Adams


\

Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“I love deadlines. I like the whooshing sound they make as they fly by.”
– Douglas Adams

Well, if your ethernet card is not autodetected then you have problems beyond
the scope of those documents. You should probably check our webpage to see
if that nic (CNET PRO200WL PCI Fast Ethernet Adapter?) is supported. Perhaps
some of our network driver guys would know. Either way, the first thing to
do is to get the nic running since without it, you can’t talk to the cable
modem.

Since NICs are so cheap, I would say that rather than fighting with it, just
run out and drop a couple bucks for a supported NIC. Then you’ll be cooking.

cheers,

Kris

Stormis Edgecrusher <shiny.blue@stormis.org> wrote:

Okay, trying this, It seems that my card is not autodetected by QNX.
I assume this means that i get to play with that techno-mambo from earlier,
then…
mmh, i guess i’ll give it a go. even tho i still think it makes no sense.
o.o;;

SDEdgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pf5p5$7l3$> 1@nntp.qnx.com> …
Well, it might not be that bad…if your ethernet card works under RTP,
we should be able to get the cable modem up and running.

Try going into the network configuration menu. It’s the little network
icon on the shelf or you can run ‘phlip’ at the command line. You’ll need
to be root. Under the ‘devices’ tab you should have a network card ‘en0’,
assuming that your card has been autodetected. If you set the connection
type to “DHCP”, you may get an IP from your cable modem. If nothing else,
you should see some ‘blinkenlights’ on the modem showing that the network
card is trying to talk to it. If it works, the ‘network’ tab should show
you some information about the IP, etc.

Now I’m still working on the assumption that your ethernet card is working
properly. If it isn’t, you have to solve that problem first. The next
thing
to try if the interface failed to come up in the last step is to enter an
ID.

I don’t know how RoadRunner works but when you get setup for Rogers@home,
they
give you a weird hostname like crd-10382 that you have to set in windows.
It
would be under ‘My Computer’/properties/network identification (or
something
like that) If there is something special that needs to be set, then you
might
want to try putting that into the ID field in the devices tab of phlip.

Give it a try…you might get lucky. > :wink:

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
O_O
okay…
I couldn’t make sense of that at all.
all this typethis, poke that, dhcp left, turn the knob one-half
circle…
;;
I couldn’t make heads or tails of any of it. > :frowning:
-
-; i guess i should just stick to windows for the 'net.
Thanks, anyway.

SDEdgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pcc8e$ds9$> 1@nntp.qnx.com> …

At > http://www.linuxdoc.org/HOWTO/Cable-Modem/index.html > you will find
the
Linux Cable modem HOWTO. This has specific notes for various providers
(including RoadRunner). Now things will be a little different with QNX
but
the principles will be the same. You’ll need to bring the interface up
with DHCP to obtain your IP. Some providers require additional stuff -
for
instance, I’m with rogers@home and they give you a special hostname
that
needs to be set for dhcp to work. For starters I’d probably just hook
it
up
and see if it comes up automatically. The default configuration for a
network card in RTP is DHCP.

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
Heyla all, I’m Stormis, and I was wondering…

I’m just getting started with QNX again, now that I have a
non-proprietary
connection to the internet, and I’ve run into a problem, it seems.

I haven’t the foggiest clue as to how to set up my Ericsson PipeRider
cablemodem (and anything else that is needed) on my box.
I tried reading the manual… I looked up an article in the self
help
area…
…and it makes no sense to me - it seems to be written for the more
tech-savvy user.

If anyone is willing to help me, I would be graeful. ^^

the NIC is a CNET PRO200WL PCI Fast Ethernet Adapter, and i’m
connected
via
RoadRunner.
If i need more info, please, tell me. > :slight_smile:

SDEdgecrusher


\

Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“I love deadlines. I like the whooshing sound they make as they fly
by.”
– Douglas Adams


\

Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“I love deadlines. I like the whooshing sound they make as they fly by.”
– Douglas Adams


Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“I love deadlines. I like the whooshing sound they make as they fly by.”
– Douglas Adams

Hmm… I was looking at the supported NIC page and i see mention of this
“Generic Tulip driver” and was wondering, would there be any way to get this
card to work with this driver?

Side Note, may/may not be important:
My install was from the small ISO, rather than the standard super-small
Windows executable.

Thanks!
Stormis D. Edgecrusher

“Kris Eric Warkentin” <kewarken@qnx.com> wrote in message
news:9pkdcr$hf0$1@nntp.qnx.com

Well, if your ethernet card is not autodetected then you have problems
beyond
the scope of those documents. You should probably check our webpage to
see
if that nic (CNET PRO200WL PCI Fast Ethernet Adapter?) is supported.
Perhaps
some of our network driver guys would know. Either way, the first thing
to
do is to get the nic running since without it, you can’t talk to the cable
modem.

Since NICs are so cheap, I would say that rather than fighting with it,
just
run out and drop a couple bucks for a supported NIC. Then you’ll be
cooking.

cheers,

Kris

Stormis Edgecrusher <> shiny.blue@stormis.org> > wrote:
Okay, trying this, It seems that my card is not autodetected by QNX.
I assume this means that i get to play with that techno-mambo from
earlier,
then…
mmh, i guess i’ll give it a go. even tho i still think it makes no
sense.
o.o;;

SDEdgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pf5p5$7l3$> 1@nntp.qnx.com> …
Well, it might not be that bad…if your ethernet card works under
RTP,
we should be able to get the cable modem up and running.

Try going into the network configuration menu. It’s the little network
icon on the shelf or you can run ‘phlip’ at the command line. You’ll
need
to be root. Under the ‘devices’ tab you should have a network card
‘en0’,
assuming that your card has been autodetected. If you set the
connection
type to “DHCP”, you may get an IP from your cable modem. If nothing
else,
you should see some ‘blinkenlights’ on the modem showing that the
network
card is trying to talk to it. If it works, the ‘network’ tab should
show
you some information about the IP, etc.

Now I’m still working on the assumption that your ethernet card is
working
properly. If it isn’t, you have to solve that problem first. The next
thing
to try if the interface failed to come up in the last step is to enter
an
ID.

I don’t know how RoadRunner works but when you get setup for
Rogers@home,
they
give you a weird hostname like crd-10382 that you have to set in
windows.
It
would be under ‘My Computer’/properties/network identification (or
something
like that) If there is something special that needs to be set, then
you
might
want to try putting that into the ID field in the devices tab of phlip.

Give it a try…you might get lucky. > :wink:

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
O_O
okay…
I couldn’t make sense of that at all.
all this typethis, poke that, dhcp left, turn the knob one-half
circle…
;;
I couldn’t make heads or tails of any of it. > :frowning:
-
-; i guess i should just stick to windows for the 'net.
Thanks, anyway.

SDEdgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pcc8e$ds9$> 1@nntp.qnx.com> …

At > http://www.linuxdoc.org/HOWTO/Cable-Modem/index.html > you will
find
the
Linux Cable modem HOWTO. This has specific notes for various
providers
(including RoadRunner). Now things will be a little different with
QNX
but
the principles will be the same. You’ll need to bring the interface
up
with DHCP to obtain your IP. Some providers require additional
stuff -
for
instance, I’m with rogers@home and they give you a special hostname
that
needs to be set for dhcp to work. For starters I’d probably just
hook
it
up
and see if it comes up automatically. The default configuration for
a
network card in RTP is DHCP.

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
Heyla all, I’m Stormis, and I was wondering…

I’m just getting started with QNX again, now that I have a
non-proprietary
connection to the internet, and I’ve run into a problem, it seems.

I haven’t the foggiest clue as to how to set up my Ericsson
PipeRider
cablemodem (and anything else that is needed) on my box.
I tried reading the manual… I looked up an article in the self
help
area…
…and it makes no sense to me - it seems to be written for the
more
tech-savvy user.

If anyone is willing to help me, I would be graeful. ^^

the NIC is a CNET PRO200WL PCI Fast Ethernet Adapter, and i’m
connected
via
RoadRunner.
If i need more info, please, tell me. > :slight_smile:

SDEdgecrusher

You can try to start io-net by hand and see if it works…first make sure that
you’re not running it: pidin | grep io-net.

If you’re not, then try ‘io-net -dtulip -ptcpip’. If that works, then you
should have an en0 entry when you type ‘ifconfig -a’. I’m not sure what the
proper way to manually set this up in your config scripts is though…I
might refer you to the system administrators guide at
http://qdn.qnx.com/support/docs/sysadmin/docs/wip.html.

You may also find the io-net page useful:
http://support.qnx.com/support/docs/neutrino_qrp/utilities/i/io-net.html

Once you get the interface running, then you should be able to start
/usr/sbin/dhcp.client running and it will hopefully get your ip from the
cable modem.

cheers,

Kris

Stormis Edgecrusher <qdn.inn.qnx.com@stormis.org> wrote:

Hmm… I was looking at the supported NIC page and i see mention of this
“Generic Tulip driver” and was wondering, would there be any way to get this
card to work with this driver?

Side Note, may/may not be important:
My install was from the small ISO, rather than the standard super-small
Windows executable.

Thanks!
Stormis D. Edgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pkdcr$hf0$> 1@nntp.qnx.com> …
Well, if your ethernet card is not autodetected then you have problems
beyond
the scope of those documents. You should probably check our webpage to
see
if that nic (CNET PRO200WL PCI Fast Ethernet Adapter?) is supported.
Perhaps
some of our network driver guys would know. Either way, the first thing
to
do is to get the nic running since without it, you can’t talk to the cable
modem.

Since NICs are so cheap, I would say that rather than fighting with it,
just
run out and drop a couple bucks for a supported NIC. Then you’ll be
cooking.

cheers,

Kris

Stormis Edgecrusher <> shiny.blue@stormis.org> > wrote:
Okay, trying this, It seems that my card is not autodetected by QNX.
I assume this means that i get to play with that techno-mambo from
earlier,
then…
mmh, i guess i’ll give it a go. even tho i still think it makes no
sense.
o.o;;

SDEdgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pf5p5$7l3$> 1@nntp.qnx.com> …
Well, it might not be that bad…if your ethernet card works under
RTP,
we should be able to get the cable modem up and running.

Try going into the network configuration menu. It’s the little network
icon on the shelf or you can run ‘phlip’ at the command line. You’ll
need
to be root. Under the ‘devices’ tab you should have a network card
‘en0’,
assuming that your card has been autodetected. If you set the
connection
type to “DHCP”, you may get an IP from your cable modem. If nothing
else,
you should see some ‘blinkenlights’ on the modem showing that the
network
card is trying to talk to it. If it works, the ‘network’ tab should
show
you some information about the IP, etc.

Now I’m still working on the assumption that your ethernet card is
working
properly. If it isn’t, you have to solve that problem first. The next
thing
to try if the interface failed to come up in the last step is to enter
an
ID.

I don’t know how RoadRunner works but when you get setup for
Rogers@home,
they
give you a weird hostname like crd-10382 that you have to set in
windows.
It
would be under ‘My Computer’/properties/network identification (or
something
like that) If there is something special that needs to be set, then
you
might
want to try putting that into the ID field in the devices tab of phlip.

Give it a try…you might get lucky. > :wink:

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
O_O
okay…
I couldn’t make sense of that at all.
all this typethis, poke that, dhcp left, turn the knob one-half
circle…
;;
I couldn’t make heads or tails of any of it. > :frowning:
-
-; i guess i should just stick to windows for the 'net.
Thanks, anyway.

SDEdgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pcc8e$ds9$> 1@nntp.qnx.com> …

At > http://www.linuxdoc.org/HOWTO/Cable-Modem/index.html > you will
find
the
Linux Cable modem HOWTO. This has specific notes for various
providers
(including RoadRunner). Now things will be a little different with
QNX
but
the principles will be the same. You’ll need to bring the interface
up
with DHCP to obtain your IP. Some providers require additional
stuff -
for
instance, I’m with rogers@home and they give you a special hostname
that
needs to be set for dhcp to work. For starters I’d probably just
hook
it
up
and see if it comes up automatically. The default configuration for
a
network card in RTP is DHCP.

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
Heyla all, I’m Stormis, and I was wondering…

I’m just getting started with QNX again, now that I have a
non-proprietary
connection to the internet, and I’ve run into a problem, it seems.

I haven’t the foggiest clue as to how to set up my Ericsson
PipeRider
cablemodem (and anything else that is needed) on my box.
I tried reading the manual… I looked up an article in the self
help
area…
…and it makes no sense to me - it seems to be written for the
more
tech-savvy user.

If anyone is willing to help me, I would be graeful. ^^

the NIC is a CNET PRO200WL PCI Fast Ethernet Adapter, and i’m
connected
via
RoadRunner.
If i need more info, please, tell me. > :slight_smile:

SDEdgecrusher


Kris Warkentin
kewarken@qnx.com
(613)591-0836 x9368
“I love deadlines. I like the whooshing sound they make as they fly by.”
– Douglas Adams

Stormis Edgecrusher <qdn.inn.qnx.com@stormis.org> wrote:

Hmm… I was looking at the supported NIC page and i see mention of this
“Generic Tulip driver” and was wondering, would there be any way to get this
card to work with this driver?

Hello,

Can you post an output from ‘pci -vvvv’, so I can check if you support
this card.

Regards,

Marcin


Side Note, may/may not be important:
My install was from the small ISO, rather than the standard super-small
Windows executable.

Thanks!
Stormis D. Edgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pkdcr$hf0$> 1@nntp.qnx.com> …
Well, if your ethernet card is not autodetected then you have problems
beyond
the scope of those documents. You should probably check our webpage to
see
if that nic (CNET PRO200WL PCI Fast Ethernet Adapter?) is supported.
Perhaps
some of our network driver guys would know. Either way, the first thing
to
do is to get the nic running since without it, you can’t talk to the cable
modem.

Since NICs are so cheap, I would say that rather than fighting with it,
just
run out and drop a couple bucks for a supported NIC. Then you’ll be
cooking.

cheers,

Kris

Stormis Edgecrusher <> shiny.blue@stormis.org> > wrote:
Okay, trying this, It seems that my card is not autodetected by QNX.
I assume this means that i get to play with that techno-mambo from
earlier,
then…
mmh, i guess i’ll give it a go. even tho i still think it makes no
sense.
o.o;;

SDEdgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pf5p5$7l3$> 1@nntp.qnx.com> …
Well, it might not be that bad…if your ethernet card works under
RTP,
we should be able to get the cable modem up and running.

Try going into the network configuration menu. It’s the little network
icon on the shelf or you can run ‘phlip’ at the command line. You’ll
need
to be root. Under the ‘devices’ tab you should have a network card
‘en0’,
assuming that your card has been autodetected. If you set the
connection
type to “DHCP”, you may get an IP from your cable modem. If nothing
else,
you should see some ‘blinkenlights’ on the modem showing that the
network
card is trying to talk to it. If it works, the ‘network’ tab should
show
you some information about the IP, etc.

Now I’m still working on the assumption that your ethernet card is
working
properly. If it isn’t, you have to solve that problem first. The next
thing
to try if the interface failed to come up in the last step is to enter
an
ID.

I don’t know how RoadRunner works but when you get setup for
Rogers@home,
they
give you a weird hostname like crd-10382 that you have to set in
windows.
It
would be under ‘My Computer’/properties/network identification (or
something
like that) If there is something special that needs to be set, then
you
might
want to try putting that into the ID field in the devices tab of phlip.

Give it a try…you might get lucky. > :wink:

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
O_O
okay…
I couldn’t make sense of that at all.
all this typethis, poke that, dhcp left, turn the knob one-half
circle…
;;
I couldn’t make heads or tails of any of it. > :frowning:
-
-; i guess i should just stick to windows for the 'net.
Thanks, anyway.

SDEdgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pcc8e$ds9$> 1@nntp.qnx.com> …

At > http://www.linuxdoc.org/HOWTO/Cable-Modem/index.html > you will
find
the
Linux Cable modem HOWTO. This has specific notes for various
providers
(including RoadRunner). Now things will be a little different with
QNX
but
the principles will be the same. You’ll need to bring the interface
up
with DHCP to obtain your IP. Some providers require additional
stuff -
for
instance, I’m with rogers@home and they give you a special hostname
that
needs to be set for dhcp to work. For starters I’d probably just
hook
it
up
and see if it comes up automatically. The default configuration for
a
network card in RTP is DHCP.

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
Heyla all, I’m Stormis, and I was wondering…

I’m just getting started with QNX again, now that I have a
non-proprietary
connection to the internet, and I’ve run into a problem, it seems.

I haven’t the foggiest clue as to how to set up my Ericsson
PipeRider
cablemodem (and anything else that is needed) on my box.
I tried reading the manual… I looked up an article in the self
help
area…
…and it makes no sense to me - it seems to be written for the
more
tech-savvy user.

If anyone is willing to help me, I would be graeful. ^^

the NIC is a CNET PRO200WL PCI Fast Ethernet Adapter, and i’m
connected
via
RoadRunner.
If i need more info, please, tell me. > :slight_smile:

SDEdgecrusher

Sure can:


pci


Class = Network (Ethernet)
Vendor ID = 1282h, Davicom Semiconductor Inc.
Device ID = 9102h, DM9102/A GFast Ethernet Adapter
PCI index = 0h
Class Codes = 020000h
Revision ID = 31h
Bus number = 0
Device number = 3
Function num = 0
Status Reg = 210h
Command Reg = 7h
I/O space access enabled
Memory space access enabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 42h
Cache Line Size= 0h
PCI IO Address = 1000h length 256 enabled
PCI Mem Address = 41000000h 32bit length 256 enabled
Subsystem Vendor ID = 4554h
Subsystem ID = 434eh
Max Lat = 40ns
Min Gnt = 20ns
PCI Int Pin = INT A
Interrupt line = 3
Capabilities Pointer = 50h
Capability ID = 1h
Capabilities = c031h - 0h
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 01 00 31 c0 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00




Tools Mail Account:

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
Hmm… I was looking at the supported NIC page and i see mention of this
“Generic Tulip driver” and was wondering, would there be any way to get
this
card to work with this driver?

Hello,

Can you post an output from ‘pci -vvvv’, so I can check if you support
this card.

Regards,

Marcin


Side Note, may/may not be important:
My install was from the small ISO, rather than the standard super-small
Windows executable.

Thanks!
Stormis D. Edgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pkdcr$hf0$> 1@nntp.qnx.com> …
Well, if your ethernet card is not autodetected then you have problems
beyond
the scope of those documents. You should probably check our webpage to
see
if that nic (CNET PRO200WL PCI Fast Ethernet Adapter?) is supported.
Perhaps
some of our network driver guys would know. Either way, the first
thing
to
do is to get the nic running since without it, you can’t talk to the
cable
modem.

Since NICs are so cheap, I would say that rather than fighting with it,
just
run out and drop a couple bucks for a supported NIC. Then you’ll be
cooking.

cheers,

Kris

Stormis Edgecrusher <> shiny.blue@stormis.org> > wrote:
Okay, trying this, It seems that my card is not autodetected by QNX.
I assume this means that i get to play with that techno-mambo from
earlier,
then…
mmh, i guess i’ll give it a go. even tho i still think it makes no
sense.
o.o;;

SDEdgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pf5p5$7l3$> 1@nntp.qnx.com> …
Well, it might not be that bad…if your ethernet card works under
RTP,
we should be able to get the cable modem up and running.

Try going into the network configuration menu. It’s the little
network
icon on the shelf or you can run ‘phlip’ at the command line.
You’ll
need
to be root. Under the ‘devices’ tab you should have a network card
‘en0’,
assuming that your card has been autodetected. If you set the
connection
type to “DHCP”, you may get an IP from your cable modem. If nothing
else,
you should see some ‘blinkenlights’ on the modem showing that the
network
card is trying to talk to it. If it works, the ‘network’ tab should
show
you some information about the IP, etc.

Now I’m still working on the assumption that your ethernet card is
working
properly. If it isn’t, you have to solve that problem first. The
next
thing
to try if the interface failed to come up in the last step is to
enter
an
ID.

I don’t know how RoadRunner works but when you get setup for
Rogers@home,
they
give you a weird hostname like crd-10382 that you have to set in
windows.
It
would be under ‘My Computer’/properties/network identification (or
something
like that) If there is something special that needs to be set, then
you
might
want to try putting that into the ID field in the devices tab of
phlip.

Give it a try…you might get lucky. > :wink:

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
O_O
okay…
I couldn’t make sense of that at all.
all this typethis, poke that, dhcp left, turn the knob one-half
circle…
;;
I couldn’t make heads or tails of any of it. > :frowning:
-
-; i guess i should just stick to windows for the 'net.
Thanks, anyway.

SDEdgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pcc8e$ds9$> 1@nntp.qnx.com> …

At > http://www.linuxdoc.org/HOWTO/Cable-Modem/index.html > you will
find
the
Linux Cable modem HOWTO. This has specific notes for various
providers
(including RoadRunner). Now things will be a little different
with
QNX
but
the principles will be the same. You’ll need to bring the
interface
up
with DHCP to obtain your IP. Some providers require additional
stuff -
for
instance, I’m with rogers@home and they give you a special
hostname
that
needs to be set for dhcp to work. For starters I’d probably just
hook
it
up
and see if it comes up automatically. The default configuration
for
a
network card in RTP is DHCP.

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
Heyla all, I’m Stormis, and I was wondering…

I’m just getting started with QNX again, now that I have a
non-proprietary
connection to the internet, and I’ve run into a problem, it
seems.

I haven’t the foggiest clue as to how to set up my Ericsson
PipeRider
cablemodem (and anything else that is needed) on my box.
I tried reading the manual… I looked up an article in the
self
help
area…
…and it makes no sense to me - it seems to be written for the
more
tech-savvy user.

If anyone is willing to help me, I would be graeful. ^^

the NIC is a CNET PRO200WL PCI Fast Ethernet Adapter, and i’m
connected
via
RoadRunner.
If i need more info, please, tell me. > :slight_smile:

SDEdgecrusher

Hi,

Sorry but this is not a supported network card.

Regards,

Joe

Stormis Edgecrusher <qdn.inn.qnx.com@stormis.org> wrote:

Sure can:


pci


Class = Network (Ethernet)
Vendor ID = 1282h, Davicom Semiconductor Inc.
Device ID = 9102h, DM9102/A GFast Ethernet Adapter
PCI index = 0h
Class Codes = 020000h
Revision ID = 31h
Bus number = 0
Device number = 3
Function num = 0
Status Reg = 210h
Command Reg = 7h
I/O space access enabled
Memory space access enabled
Bus Master enabled
Special Cycle operations ignored
Memory Write and Invalidate disabled
Palette Snooping disabled
Parity Checking disabled
Data/Address stepping disabled
SERR# driver disabled
Fast back-to-back transactions to different agents disabled
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 42h
Cache Line Size= 0h
PCI IO Address = 1000h length 256 enabled
PCI Mem Address = 41000000h 32bit length 256 enabled
Subsystem Vendor ID = 4554h
Subsystem ID = 434eh
Max Lat = 40ns
Min Gnt = 20ns
PCI Int Pin = INT A
Interrupt line = 3
Capabilities Pointer = 50h
Capability ID = 1h
Capabilities = c031h - 0h
Device Dependent Registers:
0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x50: 01 00 31 c0 00 00 00 00 00 00 00 00 00 00 00 00
0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xF0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00




Tools Mail Account:
Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
Hmm… I was looking at the supported NIC page and i see mention of this
“Generic Tulip driver” and was wondering, would there be any way to get
this
card to work with this driver?

Hello,

Can you post an output from ‘pci -vvvv’, so I can check if you support
this card.

Regards,

Marcin


Side Note, may/may not be important:
My install was from the small ISO, rather than the standard super-small
Windows executable.

Thanks!
Stormis D. Edgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pkdcr$hf0$> 1@nntp.qnx.com> …
Well, if your ethernet card is not autodetected then you have problems
beyond
the scope of those documents. You should probably check our webpage to
see
if that nic (CNET PRO200WL PCI Fast Ethernet Adapter?) is supported.
Perhaps
some of our network driver guys would know. Either way, the first
thing
to
do is to get the nic running since without it, you can’t talk to the
cable
modem.

Since NICs are so cheap, I would say that rather than fighting with it,
just
run out and drop a couple bucks for a supported NIC. Then you’ll be
cooking.

cheers,

Kris

Stormis Edgecrusher <> shiny.blue@stormis.org> > wrote:
Okay, trying this, It seems that my card is not autodetected by QNX.
I assume this means that i get to play with that techno-mambo from
earlier,
then…
mmh, i guess i’ll give it a go. even tho i still think it makes no
sense.
o.o;;

SDEdgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pf5p5$7l3$> 1@nntp.qnx.com> …
Well, it might not be that bad…if your ethernet card works under
RTP,
we should be able to get the cable modem up and running.

Try going into the network configuration menu. It’s the little
network
icon on the shelf or you can run ‘phlip’ at the command line.
You’ll
need
to be root. Under the ‘devices’ tab you should have a network card
‘en0’,
assuming that your card has been autodetected. If you set the
connection
type to “DHCP”, you may get an IP from your cable modem. If nothing
else,
you should see some ‘blinkenlights’ on the modem showing that the
network
card is trying to talk to it. If it works, the ‘network’ tab should
show
you some information about the IP, etc.

Now I’m still working on the assumption that your ethernet card is
working
properly. If it isn’t, you have to solve that problem first. The
next
thing
to try if the interface failed to come up in the last step is to
enter
an
ID.

I don’t know how RoadRunner works but when you get setup for
Rogers@home,
they
give you a weird hostname like crd-10382 that you have to set in
windows.
It
would be under ‘My Computer’/properties/network identification (or
something
like that) If there is something special that needs to be set, then
you
might
want to try putting that into the ID field in the devices tab of
phlip.

Give it a try…you might get lucky. > :wink:

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
O_O
okay…
I couldn’t make sense of that at all.
all this typethis, poke that, dhcp left, turn the knob one-half
circle…
;;
I couldn’t make heads or tails of any of it. > :frowning:
-
-; i guess i should just stick to windows for the 'net.
Thanks, anyway.

SDEdgecrusher

“Kris Eric Warkentin” <> kewarken@qnx.com> > wrote in message
news:9pcc8e$ds9$> 1@nntp.qnx.com> …

At > http://www.linuxdoc.org/HOWTO/Cable-Modem/index.html > you will
find
the
Linux Cable modem HOWTO. This has specific notes for various
providers
(including RoadRunner). Now things will be a little different
with
QNX
but
the principles will be the same. You’ll need to bring the
interface
up
with DHCP to obtain your IP. Some providers require additional
stuff -
for
instance, I’m with rogers@home and they give you a special
hostname
that
needs to be set for dhcp to work. For starters I’d probably just
hook
it
up
and see if it comes up automatically. The default configuration
for
a
network card in RTP is DHCP.

cheers,

Kris

Stormis Edgecrusher <> qdn.inn.qnx.com@stormis.org> > wrote:
Heyla all, I’m Stormis, and I was wondering…

I’m just getting started with QNX again, now that I have a
non-proprietary
connection to the internet, and I’ve run into a problem, it
seems.

I haven’t the foggiest clue as to how to set up my Ericsson
PipeRider
cablemodem (and anything else that is needed) on my box.
I tried reading the manual… I looked up an article in the
self
help
area…
…and it makes no sense to me - it seems to be written for the
more
tech-savvy user.

If anyone is willing to help me, I would be graeful. ^^

the NIC is a CNET PRO200WL PCI Fast Ethernet Adapter, and i’m
connected
via
RoadRunner.
If i need more info, please, tell me. > :slight_smile:

SDEdgecrusher