Hi all, I have a problem. Hope someone can answer quickly.
I have installed openSuSE 11.4 32-bit on my PC. Installation went okay, but when I shut down the syatem and started later it does not load.
My computers have;
Intel Pentium Dual Core processors
Asus motherboards
Onboard VGA, Sound, NW
2 GB DDR2 RAM
80 GB SATA HDD
SWAP: 2 GB
ROOT: 20 GB (ext4)
/home: 52 GB (ext4)
17" LCD monitors
Generic keyboard, mouse
What happens is, the first screen appear (where it instructs to press DEL to go to BIOS), then the system hangs us displaying “Error Loading Operating System”. There nothing works, except the CTRL+ALT+DEL. Press CTRL+ALT+DEL, same cycle repeats.
“Error Loading Operating System”
That seems to be a message from your BIOS not being able to find anything to boot from.
This can have several reasons: either your boot loader isn’t installed properly, boot sequence doesn’t contain the media where the boot loader is installed, HDD could be damaged etc.
Try booting with F12 (or whatever option to enter the boot menu) check your boot device is available and choose it manually.
Did you install from a DVD? Can you still boot from this DVD? It should give the option to boot the installed operating system. This should start the installed boot loader i.e. grub.
You may also try booting a life system to check your HDD.
If you are sure your HDD is intact and available you can try the “repair function” of the installation DVD just to repair grub. AFAIK there is such an option.
BTW, isn’t the intel dual-core a 64 bit processor? Why installing a 32 bit OS?
First of all I would like to thank you for the quick reply. Thank you very much, I appriciate it.
Then I would like to inform that I got it fixed myself. You were correct about the error message. But the error was with the openSuSE. What I did was reboot the computer with the DVD. Then configured GRUB, at least that’s what I thought I did.
Here is what I actually did. Hope it’ll help anyone who face same problem.
grub
**grub>**find /boot/grub/menu.lst
(hd0,1)
**grub>**root (hd0,1)
Filesystem type is ext2fs, partition type 0x83
**grub>**setup (hd0)
Checking if /boot/grub/stage1 exists ... yes
...
...
Succeeded.......Done
**grub>**quitreboot
Remind you, I’m new to Linux. So your question is interesting. I just downloaded 32-bit OS with no particular reason. I thought it would run without issues, specially driver issues, for the printers/ scanners etc. Do you suggest that I should go with 64-bit version of openSuSE?
I’m afraid but now have another issue. In fact, two of them…
This time it correctly identifies the OS, and goes to OS loading screen, but it then hangs there. No progress, no mouse/ keyboard feed accepted, no HDD read (no LED), nothing happens at all. It just hangs there until I hit restart button. Sometimes it loads okay once I restart it, sometimes not. For the moment, my solution is to restart it till it properly boot. Any ideas?
My PS2 mouse does not work. USB mice and wireless mice work properly, but not the PS2. Is some driver missing? Do I have to update something?
Thanks for all the replies and thanking in advance for a positive feedback.
I think more information is needed, here. If you hit “esc” as soon as you see the green boot screen you get the boot messages.
If it “hangs” you will see where.
For instance, sometimes just a check of the hard disk is being forced to be carried out. This can take long, depending on your HDD. If you don’t see the message, this can be mistaken as “hanging”.
There is also a log file i.e. “boot.log”. AFAIK it is in /var/log/… .
Isn’t there also a chapter in Yast -the set-up tool where you can check the log files?
If you can’t help yourself, post the messages or log.file here. Maybe somebody else can.
You should be able set up your mouse in Yast. I alway use PS2 to save USB ports without issue. Strange that it isn’t recognized from the start.
I am not at home right now. Sorry for not being precise. Don’t have a Linux machine at hand.
In fact I have hit ESC key, yes it shows boot messages. But they are so quick!
The problem is, see it in this way… the boot process, as I understood has three steps.
First green screen, where you can use up/down arrow keys to switch to fail-safe mode. You hit ESC, you’ll see boot messages.
Second green screen, where the lizard in the middle and some hint of a progress bar. It last for a fraction of a second, blink and go to the third green screen when no freeze. When the booting freeze, this is where it freezes. No mouse keyboard feed is taken. Only ESC is to hit RESTART.
Third green screen, where the actual progress bar is shown just below the lizard in the middle. If you get this screen then it will go all the way.
I can not read the log file. I tried to open it as root, but it looks empty.
And the mouse issue, it still remains. I see an applet called “Mouse on Text Console” in YaST, I have “Accept”-ed four (4) mouse types listed below. But no improvement.
PS/2 mouse (Aux-port)
Ligitec busmouse
Microsoft busmouse
IntelliMouse Explorer (ps2)
I go to the “Hardware Information” applet. It shows tow mouse entities.
Did you follow up the note in the openSUSE-11.4 release notes wrt KMS ?
Sometimes Kernel Modesetting (KMS) does not work well in supporting the identification/configuration of one’s graphics hardware, or keyboard/mouse hardware, and its necessary to disable modesetting upon boot, by entering the grub boot code:
nomodeset
Have you tried that ? Does it make any difference ? [my guess is it will not - but IMHO its worth a try].
On the first screen, where you can choose failsave mode you have to press ESC.
Then you should get the same menu in black/white. Now you choose the failsave.
then press e. Now there comes another menu up. Choose the line that begins
with ‘kernel’. Then press ‘e’ again. Now you can edit this line. Add ‘,nomodeset’
at the end and press ‘b’. Now it should boot with this parameter.
The log file is /var/log/boot.msg. Maybe you can post it if there is anything suspicious.
If it hangs after login, it could also be the x-server.
You may check and post the /var/log/Xorg.0.log.
A while ago, I set up my wife’s computer with 11.4 (64 bit) and got frequent freezes in KDE.
Here is what I did, and it helped:
Boot text mode = runlevel 3 (enter “3” (no quotes) in the same grub line as “nomodeset”).
Run Yast as root.
Add required repositories (main, update, oss, KDE, nvidia or ATI if you have it)
Goto install / delete software.
Update all packages with newer versions.
Force-update anything that had to do with xorg, my graphic driver, the kernel and kernel modules. (I searched the packages manually).
That takes a while.
Reboot normally (runlevel 5).
I know, not very sophisticated and quite drastic. However, I thought it could do no harm after a fresh install.
Whatever it was, I hit it by chance and now it works fine.
It’s awsome how you all turned out and try to answer my problems. I’m really thankful to all of you. I’ll follow the instructions and will post my results soon.
Yes you can make it permanent. I suspect your hardware is Intel and you may be booting to FBDEV driver, which is pretty primitive.
Before making it permanent, what is output of:
/sbin/lspci -nnk | grep VGA -A2
(note GNU/Linux is case sensitive).
Also, can you open file /var/log/Xorg.0.log and copy it and then paste it to the web site SUSE Paste and then post here the website / URL address you are given after submitting it there. That might tell us a bit more about your graphics.
Thanks for the reply. You were correct suggesting my hardware is Intel. But I have a new observation to share with you.
This is what it shows immediately after the mode selection screen when I could hit ESC quick enough (if I were late it would have been freezes and ESC would not respond)
doing fast boot
Creating device nodes with udev
71. 663371] BUG: soft lockup - CPU#0 stuck for 63S! [moreprobe: 114]
71. 663608] Process modprobe (pid:114, ti=f724c000 task=f71051b0 task.ti=f724c000)
71. 663793] Stack:
71. 663865] Call trace:
71. 664001] Code: /* HERE SOME SET OF HEX-NUMBERS, LIKE “45 2a 55 d3…” ARE SHOWN */
For me, it looks like the processor causes the freeze. Will that be the video instead?
Are you certain you get that output with the boot code ‘nomodeset’ ? Typically the boot code ‘nomodeset’ will force the loading of the FBDEV driver and NOT the i915 module ! (which is from the intel or intellegacy ‘driver’).
Do you have a custom edit of ‘intel’ or ‘initellegacy’ in your /etc/X11/xorg.conf.d/50-device.conf file ? Do you have an /etc/X11/xorg.conf file which specifies ‘intel’ or ‘initellegacy’ ? Because without either an xorg.conf or 50-device.conf custom edit, what you posted makes no sense to me, and I am scratching my head on this !
Does the /var/log/Xorg.0.log file indicate the FBDEV driver is being loaded (instead of ‘intel’ ) ?