Since on my system graphical booting fails (9 out of 10), for some time now I have been booting the notebook with the “console mode” entry, at the prompt I perform authentication and then launch the graphical session with
“startx startplasma-x11” [or … startgnome, or … startplasma-wayland] And I access (… and work).
Instead when I start with the default entry (and graphical login fails in a continuous loop), I have to change “tty” with Ctrl+Alt+Fx (x from 2 to 6); from the new console I authenticate then launch the graphical session with “startx startplasma-x11” etc. the graphical login window reappears and I have to authenticate again (wasn’t I already auenticate?).
why during boot (in “console mode”) does the “log” not appear on the screen? (maybe “plymouth.enable=0”?).
what it means:
systemd[1]: Failed to start multipathd.service - Device-Mapper Multipath Device Controller.
systemd[1]: multipathd.service: Start request repeated too quickly.
systemd[1]: multipathd.service: Failed with result 'exit-code'.
thanks to those who will take time to respond (and for the work you do).
Is a machine purchased without operating system (to avoid windoze), it is difficult to trace back to the manufacturer (I guess it is an assembled one). I try to reboot and get information during the bios startup.
"
Insyde BIOS Updates
To update Insyde BIOS, you should visit the manufacturer’s official website, not Insyde Software’s website, as Insyde Software provides BIOS solutions to hardware makers who then configure them for specific models.
For example, if you have an HP laptop, you would go to HP’s support website, enter your laptop’s model number, and navigate to the Software and Drivers section to find the latest BIOS update.
If you encounter issues finding the BIOS update, it might be due to the manufacturer purging older software downloads after an arbitrary period of time.
In such cases, contacting the manufacturer’s support directly can help you locate the necessary files.
Here are some steps to update Insyde BIOS:
Confirm your current BIOS version by opening the System Information window in Windows (press Windows + R, type msinfo32, and press Enter).
Go to the manufacturer’s support website, enter your laptop’s model number, and navigate to the Software and Drivers section.
Download the latest BIOS update available for your laptop model.
Backup all important data before proceeding.
Ensure your laptop is connected to the power adapter during the update process.
Run the downloaded BIOS update file (usually an executable file with a .exe extension).
After the update is complete and the system restarts, confirm that the BIOS version has been updated to the latest version.
"
OMLx does seem to have problems with some dual monitor set-ups. I do not know if we have more problems than other Linux distros. I don’t use anything but OMLx and only have a laptop. No monitors.
The problem with some ODM’s is the lack of consideration for anything but getting Windows running on it. It’s an unfortunate situation.
Back to the external monitor situation, they are probably different resolutions. The chances of proper support for your intel graphics card is going to be hit or miss on X11, let alone Wayland. You can try to remove the external monitor and see if that allows the GUI to load. If it does, see if you can hotplug the monitor and get it to show anything.
I have two monitors working fine. Laptop has a HIDPI screen, external HDMI monitor has an HD screen. Wayland is an absolute must in this situation; the only way X11 can handle it is if you lower the resolution on the HIDPI screen to match the HD screen.
This setup works the same on my other laptop running Arch (though that machine only has an HD screen). I use a KVM switch to swap keyboard, mouse, and monitor between the two.
I’m not doing anything crazy (not rotating the monitor or anything like that), but I can report that it does work.
@bruno Your problem seems either graphical because you can log in with startx or startplasma-x11 or a problem with sddm. Be sure sddm.service is enabled with sudo systemctl status sddm.service and if it is not run sudo systemctl enable sddm.service. We have seen users needing to enable this for some reason. (OK, honestly I forgot the reason…) If not that then for developers to resolve the problem you are seeing the logs explained below would help.
For any user: For people having unsuccessful booting we need logs of that. To get logs of a previous boot:
journalctl -b -x | tee journal-unsuccessful-boot.txt
journalctl -k -b -x | tee dmesg-unsuccessful-boot.txt
where -x is < boot_number > (How many reboots ago 0, -1, -2, etc.) 0 being current boot. -k provides dmesg output, so there are two different commands above with differing output. Also the commands create the .txt files you can post here in this forum or in your bug report. You can list previous boots with:
journalctl --list-boots
These are listed with dates/times so if you know the date/time of an unsuccessful boot you can find it in this list.
notebook A = inxi -b ; system info ; A-dmidecode.txt ; external screen via HDMI (with screen connected or disconnected the behavior is identical so external screen is irrelevant) A-dmidecode.txt (17.0 KB) A-info.txt (346 Bytes) inxi-b.txt (1.4 KB)
The TTY does not have a buffer, thus no scrolling back. One would that that after all these years, it could have been improved, but one would be wrong.
We have had several people who simply cannot use SDDM with their hardware. They have removed it and boot with lightdm. Of course this will not use the global themes from Plasma, but their systems work.
