Now I’m a beginner and I don’t know much but I did try lots of different distros and each time it would crash with a similar message (on Elementary OS and Fedora it was something about Bad RIP Value - Kernel Panic).
If you need any logs or info, I can provide it.
PS I should really clean that screen
Well, drm_kms_helper is used by all KMS drivers, so radeon as well.
I googled for your model and came up with an nvidia chip, but probably there are different variations.
That proves once again that just specifying the laptop model is not enough information…
Recovery mode seems to be working, it’s still loading…
EDIT: It says Reached target graphical interface and green OK left of it (along with other commands with mostly OK) and it hangs there.
Well, that’s bad. So you do have at least one other problem.
Can you get to a text mode login when pressing Ctrl+Alt+F1 and login there?
I just see that I misinterpreted your original post.
The picture is from the crash during the update, right?
Does a normal boot show the same crash?
Anyway, apparently the update has been interrupted somewhere in the middle, that’s probably why even recovery doesn’t work.
Try to run “zypper up” in text mode again to complete the update, the laptop should hopefully boot again then.
One problem might be to get an internet connection in text mode though.
How do you connect? A wired ethernet connection should just work, but if you use a wireless connection with NetworkManager, it’s a bit more difficult.
Okay, my problems with this laptop are really weird… That error did crash during zypper up but I can use the OS normally until it crashses. Right now, I managed to add a Chrome repo, and currently it’s installing. I also did zypper ref and zypper up and nothing crashed.
I’m used wired connection for installation but now I’m using wireless.
Do you have any other advice what to do to ensure that the system is running normally? I’ve been wanting to learn and use Linux for a very long time but each time I install any distro it just randomly crashes. And even though I do have experience with computers, random kernel panics make me really angry because I feel powerless since I have absolutely no idea what’s going on!
I mean I even updated my BIOS and VGA BIOS to see if that works, and it does in Windows (everything works flawlessly) but in Linux it keeps being weird!
This mostly points to hardware problems (maybe overheating), or issues with some drivers, the graphics driver probably.
Since you have a Mobility Radeon HD 5430/5450/5470 according to your output, I would suggest you try to install AMD’s proprietary fglrx graphics driver.
This might give you better performance and stability, and supports your graphics chip powermanagement better, so the laptop should run cooler.
See here for how to install it: http://en.opensuse.org/SDB:AMD_fglrx
If your system is running too unstable to even install that driver, try to switch off KDE’s desktop effects if you’re using KDE (press Shift+Alt+F12).
It is working now, however I’m expecting it to crash randomly. I would like to try AMD proprietary drivers but before I do that, is there something I can do in case it fails? Like make a system restore point or something (obvious Windows user here ) which I could revert to in case anything bad happens?
Hm, I don’t see anything wrong there either. Even all the files have the correct filesize.
The only thing left that’s mentioned in your log is /usr/share/X11/xorg.conf.d/, this contains only /usr/share/X11/xorg.conf.d/10-evdev.conf here, so please post that as well, and verify that the directory contains nothing else.
Other than that I would suggest to just delete 50-device.conf, it only contains comments anyway, then reboot and post /var/log/Xorg.0.log if it still doesn’t work.
I’ll try deleting that file you mentioned and rebooting!
Maybe there’s something in there that got lost during pasting.
The same applies to /etc/X11/xorg.conf.d/11-evdev.conf as well though, so maybe do try to delete that one too if it still doesn’t work.
We can get files back easily enough afterwards, by just re-installing the corresponding packages.