> Conrad Kostecki <c...@conrad-kostecki.de> hat am 26. April 2016 um 12:10
> geschrieben:
> Hi!
> The new ThinkPad T460s is the same way affected, as other current ThinkPads
> (e.G. X260) generations.
> That means, you won't be able to get sound output, when using the L
> Conrad Kostecki hat am 26. April 2016 um 12:10
> geschrieben:
> Hi!
> The new ThinkPad T460s is the same way affected, as other current ThinkPads
> (e.G. X260) generations.
> That means, you won't be able to get sound output, when using the Lenovo
> CES 2013 docking
,
as the T460s uses the same docking connector.
I am attaching a patch, which works for me.
Cheers
Conrad
--
Fixes audio output on a ThinkPad T460s, when using Lenovo CES 2013
docking station series (basic, pro, ultra).
Signed-off-by: Conrad Kostecki <ck+linux
,
as the T460s uses the same docking connector.
I am attaching a patch, which works for me.
Cheers
Conrad
--
Fixes audio output on a ThinkPad T460s, when using Lenovo CES 2013
docking station series (basic, pro, ultra).
Signed-off-by: Conrad Kostecki
--- linux-4.6-rc5
and X250,
as the X260 uses the same docking connector.
I am attaching my patch, which works for me.
Cheers
Conrad
--
Fixes audio output on a ThinkPad X260, when using Lenovo CES 2013
docking station series (basic, pro, ultra).
Signed-off-by: Conrad Kostecki <
and X250,
as the X260 uses the same docking connector.
I am attaching my patch, which works for me.
Cheers
Conrad
--
Fixes audio output on a ThinkPad X260, when using Lenovo CES 2013
docking station series (basic, pro, ultra).
Signed-off-by: Conrad Kostecki
diff
> That file is way too big. In fact, it is exactly the size of the newest
> ".dat" file from Intel. The kernel doesn't grok that text format, the
> microcode updates have to be converted to binary format, first.
> I suggest you use "iucode_tool -S --write-earlyfw=ucode.cpio" to generate
>
> Hi!
> I'am trying to use the feature of loading early an intel microcode.
> According to the documentation (early-microcode.txt) that should be possible.
>
> I am currently using my own initrd, so I've created a second one, as the docs
> specified and merged it with my own.
>
> Galactica linux
Hi!
I'am trying to use the feature of loading early an intel microcode.
According to the documentation (early-microcode.txt) that should be possible.
I am currently using my own initrd, so I've created a second one, as the docs
specified and merged it with my own.
Galactica linux # file
That file is way too big. In fact, it is exactly the size of the newest
.dat file from Intel. The kernel doesn't grok that text format, the
microcode updates have to be converted to binary format, first.
I suggest you use iucode_tool -S --write-earlyfw=ucode.cpio to generate
your
> On Fri, Jul 18, 2014 at 08:40:42PM +0000, Conrad Kostecki wrote:
> > Where is the problem? Why is the microcode not being loaded early?
>
> CONFIG_MICROCODE_INTEL_EARLY=y set in .config?
Yes!
Galactica tmp # grep -i microcode /boot/config-3.15.5
CONFIG_MICROCODE=y
CONFIG_MI
Hi!
I'am trying to use the feature of loading early an intel microcode.
According to the documentation (early-microcode.txt) that should be possible.
I am currently using my own initrd, so I've created a second one, as the docs
specified and merged it with my own.
Galactica linux # file
Hi!
I'am trying to use the feature of loading early an intel microcode.
According to the documentation (early-microcode.txt) that should be possible.
I am currently using my own initrd, so I've created a second one, as the docs
specified and merged it with my own.
Galactica linux # file
On Fri, Jul 18, 2014 at 08:40:42PM +, Conrad Kostecki wrote:
Where is the problem? Why is the microcode not being loaded early?
CONFIG_MICROCODE_INTEL_EARLY=y set in .config?
Yes!
Galactica tmp # grep -i microcode /boot/config-3.15.5
CONFIG_MICROCODE=y
CONFIG_MICROCODE_INTEL=y
> On 02/14/2014 10:13 AM, Conrad Kostecki wrote:
> >>
> >> Does it have DMI?
> >
> > Unfortunately not.
> >
> > # dmidecode 2.12
> > # No SMBIOS nor DMI entry point found, sorry.
> >
>
> Sigh. Does anyone have contacts at Soekris wh
> On 02/14/2014 10:06 AM, Conrad Kostecki wrote:
> >
> > Hm. I am not. The Soekris is my only device with an E6xx CPU. This one is
> special, as Soekris does not implement ACPI.
> > I don't know, how other E6xx systems do work. I guess, there will have
> ACPI. Th
> On 02/14/2014 02:23 AM, Conrad Kostecki wrote:
> > Hello,
> > as the Soekris net6501 does not have any ACPI implementation, HPET
> won't get enabled.
> > This patch enables HPET on such platforms.
> >
> > [0.430149] pci :00:01.0: Force enabled HPET a
patch by Peter Neubauer, slightly modified by me.
-> http://www.mail-archive.com/soekris-tech@lists.soekris.com/msg06462.html
Cheers
Conrad
Signed-off-by: Peter Neubauer
Signed-off-by: Conrad Kostecki
--- a/arch/x86/kernel/quirks.c 2014-02-14 11:13:27.703432732 +0100
+++ b/arch/x86/kernel/quirk
patch by Peter Neubauer, slightly modified by me.
- http://www.mail-archive.com/soekris-tech@lists.soekris.com/msg06462.html
Cheers
Conrad
Signed-off-by: Peter Neubauer pneuba...@bluerwhite.org
Signed-off-by: Conrad Kostecki c...@conrad-kostecki.de
--- a/arch/x86/kernel/quirks.c 2014-02-14 11:13
On 02/14/2014 02:23 AM, Conrad Kostecki wrote:
Hello,
as the Soekris net6501 does not have any ACPI implementation, HPET
won't get enabled.
This patch enables HPET on such platforms.
[0.430149] pci :00:01.0: Force enabled HPET at 0xfed0
[0.644838] HPET: 3 timers
On 02/14/2014 10:06 AM, Conrad Kostecki wrote:
Hm. I am not. The Soekris is my only device with an E6xx CPU. This one is
special, as Soekris does not implement ACPI.
I don't know, how other E6xx systems do work. I guess, there will have
ACPI. There seem not to be many out
On 02/14/2014 10:13 AM, Conrad Kostecki wrote:
Does it have DMI?
Unfortunately not.
# dmidecode 2.12
# No SMBIOS nor DMI entry point found, sorry.
Sigh. Does anyone have contacts at Soekris who can complain about this
stuff?
I don't think, that Soekris will fix
22 matches
Mail list logo
