SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Decided to upgrade my Suse from 43.2 to the new Leap 15.1
Bought a new Barracuda 1Tb HD.
Installed my image and Voila ! - Nothing.
On re-boot I get a black screen with my mouse pointer.
Reading through the threads posted here, I thought that it could be my old Nvidia GT208 graphics card, so at great expense I upgraded that to a new GT710. No improvement.
In rescue mode I opened a console window.
I could not get yast / yast2 to run, could not get zypper to run, so I don't know how I can get in to install Nvidia drivers or the Suse Nvidia repo.
Any ideas ?
It was a fresh install.
I used a brand new , clean Hard-drive and downloaded the image directly from opensuse.org.
During the installation I had one package fail.
libxcb-iccm4
I have downloaded the image again and burned it onto disk, but after repeating the installation with the new disk I have exactly the same situation as before.
I currently run SUSE leap 42.3 but I have some issues with it, ( display jitters )
It seems like a problem with the open source nouveau driver. Do you know how to pass boot options at the grub boot selection screen? If so, try passing:
Hello Kilgoretrout,
No, I'm not sure how to do that.
I followed the link you gave to the mint instructions.
I got to the full boot command line, ( choice was "C" Command line or "E" edit file, so I hit the "C" ).
At grub> I hit the [Tab] key and got a page full of files or directories, sorted I think alphabetically.
I could not page to the top, so I was only seeing files from "crc .... " so I missed files beginning with a and b .
There was a "linux" and also a "linux16" in there, and splash was mentioned under "xnu-splash", the only file I sort of recognised was lspci, so I entered that and I got some info but nothing that I could do much with.
I did not find the line mentioned in the link.
Hello Kilgoretrout,
I managed to get into the grub command line. ( GNU Grub v. 2.02 ) I worked out that I could scroll down !
I found the line " linux /boot/vmlinuz-4/ .... " and ending with " ... auto quiet" as outlined in your link.
I put a space after the "auto quiet" and then entered "nouveau.modeset=0", and then booted with ctrl+x
Nothing changed, I am still stuck with a black screen with my mouse pointer.
I also tried entering : "nvidia.modeset=0" , and "nv.modeset=0", and "nomodeset", and "grub_gfxmode=vesa", and "grub_gfxmode=vga" and "grub_gfxmode=1280x1024x24" , but none of these commands made any difference.
Does it matter where in the linux command line that I enter the code ?
I have also swapped out my old GT208 graphics card with my new GT710, and repeated the above process, but no luck.
Can you suggest anything else ?
Thanks in advance and kind regards
-Eps
Try scrapping all those other Grub changes to the linux line and use these instead:
remove quiet
remove splash=silent
append plymouth.enable=0
try with or without adding a 3 at the end, depending on whether you want X to start (3 means don't start X; 5 means start X, but that's the usual default)
Using all you'll see a lot of text messages scroll by during int, maybe among them some error messages constituting clues to a problem.
If you are able to login but not get a running X, try
Code:
sudo zypper rm xf86-video-nouveau
before next attempt to start X. That should enable either of your NVidia cards to run X on the modesetting DDX instead of nouveau, avoiding any need to taint the installation with NVidia proprietary drivers.
I have several old NVidia cards running on 15.1, all using the modesetting DDX. Here's one:
Code:
# xrandr
Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 16384 x 16384
DP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 598mm x 336mm
2560x1440 59.95*+ 74.92
1920x1440 75.00
1856x1392 75.00
1920x1080 74.91 60.00 50.00 59.94
1920x1080i 60.00 50.00 59.94
1680x1050 59.95
1280x1024 75.02 60.02...
# inxi -GxxSMza
System: Host: p5bse Kernel: 4.12.14-lp151.28.32-default x86_64 bits: 64 compiler: gcc v: 7.4.1
parameters: root=/dev/sda20 ipv6.disable=1 net.ifnames=0 noresume mitigations=auto consoleblank=0 vga=791
video=1440x900@60 5
Desktop: KDE 3 wm: kwin dm: N/A Distro: openSUSE Leap 15.1
Machine: Type: Desktop Mobo: ASUSTeK model: P5B SE v: Rev 1.xx serial: <filter> BIOS: American Megatrends v: 1103
date: 06/04/2009
Graphics: Device-1: NVIDIA GF119 [NVS 310] vendor: Hewlett-Packard driver: nouveau v: kernel bus ID: 01:00.0
chip ID: 10de:107d
Display: server: X.Org 1.20.3 driver: modesetting unloaded: fbdev,vesa alternate: nouveau,nv,nvidia
resolution: 2560x1440~60Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.2 compat-v: 3.1 direct render: Yes
#
A big Thank You for your inputs, I appreciate all the help.
Here is my situation.
As you suggested MrMazda, I removed the splash quiet added plymouth.enable=0 and runlevel 3.
Result -> I get to a console window !
So I was able to load yast2 ( not graphically ) and I added the Nvidia drivers repository. But No Joy. Still could not get a GUI on re-booting.
I tried removing xf86-video-nouveau , still no Joy.
I tried removing drm-kmp-default and then install-new-recommends, and this removed /usr/src/kernel-modules/nvidia-440.31-default. This gave me back the xf86-video-nouveau that I had removed earlier !
After this I tried to reboot and I had lost my boot loader, only a snapshot 19 was left.
So I was stuck, my Latin was at an End, and so I reinstalled my image, back to square 1.
So, at least now I can get a console window, and also into yast2.
Plasma5 and plasma sessions is running.
When I type
sudo xrandr
I get "No display"
I am still open to any new ideas, and thanks to all for your help and your patience, oh , and a happy new year to All !
This is confusing. These both require X to run. Is X running now? If it is, we need to see /var/log/Xorg.0.log uploaded to http://susepaste.org/ or http://pastebin.com/ or equivalent.
Quote:
When I type sudo xrandr I get "No display"
Xrandr also requires X to run.
There's no reason I can imagine that either NVidia GPU can't work without the closed source NVidia driver, either with nouveau DDX or modesetting DDX. The modesetting is newer technology, the upstream default for NVidia, Intel and ATI GPUs (maybe for AMD too). I suggest to get the bugs out first before adding the taint of proprietary software.
I don't know oif it's relevant, but around line 70.
It says " "failed to load module nvidia ( module does not exist,0 )
Also the same for nouveau and nv
Saurland is most likely spot on.. but to give you an explanation of why he's right so there is benefit from the answer...
nouveau is the open source driver for Nvidia, vs "nvidia" or "nv" which is the proprietary Nvidia driver.
It would appear that your system is looking for one or the either, but they cannot be installed simultaneously without conflict.
As such, you either install the nvidia/nv driver and remove/blacklist the nouveau driver, or you remove the nvidia/nv driver and remove the blacklist of nouveau. The commands provided most likely are the OpenSuse way of doing things (I'm not personally familiar with the usage of zypper), but every system will need to do the same thing with the drivers.
(Intel used to be the same way back in the days of the flgrx driver and download of the gtk1 based Catalyst Control Center.. mad times..)
Thanks Friends, but that has not helped either.
Can you check my syntax please,
I entered the following code as root,
" grep -i 'blacklist nouveau' /etc/modprobe.d/* "
and then I got my command prompt back, so I entered,
" zypper se -s nouveau nvidia "
and i got a list of stuff back, with a y/n so I entered "y".
At the command prompt I then entered:
" cat /proc/cmdline "
and I got back my boot load command line back.
I also checked " /etc/modprobe.d/50-blacklist.conf " but did not find reference to "nv" or "nvidia" or "nouveau" anywhere.
So I edited the file to add:
"blacklist nv" and next try was "blacklist nvidia" and last try was "blacklist nouveau"
nothing made any difference.
I don't know oif it's relevant, but around line 70.
It says " "failed to load module nvidia ( module does not exist,0 )
Also the same for nouveau and nv
Not relevant. Those (EE) lines are expected and do not represent real errors. The NV module has been all but useless since the advent of KMS. For nouveau and nvidia, EE is expected, because those two drivers are not installed. Shortly after the nv EE line you'll see that loading modesetting_drv.so did not result in EE. That's the default competent DDX. Later down you'll see a lot of modeset(0) lines. They confirm modesetting_drv.so loaded and is doing its job. There are no EE lines following modesetting_drv.so. Thus, it is apparent X is actually working as expected, so your problem must be something else.
I suspect your problem is sddm installation failed or became corrupted or was replaced with some other DM. Let's see which are installed:
and the status of the one on which any of those other than xdm are listed as enabled, e.g.:
Code:
systemctl status sddm
Sddm is the one normally installed and configured when the KDE Plasma role is selected at installation time. If Gnome had been selected, then gdm rather than sddm would have been installed. With other DEs, lightdm may have been preferred. It could be that none are both installed and properly configured.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
