On 12/21/2016 4:50 PM, Carlos E. R. wrote:
I am not sure what to do about /boot/efi. Microsoft has already
created an EFI boot partition in a 260MB FAT partition on the SSD drive. Again my instincts tell me to let the Leap42.2 installer install the /boot/efi partition on the second drive so as to keep the GRUB boot loader stuff separate from Microsoft's boot loading stuff, No, /boot/efi is not grub. It is... well, UEFI things. I think both systems should share the same EFI partition, but I have very little experience in this.
Thanks again Carlos for your thoughts, I don't have a lot of experience with these EFI partitions either and poorly grok what is going on also. I have managed to get very close to having a working Leap 42.2 running but unfortunately I ran into yet another problem... Deciding to be cautious and not touch the Windows EFI partition, so I can continue to use the BIOS to select it for booting up, I went ahead and installed Leap 42.2 on my laptop. I reconfigured the partitioner to install the / and swap partitions on my SSD drive and let the installer install /boot/efi and /home on my 7200RPM drive like it wanted to by default. My first attempt seemed to go well until I tried to bring up Leap 42.2 and when I reached the KDE desktop all I got was a black screen with just the cursor showing. (The cursor did respond to mouse movements, but it was useless to do anything with it.) On my second attempt to install Leap 42.2 I vaguely recalled having seen a similar problem in the past and the solution was to not only install everything that the installer selects by default, but to have YaST also install all recommended packages as well. This time everything worked and I was able to bring up Leap 42.2 and see the KDE desktop. I then configured my network and had YaST get all the latest updates and install them as well. However when I decided to reboot my laptop I got an error message saying the ksmserver-logout-greeter had crashed. Both the logout and shutdown buttons in the startup menu were unresponsive and the reboot button simply kept displaying this same error message. So in a konsole I su'd to root and forced a reboot. But unfortunately the GRUB boot loader also failed and this time it did not show me the menu to select which operating system to boot up. Instead it drops into the low level GRUB console which has a limited set of command lines that one can use. I don't have any idea of what to do or can be done with GRUB directly, so I simply decided to try and reinstall Leap 42.2 again... (I did fool around with it a bit with a couple of innocuous looking GRUB commands and one thing I saw was that the ls command was listing fd0 but reporting some kind of error about fd1. I am guessing/suspect fd1 may be my 7200RPM drive so perhaps something is getting clobbered in the /boot/efi partition?) During these installations I was also getting a warning message telling me that using the default Nouveau drivers was experimental and dangerous so on my third attempt I tried it with using the other option the dialog mentioned - a software emulator instead of the Nouveau driver. I did everything else as I reported above, configured my network settings and getting the latest updates. Same results as I described above. On my fourth attempt, thinking that the Nouveau driver might be the cause of this problem, when I reached the KDE desktop I added the NVidia repositories using YaST and had YaST again install all updates and recommended packages. That got the NVidia drivers loaded, but unfortunately I still get the ksmserver-logout-greeter crash and lose the GRUB menu of OS choices upon rebooting. It is interesting that immediately after I complete the installation process and first boot up the laptop, the GRUB menu of OS choices does show up as one would expect. But when I reboot, AFTER running Leap 42.2 and the KDE desktop, I lose the GRUB menu and get dropped into the low level GRUB command line environment. I wonder if this is connected to the ksmserver-logout-greeter crash since that is the only other anomaly that I see happening. Anyone got any ideas or suggestions, gosh I feel like I am awfully close to getting this working! Thanks again.... Marc.. -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org