Re: [opensuse] BIOS/GRUB Problem
- From: Stan Goodman <stan.goodman@xxxxxxxxxxxxx>
- Date: Mon, 8 Nov 2010 18:53:50 +0200
On Monday 08 November 2010 18:02:44 Felix Miata wrote:
On 2010/11/08 17:46 (GMT+0200) Stan Goodman composed:
Felix Miata wrote:
1-Switch to 1 of your 6 virtual consoles (Ctrl-Alt-F[1-6]; e.g.
Crtl-Alt-F2) 2-login as root
Fails right here. While the system was sitting here unloved, it has
frozen. The mouse cursor doesn't move, and Ctrl-Alt-Fx does nothing.
You'll have to force a reboot, power switch if you have no reset
button. With a system idle because frozen for several minutes or more,
there will not likely be any new filesystem corruption that auto fsck
won't handle on restart.
3A-init 6 # reboot, or
3B-init 3 # shut down X
4-fsck /dev/sda7 # what you wish
5-init 5 # restart X
If a reboot or X restart does not fix X, try:
6-Switch to 1 of your 6 virtual consoles (Ctrl-Alt-F[1-6]; e.g.
Crtl-Alt-F2) 7-login as root # if not still logged in from #2
above 8-init 3 # shut down X
9-zypper up # refreshes repos& updates installed packages to
latest versions 10-init 5 # restart X
11-report back
As an alternative to #3A, reboot from root login can also be
accomplished using the reboot command, or the shutdown command,
both of which have man pages.
Also, telinit can be substituted for any instance above of init,
which also has a man page explaining what the init/telinit numbers
mean. e.g., 3 produces runlevel 3, which is full system function
except for anything that requires X to work.
Any time you need to reboot while X is dysfunctional, you can
prevent having X start by appending any of single, 1, 2 or 3 to the
kernel line while in the Grub menu or from a Grub prompt. Then after
performing repairs to the X system, init 5 will attempt to start X
and bring up the GDM/KDM/XDM login screen.
Above (3) you need to do on your reboot, so that hopefully the broken X
won't hang the keyboard. Then login as root, and execute 'zypper up'
to hopefully cleanup whatever wasn't properly done in initial X
installation.
What gfxchip type do you have? If Intel, you might be in for continued
trouble with 11.3, and better off sticking to 11.1 or installing 11.2
to use until 11.4 is released.
This is an Intel board (915GAV). If that makes v11.3 problematic, then I
can wait for v11.4, which I think is scheduled for release in March. That
can mean either returning to v11.1, once the booting is straightened out
(on the next reboot, I will check to see how v11.1 is behaving after all
this). Or I could continue to use v11.2 on the laptop, as I have been
doing these weeks.
--To test if your window manager is working without bothering with
the login screen, you can login from any of the virtual consoles as
any regular user (or root if you dare), then run the command startx.
Done this way if the display manager is still not producing a menu
that allows you to exit, you can kill X completely with Ctrl-Alt-BS
Ctrl-Alt-BS.
Stan Goodman
Qiryat Tiv'on
Israel
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
- Follow-Ups:
- Re: [opensuse] BIOS/GRUB Problem
- From: Felix Miata
- Re: [opensuse] BIOS/GRUB Problem
- References:
- Re: [opensuse] BIOS/GRUB Problem
- From: Stan Goodman
- Re: [opensuse] BIOS/GRUB Problem
- From: Felix Miata
- Re: [opensuse] BIOS/GRUB Problem
- Prev by Date: Re: [opensuse] BIOS/GRUB Problem
- Next by Date: Re: [opensuse] BIOS/GRUB Problem
- Previous by thread: Re: [opensuse] BIOS/GRUB Problem
- Next by thread: Re: [opensuse] BIOS/GRUB Problem
- Index(es):
Relevant Pages
|
