Hello Folks!!!
I've encountered some problem with my FC5..... After I've done some updates to it... so now its Fedora Core (2.6.15-1.2054_FC5).... When I restarted my laptop (Acer TravelMate 4602WLMi) the booting up process started as usual but suddenly it jumped to some blank window... with cross icon in middle and just stopped to response ... so what I need to do now? I just don't even know what is the problem....
Hope for some help.
On 9/24/06, Ivan Evstegneev bravo.elf@gmail.com wrote:
I've encountered some problem with my FC5..... After I've done some updates to it... so now its Fedora Core (2.6.15-1.2054_FC5).... When I restarted my laptop (Acer TravelMate 4602WLMi) the booting up process started as usual but suddenly it jumped to some blank window... with cross icon in middle and just stopped to response ... so what I need to do now? I just don't even know what is the problem....
For some help, take a look at the following tread:
http://marc.theaimsgroup.com/?l=fedora-list&m=112931036311398&w=2
Paul
I dont think that my display causes some trouble... 'cause before the update it worked just fine...
On 9/24/06, Paul Smith phhs80@gmail.com wrote:
On 9/24/06, Ivan Evstegneev bravo.elf@gmail.com wrote:
I've encountered some problem with my FC5..... After I've done some updates to it... so now its Fedora Core (2.6.15-1.2054_FC5).... When I restarted my laptop (Acer TravelMate 4602WLMi) the booting up process started as usual but suddenly it jumped to some blank window... with cross icon in middle and just stopped to response ... so what I need to do now? I just don't even know what is the problem....
For some help, take a look at the following tread:
http://marc.theaimsgroup.com/?l=fedora-list&m=112931036311398&w=2
Paul
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
On 9/24/06, Ivan Evstegneev bravo.elf@gmail.com wrote:
I dont think that my display causes some trouble... 'cause before the update it worked just fine...
On 9/24/06, Ivan Evstegneev bravo.elf@gmail.com wrote:
I've encountered some problem with my FC5..... After I've done some updates to it... so now its Fedora Core (2.6.15-1.2054_FC5).... When I restarted my laptop (Acer TravelMate 4602WLMi) the booting up process started as usual but suddenly it jumped to some blank window... with cross icon in middle and just stopped to response ... so what I need to do now? I just don't even know what is the problem....
For some help, take a look at the following tread:
http://marc.theaimsgroup.com/?l=fedora-list&m=112931036311398&w=2
Are you absolutely sure that the settings regarding your monitor were not changed during the upgrade?
Paul
Zdar.
Zda se mi to OK, tech 300$ je priplatek za 20 stopy kontejner.
D.
I don't know how can I check this... cause my FC5 don't even boots up... so if you want to explain me how to do it... it would be much helpful
On 9/24/06, Paul Smith phhs80@gmail.com wrote:
On 9/24/06, Ivan Evstegneev bravo.elf@gmail.com wrote:
I dont think that my display causes some trouble... 'cause before the
update
it worked just fine...
On 9/24/06, Ivan Evstegneev bravo.elf@gmail.com wrote:
I've encountered some problem with my FC5..... After I've done some updates to it... so now its Fedora Core (2.6.15-1.2054_FC5).... When I restarted my laptop (Acer TravelMate 4602WLMi) the booting up process started as usual but suddenly it jumped to some blank window... with cross icon in middle and just stopped to response ... so what I need to do now? I just don't even know what is the problem....
For some help, take a look at the following tread:
http://marc.theaimsgroup.com/?l=fedora-list&m=112931036311398&w=2
Are you absolutely sure that the settings regarding your monitor were not changed during the upgrade?
Paul
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Ivan Evstegneev wrote:
I don't know how can I check this... cause my FC5 don't even boots up... so if you want to explain me how to do it... it would be much helpful
Try pressing any key when your computer is booting up to show the kernel line in grub. Highlight the kernel that you want to boot with. Press the a key to get into append mode where you can backspace out the rhgb entry and maybe the quiet option to show more details at boot time. After you remove the rhgb quiet from the kernel line, press the a key again to continue booting up your computer. The most likely problem is the program red hat graphical boot is locking up during your boot. If not the problem, you should be able to see where the computer is stopping and relay the text portion of the problem that you see when the computer stops responding. If you recently installed a new kernel, you might want to just try booting in the last kernel version by showing the menu as above. Then you arrow down to your alternate kernel selection to see if the older kernel boots up alright for you.
Jim
Hello Jim,
Saturday, September 30, 2006, 3:27:11 AM, you wrote:
Ivan Evstegneev wrote:
I don't know how can I check this... cause my FC5 don't even boots up... so if you want to explain me how to do it... it would be much helpful
Try pressing any key when your computer is booting up to show the kernel line in grub. Highlight the kernel that you want to boot with. Press the a key to get into append mode where you can backspace out the rhgb entry and maybe the quiet option to show more details at boot time. After you remove the rhgb quiet from the kernel line, press the a key again to continue booting up your computer. The most likely problem is the program red hat graphical boot is locking up during your boot. If not the problem, you should be able to see where the computer is stopping and relay the text portion of the problem that you see when the computer stops responding. If you recently installed a new kernel, you might want to just try booting in the last kernel version by showing the menu as above. Then you arrow down to your alternate kernel selection to see if the older kernel boots up alright for you.
Jim
-- Good advice is something a man gives when he is too old to set a bad example. -- La Rouchefoucauld
the problem is that I have no old kernel line in my GRUB loader only the new one is appeared...
Ivan Evstegneev wrote:
Hello Jim,
the problem is that I have no old kernel line in my GRUB loader only the new one is appeared...
The availability of only one kernel will limit you trying another kernel.
Have you pressed a key to see the menu, highlight your kernel, press the a key to get into append mode? When you are in append mode, backspace out the rhgb and quiet entries and then press the enter key after removing the lines from the grub boot line. I previously said the a key and noted my mistake after sending the email. Anyway, if rhgb is causing the problem, you will be able to boot. You may blank out at the GUI loading or you might see some message while booting about what is happening. If you fail once you hit the GUI still, you could boot into runlevel 3 by repeating the steps mentioned above by adding a space followed by the number 3 on the boot line. Once in runlevel 3, you could log onto the terminal as root and run system-config-display --reconfig to see if you can reconfigure X with the program. If that fails, you might try running yum -y update while you are in runlevel 3 in order to pull in later updates which could fix your problem. Then reboot your computer to see if X startx. There has to be at least another kernel newer thsn the one that you have installed. After a successful update, you should have two kernels showing in grub.
If you can't get this far, a reinstall is probably the easiest. The next time that you run yum to update your computer, do it from a root terminal so X does not restart on you and kill yum and all other programs running off of the GUI layer. (I was hit once by X respawning when yum was running in a gnome-terminal)
Jim
Hello Jim,
Sunday, October 1, 2006, 2:33:06 AM, you wrote:
Ivan Evstegneev wrote:
Hello Jim,
the problem is that I have no old kernel line in my GRUB loader only the new one is appeared...
The availability of only one kernel will limit you trying another kernel.
Have you pressed a key to see the menu, highlight your kernel, press the a key to get into append mode? When you are in append mode, backspace out the rhgb and quiet entries and then press the enter key after removing the lines from the grub boot line. I previously said the a key and noted my mistake after sending the email. Anyway, if rhgb is causing the problem, you will be able to boot. You may blank out at the GUI loading or you might see some message while booting about what is happening. If you fail once you hit the GUI still, you could boot into runlevel 3 by repeating the steps mentioned above by adding a space followed by the number 3 on the boot line. Once in runlevel 3, you could log onto the terminal as root and run system-config-display --reconfig to see if you can reconfigure X with the program. If that fails, you might try running yum -y update while you are in runlevel 3 in order to pull in later updates which could fix your problem. Then reboot your computer to see if X startx. There has to be at least another kernel newer thsn the one that you have installed. After a successful update, you should have two kernels showing in grub.
If you can't get this far, a reinstall is probably the easiest. The next time that you run yum to update your computer, do it from a root terminal so X does not restart on you and kill yum and all other programs running off of the GUI layer. (I was hit once by X respawning when yum was running in a gnome-terminal)
Jim
I got into the append mode and removed "rhgb quiet" and got to boot process I chose the "selective startup" so I could decide which daemon to run. All moved fine till I reached the "cupsd" & "sshd:/usr/sbin/sshd" & "crond" & "atd" daemonds. For all of them I've got the same message, like:"Starting ____: ____: error while loading shared libraries: libpam.so.0 can't open object file: No Such Folder Or Directory"
where "____" is the name of the daemon.
At the end of all this stuff I get the black screen with kernel version line above and:"localhost login:" invitation line. So what do I need to do now?
Some more thing, would you please reference me to some documentation about all those daemons and kernel arguments(rhgb quiet)? So I could read and understand some more things about it.
Tnx again.
P. S. I've read about runlevels... but still don't know how to handle this. Where and what I need to type if I want to run some of them?
Ivan Evstegneev wrote:
Hello Jim,
I got into the append mode and removed "rhgb quiet" and got to boot process I chose the "selective startup" so I could decide which daemon to run. All moved fine till I reached the "cupsd" & "sshd:/usr/sbin/sshd" & "crond" & "atd" daemonds. For all of them I've got the same message, like:"Starting ____: ____: error while loading shared libraries: libpam.so.0 can't open object file: No Such Folder Or Directory"
where "____" is the name of the daemon.
I have not tried the selective setup in a very long time. The last time I used it was when sendmail would take forever during Redhat 5.2 - If you chose not to run one of the services, chances are the service needed to be running before the following services could run successfully. If you allowed the system to boot up as normal, without selecting the services, the OK in green or the FAILED in red should be shown on the screen. If you let everything start, something might be missing in your install.
At the end of all this stuff I get the black screen with kernel version line above and:"localhost login:" invitation line. So what do I need to do now?
This is the terminal, much like the DOS prompt of days long past. From this terminal, you start and stop programs. You are in an interactive mode without a graphic interface. At the login: screen is where you enter your login. Since you are trying to fix the installation, the root account would be what you want. Enter the word root. Next you should see a password: prompt, enter your password for root.
Now you can try to get your X working. First you will run a program called system-config-display. You will want to type the below to get a clean configuration. system-config-display --reconfig Now, X should try to start and show you a GUI where you can pick your display if not detected and adjust your screen resolutions to the desired values.
If you are able to get a successful X configuration and the program exits, you might create a normal user with adduser username followed passwd username to get a normal user account. Then you can hit Alt-F2 to get you to another terminal. For this terminal, put in your newly created username for the regular user. Then the password that you set for that user. After you are logged into the second terminal (ALT-F2) as a normal user, type the command startx to test if you can get to a GUI mode. Your GNOME or KDE desktop should come up. If this works, you can edit out the rhgb entry permantly with an editor. You must be root to make the changes. You can use any editor that you want to do remove the entry from the file. If you are still learning and don't know a lot about all the editors and stuff, you can press the a key to remove the rhgb entry on each bootup until you know the system better.
Some more thing, would you please reference me to some documentation about all those daemons and kernel arguments(rhgb quiet)? So I could read and understand some more things about it.
I'll save the links for documentation to those familiar with the available documentations. I understand the problem with quiet and rhgb because of the lists when the graphical bootloader was introduced. Our documentation specialists for the community can give the best resources to check.
Tnx again.
P. S. I've read about runlevels... but still don't know how to handle this. Where and what I need to type if I want to run some of them?
The command telinit followed by the runlevel number should stop services in the runlevel that you are in and start services in the runlevel that you are changing to. Of course, runlevel 6 is shutdown and should just turn off your computer. I have changed successfully from runlevel 5 to 3 and from 3 to 5. I also had luck changing to runlevel 1 from either 5 or 3. Your reading up on the runlevels will probably give you a deeper understanding of when one runlevel is desired over another. I know when X misbehaves (GUI) runlevel 5 is quite a mess. X will try to start over and over again. Runlevel 3 is handy when you want a lot of shells for ALT-F1 through ALT-F6. You can run many different users and each doing a different task. You can also start the GUI from any of the users in the terminals that you have open.
Good luck and You might search google for documentation related to Linux. Documentation for Fedora Linux would cover Fedora/Redhat programs like rhgb and options to the kernel.
Jim
On 9/29/06, Ivan Evstegneev bravo.elf@gmail.com wrote:
I don't know how can I check this... cause my FC5 don't even boots up... so if you want to explain me how to do it... it would be much helpful
I do not know what to tell you beyond what is said in the thread that I suggested to you. I am sorry about that.
Paul
hey ivan....
can you tell us,
-are you able to connect to the internet from your FC5 wireless... -are you definitely up to FC5 'uname -a', cat /etc/fedora-release -can you do a 'yum grouplist' -
the description you provided sounds like you have X windows running, but not the gnome/kde environment running..
so let's see what's going on...
-----Original Message----- From: fedora-list-bounces@redhat.com [mailto:fedora-list-bounces@redhat.com]On Behalf Of Ivan Evstegneev Sent: Sunday, September 24, 2006 10:43 AM To: For users of Fedora Core releases Subject: After Update My FC5 get BLANK SCREEN.
Hello Folks!!!
I've encountered some problem with my FC5..... After I've done some updates to it... so now its Fedora Core (2.6.15-1.2054_FC5).... When I restarted my laptop (Acer TravelMate 4602WLMi) the booting up process started as usual but suddenly it jumped to some blank window... with cross icon in middle and just stopped to response ... so what I need to do now? I just don't even know what is the problem....
Hope for some help. -- Best regards, Ivan mailto:bravo.elf@gmail.com
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list