Hello Siliconbrain,
 
            We haven’t heard any additional updates on the forum.  I will proceed on closing it.  If you requiere any additional help please don’t hesitate to contact us on a new forum.
 
Please feel free to ask.

Best regards,
              
Henry A.

Thanks for sharing the observation. We will wait for your response for the final result.

Thanks,
Dilraj

Hello guys!

Right now I have i5-7400 with ram 2400 MHz summary 16 Gb. And I want upgrade to i5-8400. In Intel Ark we can see i5-8400 computable with ram 2666 MHz. So, if I’ll upgrade to i5-8400, need to upgrade ram for 2666 MHz? or i5-8th gen will work with ram 2400 MHz?

Hello Ray_S,
 
            I am afraid we haven’t heard back from you on this Forum.  I am going to close the chat but if you requiere any additional help, please don’t hesitate on creating a new forum.
 
Best regards,
             
Henry A.

Hi Petar,

Kindly be informed that this forum is only for Moon Island Gateway related questions. For your coffee lake/Xeon E3-1230v6 related questions, please use the following forums  Processors or General Questions  and post your question there.

Unfortunately this thread cannot be transferred.

Regards

CK

Intel Customer Support

Hi WS.Yang,

 Thank you for the confirmation. We will further check on this.

Regards,
Sharon T 

Hi David V,

Thanks for your help.

I will try to ask microsoft for help.

Regards.

Hi all,

I'm currently also dealing with similar/same issues. I am using Windows SDK version 11.0.27.1384 with a SR300 (Creative BlasterX Senz3D Developer Kit, Firmware version 3.21.0.0) on Windows 10.

I have been testing this with different applications by now:

1. The Camera Explorer from realsense samples folder

2. The 3D Scan sample from realsense samples folder

3. The software product I'm currently working on, which is roughly based on the 3DScan sample code and workflow.

Randomly the the apps would stop working / freezing while the camera stream is active. In my code I too traced this back to AquireFrame which will return a STATUS_EXEC_TIMEOUT after running fine for a while (around 2-10 min). Reproducing the issue is difficult as it seems really random. I cannot figure it out...

We have been testing this with various SR300 cameras and on multiple PCs, all running on windows 10. I have already looked into all kind of troubleshooting solutions in this forum including: Windows® 10 Issues with Driver for Intel® RealSense™ Camera SR300

Other threads I followed and solutions I tried:

• Sporadically -  AcquireFrame returns a timeout(SR300)
• acquireFrame make freeze sr300 in R2,R3 SDK
• SR300 freeze on face tracking in Unity3D
• error for R200, Timeout waiting for frames. · Issue #67 · IntelRealSense/librealsense · GitHub

So far I considered following reasons for the issue:

1. SenseManager object not properly released and disposed

2. The camera hardware is faulty

3. The usb 3.0 port cannot maintain a stable power supply or bandwidth for the camera to work properly

4. Some Bug in the SDK

5. Some driver or firmware problem

What I learned from looking into those reasons:

1.a Intel sample apps tend to have the same problem on my setup, my app also can face the issue after rebooting and running it the first time, so I never have to release any resources yet except frames. (I did have a problem calling SenseManager.Close() to hang as well though, so following Intels suggestion (SenseManager.Close() blocking in C# application ) to leave that out and just use SenseManager.Dispose() kind of worked here, not solving the timeout/freeze issue though)

1.b Occasionally rebooting makes the problem go away for a longer time but never entirely.

2. I tried like 3 different cameras of the same model by now, unlikely they are all faulty?

3. I tried every port I could on different PCs. I don't have a powered USB hub at hand though. However the RealSense SDK 2.0 seems to work just fine even running several hours (doesn't provide the 3DScan API though, which I need)

4. The issue seems to appear more often on the 3Dscan sample and in my app, but I also witnessed it on the Camera Explorer and the raw stream samples before. Since SDK 2.0 seems to not yield the issue, Windows SDK bug doesn't seem unlikely, however other users rarely seem to have faced the problem.

5. Updated drivers, DCM, Windows update etc., followed several blogs on how to get the camera to work on windows 10 properly. The drivers appear fine, the camera starts fine, just that it will freeze after a while.

Am I missing anything obvious? coconoeRyu did you figure it out on your side?

intel_corp I attached all the logs I could scrape together running my app and the samples I spoke off hitting the issue.

Would be very thankful for any thoughts, solutions and help on this!

Thanks

If you have only nvidia graphics, then you need to contact nvidia or the manufacturer of your invidia card and provide them with the model number of your nvidia card.

you may or may not have any intel graphics.  To determine this, provide your complete processor model number, and the model number of your motherboard/system/laptop, and your operating system.

Doc

The D415 can be used with the USB 3.0 short cable that comes with the camera in a USB 2.0 port.  It starts in USB2 mode, which limits it to 480x270 resolution only.  I do not have a USB 2.0 version of the cable to test it with to see if that works too though.

Thank you!!! it worked...

Hi, I am using a laptop with wireless-AC 9260 on ubuntu

WiFi manages to connect to my access pointin WPA2 (see EAPOL message success below), but it apparently fails to get an IP address. I have tried with many access points and android hotspot.

Looking at tcpdump traces, it seems that the wifi interface receives a bunch of truncated IP messages in response to the bootp request.

How do I check if I have the right driver version, and right firmware?

All the relevant information is below I think.

Best Regards,

Pierre

pierre@pierre-GF62-7RE:~$ sudo lshw -C network

  *-network                

       description: Wireless interface

       product: Intel Corporation

       vendor: Intel Corporation

       physical id: 0

       bus info: pci@0000:02:00.0

       logical name: wlp2s0

       version: 29

       serial: a0:c5:89:b5:42:30

       width: 64 bits

       clock: 33MHz

       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless

       configuration: broadcast=yes driver=iwlwifi driverversion=4.13.0-37-generic firmware=33.610294.0 latency=0 link=yes multicast=yes wireless=IEEE 802.11

       resources: irq:16 memory:df300000-df303fff

  *-network

       description: Ethernet interface

       product: Killer E2400 Gigabit Ethernet Controller

       vendor: Qualcomm Atheros

       physical id: 0

       bus info: pci@0000:03:00.0

       logical name: enp3s0

       version: 10

       serial: 30:9c:23:14:c6:8b

       size: 100Mbit/s

       capacity: 1Gbit/s

       width: 64 bits

       clock: 33MHz

       capabilities: pm pciexpress msi msix bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation

       configuration: autonegotiation=on broadcast=yes driver=alx duplex=full ip=192.168.1.10 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s

       resources: irq:19 memory:df200000-df23ffff ioport:d000(size=128)

pierre@pierre-GF62-7RE:~$

pierre@pierre-GF62-7RE:~$ ls -al /lib/firmware/iwlwifi-

iwlwifi-1000-5.ucode               iwlwifi-3160-9.ucode               iwlwifi-6050-5.ucode               iwlwifi-7265-17.ucode              iwlwifi-8000C-16.ucode

iwlwifi-100-5.ucode                iwlwifi-3168-21.ucode              iwlwifi-7260-10.ucode              iwlwifi-7265-8.ucode               iwlwifi-8000C-21.ucode

iwlwifi-105-6.ucode                iwlwifi-3168-22.ucode              iwlwifi-7260-12.ucode              iwlwifi-7265-9.ucode               iwlwifi-8000C-27.ucode

iwlwifi-135-6.ucode                iwlwifi-3168-27.ucode              iwlwifi-7260-13.ucode              iwlwifi-7265D-10.ucode             iwlwifi-8000C-31.ucode

iwlwifi-2000-6.ucode               iwlwifi-3168-29.ucode              iwlwifi-7260-16.ucode              iwlwifi-7265D-12.ucode             iwlwifi-8265-21.ucode

iwlwifi-2030-6.ucode               iwlwifi-3945-2.ucode               iwlwifi-7260-17.ucode              iwlwifi-7265D-13.ucode             iwlwifi-8265-22.ucode

iwlwifi-3160-10.ucode              iwlwifi-4965-2.ucode               iwlwifi-7260-7.ucode               iwlwifi-7265D-16.ucode             iwlwifi-8265-27.ucode

iwlwifi-3160-12.ucode              iwlwifi-5000-5.ucode               iwlwifi-7260-8.ucode               iwlwifi-7265D-17.ucode             iwlwifi-8265-31.ucode

iwlwifi-3160-13.ucode              iwlwifi-5150-2.ucode               iwlwifi-7260-9.ucode               iwlwifi-7265D-21.ucode             iwlwifi-9000-pu-b0-jf-b0-33.ucode

iwlwifi-3160-16.ucode              iwlwifi-6000-4.ucode               iwlwifi-7265-10.ucode              iwlwifi-7265D-22.ucode             iwlwifi-9260-th-b0-jf-b0-33.ucode

iwlwifi-3160-17.ucode              iwlwifi-6000g2a-5.ucode            iwlwifi-7265-12.ucode              iwlwifi-7265D-27.ucode            

iwlwifi-3160-7.ucode               iwlwifi-6000g2a-6.ucode            iwlwifi-7265-13.ucode              iwlwifi-7265D-29.ucode            

iwlwifi-3160-8.ucode               iwlwifi-6000g2b-6.ucode            iwlwifi-7265-16.ucode              iwlwifi-8000C-13.ucode 

pierre@pierre-GF62-7RE:~$ iwconfig

enp3s0    no wireless extensions.

lo        no wireless extensions.

wlp2s0    IEEE 802.11  ESSID:"PBV" 

          Mode:Managed  Frequency:5.22 GHz  Access Point: E0:91:F5:F9:FD:AE  

          Bit Rate=30 Mb/s   Tx-Power=22 dBm  

          Retry short limit:7   RTS thr:off   Fragment thr:off

          Power Management:on

          Link Quality=69/70  Signal level=-41 dBm 

          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0

          Tx excessive retries:0  Invalid misc:16   Missed beacon:0

pierre@pierre-GF62-7RE:~$ cat /proc/version

Linux version 4.13.0-37-generic (buildd@lcy01-amd64-026) (gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.2)) #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018

pierre@pierre-GF62-7RE:~$ ifconfig

enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.1.10  netmask 255.255.255.0  broadcast 192.168.1.255

        inet6 fe80::e554:fec3:aee7:3e80  prefixlen 64  scopeid 0x20<link>

        ether 30:9c:23:14:c6:8b  txqueuelen 1000  (Ethernet)

        RX packets 36153  bytes 29619342 (29.6 MB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 30045  bytes 5310107 (5.3 MB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

        device interrupt 19 

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::1  prefixlen 128  scopeid 0x10<host>

        loop  txqueuelen 1000  (Local Loopback)

        RX packets 6144  bytes 557630 (557.6 KB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 6144  bytes 557630 (557.6 KB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp2s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

        ether a0:c5:89:b5:42:30  txqueuelen 1000  (Ethernet)

        RX packets 1424  bytes 198826 (198.8 KB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 1441  bytes 226659 (226.6 KB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

pierre@pierre-GF62-7RE:~$ sudo tcpdump -vvv -i wlp2s0

23:20:46.120549 EAPOL key (3) v2, len 117

23:20:46.120860 EAPOL key (3) v1, len 117

23:20:46.128517 EAPOL key (3) v2, len 151

23:20:46.128681 EAPOL key (3) v1, len 95

23:20:46.164007 IP6 (hlim 1, next-header Options (0) payload length: 36) :: > ff02::16: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6, multicast listener report v2, 1 group record(s) [gaddr ff02::1:ffde:1df6 to_ex { }]

23:20:46.176243 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)

    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from a0:c5:89:b5:42:30 (oui Unknown), length 300, xid 0xcee0c667, Flags [none] (0x0000)

      Client-Ethernet-Address a0:c5:89:b5:42:30 (oui Unknown)

      Vendor-rfc1048 Extensions

        Magic Cookie 0x63825363

        DHCP-Message Option 53, length 1: Discover

        Hostname Option 12, length 15: "pierre-GF62-7RE"

        Parameter-Request Option 55, length 16:

          Subnet-Mask, BR, Time-Zone, Default-Gateway

          Domain-Name, Domain-Name-Server, Option 119, Hostname

          Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route

          NTP, Classless-Static-Route-Microsoft, Static-Route, Option 252

        END Option 255, length 0

        PAD Option 0, length 0, occurs 21

23:20:46.776096 IP6 (hlim 1, next-header Options (0) payload length: 36) :: > ff02::16: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6, multicast listener report v2, 1 group record(s) [gaddr ff02::1:ffde:1df6 to_ex { }]

23:20:47.096014 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 32) :: > ff02::1:ffde:1df6: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has pierre-GF62-7RE

      unknown option (14), length 8 (1):

        0x0000:  8ed9 a698 d136

23:20:47.420171 IP6 truncated-ip6 - 8 bytes missing!(hlim 1, next-header UDP (17) payload length: 32) fe80::cc58:8b56:69f0:3e70.63044 > ff02::1:3.hostmon: UDP, length 24

23:20:47.624912 IP truncated-ip - 8 bytes missing! (tos 0x0, ttl 64, id 12876, offset 0, flags [none], proto UDP (17), length 78)

    192.168.1.11.netbios-ns > 192.168.1.255.netbios-ns:

>>> NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST

TrnID=0xED40

OpCode=0

NmFlags=0x11

Rcode=0

QueryCount=1

AnswerCount=0

AuthorityCount=0

AddressRecCount=0

QuestionRecords:

Name=

WARNING: Short packet. Try increasing the snap length

23:20:48.120269 IP6 (hlim 1, next-header Options (0) payload length: 36) pierre-GF62-7RE > ff02::16: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6, multicast listener report v2, 1 group record(s) [gaddr ff02::1:ffde:1df6 to_ex { }]

23:20:48.121496 IP6 (flowlabel 0x1c1ef, hlim 255, next-header ICMPv6 (58) payload length: 8) pierre-GF62-7RE > ip6-allrouters: [icmp6 sum ok] ICMP6, router solicitation, length 8

23:20:48.132068 IP6 (hlim 1, next-header Options (0) payload length: 56) pierre-GF62-7RE > ff02::16: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6, multicast listener report v2, 2 group record(s) [gaddr ff02::1:3 to_ex { }] [gaddr ff02::fb to_ex { }]

23:20:48.221502 IP6 (flowlabel 0x604e6, hlim 255, next-header UDP (17) payload length: 149) pierre-GF62-7RE.mdns > ff02::fb.mdns: [bad udp cksum 0x7cf5 -> 0x9d3e!] 0 [9q] PTR (QM)? _nfs._tcp.local. PTR (QM)? _ipp._tcp.local. PTR (QM)? _ipps._tcp.local. PTR (QM)? _ftp._tcp.local. PTR (QM)? _webdav._tcp.local. PTR (QM)? _webdavs._tcp.local. PTR (QM)? _sftp-ssh._tcp.local. PTR (QM)? _smb._tcp.local. PTR (QM)? _afpovertcp._tcp.local. (141)

23:20:48.226943 IP6 (flowlabel 0x684f2, hlim 255, next-header UDP (17) payload length: 41) pierre-GF62-7RE.hostmon > ff02::1:3.hostmon: [bad udp cksum 0x7b92 -> 0x8083!] UDP, length 33

23:20:48.241681 IP6 truncated-ip6 - 8 bytes missing!(hlim 1, next-header UDP (17) payload length: 30) fe80::cc58:8b56:69f0:3e70.61412 > ff02::1:3.hostmon: UDP, length 22

23:20:48.241707 IP6 truncated-ip6 - 8 bytes missing!(hlim 255, next-header ICMPv6 (58) payload length: 32) pierre-GF62-7RE > ff02::1:ffde:1df6: ICMP6, neighbor solicitation, length 32, who has pierre-GF62-7RE

23:20:48.316907 IP6 (flowlabel 0x604e6, hlim 255, next-header UDP (17) payload length: 167) pierre-GF62-7RE.mdns > ff02::fb.mdns: [bad udp cksum 0x7d07 -> 0x8096!] 0 [2q] [2n] ANY (QM)? 6.f.d.1.e.d.a.6.9.1.5.8.2.e.f.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? pierre-GF62-7RE.local. ns: pierre-GF62-7RE.local. [2m] AAAA fe80::6fe2:8519:6ade:1df6, 6.f.d.1.e.d.a.6.9.1.5.8.2.e.f.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. [2m] PTR pierre-GF62-7RE.local. (159)

23:20:48.443993 IP6 truncated-ip6 - 8 bytes missing!(hlim 1, next-header UDP (17) payload length: 30) fe80::cc58:8b56:69f0:3e70.61412 > ff02::1:3.hostmon: UDP, length 22

23:20:48.446589 IP truncated-ip - 8 bytes missing! (tos 0x0, ttl 64, id 12894, offset 0, flags [none], proto UDP (17), length 78)

    192.168.1.11.netbios-ns > 192.168.1.255.netbios-ns:

>>> NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST

TrnID=0xED40

OpCode=0

NmFlags=0x11

Rcode=0

QueryCount=1

AnswerCount=0

AuthorityCount=0

AddressRecCount=0

QuestionRecords:

Name=

WARNING: Short packet. Try increasing the snap length

23:20:48.446602 IP truncated-ip - 8 bytes missing! (tos 0x0, ttl 64, id 12895, offset 0, flags [none], proto UDP (17), length 78)

    192.168.1.11.netbios-ns > 192.168.1.255.netbios-ns:

>>> NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST

TrnID=0xED44

OpCode=0

NmFlags=0x11

Rcode=0

QueryCount=1

AnswerCount=0

AuthorityCount=0

AddressRecCount=0

QuestionRecords:

Name=

WARNING: Short packet. Try increasing the snap length

23:20:48.476815 IP6 (flowlabel 0x684f2, hlim 255, next-header UDP (17) payload length: 41) pierre-GF62-7RE.hostmon > ff02::1:3.hostmon: [bad udp cksum 0x7b92 -> 0x8083!] UDP, length 33

23:20:48.567780 IP6 (flowlabel 0x604e6, hlim 255, next-header UDP (17) payload length: 167) pierre-GF62-7RE.mdns > ff02::fb.mdns: [bad udp cksum 0x7d07 -> 0x8096!] 0 [2q] [2n] ANY (QM)? 6.f.d.1.e.d.a.6.9.1.5.8.2.e.f.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? pierre-GF62-7RE.local. ns: pierre-GF62-7RE.local. [2m] AAAA fe80::6fe2:8519:6ade:1df6, 6.f.d.1.e.d.a.6.9.1.5.8.2.e.f.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. [2m] PTR pierre-GF62-7RE.local. (159)

23:20:48.726840 IP6 (flowlabel 0x684f2, hlim 255, next-header UDP (17) payload length: 41) pierre-GF62-7RE.hostmon > ff02::1:3.hostmon: [bad udp cksum 0x7b92 -> 0x8083!] UDP, length 33

23:20:48.818604 IP6 (flowlabel 0x604e6, hlim 255, next-header UDP (17) payload length: 167) pierre-GF62-7RE.mdns > ff02::fb.mdns: [bad udp cksum 0x7d07 -> 0x8096!] 0 [2q] [2n] ANY (QM)? 6.f.d.1.e.d.a.6.9.1.5.8.2.e.f.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. ANY (QM)? pierre-GF62-7RE.local. ns: pierre-GF62-7RE.local. [2m] AAAA fe80::6fe2:8519:6ade:1df6, 6.f.d.1.e.d.a.6.9.1.5.8.2.e.f.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. [2m] PTR pierre-GF62-7RE.local. (159)

23:20:48.824125 IP6 (hlim 1, next-header Options (0) payload length: 76) pierre-GF62-7RE > ff02::16: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6, multicast listener report v2, 3 group record(s) [gaddr ff02::1:3 to_ex { }] [gaddr ff02::fb to_ex { }] [gaddr ff02::1:ffde:1df6 to_ex { }]

23:20:48.856140 IP6 truncated-ip6 - 8 bytes missing!(flowlabel 0x5b91b, hlim 255, next-header UDP (17) payload length: 69) pierre-GF62-7RE.mdns > ff02::fb.mdns: 0*- [0q] 1/0/0 pierre-GF62-7RE.local. (Cache flush) [2m] AAAA[|domain]

23:20:49.019424 IP6 (flowlabel 0x604e6, hlim 255, next-header UDP (17) payload length: 155) pierre-GF62-7RE.mdns > ff02::fb.mdns: [bad udp cksum 0x7cfb -> 0x6515!] 0*- [0q] 2/0/0 6.f.d.1.e.d.a.6.9.1.5.8.2.e.f.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (Cache flush) [2m] PTR pierre-GF62-7RE.local., pierre-GF62-7RE.local. (Cache flush) [2m] AAAA fe80::6fe2:8519:6ade:1df6 (147)

23:20:49.112118 IP6 (hlim 1, next-header Options (0) payload length: 56) pierre-GF62-7RE > ff02::16: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6, multicast listener report v2, 2 group record(s) [gaddr ff02::1:3 to_ex { }] [gaddr ff02::fb to_ex { }]

23:20:49.221207 IP6 (flowlabel 0x604e6, hlim 255, next-header UDP (17) payload length: 149) pierre-GF62-7RE.mdns > ff02::fb.mdns: [bad udp cksum 0x7cf5 -> 0x9d3e!] 0 [9q] PTR (QM)? _nfs._tcp.local. PTR (QM)? _ipp._tcp.local. PTR (QM)? _ipps._tcp.local. PTR (QM)? _ftp._tcp.local. PTR (QM)? _webdav._tcp.local. PTR (QM)? _webdavs._tcp.local. PTR (QM)? _sftp-ssh._tcp.local. PTR (QM)? _smb._tcp.local. PTR (QM)? _afpovertcp._tcp.local. (141)

23:20:49.264576 IP6 truncated-ip6 - 8 bytes missing!(hlim 255, next-header ICMPv6 (58) payload length: 32) pierre-GF62-7RE > ff02::1:ffde:1df6: ICMP6, neighbor solicitation, length 32, who has pierre-GF62-7RE

23:20:49.326221 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)

    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from a0:c5:89:b5:42:30 (oui Unknown), length 300, xid 0xcee0c667, secs 3, Flags [none] (0x0000)

      Client-Ethernet-Address a0:c5:89:b5:42:30 (oui Unknown)

      Vendor-rfc1048 Extensions

        Magic Cookie 0x63825363

        DHCP-Message Option 53, length 1: Discover

        Hostname Option 12, length 15: "pierre-GF62-7RE"

        Parameter-Request Option 55, length 16:

          Subnet-Mask, BR, Time-Zone, Default-Gateway

          Domain-Name, Domain-Name-Server, Option 119, Hostname

          Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route

          NTP, Classless-Static-Route-Microsoft, Static-Route, Option 252

        END Option 255, length 0

        PAD Option 0, length 0, occurs 21

23:20:49.468897 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.1.2 tell gateway, length 38

23:20:49.883144 IP truncated-ip - 8 bytes missing! (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 576)

    gateway.bootps > 192.168.1.2.bootpc: BOOTP/DHCP, Reply, length 548, xid 0xcee0c667, Flags [none] (0x0000)

      Your-IP 192.168.1.2

      Client-Ethernet-Address a0:c5:89:b5:42:30 (oui Unknown)

      Vendor-rfc1048 Extensions

        Magic Cookie 0x63825363

        DHCP-Message Option 53, length 1: Offer

        Server-ID Option 54, length 4: gateway

        Lease-Time Option 51, length 4: 86400

        Subnet-Mask Option 1, length 4: 255.255.255.0

        Default-Gateway Option 3, length 4: gateway

        Domain-Name-Server Option 6, length 4: gateway

        END Option 255, length 0

        PAD Option 0, length 0, occurs 266

23:20:50.082499 IP truncated-ip - 8 bytes missing! (tos 0x0, ttl 64, id 12899, offset 0, flags [none], proto UDP (17), length 78)

    192.168.1.11.netbios-ns > 192.168.1.255.netbios-ns:

>>> NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST

TrnID=0xED44

OpCode=0

NmFlags=0x11

Rcode=0

QueryCount=1

AnswerCount=0

AuthorityCount=0

AddressRecCount=0

QuestionRecords:

Name=

WARNING: Short packet. Try increasing the snap length

23:20:50.166293 IP6 (flowlabel 0x604e6, hlim 255, next-header UDP (17) payload length: 155) pierre-GF62-7RE.mdns > ff02::fb.mdns: [bad udp cksum 0x7cfb -> 0x6515!] 0*- [0q] 2/0/0 6.f.d.1.e.d.a.6.9.1.5.8.2.e.f.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (Cache flush) [2m] PTR pierre-GF62-7RE.local., pierre-GF62-7RE.local. (Cache flush) [2m] AAAA fe80::6fe2:8519:6ade:1df6 (147)

23:20:50.287981 IP6 truncated-ip6 - 8 bytes missing!(hlim 255, next-header ICMPv6 (58) payload length: 32) pierre-GF62-7RE > ff02::1:ffde:1df6: ICMP6, neighbor solicitation, length 32, who has pierre-GF62-7RE

23:20:51.222359 IP6 (flowlabel 0x604e6, hlim 255, next-header UDP (17) payload length: 149) pierre-GF62-7RE.mdns > ff02::fb.mdns: [bad udp cksum 0x7cf5 -> 0x9d3e!] 0 [9q] PTR (QM)? _nfs._tcp.local. PTR (QM)? _ipp._tcp.local. PTR (QM)? _ipps._tcp.local. PTR (QM)? _ftp._tcp.local. PTR (QM)? _webdav._tcp.local. PTR (QM)? _webdavs._tcp.local. PTR (QM)? _sftp-ssh._tcp.local. PTR (QM)? _smb._tcp.local. PTR (QM)? _afpovertcp._tcp.local. (141)

23:20:52.061416 IP6 (flowlabel 0x1c1ef, hlim 255, next-header ICMPv6 (58) payload length: 8) pierre-GF62-7RE > ip6-allrouters: [icmp6 sum ok] ICMP6, router solicitation, length 8

23:20:52.313110 IP6 (flowlabel 0x604e6, hlim 255, next-header UDP (17) payload length: 155) pierre-GF62-7RE.mdns > ff02::fb.mdns: [bad udp cksum 0x7cfb -> 0x6515!] 0*- [0q] 2/0/0 6.f.d.1.e.d.a.6.9.1.5.8.2.e.f.6.0.0.0.0.0.0.0.0.0.0.0.0.0.8.e.f.ip6.arpa. (Cache flush) [2m] PTR pierre-GF62-7RE.local., pierre-GF62-7RE.local. (Cache flush) [2m] AAAA fe80::6fe2:8519:6ade:1df6 (147)

23:20:53.108674 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328)

    0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from a0:c5:89:b5:42:30 (oui Unknown), length 300, xid 0xcee0c667, secs 7, Flags [none] (0x0000)

      Client-Ethernet-Address a0:c5:89:b5:42:30 (oui Unknown)

      Vendor-rfc1048 Extensions

        Magic Cookie 0x63825363

        DHCP-Message Option 53, length 1: Discover

        Hostname Option 12, length 15: "pierre-GF62-7RE"

        Parameter-Request Option 55, length 16:

          Subnet-Mask, BR, Time-Zone, Default-Gateway

          Domain-Name, Domain-Name-Server, Option 119, Hostname

          Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route

          NTP, Classless-Static-Route-Microsoft, Static-Route, Option 252

        END Option 255, length 0

        PAD Option 0, length 0, occurs 21

23:20:53.155331 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.1.2 tell gateway, length 38

23:20:53.660597 IP truncated-ip - 8 bytes missing! (tos 0x0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 576)

    gateway.bootps > 192.168.1.2.bootpc: BOOTP/DHCP, Reply, length 548, xid 0xcee0c667, Flags [none] (0x0000)

      Your-IP 192.168.1.2

      Client-Ethernet-Address a0:c5:89:b5:42:30 (oui Unknown)

      Vendor-rfc1048 Extensions

        Magic Cookie 0x63825363

        DHCP-Message Option 53, length 1: Offer

        Server-ID Option 54, length 4: gateway

        Lease-Time Option 51, length 4: 86400

        Subnet-Mask Option 1, length 4: 255.255.255.0

        Default-Gateway Option 3, length 4: gateway

        Domain-Name-Server Option 6, length 4: gateway

        END Option 255, length 0

        PAD Option 0, length 0, occurs 266

^C

61 packets captured

61 packets received by filter

0 packets dropped by kernel

I'm not a new user.

The Node name mentioned is c009.

I could access the colfax yesterday.

I connected from a Mac and used SSH colfax.

-Could you please provide a picture of the BSOD error code?

-Could you please confirm if you installed the latest Intel® NVMe* driver for the SSD?

yes, i make sure the clean install include windows, amd driver and intel nvme fireware

-Could you please let us know when the SSD is not detected? Are you able to see the SSD after the BSOD?

this only happen in MSI b350m pro gaming board, no detection in bios, install win 10 also cannot find the drive, they released a new bios update on 20/3 haven't tried that yet

BSOD only happens on asus board which can detect the ssd

-Can you please let us know if the Controller Mode in your BIOS is set to AHCI?

Yes, 100%

To update this story:

I tried connecting a USB 3 flashdrive to the internal header USB 2.0/ 3.0 ports and went into the BIOS update menu (F7)

Here in the BIOS i can see the disk on the functioning ports, and it is not showing on the faulty ports.

This basically proves that the header cable itself is damaged as we bypassed the Windows10 OS (and any kind of driver or corrupted OS issues) in this test..

I inspected the cable and the USB connectors and i can't see anything wrong there.

The cables are very fine so it could very well be that 1 of them got damaged somehow..

I will also disconnect the header cables today and inspect the header itself. Maybe after reconnecting the cables everything will work again, who knows?

I ordered a new pair of header cables, but this time the panel mount versions as they seem a little stronger to me..

https://www.amazon.com/Intel-Skull-Canyon-Internal-Header/dp/B072W31XP8/ref=pd_sbs_147_2?_encoding=UTF8&pd_rd_i=B072W31XP8&pd_rd_r=QDY8ZFWYAFKRVD857677&pd_rd_w=xe6E8&pd_rd_wg=foKe4&psc=1&refRID=QDY8ZFWYAFKRVD857677

https://www.amazon.com/Intel-Canyon-Internal-Common-Header/dp/B072W3KRYH/ref=pd_sbs_147_5?_encoding=UTF8&pd_rd_i=B072W3KRYH&pd_rd_r=QDY8ZFWYAFKRVD857677&pd_rd_w=xe6E8&pd_rd_wg=foKe4&psc=1&refRID=QDY8ZFWYAFKRVD857677

I will keep this thread up to date when i get the new cables. 

For now i will work with a USB C hub that gives me 3 USB 3 connections on the rear USB C port.

If that's stable then it's all good!

Thanks for the help!

Jan

Hello Mathias,

Thank you for your patience. 

This question is more specific to RealSense than Aero and can be better addressed by the RealSense community.
However, you can follow the instructions in the following Github to install and run the example code.
I would advice you to install Ubuntu as it has more tools available for development.

Instructions to install librealsense legacy branch on Aero running Ubuntu.

https://github.com/intel-aero/meta-intel-aero/wiki/90-(References)-OS-user-Installation#intel-realsense-sdk

RealSense examples for R200

https://github.com/IntelRealSense/librealsense/tree/legacy/examples

Hope this helps.

Regards,
Octavian

Hopping that my explanation is clear. You have incompatible memory modules. If the memory module consists 16 chips for 4GB size, that means that you have memory with 2Gb SDRAM density. See the Product Specification https://www.intel.com/content/dam/support/us/en/documents/mini-pcs/nuc-kits/NUC6CAYS_NUC6CAYH_TechProdSpec.pdf  , para. 1.4 on page 19 for additional explanation. When you will replace your memory please check Intel Validated Memory list for your NUC: http://compatibleproducts.intel.com/ProductDetails/ExportPeripheralInfo?moduleName=Intel%C2%AE%20NUC&productType=Kits&pr…

Leon

I could instal  pytorch using steps you gave.

But import torch still did not work in jupyter notebook, it worked though on python shell accessed under virtual environment

one more doubt regarding jupyter:

how to save and submit script file prepared using jupyter ?

Hi JorgeG,

Thank you for your interest in the Intel Aero drone.
The GPS sampling frequency is 5 Hz. Regarding the IMU value, I'll get back to you later.

Regards,
Alexandra

please find attachment