On 3/18/19 5:51 PM, Dan Čermák wrote:

Dan Čermák <dcermak@suse.com> writes:

...

Marco Varlese <marco.varlese@suse.com> writes:

...

On 3/18/19 4:10 PM, Dan Cermak wrote:

...

...

...

> Felix Miata <mrmazda@earthlink.net> 03/18/19 3:55 PM >>> Dan Cermak composed on 2019-03-18 15:11 (UTC+0100):

...

Nope, I have blacklisted everything from Nvidia & Nouveau, so only the Intel driver should be running.

Actually it likely shouldn't. Intel pays its Linux driver writers to put most of their effort into the FOSS modesetting DDX driver. The xf86-video-intel DDX is in maintenance mode, having had no official release since 2015.

Sorry, wrong wording: there are only Intel kernel modules loaded and no Nvidia/Nouveau kernel modules.

...

...

Also, I tried the Tumbleweed rescue disk: that one will start booting, but at some point the laptop screen just turns off and that's it.

Exactly how did you "blacklist" nouveau? Do it wrong, and you might block all DDX drivers.

Like this:

$ cat /etc/modprobe.d/99-blacklist-nvidia.conf blacklist nouveau blacklist nvidia blacklist nvidia_drm blacklist nvidia_modeset

...

Precision 5530 is a model line, not a model. Which do you have? Better yet, what is output from 'inxi -Gxx' (which reports both kernel and DDX drivers, among other useful video info if X is running)? What does cat /proc/cmdline report? Xorg.0.log?

inxi -Gxx reports:

Graphics: Device-1: Intel UHD Graphics 630 vendor: Dell driver: N/A bus ID: 00:02.0 chip ID: 8086:3e9b Device-2: NVIDIA GP107GLM [Quadro P1000 Mobile] vendor: Dell driver: N/A bus ID: 01:00.0 chip ID: 10de:1cbb Display: tty server: X.org 1.20.4 driver: N/A tty: 227x82 Message: Advanced graphics data unavailable in console. Try -G --display

/proc/cmdline:

BOOT_IMAGE=/boot/vmlinuz-5.0.2-2.gd1f1d19-default root=/dev/mapper/system-root splash=silent resume=/dev/system/swap quiet mem_sleep_default=deep nomodeset

I have added the nomodeset parameter myself as Larry recomended, that gets me to at least to a tty.

There is no Xorg.0.log, as I don't automatically start X on boot. However when launching it with nomodeset added, startx fails with not being able to load the i915.ko kernel module.

That's interesting...

Ok, at least this mystery is solved: I removed xf86-video-intel and now X is starting again (haven't tried with nomodeset though, I am currently on a custom 4.20 where nomodeset is not required). I don't have that at all on my system which is running kernel 5.x...

Maybe, try to simply blacklist that and restart your machine with the 5.x kernel...?

...

...

I did update and I also have the Intel card which requires the i915 kernel module. It all works seamlessly. :/

Might be some differences in the actual CPU model?

...

Do you see anything in the "dmesg" when trying to load the kernel module itself?

mvarlese@localhost:~> sudo lsmod |grep i915 i915 2158592 28 i2c_algo_bit 16384 1 i915 drm_kms_helper 204800 5 i915 drm 499712 16 drm_kms_helper,i915 video 49152 3 dell_wmi,dell_laptop,i915

mine looks like this: Boreas:~ # lsmod |grep i915 i915 2158592 0 i2c_algo_bit 16384 1 i915 drm_kms_helper 204800 1 i915 drm 499712 2 drm_kms_helper,i915 video 49152 3 dell_wmi,dell_laptop,i915

So not sure why X is even trying to load the kernel module at all?

There is nothing in the log, because Xorg is started as an unprivileged user and thus cannot load kernel modules.

Nevertheless, I am not sure if this is the right track, as I only got this far because I appended 'nomodeset' to the boot command line. Maybe it is messing with the driver?

...

mvarlese@localhost:~> uname -a Linux localhost.localdomain 5.0.1-1-default #1 SMP Mon Mar 11 06:36:03 UTC 2019 (8c6a826) x86_64 x86_64 x86_64 GNU/Linux

...

-- Marco Varlese | Architect Developer Technologies SUSE LINUX GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg

On 3/18/19 6:33 PM, Felix Miata wrote:

In your case that's both the modesetting DDX provided by the server, and the optional antique xf86-video-intel.

xf86-video-intel is from a recent git snapshot thus cannot be called antique (IMHO). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 3/18/19 6:55 PM, Felix Miata wrote:

...

xf86-video-intel is from a recent git snapshot thus cannot be called antique (IMHO). Apparently you didn't read the link I provided that explains.

[quote]There is no Intel-specific driver provided primarily for non-ancient Intel gfx. Intel pays its Linux driver developers to put most of their effort into the FOSS modesetting DDX driver. The xf86-video-intel DDX is in maintenance mode, having had no official release since 2015.[/quote]

Maybe something is escaping me but that's a lot of commit for a dead driver: https://github.com/freedesktop/xorg-xf86-video-intel/commits/master I use this driver without problem on my 2018 laptop using the Intel UHD 630. The only thing I had to do is to add "Option" "DRI" "3" to fix some issues with the compositor (it uses DRI2 by default). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

...

I use this driver without problem on my 2018 laptop using the Intel UHD 630. The only thing I had to do is to add "Option" "DRI" "3" to fix some issues with the compositor (it uses DRI2 by default). Whatever works for you. There is good reason both exist. Old Intel GFX aren't supported by the newer technology DDX.

Optimus users at least potentially can run both GPUs on a single DDX. That suggests a shorter code path and better performance.

xf86-video-intel gets utilized either because hardware is too old, and/or because openSUSE installs optional DDX drivers by default, and/or because of what /etc/X11/xorg_pci_ids/modesetting.ids does or doesn't contain, and/or because a user has explicitly configured it.

I have two plain HD 630 running TW and 15.1 on the upstream DDX default. Neither of my 630 require any DRI or any other Xorg options to produce satisfactory behavior. I didn't have to do anything more than not have the optional xf86-video-intel installed. I do have older Intel GFX running TW that require the old tech DDX.

On 3/18/19 7:55 PM, Felix Miata wrote:

Whatever works for you. There is good reason both exist. Old Intel GFX aren't supported by the newer technology DDX.

Optimus users at least potentially can run both GPUs on a single DDX. That suggests a shorter code path and better performance.

xf86-video-intel gets utilized either because hardware is too old, and/or because openSUSE installs optional DDX drivers by default, and/or because of what /etc/X11/xorg_pci_ids/modesetting.ids does or doesn't contain, and/or because a user has explicitly configured it.

I have two plain HD 630 running TW and 15.1 on the upstream DDX default. Neither of my 630 require any DRI or any other Xorg options to produce satisfactory behavior. I didn't have to do anything more than not have the optional xf86-video-intel installed. I do have older Intel GFX running TW that require the old tech DDX.

The "modesetting" driver sure works fine with my UHD 630 and uses DRI3 by default. However, on my Optimus laptop blessed by a Quadro P600, neither "modeseting" nor "intel" work out of the box until manually adding to Xorg config the proper BusID option with the PCI ID of the intel adapter is required (with both drivers) else it is confused and ends up with a black screen (nouveau and nvidia drivers are blacklisted). And I do not even speak of the shitshow that "nouveau" is which does not work AT ALL unless the NVIDIA Card is the only one seen by the system (Can be set in BIOS). Not that it is the Nouveau's devs fault, but the experience for new users installing Linux on such laptop is terrible (black screen). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 3/19/19 12:23 AM, Dan Čermák wrote:

The nomodeset setting was a temporary addition, that I added to the cmdline of the 5.0.x kernel. If that option is absent, then kernel 5.0.x will boot into a black screen, but 4.20.y will not. Adding nomodeset "fixes" the black screen and I actually can get to a TTY, but X will then not start (which makes sense, since KMS is off).

Nevertheless, something (but probably unrelated) is also off with my Xorg config, as I *need* to have xf86-video-intel installed. Otherwise Xorg will not start with a good (=4.20) kernel.

Make sure you either don't have a file like </etc/X11/xorg.conf.d/20-intel.conf> or its contents are commented out. Make sure that there is no

Section "SomeDevice" ... Driver "intel" ... EndSection anywhere in the Xorg configs. If there is, replace "intel" with "modesetting".

Make sure xf86-video-intel is uninstalled. Make sure there is no 'nomodeset' on the kernel parameters. Do

# dracut -f

Reboot. If you still cannot get to the graphical target, post the Xorg logs (I don't think you have had). To do so, at boot time edit the kernel command line (you already know how to do this) and append

system.unit=rescue.target Then post the output of </var/log/Xorg.0.log> or </var/log/Xorg.0.log.old>. To know which one, look for a line /var/log/Xorg.0.log which contains the timestamp when the server was attempted to be started. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org