Bug#800005: fbset gets 'ioctl FBIOPUT_VSCREENINFO: Invalid argument'
- To: Mathieu Malaterre <malat@debian.org>
- Cc: 800005@bugs.debian.org
- Subject: Bug#800005: fbset gets 'ioctl FBIOPUT_VSCREENINFO: Invalid argument'
- From: Rick Thomas <rbthomas@pobox.com>
- Date: Sun, 3 Jul 2016 01:12:34 -0700
- Message-id: <[🔎] 59889C9B-68A6-4AEC-A570-DF05F54DCEBB@pobox.com>
- Reply-to: Rick Thomas <rbthomas@pobox.com>, 800005@bugs.debian.org
- In-reply-to: <CA+7wUsyB-Uyv5Ct4DECCzqhPUO0fPwfHMjnV8aJSc3cEg_aBUw@mail.gmail.com>
- References: <CA+7wUsyciGPWvhCXr1BOq0eqrKXY4TjfeT159OMx3nyDuwdqOA@mail.gmail.com> <7DB29484-9BC8-4EDD-821C-DDCB7D99C5F6@pobox.com> <BC3C69E1-4825-4579-8A0C-A7FE30046CC3@pobox.com> <CA+7wUswBEM6HY=CgWH9Tt8AWRgVcQNVCvojAe-KSdujhvQkX2Q@mail.gmail.com> <195C35FC-3843-4C31-9002-2CD92BEF4D88@pobox.com> <CA+7wUsyB-Uyv5Ct4DECCzqhPUO0fPwfHMjnV8aJSc3cEg_aBUw@mail.gmail.com>
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.
Still no help…
On powerpc64 (dual core Mac G5 running Debian 8.5):
> rbthomas@bigal:~$ dmesg > /tmp/dmesg-before.out
>
> rbthomas@bigal:~$ fbset
>
> mode "1680x1050"
> geometry 1680 1050 1680 1050 32
> timings 0 0 0 0 0 0 0
> accel true
> rgba 8/16,8/8,8/0,0/0
> endmode
>
> rbthomas@bigal:~$ fbset 800x600-60
> ioctl FBIOPUT_VSCREENINFO: Invalid argument
> rbthomas@bigal:~$ grep 800x600 /etc/fb.modes
> # 800x600, 48 Hz, Interlaced (36.00 MHz dotclock)
> mode "800x600-48-lace"
> # 800x600, 56 Hz, Non-Interlaced (36.00 MHz dotclock)
> mode "800x600-56"
> # 800x600, 60 Hz, Non-Interlaced (40.00 MHz dotclock)
> mode "800x600-60"
> # 800x600, 70 Hz, Non-Interlaced (44.90 MHz dotclock)
> mode "800x600-70"
> # 800x600, 72 Hz, Non-Interlaced (50.00 MHz dotclock)
> mode "800x600-72"
> # 800x600, 75 Hz, Non-Interlaced (49.50 MHz dotclock)
> mode "800x600-75"
> # 800x600, 90 Hz, Non-Interlaced (56.64 MHz dotclock)
> mode "800x600-90"
> # 800x600, 100 Hz, Non-Interlaced (67.50 MHz dotclock)
> mode “800x600-100"
>
> rbthomas@bigal:~$ dmesg > /tmp/dmesg-after.out
>
> rbthomas@bigal:~$ diff /tmp/dmesg-before.out /tmp/dmesg-after.out
>
> rbthomas@bigal:~$ cat /proc/cmdline
> root=/dev/mapper/bigal-root ro drm.debug=0xe
>
> rbthomas@bigal:~$ lsmod | grep drm
> drm_kms_helper 82001 1 nouveau
> drm 325466 6 ttm,drm_kms_helper,nouveau,sil164
> agpgart 39217 2 drm,ttm
> i2c_core 31058 10 drm,i2c_powermac,windfarm_smu_sat,drm_kms_helper,
> i2c_algo_bit,windfarm_lm75_sensor,nouveau,sil164,
> windfarm_max6690_sensor,snd_aoa_codec_onyx
Reply to: