X server on lenny - broken after today's dist-upgrade
David Fox
now, enough to press alt-f2 to run iceweasel. I've basically lost the
ability to start x into my normal KDE environment. I get some errors
on the controlling terminal - these error messages are strange to me.
startkde never gets to start; I get a blue screen with a mouse cursor,
and nothing more.
In desperation, I tried geting X back by doing a basic reinstall of
the xserver-xorg package but in turn seemingly lost nvidia - and now I
cannot install nvidia-glx. I had it running (from sid) up until now.
Most if not everything xserver-xorg is running from sid rather than
from lenny because at the time lenny did not have nvidia-kernel-source
or the proper revision of nvidia-glx.
When I attempt to install nvidia-glx I get unresolved dependencies
wanting nvidia-kernel-100.14.19, saying this is a virtual package. But
I want nvidia-kernel-source and nvidia-kernel-common, right?
I have those two packages installed from sid's repository but still
can't get nvidia-glx (re)installed.
Also this setup as it is is difficult to get a cut/paste or a script
of the error(s) I get when I try and startx with my normal kde
install. But I remember errors along the line of bad font path element
- and unfortunately, nothing in /var/log/Xfree86 seems to be there
detailing these errors.
I'll probably follow up to this message in a little bit.
Meanwhile, X is at least *somewhat* usable but this partial xfce
environment I have (no taskbars, no panel, nothing but a gray screen
and alt-f2 to run an app) isn't wanting to be tried that much longer.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ron Johnson
Hash: SHA1
This might not help you much, but I just upgraded Sid this afternoon
and (using startx) GNOME and my self-installed nvidia 100.14.19
driver work fine.
- --
Ron Johnson, Jr.
Jefferson LA USA
%SYSTEM-F-FISH, my hovercraft is full of eels
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHP7/FS9HxQb37XmcRAgTHAKDFFRF6ikNNYy/5FlII/Gf3ufSZlACgyNXU
YAqdF/Mj5Usjwx7Y4N+f/Xo=
=q9jL
-----END PGP SIGNATURE-----
David Fox
> I am having a problem and I've only got a minimal xfce4 setup right
> now, enough to press alt-f2 to run iceweasel. I've basically lost the
> ability to start x into my normal KDE environment. I get some errors
> on the controlling terminal - these error messages are strange to me.
> startkde never gets to start; I get a blue screen with a mouse cursor,
> and nothing more.
Update:
Still having issues, but managed to figure out how to correctly start
xfce4. It is almost usable, but slow, because of the nv fallback
driver.
I sent by mistake only the startx errors to another thread entitled
"followup to my last message". Sorry if that breaks continuity. I can
attach it to this message so as to not break the thread.
As I said before, the startkde never gets a chance to start, but at
least X is working - sort of.
I want to of course figure out what those extra errors are coming from
and how to fix it. The dist-upgrade doesn't seem to have helped this
situation - did a dist-upgrade this AM on lenny and everything was
fine, and suddenly I was trying to look at a document in openoffice
and the whole X session just hung, and I had to ctrl-alt-backspace.
After that, I can't get my display back the way it was.
Charlie
>--} On 11/17/07, David Fox <dfox...@gmail.com> wrote:
>--} > I am having a problem and I've only got a minimal xfce4 setup right
>--} > now, enough to press alt-f2 to run iceweasel. I've basically lost the
>--} > ability to start x into my normal KDE environment. I get some errors
>--} > on the controlling terminal - these error messages are strange to me.
>--} > startkde never gets to start; I get a blue screen with a mouse cursor,
>--} > and nothing more.
>--}
>--} Update:
>--}
>--} Still having issues, but managed to figure out how to correctly start
>--} xfce4. It is almost usable, but slow, because of the nv fallback
>--} driver.
>--}
>--} I sent by mistake only the startx errors to another thread entitled
>--} "followup to my last message". Sorry if that breaks continuity. I can
>--} attach it to this message so as to not break the thread.
>--}
>--} As I said before, the startkde never gets a chance to start, but at
>--} least X is working - sort of.
>--}
>--} I want to of course figure out what those extra errors are coming from
>--} and how to fix it. The dist-upgrade doesn't seem to have helped this
>--} situation - did a dist-upgrade this AM on lenny and everything was
>--} fine, and suddenly I was trying to look at a document in openoffice
>--} and the whole X session just hung, and I had to ctrl-alt-backspace.
>--} After that, I can't get my display back the way it was.
>--}
I thought I must be the only one that had this problem after the last upgrade.
Running Lenny as well. The same symptoms, just a blank screen with a working
cursor, and Gkrellm which loads before anything else GUI. But that locked up
after a second. Nothing in KDE showed up. So I dropped to a terminal and all
works there, something to do with the xserver? Maybe? I couldn't catch
anything in the logs either.
I wanted to make some changes to my partition table and reinstall anyway, but
I removed Kerry-Beagle first and autoremoved all the files as directed
through apt-get. Then installed icewm, and things worked a treat, so I
thought this could be something to do with KDE. So installed Kerry-Beagle
again, bad move, it happened the same in Icewm, a blank screen. I now new
there was something about Kerry-Beagle that was the problem. Same again with
just beagle.
I can't recall the exact name but they were libmono or something like that
files, a whole heap of them and a couple of others. I removed them all, and I
think they were mainly for Kerry Beagle.
So did the reinstall, fixed the partitions the way I wanted and installed
normally, but nothing kerry-beagle went in, but did install KDE. Same problem
again? Having deleted and resized and relocated and formatted /home, as well
as all the other partitions, there was nothing there that could have been
left from the old system. So I ripped out everything KDE, and used icewm, and
put back all the programs and apps other than kerry-beagle and all is working
a treat.
I thought it might be hardware when no one else posted about it. I like KDE
but don't have to have it.
If you don't know and don't remove all the upgraded files, then the desktop
manager won't work right. But I am not certain that's the same as my system.
I had the CPU load meter at the top of every window where the minimize,
maximise and shutdown buttons were in icewm. They worked the same as normal
though. Even after getting rid of all the files I remembered out of the
system and kerry beagle it didn't come back with a hard boot. Even using just
beagle, broke everything and i went through the removal procedure again.
It's probably no help at all, but that's my experience.
All working well with everything as before except KDE and kerry-beagle.
Be well,
Charlie
--
Registered Linux User:- 329524
+++++++++++++++++++++++++++++++++++
The lesson which life repeats and constantly enforces is "look under foot."
Every place is under the stars, every place is the center of the
world. ................John Burroughs
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Debian - Just the best way to do magic.
Florian Kulzer
> I am having a problem and I've only got a minimal xfce4 setup right
> now, enough to press alt-f2 to run iceweasel. I've basically lost the
> ability to start x into my normal KDE environment. I get some errors
> on the controlling terminal - these error messages are strange to me.
> startkde never gets to start; I get a blue screen with a mouse cursor,
> and nothing more.
>
> In desperation, I tried geting X back by doing a basic reinstall of
> the xserver-xorg package but in turn seemingly lost nvidia - and now I
> cannot install nvidia-glx. I had it running (from sid) up until now.
> Most if not everything xserver-xorg is running from sid rather than
> from lenny because at the time lenny did not have nvidia-kernel-source
> or the proper revision of nvidia-glx.
>
> When I attempt to install nvidia-glx I get unresolved dependencies
> wanting nvidia-kernel-100.14.19, saying this is a virtual package. But
> I want nvidia-kernel-source and nvidia-kernel-common, right?
Yes, and then you need to auto-install the nvidia kernel module with
module assistant. This will generate and install a .deb file which
provides "nvidia-kernel-100.14.19". Afterwards it should be possible to
install the nvidia-glx package.
> I have those two packages installed from sid's repository but still
> can't get nvidia-glx (re)installed.
>
> Also this setup as it is is difficult to get a cut/paste or a script
> of the error(s) I get when I try and startx with my normal kde
> install. But I remember errors along the line of bad font path element
> - and unfortunately, nothing in /var/log/Xfree86 seems to be there
> detailing these errors.
The relevant file is /var/log/Xorg.0.log. (The Xfree86 file only
contains stale leftovers from your pre-Etch days.)
> I'll probably follow up to this message in a little bit.
I saw your other mail, but the startup messages do not provide anything
that is useful, therefore I continue the thread here.
> Meanwhile, X is at least *somewhat* usable but this partial xfce
> environment I have (no taskbars, no panel, nothing but a gray screen
> and alt-f2 to run an app) isn't wanting to be tried that much longer.
My guess is that there is a problem with GLX; nvidia-glx and
xserver-xorg-core tend to play tug-of-war with libglx.so in
/usr/lib/xorg/modules/extensions/. The Debian nvidia packages use
dpkg-divert to avoid this, but an unclean deinstallation of the nvidia
packages can lead to lingering problems with the normal libglx from
Xorg. ("I seemingly lost nvidia" sounds like this might have happened to
you.)
At the moment it seems to me that you have a fair chance of getting the
nvidia driver to work again if you rebuild the kernel module with
module-assistant and reinstall nvidia-glx. That is what I would try
first.
If that does not work then I would purge all nvidia packages ("remove"
is not enough), reinstall xserver-xorg-core and set xorg.conf to use the
"nv" driver. If this does not give you a fully functional Xorg and KDE
(except for 3D acceleration, of course) then you should run
egrep '^\((EE|WW)\)' /var/log/Xorg.0.log > errors.txt
and send errors.txt to the list. (Please try to convince Gmail to attach
the file as "text/plain" and not as an "application/octet-stream" in
base64 encoding.)
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
David Fox
> Yes, and then you need to auto-install the nvidia kernel module with
> module assistant. This will generate and install a .deb file which
> provides "nvidia-kernel-100.14.19". Afterwards it should be possible to
> install the nvidia-glx package.
Aha. I ddn't have that missing step. module-assistant simply
reinstalled the .deb I already had, which was living in /usr/src.
> I saw your other mail, but the startup messages do not provide anything
> that is useful, therefore I continue the thread here.
I was really wondering about those 'bad path' messages in the start
up, and not being able to get startkde to run. I understand not having
''cyrillic' and that's OK since I don't do Russian, and just having
that font path get deleted on startup is fine by me. It was those
other errors "expecting keysym" lines also that are throwing me for a
loop.
Meanwhile, I've since restarted X with the nvidia driver, and all is
fine at least running xfce4 - I remembered of course to save my
original tweaked xorg.conf to a different name while I was trying to
figure it out.
Paul Cartwright
> Meanwhile, I've since restarted X with the nvidia driver, and all is
> fine at least running xfce4 - I remembered of course to save my
> original tweaked xorg.conf to a different name while I was trying to
> figure it out.
well, it bit me today. I had to reboot, I thought I had a mail issue. When I
rebooted, all I got was the console login, no X..
changed xorg.conf to nv from nvidia, and at least I am back in X..
runny lenny ~$ uname -r
2.6.22-2-686
--
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459
Paul Cartwright
> Yes, and then you need to auto-install the nvidia kernel module with
> module assistant. This will generate and install a .deb file which
> provides "nvidia-kernel-100.14.19". Afterwards it should be possible to
> install the nvidia-glx package.
could you explain this a little more??
I am running 2.6.22-2-686 and have an NVIDIA graphics card
nVidia Corporation G72 [GeForce 7300 LE]"
--
Paul Cartwright
Registered Linux user # 367800
Registered Ubuntu User #12459
Florian Kulzer
> On Sun November 18 2007, Florian Kulzer wrote:
> > Yes, and then you need to auto-install the nvidia kernel module with
> > module assistant. This will generate and install a .deb file which
> > provides "nvidia-kernel-100.14.19". Afterwards it should be possible to
> > install the nvidia-glx package.
>
> could you explain this a little more??
> I am running 2.6.22-2-686 and have an NVIDIA graphics card
> nVidia Corporation G72 [GeForce 7300 LE]"
Provided you have unstable/non-free in your sources.list, it should work
like this:
- Install the "module-assistant" package.
- Run "m-a update" and "m-a prepare" as root.
- Then you can try to build and install the module like this:
m-a a-i nvidia-kernel-source
(Users of older cards will need nvidia-kernel-legacy-96xx-source or
nvidia-kernel-legacy-71xx-source instead.)
- If you are successful in the previous steps then it should be possible
to install the nvidia-glx package from unstable.
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Paul Cartwright
> > could you explain this a little more??
> > I am running 2.6.22-2-686 and have an NVIDIA graphics card
> > nVidia Corporation G72 [GeForce 7300 LE]"
>
> Provided you have unstable/non-free in your sources.list, it should work
> like this:
>
> - Install the "module-assistant" package.
>
> - Run "m-a update" and "m-a prepare" as root.
>
> - Then you can try to build and install the module like this:
>
> m-a a-i nvidia-kernel-source
>
> (Users of older cards will need nvidia-kernel-legacy-96xx-source or
> nvidia-kernel-legacy-71xx-source instead.)
>
> - If you are successful in the previous steps then it should be possible
> to install the nvidia-glx package from unstable.
that worked, thanks.
I was also able to get the NVIDIA driver working, using the beta driver,
NVIDIA-Linux-x86-169.04-pkg1.run