Suse 11.0 cannot boot!

English Install/Boot/Login
#1

Hi,

since yesterday I’ve a new notebook (HP Compag 615) and i’ve tried to install openSUSE 11.0.
But there were some problems.
1.) I was only able to install SUSE in text mode and not the graphic mode(I don’t know why).
2.) After successful installation and reboot, I’ve tried to run SUSE from harddisk. The system check started but after
‘Checking if this processor honours the WP bit even in supervisor mode…Ok.’’
nothing happens anymore. It looks like the system hang up.
Does anybody knows about this problem and has a solution for me?
Many thanks

#2

Wondering why you chose 11.0 over 11.1

But did you try the Failsafe boot?

#3

it’s the only reason, that I haven’t a 11.1 DVD.

Ok, I’ve tried the Failsafe system starts up and ask me for login and password.
What I’ll have to do next?

#4

Enter your username and password

then try typing: startx

#5

it’s the only reason, that I haven’t a 11.1 DVD.

Ok, I’ve tried the Failsafe system starts up and ask me for login and password.
I’ve logged in now and run “startx”
Had a look at the systemlog- it shows the following error:
“CPU Freuency scaling is not supported by your processor”
“Cannot load CPUFREQ govenours - no CPUFREQ driver available”

Any idea about that one?

#6

So you have been able to login to the desktop?

For the moment just put the error to one side and tell us about your system hardware and general specification.

#7

Rexikis adjusted his/her AFDB on Sunday 13 Sep 2009 18:36 to write:

>
> it’s the only reason, that I haven’t a 11.1 DVD.
>
> Ok, I’ve tried the Failsafe system starts up and ask me for login and
> password.
> I’ve logged in now and run “startx”
> Had a look at the systemlog- it shows the following error:
> “CPU Freuency scaling is not supported by your processor”
> “Cannot load CPUFREQ govenours - no CPUFREQ driver available”
>
> Any idea about that one?
>
>

You might find that if you are in failsafe then the underlying ACPI and
other settings are off so the system will probably not be running 100%$ and
cpuscaling is disabled.

–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum

#8

I have a feeling you are right Mark. The issue is probably graphics. Once that is sorted he should be able boot normally.

#9

caf4926 adjusted his/her AFDB on Sunday 13 Sep 2009 19:36 to write:

>
> I have a feeling you are right Mark. The issue is probably graphics.
> Once that is sorted he should be able boot normally.
>
>

Yep and for that he will need the ATI`s if he wants 3D for the bling :slight_smile:

–
Mark
Caveat emptor
Nullus in verba
Nil illegitimi carborundum

#10

thx, for the reply.
Here are the specs of my laptop.

Processor AMD Athlon 64 X2 RM-74 2x 2,20 GHz
Cache 1 MB
Front Side Bus 800 MHz
Technology AMD Turion™ 64 X2 Mobile Technology
RAM 2048 MB
Technology DDR2 SDRAM
Formfactor SODIMM 200
Graphic Card ATI Radeon HD 3200
Shared Memory up to 512 MB TurboCache

@ baskitcaise

Yep and for that he will need the ATI`s if he wants 3D for the bling :slight_smile:

What does it mean for me?

#11

ATI - openSUSE

#12

sry for the late reply.

So I’ve started SUSE in failsafe and and run startx.
After succussful running the graphics, I’ve got an horrible sound out of the laptop. Sonds like a resonance frequency (feedback).

I’ve downloaded the latest version (11.1), checksum ok, and tried to run the installation. After loading the kernel (100%), the monitor stays black and nothing happens anymore.
Any ideas what to get around the problem?

#13

I’ve started again from scratch. Now everything worked well. It went completely through the installation & configuration process in graphical mode. After completion of the installation and a restart (booting from harddisk) I get the following error message:
Fatal server error:
no screens found
giving up
xinit : Connection refused (errno 111): unable to oconnect to x server
xinit : No such process (errno 3): Server error

What do I have to do next?

#14

sry, for the third posting.

Finally I’ve solved the problem.
I run sax2, changed the screen resolution, run startx and it worked.
Thanks for your support.
So the thread can be closed.

#15

Excellent - well done!