On Jun 30, 2016, at 12:50 AM, Mathieu Malaterre wrote:
> On Thu, Jun 30, 2016 at 9:45 AM, Rick Thomas wrote:
>> Do I understand correctly that I should put “drm.debug=0xe” as a kernel
>> argument at boot time? Then boot, try running my “fbset” test and send you
>> the entire output of dmesg
Do I understand correctly that I should put “drm.debug=0xe” as a kernel
argument at boot time? Then boot, try running my “fbset” test and send you the
entire output of dmesg including all boot messages. Is this correct?
Further, I guess you would prefer to have this on the amd64 machine in que
On Sun, Jun 26, 2016 at 2:59 AM, Rick Thomas wrote:
> For what it’s worth, I get the same behavior on amd64 running stretch. It’s
> not just on powerpc.
Great ! Could you please turn more debugging info. eg: drm.debug=0xe
and try again.
ref:
https://01.org/linuxgraphics/documentation/how-repor
Control: severity -1 important
... as this bug is not affecting everyone.
As per definition:
important
a bug which has a major effect on the usability of a package,
without rendering it completely unusable to everyone.
Package: fbset
Version: 2.1-28
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Prior to Jessie, I could use "fbset" toset the screen resolution on my PowerPC
Macs.
This was often necessary if the system happened to mis-guess the actual screen
resolution, or the screen wa
5 matches
Mail list logo
