Bug#750639: installing adjtimex gives syntax error message
Package: adjtimex Version: 1.29-2.2 Severity: minor Installing adjtimex gives the following syntax error Setting up adjtimex (1.29-2.2) ... egrep: character class syntax is [[:space:]], not [:space:] -- System Information: Debian Release: 6.0.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel (armv5tel) Kernel: Linux 2.6.32-5-kirkwood Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages adjtimex depends on: ii debconf [debconf-2.0] 1.5.49 Debian configuration management sy ii libc6 2.13-38+deb7u1 Embedded GNU C Library: Shared lib adjtimex recommends no packages. Versions of packages adjtimex suggests: pn ntpdate(no description available) -- debconf information: adjtimex/compare_rtc: true adjtimex/run_daemon: true -- To UNSUBSCRIBE, email to debian-qa-packages-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140605102516.19108.52805.report...@base.rcthomas.org
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 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! Thanks! Rick On Jun 29, 2016, at 11:20 PM, Mathieu Malaterre wrote: > 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-report-bugs > > thanks
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 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 > agpgart39217 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
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 was on a KVM switch. But now, with Jessie, when fbset is used this way does one of two things, neither of them useful: 1) It complains that the resolution is not in /etc/fb.modes so is "Unknown". 2) If the resolution is actually present in /etc/fb.modes, it says ioctl FBIOPUT_VSCREENINFO: Invalid argument In either case it does not change the screen resolution. The bug may not be in fbset, of course. It may be in the kernel. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: powerpc (ppc) Kernel: Linux 3.16.0-4-powerpc Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fbset depends on: ii libc6 2.19-18+deb8u1 ii udev 215-17+deb8u2 fbset recommends no packages. fbset suggests no packages. -- no debconf information
