I don’t know why openSUSE 11.4 cannot boot properly by the default option openSUSE-184.108.40.206-0.5 after using “zypper ref and up” to update some packages in this morning. Even though, it can boot from failsafe option, sometime it will go to non-gui mode. To start GUI mode, i use init 3 and back to init 5.
this openSUSE 11.4 system is a fresh installation in a week. To reduce incompatibility within those packages, I use official repositories provided by Yast2 and install phpmyadmin from opensuse.org. Is it possible that affected by the previous installation of tumbleweed standard? Because this situation also happened in the previous tumbleweed installation so that i reinstalled openSUSE 11.4 and only used the standard repositories in the fresh installation. Or is it possible that affected by my out-dated computer that consists of AMD Athlon™ XP 2500+, 768MB ram and 120G harddisk.
following is my repositories copy from the output of “zypper lr”. and sorry that contain some chinese characters, it would affect the display other than Chinese users. however, i don’t how to change the output to English type temporarily. Finally, Sorry for my chinese-english .
you may need to disable all existing repos and do zypper dup again,
also you may try and change between kernels(default==>desktop)
zypper modifyrepo --all --disable
- Add the new openSUSE 11.4 repositories,
zypper addrepo --name "openSUSE-11.4 OSS" [Index of /distribution/11.4/repo/oss](http://download.opensuse.org/distribution/11.4/repo/oss/) repo-11.4-oss
zypper addrepo --name "openSUSE-11.4 Non-OSS" [Index of /distribution/11.4/repo/non-oss](http://download.opensuse.org/distribution/11.4/repo/non-oss/) repo-11.4-non-oss
zypper addrepo --refresh --name "openSUSE-11.4 Updates" [Index of /update/11.4](http://download.opensuse.org/update/11.4/) repo-11.4-update
The last argument sets an alias (a shorthand), you can also choose another alias for the new repositories in the above command.
- Search for updated openSUSE 11.4 compatible third-party repositories that you used before and add them.
Warning: Use with caution. Using third-party repositories could increase the chances that the upgrade will not complete correctly. zypper addrepo --name <name> <url> <alias>
Or, if you have URL of a .repo file:
zypper ar <url.repo>
- Now execute the full distribution upgrade.
With the above command zypper will download the required packages when it installs them. To download all packages in advance, use: zypper dup --download "in-advance"
I had this problem after a kernel update. I had to boot into openSUSE with super grub disk and reinit the grub loader so the correct kernel was referenced in grub’s menu.lst file. But of course, that may not be relevant in your case. You can see if it’s relevant by running “uname -r” and “sudo cat /boot/grub/menu.lst” and compare the kernels, see if they’re the same.
On 2011-04-30 16:36, dadaj wrote:
> this openSUSE 11.4 system is a fresh installation in a week. To reduce
> incompatibility within those packages, I use official repositories
> provided by Yast2 and install phpmyadmin from opensuse.org.
The only “official” repos are the oss, non-oss, and updates - not a single
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
In fact, this fresh installation was proceeded alike your procedure. when I opened the KDE desktop after finished the installation. Firstly, I updated the default repositories that contain three repositories: oss, non-oss and update 11.4. Then, I restart the system. and add other community repositories. then run zypper ref and up and dup.
Is it possible that the system is affected by running the extra “zypper up” after community repositories added?
I will perform your suggestion, thank your advice. ^^
Further to swerdna’s comment, there was a kernel update in the past few days from version 220.127.116.11 to 18.104.22.168 (on openSUSE-11.4) and from version 22.214.171.124 to 126.96.36.199 (on openSUSE-11.3). If one’s PC is using a proprietary graphic driver the odds are quite high that the proprietary graphic driver (Catalyst/radeon ( ‘fglrx’ ) for AMD graphic hardware and ‘nvidia’ for nVidia graphic hardware) was broken by the kernel update. In which case one needs to either install a version of the driver specifically built for the updated kernel, or one needs to rebuild the driver themselves.
dadaj, in your computer’s case, with the Radeon RV250, there is no proprietary graphic driver in use, so the problem you are experiencing is not a problem with proprietary graphic driver breakage.
You have a large number of respositories. I do not speak your language so I can note tell what repositories are enabled and which are not enabled, but my advice has always been to stay with only 4 repositories : OSS, Non-OSS, Update and Packman. With more than those there can be problems. Its possible an update from one of the other many repositories you have in place have caused this problem.
You noted in your first post “Even though, it can boot from failsafe option, sometime it will go to non-gui mode. To start GUI mode, i use init 3 and back to init 5.”
When using ‘failsafe’ your PC should be loading the low performance FBDEV video drive. With no special boot codes, your PC should load the ‘radeon’ video driver (which appear not to be working for your PC currently). With the boot code ‘nomodeset’ (and no special configuration information) your PC should load the ‘radeonhd’ video driver.
To understand better what is going wrong, you likely need to look at your log files when to boot process fails. These files are /var/log/boot.msg, /var/log/messages, and /var/log/Xorg.0.log. Do not post those files here as they are too big. If you must post them then place their contents on a paste site such as SUSE Paste.
I think your system is affected because you ran the “zypper dup” with the community repositories and possibly picked up developing or incomplete changes.
As Carlos E. R. wrote IMO, you should have run "ypper up and dup just using the 3 official repositories, UPDATE, OSS and NON-OSS.
After that completed you could run with specific community repositories to install specific applications. either using the -r option or disabling other repos with zypper mr. For instance, disable all other repos except the Packman 11.4 multimedia to update your multimedia applications.
BTW, when I add repositories using YaST2 or zypper I also reassign their priority to define my updates. My 11.4 UPDATE may have a priority of 92, 11.4 Packman Multimedia and Essential priority of 95, OSS and NON-OSS have a priority of 99, Google Chrome priority 110, and others 110 - 140 and disabled.
After removing all repositories, I added oss and non-oss to repositories. Opensuse 11.4 could boot in normal after running zypper ref and dup. However, when update repositories was added and run “zypper up” Or updated by Yast2 . Opensuse 11.4 only boot in failsafe.
What is it that you want to accomplish with “update” repositories after zypper dup?
IMHO, it’s your “update” repositories that is corrupting your install.
I guess you can re-run the UPDATE, OSS, NON-OSS zypper ref and dup which should hopefully return your system for normal booting.
Then figure out what single you “update” and single repository you need to enable for installing that “update”, ie, “update”, UPDATE, OSS, NON-OSS enabled, su -c “zypper up -r update_repo# -r UPDATE# -r OSS# -r NON-OSS# package”.
In fact, I tried to delete all repositories by Yast2 and added UPDATE, OSS, NON-OSS. then using zypper ref and dup to refresh and distribution upgrade all necessary packages. However, it cannot boot properly in normal. the second try is to delete UPDATE repository and to keep OSS and NON-OSS two repositories and rerun zypper ref / dup to downgrade all necessary packages. this allows openSUSE 11.4 boot in normal. I guess the system are recovered to normal. but when I added back UPDATE repository and run zypper up to reboot system. opensuse 11.4 cannot start in normal again. ONLY boot in failsafe.
Finally, I followed this openSUSE Lizards to install ATI driver. opensuse can boot in normal NOW.
I don’t know why my system should install ATI proprietary driver to allow in normal boot? and would it be affected by next kernel updated?
> In fact, I tried to delete all repositories by Yast2 and added UPDATE,
> OSS, NON-OSS. then using zypper ref and dup to refresh and distribution
> upgrade all necessary packages. However, it cannot boot properly in
> normal. the second try is to delete UPDATE repository and to keep OSS
> and NON-OSS two repositories and rerun zypper ref / dup to downgrade all
> necessary packages. this allows openSUSE 11.4 boot in normal. I guess
> the system are recovered to normal. but when I added back UPDATE
> repository and run zypper up to reboot system. opensuse 11.4 cannot
> start in normal again. ONLY boot in failsafe.
Configure for multikernel.
After the update, if it fails, you can still boot with the previous kernel,
and thus make certain that it is the recent kernel which is the problem.
> I don’t know why my system should install ATI proprietary driver to
> allow in normal boot? and would it be affected by next kernel updated?
There are reports of failures, specially with radeon.
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
I tried to keep kernel 2.37.1 for recovery in case of system crash but the update process didn’t allow. It let me choice to retain the old kernel Or update to new kernel. Is there another way to keep kernel before going update process?
Is there any solution for the failure reports of radeon?