From: covici@ccs.covici.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: problem which makes gnome unusable
Date: Fri, 06 Nov 2015 21:07:08 -0500 [thread overview]
Message-ID: <15713.1446862028@ccs.covici.com> (raw)
In-Reply-To: <20151106175402.18a1897f@a6>
walt <w41ter@gmail.com> wrote:
> On Fri, 06 Nov 2015 17:26:43 -0500
> covici@ccs.covici.com wrote:
>
> > walt <w41ter@gmail.com> wrote:
> >
> > > On Fri, 06 Nov 2015 14:45:43 -0500
> > > covici@ccs.covici.com wrote:
> > >
> > > > Hi. I am having a very bad problem which makes gnome unusable --
> > > > once I get into the virtual console where the xserver is
> > > > displaying gnome, console 12 in my case, I can never get out of
> > > > that console -- control-alt-f1 or anything does not work. If I
> > > > try to ssh in from somewhere else, I cannot stop gdm because the
> > > > x server will not stop -- even kill -9 will not stop it and I
> > > > have to reboot the system.
> > >
> > > The part about kill -9 failing is exactly the problem I had with the
> > > 3.18.x kernel series a while ago. I know this problem must be
> > > hardware specific because some distros are still shipping 3.18
> > > kernels as the default, and I'll bet others in this mailing list
> > > are using it without problems too. I had some scary problems with
> > > that kernel version that were very difficult to diagnose until I
> > > just rebooted with an older kernel and the scary problems
> > > vanished. The 4.2 series seems okay so far on my VMs. (Even my
> > > gentoo VMs had some minor problems with 3.18.x)
> >
> > I am using 4.1.9 from gentoo sources -- do I need to downgrade maybe
> > the server and nvidia-drivers?
>
> I think downgrading xorg and a video driver sounds more complicated
> than trying a different kernel, but you're in a better position to know
> that than I am. Depends on how many packages you changed just before
> you noticed the problem. If you've been running kernel 4.1.9 for a
> while with no problems, and you just recently upgraded xorg/nvidia,
> then maybe that would be the simpler thing to try.
>
> If you still have some older kernels available, I personally would
> reboot with one of those and see if the nvidia driver will compile with
> that version. (You may need to reinstall/reconfigure the older kernel
> sources if you've already removed them.) A big PITA either way :(
I am running 4.1.9, but there is a 4.1.12 and I may go to that and try
again, but you are correct, its a pita either way. In this last update,
I could not keep the same x server and nvidia drivers I had which worked
fine, due to portage not letting the update go through because of
various slot conflicts -- very annoying.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
covici@ccs.covici.com
next prev parent reply other threads:[~2015-11-07 2:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 19:45 [gentoo-user] problem which makes gnome unusable covici
2015-11-06 21:46 ` [gentoo-user] " walt
2015-11-06 22:26 ` covici
2015-11-07 1:54 ` walt
2015-11-07 2:07 ` covici [this message]
2015-11-07 21:47 ` Fernando Rodriguez
2015-11-07 8:23 ` [gentoo-user] problem which makes gnome unusable partially solved covici
2015-11-07 9:17 ` Neil Bothwick
2015-11-07 13:44 ` covici
2015-11-07 15:32 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15713.1446862028@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox