I have been trying to install leap 42.2 onto a friends pc it had opensuse 11.4 but she had messed up badly her mount points and root and home got all messed up. So I decided on a clean install but it just wouldn’t install! It would get to 5 seconds remaining with all packets installed but then crash before installing the bootloader. So I backed down to 42.1 with basically the same results always nearly completing the installation but not quite. So then I upped her memory to 2GB and put a new hard disk in and changed to opensuse 13.2. Again problems with grub2. After lots of researching I discover that the 13.2 DVD installs everything using btrfs partitions and GRUB2 is incompatible with it! How did this get past the beta?
I have now reinstalled it using ext4 for everything but when I try to login from the KDE/KDM screen I get the central window that opens and an image of a hard disk starts to appear then it loops back to the login screen. I can login to the ICEVM GUI and if I try an online update using yast or yast2 I’m informed that it can’t remove akregator, ark, bluedevil and a series of other packets because they’re not installed and this even after I manually install them… insanity. If I go into kde failsafe and start init 5 I’m told that kded.powerdevil.so isn’t there yet when I check it out it is there!
I removed the nvidia graphic card and put in radeon to avoid the usual nvidia driver problems.
Can somebody tell me how I could get past this login loop?
1 grub2 is NOT a problem with BTRFS even in 13.2. Not sure where you got that info.If you are doing LVM and/or encryption or RAID or other special setups it may be an issue. Also you did not mention if using EFI or MBR boot. I’d guess MBR but it is not clear. Also are you reusing the 11.4 home partition?
2 13.2 is at end of life that means no updates going forward. You should be able to get what in the current repos for a while
3 Your log in problem may be video driver related. You say that you are currently running an AMD card so you should be running the Open Source Radion drive which should be OK But might want to install the proprietary driver
Also it helps to tell the hardware
4 Don’t understand your problem with packages perhaps show the repos you are using
between code tabs (# in the tool bar here)
zypper lr -d
to show repo list
To add to @gogalthorp’s post: Did you verify the download / check the install media?
thank you, here are the answers as numbered:-
- OpenSuSE 13.2: do not use BTRFS as rootfs | UlduzSoft
- I realise that but after the experiences with 42.2 and 42.1 I was stepping backwards until I found one that would complete the installation.
- M/B asrock 775vm600, 2GB RAM, ATI Radeon Sapphire 128MB (R420 Radeon X800) CPU Intel P4 3GHz
- zypper lr -d :-
repo-non-oss
repo-oss
repo-source
repo-update
repo-update-non-oss
Yes that’s standard. I have been using SuSe since 7.3.
I do have a big bone to pick about the install media check why do they only give SHA256 check while K3B needs the MD5 checksum? And I can no longer find the MD5 check number on the Suse site!
As a tongue in cheek aside I would nominate the Suse installation process as Murphy friendly zone 
If btrfs bothers you, the installer provides all kinds of options at the partitioning phase. Is it possible the disk has been used in a UEFI / Secure boot system, and hence has a GPT partition table instead of MBR, where the system you’re installing on is a non-UEFI one?
We like to see the Repo URL rather then just the arbitrary name. Mixing OS ver repos can cause odd stuff Those are probably alright just be sure that the URLs all point to 13.2 repos
The post thread you reference does not seem to indicate a problem with grub. I did not read the whole thing. I do seem to remember some BTRFS problem back then but the fix was in the first update
Your problems are probably video related . When did you switch from NVIDiA to AMD??
You can generally sidestep video problem by using nomodeset at boot which should give you a GUI at least and allow you to install a proprietary driver
zypper lr -d # | Alias | Name | Enabled | GPG Check | Refresh | Priority | Type | URI | Service
--+---------------------------+------------------------------------+---------+-----------+---------+----------+--------+-----------------------------------------------------------------+--------
1 | openSUSE-13.2-0 | openSUSE-13.2-0 | Yes | ( p) Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-Optiarc_DVD_RW_AD-7200A |
2 | repo-debug | openSUSE-13.2-Debug | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/distribution/13.2/repo/oss/ |
3 | repo-debug-update | openSUSE-13.2-Update-Debug | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.2/ |
4 | repo-debug-update-non-oss | openSUSE-13.2-Update-Debug-Non-Oss | No | ---- | Yes | 99 | NONE | http://download.opensuse.org/debug/update/13.2-non-oss/ |
5 | repo-non-oss | openSUSE-13.2-Non-Oss | Yes | ( p) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.2/repo/non-oss/ |
6 | repo-oss | openSUSE-13.2-Oss | Yes | ( p) Yes | Yes | 99 | yast2 | http://download.opensuse.org/distribution/13.2/repo/oss/ |
7 | repo-source | openSUSE-13.2-Source | Yes | (r ) Yes | Yes | 99 | yast2 | http://download.opensuse.org/source/distribution/13.2/repo/oss/ |
8 | repo-update | openSUSE-13.2-Update | Yes | (r ) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.2/ |
9 | repo-update-non-oss | openSUSE-13.2-Update-Non-Oss | Yes | ( p) Yes | Yes | 99 | rpm-md | http://download.opensuse.org/update/13.2-non-oss/ |
I hope this is OK. I had to do zypper lr -d >home/myhome/zypper.txt then copy and paste the contents. Is there a quicker way?
Remove the first one anyway. It points to a CD/DVD drive.
EDIT: and set the others to NOT refresh. Once you’ve got the content of those repos, it’s no use to refresh them, since they won’t change anymore…
I’ve posted the repo list
the btrfs problem was another chicken and egg problem, even if the solution was in the first update how could I update if all I’ve got is a black screen with GRUB in the top left corner and no virtual consoles to go to yet.
To be quite honest this has been going on for something like 2 months now so I’ve tried practically everything hence the subject unlimited problems. I have been changing M/b’s, HDD’s, I’ve upped the memory to 2 GB (from 1GB) somewhere in the middle of all this I thought I’d eliminate the nvidia problems by putting the ATI card in. It does have the nomodeset option activated. I should also point out that I’m a Murphy magnet.
It is unclear if you now have a installed system that boots to a GUI or not
nomodeset is a temp solution to video driver problems. It uses primitive drivers that should work with any card. More or less. Exactly how are you invoking nomodeset??
Is/was (since you changed things) UEFI or BIOS based. It maters how you install which methods you use. Maybe that is were you initial problems came from?
You can boot to terminal (runlevel 3) and run yast, zypper or other utilities
If you are running the commands from a console from a GUI you should be able to mark text copy and paste. Use the console menu. If from a terminal then re direct to a file is the way
What we need now is how things are configured and running today the rest is water under the bridge
FYI I run 42.2 with an NVIDIA 630 based card with no problems. Older cards can be an issue. I don’t use BTRFS but that is a personnel preference at this time. I don’t know anything seriously wrong with BTRFS. Works fine for most if they give root enough space. But that is a snapper issue not BTRFS itself… Before 42.2 I ran 13.2 with out problem. I don’t run AMD GPU’s so don’t keep up with them so maybe someone with more AMD experience can jump in
Thanks for your help. I can get into an iceVM GUI. If I try to login to a KDE session when I give it the password it opens a small central window as it should and an icon of a HDD starts to appear but then it just stops and returns to the login screen. So I have to select the iceVM option from the spanner at the bottom left of the login screen. If I try the last option on that list ‘failsafe’ I think it will open a console and when I run init 5 or startx it gives me a 'kded_powerdevil.so missing notice, But if I go to /usr/lib64/kde4/ the file kded_powerdevil.so is there! I will logout now and retry that just to confirm what I just wrote. I will also do a reboot to check the actual boot command line options.
Don’t run startx or init 5 there, you are already in runlevel 5 running X!
You can try to run startkde to start the desktop, you can try that in IceWM too.
It will hopefully give some error message(s) that may point to what’s wrong.
And/or have a look into/post the file ~/.xsession-errors-:0 (but that gets deleted when you login again).
I would also try to create a new user account and see if that one can login or not.
PS: /usr/lib64/kde4/kded_powerdevil.so is part of the package kdebase4-workspace, you definitely have that installed because otherwise you wouldn’t even be able to select KDE nor would see the “small window” that appears.
But maybe check whether all files are actually there:
rpm -V kdebase4-workspace
No output means that it’s fine.
Hi wolfi long time no hear.
ale@dhcppc1:~> startkde
startkde: Starting up...
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
KDE Daemon (kded) already running.
kbuildsycoca4 running...
kbuildsycoca4(4283) KMimeTypeRepository::parents: "/usr/share/mime/subclasses" refers to unknown mimetype "application/vnd.ms-excel.sheet.binary.macroEnabled.12"
kbuildsycoca4(4283) KMimeTypeRepository::parents: "/usr/share/mime/subclasses" refers to unknown mimetype "application/vnd.ms-excel.addin.macroEnabled.12"
kbuildsycoca4(4283) KMimeTypeRepository::parents: "/usr/share/mime/subclasses" refers to unknown mimetype "application/vnd.ms-powerpoint.slideshow.macroEnabled.12"
kbuildsycoca4(4283) KMimeTypeRepository::parents: "/usr/share/mime/subclasses" refers to unknown mimetype "application/vnd.ms-excel.sheet.macroEnabled.12"
kbuildsycoca4(4283) KMimeTypeRepository::parents: "/usr/share/mime/subclasses" refers to unknown mimetype "application/vnd.ms-powerpoint.presentation.macroEnabled.12"
kbuildsycoca4(4283) KMimeTypeRepository::parents: "/usr/share/mime/subclasses" refers to unknown mimetype "application/vnd.ms-word.template.macroEnabled.12"
kbuildsycoca4(4283) KMimeTypeRepository::parents: "/usr/share/mime/subclasses" refers to unknown mimetype "application/vnd.ms-excel.template.macroEnabled.12"
kbuildsycoca4(4283) KMimeTypeRepository::parents: "/usr/share/mime/subclasses" refers to unknown mimetype "application/vnd.ms-powerpoint.template.macroEnabled.12"
kbuildsycoca4(4283) KMimeTypeRepository::parents: "/usr/share/mime/subclasses" refers to unknown mimetype "application/vnd.ms-word.document.macroEnabled.12"
kbuildsycoca4(4283) KMimeTypeRepository::parents: "/usr/share/mime/subclasses" refers to unknown mimetype "application/vnd.ms-powerpoint.slide.macroEnabled.12"
Could not open library ksmserver: Cannot load library /usr/lib64/libkdeinit4_ksmserver.so: (/usr/lib64/libkworkspace.so.4: file too short)
ksmserver: error while loading shared libraries: /usr/lib64/libkworkspace.so.4: file too short
startkde: Shutting down...
klauncher: Exiting on signal 1
startkde: Running shutdown scripts...
startkde: Done.
should I try to reinstall libkworkspace.so.4 ?
The result of rpm -V kdebase4-workspace was as hoped no output.
Definitely.
Apparently the file is corrupted on your hard disk for some reason.
It’s part of kdebase4-workspace-libs, so do this:
sudo zypper in -f kdebase4-workspace-libs
The result of rpm -V kdebase4-workspace was as hoped no output.
Good.
But if some lib is corrupted, it may prevent powerdevil from loading too.
wolfi@amiga:~> ldd /usr/lib64/kde4/kded_powerdevil.so|grep work
libQtNetwork.so.4 => /usr/lib64/libQtNetwork.so.4 (0x00007fcd6f351000)
libkworkspace.so.4 => /usr/lib64/libkworkspace.so.4 (0x00007fcd6adcf000)
wolfi@amiga:~>
fantastic
ale@dhcppc1:~> sudo zypper in -f kdebase4-workspace-libs
Lettura dei dati del repository in corso...
Lettura dei pacchetti installati in corso...
Forzatura dell'installazione di 'kdebase4-workspace-libs-4.11.20-29.5.x86_64' dal repository 'openSUSE-13.2-Update'.
Risoluzione delle dipendenze dei pacchetti in corso…
Il seguente pacchetto verrà re-installato:
kdebase4-workspace-libs
1 pacchetto da reinstallare.
Dimensione complessiva scaricata: 937,0 KiB. Già nella cache: 0 B. Nessun spazio aggiuntivo verrà usato o liberato dopo questa operazione.
Continuare? [s/n/? mostra tutte le opzioni] (s):
Recupero di pacchetto kdebase4-workspace-libs-4.11.20-29.5.x86_64 (1/1), 937,0 KiB (estratto 3,6 MiB)
Recupero di: kdebase4-workspace-libs-4.11.20-29.5.x86_64.rpm ......................................................................................................................................................[fatto (390,3 KiB/s)]
Controllo dei conflitti tra file: ...............................................................................................................................................................................................[fatto]
Attenzione: Il controllo dei conflitti tra file richiede che i pacchetti non installati siano prima scaricati al fine di accedere ai relativi elenchi dei file. Si veda l'opzione '--download-in-advance' nella pagina di manuale di zypper per maggiori dettagli.
I seguenti 7 pacchetti sono stati esclusi dal controllo dei conflitti dei file in quanto non sono ancora stati scaricati:
akregator ark bluedevil plasma-nm-openvpn plasma-nm-pptp plasma-nm-vpnc python-kdebase4
(1/1) Installazione di: kdebase4-workspace-libs-4.11.20-29.5 ....................................................................................................................................................................[fatto]
Output aggiuntivo di rpm:
/sbin/ldconfig: File /usr/lib64/libkompareinterface.so.4 is empty, not checked.
/sbin/ldconfig: File /usr/lib64/libkbookmarkmodel_private.so.4 is empty, not checked.
/sbin/ldconfig: File /usr/lib64/libkomparedialogpages.so.4 is empty, not checked.
/sbin/ldconfig: File /usr/lib64/libgwenviewlib.so.4 is empty, not checked.
/sbin/ldconfig: File /usr/lib64/libgwenviewlib.so.4.14.3 is empty, not checked.
/sbin/ldconfig: File /usr/lib64/libgwenviewlib.so is empty, not checked.
/sbin/ldconfig: File /usr/lib64/libkipiplugins.so.4.6.0 is empty, not checked.
/sbin/ldconfig: File /usr/lib64/libkompareinterface.so.4.14.6 is empty, not checked.
/sbin/ldconfig: File /usr/lib64/libkbookmarkmodel_private.so.4.14.8 is empty, not checked.
/sbin/ldconfig: File /usr/lib64/libkbookmarkmodel_private.so is empty, not checked.
/sbin/ldconfig: File /usr/lib64/libkomparedialogpages.so.4.14.6 is empty, not checked.
and then I actually got past the HDD icon in the startup window I’m still in iceVM but I did :-
ale@dhcppc1:~> ldd /usr/lib64/kde4/kded_powerdevil.so|grep work
libQtNetwork.so.4 => /usr/lib64/libQtNetwork.so.4 (0x00007fc99174a000)
libkworkspace.so.4 => /usr/lib64/libkworkspace.so.4 (0x00007fc98d1c8000)
ale@dhcppc1:~>
I notice that those troublesome files I seguenti 7 pacchetti sono stati esclusi dal controllo dei conflitti dei file in quanto non sono ancora stati scaricati:
“the following 7 files (packets) have not been conflict checked because they haven’t been downloaded yet”:
akregator ark bluedevil plasma-nm-openvpn plasma-nm-pptp plasma-nm-vpnc python-kdebase4
So thanks again, I’ll do reboot now and see how it goes. I’ll let you know.
Hm, these still sound worrysome:
Shouldn’t prevent you from logging in, but the corresponding applications probably won’t work (kompare, gwenview, keditbookmarks, and kipi-plugins).
So I would recommend to reinstall those packages too:
sudo zypper in -f kompare keditbookmarks gwenview kipi-plugins
OTOH, it probably cannot be ruled out that other files are corrupted/truncated too, so it may be a good idea to run “rpm -Va” to verify all installed packages. Note that this may take quite a while though, and it likely will also display quite some false positives (e.g. certain file permissions are altered after the package installation according to the system settings, so rpm will “think” that they are wrong).
Feel free to post the output (upload it to susepaste.org or similar if it is too long) if you want somebody (e.g. me… ) to check it.
! step forward and 2 back. When I did a clean reboot I now get a green contoured screen but no login/password centre window. There are no tty’s except ctrl alt f10 which gives me the disc scan results showing surprisingly an XFS scan check after I specifically told the installation to format the partitions using ext4 file systems.
I can now only boot into rescue system mode. Even using that I saw COULD NOT MOUNT /HOME flash past on one of the failed bootups. I did mange to run the rpm -Va command once and there were some problems but I could only see them as they scrolled up the tty1 screen and don’t know where or if they were saved antwhere.
I’ll keep trying but I am considering erasing everything and starting again from zero.
At this point, I would be checking to see if your HD is failing, or if you have a bad memory stick.
The hard disk is a new one but I did install Windoze 7 Ultimate first, without using efi just a straightforward 30GB NTFS partition. I created the partition before installing anything to avoid defrag problems or the windows installation putting fixed files at the end of the disk making it a problem for the linux install.
It has now totally crashed with a vertical coloured lines crash, so I’m going to change the sound card back to nvidia and see what happens.