Desktop Problem during 13.1 updates

English Install/Boot/Login
#1

Today, I updated from `12.3 to 13.1 from DVD. The update went fine. Then I went to Yast for further updates. Those updates were going fine.

Since they were taking a while, I went web surfing. Suddenly, the screen flashed, the desktop picture reverted to the OSS 13.1 logo, and the system tray disappeared. Except for the drop down menu in the upper right corner, all of my shortcuts and other links are gone.

When I restarted the system, I noticed that the menu does not include the kernel from the previous operating system. When I choose desktop, the bootup screen seems to stall at the hard drive icon, then the screen gets crooked for a moment. Then the same default OSS 13.1 logo comes up and I only have the drop down menu at the upper right.

Then I went into failsafe and back into Yast to finish the updates. Failsafe looks like my regular desktop and works fine. The updates finished. I rebooted and went back into the desktop option, but I still only get the same problem screen.

Please let me know how to fix this. Thanks in advance!:’(

Linux 3.7.10_1.36-desktop
Opensuse 13.1 (bottle) (x86_64)
KDE platform 4.11.5

#2

It’s hard to guess, based on the information present.

Check the output of “df” (maybe post it here with code tags). I wondering whether a partition is full, causing some commands to silently fail.

What’s your video. If you were using nVidia drivers for 12.3, then there might have been problems updating them.

#3

Yes :wink:

Please give more information:

  • what kind of hardware are you using?
  • from which kind of device are you booting?

And can you see from the boot loader menu whether you are booting the same kernel in failsafe mode
as in non-failsafe mode?

Good luck
Mike

#4

OK, here’s the df output:


Filesystem      1K-blocks     Used  Available Use% Mounted on
/dev/sda6        20642428 10331100    9262752  53% /
devtmpfs          5982012       16    5981996   1% /dev
tmpfs             6027048      224    6026824   1% /dev/shm
tmpfs             6027048     2208    6024840   1% /run
tmpfs             6027048        0    6027048   0% /sys/fs/cgroup
tmpfs             6027048     2208    6024840   1% /var/lock
tmpfs             6027048     2208    6024840   1% /var/run
/dev/sda1       647306536 72937560  574368976  12% /windows/C
/dev/sda7      1247694572 60131868 1186295120   5% /home

In Kinfocenter > graphical information > Open GL, the vendor is VM Ware, Inc. The renderer is Gallium 0.4 on llvmpipe (LLVM 3.3, 128 bits)

I’m not sure what other information to offer, but I have an idea what happened: I have an HDMI cable that I forgot to disconnect during that Yast update. The other end is connected to a TV wherein if it’s turned on or off, I get a pop up screen that asks if I want to configure the monitor. Is it possible that this is the source of the trouble?

I successfully updated 12.3 to 13.1 on another HDD on the same PC using the same DVD.

#5

I have an Asustek MB with an ATI VGA compatible controller.

I’m booting from a HDD.

I can see the same boot loader menu, but there is an anomaly: Only the latest kernel is available as opposed to a previous update to 13.1 that offers two different kernels.

Thanks for your quick replies.

#6

Thanks.

Then you don’t have a disk “full” problem.

I’m not sure what other information to offer, but I have an idea what happened: I have an HDMI cable that I forgot to disconnect during that Yast update.

I guess it’s possible.

It’s also possible that something in your KDE settings have been corrupted. Try creating a new user account, and check whether everything works properly for that new user.

#7

On 2014-07-14 22:06, HealingMindNOS wrote:
>
> Today, I updated from `12.3 to 13.1 from DVD. The update went fine. Then

I went to Yast for further updates. Those updates were going fine.

The general procedure I recommend after a System Offline Upgrade, aka
DVD upgrade, is running, in text mode, and before adding any repo
besides the four official ones, this:


zypper patch
zypper up
zypper dup

Yes, the three of them.

Then you can reboot, and enter graphic mode, if it works.

Then, verify the output of this list:


rpm -q -a --queryformat "%{INSTALLTIME}	%{INSTALLTIME:day} \
%{BUILDTIME:day} %-30{NAME}	%15{VERSION}-%-7{RELEASE}	%{arch} \
%25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}
" \
| sort | cut --fields="2-" | tee rpmlist \
| egrep -v "openSUSE.13\.1" | less -S

And manually handle discrepancies.

And after that, run “rcrpmconfigcheck” and verify the resulting list of
config files. I suggest backing up both the active and the old/new file
somewhere, and then edit both with “meld”. Choose what to keep or not of
the config.

More info here: Offline upgrade method

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

#8

This is Mesa’s software renderer.
This means that you are not using the radeon driver, but probably the generic fbdev which could be the cause of your problems.

And which one exactly?

Did you select “No KMS” for the installation, or add “nomodeset” to the boot options?
If yes, remove it.

Are you really still using Linux 3.7.10_1.36-desktop as you posted in your first post? That’s the one from 12.3.
If yes, install the latest one manually, by selecting the package in YaST and clicking on “Versions” below the package list.

Please post your /var/log/Xorg.0.log to see why the radeon driver cannot be loaded.

#9

It’s Asustek MB M5A88-M w/AMD FX CPU.

I went for the automatic upgrade, so I didn’t change anything in the boot options (at least, not intentionally.)

Unfortunately, /var/log/Xorg.0.log only gets me:

bash: /var/log/Xorg.0.log: Permission denied

even when I log in as root.

Yes, I’m still on Linux 3.7.10_1.36-desktop. I’ll let you the the result from the upgrade. Thanks!

#10

But what graphic chip?
Have a look in KInfocenter or YaST->Hardware->Hardware Information f.e. or run:

/sbin/lspci

I went for the automatic upgrade, so I didn’t change anything in the boot options (at least, not intentionally.)

Well, I just thought that you maybe selected “No KMS” at the boot screen of the installation DVD.

Unfortunately, /var/log/Xorg.0.log only gets me:

bash: /var/log/Xorg.0.log: Permission denied

even when I log in as root.

You’re trying to run it. This won’t work of course as it is just a text file.
Open it in a text editor or similar.

Yes, I’m still on Linux 3.7.10_1.36-desktop. I’ll let you the the result from the upgrade. Thanks!

Ok.
And since it is an upgrade, check that you have the package “kernel-firmware” installed. This is needed on many Radeon chips for the radeon driver to fully work.

#11

I need a little more hand holding here. In Yast under view > package groups, I’m not sure where to go. Under package > all packages, I have two update options. Under extras > packages changes, nada. I’m searching under these repos?

#12

Type “kernel-desktop” into the search field, click on “Search” (or press Return).
Then select the package and click on “Versions” below the package list.

You can install/remove specific versions there. Install the 3.11.10-17.2 one.

#13

On 2014-07-15 13:56, wolfi323 wrote:

> Are you really still using Linux 3.7.10_1.36-desktop as you posted in
> your first post? That’s the one from 12.3.
> If yes, install the latest one manually, by selecting the package in
> YaST and clicking on “Versions” below the package list.

The procedure I posted would solve that one automatically, and any other
one lurking.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

#14

Something mysterious just happened - my desktop profile works now.

1st I created a new user account then logged into regular desktop and it works.

2nd I logged in as root into regular desktop and it works.

3rd I logged into my usual profile, regular desktop and it now works! (?)

I remain clueless, but I am grateful for your help.

#15

I’m still trying to figure out that procedure. If I knew how to approach it, I wouldn’t be so clueless. But thanks for your help, anyway.

#16

Yast tells me that I have 3.11.10-17.2 installed already, so I’m not sure what that info is at Kinfocenter.

Thanks for your help! My problem seems to be solved. Exactly how? Perhaps, I should ask the “Dome.”

#17

But which one are you booting?
If you don’t trust KInfocenter, run “uname -a” to find out.

Maybe you have set the 3.7.10 one as default in YaST->System->Boot Loader->Boot Loader Options?
Maybe you installed it now, but haven’t rebooted yet, so you are still using the old one?

#18

Here’s the uname -a output:


Linux linux-ppnb 3.7.10-1.36-desktop #1 SMP PREEMPT Thu Jun 12 10:14:12 UTC 2014 (fcb6f8f) x86_64 x86_64 x86_64 GNU/Linux

I went into Yast and I only found:

Desktop – openSUSE 12.3 - 3.7.10-1.36
Failsafe – openSUSE 12.3 - 3.7.10-1.36
GNU GRUB 2 – openSUSE 12.3 - GNU GRUB 2

I’m not sure what to think about this because I’ve rebooted several times.

#19

So you are still using GRUB legacy?
Do you see the new kernel when you select “GNU GRUB 2” at the boot menu?

Is the Boot Loader correctly set to “GRUB” in YaST?
Let YaST propose a new boot loader configuration, maybe it will pick up the installed 3.11 kernel then.

#20

I went to boot loader settings > other > propose new configuration. Now, I have a new boot list:

  • openSUSE 13.1 (default)
  • Failsafe – openSUSE 13.1
  • Kernel-3.11.6-4-desktop
  • Kernel-3.11.10-17-desktop
  • Kernel-3.7.10-1.36-desktop
  • Desktop – openSUSE - 3.11.10-17 (/dev/sdb7)
  • Windows

sdb7 is my 2nd HDD, I’ll see you on the other side to let you know how it works out. Thanks in advance!