Page 2 of 5 FirstFirst 1234 ... LastLast
Results 11 to 20 of 41

Thread: After latest update no graphical Interface

  1. #11
    Join Date
    Sep 2012
    Posts
    4,921

    Default Re: After latest update no graphical Interface

    Quote Originally Posted by Fraser_Bell View Post
    ... or, you might try:
    Code:
    zypper in drm-kmp-default
    There is no drm-kmp on TW, this module exists only in Leap 42 due to kernel being too old and module contains backport of DRM from newer kernel. TW has it in default kernel already.

  2. #12

    Default Re: After latest update no graphical Interface

    As I was sleeping some of you were busy trying to help - thank you it is very much appreciated.
    Quote Originally Posted by mrmazda View Post
    "Old" doesn't have the same meaning in every context or to everyone. Please tell us more by using
    Code:
    lspci -nnk | grep VGA
    and/or
    Code:
    inxi -G -c0
    OK when I wrote old it meant that the computer is more than 12 years old. I cannot copy/paste so I just type what I noted down:
    Code:
    lspci -nnk | grep VGA
    Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
    The command inxi is unknown to my computer.

    to report which it is you have. I have multiple installations to "old" Intel gfx systems, and none have required drm-kmp-default as yet. Knowing which you have I might be able to match yours and test it specifically (e.g. 845 or 865).
    I tried yesterday zypper se drm-kmp-default und the computer didn't find any. That confirms what arvidjaar wrote.

    Which DM are you using? SDDM? LightDM? GDM? KDM? XDM?
    Code:
    ps -A | egrep 'X|land'
    should tell which server, if any, is running.
    It used to be SDDM when it was working. Your code didn't give any result and went straight back to the prompt.

  3. #13
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,415

    Default Re: After latest update no graphical Interface

    Quote Originally Posted by fuerstu View Post
    Code:
    lspci -nnk | grep VGA
    Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
    2a42 translates to Cantiga, Gx40/45 and GMA X4500HD. Closest match I have is desktop G41, which is GMA X4500. Its TW I haven't updated for the past 6 weeks so will have to test after I complete a currently running task there.

    AFAIK, your hardware should support 64-bit.
    Code:
    egrep 'model name|sizes' /proc/cpuinfo
    will show whether more than 36 bits are supported, and give the CPU model so you can look up to be sure whether it should or not.

    The command inxi is unknown to my computer.
    Code:
    zypper in inxi
    should fix that.

    It used to be SDDM when it was working. Your code didn't give any result and went straight back to the prompt.
    Please excuse my brain fart. It should have been
    Code:
    ps -A | egrep 'X|land|dm'
    to report which DM and server, if any.

  4. #14

    Default Re: After latest update no graphical Interface

    Thanks mrmazda here are some or the results:
    Quote Originally Posted by mrmazda View Post
    2a42 translates to Cantiga, Gx40/45 and GMA X4500HD. Closest match I have is desktop G41, which is GMA X4500. Its TW I haven't updated for the past 6 weeks so will have to test after I complete a currently running task there.

    AFAIK, your hardware should support 64-bit.
    Code:
    egrep 'model name|sizes' /proc/cpuinfo
    will show whether more than 36 bits are supported, and give the CPU model so you can look up to be sure whether it should or not.
    Unfortunately it is an old 32 bit computer that's why I installed Tumbleweed after version 13.2.
    Code:
    egrep 'model name|sizes' /proc/cpuinfo
    36 bits physical, 48 bits virtual
    Code:
    zypper in inxi
    should fix that.
    Code:
    inxi -G -c0
    Graphics Card: Intel Mobile 4 Series Integrated Graphics Controller
    Display Server: Xorg 1.19.6 drivers: intel (unlaoded: modesetting, fbdev, vesa)
    tty size: 160x50 Advanced Data: N/A for root out of X
    Please excuse my brain fart. It should have been
    Code:
    ps -A | egrep 'X|land|dm'
    to report which DM and server, if any.
    Still no output. But at least there is some result from the inxi command althoug it does not tell me much.

  5. #15

    Default Re: After latest update no graphical Interface

    Just wanted to chime in that my Ivybridge laptop has also been hit by this. Ran all of the commands and get basically the same output (save the model differences). Sometimes I will get the boot infinity symbol and sometimes not. I always end up at a login prompt which quickly flickers once or twice and then allows me to login and type commands, but no GUI. I too am running SDDM with KDE.

  6. #16

    Default Re: After latest update no graphical Interface

    Now I want to ask something to you knowledgeable guys. I just checked the Sysconfig Editor with yast (commandline). There under Desktop when I go down to Displaymanager there is written KDM. When I go to the drop down arrow on the right I can see other displaymanagers but sddm is not included. However on the commandline
    Code:
    update-alternatives --config default-displaymanager
    shows that this is set to auto with the highest number (25). THis number is in front of the line listing sddm. Why is the Sysconfig Editor different to this command output?

  7. #17

    Default Re: After latest update no graphical Interface

    OK - I thought that there is this discrepancy between the command
    Code:
    update-alternatives --config default-displaymanager
    and the Sysconfig Editor. So first I went into /etc/sysconfig/displaymanager and changed the line "Displaymanager=kdm" to "Displaymanager=sddm". After a reboot I pressed the escape key (check if some line does not show the green OK). After the boot I still had the text on the black screen and the cursor was visible too but no GUI. So after a reboot in runlevel 3 I changed in /etc/sysconfig/displaymanager back to "Displaymanager=kdm". THen I used the command
    Code:
    update-alternatives --config default-displaymanager
    to change the displaymanager to kdm. After a reboot I had a different login screen to my normal login but the GUI was up and running. So it was either this conflict of different settings or a problem with sddm. So lakerssuperman - can you try whether this works with your computer too?
    Cheers
    Uli

  8. #18
    Join Date
    Nov 2013
    Location
    Kamloops, BC, Canada
    Posts
    3,976

    Default Re: After latest update no graphical Interface

    Quote Originally Posted by fuerstu View Post
    OK - I thought that there is this discrepancy between the command
    Code:
    update-alternatives --config default-displaymanager
    and the Sysconfig Editor. So first I went into /etc/sysconfig/displaymanager and changed the line "Displaymanager=kdm" to "Displaymanager=sddm". After a reboot I pressed the escape key (check if some line does not show the green OK). After the boot I still had the text on the black screen and the cursor was visible too but no GUI. So after a reboot in runlevel 3 I changed in /etc/sysconfig/displaymanager back to "Displaymanager=kdm". THen I used the command
    Code:
    update-alternatives --config default-displaymanager
    to change the displaymanager to kdm. After a reboot I had a different login screen to my normal login but the GUI was up and running. So it was either this conflict of different settings or a problem with sddm. So lakerssuperman - can you try whether this works with your computer too?
    Cheers
    Uli
    Yes, this is correct.

    In TW and 15.0 Beta, the Display Manager that is used is no longer set in /etc/sysconfig/displaymanager, but instead with update-alternatives. Not sure where the config is kept.

    Yet, the other DM settings you see in the /etc/sysconfig editor under the displaymanager branch are still set there.

    Why it is now separated from the rest of the Display Manager settings, instead of all together as it has been in the past, is beyond me at the moment. But, it is inconvenient, and -- as you found out -- unknown by most users, who wind up baffled that it suddenly doesn't work as before.

    Someone who has been following that might jump in here and explain the reasoning. I am curious about this, as well, as you can see.

    Instead of kdm, though, you might try XDM, as KDM is out of support for a long time, now. If that does not work, try LightDM.
    -Gerry Makaro
    Fraser-Bell Info Tech
    Solving Tech Mysteries since the Olden Days!
    ~~
    If I helped you, consider clicking the Star at the bottom left of my post.

  9. #19

    Default Re: After latest update no graphical Interface

    No go for me I'm afraid, but glad you got something working for you. I had already tried switching SDDM to LightDM and XDM. No go. Running systemctl status for SDDM it says that it is active, but throwing and error about the splash screen. My laptop is away for the night, but I'll post the exact error tomorrow.

  10. #20
    Join Date
    Dec 2008
    Location
    FL, USA
    Posts
    1,415

    Default Re: After latest update no graphical Interface

    Quote Originally Posted by Fraser_Bell View Post
    In TW and 15.0 Beta, the Display Manager that is used is no longer set in /etc/sysconfig/displaymanager, but instead with update-alternatives. Not sure where the config is kept.
    Location:
    Code:
    /etc/alternatives/default-displaymanager
    which is a symlink to the appropriate file in
    Code:
    /usr/lib/X11/displaymanagers/
    Thus, replacing an existing link with another to change DM is possible via cmdline or script, not just using YaST; not as convenient for cmdline users as /etc/sysconfig, but I think this has been becoming a cross-distro convention.

Page 2 of 5 FirstFirst 1234 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •