OpenSUSE 12.1 hangs on boot

I’ve been using OpenSUSE 12.1 for over a week without any problems, but today I can’t boot it up anymore. After choosing OpenSUSE 12.1 in the GRUB menu, The green OpenSUSE screen with the logo appears and it just hangs there. If I try secureboot it keeps repeating the text:

failed command: READ FPDMA QUEUED
cmd and some numbers
res and some numbers (media error)
status: { DRDY ERR }
error: { UNC }
configured for UDMA/100
Complete

I can boot into Windows 7 without any problems (dual boot) , and all hardware seems to work there

Is there any way to fix this without completely reinstalling OpenSUSE?

On 07/02/2012 06:16 PM, hydrot3k wrote:
> Is there any way to fix this without completely reinstalling OpenSUSE?

maybe…what is your experience level with Linux?

and, what did you do during the session just before it stopped booting?
install or uninstall anything? delete any ‘unneeded’ files? edit any
configs as root? what?

when you get to the first green screen try pushing the F5 key and select
like here:
http://dl.dropbox.com/u/10573557/12.1_Misc/12.1_F5_sysV.jpg

maybe then it will boot…if so, return and someone can tell you how
to make that permanent…

it it still won’t progress, then restart and see if you can type “3”
(without the quotes) in the boot options block, and then hit enter…

it may start up to a log in prompt, if so, please put in your user ID,
and then password and then


zypper lr -d

which will result in a grid of info…take a photo of that and put it on
paste.opensuse.org and return the generated URL link to here…

if it fills more than the screen then do it again with


zypper lr -d | less

and you can use the up/down arrow to scroll…photo all the info…


dd

My last session on OpenSUSE thunderbird and davmail were running, ktorrent was running and i had been surfing the web with chromium.

I tried to boot with system V but it also hangs on boot.

Then i tried to type “3” to boot, I didn’t get a log in prompt, just lines of text all saying “starting program name” with program name the names of various programs or modules.

On 07/03/2012 10:36 AM, hydrot3k wrote:
> i tried to type “3” to boot, I didn’t get a log in prompt, just
> lines of text all saying “starting program name” with program name the
> names of various programs or modules.

ok…well, that is you seeing the machine booting up…let it run and
i’d expect it to eventually stop and say something like:


Master Resource Control: runlevel 3 has been        reached

Welcome to openSUSE 12.1 blah blah blah blah

[something-xxxx] login:

with a blinking cursor underline right after the “login:”

type your user ID there, press enter and it will ask


Password:

with a following blinking cursor…type in your password and press enter

then follow the previous direction…by the way “zypper lr -d” has no
numbers in it, instead that “lr” is a lower case “L”

and, also when you come back try to remember to answer “what did you do
during the session just before it stopped booting? install or uninstall
anything? delete any ‘unneeded’ files? edit any configs as root? what?”

and, “what is your experience level with Linux?” (apparently not
much…had i known that i could have explained the above, the first
time…and, saved you many hours of waiting, maybe)

and NOTE to any other potential helpers who look in…i’m gonna be in
and out, so if you see an lr -d before i do, help him/her un-jumble the
mess…


dd

I tried what you said, but zypper lr -d just gave me a list of repositories…

I’m giving up on OpenSUSE for now, hopefully I can find another distribution with decent KDE implementation

>
> I tried what you said, but zypper lr -d just gave me a list of
> repositories…

which is exactly what i needed to see to try to help you…(because your
symptoms sound like they might very well be due to the introduction of
incompatible software into the system near the end of that “I’ve been
using OpenSUSE 12.1 for over a week without any problems”…

i mean, it doesn’t just stop being trouble free just because the
calendar say Monday 2 July!!

there is a reason it stopped working…and, discovering that reason
is the only pathway to fixing…

but, if you are unwilling to provide the info needed to help then that
is your business…

> I’m giving up on OpenSUSE for now, hopefully I can find another
> distribution with decent KDE implementation

most folks who know a lot about KDE know that there are many KDE
developers who are also SUSE developers…and, lots and lots of folks
think that openSUSE has a not only “decent KDE implementation” but maybe
the best, certainly one of the top two…

but, if you wanna quit, that is ok…drop in again sometimes…

bye!


dd

When booting 12.1, my computer frooze also after the first splashscreen and presented a login line. The reason, as in earlier Versions 11.x was the well known problem that SUSE has with NVIDIA graphic cards. After updating to “Asparagus” today (Kernel 3.1.10-1.16) the installed NVIDIA driver was no longer recognized. To solve the problem I had to install the NVIDIA drivers manually. NVIDIA provides the driver for your system and your graphics card. It has the name NVIDIA…run. Download it and install as decribed by NVIDIA, i.e.

  1. boot the system with the option “nomodeset”
  2. after initial boot a login line shows up:
    login as user with your name and password
    su
    init 3
    sh <path to the driver you downloaded>

Maybe you had as I problems with the SUSE nouveau drivers and you need to install the NVIDIA drivers.

Thank you for your suggestion. I have an ATI graphic card and I have the proprietary drivers for it installed, so this might be a different problem.

On 2012-07-04 16:46, hydrot3k wrote:
>
> I tried what you said, but zypper lr -d just gave me a list of
> repositories…

Which we expected you to post here.

> I’m giving up on OpenSUSE for now, hopefully I can find another
> distribution with decent KDE implementation

Ok, please yourself.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

On 07/05/2012 11:06 PM, hydrot3k wrote:
> this might be a different problem.

i suspect (but can’t know since you refuse to provide the info needed to
help you), that your problem is the same as in this thread…

which was solved, as noted in this post: http://tinyurl.com/cg2gzwu


dd