Kernel 4.0, lightdm startup issue

[dibl]

I ran d-u this morning and all updates including the new kernel were installed without error.  On my HP laptop with Intel graphics there were no issues booting the new kernel.  However on my big desktop rig with Nvidia graphics (which needs "nomodeset"), there is some problem starting lightdm, which I have never seen before.  After 3 or 4 attempts with kernel 4.0, I booted 3.19.3-towo.3 and there is no problem.  Here is the systemctl output, booting kernel 4.0:

Code: [Select]

systemctl status -l lightdm.service
● lightdm.service - Light Display Manager
   Loaded: loaded (/lib/systemd/system/lightdm.service; enabled)
   Active: failed (Result: start-limit) since Tue 2015-04-14 11:46:43 EDT; 2min 16s ago
     Docs: man:lightdm(1)
  Process: 1757 ExecStart=/usr/sbin/lightdm (code=exited, status=1/FAILURE)
  Process: 1753 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/sbin/lightdm" ] (code=exited, status=0/SUCCESS)
 Main PID: 1757 (code=exited, status=1/FAILURE)


Apr 14 11:46:42 imerabox systemd[1]: lightdm.service: main process exited, code=exited, status=1/FAILURE
Apr 14 11:46:42 imerabox systemd[1]: Unit lightdm.service entered failed state.
Apr 14 11:46:43 imerabox systemd[1]: lightdm.service holdoff time over, scheduling restart.
Apr 14 11:46:43 imerabox systemd[1]: Stopping Light Display Manager...
Apr 14 11:46:43 imerabox systemd[1]: Starting Light Display Manager...
Apr 14 11:46:43 imerabox systemd[1]: lightdm.service start request repeated too quickly, refusing to start.
Apr 14 11:46:43 imerabox systemd[1]: Failed to start Light Display Manager.
Apr 14 11:46:43 imerabox systemd[1]: Unit lightdm.service entered failed state.
Apr 14 11:47:35 imerabox systemd[1]: Stopped Light Display Manager.

Here is the configuration:

Code: [Select]

don@imerabox:/$ inxi -v3
System:    Host: imerabox Kernel: 3.19.3-towo.3-siduction-amd64 x86_64 (64 bit gcc: 4.9.2)
           Desktop: KDE 4.14.3 (Qt 4.8.6) Distro: aptosid 2011-02 Ἡμέρα - kde-lite - (201107131633)
Machine:   System: ASUS product: All Series
           Mobo: ASUSTeK model: Z87-WS v: Rev 1.xx Bios: American Megatrends v: 2004 date: 06/05/2014
CPU:       Quad core Intel Core i7-4770 (-HT-MCP-) cache: 8192 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28022
           clock speeds: max: 3900 MHz 1: 3600 MHz 2: 3404 MHz 3: 3429 MHz 4: 3440 MHz 5: 3402 MHz 6: 3414 MHz
           7: 3400 MHz 8: 3401 MHz
Graphics:  Card: NVIDIA GM107 [GeForce GTX 750 Ti] bus-ID: 05:00.0
           Display Server: X.Org 1.16.4 driver: nvidia Resolution: 1920x1200@59.88hz
           GLX Renderer: GeForce GTX 750 Ti/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 346.47 Direct Rendering: Yes
Network:   Card-1: Intel I210 Gigabit Network Connection driver: igb v: 5.2.15-k port: d000 bus-ID: 07:00.0
           IF: eth1 state: up speed: 100 Mbps duplex: full mac: e0:3f:49:e6:85:c3
           Card-2: Intel I210 Gigabit Network Connection driver: igb v: 5.2.15-k port: a000 bus-ID: 0a:00.0
           IF: eth2 state: down mac: e0:3f:49:e6:85:c4
Drives:    HDD Total Size: 2220.5GB (35.9% used) ID-1: model: OCZ
           ID-2: model: Hitachi_HTS72101 ID-3: model: OCZ
           ID-4: model: WDC_WD1000DHTZ ID-5: model: WDC_WD1000DHTZ
Info:      Processes: 311 Uptime: 2 min Memory: 1463.0/7927.8MB Init: systemd runlevel: 5 Gcc sys: 4.9.2
           Client: Shell (bash 4.3.331) inxi: 2.2.18

Any ideas how to fix?

[towo]

Any ideas how to fix?

Use the driver from our repo, fixes or extra/exterimental.


Edit, o i see, you do. I have not tested 346.47 myself, but 349.12 works.
Please provide /var/log/Xorg.0.log

[dibl]

Before you edited, I installed 349.12.  It was not a pretty process, going through the many dependencies that were all looking for 346.47.  However, I deleted and reinstalled them at version 349.12, one at a time, and finally nvidia-driver=349.12-1.siduction.1 and now it runs perfectly.


Thank you towo -- good help as always!