foundry27 : Post

Forum Topic - QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32: Page 1 of 2 (29 Items)

View: as

Scott Poulin(deleted)

12/29/2017 4:26 PM

post118298

QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

I made a bsp with the alpha qnx7 momentics and was able to get a x86_64 bsp to work with a Dell R720 and all it's pci 
and integrated interfaces. 
I tried to create a x86_32 bsp and the nic isn't compatible.  Am I doing something wrong? I made sure to set the 
stacksize to 4096 and made sure all of the 32bit architecture parameters were accounted for.

When I would run a ifconfig the bottom of the output would state ifconfig: link_status: ioctl: Bad Address
Along with nicinfo -v would output bad address next to dvcr_config and another attribute.

I am assuming that the x86_32 bit version of the e1000 driver is not compatible with the NIC. 
Am I wrong in this assumption?

Thanks! Also if there is any additional information out there for building bsps I would appreciate the help. I have 
pulled all the documentation from qnx and foundry but any additional info would be nice!

Hugh Brown

01/02/2018 9:04 AM

post118301

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Please try the attached 32-bit driver.

Thanks, Hugh.

On 2017-12-29, 4:05 PM, "Scott Poulin" <community-noreply@qnx.com> wrote:

    I made a bsp with the alpha qnx7 momentics and was able to get a x86_64 bsp to work with a Dell R720 and all it's 
pci and integrated interfaces. 
    I tried to create a x86_32 bsp and the nic isn't compatible.  Am I doing something wrong? I made sure to set the 
stacksize to 4096 and made sure all of the 32bit architecture parameters were accounted for.
    
    When I would run a ifconfig the bottom of the output would state ifconfig: link_status: ioctl: Bad Address
    Along with nicinfo -v would output bad address next to dvcr_config and another attribute.
    
    I am assuming that the x86_32 bit version of the e1000 driver is not compatible with the NIC. 
    Am I wrong in this assumption?
    
    Thanks! Also if there is any additional information out there for building bsps I would appreciate the help. I have 
pulled all the documentation from qnx and foundry but any additional info would be nice!
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post118298
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

Attachment:

devnp-e1000.so.32.gz 212.69 KB

Scott Poulin(deleted)

01/03/2018 11:02 AM

post118309

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

So I tried using the driver you supplied but the result was the same. I am posting a picture of what I am seeing.

Attachment:

Capture2.PNG 55.91 KB

Hugh Brown

01/03/2018 11:45 AM

post118310

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

I have installed the 32-bit X86 BSP on my development machine, created a boot image and booted my PC with this image. 
Both e1000 interfaces on my PC work fine with the 32-bit driver. Are you sure that you are not mixing 32 and 64-bit 
executables?

On 2018-01-03, 10:41 AM, "Scott Poulin" <community-noreply@qnx.com> wrote:

    So I tried using the driver you supplied but the result was the same. I am posting a picture of what I am seeing.
    
    
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post118309
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

Scott Poulin(deleted)

01/03/2018 11:55 AM

post118311

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

I am fairly certain I am using only 32 bit executables. 
Do you mind sharing your build file for me to compare. To make sure that I am not accidentally forgetting something?

I appreciate it!

Scott Poulin(deleted)

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Scott Poulin(deleted)

01/03/2018 11:58 AM

post118312

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Also I am using the io-pkt-v4-hc driver instead of the io-pkt-v6-hc driver

Hugh Brown

01/03/2018 12:04 PM

post118314

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

You should only use the io-pkt-v6-hc driver with SDP7.

On 2018-01-03, 11:37 AM, "Scott Poulin" <community-noreply@qnx.com> wrote:

    Also I am using the io-pkt-v4-hc driver instead of the io-pkt-v6-hc driver
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post118312
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

Scott Poulin(deleted)

01/03/2018 12:19 PM

post118315

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

I guess what is the difference between io-pkt-v4-hc and io-pkt-v6-hc?
In the alpha of SDP7 I was able to use io-pkt-v4-hc in the x86_64 bit version?

Dean Denter

RE: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Dean Denter

01/03/2018 12:56 PM

post118317

RE: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Both io-pkt-v4-hc and io-pkt-v6-hc are supported on both 32bit & 64bit targets in SDP7.

You should not use io-pkt-v4 in SDP7.

For your e1000 issue, check the pci-server configuration --  there may be a base address missing from your build file.  
 'pci -v' output may help troubleshoot this.

regards,
Dean.

________________________________________
From: Scott Poulin [community-noreply@qnx.com]
Sent: Wednesday, January 03, 2018 12:19 PM
To: drivers-networking
Subject: Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

I guess what is the difference between io-pkt-v4-hc and io-pkt-v6-hc?
In the alpha of SDP7 I was able to use io-pkt-v4-hc in the x86_64 bit version?



_______________________________________________

Networking Drivers
http://community.qnx.com/sf/go/post118315
To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

Scott Poulin(deleted)

01/03/2018 1:34 PM

post118319

Re: RE: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Hello Dean,

Can you elaborate what you mean the base address is missing in my build file?

Thanks,
Scott

Dean Denter

01/03/2018 1:58 PM

post118322

RE: RE: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

should be "device id" not "base address" -- the output from "pci" or "pci -v" should indicate the device ID of your NIC,
 I usually see them defined in the "net-start.sh" script in the build file.

________________________________________
From: Scott Poulin [community-noreply@qnx.com]
Sent: Wednesday, January 03, 2018 1:34 PM
To: drivers-networking
Subject: Re: RE: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Hello Dean,

Can you elaborate what you mean the base address is missing in my build file?

Thanks,
Scott

_______________________________________________

Networking Drivers
http://community.qnx.com/sf/go/post118319
To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

Hugh Brown

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Hugh Brown

01/03/2018 1:11 PM

post118318

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

io-pkt-v4-hc was dropped from the official release of SDP7, so only io-pkt-v6-hc is supported.


On 2018-01-03, 11:58 AM, "Scott Poulin" <community-noreply@qnx.com> wrote:

    I guess what is the difference between io-pkt-v4-hc and io-pkt-v6-hc?
    In the alpha of SDP7 I was able to use io-pkt-v4-hc in the x86_64 bit version?
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post118315
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

Hugh Brown

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Hugh Brown

01/03/2018 12:04 PM

post118313

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

I have attached my build file.

On 2018-01-03, 11:34 AM, "Scott Poulin" <community-noreply@qnx.com> wrote:

    I am fairly certain I am using only 32 bit executables. 
    Do you mind sharing your build file for me to compare. To make sure that I am not accidentally forgetting something?

    
    I appreciate it!
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post118311
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

Attachment:

x86-generic.build 22.16 KB

Scott Poulin(deleted)

01/03/2018 1:37 PM

post118320

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Hello Hugh,

So I took your build image and created an image from it and included the 32 bit e1000 driver as well.
I get the same results as before. Is there something wrong with the BSP that I downloaded from QNX.

Also there shouldn't be any issues if I am running the image as a virtual image via a DRAC console correct? It treats it
 as if it were a disk image on a harddrive so i figure there shouldn't be any issues from this.

Thanks,
Scott

Hugh Brown

01/03/2018 1:40 PM

post118321

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

This sounds as though there could be an incompatibility issue with your virtual machine. I ran on a native PC. The BSP 
that you downloaded from QNX should be OK, but to be on the safe side, you should be running the official release of 
SDP7.

Hugh.

On 2018-01-03, 1:16 PM, "Scott Poulin" <community-noreply@qnx.com> wrote:

    Hello Hugh,
    
    So I took your build image and created an image from it and included the 32 bit e1000 driver as well.
    I get the same results as before. Is there something wrong with the BSP that I downloaded from QNX.
    
    Also there shouldn't be any issues if I am running the image as a virtual image via a DRAC console correct? It 
treats it as if it were a disk image on a harddrive so i figure there shouldn't be any issues from this.
    
    Thanks,
    Scott
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post118320
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

Scott Poulin(deleted)

01/03/2018 3:03 PM

post118323

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

So I went and wrote the image to a harddrive and booted from the harddrive. I achieved the same results as before. I 
checked the pci-tool and it shows the nic is there. For some reason, there is still a compatibility issue with the 
integrated nic x540/i350 

I ran the ixgbe for the x540 and e1000 for i350. 
I even used the did and vid when starting the driver.

Hugh Brown

01/03/2018 3:05 PM

post118324

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Does the problem occur with both the x540 and i350? If so, then this isn’t a driver problem. Have you updated to the 
official SDP7 release?


On 2018-01-03, 2:42 PM, "Scott Poulin" <community-noreply@qnx.com> wrote:

    So I went and wrote the image to a harddrive and booted from the harddrive. I achieved the same results as before. I
 checked the pci-tool and it shows the nic is there. For some reason, there is still a compatibility issue with the 
integrated nic x540/i350 
    
    I ran the ixgbe for the x540 and e1000 for i350. 
    I even used the did and vid when starting the driver.
    
    
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post118323
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

Scott Poulin(deleted)

01/03/2018 3:17 PM

post118325

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

It occurs for both the x540 and i350 only on 32bit. I have not tried the x540 for 64bit, but I know the i350 works for 
the 64bit using the e1000 driver and io-pkt-v4-hc. 

I believe the SDP I am using is the official release of QNX7.

Hugh Brown

01/03/2018 3:21 PM

post118326

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

I have attached my boot image to this email. Please can you try it?

Thanks, Hugh.

On 2018-01-03, 2:56 PM, "Scott Poulin" <community-noreply@qnx.com> wrote:

    It occurs for both the x540 and i350 only on 32bit. I have not tried the x540 for 64bit, but I know the i350 works 
for the 64bit using the e1000 driver and io-pkt-v4-hc. 
    
    I believe the SDP I am using is the official release of QNX7. 
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post118325
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

Attachment:

x86-generic.bin.gz 7.95 MB

Scott Poulin(deleted)

01/03/2018 5:07 PM

post118327

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Hugh,

I built an image from the binary you sent me and I am getting the same result. When the image boots it actually doesn't 
start the network driver. When I start the network driver it gives me the same result as before. I did notice something 
odd and I think it may be something with pci-server or when I create the image.(Not sure yet)
But when I go to cat the pcidatabase.com-tab_delimited.txt file it throws a bad address.

Attached is the cat of the pcidatabase.com-tab_delimited.txt file.

Thanks,
Scott

Attachment:

Capture3.PNG 112.21 KB

Hugh Brown

01/04/2018 8:27 AM

post118331

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Scott,

Do all commands on your system fail under 32-bit, or only some of them? Do you see any errors on the screen while 
booting the system? Does USB work?
Please can you send me the output from “pidin in” and “pidin arg”. Can you run “ls –lR /” to see if the file 
system recurses?
I’m trying to figure out why 32-bit isn’t working, but 64-bit is.

Thanks, Hugh.

On 2018-01-03, 4:46 PM, "Scott Poulin" <community-noreply@qnx.com> wrote:

    Hugh,
    
    I built an image from the binary you sent me and I am getting the same result. When the image boots it actually 
doesn't start the network driver. When I start the network driver it gives me the same result as before. I did notice 
something odd and I think it may be something with pci-server or when I create the image.(Not sure yet)
    But when I go to cat the pcidatabase.com-tab_delimited.txt file it throws a bad address.
    
    Attached is the cat of the pcidatabase.com-tab_delimited.txt file.
    
    Thanks,
    Scott
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post118327
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

Armin Steinhoff

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Armin Steinhoff

01/04/2018 9:57 AM

post118332

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

I wonder why there are no compatibility libs available for running 32bit
drivers within a 64bit environment and vs.
Please explain ..

Armin

Hugh Brown schrieb:
>  Scott,
>
> Do all commands on your system fail under 32-bit, or only some of them? Do you see any errors on the screen while 
booting the system? Does USB work?
> Please can you send me the output from âpidin inâ and âpidin argâ. Can you run âls âlR /
â to see if the file system recurses?
> Iâm trying to figure out why 32-bit isnât working, but 64-bit is.
>
> Thanks, Hugh.
>
> On 2018-01-03, 4:46 PM, "Scott Poulin" <community-noreply@qnx.com> wrote:
>
>     Hugh,
>     
>     I built an image from the binary you sent me and I am getting the same result. When the image boots it actually 
doesn't start the network driver. When I start the network driver it gives me the same result as before. I did notice 
something odd and I think it may be something with pci-server or when I create the image.(Not sure yet)
>     But when I go to cat the pcidatabase.com-tab_delimited.txt file it throws a bad address.
>     
>     Attached is the cat of the pcidatabase.com-tab_delimited.txt file.
>     
>     Thanks,
>     Scott
>     
>     
>     
>     _______________________________________________
>     
>     Networking Drivers
>     http://community.qnx.com/sf/go/post118327
>     To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com
>     
>
>
>
>
>
> _______________________________________________
>
> Networking Drivers
> http://community.qnx.com/sf/go/post118331
> To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

Scott Poulin(deleted)

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Scott Poulin(deleted)

01/04/2018 10:14 AM

post118333

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Hugh,

When it loads I don't see any errors. Everything works as it should. I am able to run a pidin in, pidin arg, and ls -lR 
without any errors.

The only error I see is when I run the ifconfig and nicinfo -v pertaining to the bad address of the nics.

The first image is the pidin in 
second image is pidin arg

Attachment:

Capture5.PNG 116.47 KB

Capture4.PNG 213.18 KB

Hugh Brown

01/04/2018 10:38 AM

post118334

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Scott,

Are you able to insert a USB stick into the machine and mount it? Please let me know, as I would like to capture more 
information, rather than screen shots.

Thanks, Hugh.

On 2018-01-04, 9:53 AM, "Scott Poulin" <community-noreply@qnx.com> wrote:

    Hugh,
    
    When it loads I don't see any errors. Everything works as it should. I am able to run a pidin in, pidin arg, and ls 
-lR without any errors.
    
    The only error I see is when I run the ifconfig and nicinfo -v pertaining to the bad address of the nics.
    
    The first image is the pidin in 
    second image is pidin arg
    
    
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post118333
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com

Scott Poulin(deleted)

01/05/2018 2:57 PM

post118337

Re: QNX7 devnp-e1000.so works for Intel Integrated I350 NIC for x86_64 but not x86_32

Hey Hugh, it appears that I am able to mount a usb drive and there doesn't appear to be issues there. I happen to be 
going through the slog2info and found the attached error. It looks like that there is an issue with the pci_cap-0x10 or 
pci_cap-0x11


it states that pci_log says that the pci_cap-0x10 file can't be found for my nics.

I also tested this image an alternate server. It was a different model/make server, but it was able to boot the image 
and use the nic and io-blk drivers. 

So from the image provided, is there an issue with the NIC and driver compatibility?

Thanks,
Scott

Attachment:

Capture6.PNG 95.19 KB

Return

The text you entered is not a valid object ID
More Information
Object IDs begin with an object prefix and end with a number. For example, if you enter
artf2345
the application will jump directly to an artifact with the ID artf2345. Some valid object prefixes are:
artf	for an artifact
doc	for a document
page	for a project page
topc	for a discussion topic
wiki	for a wiki page