While I was waiting for a response, I went back and opened /etc/X11/xorg.conf; there is no mouse[5] mentioned at all under a list of input devices

I will go back and look again; there are other mice (amigamouse and sunmouse among them). My mouse was identified as mouse[1] during our "stalled mouse" correction; I did not see an MS Explorer mouse either.

Back to Linux SuSE and now back here with an edit; 3 immediate problems:1.I can't find an command prompt once xorg.conf is open; 1. I see a list of input devides with names, but I don't know how to open one on these mouse lines and examine their contents, even if I have a command prompt. 3. I would like to close out with a standard logout ; but now I have to use Ctrl+Alt+Delete since I can't "find" a command line.
langein

I don't think I get what you mean by a command prompt once xorg.conf is open. If you mean you have you have to hit "Esc" then ":" and then type save and hit enter to save changes.(once done editting)

You see a list of input devices, you need to find the one causing the error, and then edit it(hit "insert") and you should be able to start typing. put a "#" in front of all but the only mouse you use. You can uncomment them later, but for now, you have to get rid of the erroring one.

I think once you have saved the file, you should be able to use the standard logout, unless i am mireading the current situation...

Hello again, RedShirt

I think of a command prompt as a string of letters and symbols with a flashing cursor at the end, e.g., linux:/_

The old fashioned DOS command prompt was something like the following: C:\>__ (with a flashing cursor where keyboard data was inserted.) The flashing cursor permits alpha-numeric command data to be entered for command execution by pushing the Enter key once the correct command had been entered at the prompt.

When a I open xorg.conf the screen displays a long list of entries such as:
Input Devices "/dev/mouse/"

In the current situation the cursor sits quitely on the left hand side of the screen. Since there are no symbols with the cursor and it is not flashing, I am at a loss as how to edit one of these entries,
e.g., Input Devices "/dev/mouse/."

Thinking back to our Stalled Mouse problem, I had an active mouse that would open the string and display the parameters you mentioned earlier, i.e.,
identifier
driver
option "Device"
option "Name"
option "Protocol" and etc.

Does each of these options, driver, identifier have to typed in place of the string: "/dev/mouse/"? I'm sorry, but I just can't grasp the editing format right now.

QUOTE: < you have to hit "Esc" then ":" and then type save and hit enter to save changes.(once done editting) You see a list of input devices, you need to find the one causing the error, and then edit it (hit "insert") and you should be able to start typing. put a "#" in front of all but the only mouse you use. You can uncomment them later, but for now, you have to get rid of the erroring one.> These instructions are new to me and should help once I get back to Linux screen.

Thanks again,
langbein

While editting the file, there is no command prompt, it is replaced by the file edittor, and you are in the file. All you have to do is type and replace the bad, there is no messing with commands until you have editted what you need to and are ready to save and go back to main command prompt.

Hello again,
I was incorrect: the cursor on the far left does flash and I am able with the four-way arrows to move the cursor to an "offending Input Device."

But here is my delimma, RedShirt:
This is the exact typed contents of the last
portion of linux:/etc/X11/xorg.conf

(a lengthy list of fonts)
(a list of 8 ttyS1 to ttyS8 entries)

Input Devices "/dev/psaux"

Input Devices "/dev/logibm"

Input Devices "/dev/sunmouse"

Input Devices "/dev/atibm"

Input Devices "/dev/amigamouse"

Input Devices "/dev/atarimouse"

Input Devices "/dev/importbm"

Input Devices "/dev/gpmdata"

Input Devices "/dev/mouse"

Input Devices "/dev/usbmouse"

Input Devices "/dev/adbmouse"

Input Devices "/dev/input/mice"

Input Devices "/dev/input/event0

Input Devices "/dev/pointer0

Input Devices "/dev/pointer1

Input Devices "/dev/pointer2

Input Devices "/dev/pointer3

End Section

Can you decide which one or of these InputDevices is the 'Undefined Input Device "Mouse[5]"' referenced by ServerLayout "Layout[all]" ?

And once that is determined would you type out the simulated correction steps required to return this stalled boot back to the 11/16/05 condition (before the corruption dated 11/18/05)?

Having created such a corrupted mess now, I'm wary of attempting to edit one or more of these entries when I have still no idea how to proceed.

I'm sorry that I seem so dense, but I feel you are attributing more skill in "things Linux" than I have.

Sincerely,
langbein

The xorg.conf is like an HTML file, closer to XML maybe, but either way. It has a header, and a body. The section you are looking at with all those listings is a header, you need to scroll down into the body. Basically there will be a corresponding chunk of code like the one I posted earlier to each one of those.

Possibly we could go a much easier route here... you don't happen to have backed up the xorg.conf, did you? In that case we could just overwrite this file with the old one that allowed you to boot, and wham, you are back into GUI. If not, I am afraid there is still some steep learning and a bit of work to get done to get you back into GUI.

Good morning, RedShirt !
Well, your header lines and slow scroll down instructions about the xorg.conf file paid off very well.
I am now reporting the similarites and differences between these 2 files:
1. 2005-11-18 xorg.conf (without THE TILDE ICON "~")
2. 2005-11-16 xorg.conf~ (with TILDE ICON AT THE END "~")

When you mentioned a possible backup of xorg.conf I thought about this TILDE ICON xorg.conf~ file that has always
intrigued me since it contains the DATE OF 11/16/2005 that WAS TWO DAYS BEFORE the fatal date of 11/18/2005 when the
stalled boot occurred.
This morning I opened both files for editing and found some interesting information. First the string of header lines
in xorg.conf that I sent you on Sunday is EXACTLY THE SAME as the headers in xorg.conf~ . Second, look at the striking
difference between:
A: Section "ServerLayout" in the *.conf file--
Identifier "Layout[all]"
InputDevice "Keyboard[0]" "CoreKeyboard"
InputDevice "Mouse[1]" "CorePointer"
InputDevice "Mouse[3]" "SendCoreEvents"
InputDevice "Mouse[5]" "SendCoreEvents"<-Undefined InputDevice "Mouse[5]" ref ServerLayout"(Xorg.0.log)
Option "Clone" "off"
Option "Xinerama" "off"
Screen "Screen[0]

and B: Section "ServerLayout" in the *.conf~ (NOTE THE TILDE) file--
Identifier "Layout[all]"
InputDevice "Keyboard[0]" "CoreKeyboard"
InputDevice "Mouse[1]" "CorePointer" <-ONLY ONE MOUSE; IT IS MINE
Option "Clone" "off"
Option "Xinerama" "off"
Screen "Screen[0]

Note that both Mouse[3] and Mouse [5] are NOT PRESENT in the xorg.conf~ (TILDE) file! Could we overwrite xorg.conf with
xorg.conf~ and solve the boot stall? If not, is the Section "ServerLayout" in xorg.conf the correct location for editing out one or even two mice by using the # icon to "uncomment" their existence?
Mouse[1] contains all the correct parameters that we set during the "Stalled Mouse" problem earlier. These correct
parameters are displayed in Section "InputDevice" as I scroll down in the *.conf file and the *.conf~ file.
Mouse[1] is unequivocally my mouse!!

I'm excited since this the first time that Mouse [5] has been visible.
TTFN, langbein

to setup videocard, monitor, mouse etc.

you should start sax2 in runlevel 3:

STRG+ALT+F1
"root"
password

init 3
sax2

this will restart sax2.

Thank you for returning to this stalled boot problem, Keruskerfürst

Quote: <you should start sax2 in runlevel 3:
STRG+ALT+F1
"root"
password

init 3
sax2

this will restart sax2>

I opened runlevel3 using START (?STRG)+ALT+F1; it seemed to have moved back in the boot sequence, which I assume is where runlevel3 resides.
But I don't know how to use the next four commands at the flashing cursor along the left margin of the boot sequence window. As a "newbie" I need instructions spelled out in every detail as the Linux OS is a complete "black box" to me, so far.

I appreciate your new input and am anxious to implement it now if I can.

Sincerely,
langbein

1. Press CTRL+ALT+F1 to get on one of the textconsoles (I typed STRG+ALT+F1, STRG=CTRL)
2. type "root"
3. system asks for password, enter this
4. type "init 3" to get into runlevel 3
5. type "sax2"
6. change configuration
7. select monitor etc.

Also, you should visit http://www.opensuse.org/Documentation
and dowload and read the instructions.
Check http://www.linuxquestions.org/questions/answers.php

Good afternoon, Keruskerfürst,

I'm sitting here typing from SUSE 9.3!
I'm almost afraid to log off: 112105---after >3 days without GUI suddenly the Desktop/GUI is back and all I did was at /root = linux:/# I typed "init 3" and then typed "sax2" and a SaX2 window that i recognized appeard and asked if its appearance was correct; I said OK and pushed Enter, having forgotten that you wanted me to type "change configuration."
The stalled sequence window remained so I used CTRL+ALT+DEL to logout (still the only way to exit since the stalled boot sequence occurred on the 18th of Nov).

After reboot, and the loading of Linux OS started I looked down at some notes and WHEN I LOOKED BACK UP I COULD NOT BELIEVE MY EYES: MY DESKTOP WITH THE SOFT BROWN TONE OUTDOORS SCENE WAS LOOKING BACK AT ME. IF YOU BELIEVE IN MIRACLES, THIS IS CERTAINLY ONE IN THE TECHNICAL REALM.

I going to reboot to see if this Reality or just a fantastic dream.

langbein

PS: back at 14:57 and after 3 reboots and 2 controlled logout from the GUI decktop, the "BIG SLEEP" is over!

=================================================================================
Hello RedShirt,
Just wanted to be sure you've learned the good results of the "stalled boot" problem:
THE UNBELIEVABLE: THE ENTIRE STALLED BOOT HAS DISAPPEARED ( post #26)

Good afternoon, Keruskerfürst,

I'm sitting here typing from SUSE 9.3!
I'm almost afraid to log off: 112105---after >3 days without GUI suddenly the Desktop/GUI is back and all I did was at /root = linux:/# I typed "init 3" and then typed "sax2" and a SaX2 window that i recognized appeard and asked if its appearance was correct; I said OK and pushed Enter, having forgotten that you wanted me to type "change configuration."
The stalled sequence window remained so I used CTRL+ALT+DEL to logout (still the only way to exit since the stalled boot sequence occurred on the 18th of Nov).

After reboot, and the loading of Linux OS started I looked down at some notes and WHEN I LOOKED BACK UP I COULD NOT BELIEVE MY EYES: MY DESKTOP WITH THE SOFT BROWN TONE OUTDOORS SCENE WAS LOOKING BACK AT ME. IF YOU BELIEVE IN MIRACLES, THIS IS CERTAINLY ONE IN THE TECHNICAL REALM.

I going to reboot to see if this Reality or just a fantastic dream.

langbein

PS: back at 14:57 and after 3 reboots and 2 controlled logout from the GUI decktop, the "BIG SLEEP" is over!