[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#728918: intel



I believe when using intel as a user, especially for on-processor graphics like Haswell and Sandy, I got improved driver results when using the latest microcode (video gfx acceleration is one. My i5 4670k processor was new this year, and the latest microcode came out around Aug 2013.. Gfx acceleration wasn't working with the packaged outdated microcode of a few months older, but furthermore in order for me to use proper working Haswell, I had to dive a bit into the testing branch, as intel is making a lot of new work for it's latest HD-capable processors)

the command I use iucode-tool -K microcode.dat,

microcode.dat is inside tarballed file but is not usable for the microcode service loader without extracting it (you're pretty much extracting the tarball which yields one file, then extracting/pulling an arragenment of binary snippets for different processors from microcode.dat, there's a way to extract just for your processor, if interested for more elaboration, I made a post over here https://plus.google.com/105696767572828808697/posts/fSMY3kT4c3s )

There's also this
https://01.org/linuxgraphics/community?qt-projects_aggregated_links=1
,but I would definitely include the processor type (eg, for me I'm using an intel i5 "4670k".. The processor should be spottable somewhere with dmidecode or cat /proc/cpuinfo (not sure if they can take debian reports)

Hopefully this helps :)


Reply to: