on my laptop TUXEDO InfinityBook Pro 15 v4, ssd disk=2Tb, /home EXT3 partition=58Gb, processor= Intel Core i7-8565U, RAM=32Gb, graphics card Model: “Intel UHD Graphics 620 (Whiskey Lake)” with tri boot leap 15.2, leap 15.3, windows 10
I upgraded my leap 15.2 to 15.3 via usb stick offline upgrade but I have only text login, I can login as user but no graphic login, also in recovery mode I have only text login.
how can I solve and have a working leap 15.3?
Hi,
I’d first check if the repos all are set to 15.3:
zypper lr -u
If not, change them to 15.3. Did you update after the offline upgrade?
sudo zypper up
At last check the drivers. I’m not totally sure, which are inevitable but since my laptop is an optimus with intel some of this should be there:
(I’m on 15.2, so you need other versions, of course)
kasi@pluto:~> LANG=C zypper se -s intel
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+--------------------------+------------+--------------------------------------+--------+--------------------------------
| intel-SINIT | package | 2.3-lp152.4.2 | noarch | Haupt-Repository (OSS)
| intel-cmt-cat | package | 2.0.0-lp152.4.8 | x86_64 | Haupt-Repository (OSS)
| intel-gpu-tools | package | 1.23-lp152.2.9 | x86_64 | Haupt-Repository (OSS)
| intel-hybrid-driver | package | 1.0.2-lp152.3.7 | x86_64 | Haupt-Repository (OSS)
i | intel-media-driver | package | 19.2.1-lp152.3.3 | x86_64 | Haupt-Repository (OSS)
i | intel-vaapi-driver | package | 2.4.0-lp152.1.4 | x86_64 | Haupt-Repository (OSS)
| intel-vaapi-driver-32bit | package | 2.4.0-lp152.1.4 | x86_64 | Haupt-Repository (OSS)
| intelhex | package | 1.5-lp152.3.3 | x86_64 | Haupt-Repository (OSS)
i | libdrm_intel1 | package | 2.4.100-lp152.1.4 | x86_64 | Haupt-Repository (OSS)
i | libdrm_intel1-32bit | package | 2.4.100-lp152.1.4 | x86_64 | Haupt-Repository (OSS)
| libvulkan_intel | package | 19.3.4-lp152.27.1 | x86_64 | Haupt-Repository (OSS)
| libvulkan_intel-32bit | package | 19.3.4-lp152.27.1 | x86_64 | Haupt-Repository (OSS)
i+ | ucode-intel | package | 20210525-lp152.2.17.1 | x86_64 | Hauptaktualisierungs-Repository
v | ucode-intel | package | 20210216-lp152.2.14.1 | x86_64 | Hauptaktualisierungs-Repository
v | ucode-intel | package | 20201118-lp152.2.11.1 | x86_64 | Hauptaktualisierungs-Repository
v | ucode-intel | package | 20201118-lp152.2.8.1 | x86_64 | Hauptaktualisierungs-Repository
v | ucode-intel | package | 20200616-lp152.1.1 | x86_64 | Haupt-Repository (OSS)
| ucode-intel | srcpackage | 20210525-lp152.2.17.1 | noarch | Hauptaktualisierungs-Repository
| ucode-intel | srcpackage | 20210216-lp152.2.14.1 | noarch | Hauptaktualisierungs-Repository
| ucode-intel | srcpackage | 20201118-lp152.2.11.1 | noarch | Hauptaktualisierungs-Repository
| ucode-intel | srcpackage | 20201118-lp152.2.8.1 | noarch | Hauptaktualisierungs-Repository
| xf86-video-intel | package | 2.99.917+git8674.25c9a2fcc-lp152.3.7 | x86_64 | Haupt-Repository (OSS)
| xf86-video-intel-32bit | package | 2.99.917+git8674.25c9a2fcc-lp152.3.7 | x86_64 | Haupt-Repository (OSS)
kasi@pluto:~>
I guess ucode-intel, libdrm_intel1, intel-vaapi-driver and intel-media-driver must be there.
Edit: You can also do this with YaST in CLI, just run “yast” as root.
checked, all repositories are for 15.3
zypper up says nothing to do
I don’t understand what to do here:
kasi@pluto:~> LANG=C zypper se -s intel
I guess ucode-intel, libdrm_intel1, intel-vaapi-driver and intel-media-driver must be there.
Edit: You can also do this with YaST in CLI, just run "yast" as root.[/QUOTE]Sorry for not being clear. I was suggesting to check what driver packages you have installed and showed mine as comparison.
Try
zypper se -s intel
My understanding is that at least these packages are required:
i | intel-media-driver | Intel Media Driver for VAAPI | package
i | intel-vaapi-driver | Intel Driver for Video Acceleration (VA) API for Linux | package
i | libdrm_intel1 | Userspace interface for Kernel DRM services for Intel chips | package
i+ | ucode-intel | Microcode Updates for Intel x86/x86-64 CPUs | package
If they are installed in your system you should see the “i” at the beginning of the line.
You can also use
zypper se -is intel
which will only show the installed packages.
If a package is missing, try
sudo zypper in {missing-package}
If there was a missing driver then try rebooting.
manythanks kasi 
I tried and it seems that the packages that you intend as minimun required are installed, I see a repository that 15.3 upgrade automatically installed
Update repository with updates from SUSE Linux Enterprise 15
I don’t know if it is relevant.
here is the output of
zypper se -s intel > /home/pla/zypper.intel
I used > command becouse I don’t know how to copy the screen in a text file
Loading repository data...Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+--------------------------+------------+---------------------------------+--------+-------------------------------------------------------------
| intel-SINIT | package | 2.3-2.17 | noarch | Main Repository
| intel-cmt-cat | package | 2.0.0-5.17 | x86_64 | Main Repository
| intel-gpu-tools | package | 1.23-10.63 | x86_64 | Main Repository
| intel-hybrid-driver | package | 1.0.2-bp153.1.12 | x86_64 | Main Repository
**i+ | intel-media-driver | package | 20.3.0-1.41 | x86_64 | Main Repository**
**i | intel-vaapi-driver | package | 2.4.1-1.62 | x86_64 | Main Repository**
| intel-vaapi-driver-32bit | package | 2.4.1-1.62 | x86_64 | Main Repository
| intelhex | package | 1.5-bp153.1.12 | x86_64 | Main Repository
i | kernel-firmware-intel | package | 20210208-2.4 | noarch | Main Repository
**i+ | libdrm_intel1 | package | 2.4.104-1.12 | x86_64 | Main Repository**
i+ | libdrm_intel1-32bit | package | 2.4.104-1.12 | x86_64 | Main Repository
| libvulkan_intel | package | 20.2.4-57.12 | x86_64 | Main Repository
| libvulkan_intel-32bit | package | 20.2.4-57.12 | x86_64 | Main Repository
v | ucode-intel | package | 20210525-7.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | ucode-intel | package | 20210525-3.203.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | ucode-intel | package | 20210525-3.67.1 | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
**i+ | ucode-intel | package | 20210216-2.19.1 | x86_64 | Main Repository**
v | ucode-intel | package | 20210525-7.1 | i586 | Update repository with updates from SUSE Linux Enterprise 15
v | ucode-intel | package | 20210525-3.203.1 | i586 | Update repository with updates from SUSE Linux Enterprise 15
v | ucode-intel | package | 20210525-3.67.1 | i586 | Update repository with updates from SUSE Linux Enterprise 15
| ucode-intel | srcpackage | 20210525-7.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15
| ucode-intel | srcpackage | 20210525-3.203.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15
| ucode-intel | srcpackage | 20210525-3.67.1 | noarch | Update repository with updates from SUSE Linux Enterprise 15
| xf86-video-intel | package | 2.99.917+git8674.25c9a2fcc-5.19 | x86_64 | Main Repository
| xf86-video-intel-32bit | package | 2.99.917+git8674.25c9a2fcc-5.19 | x86_64 | Main Repository
this is the output of
zypper se -s intel > /home/pla/zypper.intel.tw
in the working leap15.2 on the same hardware if it can help
Loading repository data...Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+-----------------------------+------------+--------------------------------------+--------+--------------------------------
| intel-SINIT | package | 2.3-lp152.196.1 | noarch | suse-/security(ike-scan)
| intel-SINIT | package | 2.3-lp152.4.2 | noarch | Main Repository
| intel-SINIT | srcpackage | 2.3-lp152.196.1 | noarch | suse-/security(ike-scan)
| intel-clear-sans-fonts | package | 1.00-lp152.1.1 | noarch | suse-M17N:/fonts
| intel-clear-sans-fonts | srcpackage | 1.00-lp152.1.1 | noarch | suse-M17N:/fonts
| intel-cmt-cat | package | 2.0.0-lp152.4.8 | x86_64 | Main Repository
| intel-gpu-tools | package | 1.24-lp152.6.3 | x86_64 | suse-home:/Dead_Mozay(megasync)
| intel-gpu-tools | package | 1.23-lp152.2.9 | x86_64 | Main Repository
| intel-gpu-tools | srcpackage | 1.24-lp152.6.3 | noarch | suse-home:/Dead_Mozay(megasync)
| intel-gpu-tools-debuginfo | package | 1.24-lp152.6.3 | x86_64 | suse-home:/Dead_Mozay(megasync)
| intel-gpu-tools-debugsource | package | 1.24-lp152.6.3 | x86_64 | suse-home:/Dead_Mozay(megasync)
| intel-hybrid-driver | package | 1.0.2-lp152.3.7 | x86_64 | Main Repository
i | intel-media-driver | package | 19.2.1-lp152.3.3 | x86_64 | Main Repository
i | intel-vaapi-driver | package | 2.4.0-lp152.1.4 | x86_64 | Main Repository
| intel-vaapi-driver-32bit | package | 2.4.0-lp152.1.4 | x86_64 | Main Repository
| intelhex | package | 1.5-lp152.3.3 | x86_64 | Main Repository
i | libdrm_intel1 | package | 2.4.100-lp152.1.4 | x86_64 | Main Repository
| libdrm_intel1-32bit | package | 2.4.100-lp152.1.4 | x86_64 | Main Repository
| libvulkan_intel | package | 19.3.4-lp152.27.1 | x86_64 | Main Repository
| libvulkan_intel-32bit | package | 19.3.4-lp152.27.1 | x86_64 | Main Repository
i+ | ucode-intel | package | 20210525-lp152.2.17.1 | x86_64 | Main Update Repository
v | ucode-intel | package | 20210216-lp152.2.14.1 | x86_64 | Main Update Repository
v | ucode-intel | package | 20201118-lp152.2.11.1 | x86_64 | Main Update Repository
v | ucode-intel | package | 20201118-lp152.2.8.1 | x86_64 | Main Update Repository
v | ucode-intel | package | 20200616-lp152.1.1 | x86_64 | Main Repository
| ucode-intel | srcpackage | 20210525-lp152.2.17.1 | noarch | Main Update Repository
| ucode-intel | srcpackage | 20210216-lp152.2.14.1 | noarch | Main Update Repository
| ucode-intel | srcpackage | 20201118-lp152.2.11.1 | noarch | Main Update Repository
| ucode-intel | srcpackage | 20201118-lp152.2.8.1 | noarch | Main Update Repository
| xf86-video-intel | package | 2.99.917+git8674.25c9a2fcc-lp152.3.7 | x86_64 | Main Repository
| xf86-video-intel-32bit | package | 2.99.917+git8674.25c9a2fcc-lp152.3.7 | x86_64 | Main Repository
Just for the sake that the graphics chip is defective ( I have found a few intel 630 not to work right in gen 8 CPU’s with 15.3 that worked fine in 15.2)
Add to the linux line at boot to the end of that line i915.modeset=0 - that fixed the defective ones to use a different video driver.
looks something like these 2 one for BIOS and the other for UEFI boot - what you have may be different
linux /boot/vmlinuz-5.3.18-59.5-default root=UUID=a2fe727a-9492-4a23-b8c0-ed348b9c2118 resume=/dev/sda2 splash=verbose showopts i915.modeset=0
or
linuxefi /boot/vmlinuz-5.3.18-59.5-default root=UUID=868bf3ab-5299-495e-8104-fee60868253f splash=verbose showopts nouveau.modeset=0 net.ifnames=0 usbcore.autosuspend=-1 i915.modeset=0
manythanks to everybody, it seems solved adding nomodeset to the linux line at boot as indicated in this thread
https://forums.opensuse.org/showthread.php/555021-upgrade-from-15-2-no-GUI/page2
tried also i915.modeset=0 as larryr suggested but didn’t work
That’s not a solution. It’s a troubleshooting workaround if your GPU is Intel or AMD, or of you’re using FOSS drivers for an NVidia GPU. X performance using the fallback drivers forced by disabling KMS is dismal.
https://forums.opensuse.org/showthread.php/541438-AMD-Intel-amp-NVidia-X-graphics-driver-primer
manythanks mrmazda so if I get correctly for my Intel UHD Graphics 620 (Whiskey Lake) I have to:
uninstalling the xorg-x11-driver-video package and whichever xf86-video-* package (searching “xorg-x11-driver-video” and “xf86-video-” on yast is ok?)
install the modesetting (DDX) software (searching “modesetting” and “DDX” on yast is ok?)
try if it works
uninstall the modesetting (DDX) software
install xf86-video-* for **i915 **plus **intel (DDX) **(searching “i915” and “DDX” on yast is ok?)
try if it works better or not and adopt the better one
is it correct?
Yes.
- The Modesetting DIX is standard equipment. To eliminate it requires removing the X server, thus, no X or Gnome or Plasma, etc. It supports all GPUs that have KMS support and are not too ancient or bleeding edge new.]xorg-x11-driver-video is a meta package. A meta package exists only to cause installation of some list of packages, in this case, xf86-video-.
]xf86-video-intel is the old technology DDX driver applicable exclusively to Intel GPUs. It’s the only DDX suitable for Intel GPUs roughly 15 years old or older. It can be used with nearly all Intel GPUs, but is generally characterized less than optimal for most that are supported by the Modesetting DIX.]i915 is a kernel driver that provides KMS for Intel GPUs. Without it, neither the Intel DDX nor the Modesetting DIX can function for an Intel GPU. It’s provided with each kernel package specifically for the kernel providing it.
manythanks mrmazda
as “The Modesetting DIX is standard equipment.” my 15.3 has worked until now with it, so graphic login works only with nomodeset
I installed xf86-video-intel and graphic login also works only with nomodeset
and also resume from sleep and cube desktop effect don’t work as before
is there a way to have a working 15.3?
We need to look at logs to find clues. First, you need to boot without nomodeset to get a fresh log made with the problem existing. If you can log in on a vtty on the same boot, do:
susepaste /var/log/Xorg.0.log
If you cannot log in on the same boot you need to reboot with nomodeset and immediately do instead:
susepaste /var/log/Xorg.0.log.old
FWIW I know this won’t really help, but I have nothing as new as Whiskey Lake. I do have two Kaby Lakes, which are not very much older, working just fine with 15.3.
Pasted here input/output from
inxi -GMSa
lsmod | grep i915
journalctl -b -1| grep ailed
could prove helpful as well. The last (journalctl) should come from a current boot using nomodeset for the prior boot. If it can come from a current boot without using nomodeset, then leave out the -1.
Hi mrmazda manythanks
I can easily login in text mode without using nomodeset and this is the output of
/var/log/Xorg.0.log
in susepaste:
https://paste.opensuse.org/94174743
without using nomodeset at boot here is the output of
inxi -GMSa
System: Host: pla4ST.homenet.telecomitalia.it Kernel: 5.3.18-59.5-default x86_64 bits: 64 Console: tty 1
Distro: openSUSE Leap 15.3
Machine: Type: Laptop System: TUXEDO product: TUXEDO v: N/A serial: <superuser/root required>
Mobo: TUXEDO model: N150ZU serial: <superuser/root required> UEFI: INSYDE v: 1.07.04RTR3 date: 02/22/2019
Graphics: Device-1: Intel WhiskeyLake-U GT2 [UHD Graphics 620] driver: N/A
Device-2: Chicony Chicony USB2.0 Camera type: USB driver: uvcvideo
Display: server: X.org 1.20.3 driver: N/A note: display driver n/a - try sudo/root unloaded: fbdev,modesetting,vesa
tty: 240x67
Message: Advanced graphics data unavailable in console. Try -G --display
Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel
Sound Server: ALSA v: k5.3.18-59.5-default
the output of
lsmod | grep i915
is empty
here is the output of
journalctl -b | grep ailed
is empty, I leaved -1 becouse I logged in in text mode without using nomodeset at boot
as system said me that no journalctl was opened I did it as root
jJun 28 19:36:59 pla4ST colord[1184]: failed to get session [pid 974]: No data available
Jun 28 19:36:59 pla4ST colord[1184]: failed to get session [pid 974]: No data available
Jun 28 19:36:59 pla4ST colord[1184]: failed to get session [pid 974]: No data available
Jun 28 19:36:59 pla4ST colord[1184]: failed to get session [pid 974]: No data available
Jun 28 19:36:59 pla4ST systemd[1]: ca-certificates.service: Failed with result 'exit-code'.
Jun 28 19:36:59 pla4ST systemd[1]: Failed to start Update system wide CA certificates.
Jun 28 19:37:00 pla4ST kernel: thermal thermal_zone3: failed to read out thermal zone (-61)
Jun 28 19:37:00 pla4ST NetworkManager[980]: <warn> [1624901820.5979] sup-iface: failed to cancel p2p connect: P2P cancel failed
Jun 28 19:37:01 pla4ST charon-systemd[1405]: expanding file expression '/etc/ipsec.d/*.secrets' failed
Jun 28 19:37:01 pla4ST charon-systemd[1405]: opening triplet file /etc/ipsec.d/triplets.dat failed: No such file or directory
Jun 28 19:37:01 pla4ST charon-systemd[1405]: opening configuration file '/etc/tnc_config' failed: No such file or directory
Jun 28 19:37:01 pla4ST charon-systemd[1405]: opening configuration file '/etc/tnc_config' failed: No such file or directory
Jun 28 19:37:01 pla4ST swanctl[1812]: expanding file pattern '/etc/swanctl/conf.d/*.conf' failed: No such file or directory
Jun 28 19:37:01 pla4ST swanctl[1812]: opening directory '/etc/swanctl/x509' failed: No such file or directory
Jun 28 19:37:01 pla4ST swanctl[1812]: opening directory '/etc/swanctl/x509ca' failed: No such file or directory
Jun 28 19:37:01 pla4ST swanctl[1812]: opening directory '/etc/swanctl/x509ocsp' failed: No such file or directory
Jun 28 19:37:01 pla4ST swanctl[1812]: opening directory '/etc/swanctl/x509aa' failed: No such file or directory
Jun 28 19:37:01 pla4ST swanctl[1812]: opening directory '/etc/swanctl/x509ac' failed: No such file or directory
Jun 28 19:37:01 pla4ST swanctl[1812]: opening directory '/etc/swanctl/x509crl' failed: No such file or directory
Jun 28 19:37:01 pla4ST swanctl[1812]: opening directory '/etc/swanctl/pubkey' failed: No such file or directory
Jun 28 19:37:01 pla4ST swanctl[1812]: opening directory '/etc/swanctl/private' failed: No such file or directory
Jun 28 19:37:01 pla4ST swanctl[1812]: opening directory '/etc/swanctl/rsa' failed: No such file or directory
Jun 28 19:37:01 pla4ST swanctl[1812]: opening directory '/etc/swanctl/ecdsa' failed: No such file or directory
Jun 28 19:37:01 pla4ST swanctl[1812]: opening directory '/etc/swanctl/bliss' failed: No such file or directory
Jun 28 19:37:01 pla4ST swanctl[1812]: opening directory '/etc/swanctl/pkcs8' failed: No such file or directory
Jun 28 19:37:01 pla4ST swanctl[1812]: opening directory '/etc/swanctl/pkcs12' failed: No such file or directory
Jun 28 19:37:02 pla4ST kernel: Bluetooth: hci0: setting interface failed (71)
Jun 28 19:37:05 pla4ST.homenet.telecomitalia.it dbus-daemon[975]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Jun 28 19:37:13 pla4ST.homenet.telecomitalia.it systemd[1]: postfix.service: Failed with result 'exit-code'.
Jun 28 19:37:13 pla4ST.homenet.telecomitalia.it systemd[1]: Failed to start Postfix Mail Transport Agent.
That log is from a nomodeset boot, thus useless:
8.622] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.3.18-59.5-default root=UUID=21d87d67-0f83-47bd-8c00-88b275d8283f resume=/dev/disk/by-label/swap splash=silent quiet showopts loglevel=0 acpi_osi= acpi_os_name=Linux acpi_backlight=vendor nomodeset
without using nomodeset at boot here is the output of
inxi -GMSa System: Host: pla4ST.homenet.telecomitalia.it Kernel: 5.3.18-59.5-default x86_64 bits: 64 Console: tty 1 Distro: openSUSE Leap 15.3...
That’s broken, apparently from 15.3’s broken ancient inxi. Please do
sudo inxi -U
sudo zypper al inxi
before responding with inxi output in the future. -U should update the installed version with the latest from upstream, and the lock will ensure a broken rpm package won’t downgrade it. Optionally, uninstall inxi, then follow the installation instructions here.
not, it is a login without nomodeset, I edited the grub boot panel pressing “e” before the boot, erased the “nomodeset” command and then booted pressing f10, in any case I redid it after the upgrade of inxi that now is version 3.1.00-bp153.1.14 and an update of the system but it didn’t solve, I have always text login
here is the result of
logged in as user, ctrl+f2 and logged in as root and executed
inxi -U
zypper al inxi
rebooted but didn’t solve, I have only text login without nomodeset command
system update
rebooted but didn’t solve
rebooted editing the grub boot panel pressing “e” before the boot, erased the “nomodeset” command and then booted pressing f10,
the result of
cp /var/log/Xorg.0.log /home/pla/no-nomodeset-cp-log-06-30giu.txt
in susepaste here
https://paste.opensuse.org/62480730
manythanks again
I copied from that upload the following:
823.044] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.3.18-59.5-default root=UUID=21d87d67-0f83-47bd-8c00-88b275d8283f resume=/dev/disk/by-label/swap splash=silent quiet showopts loglevel=0 acpi_osi= acpi_os_name=Linux acpi_backlight=vendor **nomodeset**
That means the linu line from Grub, as may have been edited in any fashion by you first striking the E key before proceeding with that boot, for the boot that resulted in that file, contained the string nomodeset.
What we need for you to do:
- boot without nomodeset
- wait at least a minute after all goes quiet from the boot process
- reboot using nomodeset
- login as root however and wherever you can
- execute
ls -Gg /var/log/*log /var/log/*log.old >> /var/log/Xorg.0.*
- execute
susepaste -e 10080 /var/log/Xorg.0.log
susepaste -e 10080 /var/log/Xorg.0.log.old
*]report here the URLs resulting from the susepaste commands
may be the kernel command line that contains “nomodeset” is from the file the contain “nomodeset”, anyway, I proceeded in this way:
I booted with nomodeset, went to yast>boot loader>kernel parameters and erased “nomodeset” and applied, then I rebooted without “nomodeset”;
wait at least a minute after all goes quiet from the boot process
I logged in as user, waited 3 minutes, rebooted using
sudo shutdown -r now
reboot using nomodeset
I rebooted editing the grub boot panel pressing “e” before the boot, added the “nomodeset” kernel command and then booted pressing f10;
login as root however and wherever you can
loged in in graphic mode, clicked on “other”, logged in as root, entered in graphic mode;
execute
ls -Gg /var/log/*log /var/log/*log.old >> /var/log/Xorg.0.*
launched konsole,
the result is
-bash: /var/log/Xorg.0.*: ambiguos redirect
so I executed
ls -Gg /var/log/*log /var/log/*log.old >> /var/log/Xorg.0.pier1
execute
susepaste -e 10080 /var/log/Xorg.0.log susepaste -e 10080 /var/log/Xorg.0.log.old
report here the URLs resulting from the susepaste commands
here are the outputs:
pla4ST:~ # susepaste -e 10080 /var/log/Xorg.0.log
Pasted as:
https://susepaste.org/54969439
https://paste.opensuse.org/54969439
Link is also in your clipboard.
pla4ST:~ #
pla4ST:~ # susepaste -e 10080 /var/log/Xorg.0.log.old
Pasted as:
https://susepaste.org/50697093
https://paste.opensuse.org/50697093
Link is also in your clipboard.
pla4ST:~ #
pla4ST:~ # susepaste -e 10080 /var/log/Xorg.0.pier1
Pasted as:
https://susepaste.org/39055658
https://paste.opensuse.org/39055658
Link is also in your clipboard.
pla4ST:~ #
{URL}Nomodeset is a troubleshooting parameter](https://en.opensuse.org/SDB:Nomodeset:Work_Around_Graphic_Upgrade&_Installation_Obstacles){/URL}. Normally, it should not be kept present in grub.cfg, thus not in /etc/default/grub.
The object regarding nomodeset is to only have it utilized or not via the E key at the Grub menu. Please remove nomodeset from /etc/default/grub either using YaST or by direct edit, then in YaST save, or run
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Both of Xorg.0.lo* you uploaded ~9 hours ago are nomodeset boots. You can see for yourself any time if an Xorg.0.log* was produced during a nomodeset boot by viewing the file’s head on about the seventh line containing “Kernel command line:”:
grep "mand line" /var/log/Xorg.0.log /var/log/Xorg.0.log.old
We need to see an Xorg.0.log file that does not have nomodeset on this line. In order to get one that doesn’t have it present, strike the E key at the Grub menu, and ensure that nowhere on the edit screen does nomodeset appear, then proceed to boot. Once that boot has completed, reboot, but on this boot, strike the E key again. This time, ensure that nomodeset is present on the linu line (which may be wrapped), and at its end, append a space and a 3. Next proceed with boot, and upon reaching a login prompt, login as root. Then:
susepaste -e 10080 /boot/grub2/grub.cfg
cd /var/log
head Xorg.0.log Xorg.0.log.old
Either or both should show an absence of nomodeset on “Kernel command line”. Please susepaste -e 10080 whichever file is newer and does not contain nomodeset, and provide here susepaste’s URLs.
hi mrmazda
nomodeset is absent in /etc/default/grub I removed before the last test we made and I controled now, it is absent
as I said you, before perform this test I removed nomodeset by YAST and saved
I followed all your procedure;
this is the susepaste of :
susepaste -e 10080 /boot/grub2/grub.cfg
https://susepaste.org/5917024
I checked the output of
:
cd /var/log
head Xorg.0.log Xorg.0.log.old
but both does contains nomodeset
I also booted again **without **inserting nomodeset on the linu line, and appended at its end a space and a **3
**but alwais both files does contains nomodeset
I don’t know where nomodeset come from but booting without touching nothing at boot I get a text login.
where is the error??