Bug#800005: fbset gets 'ioctl FBIOPUT_VSCREENINFO: Invalid argument'
OK… I’ll try to get that done soon. Enjoy!
On Jun 30, 2016, at 12:50 AM, Mathieu Malaterre <malat@debian.org> wrote:
> On Thu, Jun 30, 2016 at 9:45 AM, Rick Thomas <rbthomas@pobox.com> 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 including all boot messages. Is this correct?
>>
>> Further, I guess you would prefer to have this on the amd64 machine in question rather than the original powerpc machine?
>>
>> What other info should I send? If I use the amd64 machine, I guess you’d like some hardware configuration info as well? Please be specific: a verbatim list of shell commands you’d like me to run would be most helpful!
>
> Hi Rick,
>
> Adding the boot parameter *should* tell us what went wrong in the
> fbset command. So yes I do expect you change the boot parameter, run
> dmesg before and after the fbset command. I do not care about amd64,
> so please do it on the powerpc.
>
> Thanks.
Reply to: