[opensuse] Problems with going back to 12.2
Hi all, Since I could not bear the noise the video card's fan was making, and was afraid the high temperature kills the video chip before time, decided to go back to 12.2.from 12.3. As I learned there is no fglrx-legacy driver in 12.3 for my old ATI 48xx card, so had to use Mesa instead. Going back to 12.2 is not simple. I try to install from live KDE from an USB stick (has no DVD at the moment). There is no net connection after installation and my other HDD is not mounted. The major thing is that the HDD is spinning endlessly and I cannot figure out, what does it do or what does it looking for. I could start net and mount the other HDD in the first minute ( (in repeated boot ups) while the system is usable, after that it is extremely slow or does not respond at all. The cause is somewhere in KDE I suspect, because in failsafe (not KDE failsafe) mode or in CLI the HDD does not spin madly. So I tried to update KDE from 4.8.4 to somewhat higher version and separately install Fglrx-legacy, but after that the system could not reboot. Only GRUB is seen on the screen and the system halts (though i set grub2). Any hints are welcome, how can I remedy these problems. I also have a WIN 7 on the same HDD. Thanks, Albert -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/24/2013 02:52 AM, Oszkó Albert wrote:
Hi all,
Since I could not bear the noise the video card's fan was making, and was afraid the high temperature kills the video chip before time, decided to go back to 12.2.from 12.3. As I learned there is no fglrx-legacy driver in 12.3 for my old ATI 48xx card, so had to use Mesa instead. Going back to 12.2 is not simple. I try to install from live KDE from an USB stick (has no DVD at the moment). There is no net connection after installation and my other HDD is not mounted. The major thing is that the HDD is spinning endlessly and I cannot figure out, what does it do or what does it looking for. I could start net and mount the other HDD in the first minute ( (in repeated boot ups) while the system is usable, after that it is extremely slow or does not respond at all. The cause is somewhere in KDE I suspect, because in failsafe (not KDE failsafe) mode or in CLI the HDD does not spin madly. So I tried to update KDE from 4.8.4 to somewhat higher version and separately install Fglrx-legacy, but after that the system could not reboot. Only GRUB is seen on the screen and the system halts (though i set grub2).
Any hints are welcome, how can I remedy these problems. I also have a WIN 7 on the same HDD.
Thanks, Albert
if you upgrade to KDE 4.10, which is the same as what you installed in 12.3, your system will probably run. Here is something you can try to upgrade: When you are on the grub boot screen, hit the "e" button to edit the boot script. Then down-arrow until the line that is the linux boot line for openSUSE 12.2 (make sure it is 12.2 and you don't accidentally do all this in 12.3). Hit the "end" key to go to the end of that line, type a space, and put in the number 3. Then hit f10 to boot, and you should boot into run level 3 (command line only with networking). If you know how to use zypper, you can modify, delete, and add repositories. First delete your old KDE repositories using zypper rr. Then you can add the KDE 4.10 repositories with the following commands. As root, type the following: zypper ar -f -n KR410 http://download.opensuse.org/repositories/KDE:/Release:/410/openSUSE_12.2/ KR410 zypper ar -f -n KR410_Extra http://download.opensuse.org/repositories/KDE:/Extra/KDE_Release_410_openSUS... KR410_Extra Before you do the next line, make sure that you really did delete all your old KDE repositories and the only KDE repositories you have are what you just added here. Next, do a zypper refresh. After that, you can do the following as root: zypper dup --from KR410 --from KR410_Extra This should make your KDE 4.10 for openSUSE 12.2. After you have it installed, you should be able to boot again into openSUSE 12.2 with minimal problems. At least this worked for me. -- George Olson Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | ATI Radeon HD 3300 | 16GB Box #2: 12.2 | KDE 4.10 | AMD Athlon X3 | 64 | nVidia C61 GeForce 7025 | 4GB Laptop: 12.2 | KDE 4.9.2 | Core i7-2620M | 64 | Intel HD Graphics 3000 | 8GB learning openSUSE and loving it -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
2013.03.24. 14:38 keltezéssel, George Olson írta:
On 03/24/2013 02:52 AM, Oszkó Albert wrote:
Hi all,
Since I could not bear the noise the video card's fan was making, and was afraid the high temperature kills the video chip before time, decided to go back to 12.2.from 12.3. As I learned there is no fglrx-legacy driver in 12.3 for my old ATI 48xx card, so had to use Mesa instead. Going back to 12.2 is not simple. I try to install from live KDE from an USB stick (has no DVD at the moment). There is no net connection after installation and my other HDD is not mounted. The major thing is that the HDD is spinning endlessly and I cannot figure out, what does it do or what does it looking for. I could start net and mount the other HDD in the first minute ( (in repeated boot ups) while the system is usable, after that it is extremely slow or does not respond at all. The cause is somewhere in KDE I suspect, because in failsafe (not KDE failsafe) mode or in CLI the HDD does not spin madly. So I tried to update KDE from 4.8.4 to somewhat higher version and separately install Fglrx-legacy, but after that the system could not reboot. Only GRUB is seen on the screen and the system halts (though i set grub2).
Any hints are welcome, how can I remedy these problems. I also have a WIN 7 on the same HDD.
Thanks, Albert if you upgrade to KDE 4.10, which is the same as what you installed in 12.3, your system will probably run.
Here is something you can try to upgrade:
When you are on the grub boot screen, hit the "e" button to edit the boot script. Then down-arrow until the line that is the linux boot line for openSUSE 12.2 (make sure it is 12.2 and you don't accidentally do all this in 12.3). Hit the "end" key to go to the end of that line, type a space, and put in the number 3. Then hit f10 to boot, and you should boot into run level 3 (command line only with networking).
If you know how to use zypper, you can modify, delete, and add repositories.
First delete your old KDE repositories using zypper rr. Then you can add the KDE 4.10 repositories with the following commands. As root, type the following:
zypper ar -f -n KR410 http://download.opensuse.org/repositories/KDE:/Release:/410/openSUSE_12.2/ KR410
zypper ar -f -n KR410_Extra http://download.opensuse.org/repositories/KDE:/Extra/KDE_Release_410_openSUS... KR410_Extra
Before you do the next line, make sure that you really did delete all your old KDE repositories and the only KDE repositories you have are what you just added here.
Next, do a zypper refresh.
After that, you can do the following as root:
zypper dup --from KR410 --from KR410_Extra
This should make your KDE 4.10 for openSUSE 12.2. After you have it installed, you should be able to boot again into openSUSE 12.2 with minimal problems. At least this worked for me.
Thanks you for the tips! Now I can boot into runlevel 3, but do not go further yet. Do you think I can makebrepo changes also with Yast? I am not very familiar with zypper. Regards, Albert -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2013-03-24 at 21:02 +0100, Oszkó Albert wrote:
Thanks you for the tips! Now I can boot into runlevel 3, but do not go further yet. Do you think I can makebrepo changes also with Yast? I am not very familiar with zypper.
YaST works fully in text mode, so you can use that. Probably you also have some other minimal graphical desktop installed that you might use. To find what is using your disk, you can try "iotop" in a terminal. My guess is that it is the disk indexer. - -- Cheers, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) iEYEARECAAYFAlFPZR4ACgkQtTMYHG2NR9VLJQCeJiApDLmKB+EWChLvOBQloV+2 bWUAoJSeYvkAJxyE9Xoc6Yi0f58V5F5Q =PsA8 -----END PGP SIGNATURE-----
On 2013-03-24 21:02 (GMT+0100) Oszkó Albert composed:
Thanks you for the tips! Now I can boot into runlevel 3, but do not go further yet. Do you think I can makebrepo changes also with Yast? I am not very familiar with zypper.
You could use YaST, but it's actually much much easier doing it manually if you know how to use any of the installed plain text editors, including the one in Midnight Commander if it's installed. Simply goto /etc/zypp/repos.d/ and change each instance of 12.3 to 12.2 in each of the files in that directory. Doing zypper rr and zypper ar involves a _lot_ of typing that accomplishes essentially the very same thing as changing 3s to 2s. Right before editing, do 'zypper se -s grub', then do 'zypper clean -a'. Then do the edits. Then do 'zypper ref', followed by 'zypper dup'. At this point you should be able to reboot into 12.2, but first check to see which Grub is installed, again doing 'zypper se -s grub'. If you had grub2 in 12.3 but only grub after the dup, it would be a good idea to inspect /boot/grub/menu.lst to ensure the kernel(s) present in /boot is/are the same as those in it. As an extra safety measure you might like to create a stanza manually based on the default one to specify vmlinuz and initrd to match the symlinks in /boot that have no version appendages. /boot/vmlinuz and /boot/initrd in openSUSE nearly always exist and are symlinks to the last installed kernel, even when last installed is older. I nearly always boot from stanzas that use the symlinks instead of those created by the customary upgrade or install processes. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
2013.03.23. 19:52 keltezéssel, Oszkó Albert írta:
Hi all,
Since I could not bear the noise the video card's fan was making, and was afraid the high temperature kills the video chip before time, decided to go back to 12.2.from 12.3. As I learned there is no fglrx-legacy driver in 12.3 for my old ATI 48xx card, so had to use Mesa instead. Going back to 12.2 is not simple. I try to install from live KDE from an USB stick (has no DVD at the moment). There is no net connection after installation and my other HDD is not mounted. The major thing is that the HDD is spinning endlessly and I cannot figure out, what does it do or what does it looking for. I could start net and mount the other HDD in the first minute ( (in repeated boot ups) while the system is usable, after that it is extremely slow or does not respond at all. The cause is somewhere in KDE I suspect, because in failsafe (not KDE failsafe) mode or in CLI the HDD does not spin madly. So I tried to update KDE from 4.8.4 to somewhat higher version and separately install Fglrx-legacy, but after that the system could not reboot. Only GRUB is seen on the screen and the system halts (though i set grub2).
Any hints are welcome, how can I remedy these problems. I also have a WIN 7 on the same HDD.
Thanks, Albert ,Hi all,
I reply to myself, after two night's struggle, arriving back to where I started from. As I said, managed to boot into runlevel 3, using YAST installed KDE 410 packages and did not manage to reboot. I could not read and understand the text during the process, but it complained twice about grub and initrd. After that tried several combinations of bootloader, none succeded, except this one: GRUB2 in MBR and dev/sdg ( the last option in system start settings) which is my main disk. Interestingly, this disk is called sdg upon installation and sda after that. I could only try combination with GRUB2 since for GRUB I always got some warning regrding BIOS and lb24(?) and that system may possibly will not boot. Carlos, if you thought of Nepomuk as the indexer, then it is not running. I could not execute "iotop" command, since it was not found. Next time I will try to understand what Felix wrote about GRUB settings. Until then I have to use WIN7 to do some work. Regards, Albert Regards, Albert -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/26/2013 08:59 PM, Oszkó Albert wrote:
Next time I will try to understand what Felix wrote about GRUB settings. Until then I have to use WIN7 to do some work.
- grub2 is such an improvement . . . perhaps simpler to use LILO ?? ........................... best regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Carlos E. R. -
ellanios82 -
Felix Miata -
George Olson -
Oszkó Albert