Installation issue during update from 12.2 to 12.3

Hello everybody

Today I was upgrading my system from the version 12.2 to the 12.3, following the steps I have used in the past upgrades successfully.During the upgrading I did not receive any error message of whatsoever, but when I reboot the system, I got the following booting messages:

[OK] Started Network Manager
Starting Network Manager Wait Online
[FAILED] Failed to start Network Manager Wait Online
see ‘systemctl status Network Manager-Wait-Online service’ for details

[OK] Reached Target Network
Starting Command Scheduler…
[OK] Started Command Scheduler
Starting LSB : NFS client services…
[OK] Reached Target Host and Network Name Lookups.
Starting Postfix Mail Transport Agent…
Starting /etc/init.d/boot.local Compatibility…
[OK] Started /etc/init.d/boot.local Compatibility
Started LSB : NFS client services.
Starting LSB : Import remote SMB /CIFS (MS Windows) file systems…
[OK] Started LSB : Import remote SMB /CIFS (MS Windows) file systems…
[OK] Reached target Remote File Systems (Pre)
[OK] Started Postfix Mail Transport Agent
[OK] Reached target Multi-User
[OK] Reached target Graphical Interface

And I got stuck here !!! I am not able to go further this point.

So I tried to boot in failsafe mode, and I was able to overcome the booting process (no errors have been seen) but at the end , after the initial graphical introductory screen , the screen itself became black and the only thing I could see was only the mouse pointer and nothing else.

Furthermore I verified I was able to boot the system without graphic interface (init 3) but unfortunately I realized that my Linux knowledge was good enough to solve the issue.

It seems to me that there is a graphic interface issue.

Please do you have any idea ? Did I make a mistake somewhere ?

Thanks for your attention

Fabrizio

Yes.
What graphics card do you have?
Did you use a proprietary driver on 12.2? (nvidia maybe?)
You would have to reinstall that.
If you have /etc/X11/xorg.conf that tries to load that driver, the graphical system would fail to load, like in your case, so try to remove/rename that if it exists.

Pity that not even failsafe mode is working, that would make it much easier.
You said you get a black screen with mouse pointer? What Desktop Environment are you using?
Does pressing Alt+F2 give you a command run window?

Try to press Ctrl+Alt+Backspace twice, this should get you to the login screen.
Does it work when you select a different Desktop session there? (IceWM f.e., that should be installed by default)
You could at least work in graphical mode then for further diagnostics.

Thanks for you prompt reply

  1. I have an ATI HD3650 graphic card
  2. I was not using any proprietary driver but the opensource installed with Suse
  3. I am using the KDE graphic interface

Please let me know if you need further info

OK, then there should not be an xorg.conf that is interfering.

So, can you run programs in failsafe mode when you press Alt+F2?
You could enter “dolphin” to get a file manager f.e., or “firefox” for a Webbrowser. :wink:

And how exactly did you do the upgrade?

Hello

I was able to launch the Dolphin file manager through the failsafe mode using ALT+F2 and I checked in /etc/X11/ and there is no xorg.conf file. So no attemptive to load the fglrx driver was done.

I am able to launch Firefox perfectly and to update the system through internet normally. But I still see the desktop completely black. Only the mouse cursor is visible

As far as the update is concern, I did it in the following way:

  1. I added the version 12.3 repositories. I added the Packman as well but I have lowered its priority to the bottom, so the other repositories got updated first.
    n

  2. In a console terminal I ran the command : zypper -ref, and every repository was fine

  3. I ran the command zypper dup, I accepted the license and the update begun smoothly.

  4. I use the shutdown -r now command and the system restarted unfortunately with some issue.

Please do you need me to do anything else ?

Thank you

Fabrizio

You have not anything on the desktop??

Try a different user as a test see if the problem is there may be messed up config files in the ~/.kde4

Unfortunately there is no other user apart me !!!

I have installed Linux in my personal laptop with dual boot with Windows, and there are not other profiles apart mine.

Yes there are not any icon in the desktop only a black screen. I have to use ALT+F2 to run the programs.

Is there any way to check if the KDE setting files were corrupted ?

Thanks

Fabrizio

Create a new user for a test to see

You could rename the ~/.kde4 directory but you can’t do it hen you are running KDE so you have to leave to the command line

Press vtrl-alt-F1

type


su -
enter root password
init 3
mv /home/*yournamehere*/.kde4 /home/*yournamehere*/.kde4.bak
init 5


Note
this will give you a new default desktop
Any KDE stuff you may want will be in ~/.kde4.bak

Note period in front of kde4 in all the above

Thanks for your quick reply

Let’s see if I have understood correctly

Once the booting process is finished and I am in front of my black screen (the faulty KDE) I have to :

  1. Press Ctrl+Alt+F1
  2. Insert the following commands :

su -
enter root password
init 3
mv /home/yournamehere/.kde4 /home/yournamehere/.kde4.bak
init 5

For yournamehere you mean the name of the profile I am currently used ?

Once I have finished should I reboot ?

Sorry if I sound silly , but you know I do not want to make further mistakes :beat-up:

Fabrizio

On 2014-03-20 01:06, FabrizioS wrote:
> Sorry if I sound silly , but you know I do not want to make further
> mistakes :beat-up:

Just create a new user, and try with that user first. If the new user
works, doesn’t have the problem, then you can consider what to do with
your normal user.

This way you run no risks.


Cheers / Saludos,

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

OK, then apparently plasma-desktop is crashing on startup.
As has been mentioned already, try to remove/rename its configuration.
You shouldn’t have to remove/rename the whole ~/.kde4/ though, ~/.kde4/share/config/plasma-desktop-appletsrc should be enough.

Or try to create a new user (in YaST->Security and Users->User and Group Management) and login as that, as mentioned. (if you have auto-login enabled, then press Ctrl+Alt+Backspace twice to get to the login screen)

If that doesn’t work as well, please start konsole (via Alt+F2) and type in “plasma-desktop”.
Does it start?
If not, please post the output you get. The last lines should suffice.

As far as the update is concern, I did it in the following way:

  1. I added the version 12.3 repositories. I added the Packman as well but I have lowered its priority to the bottom, so the other repositories got updated first.
    n
  2. In a console terminal I ran the command : zypper -ref, and every repository was fine
  1. I ran the command zypper dup, I accepted the license and the update begun smoothly.
  1. I use the shutdown -r now command and the system restarted unfortunately with some issue.

That sounds ok. But did you remove all other repos before upgrading?

Hello everybody

Good news !!!

I have created a test user account following your instructions and when I logged in Plasma was working !!!

The strange is that it looks a bit shabby like I was in failsafe mode unless with the 12.3 version the ATI HD 3650 is not supported like before.

You asked me

That sounds ok. But did you remove all other repos before upgrading?

Yes I did and I have verified it, but strangely things did not go well

Thanks

Fabrizio

Then remove/rename ~/.kde4/share/config/plasma-desktop-appletsrc for your standard user and it should work again. You will lose your plasmoid setup though.
Maybe you added some plasmoid that causes the crash (but did work on 12.2)?

You could post the output when starting plasma-desktop manually in konsole (when it is crashing), maybe it would provide a clue.

The strange is that it looks a bit shabby like I was in failsafe mode unless with the 12.3 version the ATI HD 3650 is not supported like before.

Please post /var/log/Xorg.0.log (upload it to http://susepaste.org/ and post a link)

Yes I did and I have verified it, but strangely things did not go well

Your plasma crash might not be related to the upgrade procedure.

Hello

I have deleted the file you told me ~/.kde4/share/config/plasma-desktop-appletsrc , and when I rebooted I could see Plasma perfectly working but still shabby.

For this reason I copied and pasted the /var/log/Xorg.0.log

http://susepaste.org/86440312

Now I will answer to your questions:

Maybe you added some plasmoid that causes the crash (but did work on 12.2)?

It worked perfectly in 12.1

You could post the output when starting plasma-desktop manually in konsole (when it is crashing), maybe it would provide a clue.

I did not get any error message during the booting process

Please tell me if you need further info

Regards

Fabrizio

Of course. This was to fix the plasma-desktop crash on startup.

For this reason I copied and pasted the /var/log/Xorg.0.log

http://susepaste.org/86440312

Well, you are using the VESA driver.

The reason for this is you kernel command line:

    30.904] Kernel command line: root=/dev/disk/by-id/ata-Hitachi_HTS543216L9A300_081002FB0240LCDSRK6B-part2 devfs=mount,dall resume=/dev/disk/by-id/ata-Hitachi_HTS543216L9A300_081002FB0240LCDSRK6B-part1 splash=silent quiet nomodeset vga=0x31A

“nomodeset” effectively prevents the use of the radeon driver.

So please enter YaST->System->Boot Loader->Boot Loader Options, and remove “nomodeset” from the “Optional Kernel Parameter” line. (for grub2)

If you’re still using grub1, you should edit the menu entry accordingly (also in YaST->System->Boot Loader).

It worked perfectly in 12.1

Maybe you used the fglrx driver back then?
This one would still work with “nomodeset”, but the legacy driver doesn’t work in openSUSE 12.3 anymore, and the latest version doesn’t support your card.
So you cannot go down that road.

I did not get any error message during the booting process

Yes, but you should have gotten one when running plasma-desktop in konsole.
Anyway, too late now…
Doesn’t matter anyway if you’re fine with configuring plasma from scratch. :wink:

Hello

Unfortunately this time things did not go smoothly!!!

When I removed the “nomodeset” from

    30.904] Kernel command line: root=/dev/disk/by-id/ata-Hitachi_HTS543216L9A300_081002FB0240LCDSRK6B-part2 devfs=mount,dall resume=/dev/disk/by-id/ata-Hitachi_HTS543216L9A300_081002FB0240LCDSRK6B-part1 splash=silent quiet nomodeset vga=0x31A

The only thing I got was to see all dots and lines once rebooted, even the mouse pointer was a huge square full of dots. I had to force the reboot manually and start in failsafe mode. I remember now that in one of my first post in this forum, people suggested me that the issue was caused by the fact that the “nomodeset” was not present.

Unless I am mistaken there should be the possibility to set the graphic card from the file:

/etc/x11/xorg.conf.install

Section “Device”
Identifier “vboxvideo”
Driver “vboxvideo”
EndSection

Section “Screen”
Identifier “vboxvideo”
Device “vboxvideo”
EndSection

Section “Device”
Identifier “vmware”
Driver “vmware”
EndSection

Section “Screen”
Identifier “vmware”
Device “vmware”
EndSection

Section “Device”
Identifier “cirrus”
Driver “cirrus”
EndSection
Section “Screen”
Identifier “cirrus”
Device “cirrus”
EndSection

Section “Device”
Identifier “fbdev”
Driver “fbdev”
EndSection
Section “Screen”
Identifier “fbdev”
Device “fbdev”
EndSection

Section “Device”
Identifier “vesa”
Driver “vesa”
EndSection

Section “Screen”
Identifier “vesa”
Device “vesa”
EndSection

Section “ServerLayout”
Identifier “Layout”
Screen “vboxvideo”
Screen “vmware”
Screen “cirrus”
Screen “fbdev”
Screen “vesa”
EndSection

Should I edit something here or I am wrong ?

Regards

Fabrizio

No. That’s the configuration for the failsafe mode. Leave that as it is!

OK, we’re in a bit of a dilemma here.
Apparently the “radeon” driver shipped with openSUSE 12.3 doesn’t work well with your card. OTOH, the vesa driver (which you get when you specify “nomodeset”) gives you a bad resolution.

One thing I didn’t notice earlier:

    30.904] Kernel command line: root=/dev/disk/by-id/ata-Hitachi_HTS543216L9A300_081002FB0240LCDSRK6B-part2 devfs=mount,dall resume=/dev/disk/by-id/ata-Hitachi_HTS543216L9A300_081002FB0240LCDSRK6B-part1 splash=silent quiet nomodeset vga=0x31A

Why do you have that “devfs=mount,dall” there?
You should remove that.
There’s this error in your Xorg.0.log:

(EE) open /dev/fb0: No such file or directory

Maybe this is caused by that “devfs” option? It prevents the fbdev driver from being used which should give you a better resolution.
If that helps, you might try again to remove the “nomodeset” option, maybe the radeon driver had problems because of that as well.

But in the end, a working radeon driver would really be the best thing for you. It has improved a lot (especially for newer cards) since 12.3 got released, so you might want to try to update it to a newer version.
Either upgrade to 13.1 (much similar to how you upgraded to 12.3), or install the latest X/Mesa/radeon from the [noparse]X11:XOrg[/noparse] repo.

sudo zypper ar http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_12.3/ X11:XOrg
sudo zypper dup --from X11:XOrg

Since part of the radeon driver is in the kernel, you should update your kernel as well:

sudo zypper ar http://download.opensuse.org/repositories/Kernel:/stable/standard/ Kernel:standard
sudo zypper in kernel-desktop-3.13.6

Hello

I updated as you advised me :

sudo zypper ar http://download.opensuse.org/repositories/X11:/XOrg/openSUSE_12.3/ X11:XOrg
sudo zypper dup --from X11:XOrg

And

sudo zypper ar http://download.opensuse.org/repositories/Kernel:/stable/standard/ Kernel:standard
sudo zypper in kernel-desktop-3.13.6

Things didn’t change at as far as the graphics is concerned, but I lost the audio and even the possibility to connect to internet !!!

What happened is that notwithstanding I see the speaker symbol no sound is emitted. Furthermore even the Networkmanager seems to work I cannot setup any wireless connection because a window pops out stating a KDE error.

On top of that in the bootloader two new line has been added : the ones related with the new 3.13.6 kernel (Desktop and Failsafe).
Booting in Failsafe mode did not seem to help: same situation.

Answering to you question:

30.904] Kernel command line: root=/dev/disk/by-id/ata-Hitachi_HTS543216L9A300_081002FB0240LCDSRK6B-part2 devfs=mount,dall resume=/dev/disk/by-id/ata-Hitachi_HTS543216L9A300_081002FB0240LCDSRK6B-part1 splash=silent quiet nomodeset vga=0x31A

The command “devfs=mount,dall” has always been there since the first time I installed 11.3

Something went bad during the kernel update, but during the process I did not get any error message and neither during all the booting process

Regards

Fabrizio

You should still be able to select the older 3.11 kernel in the boot menu (if you use grub2, it’s hidden below “Advanced Options”).

No idea why the latest kernel would give you problems.
But have you tried to remove that “devfs” option already? As I said, this might interfere with the /dev directory and cause all sorts of problems.
This definitely is not needed, I never saw that one before TBH.