Dev1 Galaxy Forum / [SOLVED] startx fails since upgrade to 4.9 kernel

Re: [SOLVED] startx fails since upgrade to 4.9 kernel

dummy@example.com (stevewalsh) — Thu, 11 Jan 2018 17:16:59 +0000

SUCCESS !!!!

Well, I have a nice gui on the very latest kernel using the instructions at Devuan stable and Skylake (and Kaby Lake?) integrated GPU https://dev1galaxy.org/viewtopic.php?id=542

Alas, the wifi instructions there didn't work... time for a bit more research... (any ideas ?)

(I was almost ready to give up and start again with a.n.other distribution)

Thanks again everyone...

Re: [SOLVED] startx fails since upgrade to 4.9 kernel

dummy@example.com (bbatten) — Thu, 11 Jan 2018 17:00:54 +0000

stevewalsh wrote:

4 - I don't have nomodeset or vga= as kernel parameters

Nothing in /etc/modprobe.d along the lines of "modeset=0" or nomodeset=1"? Does "modinfo i915" show anything suspicious/interesting?

Good luck.

Re: [SOLVED] startx fails since upgrade to 4.9 kernel

dummy@example.com (golinux) — Thu, 11 Jan 2018 16:45:57 +0000

This post is a bit old but if you have a troublesome 'skylake' chip, this may have something relevant:

Devuan stable and Skylake (and Kaby Lake?) integrated GPU

Re: [SOLVED] startx fails since upgrade to 4.9 kernel

dummy@example.com (cynwulf) — Thu, 11 Jan 2018 16:32:13 +0000

00:00.0 Host bridge: Intel Corporation Device 1918 (rev 07)

Apparently this is a 'skylake' chip. Stable support was added in the 4.2 kernel. However from a few duckduckgo searches, it's been problematic.

Blacklisting of kernel mode setting drivers is less likely to work these days.

To boot with kernel mode setting disabled append nomodeset to the kernel command line (i915.modeset=0 also works). This can be made permanent via bootloader config.

The 3.16 kernel didn't support your hardware, so was likely loading the vesa driver. Disabling KMS on the 4.9 kernel and NOT explicitly loading the intel driver via any xorg configuration files, should yield the same result on the 4.9 kernel (the vesa driver being used). But surely just using vesa is not you end objective...?

You could just build a stable or mainline kernel, boot, startx leaving auto configured (no xorg config), cross your fingers and see what happens.

But mesa/drm and especially xorg (in particular xf86-video-intel) may all benefit from an upgrade. Simply put - the jessie release is probably too old for your hardware. It might be best for you to install the testing distribution. If the 4.9 kernel yields the same results there, building a newer kernel for that toolchain will be more worthwhile than building one for what you have now.

Re: [SOLVED] startx fails since upgrade to 4.9 kernel

dummy@example.com (stevewalsh) — Thu, 11 Jan 2018 14:24:45 +0000

ok, apologies for the delay in replying - weekends/work etc...

So here goes...

1 - xorg.conf with only monitor section

Section "Monitor"
	Identifier   "default monitor"
	VendorName   "Lenovo"
	ModelName    "Thinkpad LCD"
Modeline "1024x768_60.00"   63.50  1024 1072 1176 1328  768 771 775 798 -hsync +vsync
Modeline "0x0"   63.50  1024 1072 1176 1328  768 771 775 798 -hsync +vsync
EndSection

The Identifier, VendorName and ModelName were changed by me for a further test after seeing messages related to "no default monitor found"

Anyhow, with the defaults, I got the same result - no screens configured
Log here : https://pastebin.com/1hY5k1bk

2 - xorg.conf with chipset declaration

Section "ServerLayout"
	Identifier     "X.org Configured"
	Screen      0  "Screen0" 0 0
	Screen      1  "Screen1" RightOf "Screen0"
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
	ModulePath   "/usr/lib/xorg/modules"
	FontPath     "/usr/share/fonts/X11/misc"
	FontPath     "/usr/share/fonts/X11/cyrillic"
	FontPath     "/usr/share/fonts/X11/100dpi/:unscaled"
	FontPath     "/usr/share/fonts/X11/75dpi/:unscaled"
	FontPath     "/usr/share/fonts/X11/Type1"
	FontPath     "/usr/share/fonts/X11/100dpi"
	FontPath     "/usr/share/fonts/X11/75dpi"
	FontPath     "built-ins"
EndSection

Section "Module"
	Load  "glx"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "auto"
	Option	    "Device" "/dev/input/mice"
	Option	    "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
	Identifier   "Monitor0"
	VendorName   "Monitor Vendor"
	ModelName    "Monitor Model"
EndSection

Section "Monitor"
	Identifier   "Monitor1"
	VendorName   "Monitor Vendor"
	ModelName    "Monitor Model"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: : integer, : float, : "True"/"False",
        ### : "String", : " Hz/kHz/MHz",
        ### : "%"
        ### [arg]: arg optional
        #Option     "NoAccel"            	# []
        #Option     "AccelMethod"        	# 
        #Option     "Backlight"          	# 
        #Option     "DRI"                	# 
        #Option     "ColorKey"           	# 
        #Option     "VideoKey"           	# 
        #Option     "Tiling"             	# []
        #Option     "LinearFramebuffer"  	# []
        #Option     "SwapbuffersWait"    	# []
        #Option     "TripleBuffer"       	# []
        #Option     "XvPreferOverlay"    	# []
        #Option     "HotPlug"            	# []
        #Option     "ReprobeOutputs"     	# []
        #Option     "XvMC"               	# []
        #Option     "ZaphodHeads"        	# 
        #Option     "TearFree"           	# []
        #Option     "PerCrtcPixmaps"     	# []
        #Option     "FallbackDebug"      	# []
        #Option     "DebugFlushBatches"  	# []
        #Option     "DebugFlushCaches"   	# []
        #Option     "DebugWait"          	# []
        #Option     "BufferCache"        	# []
	Identifier  "Card0"
	Driver      "intel"
	BusID       "PCI:0:2:0"
	Chipset     "i915"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: : integer, : float, : "True"/"False",
        ### : "String", : " Hz/kHz/MHz",
        ### : "%"
        ### [arg]: arg optional
        #Option     "SWcursor"           	# []
        #Option     "HWcursor"           	# []
        #Option     "NoAccel"            	# []
        #Option     "ShadowFB"           	# []
        #Option     "VideoKey"           	# 
        #Option     "WrappedFB"          	# []
        #Option     "GLXVBlank"          	# []
        #Option     "ZaphodHeads"        	# 
        #Option     "PageFlip"           	# []
        #Option     "SwapLimit"          	# 
        #Option     "AsyncUTSDFS"        	# []
        #Option     "AccelMethod"        	# 
	Identifier  "Card1"
	Driver      "nouveau"
	BusID       "PCI:1:0:0"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
	SubSection "Display"
		Viewport   0 0
		Depth     1
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     4
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     8
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     15
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     16
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

Section "Screen"
	Identifier "Screen1"
	Device     "Card1"
	Monitor    "Monitor1"
	SubSection "Display"
		Viewport   0 0
		Depth     1
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     4
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     8
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     15
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     16
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
	EndSubSection
EndSection

Again, no joy with startx

log here : https://pastebin.com/nK1vtTnJ

3 - I tried the linux-image-4.9.0-0.bpo.2-amd64 kernel but still no difference :-(

4 - I don't have nomodeset or vga= as kernel parameters

5 - doing the egrep command I get no output on 3.6 or 4.9 kernels

root@devuan:/home/user# egrep -R i915 /etc/modprobe.d
root@devuan:/home/user#

So what now ?
Do I give up and start again? (I'll be honest, it's beginning to feel like this - I need to start using this laptop and I've never had such problems with linux before - Ubuntu/Centos/Fedora... albeit, none of those were on this latest laptop)

Thanks again, Steve

Re: [SOLVED] startx fails since upgrade to 4.9 kernel

dummy@example.com (bbatten) — Sat, 06 Jan 2018 20:29:31 +0000

Hi Steve,
Looks like you're still working this problem. I don't have a fix, but here are some links that might help:
First, Intel_graphics says
Make sure you do not have nomodeset or vga= as a kernel parameter, since Intel requires kernel mode-setting.
Also, check that you have not disabled Intel by using any modprobe blacklisting within /etc/modprobe.d/ or /usr/lib/modprobe.d/
FWIW, my Devuan Jessie has
[7] bryan: egrep -R i915 /etc/modprobe.d /etc/modprobe.d/i915-kms.conf:options i915 modeset=1:
even though I'm actually using a somewhat elderly Radeon 3000. "dpkg -S" can't find any package it belongs to, so I'm not sure exactly where that comes from.
Second, Kernel mode setting says
you should always disable:
Any vga= options in your bootloader as these will conflict with the native resolution enabled by KMS.
Any video= lines that enable a framebuffer that conflicts with the driver.
Any other framebuffer drivers (such as uvesafb).
Finally, enforcing the mode talks about EDID issues, just in case the i915 has issues there.
Hope this is helpful.

Re: [SOLVED] startx fails since upgrade to 4.9 kernel

dummy@example.com (Geoff 42) — Sat, 06 Jan 2018 16:06:48 +0000

Looking at kernels on Jessie, you have available linux-image-4.9.0-0.bpo.4-amd64 and linux-image-4.9.0-0.bpo.2-amd64.
These version numbers are the package numbers which are a bit different from the kernel versions.
The bpo.4 package is kernel 4.9.65-3+deb9u1~.
It is kernel 4.9.65 which people are complaining about causing graphics difficulties.
The bpo.2 package is kernel 4.9.18-1~bpo8+1.
Some people have reported that going back to an earlier 4.9 kernel got round their graphics problems.
If it is easy for you to try this earlier version, it may show whether the kernel is the problem.
Geoff

Re: [SOLVED] startx fails since upgrade to 4.9 kernel

dummy@example.com (ralph.ronnquist) — Sat, 06 Jan 2018 06:09:13 +0000

The more I read in on this, the more wrong I think I am, and the problem is in fact that the intel module gets unloaded, which seems to be because it can't detect the chipset. The underlying reason for that is one of many possibilities, but maybe an explicit chipset declaration in xorg.conf would make a difference. I.e., a device section including a chipset declaration.
For example, that you create an xorg.conf with the working kernel, and then use that with the new kernel, adding a chipset "i915" declaration for device "intel" .
However there may well be an "external" (to X) reason why probing fails, and why no screens are detected; even some kind of permission problem between the program (X) and the device (kernel).

Re: [SOLVED] startx fails since upgrade to 4.9 kernel

dummy@example.com (ralph.ronnquist) — Sat, 06 Jan 2018 02:41:24 +0000

Note: I just learned that the "pinning" of ascii seems to require a "pinning" of testing as well, so I've updated my post above (#6) for that. It doesn't really make a difference tor the topic here; it's just if someone tries that tidbit on some other quest.
So, the problem relates to the nouveau module, rather. The 3.6 kernel appears to have these modules compiled into the kernel, so comparisons of kernels don't say much.
I then see some 3 lines of inquiry, including that of declaring mode lines (and backgrounding @Geoff's point). The other two are to look into the solutions around "optimus/bumblebee", and/or using an nvidia module instead of nouveau.
There may be more of course, and I don't know which approach is most likely to succeed (if any).
Declaring mode lines might be the "least intrusive", but perhaps also the least likely to succeed. The steps for this would be:
Use cvt 1024 768 to get a mode line to use
Use X -configure to generate a xorg.conf file, where you
remove everything except the Monitor section,
add the mode line twice, with the first renamed to be "0x0",
before installing it as /etc/X11/xorg.conf
That should be it, I think. Run startx and capture the log, unless it works of course. The renamed mode line is as an attempt to pick up on the defaulted one as per the log; though that one is likely to, if it makes anything happier, still result in rendering a 0x0 screen, which isn't too useful. You also have a couple of test variations where you exclude the one or the other of the mode lines.
Ah, you need to undo my useless suggestions about i915.

Re: [SOLVED] startx fails since upgrade to 4.9 kernel

dummy@example.com (Geoff 42) — Fri, 05 Jan 2018 19:04:58 +0000

Whoops! 4.13 is in backports in ascii and I just noticed that you are running Jessie. Sorry.
Geoff

Re: [SOLVED] startx fails since upgrade to 4.9 kernel

dummy@example.com (stevewalsh) — Fri, 05 Jan 2018 18:46:12 +0000

If I blacklist the i915 kernel module, 4.9 fails to boot up completely - onscreen it appears to hang during it's failed attempts to load iwlwifi... However, the /var/log/messages log contains further entries...
Full excerpt here : https://pastebin.com/VeWHXrxp
For what it's worth, the module has dependencies of :
root@devuan:/home/user# modinfo -F depends i915 drm_kms_helper,drm,i2c-core,video,button,i2c-algo-bit
Perhaps this will explain (to someone who knows) why the blacklisting fails...
Looking at PCI device 01:00.0, the outputs are :
3.16
01:00.0 VGA compatible controller: NVIDIA Corporation Device 13b0 (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 222e Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 Capabilities: [900 v1] #19 01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1) Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-
4.9
01:00.0 VGA compatible controller: NVIDIA Corporation Device 13b0 (rev a2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 222e Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1 Len=024 Capabilities: [900 v1] #19 Kernel driver in use: nouveau
@Geoff, I don't see kernel 4.13 in the backports
root@devuan:/home/user# apt-cache search linux-image linux-headers-3.16.0-4-amd64 - Header files for Linux 3.16.0-4-amd64 linux-image-3.16.0-4-amd64 - Linux 3.16 for 64-bit PCs linux-image-3.16.0-4-amd64-dbg - Debugging symbols for Linux 3.16.0-4-amd64 linux-image-amd64 - Linux for 64-bit PCs (meta-package) linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration (meta-package) nvidia-kernel-3.16.0-4-amd64 - NVIDIA binary kernel module for Linux 3.16.0-4-amd64 linux-image-4.9.0-0.bpo.4-amd64 - Linux 4.9 for 64-bit PCs linux-image-4.9.0-0.bpo.4-amd64-dbg - Debug symbols for linux-image-4.9.0-0.bpo.4-amd64 linux-image-4.9.0-0.bpo.4-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT linux-image-4.9.0-0.bpo.4-rt-amd64-dbg - Debug symbols for linux-image-4.9.0-0.bpo.4-rt-amd64 linux-image-4.9.0-2-grsec-amd64 - Linux 4.9 for 64-bit PCs, Grsecurity protection linux-image-grsec-amd64 - Linux image meta-package, grsec featureset linux-image-rt-amd64 - Linux for 64-bit PCs (meta-package), PREEMPT_RT linux-image-rt-amd64-dbg - Debugging symbols for Linux rt-amd64 configuration (meta-package) linux-image-4.9.0-0.bpo.2-amd64 - Linux 4.9 for 64-bit PCs (signed) linux-image-4.9.0-0.bpo.2-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT (signed)
Again, thanks for the continued assistance and advice, at least the support for Devuan is keeping me going otherwise I might've thrown in the towel before now :-) Cheers, Steve
Re: [SOLVED] startx fails since upgrade to 4.9 kernel dummy@example.com (Geoff 42) — Fri, 05 Jan 2018 15:55:23 +0000 There have been a number of graphics problems reported with 4.9. I hit one with Intel graphics, but there were others. https://dev1galaxy.org/viewtopic.php?id=1794 There were suggestions that it was fixed by installing 4.13 from backports. This installs ok and I have not had any problems yet, but have not given it a good thrashing. Geoff Re: [SOLVED] startx fails since upgrade to 4.9 kernel dummy@example.com (ralph.ronnquist) — Fri, 05 Jan 2018 12:51:47 +0000 btw, what you want to use I would guess is the PCI device 01:00.0 rather. Maybe you can check that with lspci -vvv -s 01:00 for the two kernels. Re: [SOLVED] startx fails since upgrade to 4.9 kernel dummy@example.com (ralph.ronnquist) — Fri, 05 Jan 2018 12:41:48 +0000 Ah, there should be a newline; though I'm not sure that makes a difference by itself. Perhaps you should add the following line as well (with newline): install i915 /bin/false and probably rename the file to /etc/modprobe.d/blacklist.conf The install line supposedly fools the kernel to run the /bin/false program as way of trying to install the module, with the desired effect of not installing it. Apparently, with "just" a blacklist line, the module might be loaded anyhow due to a dependency from another module, whereas the added install line should counteract that load path as well. ... and add it into the initramfs of course. Re: [SOLVED] startx fails since upgrade to 4.9 kernel dummy@example.com (stevewalsh) — Fri, 05 Jan 2018 12:25:35 +0000 Thanks for the advice... Here's the lspci -vvv -s 2 output 3.16 kernel 00:02.0 VGA compatible controller: Intel Corporation Device 191d (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 222e Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: [40] Vendor Specific Information: Len=0c Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable- Count=1/1 Maskable- 64bit- Address: 00000000 Data: 0000 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] #1b Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] #13 4.9 kernel 00:02.0 VGA compatible controller: Intel Corporation Device 191d (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device 222e Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: 0000 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] #1b Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] #13 Kernel driver in use: i915 I created the blacklist file as advised and did the update-initramfs command root@devuan:/home/user# update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.9.0-0.bpo.4-amd64 Alas, when I reboot using the 4.9 kernel, the i915 module is still being used (checked with lscpi -k and -vvv -s 2 commands) fyi - there are several other files in the /etc/modprobe.d dir root@devuan:/home/user# ls -al /etc/modprobe.d total 20 drwxr-xr-x 1 root root 180 Jan 5 12:20 . drwxr-xr-x 1 root root 3314 Jan 5 12:16 .. -rw-r--r-- 1 root root 15 Jan 5 12:11 blacklist -rw-r--r-- 1 root root 390 Apr 8 2017 fbdev-blacklist.conf -rw-r--r-- 1 root root 154 Jul 9 01:33 intel-microcode-blacklist.conf -rw-r--r-- 1 root root 16 Jun 14 2014 libpisock9.conf -rw-r--r-- 1 root root 51 Jul 13 2015 modesetting.conf I've checked and blacklist contains only the line you suggested - no new line after etc... Again, thanks for everyones continued help with this... Steve