When I select KDE as a DE in installer, openSUSE Leap 42.1 always freezes at this point (I can’t access terminal and have to do a hard reset): http://i68.tinypic.com/2hggv3l.jpg
The issue is repeatable, I installed twice with KDE and rebooted several times. I also installed using Gnome and Xfce desktops, both seem to work. I doubt that this is a user error since:
This was a fresh install, I formatted my hard drive using the default partition scheme and file systems
It only comes to mind that I removed Icedax because of complications before installing Brasero. I really don’t know if Icedax is essential part of Linux/openSUSE.
I also added all online repositories excluding “expert” ones in the installer.
openSUSE Leap 42.1 64-bit
Intel Core i7-4770K @ 3.50GHz
16,00Gt Dual-Channel DDR3
ASUSTeK COMPUTER INC. Z87-PRO
Nvidia GeForce GTX 780 Ti
No I didn’t. Do I access Yast during boot? Feel free to tell me, I don’t really know how to access terminal in this situation.
I read that the Nouveau driver might not work correctly, I did!'t have time to install the proprietary one.
When you first install, when it comes to a stop the first time offering you a menu that includes booting from the disk, install, check the install media, etc., along the bottom you will see a number of install options including a video option that would implement nomodeset.
Have you checked your system memory?
Although I haven’t had to make changes in the BIOS in recent years, a long time ago I also made changes to slow down memory access.
Just now, I downloaded the LEAP DVD, and for one thing I do not see your screenshot after selecting the KDE Desktop… I only see that lightbulb in the very beginning when the Install selection is first made (I didn’t check but oftentimes you can hit ESC <immediately> and see the text stdout of what is happening). After selecting a Desktop (including KDE), the standard 3 tab display of the install should be seen.
By selecting ‘nomodeset’, my understanding is you disable the kernel mode setting. What does that mean ? My rather fuzzy understanding is some years, back the automatic video mode setting was moved into the kernel. But if the kernel has a problem loading the video, then by selecting nomodeset you tell the kernel not to load the video drivers but to rely instead on some other means for video driver selection. In this case, for openSUSE, I think with nomodeset and newer nVidia GPUs it will fall back to either the Vesa or some sort of Frame Buffer driver (fbdev) [more likely the latter].
This is a pretty primative graphic mode, but it will allow X to run , and once there one can complete the install, and then later use the GUI to help one figure out what went wrong. If nouveau does not work and nvidia does, then later one can install the nvidia driver followed by removing the nomodeset option.
I can complete the install with Gnome and Xfce, I don’t even know if I can set “nomodeset” outside of the installer. I was able to sign in to Xfce, restored my backups and started adding repos & installing software. Then maybe two hours later openSUSE froze all of sudden and I had to do a hard reset. Afte that I haven’t been able to sign in.
Does Novell offer paid support for individuals? I might be interested
Sure you can use nomodes set on a normal boot there is an advanced option, in it there is an option to boot to recovery this among other things uses nomodeset settings thus boots to the fall back drivers. This should only be used to get to installing the NVIIDA drivers in a GUI. You can also change to edit mode by pressing e at the boot screen and enter nomodeset at the end of the linux line.
BTW you can also boot to the command line and install NVIDIA from there. But that is another story
When it freezes is it a real freeze, or can you obtain a full screen terminal session by pressing <CTRL><ALT><F2> ?
Sorry to read that.
You could try ‘nomodest’ as noted. You press ‘e’ (I believe) at the grub boot menu, and then navigate to the linux boot line, and type ‘nomodeset’ (no quotes) at the end. If you do not know which line I mean, post here and we will try to explain better.
Definitely a “real freeze”, can’t access terminal.
Is this the correct line: " linux /boot/vmlinuz-4.1.12-1-default"… so after that just “/nomodeset”? Or is “/” requiref?
Edit: after " silent quiet showopts”.
‘Nomodeset’ didn’t really work, if I did it right. I just saw my mouse cursor and nothimg more. Xfce wallpaper quicjly flashed when I turned of my PC.
I’ve decided to switch distro. Ubuntu is practically the only distro the game developers support and they don’t help me because I’m on openSUSE. Ubuntu also has much more software packages available, I’ve already encountered five programs that I’d have to build from source in order to use.
I may install openSUSE on my secondary machine, but for everyone who games Ubuntu is really the best bet.
I figured this out, I didn’t use “/”. Nomodeset apparently worked, but I wasn’t able to boot.
Despite the problems, this was a good experience. I learned a lot about Linux in the process: the basic terminal usage, many programs don’t need GUI, backing up all user files and restoring them even on a different distro, software repositories, compiling from the source…
I definitely prefer Linux over Windows that only works as a GUI for launching proprietary games.
I need Windows for gaming, Linux still isn’t nearly good enough. I need a new hard drive so I can properly use Linux and start experimenting - RAID 0 isn’t supported that well and I wasn’t able to take disk image backups. I’ve broken Android probably over 20 times and TWRP has saved me every time.
It was a mistake to use RAID in the first place.
I’ve only just started spending time on learning how to flash Android. I rooted and flashed many android variants on an ancient Asus Transformer TF-101 tablet (it came with 3.x and I updated to 5.x, before rolling back to a recent 4.4.x variant). I’ve now given that tablet away to a friend of my wife’s (where this friend has never used a computer in her life before).
I flashed a friends Chinese Zopo ZP-500 for them sometime back, when they had a problem with the phone (broken hardware wireless) to see if burning to a newer ROM would help (it did not). Fortunately their Zopo came rooted. So I did not need to figure out how to do that.
I recently burned a new Android on my old Chinese Zopo ZP980+ (updating from Android 4.2.2 to Android-4.4.2). Rooting the ZP980+ with 4.4.2 installed was a big challenge. It turns out the ZP980+ is difficult to root. When trying to update Android, I actually ended up bricking the ZP980+ for a while, and I had to connect it to a PC to recover using a very low level mode unique to the MediaTek processor on that phone.
As of a week (ago) I now have a Xiaomi Mi 4c and I am pondering flashing a new Android on it. The phone was built for the Chinese market (which is the “c” in “4c” ) but mine had many languages on it and not just Chinese & English. Which tells me the company that I purchased the phone from applied a custom international PROM on it (and hence I won’t receive the Xiaomi Android updates - if any). Plus the custom ROM is loaded with spyware. Hence I am contemplating flashing the Xiamoi factory PROM back on the phone which will give only Chinese and English (and I will lose then the other language support).
One thing interesting about Android and Smartphones, is the situation is evolving, and it is now possible to find open source Android (GNU/Linux) implementations that one can install on their phone - where only a few years back this was much more difficult to do. A lot thou - depends on one picking a pretty popular Android phone, where there are more users available - and hence the probability of getting 3rd party custom ROM support much higher.
I’m thinking of writing a blog on using openSUSE with my Android phone (ie talk about the openSUSE apps together with android apps) that I use - but first - I want to learn some more before I start pontificating on something I know little about.