Alle 19:23, sabato 3 luglio 2004, Leendert Meyer ha scritto:
On Saturday 03 July 2004 18:39, Patrick Shanahan wrote:
- Leendert Meyer <leen.meyer@home.nl> [07-03-04 11:22]:
On Saturday 03 July 2004 17:42, Patrick Shanahan wrote:
- Leendert Meyer <leen.meyer@home.nl> [07-03-04 10:32]:
On Saturday 03 July 2004 17:12, Patrick Shanahan wrote:
after issuing init 3, startx will start kde, but init 5 returns the same result.
Perhaps it is a display manager issue. [gkx]dm does not run in runlevel 3, but does in 5.
Should I change the display manager from kdm to xdm or ?? and try 'init 3', 'init 5' again? Or should I reinstall kdm, can I? I am grasping at straws here <grin>.
If you do that, and the problem does not go away, than it is at least not specific to 1 display manager.
BTW, try 'startx', followed by 'startx -- :1' from another console. I like to know if you can run two instances at the same time. My guess is 'no'.
You are correct. See other post in this thread (answering Anders).
I just rebooted after changing parallel yes to no
This keeps the 'Starting ...' and their eventual error messages next to eachother. (Booting is slightly slowed down, but I can't tell on my pc)
and changing from auto-logon to not.
The 'welcome' screen shows and X hangs right there. I suppose it is doing the same thing that it did with the auto-logon but doesn't display the 'welcome' screen.
Tried again 'startx -- :1', with same errors reported previous. Something about failed to allocate decoder object ...
My believe that it's the nvidia driver gets stronger. But perhaps it's just permissions being wrong somewhere (/dev/* ?).
I am reading now this thread and I have to say that old Nvidia drivers are sometimes faulty. At least they did not work very well on my laptop giving me the problem similar to what you describe. I solved with a shell script which waited for 5 seconds after X hung up, then killed it, then restarted it and everything worked. A better solution though could be using the lastest nvidia driver, which are not giving me that bad behaviour now. If you have the latest SuSE kernel and have the same problem I got installing those drivers, see my other posts.
Cheers,
Leen
Greetings, Praise