On Ter, 2015-06-16 at 11:37 -0300, Sergio Belkin wrote:
> 2015-06-16 11:30 GMT-03:00 Reindl Harald :
>
>
> Am 16.06.2015 um 16:14 schrieb Sergio Belkin:
> Well,
>
> I was not crazy:
>
>
> ht
2015-06-16 11:30 GMT-03:00 Reindl Harald :
>
>
> Am 16.06.2015 um 16:14 schrieb Sergio Belkin:
>
>> Well,
>>
>> I was not crazy:
>>
>>
>> http://fedoramagazine.org/solution-graphics-issues-intel-graphics-chipsets-fedora-22/
>>
>
> well, you did not mention your hardware nor any issues
> you just s
Am 16.06.2015 um 16:14 schrieb Sergio Belkin:
Well,
I was not crazy:
http://fedoramagazine.org/solution-graphics-issues-intel-graphics-chipsets-fedora-22/
well, you did not mention your hardware nor any issues
you just showed some log warnings
2015-05-29 7:57 GMT-03:00 kendell clark mailt
Well,
I was not crazy:
http://fedoramagazine.org/solution-graphics-issues-intel-graphics-chipsets-fedora-22/
HTH
2015-05-29 7:57 GMT-03:00 kendell clark :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> hi
> Well, I don't know about the OP, but for me there are no symptoms. I
> just ge
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
hi
Well, I don't know about the OP, but for me there are no symptoms. I
just get the error at every startup, but the system functions normally
Thanks
Kendell clark
drago01 wrote:
> On Fri, May 29, 2015 at 12:13 PM, Sergio Belkin
> wrote:
>> Hi,
>>
Am 29.05.2015 um 12:51 schrieb drago01:
On Fri, May 29, 2015 at 12:13 PM, Sergio Belkin wrote:
Could you tell me if anyone else is having this kind of issues:
[vie may 29 07:01:22 2015] [drm] Initialized drm 1.1.0 20060810
[vie may 29 07:01:22 2015] [drm] Memory usable by graphics device = 2
On Fri, May 29, 2015 at 12:13 PM, Sergio Belkin wrote:
> Hi,
>
> Could you tell me if anyone else is having this kind of issues:
>
> [vie may 29 07:01:22 2015] [drm] Initialized drm 1.1.0 20060810
> [vie may 29 07:01:22 2015] [drm] Memory usable by graphics device = 2048M
> [vie may 29 07:01:22 20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
hi
I don't have a solution for you, but I also experience this error, and
have ever since, I think, kernel 3.16 or so. It seems like a harmless
error, the system seems to work normally. Nevertheless, it should get
fixed if it is a bug.
Thanks
Kendell