Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Network Device not found: (15 Items)
   
Network Device not found  
Hi

I installed qnx momentics on my laptop. I am not able to connect to the wired ethernet network since it does not 
recognize the network device en0 under qnx. 
What's the reason?

The network adapter vendor is Marvell. Would I be able to connect to the internet using a Marvell Network Adapter

Thanks,
Nishchal
RE: Network Device not found  
> laptop ... wired ethernet ... Marvell

Although we have drivers for the wireless
ethernet marvell chipsets, I don't remember
any for the wired marvell.

Can you snapshot and attach the relevant
portion of the "pci -v" output for this
network controller?

If we don't currently have a driver - which
I suspect is the case - once I know the VID/DID 
I can take a peek at the NetBSD source and 
see if there's a driver which could be ported
quickly.

--
aboyd
Re: RE: Network Device not found  
Thanks for replying Andrew

I have attached a screen shot here

Nishchal
Attachment: Image snap.jpg 77.01 KB
RE: RE: Network Device not found  
OK, got:

  VID x11AB (marvell)
  DID x4380 

which I have googled as:

88e8057 Marvell Yukon 88E8057 PCI-E Gigabit Ethernet Controller

I'm pretty sure we currently don't have a driver for this.

--
aboyd
RE: RE: Network Device not found  
> 88e8057 Marvell Yukon 88E8057 PCI-E Gigabit Ethernet Controller

Actually, the NetBSD-ported devnp-msk.so driver supports
Yukon 8050/8052/8053/8055/8056 ... but not 8057   :-(

I just checked the NetBSD head branch, and it's the same
as our snapshot.

I don't think this driver takes DID command line arguments
so one wild shot in the dark is to add this DID to the
driver and recompile it - so it finds it - and see if it
works.  It might.

I don't have hardware to test on, though.

--
aboyd
RE: RE: Network Device not found  
ok, I have manually added DID 0x4380 for
Marvell Yukon 8057 to:

www.PoweredByQNX.com/etc/devnp-msk.so

A long shot, but ... let me know if it 
works so I can go out and buy some lottery 
tickets!

--
aboyd
Re: RE: RE: Network Device not found  
Hi Andrew

Thanks a lot for your inputs. Please excuse my ignorance but what exactly should I do with the file you sent?  Also, you
 said that it is possible to connect wirelessly. I have an Intel Wi-Fi adapter, so is it possible for a wireless 
connection as well.

But yeah, definitely want to get the wired ethernet problem solved first since that is important. So yeah, could you 
guide with the function of the files. 

Thanks Again
Nishchal
RE: RE: RE: Network Device not found  
Ok.  Let's say you download devnp-msk.so to
the directory /tmp.  Start a terminal and get
a root command line, with a "#" prompt.  Then
do the following:

 # chmod 777 /tmp/devnp-msk.so
 # mount -T io-pkt -o verbose /tmp/devnp-msk.so

Note that you could omit the "-o verbose" - that
causes the driver to put diagnostic information 
in the "sloginfo" output.

Another way:

 # slay io-pkt-v4-hc
 # io-pkt-v4-hc -d /tmp/devnp-msk.so verbose

Now, assuming the driver doesn't give you an
error in the _attach routine - called when you
mount it - it's time to call the _init routine,
either by running dhcp.client or statically
assigning an IP address as such:

# ifconfig en0 10.42.110.5

Again, the sloginfo output will be useful, as 
will the nicinfo output, and the "ifconfig -v en0"
output.  Hopefully you should see a link speed/duplex
being detected, then start to see packets being 
received - if that happens, pretty much everything 
should work!

--
aboyd
Re: RE: RE: RE: Network Device not found  
Hi

I tried the mount command and the other way using the slay command. For the mount command, it gives me an error saying 
 "can't mount / (type io-pkt)
Possible reason : Can't access shared library"

and for the slay command, it says "Can't find process 'io-pkt-v4-hc'"

Should I try to copy the file to some other directory?

Thanks,
Nishchal
RE: RE: RE: RE: Network Device not found  
> Can't find process io-pkt-v4-hc

From the command line, what is the output of

  # uname -a

--
aboyd
Re: RE: RE: RE: RE: Network Device not found  
Hi Andrew

When I type uname -a at the comman line, it gives me the following output:

QNX localhost 6.3.2 2006/03/16-14:19:50EST x86pc x86

Thanks,
Nishchal
RE: RE: RE: RE: RE: Network Device not found  
> 6.3.2

As I suspected.  Sigh.  The experimental driver
that you have is a "devnp" driver which means
that it is for QNX 6.4 - io-pkt - not QNX 6.3
and earlier, which uses io-net and "devn" drivers.

AFAIK we don't have any "devn" io-net network 
drivers for the marvell yukon for 6.3 - sorry!

--
aboyd
Re: RE: RE: RE: RE: RE: Network Device not found  
Is there no way this problem can be resolved? If I get an external network adapter?

Or if I install QNX 6.4, will I be able to resolve the issue?

Regards,
Nishchal
RE: RE: RE: RE: RE: RE: Network Device not found  
> if I install QNX 6.4, will I be able to resolve the issue?

The experimental driver was exactly that - we do not have
any docs from Marvell for that adapter, it was merely added
to the DID list and hoped for the best.  Installing 6.4 will
NOT guarantee that the experimental driver will work - rather
I assumed that you were already running 6.4 and thus this
was a no-cost alternative for you.

For 6.3 I might suggest an ASIX usb ethernet adapter - see
devn-asix.so ... I know many people have had success with
it in the past.

--
aboyd
Re: RE: RE: RE: RE: RE: RE: Network Device not found  
Okay, will look into that. Thanks a lot for you help Andrew!