Author Topic: Green Screen/Kernel Panic after first login  (Read 2285 times)

0 Members and 1 Guest are viewing this topic.

Offline gohlip

  • Held Mitglied
  • *****
  • Posts: 1689
  • Desktop: OpenBox
  • GPU Card: nvidia
  • GPU driver: nonfree
  • Kernel: linux46 - x64
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #15 on: 05. January 2016, 20:29:58 »
Not sleeping yet, maybe I'll watch the morning sunrise.  :)
So "systemctl status display-manager" gives anything?
Now I am not sure if you should do "sudo systemctl enable lightdm"
or "sudo systemctl enable lightdm-plymouth" (needs reboot for both)
Also, confusingly, you need to disable one of them.
[that's a bad thingy about manjaro needing this 'splice' for plymouth dm's - sddm don't need this thing now]
But always remove 'splash' and 'quiet' for the time being - makes things easier.

But check first if they are installed in the first place.
Code: [Select]
pacman -Q lightdm
[edit] - I'll just disable lightdm-plymouth
Code: [Select]
sudo systemctl disable lightdm-plymouth
sudo systemctl enable lightdm
there might be an error when disabling lightdm-plymouth, but its\'s ok. Good in fact.
Repeat, remove 'quiet and splash when booting.


« Last Edit: 05. January 2016, 20:41:48 by gohlip »
Life is a sexually transmitted disease with a 100% mortality rate.

Offline Fred Barclay

  • Neuling
  • *
  • Posts: 23
  • Branch: Testing
  • Desktop: Xfce
  • GPU Card: Intel 82915G/GV/910GL Integrated
  • GPU driver: free
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #16 on: 05. January 2016, 21:04:03 »
Sorry I'm a tad late--the forums logged me out so I'm retyping this:

In my last post, I should have specified that the output was from "systemctl status lightdm." Just to be safe, I'll repost it here:
Code: [Select]
sudo systemctl status lightdm
● lightdm.service - Light Display Manager
   Loaded: error (Reason: File exists)
   Active: inactive (dead)
     Docs: man:lightdm(1)

Jan 06 06:08:07 platypus systemd[1]: lightdm.service: Two services allocated for the same bus name org.freedesktop.DisplayManager, refusing operation.
Jan 06 06:10:20 platypus systemd[1]: lightdm.service: Two services allocated for the same bus name org.freedesktop.DisplayManager, refusing operation.
Jan 06 06:11:53 platypus systemd[1]: lightdm.service: Two services allocated for the same bus name org.freedesktop.DisplayManager, refusing operation.

Now with lightdm-plymouth disabled and lightdm (re?)enabled, the output is different:
Code: [Select]
sudo systemctl status lightdm
● lightdm.service - Light Display Manager
   Loaded: loaded (/usr/lib/systemd/system/lightdm.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Wed 2016-01-06 06:54:56 AEDT; 2min 49s ago
     Docs: man:lightdm(1)
  Process: 569 ExecStart=/usr/bin/lightdm (code=exited, status=1/FAILURE)
 Main PID: 569 (code=exited, status=1/FAILURE)

Jan 06 06:54:56 platypus systemd[1]: lightdm.service: Unit entered failed state.
Jan 06 06:54:56 platypus systemd[1]: lightdm.service: Failed with result 'exit-code'.
Jan 06 06:54:56 platypus systemd[1]: lightdm.service: Service hold-off time over, scheduling restart.
Jan 06 06:54:56 platypus systemd[1]: Stopped Light Display Manager.
Jan 06 06:54:56 platypus systemd[1]: lightdm.service: Start request repeated too quickly.
Jan 06 06:54:56 platypus systemd[1]: Failed to start Light Display Manager.
Jan 06 06:54:56 platypus systemd[1]: lightdm.service: Unit entered failed state.
Jan 06 06:54:56 platypus systemd[1]: lightdm.service: Failed with result 'start-limit'.

This is with quiet splash disabled, btw.

I tried disabling lightdm and enabling lightdm-plymouth. No change occured, so I'm back to lightdm enabled and lightdm-plymouth disabled.

Lightdm is installed as per "pacman -Q lightdm"

Thanks!

EDIT: I'm going to take a peek at my lightdm.conf file. Maybe there's something there?
« Last Edit: 05. January 2016, 21:33:13 by Fred Barclay »

Offline Fred Barclay

  • Neuling
  • *
  • Posts: 23
  • Branch: Testing
  • Desktop: Xfce
  • GPU Card: Intel 82915G/GV/910GL Integrated
  • GPU driver: free
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #17 on: 06. January 2016, 03:29:53 »
An update on what I've done so far:

I tried removing and reinstalling plymouth to see if that would help. One of the dependencies, plymouth-theme-manjaro-elegant, I did not reinstall*, so
Code: [Select]
sudo pacman -Rns plymouth plymouth-theme-manjaro-elegant
sudo pacman -S plymouth
Plymouth gave some interesting output upon reinstallation:
Code: [Select]
fred@aussie! /mnt/home/fred $ cat plymouth.txt
resolving dependencies...
looking for conflicting packages...

Packages (1) plymouth-1:0.8.8-1

Total Installed Size:  1.59 MiB
Net Upgrade Size:      0.00 MiB

checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
reinstalling plymouth...

==================================================================================
1. To make Plymouth work:
     1.1. Add "plymouth" to HOOKS after "base" and "udev" in /etc/mkinitcpio.conf
     1.2. Add 'quiet splash' to the grub command line in /etc/default/grub
     1.3. Rebuild your initrd image (# mkinitcpio -p [kernel preset name]).
          E.g.: sudo mkinitcpio -p linux38

2. To enable encryption, replace "encrypt" with "plymouth-encrypt" in
   mkinitcpio.conf and rebuild your initrd image.

3. You will also need to rebuild your initrd image every time you change your theme
   (the default is set as 'spinfinity').

   To list all plymouth themes:
       plymouth-set-default-theme -l

   To change theme:
       # plymouth-set-default-theme <theme>

   To rebuild initrd image:
       # mkinitcpio -p <kernel present name>

4. For Smooth Transition to Display Manager you have to:
     4.1. See the Wiki Page (link in 5) to prepare your Display Manager
     4.2. Disable your Display Manager Unit
          E.g. : systemctl disable kdm.service
     4.3. Enable the respective DM-plymouth Unit (GDM,KDM,Lightdm,LXDM units provided)
          E.g. : systemctl enable kdm-plymouth.service

5. For more information please visit the Wiki page:
   https://wiki.archlinux.org/index.php/Plymouth

OBS. If you have any leftover "kill Plymouth" lines in /etc/rc.local or ~/.xinitrc
     they are no longer required.
==================================================================================
So, following directions like a good Archer--I mean Manjar... Manjarorer? :o --I checked the hooks. All good. I rebuilt the initrd image, though I took the lazy method of "mkinitcpio -P". I didn't worry about encryption or themes, though I did read the wiki, disabled lightdm.service, and enabled lightdm-plymouth.service. I also used "quiet splash" in the boot arguments.

The wiki entry was very interesting. Apparently Plymouth 0.9.2-5 has been known to cause problems with LightDM. However, I can't tell what version of Plymouth I'm on. If I look at the reinstallation output, it would appear to be 0.8.8-1. Surely that can't be right? I know there's a delay in Arch packages trickling downstream to Manjaro, but surely not that much of a difference?
Besides, I've used lightdm and plymouth splash screens before--though I don't recall if that was on this machine or not.

With all that said, there hasn't been a change in my situation. I still get a blank screen where lightdm should be--besides a small blinking cursor in the upper-left corner--but switching to console is no trouble.
I'm wondering if this is only a symptom of the "failure to load kernel modules" reported earlier. ??? Maybe more is going on that I'm not aware of.

Anyhow, I'll be signing off in a bit, but I wanted to give the update. Thanks for your help so far!

*So far as I could tell, all it did was make the splash screen more elegant, so I didn't bother about installing it. I actually like the splash screen better without it. :)

Offline gohlip

  • Held Mitglied
  • *****
  • Posts: 1689
  • Desktop: OpenBox
  • GPU Card: nvidia
  • GPU driver: nonfree
  • Kernel: linux46 - x64
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #18 on: 06. January 2016, 05:40:51 »
Fred, now here the point I have to say, "I don't know".
I don't use much lightdm, I have lxqt, fluxbox and i3 (besides my regulars, kde and openbox). I don't use gnome, mate, cinnamon, xfce..etc (tested maybe).
Only i3 (early edition) uses lightdm and I don't have any issue with it.
But recalling some posts in this forum, it may have something to do with lightdm-greeter (lightdm-gtk-greeter?) or their conf files.
I am definitely not good enough in this lightdm area to give any meaningful suggestion.

There may be other causes of course, but I can't think of anything else that could be it.
As far as I know, your graphics is settled and is usually the main cause of such problem.

Sorry then Fred, I have to say "Take it easy" at this point (unless something hits me).  :D
Oh, I didn't do much but your thanks is warmly accepted. Fair dingkums. G'day.
Life is a sexually transmitted disease with a 100% mortality rate.

Offline Fred Barclay

  • Neuling
  • *
  • Posts: 23
  • Branch: Testing
  • Desktop: Xfce
  • GPU Card: Intel 82915G/GV/910GL Integrated
  • GPU driver: free
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #19 on: 06. January 2016, 13:50:29 »
No worries, mate. At least I'm further ahead than I was two days ago. :)
See you around.

Offline Fred Barclay

  • Neuling
  • *
  • Posts: 23
  • Branch: Testing
  • Desktop: Xfce
  • GPU Card: Intel 82915G/GV/910GL Integrated
  • GPU driver: free
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #20 on: 07. January 2016, 17:18:45 »
gohlip: out of curiosity, what do you use for logging in? Another display manager? .xinitrc?

Right now I'm examining the unloaded modules that systemd warned of, but if nothing comes of that I might try a different display manager.

Offline gohlip

  • Held Mitglied
  • *****
  • Posts: 1689
  • Desktop: OpenBox
  • GPU Card: nvidia
  • GPU driver: nonfree
  • Kernel: linux46 - x64
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #21 on: 07. January 2016, 17:39:13 »
Not sure what you mean, but my display manager is usually sddm.
It is in all my kde, plasma and openbox (from net install, so I manually install sddm).
There is no sddm-plymouth.service in any of them even though kde and plasma uses plymouth (it works).
My lxqt is also sddm, my (old) fluxbox uses slim, only i3 uses lightdm (no plymouth), but has lightdm-gtk-greeter and lightdm-gtk-settings installed.
As I said, I don't know much about these "greeter" thingies (no such thing in sddm) and not sure if these causes problems for you.

Again, I am not sure about .xinitrc, some uses .xsession, most simple de's uses autostart too.
Still unsure where these 'unloaded modules' come about in your case.
Hope I answered what you're looking for. I really don't know if I did.

ps: can someone else good in lightdm help out Fred, please.
Or know these 'unloaded modules' in systemd come about?

« Last Edit: 07. January 2016, 17:41:57 by gohlip »
Life is a sexually transmitted disease with a 100% mortality rate.

Offline Fred Barclay

  • Neuling
  • *
  • Posts: 23
  • Branch: Testing
  • Desktop: Xfce
  • GPU Card: Intel 82915G/GV/910GL Integrated
  • GPU driver: free
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #22 on: 07. January 2016, 18:52:54 »
That was actually exactly what I was asking. :) If I can't track down the module stuff I might try a different DM.

With me being new here, I'm not quite sure what the accepted standards are. Since I am no longer experiencing kernel panics should I start a new thread for the non-loading modules? Or should I just keep using this one?

EDIT: found one non-loading module!
Code: [Select]
sudo /usr/lib/systemd/systemd-modules-load
Failed to insert 'fglrx': No such device
:(
« Last Edit: 07. January 2016, 19:01:01 by Fred Barclay »

Offline gohlip

  • Held Mitglied
  • *****
  • Posts: 1689
  • Desktop: OpenBox
  • GPU Card: nvidia
  • GPU driver: nonfree
  • Kernel: linux46 - x64
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #23 on: 07. January 2016, 19:41:48 »

Ah... still graphics some loose ends not settled (modules or mhwd)
then
Code: [Select]
sudo mhwd-gpu --setgl <what's installed>like say, 'sudo mhwd-gpu --setgl nvidia'
Reboot normally.
So did you do
Code: [Select]
sudo mhwd-gpu --setgl ati


Also, this may be useful to you.
https://wiki.archlinux.org/index.php/ATI#Artifacts_upon_logging_in

Always good to come up with a new topic when it 'moved' to another issue.
But you may not find me there because I'm no good in these.
Good luck again, Fred

Life is a sexually transmitted disease with a 100% mortality rate.

Offline mngc

  • Neuling
  • *
  • Posts: 1
  • I'm new. Be nice!
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #24 on: 15. March 2016, 13:50:28 »
Hi,

I have near same problem. Any 3.x kernel working ok, stable all time. For example: 3.19.8.15-1-MANJARO, all 4.x kernel bad, but sometimes booted ok. The problem: when booting, Manjaro label and 5 pc green white dots displayed ok, next burning this labels to white, next slowly brighten all pixels on screen, on display near all pixels white. System freezed.

01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS690M [Radeon Xpress 1200/1250/1270]

Any idea?
Thanks

Offline Fred Barclay

  • Neuling
  • *
  • Posts: 23
  • Branch: Testing
  • Desktop: Xfce
  • GPU Card: Intel 82915G/GV/910GL Integrated
  • GPU driver: free
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #25 on: 02. April 2016, 23:41:49 »
It appears we have the exact same graphic card!
I recently found that this occurs with Arch as well too, so I'm going to start a support request there in a few days. After all, this doesn't appear to be Manjaro's fault. ;)

For now, I'd recommend another Linux distro (unless someone else here knows how to fix this) such as Linux Mint, which performs beautifully on my machine, but I'll definitely post back if the Arch guys can help. :)

Cheers!
Fred

Offline eugen-b

  • Support Team
  • ****
  • Posts: 3191
  • Branch: testing
  • Desktop: LXDE, Fluxbox, JWM, LXQt, bspwm
  • GPU Card: Intel 82945G/GZ
  • GPU driver: free
  • Kernel: 4.5, 4.6
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #26 on: 02. April 2016, 23:48:38 »
You may try to find out which Xorg version and video-ati version do the distros have which work on your machine.
My advise apart from Mint would be s.th. based on Debian Jessie.
MSI Wind Nettop, Intel Atom 230 1.6GHz (64bit), 2GB RAM
DEs: NET-minimal + (LXDE / Fluxbox / JWM); LXQt OpenRC
how to install on btrfs subvolumes
http://manjaro.github.io/donate/

Offline Fred Barclay

  • Neuling
  • *
  • Posts: 23
  • Branch: Testing
  • Desktop: Xfce
  • GPU Card: Intel 82915G/GV/910GL Integrated
  • GPU driver: free
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #27 on: 02. April 2016, 23:51:10 »
My advise apart from Mint would be s.th. based on Debian Jessie.
Like LMDE Betsy! :lol:

Sorry, couldn't resist...

Offline eugen-b

  • Support Team
  • ****
  • Posts: 3191
  • Branch: testing
  • Desktop: LXDE, Fluxbox, JWM, LXQt, bspwm
  • GPU Card: Intel 82945G/GZ
  • GPU driver: free
  • Kernel: 4.5, 4.6
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #28 on: 03. April 2016, 00:13:34 »
Not a bad idea actually. This way you could find out is it the Mint "voodoo" or just the Xorg and the ati driver by comparing it to plain Debian.
MSI Wind Nettop, Intel Atom 230 1.6GHz (64bit), 2GB RAM
DEs: NET-minimal + (LXDE / Fluxbox / JWM); LXQt OpenRC
how to install on btrfs subvolumes
http://manjaro.github.io/donate/

Offline Fred Barclay

  • Neuling
  • *
  • Posts: 23
  • Branch: Testing
  • Desktop: Xfce
  • GPU Card: Intel 82915G/GV/910GL Integrated
  • GPU driver: free
  • Skill: Intermediate
Re: Green Screen/Kernel Panic after first login
« Reply #29 on: 13. May 2016, 20:49:46 »
It's still being worked on but there is a thread on the Arch forums about this: https://bbs.archlinux.org/viewtopic.php?id=211873