On my previous laptop, I turned the nvidia card off by default. You need to install ‘bbswitch’ to do so. For the rendering in KDE ( Systemsettings - Display and Monitor - Compositor ) I switched it to openGL2, turned off the desktop effects and I was completely satisfied. Also, like suggested, you could use ‘nomodeset’ as a kernel parameter ( YaST - Bootloader - Kernelparameters - add ’ nomodeset’ after ‘showopts’ ).
Just ‘bbswitch’ and not have to put in bumblebee first(or at all)?
I tried the ‘nomodeset’ for the install that I can’t get to boot in the GRUB2 edit mode and that did no good. (it boots to a blank screen with a cursor from which I can get to terminal mode.
Can I open YaST from the format 3 full text screen and have a chance of adding ‘nomodeset’ and getting the installed version to work?
]Can I open YaST from the format 3 full text screen and have a chance of adding ‘nomodeset’ and getting the installed version to work?
Yes, you can use the ncurses YaST user interface to modify the boot parameters, and they will take effect at next boot. This will permanent, so you’ll need to modify again if you later need to remove it.
I’ve done everything with the full screen terminal I know how to do, and nothing has worked so far to bring back my installed version.
Thanks, nothing so far has been able to get me to the installed version.
Looks like another install tomorrow, and hopefully I can get things in and working before the hybrid graphics decides to mess it up again.
Thanks Knurpht and deano_ferrari again for your help.
I read about the hybrid graphics in the release notes(and in other openSuse docs) and went through the rest of the notes as well.
I don’t know what is the way forward. But so far nothing gets me farther than that blank screen with a cursor, and I have let it set for 20 to 30 minutes to see if it would do anything. Nope, doesn’t.
<are you the ‘ferrari’ in another Linux/Unix forum?>
I don’t know what is the way forward. But so far nothing gets me farther than that blank screen with a cursor, and I have let it set for 20 to 30 minutes to see if it would do anything. Nope, doesn’t.
Waiting won’t help. It’s a graphics issue that needs to be sorted (although it’s not clear to me why ‘nomodeset’ didn’t help here). Not being over your shoulder adds to understanding how far you got and/or what wasn’t working for you.
Anyway, you mentioned…
I tried the ‘nomodeset’ for the install that I can’t get to boot in the GRUB2 edit mode and that did no good. (it boots to a blank screen with a cursor from which I can get to terminal mode.
Were you not able to boot to runlevel 3 by editing the GRUB2 boot parameters on the fly, and entering ‘3’ at the end of the linux boot stanza? Here’s a graphical guide on how to do that with GRUB2 (it references Fedora, but applicable to openSUSE as well)…
Assuming you have network connectivity at runlevel 3 (eg wired ethernet), then you should be able to proceed by following the bumblebee guide?
I tried the ‘nomodeset’ for the install that I can’t get to boot in the GRUB2 edit mode and that did no good. (it boots to a blank screen with a cursor from which I can get to terminal mode.
Another way to proceed might be to get to a VT as quickly as possible, login as root and do
I didn’t add a 3 to the linuxefi line, but is easy enough to do, as will the init 3.
But remember my level of knowledge after I get to runlevel 3 or a VT.
You folks are long time users, and I have been at it for only a few weeks at most, and am basically dazed and confused in terminal modes.
But I will try. Making a couple directories and cd to them no problem.
But fumble fingering a laptop keyboard to enter the symlinks without errors may destroy a few more brain cells.
I got bumblebee in and nouveau blacklisted per the SDB for bumblebee. I did not do the directories and symlinks way down that page under the nVidia driver ‘easy’ instructions.
Still no complete boot. I still get the bouncing white square, the green Leap logo and a very quick flash of a login screen(that goes to GUI on the desktop), and then right to the black screen with a cursor(not the Leap cursor). So I take that as it is trying, but there is still something blocking a full boot.
One thing I did notice is that in the linuxefi line it shows the disk identifier followed by ‘-part10’ If that is a partition for booting, partition 10 is my swap partition. I can’t get a capture of that screen nor fdisk -l for that install. I tried with the iPad camera but it is too blurry to read.
One thing I did notice is that in the linuxefi line it shows the disk identifier followed by ‘-part10’ If that is a partition for booting, partition 10 is my swap partition. I can’t get a capture of that screen nor fdisk -l for that install. I tried with the iPad camera but it is too blurry to read.
**optirun --status = Bumblebee status: Ready (3.2.1). X inactive. Discrete video card is off.
**
These are the steps I followed (are there others?)
Install bumblebee
Installing bumblebee is pretty straightforward:
sudo zypper in bumblebee bbswitch
Add yourself to the bumblebee group (here “username” should be replaced with your real username):
sudo usermod -aG bumblebee username
Then enable and start bumblebee:
sudo systemctl enable bumblebeed
sudo systemctl start bumblebeed
Blacklist nouveau (even if you plan to use nouveau driver):
echo “blacklist nouveau” | sudo tee -a /etc/modprobe.d/99-local.conf
sudo mkinitrd
If you plan to use 32bit apps (like steam), install required libraries: .
sudo zypper in Mesa-libGL1-32bit libX11-6-32bit primus-32bit I <<<<DIDN’T DO THIS 32bit apps thing
Ok, that checks out okay. The intel graphics hardware should be active when the X-server starts. The next step is to find out why the X-server fails to start. Can you examine /var/log/Xorg.0.log for errors please? The easiest way to do this from a VT is to invoke
cat /var/log/Xorg.0.log|more
and take pictures to share here perhaps.
If you’re staying with the nouveau (open source) driver then that should be all that is required (going by the guide).
I did take the nouveau.modeset=0 from the linuxefi line in Yast boot loader. Mistake?
Pictures will be a while. Have to get them to a place form iPad to where I can move them to openSuse. (thre 1r 16 of them and a lot of them seem to me to not be what are needed, But they will come via susepaste.
I did take the nouveau.modeset=0 from the linuxefi line in Yast boot loader. Mistake?
That should be ok. It should be blacklisted in /etc/modprobe.d/99-local.conf anyway, and only intel graphics active anyway (as ‘optirun --status’ confirmed already).
Pictures will be a while. Have to get them to a place form iPad to where I can move them to openSuse. (thre 1r 16 of them and a lot of them seem to me to not be what are needed, But they will come via susepaste.
All good Bill. I’ll review them soon. Meanwhile, could you please check the BIOS settings of this machine? From what I’m reading, some machines implement Optimus graphics with the BIOS having control of the integrated and discrete video hardware, while others don’t have any applicable settings. Just see what you can find there.
(