Non-Intel Bloggers on the Intel® Developer Zone

While most of the people who post on the Intel Developer Zone blog are Intel employees, we welcome and encourage guest bloggers who aren't Intel employees. This document explains both process for getting permission and training for posting on the blog, and the rules and guidelines that non-Intel bloggers agree to follow.

Getting Started - Account Permissions and Training

As a non-Intel employee, there are a few steps to get started posting on the Intel Developer Zone blog. Basically, you need to have an Intel Developer Zone account, request permission to be a blog author, and receive training on how to post, etc.

  1. Create an Intel Developer Zone account - If you don't already have one, you'll need to create a free account on Intel Developer Zone. Visit the Registration page and create an account.
  2. Receive Blog Training - Contact Josh Bancroft to schedule a 30 minute phone meeting, to go over how to log in and post to the blog, deal with comments, and answer any questions you have.

Your posts will need to be reviewed by an Intel employee (usually your contact person at Intel Developer Zone), who will be the one to actually publish your post. This isn't an editorial review, just a quick check to make sure the post is OK to appear on the site. When you are ready to have a post published, please set the Moderation State to "Needs Review" (under Publishing Options), click "Submit", then send an email to your Intel contact to let them know you have a post that's ready to be published. Setting your post to "Needs Review" doesn't guarantee it will be looked at - please send a note to your Intel contact to make sure it gets seen.

Rules and Guidelines

To post on the Intel Developer Zone blog, non-Intel employees agree to follow Intel's Social Media Guidelines. Please read them, and bring any questions you have to the blog training meeting. They're pretty simple, and could be summed up by "don't do anything that would get you or Intel in trouble".


For more complete information about compiler optimizations, see our Optimization Notice.


Axel Abraham V.'s picture

Excellent information, and thanks in advance.

I hope can write like a blogger to be better contributions in this community.

THOMAS BABU B.'s picture

This about making Bluez 5 work on LFS machine.


Initially it was really difficult to bring up bluetooth using Bluez 5. It seems it was okay with Bluez 4.I have tried different
versions of Bluez 5 on my LFS build. Even up to Bluez 5.28 it was not satisfactory.
Now it is Bluz5.30, with this, LFS doc and lot of trail, I could manage.
I feel Bluez is one of the most badly documented user unfriendly software.
I also feel it is very buggy. It can hang machines forcing to hard boot the system.
I have seen bluetooth forcing the Android phone also to reboot.
So it is important to get the latest version of the software.
But to make the bluetooth speaker work Pulseaudio was needed.
It is better to get the latest version; here also LFS doc was fine.
So the process of connecting speaker was using
power on
scan on
pairable on
pair <device>

agent on
connect <device>

Second time onwards just connection is fine. Probably you can trust the device.

Now the actual sound. Here pactl and pacmd are useful.
paplay -d <device> <wav file> can test the devices.
using pacmd and with command 'list-sinks' can show the devices.

pacmd ->list-modules can show the modules loaded.
How to change automatically the audio output to bluetooth speaker when it
is connected? For me in one machine it was working fine, with an identical

LFS in another machine it was not working. Finally it was identified as a
missing  module 'module-device-manager' with arg 'do_routing=1'.
Once it was loaded everything was fine. This particular module was not shown in the pulse configurations. So I have to find that.
ie pacmd
 > load-module  module-device-manager do_routing=1
One can add a line in the default configuration file available in /etc/pulse.
or one can add it in the user configuration file also

Now to make the new bluetooth speaker being used to play sound,
For that issue the command 'move-sink-input <present index> <new bluetooth sink>' using pacmd. You can find the sink names my issuing the command 'list-sinks'.
If your speaker is not connecting, it may be that it is already connected elsewhere. If it is not so, remove-device; scan on; pair; and connect using bluetoothctl.

I was worrying how to make file transfer using bluetooth (Bluez5). Actually very little information is available in LFS documention or in general in the NET. This is very true and unfortunate about Bluez in general. They do not provide any real user doc or nothing is available in net (hence this note). So the steps are as follows:
You need to install OBEX library. Then you build Bluez5 (if it not done already). It will install obexd.
After installation you can find obexd in $PREFIX/libexec/bluetooth/obexd.
This is where you find bluetoothd also.

One generally make a link for bluetoothd in /usr/sbin. A similar link can be made for obexd also. Once you start bluetoothd and obexd you can find object transfer profiles in bluetoothctl->show.

If you need a phone to push objects to the computer, you need to run obexd with  options '-a' and '-r <directory to get files>'. if '-a' is not given phone will fail to send the file.


Now how to push a file from Computer to Phone. For this you need obexctl, I do not think it is a finished tool, and it will not be installed while we build Bluez 5. I have seen it in the source tree and copied to /usr/bin/. It should be used to connect the Phone and when the connection is established one can 'send <file>' and you have to accept the request in the phone.

Starting obexd as deamon was a problem. When obexd was tried on a text terminal (init 3) it was  not possible to start since it needs a dbus session which in turn needs  X display. It means one need to login an X seession before you start obexd. If you dissable X while building DBUS (--without-x) then Window Managers will not  work. But there is solution with 'dus-run-session < command> [args]'. That means you can start a service obexd (like bluetoothd) in the system start-up. So just by switching on the Computer ( if pairing, trusting etc... was done earlier) one can push files from Phone to computer.

This is my experience, and I can push objects from phone to computer just by keeping the computer switched on. I can also push files from computer to phone. I can connect bluetooth speaker.

I hope this experience is useful for others.

abraham a.'s picture


pleas i have a project it is the smart security project , with this project we will not look for the viruses because the computers will be smart to do that 

i am seeking an opportunity to work with intel for that 


vishal t.'s picture

i am planning to buy a new LED monitor for my computer.i am using intel 82945G chipset.please suggest me what is the maximum resolution monitor i can purchase for my computer.i am attaching the intel report below

Intel(R) Graphics Media Accelerator Driver Report

Report Date: 11/02/2013
Report Time[hr:mm:ss]: 15:42:18
Driver Version:
Operating System: Windows 7 Ultimate* , (6.1.7600)
Default Language: English
DirectX* Version: 11.0
Physical Memory: 1013 MB
Minimum Graphics Memory: 8 MB
Maximum Graphics Memory: 250 MB
Graphics Memory in Use: 99 MB
Processor: x86 family 6 Model 15 Stepping 13
Processor Speed: 2194 MHZ
Vendor ID: 8086
Device ID: 2772
Device Revision: 02

* Accelerator Information *

Accelerator in Use: Intel(R) 82945G Express Chipset

Video BIOS: 1374
Current Graphics Mode: 1024 by 768 True Color (60 Hz)

* Devices Connected to the Graphics Accelerator *

Active Monitors: 1

* Monitor *

Monitor Name: Generic PnP Monitor
Display Type: Analog
Gamma Value: 2.50
DDC2 Protocol: Supported
Maximum Image Size: Horizontal: 10.6 inches
Vertical: 7.8 inches
Monitor Supported Modes:
640 by 350 (70 Hz)
640 by 350 (85 Hz)
640 by 480 (60 Hz)
640 by 480 (72 Hz)
640 by 480 (75 Hz)
640 by 480 (85 Hz)
640 by 480 (100 Hz)
720 by 400 (70 Hz)
800 by 600 (60 Hz)
800 by 600 (72 Hz)
800 by 600 (75 Hz)
800 by 600 (85 Hz)
832 by 624 (75 Hz)
1024 by 768 (60 Hz)
Display Power Management Support:
Standby Mode: Supported
Suspend Mode: Supported
Active Off Mode: Supported

* Other names and brands are the property of their respective


Joshua Bancroft (Intel)'s picture

Yes, contact Paul, or the community manager that you've worked with in the past, and they can help you.

Sergey Kostrov's picture

I'm an Intel Black Belt Software Developer and am Non-Intel employee. Should I contact Paul Steinberg in order to arrange a 30 minute phone meeting, that is Blog Training?

Thank in advance.

Add a Comment

Have a technical question? Visit our forums. Have site or software product issues? Contact support.