The officially official Devuan Forum!

You are not logged in.

#1 2018-01-03 16:16:21

stevewalsh
Member
Registered: 2018-01-03
Posts: 9  

[SOLVED] startx fails since upgrade to 4.9 kernel

Hello,

New to Devuan (jessie) - I like the non-systemd idea...

All went well with the initial install (a few niggles aside with EFI boot manager and installing grub)
Alas, my wifi adapter doesn't work - UNCLAIMED is the issue there...
reading around the subject it turns out my wifi card (Intel 8260) isn't supported out of the box with the default jessie kernel (3.6)
I stumbled across this page https://askubuntu.com/questions/693109/ … ed-network and was tempted to follow the advice.
https://www.intel.com/content/www/us/en … rking.html states that support exists in 4.1+ kernels hence I'm here having installed the 4.9 kernel from the jessie backports repo.

However, as per the subject, I now have no fancy gui (well, as fancy as LXDE gets)

I'm able to successfully "startx" when using the 3.6 kernel but with 4.9 my Xorg.0.log has the following errors :
[   648.776] (EE) Screen(s) found, but none have a usable configuration.
[   648.776] (EE)
Fatal server error:
[   648.776] (EE) no screens found(EE)

Here's the full log... https://pastebin.com/5SWp4WTG

Any advice gratefully received...

Thanks, Steve

Last edited by stevewalsh (2018-01-12 08:32:46)

Offline

#2 2018-01-03 16:38:18

fsmithred
Administrator
Registered: 2016-11-25
Posts: 857  

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

You can do one of two things to fix this.

1. Install a display manager.
or
2. Install xserver-xorg-legacy and add the following line to /etc/X11/Xwrapper.config

needs_root_rights=yes

Offline

#3 2018-01-03 19:19:03

stevewalsh
Member
Registered: 2018-01-03
Posts: 9  

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

thank you for the reply.

is xserver-xorg-legacy available for jessie ?

root@devuan:/home/user# apt-get install xserver-xorg-legacy
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package xserver-xorg-legacy

here's the list of repo's I currently have enabled...

deb http://gb.mirror.devuan.org/merged/ jessie main
deb-src http://gb.mirror.devuan.org/merged/ jessie main

# jessie-security, previously known as 'volatile'
deb http://gb.mirror.devuan.org/merged/ jessie-security main non-free
deb-src http://gb.mirror.devuan.org/merged/ jessie-security main non-free

# jessie-updates, previously known as 'volatile'
deb http://gb.mirror.devuan.org/merged/ jessie-updates main non-free
deb-src http://gb.mirror.devuan.org/merged/ jessie-updates main non-free

# non-free intel 8260 wlan firmware
deb http://httpredir.debian.org/debian/ jessie main contrib non-free

# backports
deb http://gb.mirror.devuan.org/merged/ jessie-backports main

# virtualbox
deb http://download.virtualbox.org/virtualbox/debian/ jessie contrib

Offline

#4 2018-01-04 09:23:32

fungus
Member
From: Any witch way
Registered: 2017-07-12
Posts: 497  
Website

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

apt install  xserver-xorg-legacy

Offline

#5 2018-01-04 11:13:36

stevewalsh
Member
Registered: 2018-01-03
Posts: 9  

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

root@devuan:~# apt install xserver-xorg-legacy
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Unable to locate package xserver-xorg-legacy

Offline

#6 2018-01-04 12:34:54

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 253  

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

No, xserver-xorg-legacy is in ASCII.

If @fsmithred meant for you bring it in from ASCII, you should make sure to "pin" ASCII as well, e.g. by a file /etc/apt/preferences.d/reluctant-ascii with the following content:

Package: *
Pin: release a=ascii
Pin-Priority: 10

Package: *
Pin: release a=testing
Pin-Priority: 10

Then you can (temporarily) add a lline to your sources.list:

deb http://pkgmaster.devuan.org/merged ascii main

And install xserver-xorg-legacy using the special command

# apt-get install -t ascii --no-install-recommends xserver-xorg-legacy

However if that threatens to bring in a lot and/or remove a lot, you should probably abort, rather.

Last edited by ralph.ronnquist (2018-01-06 02:00:21)

Offline

#7 2018-01-04 13:48:15

fsmithred
Administrator
Registered: 2016-11-25
Posts: 857  

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

Oh, good catch, rrq. No, I did not mean to get the package from ascii. I gave the solution to the wrong problem. The legacy issue is related to the newer version of xorg, not the newer kernel. Sorry about that, Steve.

jessie...   xorg...

First thing I would try is adding 'nomodeset' to the boot command. At the grub boot menu, press 'e' to edit the boot entry, scroll down to the linux line and add nomodeset to the end of that line. Then ctrl-x to boot.

If that doesn't work, it might be a firmware issue.

What is the output of lspci? (so we can see what hardware you have)

For future reference, you're better off using debian documentation than ubuntu. Here' s a wiki page for your wireless. The package you need is firmware-iwlwifi, and you should get it from jessie-backports.
https://wiki.debian.org/iwlwifi

Offline

#8 2018-01-04 16:07:43

stevewalsh
Member
Registered: 2018-01-03
Posts: 9  

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

Thank you for the replies...

Here's the story so far...

I tried with nomodeset and got the same result...

Here's the output of lspci

root@devuan:/home/user# lspci
00:00.0 Host bridge: Intel Corporation Device 1918 (rev 07)
00:01.0 PCI bridge: Intel Corporation Device 1901 (rev 07)
00:02.0 VGA compatible controller: Intel Corporation Device 191d (rev 06)
00:14.0 USB controller: Intel Corporation Device a12f (rev 31)
00:14.2 Signal processing controller: Intel Corporation Device a131 (rev 31)
00:16.0 Communication controller: Intel Corporation Device a13a (rev 31)
00:16.3 Serial controller: Intel Corporation Device a13d (rev 31)
00:17.0 SATA controller: Intel Corporation Device a102 (rev 31)
00:1c.0 PCI bridge: Intel Corporation Device a112 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Device a114 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Device a11c (rev f1)
00:1f.0 ISA bridge: Intel Corporation Device a150 (rev 31)
00:1f.2 Memory controller: Intel Corporation Device a121 (rev 31)
00:1f.3 Audio device: Intel Corporation Device a170 (rev 31)
00:1f.4 SMBus: Intel Corporation Device a123 (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-LM (rev 31)
01:00.0 VGA compatible controller: NVIDIA Corporation Device 13b0 (rev a2)
01:00.1 Audio device: NVIDIA Corporation Device 0fbc (rev a1)
02:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
06:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 525a (rev 01)

Given the prospect of install xserver-xorg-legacy from ascii, I took the other original option of installing a display manager... I chose SLiM.
I now get a nice login screen with the 3.16 kernel, but not with the 4.9 kernel so still stuck at the same point. (why isn't SLiM working with 4.9 ?)

The slim.log just says

slim: waiting for X server to begin accepting connections.
Giving up.
slim: unable to connect to X server


slim: waiting for X server to begin accepting connections.

slim: waiting for X server to shut down.

(I should point out that with the 3.16 kernel, I do also get the "error" message box : no session for pid xxxx)

Any further help would be much appreciated.

On the wireless thing, I did try the advice on https://wiki.debian.org/iwlwifi to start with, but it didn't work for my 8260 adapter, hence I'm here with the later kernel which "should" include firmware for this adapter (see original post).

Thanks again, Steve

Offline

#9 2018-01-04 20:45:34

fungus
Member
From: Any witch way
Registered: 2017-07-12
Posts: 497  
Website

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

Sorry for the above I took a look and seems the whole X in Jessie is of a much older edition than that of ascii.  So I don't think a partial installation would be compatible as it also replaces a couple of X11 server pkgs. 

If you can compare lspci -k from both kernels you may be able to find what is missing or different on 4.9

Also, if you really want to get deep into it and have the time try the ascii iso from refracta to see if it works.

Everytime I see nvidia in a linux forum is like looking at a can of worms.,

Offline

#10 2018-01-05 09:49:01

stevewalsh
Member
Registered: 2018-01-03
Posts: 9  

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

Thanks for the tip fungus...

I've compared lscpi -k on both kernels and there is a difference !

here's 3.16

00:02.0 VGA compatible controller: Intel Corporation Device 191d (rev 06)
	Subsystem: Lenovo Device 222e

here's 4.9

00:02.0 VGA compatible controller: Intel Corporation Device 191d (rev 06)
	Subsystem: Lenovo Device 222e
	Kernel driver in use: i915

So, no kernel driver "works" (kinda - see prvious post for error) and a kernel driver completely fails...

Next steps ?
modprobe -r <something i915> on the 4.9 kernel ?

Thanks in advance, Steve

Offline

#11 2018-01-05 10:56:39

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 253  

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

Apparently the module i915 doesn't recognize the chipset. Could you please run $ lspci -vvv -s 2 with both kernels, to give us some more things to look at. Especially it should tell which module is used for your 3.6 kernel (or maybe not).

One end result that I could see in your Xorg.0.log is that it uses mode "0x0", which is a rather small display. But from that I'm guessing there might also be a way out by declaring a mode line, which would be through an /etc/X11/xconf.org with a Monitor section. This path of resurrection is windy and chilly...

Before that, you should maybe try just blackilisting i915, by making/editing the file /etc/modprobe.d/blacklist, to include:

blacklist i915

and then also make sure that it propagates into your initramfs, by

# update-initramfs -u

The wanted result from that is that i915 is not loaded, but that something else and better is loaded instead. smile

Remember to keep tab of what you do, so you can unwind if it doesn't work.

Offline

#12 2018-01-05 12:25:35

stevewalsh
Member
Registered: 2018-01-03
Posts: 9  

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

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 11
	Region 0: Memory at d2000000 (64-bit, non-prefetchable) [size=16M]
	Region 2: Memory at a0000000 (64-bit, prefetchable) [size=512M]
	Region 4: I/O ports at 5000 [size=64]
	Expansion ROM at <unassigned> [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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 130
	Region 0: Memory at d2000000 (64-bit, non-prefetchable) [size=16M]
	Region 2: Memory at a0000000 (64-bit, prefetchable) [size=512M]
	Region 4: I/O ports at 5000 [size=64]
	[virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
	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: 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

Offline

#13 2018-01-05 12:41:48

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 253  

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

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.

Offline

#14 2018-01-05 12:51:47

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 253  

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

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.

Offline

#15 2018-01-05 15:55:23

Geoff 42
Member
Registered: 2016-12-15
Posts: 180  

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

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

Offline

#16 2018-01-05 18:46:12

stevewalsh
Member
Registered: 2018-01-03
Posts: 9  

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

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at d3000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at d0000000 (64-bit, prefetchable) [size=32M]
	Region 5: I/O ports at 4000 [size=128]
	Expansion ROM at d4080000 [disabled] [size=512K]
	Capabilities: [60] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 00000000fee003f8  Data: 0000
	Capabilities: [78] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <512ns, L1 <4us
			ClockPM+ Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range AB, TimeoutDis+, LTR+, OBFF Via message
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, EqualizationPhase1+
			 EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [250 v1] Latency Tolerance Reporting
		Max snoop latency: 71680ns
		Max no snoop latency: 71680ns
	Capabilities: [258 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=255us PortTPowerOnTime=10us
	Capabilities: [128 v1] Power Budgeting <?>
	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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 17
	Region 0: Memory at d4000000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: [60] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
		Address: 0000000000000000  Data: 0000
	Capabilities: [78] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <512ns, L1 <4us
			ClockPM+ Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk-
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range AB, TimeoutDis+, LTR+, OBFF Via message
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
			 EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
	Kernel driver in use: snd_hda_intel

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- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 133
	Region 0: Memory at d3000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at c0000000 (64-bit, prefetchable) [size=256M]
	Region 3: Memory at d0000000 (64-bit, prefetchable) [size=32M]
	Region 5: I/O ports at 4000 [size=128]
	Expansion ROM at d4000000 [disabled] [size=512K]
	Capabilities: [60] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
		Address: 00000000fee003b8  Data: 0000
	Capabilities: [78] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 256 bytes, PhantFunc 0, Latency L0s unlimited, L1 <64us
			ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
			RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 256 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <512ns, L1 <4us
			ClockPM+ Surprise- LLActRep- BwNot-
		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range AB, TimeoutDis+, LTR+, OBFF Via message
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled
		LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, EqualizationPhase1+
			 EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest-
	Capabilities: [100 v1] Virtual Channel
		Caps:	LPEVC=0 RefClk=100ns PATEntryBits=1
		Arb:	Fixed- WRR32- WRR64- WRR128-
		Ctrl:	ArbSelect=Fixed
		Status:	InProgress-
		VC0:	Caps:	PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
			Arb:	Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
			Ctrl:	Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
			Status:	NegoPending- InProgress-
	Capabilities: [250 v1] Latency Tolerance Reporting
		Max snoop latency: 0ns
		Max no snoop latency: 0ns
	Capabilities: [258 v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=255us PortTPowerOnTime=10us
	Capabilities: [128 v1] Power Budgeting <?>
	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

Last edited by stevewalsh (2018-01-06 10:04:10)

Offline

#17 2018-01-05 19:04:58

Geoff 42
Member
Registered: 2016-12-15
Posts: 180  

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

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

Geoff

Offline

#18 2018-01-06 02:41:24

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 253  

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

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.

Offline

#19 2018-01-06 06:09:13

ralph.ronnquist
Administrator
From: Clifton Hill, Victoria, AUS
Registered: 2016-11-30
Posts: 253  

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

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).

Offline

#20 2018-01-06 16:06:48

Geoff 42
Member
Registered: 2016-12-15
Posts: 180  

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

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

Offline

#21 2018-01-06 20:29:31

bbatten
Member
Registered: 2017-07-02
Posts: 29  

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

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.

Offline

#22 2018-01-11 14:24:45

stevewalsh
Member
Registered: 2018-01-03
Posts: 9  

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

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: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
        ### <percent>: "<f>%"
        ### [arg]: arg optional
        #Option     "NoAccel"            	# [<bool>]
        #Option     "AccelMethod"        	# <str>
        #Option     "Backlight"          	# <str>
        #Option     "DRI"                	# <str>
        #Option     "ColorKey"           	# <i>
        #Option     "VideoKey"           	# <i>
        #Option     "Tiling"             	# [<bool>]
        #Option     "LinearFramebuffer"  	# [<bool>]
        #Option     "SwapbuffersWait"    	# [<bool>]
        #Option     "TripleBuffer"       	# [<bool>]
        #Option     "XvPreferOverlay"    	# [<bool>]
        #Option     "HotPlug"            	# [<bool>]
        #Option     "ReprobeOutputs"     	# [<bool>]
        #Option     "XvMC"               	# [<bool>]
        #Option     "ZaphodHeads"        	# <str>
        #Option     "TearFree"           	# [<bool>]
        #Option     "PerCrtcPixmaps"     	# [<bool>]
        #Option     "FallbackDebug"      	# [<bool>]
        #Option     "DebugFlushBatches"  	# [<bool>]
        #Option     "DebugFlushCaches"   	# [<bool>]
        #Option     "DebugWait"          	# [<bool>]
        #Option     "BufferCache"        	# [<bool>]
	Identifier  "Card0"
	Driver      "intel"
	BusID       "PCI:0:2:0"
	Chipset     "i915"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
        ### <percent>: "<f>%"
        ### [arg]: arg optional
        #Option     "SWcursor"           	# [<bool>]
        #Option     "HWcursor"           	# [<bool>]
        #Option     "NoAccel"            	# [<bool>]
        #Option     "ShadowFB"           	# [<bool>]
        #Option     "VideoKey"           	# <i>
        #Option     "WrappedFB"          	# [<bool>]
        #Option     "GLXVBlank"          	# [<bool>]
        #Option     "ZaphodHeads"        	# <str>
        #Option     "PageFlip"           	# [<bool>]
        #Option     "SwapLimit"          	# <i>
        #Option     "AsyncUTSDFS"        	# [<bool>]
        #Option     "AccelMethod"        	# <str>
	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

Offline

#23 2018-01-11 16:32:13

cynwulf
Member
Registered: 2017-10-09
Posts: 178  

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

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.

Last edited by cynwulf (2018-01-11 16:36:31)

Offline

#24 2018-01-11 16:45:57

golinux
Administrator
Registered: 2016-11-25
Posts: 1,224  

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

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

Offline

#25 2018-01-11 17:00:54

bbatten
Member
Registered: 2017-07-02
Posts: 29  

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

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.

Offline

Board footer