Arch Linux

hacstac

Member

Registered: 2020-12-12

Posts: 5

ROG GL553VE Stuck On Boot!!

Hey, I Install Arch with KDE ( with LTS Kernel ) on my laptop yesterday, everything works correctly but now when i restart my machine it stuck on boot. I read so many community posts and comments, but nothing is solved my issue. I think it is a problem with Nvidia & Xorg ( I cant understand how to resolve this ). I also try to change to tty mode and use

startx

( but it will also stuck on there ), But

startplasma-wayland

works, but the browsers & vs code shows very small title bars and fonts. I also tried the Intel Optimus but no success ( So i removed nvidia drivers ).

Laptop Specification (Asus-ROG-GL553VE)
- I7-7GEN
- Nvidia 1050 TI Mobile
- Samsung Evo 970 Nvme SSD

https://s3.ap-south-1.amazonaws.com/aka … n-boot.jpg
https://s3.ap-south-1.amazonaws.com/aka … irefox.png

        00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) (prog-if 00 [VGA controller])
        DeviceName:  Onboard IGD
        Subsystem: ASUSTeK Computer Inc. Device 15e0
        Flags: bus master, fast devsel, latency 0, IRQ 136
        Memory at dd000000 (64-bit, non-prefetchable) [size=16M]
        Memory at b0000000 (64-bit, prefetchable) [size=256M]
        I/O ports at f000 [size=64]
        Expansion ROM at 000c0000 [virtual] [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: i915
        Kernel modules: i915

        01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] (rev a1)
        Subsystem: ASUSTeK Computer Inc. Device 15e0
        Flags: bus master, fast devsel, latency 0, IRQ 143
        Memory at de000000 (32-bit, non-prefetchable) [size=16M]
        Memory at c0000000 (64-bit, prefetchable) [size=256M]
        Memory at d0000000 (64-bit, prefetchable) [size=32M]
        I/O ports at e000 [size=128]
        Expansion ROM at df000000 [disabled] [size=512K]
        Capabilities: <access denied>
        Kernel driver in use: nouveau
        Kernel modules: nouveau

Last edited by V1del (2020-12-12 10:12:43)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,659

Re: ROG GL553VE Stuck On Boot!!

Please don't embed huge images directly.

Post a xorg log and a

sudo journalctl -b 

from another tty after reproducing the "stuck" state. What exactly did you "try the intel optimus" with?

More general I'd say you will want to enable early KMS with i915 to prevent race conditions between the GUI and graphics card initalisation

hacstac

Member

Registered: 2020-12-12

Posts: 5

Re: ROG GL553VE Stuck On Boot!!

Kernel Logs
Xorg Logs

- Process I follow to install nvidia drivers
  - 1.0   

$ lspci -k | grep -A 2 -E "(VGA|3D)"
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
        DeviceName:  Onboard IGD
        Subsystem: ASUSTeK Computer Inc. Device 15e0
--
01:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] (rev a1)
        Subsystem: ASUSTeK Computer Inc. Device 15e0
        Kernel modules: nouveau, nvidia_drm, nvidia

  - 2.0 As I install arch with LTS Kernel ( 5.4.82-1-lts ), I install nvidia-lts, nvidia-utils, nvidia-settings, nvidia-prime

$ nvidia-settings : Error: Unable to find display on any available system

$ glxinfo | grep "OpenGL renderer" : OpenGL renderer string: Mesa Intel(R) HD Graphics 630

$ inxi -G : Graphics:  Device-1: Intel HD Graphics 630 driver: i915 v: kernel 
           Device-2: NVIDIA GP107M [GeForce GTX 1050 Ti Mobile] driver: nvidia v: 455.45.01 
           Device-3: Realtek USB2.0 HD UVC WebCam type: USB driver: uvcvideo 
           Display: server: X.org 1.20.10 driver: intel tty: 115x54 
           Message: Advanced graphics data unavailable in console. Try -G --display

I also tried ealy KMS ( no success ) (

$ /etc/mkinitcpio.conf
MODULES=(intel_agp i915)

$ mkinitcpio -P
$ reboot

hacstac

Member

Registered: 2020-12-12

Posts: 5

Re: ROG GL553VE Stuck On Boot!!

I don't have need of high performance graphics tasks in this system ( I only want to use for my software development purpose [VScode, browsers, pdf readers etc] ). So if there is any way, I can simply use my integrated gpu ( Intel HD 630 ) and completely off 1050TI in arch?? ( so i don't need to bumble with these NVIDIA drivers .:/ )

Lone_Wolf

Member

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,911

Re: ROG GL553VE Stuck On Boot!!

Dec 12 15:42:56 arch kernel: Speculative Store Bypass: Vulnerable
Dec 12 15:42:56 arch kernel: SRBDS: Vulnerable: No microcode
Dec 12 15:42:56 arch kernel: MDS: Vulnerable: Clear CPU buffers attempted, no microcode

Dec 12 15:42:56 arch kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.

please configure early microcode loading , https://wiki.archlinux.org/index.php/Mi … ly_loading

Dec 12 15:42:56 arch kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SAT0.PRT0], AE_ALREADY_EXISTS (20190816/dswload2-326)
Dec 12 15:42:56 arch kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
Dec 12 15:42:56 arch kernel: ACPI: Skipping parse of AML opcode: Device (0x5B82)
Dec 12 15:42:56 arch kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SAT0.PRT1], AE_ALREADY_EXISTS (20190816/dswload2-326)
Dec 12 15:42:56 arch kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
Dec 12 15:42:56 arch kernel: ACPI: Skipping parse of AML opcode: Device (0x5B82)
Dec 12 15:42:56 arch kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SAT0.PRT3], AE_ALREADY_EXISTS (20190816/dswload2-326)
Dec 12 15:42:56 arch kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
Dec 12 15:42:56 arch kernel: ACPI: Skipping parse of AML opcode: Device (0x5B82)
Dec 12 15:42:56 arch kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SAT0.PRT4], AE_ALREADY_EXISTS (20190816/dswload2-326)
Dec 12 15:42:56 arch kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
Dec 12 15:42:56 arch kernel: ACPI: Skipping parse of AML opcode: Device (0x5B82)
Dec 12 15:42:56 arch kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SAT0.PRT5], AE_ALREADY_EXISTS (20190816/dswload2-326)
Dec 12 15:42:56 arch kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190816/psobject-220)
Dec 12 15:42:56 arch kernel: ACPI: Skipping parse of AML opcode: Device (0x5B82)

not sure what those mean, but don't like seeing them.

Dec 12 15:42:56 arch kernel: speakup: module is from the staging directory, the quality is unknown, you have been warned.
Dec 12 15:42:56 arch kernel: input: Speakup as /devices/virtual/input/input7
Dec 12 15:42:56 arch kernel: initialized device: /dev/synth, node (MAJOR 10, MINOR 25)
Dec 12 15:42:56 arch kernel: speakup 3.1.6: initialized
Dec 12 15:42:56 arch kernel: synth name on entry is: (null)
Dec 12 15:42:56 arch kernel: speakup_soft: module is from the staging directory, the quality is unknown, you have been warned.
Dec 12 15:42:56 arch kernel: synth probe
Dec 12 15:42:56 arch kernel: initialized device: /dev/softsynth, node (MAJOR 10, MINOR 26)
Dec 12 15:42:56 arch kernel: initialized device: /dev/softsynthu, node (MAJOR 10, MINOR 27)

Why do you need a kernel module from staging ?

Dec 12 15:42:57 arch systemd-timesyncd[490]: The system is configured to read the RTC time in the local time zone. This mode cannot be fully supported. All system time to RTC updates are disabled.
Dec 12 15:42:57 arch systemd[1]: Started Network Time Synchronization.

Are you dualbooting with windows ?

You appear to be booting to graphical target / SDDM .
Try booting to multi-user.target and configure xinitrc ,
see https://wiki.archlinux.org/index.php/Sy … _boot_into and https://wiki.archlinux.org/index.php/Xinit

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

hacstac

Member

Registered: 2020-12-12

Posts: 5

Re: ROG GL553VE Stuck On Boot!!

Yes, I am dual booting with Windows

hacstac

Member

Registered: 2020-12-12

Posts: 5

Re: ROG GL553VE Stuck On Boot!!

Steps i follow :
- For Intel-ucode: I install a intel-ucode package & check my /boot/grub/grub.cfg for intel-ucode.img, now my grub.cfg has

initrd /boot/intel-ucode.img /boot/initramfs-linux.img

- I also don't understand this ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.SAT0.PRT0], AE_ALREADY_EXISTS (20190816/dswload2-326)

- I don't  understand this either : kernel module from staging ?

- I changed to multiuser.mode

sudo systemctl set-default multi-user.target

- For xinitrc

$ cat ~/.xinitrc 
exec startplasma-wayland

Now, when I $startx, my system boots with 1024x768, ( how to set it to 1920x1080? )

https://s3.ap-south-1.amazonaws.com/aka … 24x768.jpg

Again found this in kernel logs

nvidia: loading out-of-tree module taints kernel.
Dec 13 09:52:52 arch kernel: nvidia: module license 'NVIDIA' taints kernel.
Dec 13 09:52:52 arch kernel: Disabling lock debugging due to kernel taint
Dec 13 09:52:52 arch kernel: nvidia: module verification failed: signature and/or required key missing - tainting >
Dec 13 09:52:52 arch kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 234
Dec 13 09:52:52 arch kernel: nvidia 0000:01:00.0: enabling device (0006 -> 0007)
Dec 13 09:52:52 arch kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  455.45.01  Thu Nov  5 23:03:56 UTC 20>
Dec 13 09:52:52 arch kernel: ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], 

Last edited by hacstac (2020-12-13 04:38:45)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,659

Re: ROG GL553VE Stuck On Boot!!

You don't want to start plasma-wayland from your .xinitrc. You need to fix your .xinitrc you don't want to start wayland from there.  Make sure you have the template from https://wiki.archlinux.org/index.php/Xinit#xinitrc (follow the blue note boxes)  and startplasma-x11: https://wiki.archlinux.org/index.php/KD … he_console

Or do you want to use wayland? Then follow that to start the wayland session but start it properly, however there are still a few pitfalls with a Wayland session from what I know, not unlike what you are describing.

Also remove xf86-video-intel and retry.