i upgraded to 12.3 from 12.2 using 3 repos (oss,non-oss and update of 12.3) and zypper dup from init 3.
It took me 1H30 hour and seemed ok, after the install i removed fglrx-legacy for i have an amd HD 4850 and itâs not supported anymore.
Then i did a reboot, but it went wrong (using shutdown -r now) it would not stop down and reboot as usual. I waited and then had to turn the pc off manually.
Reboot showed me the usual screen but no keyboard was available : not ctrl/alt/Fx or Backspace_twice or Del would work for example. No way to use escape at the boot screen (grub2).
I then had a black screen, pc monitor light is blue (On) but only a black screen and nothing can be done but turning the pc Off manually.
After maybe 3 or 4 times rebooting it finally went to the desktop ok , i was able to update my repos for 12.3 , i upgraded KDe to 4.10 for something like 255 packages and then rebooted the pc.
Since then it seems the pc will only boot after 3 or 4 times each time i need it.
What can i do to improve this ?
thanks
When you say it takes 3 or 4 reboots to get it to work, is that because of a video problem or a keyboard problem? You gave a short dissertation on your upgrade process but did you consult this guide on doing it properly? SDB:System upgrade - openSUSE Wiki One could do the upgrade again OR you could just do a clean install of openSUSE 12.3, but doing a custom partition where you mount all of your old partitions in the same locations and names, but only reformat your / root partition and keeping your /home and other partitions just as they were. This maintains all personnel settings while requireing you reload all applications and redo all system settings. The latter method is the way I decided to âupgradeâ my main PC. When an upgrade goes south, so to speak, its hard to know exactly what went wrong or if you have a distro problem you would have had anyway. Video issues can be solved sometimes by upgrading the Linux kernel, perhaps up to 3.8 out right now, but I would reread the upgrade procedure to see if you left out something.
i reread the procedure just in case, i did a a bit differently but did it ok as iâm used to it, i guess dvd clean install is still the best option.
Iâm already using last kernel and re ran mkinitrd just in case.
# uname -r
3.8.3-1-desktop
iâve been told xorg.conf could disturb, it this wrong ?
You donât have a âxorg.confâ file there in /etc/X11 and the file is not needed. Surely a hardware problem is bad but there is no way for me to evaluate just what that might mean on your system. Do you wish to expand on the hardware issue you think you might have?
iâd like to understand whatâ going on, yes iâve looked for it already , but could not find the -exact- problem (yet). i donât like it when problem occurs, specially when i donâ get where they are coming from. Moreother i think itâs always a good way to learn more
On 2013-03-23 15:16, manchette fr wrote:
> i reread the procedure just in case, i did a a bit differently but did
> it ok as iâm used to it, i guess dvd clean install is still the best
> option.
I have a small extra partition where I test the target distro before an
upgrade. That is, I install fresh in that small partition and see if
everything works right. If it does, then I upgrade on the main partition.
â
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 âAsparagusâ at Telcontar)
If you did not enable the ability to maintain multiple installed kernel versions (of the same release) in YaST, then older kernel versions are just gone. One would ask why you want to drop back to such an older version? I have a bash script that can fetch any kernel version you can find here:
once installed, use Kernel Source option 3, install git kernel for Linux-Stable, then input the exact kernel version you want to âgitâ. You then use SAKC to compile that kernel:
Kernels installed using SAKC operate in Parallel with those installed using YaST and it does not remove them or modify them. The only issue is if you decide to install the exact same kernel version with SAKC that was also installed by YaST which I suggest you do not do.
actually i had some difficulties again, shutdown -r now is ko, itâs not working properly.
i had to switch the pc On may be 5 times for the desktop to come, without dsl ⊠a reboot put back dsl On.
I thought taht default options (radeon/ kernel 3.7.10) would suffice, it seems it does not
i saw some other case with a different driver where it seems the problem is being similar (nouveau in their case, radeon in mine) : no boot and screen stays black.
Let me tell you what seems to work almost each time to be able to boot in kde for me :
Switch the pc On and stay there, 1st screen is like usual (but the fact i canât go on the detailed boot options), the screen thn becomes black with code, then comes the chameleon on itâs tree, and after this the screen becomes grey.
If i strike Escape after the screen is grey i come to a black screen with the code showing the boot process, then only comes the mouse cursor and then usual kde boot and desktop.
If i do not strike Escape after the screen is grey then : no boot and screen stays black , where am i then in the boot process i do not know.
Only magic keys seems to work (alt + print screen + R S E I U B), the monitorâs light becomes orange (Off) but nothing more, the pc does not reboot
So I do not read French and miss much of what is said. If you are trying to manually compile a kernel as root, that is wrong. My bash script would do this automatically, you only need to run it. For good compile instructions, have a look at this blog: openSUSE and Installing New Linux Kernel Versions - Blogs - openSUSE Forums
The command before the && is running under sudo, the second is not. Thus
âmake prepareâ does not have permission to write files in a root owned
directory.
There are methods to make the kernel as user, not as root.
â
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 âAsparagusâ at Telcontar)