Bug#800005: fbset gets 'ioctl FBIOPUT_VSCREENINFO: Invalid argument'

Hi Rick, On Sat, Jun 25, 2016 at 02:20:17AM -0700, Rick Thomas wrote: > > On Jun 20, 2016, at 5:57 AM, Mathieu Malaterre wrote: > > > Control: tags -1 moreinfo > > > == begin transcript === > root@bigal:~# dmesg > /tmp/dmesg-out-pre-fbset >

Bug#800005: fbset gets 'ioctl FBIOPUT_VSCREENINFO: Invalid argument'

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

Bug#800005: fbset gets 'ioctl FBIOPUT_VSCREENINFO: Invalid argument'

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

Bug#800005: fbset gets 'ioctl FBIOPUT_VSCREENINFO: Invalid argument'

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