#
# SPDX-License-Identifier: GPL-3.0-or-later
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES=(piix ide_disk reiserfs)
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS=(base)
#
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS=(base udev autodetect block filesystems)
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS=(base udev block filesystems)
#
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS=(base udev block mdadm encrypt filesystems)
#
## This setup loads an lvm2 volume group on a usb device.
# HOOKS=(base udev block lvm2 filesystems)
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block keyboard keymap resume filesystems fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
cat is the command. put that in the terminal and it will show whats’ it the conf file. Then scroll down to find MODULES= and see if it shows anything like MODULES=“i915”
Okay maybe try adding i915 to the conf file
sudo nano /etc/mkinitcpio.conf
add so MODULES=“i915”
ctrl + o + enter to write
ctrl +x to exit
Edit: Then you could reboot and see if it’s any better.
no difference unfortunately. I’m not sure I did the modules part correctly. Is there an open terminal as root command so I can just edit the file?
You have to use an editor such as nano or you can use kate if you have it installed on kde.
with nano, I couldn’t get the cursor to the modules part so I can write it
The issue is you have a hybrid graphics set up and I’m not exactly sure how it works. Some laptops switch to the Nvidia graphics when you have a second monitor. The problem is with most of this hardware is it’s designed to do all this stuff around Windows. In Linux a lot of times you have to set up configurations your self to make it work correctly. You may need to set the second display up. I don’t have this type of hardware. I have a ryzen based laptop with amd graphics. May check the Arch wiki on the monitor set ups & configurations.
https://wiki.archlinux.org/index.php/multihead#VGA1_right_of_HDMI1_at_fixed_resolutions
1 Like
You just use the arrow down and arrow over.
Ok, I’ll check more since at least I have a direction now.
Thank you so much for the help Rick, I really appreciate it.
1 Like
Just so you know on KDE there is a startup script that can be set up that runs on boot up using xrandr that you can set to choose what monitor you want to output to. If you are using sddm the script conf file is in /usr/share/sddm/scripts/Xsetup
Check here on this page and especially under configuration.
1 Like
Yes, it looks like it, but I don’t know If I will have the choice to get the screen back to the laptop.
I’ve read over all your links to make me more secure in doing it, and I’ll be doing them tonight.
Ok, I tried everything, I feel like I’m fighting a losing battle because now I’m certain it’s the hardware itself.
I even tried different distros with KDE and guess what, the exact same problem. I have to switch the displays from the laptop to external monitor, unify outputs, internal screen, then external monitor, and after a random amount of time, it works, the launcher shows on the screen. This happens no matter what distro that has KDE on it. I have EnOS KDE running happily on my dektop so I’m just going to install an EnOS version of XFCE or Cinnamon on this possessed laptop and be done with it.
Thank you Rick for all your help and time!
4 Likes
Hey, this is a late reply but I’m having a similar problem. I have Intel Iris XE graphics and my interface won’t work in KDE Plasma. Did you ever get that working? I’m thinking of switching to Gnome but I don’t want to continuously reinstall the whole OS just to see what works.