This is a discussion on Cant't get into win manager from kdm/xdm within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> I have just upgraded from slack 9.0 to 9.1. Everything was fine on one machine but on another I ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I have just upgraded from slack 9.0 to 9.1. Everything was fine on one machine but on another I can't get into KDE, TWM etc from kdm or xdm. There are no errors reported in ~/.xsession-errors, but in /var/log/kdm.log I get the following (see below): I have one of the latest NVIDIA drivers installed (NVIDIA-Linux-x86-1.0-4496-pkg2.run). I can get into kde etc using "startx". Can anybody unravel this one? /var/log/kdm.log below: (II) [GLX]: Initializing GLX extension XFree86 Version 4.3.0 Release Date: 27 February 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.4.22 i686 [ELF] Build Date: 16 September 2003 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Sat Oct 11 10:43:29 2003 (==) Using config file: "/etc/X11/XF86Config" Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! Symbol __glXActiveScreens from module /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! (II) [GLX]: Initializing GLX extension (II) [GLX]: Initializing GLX extension (II) [GLX]: Initializing GLX extension |
| |||
| In news:fac9158b.0310101705.7d1c6888@posting.google.c om, Robert <send_to_me@areujoking.com> rambled: > I have just upgraded from slack 9.0 to 9.1. Everything was fine on > one machine but on another I can't get into KDE, TWM etc from kdm or > xdm. There are no errors reported in ~/.xsession-errors, but in > /var/log/kdm.log I get the following (see below): > > I have one of the latest NVIDIA drivers installed > (NVIDIA-Linux-x86-1.0-4496-pkg2.run). > > I can get into kde etc using "startx". > > Can anybody unravel this one? > You haven't followed the installation instructions for the Nvid drivers. Check the bit on editing your xf86config file. Billy |
| |||
| -----------------------------8><---------------------------------------- > > I have just upgraded from slack 9.0 to 9.1. Everything was fine on > > one machine but on another I can't get into KDE, TWM etc from kdm or > > xdm. There are no errors reported in ~/.xsession-errors, but in > > /var/log/kdm.log I get the following (see below): > You haven't followed the installation instructions for the Nvid drivers. > > Check the bit on editing your xf86config file. > > Billy Thanks. I've removed the load "glx" from my XF86Config. Still no luck. I AM able to get into kde etc by using the startx command - I therefore assume that X is working OK. I note that /usr/X11R6/bin isn't in my PATH when I'm in kde - I wonder if some file(s) aren't being found. Where is the best place to add /usr/X11R6/bin to my path in this setting? - which script? Robert. |
| |||
| In news:fac9158b.0310110516.666b3238@posting.google.c om, Robert <send_to_me@areujoking.com> rambled: >>> I have just upgraded from slack 9.0 to 9.1. Everything was fine on >>> one machine but on another I can't get into KDE, TWM etc from kdm or >>> xdm. There are no errors reported in ~/.xsession-errors, but in >>> /var/log/kdm.log I get the following (see below): >> You haven't followed the installation instructions for the Nvid >> drivers. >> >> Check the bit on editing your xf86config file. >> > > Thanks. I've removed the load "glx" from my XF86Config. Still no > luck. > > Did you remove the bit about dri as well ? Billy |
| |||
| "Billy Watt" <newsspam@cjwatt.plus.net> wrote in message news:<jsWhb.7244$kA.2043285@wards.force9.net>... > In news:fac9158b.0310110516.666b3238@posting.google.c om, > Robert <send_to_me@areujoking.com> rambled: > > >>> I have just upgraded from slack 9.0 to 9.1. Everything was fine on > >>> one machine but on another I can't get into KDE, TWM etc from kdm or > >>> xdm. There are no errors reported in ~/.xsession-errors, but in > >>> /var/log/kdm.log I get the following (see below): > >> You haven't followed the installation instructions for the Nvid > >> drivers. > >> > >> Check the bit on editing your xf86config file. > >> > > > > Thanks. I've removed the load "glx" from my XF86Config. Still no > > luck. > > > > > > Did you remove the bit about dri as well ? > > Billy Yes - its well gone. I think its a problem with my environment or path or something like that. I AM able to get X up and running with no problems. Robert. |
| |||
| On Sat, 11 Oct 2003 17:33:46 -0700, Robert wrote: <snippage>>> > >> >> Did you remove the bit about dri as well ? >> >> Billy > > Yes - its well gone. I think its a problem with my environment or > path or something like that. I AM able to get X up and running with > no problems. > > Robert. Hello Robert I agree with you that your /etc/X11/XF86Config file must be basically OK as long as "startx" or "startkde" ( or any other direct call for a WM ) successfully loads an xserver. Like you, I prefer to boot to console and then call "kdm" to susbsequently load or switch WMs. It is superior to gdm and xdm in a few ways that matter to me. However, as I understand it, kdm is not merely a login manager, it is like the others also a display manager, and both gdm and kdm depend on xdm. While you can edit kdm to some extent graphically in KDE's Control Center, still you must pay attention to xdm and XSession. Look in /etc/X11/xdm/XSession where you will see the list of loadable WMs and path statements as well as some useful comments. You may solve your problem right there but if not calling for the xdm and kdm manpages should take you the rest of the way. As for adding to your path statement, it follows normal programming protocols in that if you type "$PATH" in a terminal the path env variables for that user will be shown. If you need to add you simply "export" the location description you require ie "/usr/X11R6/bin" . Hope this helps Jimmy |
| ||||
| On 2003-10-11, Robert <send_to_me@areujoking.com> wrote: > I have just upgraded from slack 9.0 to 9.1. Everything was fine on > one machine but on another I can't get into KDE, TWM etc from kdm or > xdm. There are no errors reported in ~/.xsession-errors, but in > /var/log/kdm.log I get the following (see below): > > I have one of the latest NVIDIA drivers installed > (NVIDIA-Linux-x86-1.0-4496-pkg2.run). > > I can get into kde etc using "startx". > > Can anybody unravel this one? > > /var/log/kdm.log below: > > (II) [GLX]: Initializing GLX extension > > XFree86 Version 4.3.0 > Release Date: 27 February 2003 > X Protocol Version 11, Revision 0, Release 6.6 > Build Operating System: Linux 2.4.22 i686 [ELF] > Build Date: 16 September 2003 > Before reporting problems, check http://www.XFree86.Org/ > to make sure that you have the latest version. > Module Loader present > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/XFree86.0.log", Time: Sat Oct 11 10:43:29 > 2003 > (==) Using config file: "/etc/X11/XF86Config" > Symbol __glXActiveScreens from module > /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! > Symbol __glXActiveScreens from module > /usr/X11R6/lib/modules/extensions/libdri.a is unresolved! > (II) [GLX]: Initializing GLX extension > (II) [GLX]: Initializing GLX extension > (II) [GLX]: Initializing GLX extension You DID remember to comment out the Load DRI line in XF86Config, right? |
| Thread Tools | |
| Display Modes | |
|
|