Any progress with this yet Allan? I have just bought an NUC DN2820FYK and I am getting the exact same problem - infrared light not responding and no activity reported with 'irw'. Perhaps there's a firmware update to enable the infrared receiver?

Honestly I do not know what exactly is going on with the boards. Maybe J1 would work with a lower voltage DC power supply? Maybe the VIN header is connected into a different pin of the  SWITCHER and so the switcher partially works. Glad you were able to figure that part of it out!

My DN2820FYKH constantly refuses to run WIDi 3.1.29 and 3.0.13, and even to install 4.2.29 at all, reporting the system that is not compatible with WiDi.

However, when I use Windows 8.1 charms bar Devices => Project, my DN2820FYKH successfully connects to my LG TV via WiDi.  Practical problem is, it still doesn't see Belkin Screencast F7D4501. I tried getting some help from Belkin, but in five days they didn't come with any real support.

I use Intel Graphics driver 10.18.10, and PROSet/Wireless 17.1.0. I tried earlierversions but no success in connecting to Belkin either. I still have some hope to manage the Belkin with WiDi software, but as I say the installation reports incompatible platform.

Any way out of here? Thanks

I was just looking at the Intel wireless SW and drivers and noticed that for some reason, since 16.11 and going until even the (development?) 17.13.0.9 version, the 6150 and 6250 seem to be the only variants to not receive an update (still at 15.12.0.6 vs others at 15.13/15.14 ), has it been discontinued support wise, or is it simply that the 6X50 variants new drivers are just not finished/stable/feature-complete enough for a prime-time release as of yet?...

my old Toshiba P755 used to have a 6150 in it, now has a 6250 in it and though definitely better, I suspect an update could definitely help...

I would upgrade to a 7260/7265, but then my WIMAX lights would go to waste!

I have the same problem, did  to solve it?

I recently spend some time figuring out this problem and can confirm that - in my case - the following BIOS setting (I'm running BIOS 0030) fixes the problem of the drives not being detected by the operating system (Windows 7 in my case) upon startup:

Enter the BIOS -> Power -> Enable "Deep S4/S5".

Actually, settings this option solved all USB problems I had with my D54250WYKH NUC. Even the issue with the HDMI-CEC adapter from Pulse Eight, which didn't work after powering on my NUC. It now works fine.

ShadiElwan,

It's your processor so you can choose what you want to do, but if it was me, I would NOT be satisfied with a chip running in 90C-100C on stock settings even with a stock cooler.  When Intel says that the recommended heat for this processor is 74C, that SHOULD (and that's a BIG should) mean that your processor should run at a max of 68C-78C at stock settings with their stock cooler; at least that's what it should mean from a marketing/advertising standpoint.  If you're running 90Cs with stock cooler, that means with aftermarket cooler, you could see into 70C-80C range depending on the cooler you get, meaning if you decide to overclock the processor, you could be back up into the 90C-100C range again!  That brings back the same point of why buy an unlocked processor if you cannot safely overclock it?  Why not pay 40 bucks less and get the 4790 instead?

With the new RMA chip I received, at stock speeds I got temperatures in mid 60Cs with high of 71C with stock cooler and with Corsair H60 I got low to mid 50Cs with high of 62.  Correct me if I'm wrong, but this is the correct temperatures that the processor should run, not 90C-100C on stock settings with stock cooler.

Hope it works out for you one way or the other.

I recently encountered the problem of my USB 3.0 drives not being detected after a cold boot until I restart the system once.

I was able to fix this issue and other USB issues I had with my NUC by enabling the "Deep S4/S5" option in the "Power" menu of the BIOS (version 0030 on a D54250WYKH in my case). It seems like the USB 3.0 controller isn't being initialized properly after a "cold boot" when that option is disabled.

I have the same adapter and had the same issue. You can solve it temporarily by connecting the adapter to a USB 2.0 hub, then connect the hub to the NUC.

Then, update your BIOS to the newest version (0030 as of now) and enable the "Deep S4/S5" option in the "Power" menu of the BIOS. This will solve this issue and other USB 3.0 issues that the NUC has, like USB 3.0 drives not being detected after a cold boot. From then on, you will no longer need the USB 2.0 hub and the adapter will work just fine, connected directly to a USB 3.0 port on the NUC.

As I was having issues with Yocto not seeing my devices on the USB on my Galileo G2, I thought I would try out the Debian build. Thanks!

Took two attempts, the first one downloaded the 1.0... build, Tried again and again it wanted to download the 1.0 file, so went to files and found the 1.2 version and downloaded it.

Used GParted to expand partition...

My first attempt it worked that it saw my devices (note I plugged them in after I booted.  Found and created the USB2AX and created ttyACM0, found FTDI serial cable created ttyUSB0 and I think saw an Edimax USB wifi....  So I rebooted with the USB hub plugged in and it wants to hang (or at least take forever to boot).

Booting 'Debian GNU/Linux, with Linux 3.8.7'

Loading Linux 3.8.7 ...

Loading initial ramdisk ...

error: no suitable mode found.

Booting however

[    2.097449] console [ttyS1] enabled, bootconsole disabled

[    2.114743] brd: module loaded

[    2.127255] loop: module loaded

[    2.131559] lpc_sch_probe BIOS_CNTL 0x00000101

[    2.136076] lpc_sch_probe new BIOS_CNTL 0x00000101

[    2.141052] lpc_sch_probe RCBA @ 0xfed1c000

[    2.151907] rtc_cmos 00:01: RTC can wake from S4

[    2.161095] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0

[    2.167549] rtc0: alarms up to one day, 242 bytes nvram, hpet irqs

[    2.174547] cpuidle: using governor ladder

[    2.178715] cpuidle: using governor menu

[    2.183096] sdhci: Secure Digital Host Controller Interface driver

[    2.189363] sdhci: Copyright(c) Pierre Ossman

[    2.194118] sdhci-pci 0000:00:14.0: SDHCI controller found [8086:08a7] (rev 10)

[    2.250436] mmc0: SDHCI controller on PCI [0000:00:14.0] using ADMA

[    2.257812] sdhci-pltfm: SDHCI platform and OF driver helper

[    2.278936] eSRAM: CTRL 0x047f3f91 block 0x00000000

[    2.283999] eSRAM: pages 128

[    2.310813] intel_qrk_esram_test_probe/Sep  8 2014/03:48:09 complete OK !!

[    2.323045] TCP: cubic registered

[    2.326430] NET: Registered protocol family 17

[    2.334155] Using IPI Shortcut mode

[    2.355354]   Magic number: 6:124:287

[    2.359566] tty tty20: hash matches

[    2.363531] rtc_cmos 00:01: setting system clock to 2014-11-09 16:17:47 UTC (1415549867)

[    2.389072] mmc0: new high speed SDHC card at address b368

[    2.395498] Freeing unused kernel memory: 312k freed

[    2.408145] Write protecting the kernel text: 3424k

[    2.414355] Write protecting the kernel read-only data: 1316k

[    2.420289] NX-protecting the kernel data: 2720k

[    2.427577] mmcblk0: mmc0:b368 USD   3.75 GiB

[    2.460557]  mmcblk0: p1 p2

Loading, please wait...

[    2.762168] udevd[43]: starting version 175

[    2.831173] tsc: Refined TSC clocksource calibration: 399.076 MHz

[    2.837511] Switching to clocksource tsc

[    4.318323] ACPI: bus type usb registered

[    4.351500] usbcore: registered new interface driver usbfs

[    4.358032] usbcore: registered new interface driver hub

[    4.471413] usbcore: registered new device driver usb

[    4.700637] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

[    4.852948] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver

[    4.859789] ohci_hcd 0000:00:14.4: OHCI Host Controller

[    5.037980] ohci_hcd 0000:00:14.4: new USB bus registered, assigned bus number 1

[    5.087768] stmmac: Unknown symbol intel_cln_plat_get_mac (err 0)

[    5.145501] ohci_hcd 0000:00:14.4: irq 16, io mem 0x9000c000

[    5.241808] stmmac: Unknown symbol intel_cln_plat_get_id (err 0)

[    5.296447] stmmac: Unknown symbol intel_cln_plat_get_mac (err 0)

[    5.338114] hub 1-0:1.0: USB hub found

[    5.377988] stmmac: Unknown symbol intel_cln_plat_get_id (err 0)

[    5.468897] hub 1-0:1.0: 2 ports detected

[    5.870438] usb 1-1: new full-speed USB device number 2 using ohci_hcd

[    5.878946] ohci_hcd 0000:00:14.4: bad entry  bc92080

It first appears to want to hang here

udevadm settle - timeout of 120 seconds reached, the event queue contains:

  /sys/devices/pci0000:00/0000:00:14.4/usb1 (812)

  /sys/devices/pci0000:00/0000:00:14.4/usb1/1-0:1.0 (813)

udevadm settle - timeout of 120 seconds reached, the event queue contains:

  /sys/devices/pci0000:00/0000:00:14.4/usb1 (812)

  /sys/devices/pci0000:00/0000:00:14.4/usb1/1-0:1.0 (813)

Begin: Loading essential drivers ... done.

Begin: Running /scripts/init-premount ... done.

Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.

udevadm settle - timeout of 10 seconds reached, the event queue contains:

  /sys/devices/pci0000:00/0000:00:14.4/usb1 (812)

  /sys/devices/pci0000:00/0000:00:14.4/usb1/1-0:1.0 (813)

Begin: Running /scripts/local-premount ... done.

[  255.998474] kjournald starting.  Commit interval 5 seconds

[  256.005025] EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode

Begin: Running /scripts/local-bottom ... done.

done.

Begin: Running /scripts/init-bottom ... done.

INIT: version 2.88 booting

[info] Using makefile-style concurrent boot in runlevel S.

mount: /dev not mounted or bad option

[ ok ] Activating swap...done.

[  321.366882] EXT3-fs (mmcblk0p2): warning: mounting unchecked fs, running e2fsck is recommended

[  321.400581] EXT3-fs (mmcblk0p2): using internal journal

[  323.033197] g_serial: Vendor 0x0525 Product 0xa4a7

[  323.038474] g_serial gadget: Gadget Serial v2.4

[  323.081912] g_serial gadget: g_serial ready

[info] Loading kernel module pch_udc.

[info] Loading kernel module g_serial.

[ ok ] Cleaning up temporary files... /tmp.

[ ok ] Activating lvm and md swap...done.

[....] Checking file systems...fsck from util-linux 2.20.1

done.

[ ok ] Mounting local filesystems...done.

[ ok ] Activating swapfile swap...done.

[ ok ] Cleaning up temporary files....

[ ok ] Setting kernel variables ...done.

[....] Configuring network interfaces...[  339.944132] NET: Registered protocol family 10

Internet Systems Consortium DHCP Client 4.2.2

Copyright 2004-2011 Internet Systems Consortium.

All rights reserved.

For info, please visit https://www.isc.org/software/dhcp/

Cannot find device "eth0"

Bind socket to interface: No such device

Failed to bring up eth0.

done.

[ ok ] Cleaning up temporary files....

INIT: Entering runlevel: 2

[info] Using makefile-style concurrent boot in runlevel 2.

[ ok ] Starting enhanced syslogd: rsyslogd.

[ ok ] Starting periodic command scheduler: cron.

[ ok ] Starting OpenBSD Secure Shell server: sshd.

It is now maybe 10 minutes and still no login prompt:

Will reboot now, with no USB devices plugged in...

I get the login prompt, probably arount time 54.60 seconds.

But now when I plug in lets say the FTDI device I only get

[  115.750378] usb 1-1: new full-speed USB device number 2 using ohci_hcd

[  115.758453] ohci_hcd 0000:00:14.4: bad entry  e6fc080

Note: this is without plugging in hub, if I unplug it and for example plug in hub, I see no new messages show up with dmesg | tail

Also note: I am getting that error about Ramdisk on every boot, not sure if it is an issue or not.

Suggestions?

Yes, it's the same kernel. It's built using bitbake in the Yocto environment, and then copied to the Debian image or system.

So if it's a kernel driver that's missing, you'll need to build the kernel with the needed drivers.

If it's a missing library issue, you should be able to apt-get. Failing that, compile from source.

Rgds,

Dave.

u-boot on Edison expects vmlinuz (not vmlinux) to be present in the vfat boot partition (partition 7). NOT bzImage in the /boot folder in the ext4 partition, which is entiretly redundant. Why that's still there I don't know. That one caught me out for quite a while...

So if you bitbake your new kernel, look for vmlinuz (it'll be in there somewhere under build/tmp in the Yocto environment), and copy that to the vfat partition (mounted at /boot in latest ubilinux), reboot, and it should use vmlinuz. It should be about 5-7MB, maybe a bit bigger, if you've added lots of stuff.

Dave.

How do I determine if my board is bricked? Here is my situation. I am trying to telnet into it so I can start working with Motion, and I was unable to connect over Ethernet. I then decided to just run blink to see if I could at least get something going, however the LED does not blink. When I upload the sketch from the Arduino IDE (Galileo version) it shows "upload complete" but I do not seem to be getting anything from the board. Are there any other tests or some way I can determine if it is the board or just operator error?

Thanks for the help.

Hello Jay,

I had the same problem before, although my laptop-hardware meets all conditions I had this problem.

My issue was a second graphic card (HD 4000 integrated plus NVIDIA GTX 675 m). I shut down the nvidia-card, restartet my pc and so in a "HD4000-solo-System" the installation works. After that, the WiDi program found my adapter and i was able to restart my nvidia-card without problems.

Good luck

Jochen

If 2 core 2 thread and 1 core 2 threads. which s best (fast) ? Sorry my bad English and silly question. I don't understand about thread correctly

I have recently bought an Intel Edison with the Arduino compatible breakout board. I am planning to use this for an universal translator project. Something like this: http://makezine.com/projects/universal-translator/. But what I am hoping to do is make it into a wearable, controlled by my phone, which would be connected to a microphone and a speaker. The translation would be using the Google speech recognition API and Microsoft translate API.

The problem is that this would involve making the whole breakout board smaller. I have seen many projects online which used the Edison board and arduino and the whole thing was small.

So what I ask for in this thread is a bit of advice about the project:

1. Should this run on Linux or Arduino? Which one is better for this project?
2. How can I make the whole thing as small as possible?

P.S.: AS far as my skills are concerned, I think I am quite qualified to do this project. I am an advanced programmer, so the software side of this project should be a piece of cake and my hardware abilities are, I would say, about upper intermediate, since I have lots of experience in hardware. But I have never worked with Edison or Galileo, so I will need some help in this way.

Any help would be appriciated.

HI there,

I'm new to Ardiuno in general and I'm a bit confused as to how this is all supposed to work.

I've got a Galileo - it came with Windows. I've gone to the Software Downloads page and downloaded SD-Card Linux Image, extracted to top level of the FAT32-formatted SD Card. I have three cables: an Ethernet, a USB to Micro-USB, and a weird USB-Ethernet thing that I got with the Galileo from Windows IoT.

I can talk to the Linux on the board via serial with the USB Client port and the sketch that sets this up 'Custom Arduino Sketch' here: sparkfun.

From here I can also simply do this on the command line to talk to the Linux over Ethernet, and then open a new Putty connection on that IP.

So that's two telnets onto the Linux on the Galileo. In fact I did this link above in a BlinkWithoutDelay sketch and spoke to the Board-Installed Linux over Ethernet while it was blinking.

However, I don't seem to be able to upload a sketch while the Bigger Linux on the SD card is in the Galileo? Surely this is possible?

When I'm uploading the same BlinkWithoutDelay sketch that does telnet on Ethernet, with the SD-Card-Linux in the Galileo, I get something like this in the Arduino IDE:

#mv the downloaded file to /sketch/sketch.elf

target_download_name="${host_file_name##*/}"

echo "Moving downloaded file to /sketch/sketch.elf on target"

Moving downloaded file to /sketch/sketch.elf on target

#$fixed_path/lsz.exe --escape -c "cp sketch /sketch/sketch.elf" <> $tty_port_id 1>&0

$fixed_path/lsz.exe --escape -c "mv $target_download_name /sketch/sketch.elf; chmod +x /sketch/sketch.elf" <> $tty_port_id 1>&0

^XB00000000123273^XB0600000012fff6^XB00000000000000^XB0600000000cd85^XB00000000000000^XB0600000000cd85^XB00000000000000^XB0600000000cd85^XB0600000000cd85^XB0600000000cd85^XB0600000000cd85

Transfer incomplete

Please help!

We have two Cisco C240 servers running Windows Server 2008 R2 Datacenter with X540 cards directly connected with cat 6A cord and they only run 0.1 Gbps (1%) with iperf. What am I doing wrong?

Intel site lists driver as PROWinx64.exe version: 18.4 (Latest) Date: 07/19/2013, but Cisco installed Intel driver 3.9.58.9101 7/11/2014 and it seems to work other than the performance.

I agree with mhahn, can you share what you're trying to accomplish.  I'll try to help you figure out a how.

@David_J_Hunt, I am going to see if I can get some steps for how-to via the tools on a bare Yocto image.