You are not logged in.

#1 2017-11-08 01:58:51

mcbaron
Member
Registered: 2017-03-07
Posts: 11

Need help with redshift/f.lux

Hello all,

I've been fighting with my install for a while trying to get either flux or redshift to be able to change the color temperature of my screen. It's getting to the point that it really is affecting my sleep.

I have Intel graphics drivers on this machine, which I've updated from the jessie-backports repository following the directions from this post.

I think this post is close to my problem, but I'm connected to an external monitor via HDMI, not a laptop screen, and I'm not using an NVIDIA graphics card. For S's & G's I did try installing bumblebee, to no effect.

Here are some outputs:

# lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Device 193b (rev 09)
# glxinfo | egrep "OpenGL vendor|OpenGL renderer"
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits)
# lshw -c video
  *-display UNCLAIMED     
       description: VGA compatible controller
       product: Intel Corporation
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 09
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list
       configuration: latency=0
       resources: memory:db000000-dbffffff memory:90000000-9fffffff ioport:f000(size=64) memory:c0000-dffff
# modinfo -F filename `lshw -c video | awk '/configuration: driver/{print $2}' | cut -d= -f2`
modinfo: ERROR: missing module or filename.
# lspci -nnk | grep -i vga -A3 | grep 'in use'
# xrandr --listproviders
Providers: number : 0

If I try to use xrandr directly:

# xrandr --output default --brightness .8
xrandr: Gamma size is 0.

But nothing happens, regardless of what value of brightness I input.

The really frustrating thing is that at one point in this computer's short lifetime f.lux worked perfectly. I really have no idea why that changed after a bunsenlabs reinstall.

I'm happy to provide more diagnostic info upon request. Thank you all in advance!

Last edited by mcbaron (2017-11-08 01:59:08)

Offline

#2 2017-11-08 07:11:46

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: Need help with redshift/f.lux

mcbaron wrote:

I have Intel graphics drivers on this machine, which I've updated from the jessie-backports repository

Did you actually need to do this? Were the graphics working OK with the stock drivers?

If so then I suggest that you return to the stock configuration as it will probably be less buggy, the Intel drivers in particular are notorious for introducing new bugs with every new version roll

I think we also need to know the exact hardware so first update the database with

sudo update-pciids

Then run this command and post the output here:

lspci -knn | grep -iA2 'vga\|3d'

Thanks!

Offline

#3 2017-11-08 22:41:07

mcbaron
Member
Registered: 2017-03-07
Posts: 11

Re: Need help with redshift/f.lux

I actually hit that post, and went to update the drivers from jessie-backports only to find that I'd already been running the updated drivers. I can revert, but haven't yet.

Here's the output:

# lspci -knn | grep -iA2 'vga\|3d'
00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Pro Graphics 580 [8086:193b] (rev 09)
	Subsystem: Intel Corporation Device [8086:2064]
00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911]
--
3d:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM951/PM951 [144d:a802] (rev 01)
	Subsystem: Samsung Electronics Co Ltd Device [144d:a801]
	Kernel driver in use: nvme

Thanks!

Offline

#4 2017-11-08 22:49:30

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: Need help with redshift/f.lux

mcbaron wrote:

I actually hit that post, and went to update the drivers from jessie-backports only to find that I'd already been running the updated drivers

BunsenLabs does not run the backported kernel unless you force it to and your output indicates that you have no kernel drivers loaded for your video card at all.

Try that guide again, your hardware does need it.

Confirm the running kernel with

uname -a

Offline

#5 2017-11-08 22:51:32

mcbaron
Member
Registered: 2017-03-07
Posts: 11

Re: Need help with redshift/f.lux

# uname -a
Linux nyquist 4.9.0-0.bpo.4-amd64 #1 SMP Debian 4.9.51-1~bpo8+1 (2017-10-17) x86_64 GNU/Linux

I'll kick through the guide again.

--Edit--
Nope, nothing changed with the apt-get installs...

Last edited by mcbaron (2017-11-08 22:56:01)

Offline

#6 2017-11-14 15:50:42

mcbaron
Member
Registered: 2017-03-07
Posts: 11

Re: Need help with redshift/f.lux

*Bump*

What should be my next steps?

Offline

#7 2017-11-14 20:14:22

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: Need help with redshift/f.lux

Let's check the current status of your system:

apt-cache policy xserver-xorg-video-intel libegl1-mesa libgl1-mesa-glx libgl1-mesa-dri

Can we also please see the content of /var/log/Xorg.0.log

Offline

#8 2017-11-15 01:31:06

mcbaron
Member
Registered: 2017-03-07
Posts: 11

Re: Need help with redshift/f.lux

$ apt-cache policy xserver-xorg-video-intel libegl1-mesa libgl1-mesa-glx libgl1-mesa-dri
xserver-xorg-video-intel:
  Installed: 2:2.99.917+git20161206-1~bpo8+1
  Candidate: 2:2.99.917+git20161206-1~bpo8+1
  Version table:
 *** 2:2.99.917+git20161206-1~bpo8+1 0
        100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
        100 /var/lib/dpkg/status
     2:2.21.15-2+b2 0
        500 http://httpredir.debian.org/debian/ jessie/main amd64 Packages
libegl1-mesa:
  Installed: 13.0.6-1~bpo8+1
  Candidate: 13.0.6-1~bpo8+1
  Version table:
 *** 13.0.6-1~bpo8+1 0
        100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
        100 /var/lib/dpkg/status
     10.3.2-1+deb8u1 0
        500 http://httpredir.debian.org/debian/ jessie/main amd64 Packages
libgl1-mesa-glx:
  Installed: 13.0.6-1~bpo8+1
  Candidate: 13.0.6-1~bpo8+1
  Version table:
 *** 13.0.6-1~bpo8+1 0
        100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
        100 /var/lib/dpkg/status
     10.3.2-1+deb8u1 0
        500 http://httpredir.debian.org/debian/ jessie/main amd64 Packages
libgl1-mesa-dri:
  Installed: 13.0.6-1~bpo8+1
  Candidate: 13.0.6-1~bpo8+1
  Version table:
 *** 13.0.6-1~bpo8+1 0
        100 http://httpredir.debian.org/debian/ jessie-backports/main amd64 Packages
        100 /var/lib/dpkg/status
     10.3.2-1+deb8u1 0
        500 http://httpredir.debian.org/debian/ jessie/main amd64 Packages

and /var/log/Xorg.0.log:

[     4.071] 
X.Org X Server 1.16.4
Release Date: 2014-12-20
[     4.071] X Protocol Version 11, Revision 0
[     4.071] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian
[     4.071] Current Operating System: Linux nyquist 4.9.0-0.bpo.4-amd64 #1 SMP Debian 4.9.51-1~bpo8+1 (2017-10-17) x86_64
[     4.071] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.9.0-0.bpo.4-amd64 root=UUID=8a9061ea-8976-4618-a803-17e184a08efa ro intel_pstate=no_hwp quiet nomodeset
[     4.071] Build Date: 14 October 2017  10:41:31AM
[     4.071] xorg-server 2:1.16.4-1+deb8u2 (http://www.debian.org/support) 
[     4.071] Current version of pixman: 0.32.6
[     4.071] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[     4.071] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     4.071] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov  7 20:47:32 2017
[     4.071] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     4.071] (==) No Layout section.  Using the first Screen section.
[     4.071] (==) No screen section available. Using defaults.
[     4.071] (**) |-->Screen "Default Screen Section" (0)
[     4.071] (**) |   |-->Monitor "<default monitor>"
[     4.072] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[     4.072] (==) Automatically adding devices
[     4.072] (==) Automatically enabling devices
[     4.072] (==) Automatically adding GPU devices
[     4.073] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[     4.073] 	Entry deleted from font path.
[     4.073] (==) FontPath set to:
	/usr/share/fonts/X11/misc,
	/usr/share/fonts/X11/100dpi/:unscaled,
	/usr/share/fonts/X11/75dpi/:unscaled,
	/usr/share/fonts/X11/Type1,
	/usr/share/fonts/X11/100dpi,
	/usr/share/fonts/X11/75dpi,
	built-ins
[     4.073] (==) ModulePath set to "/usr/lib/xorg/modules"
[     4.073] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[     4.073] (II) Loader magic: 0x5591a5b0ed80
[     4.073] (II) Module ABI versions:
[     4.073] 	X.Org ANSI C Emulation: 0.4
[     4.073] 	X.Org Video Driver: 18.0
[     4.073] 	X.Org XInput driver : 21.0
[     4.073] 	X.Org Server Extension : 8.0
[     4.078] (--) PCI:*(0:0:2:0) 8086:193b:8086:2064 rev 9, Mem @ 0xdb000000/16777216, 0x90000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
[     4.078] (II) LoadModule: "glx"
[     4.079] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     4.083] (II) Module glx: vendor="X.Org Foundation"
[     4.083] 	compiled for 1.16.4, module version = 1.0.0
[     4.083] 	ABI class: X.Org Server Extension, version 8.0
[     4.083] (==) AIGLX enabled
[     4.083] (==) Matched intel as autoconfigured driver 0
[     4.083] (==) Matched modesetting as autoconfigured driver 1
[     4.083] (==) Matched fbdev as autoconfigured driver 2
[     4.083] (==) Matched vesa as autoconfigured driver 3
[     4.083] (==) Assigned the driver to the xf86ConfigLayout
[     4.083] (II) LoadModule: "intel"
[     4.083] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[     4.084] (II) Module intel: vendor="X.Org Foundation"
[     4.084] 	compiled for 1.16.4, module version = 2.99.917
[     4.084] 	Module class: X.Org Video Driver
[     4.084] 	ABI class: X.Org Video Driver, version 18.0
[     4.084] (II) LoadModule: "modesetting"
[     4.084] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     4.084] (II) Module modesetting: vendor="X.Org Foundation"
[     4.084] 	compiled for 1.16.4, module version = 0.9.0
[     4.084] 	Module class: X.Org Video Driver
[     4.084] 	ABI class: X.Org Video Driver, version 18.0
[     4.084] (II) LoadModule: "fbdev"
[     4.085] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[     4.085] (II) Module fbdev: vendor="X.Org Foundation"
[     4.085] 	compiled for 1.15.99.904, module version = 0.4.4
[     4.085] 	Module class: X.Org Video Driver
[     4.085] 	ABI class: X.Org Video Driver, version 18.0
[     4.085] (II) LoadModule: "vesa"
[     4.085] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[     4.085] (II) Module vesa: vendor="X.Org Foundation"
[     4.085] 	compiled for 1.15.99.904, module version = 2.3.3
[     4.085] 	Module class: X.Org Video Driver
[     4.085] 	ABI class: X.Org Video Driver, version 18.0
[     4.085] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
	i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
	915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
	Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
	GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[     4.085] (II) intel: Driver for Intel(R) HD Graphics
[     4.085] (II) intel: Driver for Intel(R) Iris(TM) Graphics
[     4.085] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics
[     4.085] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     4.085] (II) FBDEV: driver for framebuffer: fbdev
[     4.085] (II) VESA: driver for VESA chipsets: vesa
[     4.085] (++) using VT number 7

[     4.093] (EE) open /dev/dri/card0: No such file or directory
[     4.093] (WW) Falling back to old probe method for modesetting
[     4.093] (EE) open /dev/dri/card0: No such file or directory
[     4.093] (II) Loading sub module "fbdevhw"
[     4.093] (II) LoadModule: "fbdevhw"
[     4.093] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[     4.093] (II) Module fbdevhw: vendor="X.Org Foundation"
[     4.093] 	compiled for 1.16.4, module version = 0.0.2
[     4.093] 	ABI class: X.Org Video Driver, version 18.0
[     4.093] (**) FBDEV(1): claimed PCI slot 0@0:2:0
[     4.093] (II) FBDEV(1): using default device
[     4.093] (WW) Falling back to old probe method for vesa
[     4.093] (EE) Screen 0 deleted because of no matching config section.
[     4.093] (II) UnloadModule: "modesetting"
[     4.093] (II) FBDEV(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[     4.093] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
[     4.093] (==) FBDEV(0): RGB weight 888
[     4.093] (==) FBDEV(0): Default visual is TrueColor
[     4.093] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
[     4.093] (II) FBDEV(0): hardware: EFI VGA (video memory: 9024kB)
[     4.093] (II) FBDEV(0): checking modes against framebuffer device...
[     4.093] (II) FBDEV(0): checking modes against monitor...
[     4.093] (--) FBDEV(0): Virtual size is 1920x1200 (pitch 1920)
[     4.093] (**) FBDEV(0):  Built-in mode "current": 230.4 MHz, 94.7 kHz, 77.4 Hz
[     4.093] (II) FBDEV(0): Modeline "current"x0.0  230.41  1920 1952 2192 2432  1200 1204 1208 1224 -hsync -vsync -csync (94.7 kHz b)
[     4.093] (==) FBDEV(0): DPI set to (96, 96)
[     4.093] (II) Loading sub module "fb"
[     4.093] (II) LoadModule: "fb"
[     4.093] (II) Loading /usr/lib/xorg/modules/libfb.so
[     4.094] (II) Module fb: vendor="X.Org Foundation"
[     4.094] 	compiled for 1.16.4, module version = 1.0.0
[     4.094] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     4.094] (**) FBDEV(0): using shadow framebuffer
[     4.094] (II) Loading sub module "shadow"
[     4.094] (II) LoadModule: "shadow"
[     4.094] (II) Loading /usr/lib/xorg/modules/libshadow.so
[     4.094] (II) Module shadow: vendor="X.Org Foundation"
[     4.094] 	compiled for 1.16.4, module version = 1.1.0
[     4.094] 	ABI class: X.Org ANSI C Emulation, version 0.4
[     4.094] (II) UnloadModule: "vesa"
[     4.094] (II) Unloading vesa
[     4.094] (==) Depth 24 pixmap format is 32 bpp
[     4.094] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[     4.095] (==) FBDEV(0): Backing store enabled
[     4.095] (==) FBDEV(0): DPMS enabled
[     4.095] (==) RandR enabled
[     4.098] (II) SELinux: Disabled on system
[     4.099] (II) AIGLX: Screen 0 is not DRI2 capable
[     4.099] (EE) AIGLX: reverting to software rendering
[     4.138] (II) AIGLX: Loaded and initialized swrast
[     4.138] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[     4.167] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[     4.167] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[     4.167] (II) LoadModule: "evdev"
[     4.167] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[     4.168] (II) Module evdev: vendor="X.Org Foundation"
[     4.168] 	compiled for 1.16.0, module version = 2.9.0
[     4.168] 	Module class: X.Org XInput Driver
[     4.168] 	ABI class: X.Org XInput driver, version 21.0
[     4.168] (II) Using input driver 'evdev' for 'Power Button'
[     4.168] (**) Power Button: always reports core events
[     4.168] (**) evdev: Power Button: Device: "/dev/input/event2"
[     4.168] (--) evdev: Power Button: Vendor 0 Product 0x1
[     4.168] (--) evdev: Power Button: Found keys
[     4.168] (II) evdev: Power Button: Configuring as keyboard
[     4.168] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2/event2"
[     4.168] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[     4.168] (**) Option "xkb_rules" "evdev"
[     4.168] (**) Option "xkb_model" "pc105"
[     4.168] (**) Option "xkb_layout" "us"
[     4.168] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[     4.168] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[     4.168] (II) Using input driver 'evdev' for 'Power Button'
[     4.168] (**) Power Button: always reports core events
[     4.168] (**) evdev: Power Button: Device: "/dev/input/event1"
[     4.168] (--) evdev: Power Button: Vendor 0 Product 0x1
[     4.168] (--) evdev: Power Button: Found keys
[     4.168] (II) evdev: Power Button: Configuring as keyboard
[     4.168] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1/event1"
[     4.168] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[     4.168] (**) Option "xkb_rules" "evdev"
[     4.168] (**) Option "xkb_model" "pc105"
[     4.168] (**) Option "xkb_layout" "us"
[     4.168] (II) config/udev: Adding input device Sleep Button (/dev/input/event0)
[     4.168] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[     4.168] (II) Using input driver 'evdev' for 'Sleep Button'
[     4.168] (**) Sleep Button: always reports core events
[     4.168] (**) evdev: Sleep Button: Device: "/dev/input/event0"
[     4.168] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[     4.168] (--) evdev: Sleep Button: Found keys
[     4.168] (II) evdev: Sleep Button: Configuring as keyboard
[     4.168] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0/event0"
[     4.168] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[     4.168] (**) Option "xkb_rules" "evdev"
[     4.168] (**) Option "xkb_model" "pc105"
[     4.168] (**) Option "xkb_layout" "us"
[     4.169] (II) config/udev: Adding input device MOSART Semi. 2.4G Wireless Mouse (/dev/input/event5)
[     4.169] (**) MOSART Semi. 2.4G Wireless Mouse: Applying InputClass "evdev pointer catchall"
[     4.169] (II) Using input driver 'evdev' for 'MOSART Semi. 2.4G Wireless Mouse'
[     4.169] (**) MOSART Semi. 2.4G Wireless Mouse: always reports core events
[     4.169] (**) evdev: MOSART Semi. 2.4G Wireless Mouse: Device: "/dev/input/event5"
[     4.232] (--) evdev: MOSART Semi. 2.4G Wireless Mouse: Vendor 0x62a Product 0x4102
[     4.232] (--) evdev: MOSART Semi. 2.4G Wireless Mouse: Found 9 mouse buttons
[     4.232] (--) evdev: MOSART Semi. 2.4G Wireless Mouse: Found scroll wheel(s)
[     4.232] (--) evdev: MOSART Semi. 2.4G Wireless Mouse: Found relative axes
[     4.232] (--) evdev: MOSART Semi. 2.4G Wireless Mouse: Found x and y relative axes
[     4.232] (--) evdev: MOSART Semi. 2.4G Wireless Mouse: Found absolute axes
[     4.232] (II) evdev: MOSART Semi. 2.4G Wireless Mouse: Forcing absolute x/y axes to exist.
[     4.232] (II) evdev: MOSART Semi. 2.4G Wireless Mouse: Configuring as mouse
[     4.232] (II) evdev: MOSART Semi. 2.4G Wireless Mouse: Adding scrollwheel support
[     4.232] (**) evdev: MOSART Semi. 2.4G Wireless Mouse: YAxisMapping: buttons 4 and 5
[     4.232] (**) evdev: MOSART Semi. 2.4G Wireless Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[     4.232] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.3/1-3.3:1.0/0003:062A:4102.0001/input/input5/event5"
[     4.232] (II) XINPUT: Adding extended input device "MOSART Semi. 2.4G Wireless Mouse" (type: MOUSE, id 9)
[     4.232] (II) evdev: MOSART Semi. 2.4G Wireless Mouse: initialized for relative axes.
[     4.232] (WW) evdev: MOSART Semi. 2.4G Wireless Mouse: ignoring absolute axes.
[     4.232] (**) MOSART Semi. 2.4G Wireless Mouse: (accel) keeping acceleration scheme 1
[     4.232] (**) MOSART Semi. 2.4G Wireless Mouse: (accel) acceleration profile 0
[     4.232] (**) MOSART Semi. 2.4G Wireless Mouse: (accel) acceleration factor: 2.000
[     4.232] (**) MOSART Semi. 2.4G Wireless Mouse: (accel) acceleration threshold: 4
[     4.232] (II) config/udev: Adding input device MOSART Semi. 2.4G Wireless Mouse (/dev/input/mouse0)
[     4.232] (II) No input driver specified, ignoring this device.
[     4.232] (II) This device may have been added with another device file.
[     4.232] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event6)
[     4.232] (II) No input driver specified, ignoring this device.
[     4.232] (II) This device may have been added with another device file.
[     4.232] (II) config/udev: Adding input device HDA Intel PCH Speaker (/dev/input/event7)
[     4.232] (II) No input driver specified, ignoring this device.
[     4.232] (II) This device may have been added with another device file.
[     4.232] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event8)
[     4.232] (II) No input driver specified, ignoring this device.
[     4.232] (II) This device may have been added with another device file.
[     4.232] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
[     4.232] (II) No input driver specified, ignoring this device.
[     4.232] (II) This device may have been added with another device file.
[     4.233] (II) config/udev: Adding input device Nuvoton w836x7hg Infrared Remote Transceiver (/dev/input/event4)
[     4.233] (**) Nuvoton w836x7hg Infrared Remote Transceiver: Applying InputClass "evdev keyboard catchall"
[     4.233] (II) Using input driver 'evdev' for 'Nuvoton w836x7hg Infrared Remote Transceiver'
[     4.233] (**) Nuvoton w836x7hg Infrared Remote Transceiver: always reports core events
[     4.233] (**) evdev: Nuvoton w836x7hg Infrared Remote Transceiver: Device: "/dev/input/event4"
[     4.233] (--) evdev: Nuvoton w836x7hg Infrared Remote Transceiver: Vendor 0x1050 Product 0xc3
[     4.233] (--) evdev: Nuvoton w836x7hg Infrared Remote Transceiver: Found keys
[     4.233] (II) evdev: Nuvoton w836x7hg Infrared Remote Transceiver: Configuring as keyboard
[     4.233] (**) Option "config_info" "udev:/sys/devices/pnp0/00:01/rc/rc0/input3/event4"
[     4.233] (II) XINPUT: Adding extended input device "Nuvoton w836x7hg Infrared Remote Transceiver" (type: KEYBOARD, id 10)
[     4.233] (**) Option "xkb_rules" "evdev"
[     4.233] (**) Option "xkb_model" "pc105"
[     4.233] (**) Option "xkb_layout" "us"
[     4.234] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[     4.441] (II) config/udev: Adding input device Lenovo Lenovo Black Silk USB Keyboard (/dev/input/event10)
[     4.441] (**) Lenovo Lenovo Black Silk USB Keyboard: Applying InputClass "evdev keyboard catchall"
[     4.442] (II) Using input driver 'evdev' for 'Lenovo Lenovo Black Silk USB Keyboard'
[     4.442] (**) Lenovo Lenovo Black Silk USB Keyboard: always reports core events
[     4.442] (**) evdev: Lenovo Lenovo Black Silk USB Keyboard: Device: "/dev/input/event10"
[     4.442] (--) evdev: Lenovo Lenovo Black Silk USB Keyboard: Vendor 0x17ef Product 0x602d
[     4.442] (--) evdev: Lenovo Lenovo Black Silk USB Keyboard: Found keys
[     4.442] (II) evdev: Lenovo Lenovo Black Silk USB Keyboard: Configuring as keyboard
[     4.442] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.4/1-3.4.1/1-3.4.1:1.1/0003:17EF:602D.0003/input/input10/event10"
[     4.442] (II) XINPUT: Adding extended input device "Lenovo Lenovo Black Silk USB Keyboard" (type: KEYBOARD, id 11)
[     4.442] (**) Option "xkb_rules" "evdev"
[     4.442] (**) Option "xkb_model" "pc105"
[     4.442] (**) Option "xkb_layout" "us"
[     4.442] (II) config/udev: Adding input device Lenovo Lenovo Black Silk USB Keyboard (/dev/input/event9)
[     4.442] (**) Lenovo Lenovo Black Silk USB Keyboard: Applying InputClass "evdev keyboard catchall"
[     4.442] (II) Using input driver 'evdev' for 'Lenovo Lenovo Black Silk USB Keyboard'
[     4.442] (**) Lenovo Lenovo Black Silk USB Keyboard: always reports core events
[     4.442] (**) evdev: Lenovo Lenovo Black Silk USB Keyboard: Device: "/dev/input/event9"
[     4.442] (--) evdev: Lenovo Lenovo Black Silk USB Keyboard: Vendor 0x17ef Product 0x602d
[     4.442] (--) evdev: Lenovo Lenovo Black Silk USB Keyboard: Found keys
[     4.442] (II) evdev: Lenovo Lenovo Black Silk USB Keyboard: Configuring as keyboard
[     4.442] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3.4/1-3.4.1/1-3.4.1:1.0/0003:17EF:602D.0002/input/input9/event9"
[     4.442] (II) XINPUT: Adding extended input device "Lenovo Lenovo Black Silk USB Keyboard" (type: KEYBOARD, id 12)
[     4.442] (**) Option "xkb_rules" "evdev"
[     4.442] (**) Option "xkb_model" "pc105"
[     4.442] (**) Option "xkb_layout" "us"
[ 39847.620] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 39847.621] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 39848.781] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 54126.738] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 54126.739] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 54126.742] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 54132.256] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 73197.406] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 73197.406] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 73198.102] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 74739.739] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 74739.740] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 74739.742] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 74745.255] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[ 75030.572] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[128891.152] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[128891.152] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[128921.124] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[145790.872] (EE) FBDEV(0): FBIOBLANK: Invalid argument
[145790.872] (EE) FBDEV(0): FBIOBLANK: Invalid argument

Offline

#9 2017-11-15 07:21:09

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 9,093
Website

Re: Need help with redshift/f.lux

Your outputs seems inconsistent to me, unless I've missed something.

mcbaron wrote:

Here's the output:

# lspci -knn | grep -iA2 'vga\|3d'
00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Pro Graphics 580 [8086:193b] (rev 09)
	Subsystem: Intel Corporation Device [8086:2064]

This shows that no kernel driver is loaded for your video card but the Xorg log shows that the Intel DDX drivers are loading fine  hmm

Are you sure there is no "kernel driver in use" line for your video card in the full output of `lspci -k`?

You could try loading up a Debian stretch "live" image and see if stuff works there, support should be better with that release.

Offline

#10 2017-11-15 14:28:48

mcbaron
Member
Registered: 2017-03-07
Posts: 11

Re: Need help with redshift/f.lux

$ lspci -k 
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 0a)
	Subsystem: Intel Corporation Device 2064
	Kernel driver in use: skl_uncore
00:02.0 VGA compatible controller: Intel Corporation Iris Pro Graphics 580 (rev 09)
	Subsystem: Intel Corporation Device 2064
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model
	Subsystem: Intel Corporation Device 2064
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
	Subsystem: Intel Corporation Device 2064
	Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
	Subsystem: Intel Corporation Device 2064
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
	Subsystem: Intel Corporation Device 2064
	Kernel driver in use: mei_me
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
	Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #2 (rev f1)
	Kernel driver in use: pcieport
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1)
	Kernel driver in use: pcieport
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1)
	Kernel driver in use: pcieport
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
	Kernel driver in use: pcieport
00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13 (rev f1)
	Kernel driver in use: pcieport

There doesn't seem to be a kernel driver in use for the video card. Something must be awry.

I'll look into loading up a stretch live disk, and see what happens.
Thanks again for your help on this!

Offline

Board footer

Powered by FluxBB