|
I've just built a new PC as follows :
:: Code :: System: Host: siduction Kernel: 3.19.1-towo.1-siduction-amd64 x86_64 (64 bit gcc: 4.9.2)
Desktop: KDE 4.14.2 (Qt 4.8.6) Distro: siduction 14.1.0 Indian Summer - kde - (201411230337) Machine: Mobo: Gigabyte model: Z97X-UD5H v: x.x Bios: American Megatrends v: F7 date: 05/30/2014 CPU: Quad core Intel Core i7-4790 (-HT-MCP-) cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 28811 clock speeds: max: 4000 MHz 1: 3987 MHz 2: 3998 MHz 3: 4000 MHz 4: 3992 MHz 5: 3992 MHz 6: 3981 MHz 7: 3997 MHz 8: 3993 MHz Graphics: Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0 Display Server: X.Org 1.16.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz GLX Renderer: Mesa DRI Intel Haswell Desktop GLX Version: 3.0 Mesa 10.4.2 Direct Rendering: Yes Network: Card-1: Intel Ethernet Connection I217-V driver: e1000e v: 2.3.2-k port: f080 bus-ID: 00:19.0 IF: eth1 state: up speed: 1000 Mbps duplex: full mac: 74:d4:35:ea:b0:d5 Card-2: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller driver: alx port: e000 bus-ID: 02:00.0 IF: eth0 state: down mac: 74:d4:35:ea:b0:d7 Drives: HDD Total Size: 6513.3GB (31.2% used) ID-1: model: Crucial_CT512MX1 ID-2: model: ST2000DM001 ID-3: model: ST2000DM001 ID-4: model: ST2000DM001 Info: Processes: 255 Uptime: 2:30 Memory: 1358.5/15837.5MB Init: systemd runlevel: 5 Gcc sys: 4.9.2 Client: Shell (bash 4.3.331) inxi: 2.2.18 1. I get the script to close desktop environment. When I run smxi I get two errors that there is no etc/inittab 2. When I try and restart the desktop, it falls back to a log in prompt (I am just using the onbord intel graphics so video driver isn't the issue.) :: Code :: systemctl isolate multi-user.targetfollowed by :: Code :: systemctl isolate graphical.targetthen starts the desktop I've tried :: Code :: systemctl isolate multi-user.targetThe only time the desktop starts is if I type 3 on to the linux line at boot then run smxi. Edit : Last few lines of smxi log : :: Code :: Function: start_stop_default_dm - Utility: Start
Args: full start Function: get_default_display_manager - Utility: Start defaultDM: lightdm Function: get_default_display_manager - Utility: End dmanCommand: systemctl start lightdm.service nohup: ignoring input and appending output to 'nohup.out' Back to top |
|||||
|
It's possible systemd has once again changed.
I had to remove the isolate target method from smxi because it leads to many unwanted behaviors, that's why I went back to the basic service start/restart/stop method you note in the last log lines. The inittab is becoming legacy so I'll have to update that test to not assume it's there. Show: inxi -bxxx so I can see what the default level is, and other related system infos. Also paste the /var/log/smxi.log in a paste site and give the url. My guess is that smxi (and sgfxi) is getting the wrong data about what to do and defaults about systemd. Back to top |
|||||
|
smxi log at : www.pastebin.ca/2954578
:: Code :: inxi -bxxx
System: Host: siduction Kernel: 3.19.1-towo.1-siduction-amd64 x86_64 (64 bit gcc: 4.9.2) Desktop: KDE 4.14.2 (Qt 4.8.6) info: plasma-desktop dm: lightdm Distro: siduction 14.1.0 Indian Summer - kde - (201411230337) Machine: Mobo: Gigabyte model: Z97X-UD5H v: x.x Bios: American Megatrends v: F7 date: 05/30/2014 CPU: Quad core Intel Core i7-4790 (-HT-MCP-) speed/max: 3989/4000 MHz Graphics: Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0 chip-ID: 8086:0412 Display Server: X.Org 1.16.4 drivers: intel (unloaded: fbdev,vesa) Resolution: 1920x1080@60.00hz GLX Renderer: Mesa DRI Intel Haswell Desktop GLX Version: 3.0 Mesa 10.4.2 Direct Rendering: Yes Network: Card-1: Intel Ethernet Connection I217-V driver: e1000e v: 2.3.2-k port: f080 bus-ID: 00:19.0 chip-ID: 8086:153b Card-2: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller driver: alx port: e000 bus-ID: 02:00.0 chip-ID: 1969:e091 Drives: HDD Total Size: 6513.3GB (31.2% used) Info: Processes: 253 Uptime: 52 min Memory: 1644.8/15837.5MB Init: systemd v: 215 runlevel: 5 Gcc sys: 4.9.2 alt: 4.4 Client: Shell (bash 4.3.331 running in konsole) inxi: 2.2.18 Back to top |
|||||
|
is /etc/inittab present? To me it looks like it is.
Check, and paste: /etc/inittab Otherwise this is something I don't understand about systemd. As a test, try this: logout of desktop, but do not shut down x. Go to ctrl + alt + F1, login as root, make sure desktop is: ctrl + alt + f6, or f7, the one where you see the login screen. then: systemctl stop lightdm.service see if there are any errors. Go back to desktop, check if it's off or on. crtl +alt + f6, or whichever your desktop was on. If it's on, that would be weird, since systemd shut it down. Back to top |
|||||
|
I've no etc/inittab file
I went through the above and ctrl + alt + f7 starts the desktop (but dod not start from start desktop in smxi) Back to top |
|||||
|
"I went through the above and ctrl + alt + f7"
that's unclear. So F7 is the desktop. And you can go to it from ctrl alt f1, but when you shutdown lightdm, what happens then? ie, starting at the desktop and NOT shutting it down to get out of X: systemctl stop lightdm.service then ctrl alt f7 - does that show a desktop, or just a black space? It should show a black space, or a cursor, since there is nothing running a desktop at this stage. If the desktop still shows, and no error showed on lightdm stop, then we have a true systemd mystery on our hands. Although this won't change anything, I've updated sgfxi/smxi to test explicitly for /etc/inittab, those errors were however not relevant, but they won't appear now. What you have to figure out is what happens when the command smxi/sgfxi issues: systemctl start/stop lightdm.service runs. the only way I can find that out is for you to test it and verify that when stop is issued, with the desktop running, that it stops, and when start is issued, it starts. For example, if are out of x, and x is stopped, and you use that command to start lghtdm, what happens? did x start, but you stayed in console? did x start, and you now are in x? I just ran smxi on my system to do an upgrade and it was all normal, that's with kdm, it stopped kdm, did the upgrade, then started kdm, it was all very boring. Back to top |
|||||
|
:: Quote :: that's unclear. So F7 is the desktop. And you can go to it from ctrl alt f1Yes :: Quote :: systemctl stop lightdm.service
then ctrl alt f7 - does that show a desktop, or just a black space? Just a black space :: Quote :: systemctl start/stop lightdm.service Just tried it and desktop starts with start lightdm.service I'll try another smxi dist-upgrade allowing smxi to shutdown the system to see what happens Back to top |
|||||
|
I've run smxi again and had the same problem. smxi log at www.pastebin.ca/2955242
********************************** I typed ctrl + Alt + F1 logged in as root smxi pressed 1 when I was asked to shutdown the desktop Dist-upgrade Start desktop . . . takes me to black login page Login Stop / Start lightdm.service starts the desktop ************************************** One thing I noticed was that on stopping lightdm, there was a 3-4 second delay before it took me to the root prompt. Is this delay causing the problem? Back to top |
|||||
|
There aren't many more areas I can test, but you can try this.
Do exactly as you did, ctrl alt f1 to console, start smxi, say yes shutdown desktop option, run smxi, then at end, do NOT use smxi to start desktop, but rather exit, and then run this manually: :: Code :: systemctl start lightdm.serviceThis is exactly the command smxi runs on the exit, but there is a small chance that systemd is having an issue with something else smxi does at the end, but this will help narrow it down. if your desktop starts with this command, then there is something very strange going on, if it fails to start, at least we know something at that point. What exactly that is, I can't say, but it will be something. Back to top |
|||||
|
Yes, exiting smxi and start lightdm.service starts the desktop OK
Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||