Re: [Linux-4.9.28] iwlwifi 6230 AGN: Microcode SW error detected

[Luca Coelho]

On Wed, 2017-05-24 at 10:15 +0200, Sedat Dilek wrote:
> On Wed, May 24, 2017 at 9:57 AM, Luca Coelho  wrote:
> > On Wed, 2017-05-24 at 09:41 +0200, Sedat Dilek wrote:
> > > Hi,
> > 
> > Hi Sedat,
> > 
> > 
> > > I am seeing the below/following in my logs today.
> > > My AP is a Lenovo Moto-Z with LTE support.
> > > 
> > > Can you comment on this?
> > > Is this a "buggy" firmware and a new firmware around?
> > 
> > Looks like a buggy firmware, but unfortunately we don't have a newer
> > firmware with a fix for this.
> > 
> > 
> > > My kernel-config and full dmesg are attached.
> > > 
> > > If you need further informations, please let me know.
> > > 
> > > Hope this helps.
> > > 
> > > Regards,
> > > - Sedat -
> > > 
> > > P.S.: Excerpts from my dmesg-log.
> > > 
> > > [   16.708016] iwlwifi :01:00.0: Detected Intel(R) Centrino(R)
> > > Advanced-N 6230 AGN, REV=0xB0
> > 
> > This is a really old NIC (6+ years old) and unfortunately we can't
> > provide firmware fixes for it anymore.
> > 
> > Hopefully the recovery flow in the driver recovers the connectivity and
> > everything continues working fine.
> > 
> 
> Thanks for the fast reply.
> 
> Intel was(?) a good choice is my conclusion after getting no more
> replies/fixes for my SandyBridge-GPU from intel-gfx guys.
> This Samsung Ultrabook is 5 years young.
> I can understand that fixing a 6 years old NIC is not your prio #1.
> 
> As an example, there is no vulkan support for my GPU, so it's time for a 
> change?
> 
> No glue if other hardware vendors have better support.

We still do our best effort to fix driver bugs for these old NICs, but
unfortunately fixing the FW is a much more complicated issue and there's
nothing we can do. :(

Regarding the GPU stuff, I really can't comment, since I don't know much
about it.

--
Cheers,
Luca.

Re: [Linux-4.9.28] iwlwifi 6230 AGN: Microcode SW error detected

[Sedat Dilek]

On Wed, May 24, 2017 at 9:57 AM, Luca Coelho  wrote:
> On Wed, 2017-05-24 at 09:41 +0200, Sedat Dilek wrote:
>> Hi,
>
> Hi Sedat,
>
>
>> I am seeing the below/following in my logs today.
>> My AP is a Lenovo Moto-Z with LTE support.
>>
>> Can you comment on this?
>> Is this a "buggy" firmware and a new firmware around?
>
> Looks like a buggy firmware, but unfortunately we don't have a newer
> firmware with a fix for this.
>
>
>> My kernel-config and full dmesg are attached.
>>
>> If you need further informations, please let me know.
>>
>> Hope this helps.
>>
>> Regards,
>> - Sedat -
>>
>> P.S.: Excerpts from my dmesg-log.
>>
>> [   16.708016] iwlwifi :01:00.0: Detected Intel(R) Centrino(R)
>> Advanced-N 6230 AGN, REV=0xB0
>
> This is a really old NIC (6+ years old) and unfortunately we can't
> provide firmware fixes for it anymore.
>
> Hopefully the recovery flow in the driver recovers the connectivity and
> everything continues working fine.
>

Thanks for the fast reply.

Intel was(?) a good choice is my conclusion after getting no more
replies/fixes for my SandyBridge-GPU from intel-gfx guys.
This Samsung Ultrabook is 5 years young.
I can understand that fixing a 6 years old NIC is not your prio #1.

As an example, there is no vulkan support for my GPU, so it's time for a change?

No glue if other hardware vendors have better support.

- sed@ -

Re: [Linux-4.9.28] iwlwifi 6230 AGN: Microcode SW error detected

[Luca Coelho]

On Wed, 2017-05-24 at 09:41 +0200, Sedat Dilek wrote:
> Hi,

Hi Sedat,


> I am seeing the below/following in my logs today.
> My AP is a Lenovo Moto-Z with LTE support.
> 
> Can you comment on this?
> Is this a "buggy" firmware and a new firmware around?

Looks like a buggy firmware, but unfortunately we don't have a newer
firmware with a fix for this.


> My kernel-config and full dmesg are attached.
> 
> If you need further informations, please let me know.
> 
> Hope this helps.
> 
> Regards,
> - Sedat -
> 
> P.S.: Excerpts from my dmesg-log.
> 
> [   16.708016] iwlwifi :01:00.0: Detected Intel(R) Centrino(R)
> Advanced-N 6230 AGN, REV=0xB0

This is a really old NIC (6+ years old) and unfortunately we can't
provide firmware fixes for it anymore.

Hopefully the recovery flow in the driver recovers the connectivity and
everything continues working fine.


--
Cheers,
Luca.