Hellow all, I have a fedora-version blue screen. Yes, the blue screen as of Windows. Two days ago, I updated some utilities using Synaptic and tries to shut down the computer. However, it did not shutdown and got stuck with a blue screen with the rolling sand watch that used to give a way to text-mode. So, I just push the button to turn it off.
When I turn on the computer the next time, booting went well, doing starting utilities and so on until it stop right before the log-in screen. And it again was the blue screen with the watch where it stoped.
It doesn't boot from CD-ROM; Booting disk didn't help either.
Is there any one who can help me with this? I'm really frustrated and my wife is mad and demands Windows back.
ssh was blocked so that my friend couldn't help me. I'd like to know at least how to let ssh go through.
Any help will be greatly appreciated.
__________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thursday 26 February 2004 20:29, taehyun nam wrote:
ssh was blocked so that my friend couldn't help me. I'd like to know at least how to let ssh go through.
Ctrl-Alt-F1 thru F6 will get you an 80x25 textmode console that you can log into. From there you can do what you need to get sshd up.
- -Andy
- -- Find your answer without waiting for replies.... Searchable list archives at http://marc.theaimsgroup.com/?l=fedora-list&r=1&w=2
and I see a man with no romantic experience.
AMAZING POWERS OF OBSERVATION wrote:
i see who the man is of your householdOn Thu, 2004-02-26 at 14:39, J.L. Coenders wrote:
/> Is there any one who can help me with this?
I'm really frustrated and my wife is mad and demands Windows back.
Ouch, we should help you quickly. Too bad I cannot help you with it ;)
- Jeroen
/
On Thu, 2004-02-26 at 23:15, AMAZING POWERS OF OBSERVATION wrote:
i see who the man is of your householdOn Thu, 2004-02-26 at 14:39, J.L. Coenders wrote:
Is there any one who can help me with this? I'm really frustrated and my wife is mad and demands Windows back.
Ouch, we should help you quickly. Too bad I cannot help you with it ;)
- Jeroen
Hi Jeroen,
You help with the wife we will help with the blue screen. [Ha Ha just kidding] I have never in 5 years seen a blue screen of death in linux. Mr Coenders could you give more detail on the events before you get the blue screen and what thscreen looks like maybe some error messages. Thanks
Blue screen in Linux:=| mmm! box must be infected with windoze.
On Fri, 27 Feb 2004 00:31:09 +0200, Chadley Wilson wrote
I have never in 5 years seen a blue screen of death in linux. Mr Coenders could you give more detail on the events before you get the blue screen and what thscreen looks like maybe some error messages. Thanks
It sounds to me like GNOME isn't starting for some reason and the user is reporting the blue background painted by gdm (as configured in /etc/X11/gdm/gdm.conf) as a BSOD when that's not what it actually is.
Is that more or less correct?
-- Chris
"Build a man a fire and he will be warm for the rest of the night. Set a man on fire and he will be warm for the rest of his life." -- Unknown
Em Qui, 2004-02-26 às 17:29, taehyun nam escreveu:
Hellow all, I have a fedora-version blue screen. Yes, the blue screen as of Windows. Two days ago, I updated some utilities using Synaptic and tries to shut down the computer. However, it did not shutdown and got stuck with a blue screen with the rolling sand watch that used to give a way to text-mode. So, I just push the button to turn it off.
Ok, may I assume you're a newbie in linux? When something goes wrong with X (simplifying, the linux graphical mode) try closing X first.
You can 1) restart X: type ctrl-alt-backspace 2) Go to a text-mode window and see if machine is still responding You can do this by typing CTRL-ALT-FX, where FX is from F1 to F6 in Fedora.
When you are on one of those windows, log is as root and type: telinit 3, wait for stuff happen and type enter. This way you have a linux without X enabled at this time. Is easier see what's wrong.
Once you're in text-mode, just type xinit. It will load X, without anything else, like gnome. In fact, you'll have mouse and a graphic terminal.
If you reached this step, type exit and return to text-mode. You will have some output from X, maybe there's something useful on it.
If it doesn't, type startx - it will load X, but with gnome or kde. If this is ok, your problem is with something else, a package called GDM.
Then, you will need to repair the gdm package.
When I turn on the computer the next time, booting went well, doing starting utilities and so on until it stop right before the log-in screen. And it again was the blue screen with the watch where it stoped.
Looks like a gdm error.
It doesn't boot from CD-ROM; Booting disk didn't help either.
Why not? Are your cd and floppy drives damaged? You can always set boot order in your BIOS setup.
Maybe it's possible to boot from cd and repair some things...
http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/s1-grub-runl...
You want run level 3 (non-gui)
Login as root Finish your update or roll back whatever got messed up then try just starting x with startx
Either that or you could "init 5" and try to launch that run level again.
-Chris
On Thu, 2004-02-26 at 14:29, taehyun nam wrote:
Hellow all, I have a fedora-version blue screen. Yes, the blue screen as of Windows. Two days ago, I updated some utilities using Synaptic and tries to shut down the computer. However, it did not shutdown and got stuck with a blue screen with the rolling sand watch that used to give a way to text-mode. So, I just push the button to turn it off.
When I turn on the computer the next time, booting went well, doing starting utilities and so on until it stop right before the log-in screen. And it again was the blue screen with the watch where it stoped.
It doesn't boot from CD-ROM; Booting disk didn't help either.
Is there any one who can help me with this? I'm really frustrated and my wife is mad and demands Windows back.
ssh was blocked so that my friend couldn't help me. I'd like to know at least how to let ssh go through.
Any help will be greatly appreciated.
Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html
Hi, all. Thanks to you, I managed to have X-window work, kind of, which made my wife happy for a while.
A) So, I ran X-window, and I keep getting the following error
error while loading shared libraries: libxml2.So2 cannot open: no such file or directory
whenever I try 1) startx 2) synaptic 3) yum
B) I can manage to initiate X-window by xinit, but as I said not by startx. What is the difference? C) lokkit was not recognized, by which I tried to turn on ssh. Any other way to turn on ssh?
If you have any advice, I'm sure you do, please let me know. Many thanks in advance.
--- Chris Spencer cspencer@cait.org wrote:
http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/ref-guide/s1-grub-runl...
You want run level 3 (non-gui)
Login as root Finish your update or roll back whatever got messed up then try just starting x with startx
Either that or you could "init 5" and try to launch that run level again.
-Chris
On Thu, 2004-02-26 at 14:29, taehyun nam wrote:
Hellow all, I have a fedora-version blue screen. Yes, the blue screen as of Windows. Two days ago, I updated some utilities using
Synaptic
and tries to shut down the computer. However, it
did
not shutdown and got stuck with a blue screen with
the
rolling sand watch that used to give a way to text-mode. So, I just push the button to turn it
off.
When I turn on the computer the next time, booting went well, doing starting utilities and so on
until it
stop right before the log-in screen. And it again
was
the blue screen with the watch where it stoped.
It doesn't boot from CD-ROM; Booting disk didn't
help
either.
Is there any one who can help me with this? I'm really frustrated and my wife is mad and
demands
Windows back.
ssh was blocked so that my friend couldn't help
me.
I'd like to know at least how to let ssh go
through.
Any help will be greatly appreciated.
Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing
online.
__________________________________ Do you Yahoo!? Get better spam protection with Yahoo! Mail. http://antispam.yahoo.com/tools
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Just wondered if there was a better way of syncing time. Sometimes on booting I don't have my gateway PC switched on. Fedora will pause the boot sequence while it starts the ntpd and tries to sync with the time server (which fails due to no net connection).
Really this isn't a boot critical process and can be done once X windows has started.
Can someone describe how I could keep the standard fedora clock settings but change when the ntpd is started.
I also am not bothered about running a time server, just really want it to sync on boot or every hour would be good enough.
Kind Regards Phil Hannent
Hi, running chkconfig ntpd off as root should disable ntpd. If you just want to sync time, you can run ntptimeset -s (also as root) from a console.
By the way, please don't reply to a random message when posting to mailing lists. That messes up the threading. For example, your email shows up as a response to "Still Blue screen in Fedora" in a thread-aware email client.
HTH, Levin
On Mon, 2004-03-01 at 11:09, Phil Hannent wrote:
I also am not bothered about running a time server, just really want it to sync on boot or every hour would be good enough.
You could create a cron job in root and have it run daily. Here's my cron entry. This runs every day at noon, to do this hourly change the 12 to a *.
================================================== [root@therock bin]# cat crontab.txt SHELL=/bin/bash MAILTO=root HOME=/root LANG=en_US
00 12 * * * /usr/sbin/ntpdate -u -s -t 20 ntp.cpsc.ucalgary.ca ntp1.cmc.ec.gc.ca tick.utoronto.ca time.chu.nrc.ca time.nrc.ca timelord.uregina.ca ===================================================
You install this as root by typing at the console
# crontab crontab.txt
You can verify that it is set by typing...
# crontab -l
Cheers, Chris
On Mon, Mar 01, 2004 at 02:15:33PM -0500, Christopher Ness wrote:
On Mon, 2004-03-01 at 11:09, Phil Hannent wrote:
I also am not bothered about running a time server, just really want it to sync on boot or every hour would be good enough.
You could create a cron job in root and have it run daily. Here's my cron entry. This runs every day at noon, to do this hourly change the 12 to a *.
00 12 * * * /usr/sbin/ntpdate -u -s -t 20 ntp.cpsc.ucalgary.ca....
Be kind to your time servers and do this in a pseudo random way. i.e. be fashionably late. Change the 00 for minutes to be something random for each machine you setup this type of cron task. No good reason to do it at 12 either for once a day tasks.
For once a day tasks like this you only need to invent fashionable numbers once for each box. Rolling dice or something like this will get some.
# bash expr $RANDOM % 60; expr $RANDOM % 24
Little tricks like this can reduce pileups on lots of shared services. For example those that maintain personal/local yum/up2date mirrors with cron could smooth the load by picking a random time to update.
See also the way cool "-R [time in minutes]" option in yum.
Tom Needs a Hat Mitchell wrote:
On Mon, Mar 01, 2004 at 02:15:33PM -0500, Christopher Ness wrote:
On Mon, 2004-03-01 at 11:09, Phil Hannent wrote:
I also am not bothered about running a time server, just really want it to sync on boot or every hour would be good enough.
You could create a cron job in root and have it run daily. Here's my cron entry. This runs every day at noon, to do this hourly change the 12 to a *.
00 12 * * * /usr/sbin/ntpdate -u -s -t 20 ntp.cpsc.ucalgary.ca....
It's not clear to me why you would want to do this when configuring ntpd is so easy -- just run redhat-config-date and check "enable network time protocol".
If you want time synchronization on a dial-up connection (where you aren't connected all the time), then there are ntp alternatives that do a good job for that: chrony (http://chrony.sunsite.dk/) for example. Just having npdate change the clock periodically isn't all that good -- note that ntp (and chrony, I expect) use adjtime(2) to speed up or slow down time to keep the clock adjusted.
jch
On Tue, 2004-03-02 at 06:16, John Haxby wrote:
Tom Needs a Hat Mitchell wrote:
On Mon, Mar 01, 2004 at 02:15:33PM -0500, Christopher Ness wrote:
You could create a cron job in root and have it run daily. Here's my cron entry. This runs every day at noon, to do this hourly change the 12 to a *.
00 12 * * * /usr/sbin/ntpdate -u -s -t 20 ntp.cpsc.ucalgary.ca....
It's not clear to me why you would want to do this when configuring ntpd is so easy -- just run redhat-config-date and check "enable network time protocol".
Won't this stall the machine on boot if a network connection is not available? Don't be scared of cron. It is quite helpful, and if you have an application that requires all your machines to be somewhat close in time then is "enable network time protocol" good enough?
I agree with Tom that everyone should randomize their network accesses though.
If you want time synchronization on a dial-up connection (where you aren't connected all the time), then there are ntp alternatives that do a good job for that: chrony (http://chrony.sunsite.dk/) for example. Just having npdate change the clock periodically isn't all that good -- note that ntp (and chrony, I expect) use adjtime(2) to speed up or slow down time to keep the clock adjusted.
The above simply fails. If you do not want to recieve emails from cron about failures (you probably do, unless you are often not connected to the network) then redirect the output to /dev/null
The magic of computers. There are 8x10^6 ways to do something. Choose your weapon and stick with it unless something absolutely better comes by.
Chris
Christopher Ness wrote:
It's not clear to me why you would want to do this when configuring ntpd is so easy -- just run redhat-config-date and check "enable network time protocol".
Won't this stall the machine on boot if a network connection is not available? Don't be scared of cron. It is quite helpful, and if you have an application that requires all your machines to be somewhat close in time then is "enable network time protocol" good enough?
No. ntpd just attempts to run anyway. The initial ntpdate tends to stall for a few seconds if the network connection isn't there, and if that's too much then it's OK to just remove or empty the step-tickers file. I didn't run NTP at all until I had a permanent network connection. Now, however, I have a permanently running server that provides a stratum 3 server for everything else that boots. If the DSL connection goes down then it doesn't much matter from the point of view of NTP.
I agree with Tom that everyone should randomize their network accesses though.
This is why ntp was created in the first place, well, one of the reasons.
If you want time synchronization on a dial-up connection (where you aren't connected all the time), then there are ntp alternatives that do a good job for that: chrony (http://chrony.sunsite.dk/) for example. Just having npdate change the clock periodically isn't all that good -- note that ntp (and chrony, I expect) use adjtime(2) to speed up or slow down time to keep the clock adjusted.
The above simply fails. If you do not want to recieve emails from cron about failures (you probably do, unless you are often not connected to the network) then redirect the output to /dev/null
What simply fails? chronyd doesn't work do you mean? I remembered another one as well: k9 (kaska.demon.co.uk), although I think that just picks up ntp broadcasts which gives it limited use.
The magic of computers. There are 8x10^6 ways to do something. Choose your weapon and stick with it unless something absolutely better comes by.
True. And about 75% of them break sooner or later. The adjtime() system call was put in place because various applications -- "make" was the main one at the time -- break when they find time has suddenly gone backwards. You can use ntpdate and cron to set the time, but don't complain when things behave badly, if, of couse, you can work out why they broke in the first place.
If you really want to run ntpdate to periodically synchronise the time (and I would say that chronyd is still a better choice), then stick at the end of the ifup script so that you only step the time when you bring the dial-up connection up. If you have a permanent connection then just run ntp and forget it.
jch
On Tue, Mar 02, 2004 at 03:46:37PM +0000, John Haxby wrote:
Christopher Ness wrote:
It's not clear to me why you would want to do this when configuring ntpd is so easy -- just run redhat-config-date and check "enable network time protocol".
Won't this stall the machine on boot if a network connection is not available? Don't be scared of cron. It is quite helpful, and if you have an application that requires all your machines to be somewhat close in time then is "enable network time protocol" good enough?
No. ntpd just attempts to run anyway. The initial ntpdate tends to stall for a few seconds if the network connection isn't there, and if that's too much then it's OK to just remove or empty the step-tickers file.
I agree with Tom that everyone should randomize their network accesses though.
Thanks... (this little trick does help on real networks).
This is why ntp was created in the first place, well, one of the reasons.
...
If you want time synchronization on a dial-up connection (where you aren't connected all the time), then there are ntp alternatives that do a good job for that: chrony (http://chrony.sunsite.dk/) for example. Just having npdate change the clock periodically isn't all that good -- note that ntp (and chrony, I expect) use adjtime(2) to speed up or slow down time to keep the clock adjusted.
Some may have missed the announcement of changes to "ntpdate". "ntpdate" will no longer do the fast update that it once did. See the 'ntp' home pages and read the discussion.
Because of this change to ntpdate people with volatile connectivity may need to revisit how the local clock is checked and set at boot/ network connect time.
As the time on individual machines improves the need to randomize timed connections will need minor random delays with resolutions less than a minute. Today lots can be done in 60 seconds, no need to gang up on the first second of 60 ;-)
When local clocks were sort of sloppy this hardly mattered but the quality of time that ntp can distribute absolutely changes the rules for pileups due to simple cron tasks.
Hi,
On Mon, 01 Mar 2004 14:15:33 -0500 Christopher Ness nesscg@mcmaster.ca wrote:
On Mon, 2004-03-01 at 11:09, Phil Hannent wrote:
I also am not bothered about running a time server, just really want it to sync on boot or every hour would be good enough.
You could create a cron job in root and have it run daily.
I just added the line /usr/sbin/ntptimeset -s to /etc/ppp/ip-up.local. This script is executed each time the internet connection is established. This way the time is regularly re-set, but never when we're offline.
Levin
-
Alexandre Strube -
Andy Green -
Chadley Wilson -
Chris Spencer -
Christofer C. Bell -
Christopher Ness -
J.L. Coenders -
John Haxby -
Levin Fritz -
Matt Morgan -
mitch epling -
Phil Hannent -
taehyun nam -
Tom Mitchell