TeamForge : Post

Forum Topic - e1000 network driver and Intel QM57 chipset not working: (5 Items)

View: as

Gunnar Piel

06/01/2011 8:42 AM

post86315

e1000 network driver and Intel QM57 chipset not working

Hi

I run QNX6.5 on a HP 8540w notebook. It got an Intel core i7 and the QM57 chipset.
I use startup-apic and pci-bios-v2 in my image. As for a network controller the notebook offers an Intel 82577LM Gigabit
 Network Connection. 

I run:

io-pkt-v4-hc -de1000 name=pn &
if_up -p pn0
ifconfig pn0 inet alias 192.168.102.11 up

but it is not possible to establish any kind of link to the notebook. I try to ping from the outside or connect with the
 QNX IDE.

BUT if I run:

io-pkt-v4-hc -de1000 name=pn &
if_up -p pn0
ifconfig pn0 inet alias 192.168.102.11 up
ping 192.168.102.1

then I am able to get a response to my pings from within and without. And the QNX IDE connects to the qconn. If I slay 
the internal ping process every connection breaks down right away.

Any ideas?
Regards
Gunnar

Hugh Brown(deleted)

06/01/2011 8:45 AM

post86316

Re: e1000 network driver and Intel QM57 chipset not working

Please can you post the output from pci v¹ and nicinfo¹.


On 11-06-01 8:42 AM, "Gunnar Piel" <community-noreply@qnx.com> wrote:

> Hi
> 
> I run QNX6.5 on a HP 8540w notebook. It got an Intel core i7 and the QM57
> chipset.
> I use startup-apic and pci-bios-v2 in my image. As for a network controller
> the notebook offers an Intel 82577LM Gigabit Network Connection.
> 
> I run:
> 
> io-pkt-v4-hc -de1000 name=pn &
> if_up -p pn0
> ifconfig pn0 inet alias 192.168.102.11 up
> 
> but it is not possible to establish any kind of link to the notebook. I try to
> ping from the outside or connect with the QNX IDE.
> 
> BUT if I run:
> 
> io-pkt-v4-hc -de1000 name=pn &
> if_up -p pn0
> ifconfig pn0 inet alias 192.168.102.11 up
> ping 192.168.102.1
> 
> then I am able to get a response to my pings from within and without. And the
> QNX IDE connects to the qconn. If I slay the internal ping process every
> connection breaks down right away.
> 
> Any ideas?
> Regards
> Gunnar
> 
> 
> 
> 
> _______________________________________________
> 
> Networking Drivers
> http://community.qnx.com/sf/go/post86315
> 
> 

-- 
Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd.        (613) 591-3579           (fax)
175 Terence Matthews Cres.       email:  hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8

Gunnar Piel

06/01/2011 8:59 AM

post86318

Re: e1000 network driver and Intel QM57 chipset not working

I included the logs.
I already run this patch: patch-650-2338-RS3775_x86-650-updates.tar
http://community.qnx.com/sf/frs/do/downloadFile/projects.bsp/frs.x86_update_1_for_sdp_6_5_0.x86_update_1_for_sdp_6_5_0/
frs34861?dl=1

Attachment:

pci-v_nicinfo.log 21.59 KB

Hugh Brown(deleted)

06/01/2011 9:10 AM

post86322

Re: e1000 network driver and Intel QM57 chipset not working

This doesn¹t look like a driver problem as the nicinfo output shows received
and transmitted packets without any packets being dropped.

Can you try an ifconfig without the alias and see if that works.

On 11-06-01 8:59 AM, "Gunnar Piel" <community-noreply@qnx.com> wrote:

> I included the logs.
> I already run this patch: patch-650-2338-RS3775_x86-650-updates.tar
> http://community.qnx.com/sf/frs/do/downloadFile/projects.bsp/frs.x86_update_1_
> for_sdp_6_5_0.x86_update_1_for_sdp_6_5_0/frs34861?dl=1
> 
> 
> 
> _______________________________________________
> 
> Networking Drivers
> http://community.qnx.com/sf/go/post86318
> 

-- 
Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd.        (613) 591-3579           (fax)
175 Terence Matthews Cres.       email:  hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8

Gunnar Piel

06/01/2011 9:33 AM

post86326

Re: e1000 network driver and Intel QM57 chipset not working

The logs were generated when the internal ping was running. In that case networking is fine. Otherwise I cannot reach 
the device.

Nevertheless I did some other test with ping replaced by a simple sleep. As long as the sleep is halting the scrip 
networking works. So there must be something else that kills the connection. I will now look for that.
Thanks for the support so far.
Cheers 
Gunnar

Return