Hai,
I am using puppy-2.15 in USB flash drive. I am using
xvesa video wizard. when loading puppy-2.15 message box
displayed (the reason of, previously system hang or
powercut) .I am using booting screen in puppy-2.15 . so
Messagebox displayed back of booting screen.
I have two problem
-----------------------
1. Messagebox displayed back of booting screen. How do I reenter into x .
2. when I type restartwm in console the system go to text mode. In that window we must type xwin .If type xwin
in text mode then go to graphical mode. Otherwise stay in
text mode not go to graphical mode. How to avoid
typing xwin command and go to text mode in puppy-2.15.
Anyone please help me.
Thank you,
Thunder
how to avoid typing xwin in puppy-2.15
-
Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
Okay, I think I've deciphered the message.
1. When the system hangs (or the power is cut), Puppy doesn't start back up into X. In 2.15CE specifically, it shows a dialog box asking if you want to "try again" or go to the "command line".
All you do to enter X is hit the enter key over the "try again" box.
This message box is equivalent to Windows saying "I crashed again. Do you want to enter safe mode?". Normally, it's okay to just continue into X, but if X itself is broken, that wouldn't work. So rather than having Puppy boot straight into X and freeze every time you start, it gives you this option to drop into the command line so you can fix it.
There are ways to make the message disappear, but I don't remember them. A search of the forum should bring them up. I think they involved adding a line to /etc/rc.d/rc.local to delete /etc/.XLOADED, or maybe echo "FALSE" > /etc/.XLOADED
2. When Puppy is running, X and all, running restartwm exits X but doesn't restart it.
That's a glitch, as far as I know. It's supposed to start X back up. I don't know why it breaks nor how to fix it, as I never bother with that command. Instead, I just restart the windowmanager from the start menu. In IceWM, that's Start -> logout -> restart IceWM. I don't remember how it is in JWM.
The restartwm script would be handy for restarting X though, since that's what it's supposed to do (it's name is a misnomer).
1. When the system hangs (or the power is cut), Puppy doesn't start back up into X. In 2.15CE specifically, it shows a dialog box asking if you want to "try again" or go to the "command line".
All you do to enter X is hit the enter key over the "try again" box.
This message box is equivalent to Windows saying "I crashed again. Do you want to enter safe mode?". Normally, it's okay to just continue into X, but if X itself is broken, that wouldn't work. So rather than having Puppy boot straight into X and freeze every time you start, it gives you this option to drop into the command line so you can fix it.
There are ways to make the message disappear, but I don't remember them. A search of the forum should bring them up. I think they involved adding a line to /etc/rc.d/rc.local to delete /etc/.XLOADED, or maybe echo "FALSE" > /etc/.XLOADED
2. When Puppy is running, X and all, running restartwm exits X but doesn't restart it.
That's a glitch, as far as I know. It's supposed to start X back up. I don't know why it breaks nor how to fix it, as I never bother with that command. Instead, I just restart the windowmanager from the start menu. In IceWM, that's Start -> logout -> restart IceWM. I don't remember how it is in JWM.
The restartwm script would be handy for restarting X though, since that's what it's supposed to do (it's name is a misnomer).
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
This comes up time and time again.
I appreciate why it is done this way, to catch a buggy xorg.conf that is on a crash restart loop.
It would save a lot of questions if the boot just paused for a minute with a warning that allowed you to drop to the shell if you chose to, otherwise it continued to start X.
pretty please Barry
I appreciate why it is done this way, to catch a buggy xorg.conf that is on a crash restart loop.
It would save a lot of questions if the boot just paused for a minute with a warning that allowed you to drop to the shell if you chose to, otherwise it continued to start X.
pretty please Barry
Will
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
contribute: [url=http://www.puppylinux.org]community website[/url], [url=http://tinyurl.com/6c3nm6]screenshots[/url], [url=http://tinyurl.com/6j2gbz]puplets[/url], [url=http://tinyurl.com/57gykn]wiki[/url], [url=http://tinyurl.com/5dgr83]rss[/url]
-
Pizzasgood
- Posts: 6183
- Joined: Wed 04 May 2005, 20:28
- Location: Knoxville, TN, USA
I thought about that while I was typing but I had to leave for class. Looking at dialog (the program I used to display the improved version) there is an option for a timeout. So maybe that could be used to give a 10-20 second pause to let the user know what's going on, then continue. That would be especially handy for kiosk setups, which seem to be prone to hard reboots.
Even if something like that doesn't work it's way into Puppy, I'll add it to the next Pizzapup.
Even if something like that doesn't work it's way into Puppy, I'll add it to the next Pizzapup.
[size=75]Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]
[img]http://www.browserloadofcoolness.com/sig.png[/img]