Finished the install and now it wont start for SUSE

English Install/Boot/Login
#1

OpenSUSE 12.3, KDE 4.1 along with Win 7

I had run previously from the Live CD but only after poking F3 (video) and selecting NoHMS—(something, like HMS). I cant remember the acronym.
So, deciding to forge ahead, I did the install from the LiveCD, remembering to poke F3.
It finished but I can’t say successfully because I cant remember, the messages flew by so fast.

I think I saw a
"KWIN PID: 3626 Signal: segmentation fault (11).

Not knowing what to do, I rebooted and got a menu offering me this:

  1. Opensuse 12.3
  2. Advanced options for openSUSE
  3. openSUSE 12.3 Memtest
  4. Windows Recovery Environment
  5. Windows 7 (loader) (on /dev/sda<------the a is partially chopped off.

Happily, option 5 works ok. At least for now.
Option 1 gets me to the gecko screen and part of the icons before freezing
Option 2 gives me 2 more options but they both say the same thing, unless the text has been truncated which I suspect.
a) opensuse with linux 3.7.1
b) —same—

I took option 2a hoping I could get a safe mode and what I got was:

-------------------toggle starts here-------------------
a lot of command logging and stop at:
[OK] reached target graphical interface
------------------toggle ends here-----------------

and then it stops.

pressing any key will toggle back and forth.

So, what next ?

Should I try and redo the install ?

Maybe I messed up doing the install but I had elected the F3, NOHMS(?) for the install.

===============================================

Help me Obi-Wan-Kenobi

thanks

#2

It’s KDE 4.10! :wink:

I had run previously from the Live CD but only after poking F3 (video) and selecting NoHMS—(something, like HMS). I cant remember the acronym.

The correct acronym is NoKMS (No Kernel Mode Setting).

I took option 2a hoping I could get a safe mode and what I got was:

-------------------toggle starts here-------------------
a lot of command logging and stop at:
[OK] reached target graphical interface
------------------toggle ends here-----------------

and then it stops.

Try to use option 2b, this should be failsafe mode.

Which graphics card do you have? (I guess you mentioned it in one of your other threads but I don’t want to search right now :wink: )

If you need “nomodeset” do this:
Run YaST->System->Boot Loader, select “Boot Loader Options” and add “nomodeset” to the “Optional Kernel Command Line Parameter” line.
Then even the standard entry should boot.
You can also change the boot menu’s screen resolution there so the entries don’t get cut off.

#3 
How can I do that when I never see a command prompt and when I booted into what I thought was safe mode, whenever I pressed any key it would look like it was trying to boot again and getting stuck at the same place.
#4

You said you took option 2a, which I take as being the first line in “Advanced Options”.
The second line in “Advanced Options” should be failsafe mode, so choose that (that’s what I meant with “2b”).

#5

I took 2b and it would get to a point and stop, the stop point displayed this:

[OK] reached target graphical interface. <-----the OK was green.

Before this was a lot of what looked like command line logging, and any key that I pushed, started it over again.
At the point when it pauses, are there maybe some commands off the screen that I cannot see ?
Can I get to a command prompt ?
Can I change the display setting, maybe via hardware ?
Are there F-keys that I can press ?

#6

OK, so X even fails to start in failsafe mode. I guess this is down to a bug in the “modesetting” driver (already fixed, but the version included in 12.3 final still contains the bug… :frowning: )

So try this:
At the boot menu, select the standard boot entry and press ‘e’ on your keyboard. You should get into edit mode then.
Search for a line starting with “linux” and append “nomodeset” at the end.
Then press the ‘F10’ key to boot.

Hopefully you will get a graphical login screen then…

#7

I am afraid to touch it, it’s so unpredictable.

I took option 1, opensuse 12,3 and while it was doing it’s thing, I kept pressing e.
The screen went black, then voila the desktop appeared.

So, what should I do/check now so as to somehow make this permanent.

He is telling me that there is one new update, opensuse-2013-609 which I will wait on.

You mentioned Yast, should I start it ?

Well, I spoke too soon, it looks like none of the icons do anything.

and it crashed with rainbow squiggle lines.

round 2
I rebooted into opensuse 12.3 and only pressed e once.
It continued to the desktop and at lease one of the icons works.
Dolphin.
So, is there something I can edit to include NOMODSET ?

#8

Hmmm, I tried to start Yast and got a short term listing like this:
[OK] <----green Started LSB VMware tools daemon
then the rainbow crash.

I am typing this on another PC and the linux beast restarted with the same message about VMware

argggggg

#9

You have to press ‘e’ before you press Enter to boot the entry.

But I don’t really understand what you mean with “none of the icons do anything”.
If you add “nomodeset” as explained it should work then, since it did work when booting the LiveCD.
You can then add “nomodeset” permanently with YaST as written before. Or if you can start YaST you could do that now…

#10

On 2013-08-13, hextejas <hextejas@no-mx.forums.opensuse.org> wrote:
> Well, I spoke too soon, it looks like none of the icons do anything.

Can you access the virtual consoles? The virtual consoles should be accessible by holding CTRL-ALT while pressing F1-6.
If you can, then do you have internet access (e.g. can you ping www.opensuse.org )? If so, log in then try this:


sh-4.2$ su -
sh-4.2$ zypper up
sh-4.2$ shutdown -r now
#11

ok, I will try the e before the selection.

Where it stands right now is that I have booted the LiveCD, thinking that I might be able to do an edit to a boot file somewhere.
If not then I won’t.
Would that be of any good ?

By icons doing nothing, I mean just that. I pressed Dolphin and nothing happened, no bouncing icon, no nothing.

Is there a boot file that I could change and include the NOMODSET ?

#12

Yes, you could mount your root partition, edit /etc/default/grub and reinstall the boot loader.
But I guess it’s easier the other way…

#13

Easier is good, but how do I do it ? Is that the e routine ?

#14

Exactly. And don’t worry, you can’t break anything that way, because nothing is saved.

And then, if it works, you should start YaST->System->Boot Loader and add “nomodeset” permanently as explained.

#15

ok, found the linux statement and the last 2 characters are \s
is there a space<> before nomodeset ?

#16

Hm, the last thing on that line should be “showopts”… But it may be slightly different on your system.

And yes, there should be a space before “nomodeset”.

#17

Ok, that got me booted but I need to do something to fix the screen resolution.
How do I work on configuring the video ? Is that Yast ?

A small step for man,etc.

There was more before the end of the line b ut it had continued to another line with an /

#18

Yeah, right.
That ‘’ is not really there, it just means that this is no new line but the continuation of the previous line (because it didn’t fit on the screen).
So is it working now (except for the resolution)?

Then enter YaST->System->Boot Loader, add that “nomodeset” there and you should be fine for now.
And if you change the boot loader’s resolution on that screen, it should be carried over to KDE then I think.
That would be the option “Console resolution” below “Use graphical console”, which should be set to “Autodetect by grub2” by default. Change that to something different like “1280x1024” or “1024x768”.

Then I think the best thing to do in your case would be to install all online updates (YaST->Software->Online Updates) and the proprietary nvidia driver.
But let’s do that later, one step after the other…:wink:

#19

On 2013-08-13 14:06, hextejas wrote:

> I took 2b and it would get to a point and stop, the stop point
> displayed this:
>
> [OK] reached target graphical interface. <-----the OK was green.

> Can I get to a command prompt ?

Press ‘Enter’

–
Cheers / Saludos,

Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))

#20

I tried changing the console nresolution but there is no “apply” button.
When I exit Yast and come back in, it’s set back to autodetect.