Arch Linux

eryx

Member

Registered: 2018-09-11

Posts: 24

how to make the system boot sequence be like a windows machine?

how can i make the booting of the laptop more like a windows machine i.e Asus logo(its an Asus laptop...) and then a GUI login screen?
right now the boot sequence is like so -
1. Asus logo
2. grub menu to choose an operating system(why? i only have arch linux installed..)
3. some messages i dont understand(dell_smbios cant run on a non dell machine and some other crap)
4. and then tty1 where i login and write 'startx' so xorg and KDE can start..

i want to boot and only see the asus logo and then a GUI login screen to choose a user(like the kde one when the lid is closed then opened back on)

graysky

Wiki Maintainer

From: :wq

Registered: 2008-12-01

Posts: 10,731

Website

Re: how to make the system boot sequence be like a windows machine?

2) You need a boot loader and you installed grub.
3) Might be systemd's output/append the quiet option to your kernel line in grub.cfg (ie linux /vmlinuz-linux root=... quiet ...).
4) Install a greeter.

...is this post a troll attempt?  If not, you really need to read the wiki more.

---

AUR packages • Zsh and other configs

circleface

Member

Registered: 2012-05-26

Posts: 639

Re: how to make the system boot sequence be like a windows machine?

[Sarcasm] Why on earth would you want your system to take 10 minutes to boot up??? [/Sarcasm]

For real though, look into the plymouth program, it can show a graphical picture while the system is booting.

eryx

Member

Registered: 2018-09-11

Posts: 24

Re: how to make the system boot sequence be like a windows machine?

2) You need a boot loader and you installed grub.
3) Might be systemd's output/append the quiet option to your kernel line in grub.cfg (ie linux /vmlinuz-linux root=... quiet ...).
4) Install a greeter.

...is this post a troll attempt?  If not, you really need to read the wiki more.

tried installing sddm already it didnt work just booted into black screen and from there i needed to go to another tty to 'pkill sddm' 'systemctl disable' it and to remove it so the screen wont boot to black screen... same goes for lightDM.

and why is it a troll post? its my first install of arch and actually of linux machine ever i know nothing about this system and i taught newbie corner is the place to ask that question since im a newbie at this operating system..

loqs

Member

Registered: 2014-03-06

Posts: 18,859

Re: how to make the system boot sequence be like a windows machine?

Without knowing any details of the system's hardware,  the journal for the sddm.service or the contents of the logs from /var/log/lightdm how could anyone know why the services are failing?
Xorg starts late so that will not resolve your issue output during early boot.
Edit:
I would also as a suggestion not continue with trying to hide output until you have the system fully configured and working without other issues as you will be hiding output relevant to those other issues.

Last edited by loqs (2018-09-11 19:58:09)

eryx

Member

Registered: 2018-09-11

Posts: 24

Re: how to make the system boot sequence be like a windows machine?

Without knowing any details of the system's hardware,  the journal for the sddm.service or the contents of the logs from /var/log/lightdm how could anyone know why the services are failing?
Xorg starts late so that will not resolve your issue output during early boot.
Edit:
I would also as a suggestion not continue with trying to hide output until you have the system fully configured and working without other issues as you will be hiding output relevant to those other issues.

its asus x556u laptop, i5-7200U, geforce 930mx
i dont know how to get you the sddm logs(remember its my first time using linux)
but the lightdm logs:

[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.26.0, UID=0 PID=348
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Registered seat module unity
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.10s] DEBUG: Monitoring logind for seats
[+0.10s] DEBUG: New seat added from logind: seat0
[+0.10s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.10s] DEBUG: Seat seat0: Starting
[+0.10s] DEBUG: Seat seat0: Creating greeter session
[+0.10s] DEBUG: Seat seat0: Creating display server of type x
[+0.10s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.10s] DEBUG: Using VT 7
[+0.10s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.10s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.10s] DEBUG: XServer 0: Writing X server authority to /run/lightdm/root/:0
[+0.10s] DEBUG: XServer 0: Launching X Server
[+0.10s] DEBUG: Launching process 365: /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.10s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.10s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.10s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.28s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.28s] DEBUG: User /org/freedesktop/Accounts/User1000 added
[+3.83s] DEBUG: Got signal 10 from process 365
[+3.83s] DEBUG: XServer 0: Got signal from X server :0
[+3.83s] DEBUG: XServer 0: Connecting to XServer :0
[+3.83s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+3.84s] DEBUG: Session pid=408: Started with service 'lightdm-greeter', username 'lightdm'
[+3.87s] DEBUG: Session pid=408: Authentication complete with return value 0: Success
[+3.87s] DEBUG: Seat seat0: Session authenticated, running command
[+3.87s] DEBUG: Session pid=408: Running command /usr/bin/lightdm-gtk-greeter
[+3.87s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+3.87s] DEBUG: Session pid=408: Logging to /var/log/lightdm/seat0-greeter.log
[+3.93s] DEBUG: Activating VT 7
[+3.93s] DEBUG: Activating login1 session c1
[+3.93s] DEBUG: Seat seat0 changes active session to c1
[+3.93s] DEBUG: Session c1 is already active
[+4.14s] DEBUG: Greeter connected version=1.26.0 api=1 resettable=false
[+4.24s] DEBUG: Greeter start authentication for eryx
[+4.24s] DEBUG: Session pid=436: Started with service 'lightdm', username 'eryx'
[+4.25s] DEBUG: Session pid=436: Got 1 message(s) from PAM
[+4.25s] DEBUG: Prompt greeter with 1 message(s)
[+21.10s] DEBUG: Seat seat0 changes active session to 
[+27.67s] DEBUG: Seat seat0 changes active session to 2
[+68.44s] DEBUG: Got signal 15 from process 1
[+68.44s] DEBUG: Caught Terminated signal, shutting down
[+68.44s] DEBUG: Stopping display manager
[+68.44s] DEBUG: Seat seat0: Stopping
[+68.44s] DEBUG: Seat seat0: Stopping display server
[+68.44s] DEBUG: Sending signal 15 to process 365
[+68.44s] DEBUG: Seat seat0: Stopping session
[+68.44s] DEBUG: Terminating login1 session c1
[+68.46s] DEBUG: Session pid=408: Sending SIGTERM
[+68.46s] DEBUG: Seat seat0: Stopping session
[+68.46s] DEBUG: Session pid=436: Sending SIGTERM
[+68.46s] DEBUG: Session pid=436: Terminated with signal 15
[+68.46s] DEBUG: Session: Failed during authentication
[+68.46s] DEBUG: Seat seat0: Session stopped
[+68.46s] DEBUG: Greeter closed communication channel
[+68.47s] DEBUG: Session pid=408: Exited with return value 0
[+68.47s] DEBUG: Seat seat0: Session stopped
[+68.50s] DEBUG: Process 365 exited with return value 0
[+68.50s] DEBUG: XServer 0: X server stopped
[+68.50s] DEBUG: Releasing VT 7
[+68.50s] DEBUG: XServer 0: Removing X server authority /run/lightdm/root/:0
[+68.50s] DEBUG: Seat seat0: Display server stopped
[+68.50s] DEBUG: Seat seat0: Stopped
[+68.50s] DEBUG: Display manager stopped
[+68.50s] DEBUG: Stopping daemon
[+68.50s] DEBUG: Exiting with return value 0

i stoped it after a minute or so with moving to tty2 and then pkill lighdm

loqs

Member

Registered: 2014-03-06

Posts: 18,859

Re: how to make the system boot sequence be like a windows machine?

What is the contents of /var/log/lightdm/seat0-greeter.log and /var/log/Xorg.0.log?  (the latter's contents may gave been overwritten by newer invocations of X)
Edit:
Have you done anything to configure hybrid graphics?
Edit2:
Systemd#Filtering_output to find the output from a service such as sddm.service.

Last edited by loqs (2018-09-11 20:24:17)

eryx

Member

Registered: 2018-09-11

Posts: 24

Re: how to make the system boot sequence be like a windows machine?

What is the contents of /var/log/lightdm/seat0-greeter.log and /var/log/Xorg.0.log?  (the latter's contents may gave been overwritten by newer invocations of X)
Edit:
Have you done anything to configure hybrid graphics?
Edit2:
Systemd#Filtering_output to find the output from a service such as sddm.service.

hmm ok i installed bumblebee and then lightdm again and now i have a login screen(black and weird login screen but i guess i can configure it how ever i want.. so thanks for the help man!

Trilby

Inspector Parrot

Registered: 2011-11-29

Posts: 30,456

Website

Re: how to make the system boot sequence be like a windows machine?

This is much better than your first post which asked dozens of questions all at once, but this is still really several questions.

Most of the focus above is on getting a Display Manager working.  A DM will address part of your desires (though they are a general PITA).  But you should also read the GRUB wiki page to see how to configure a default boot option with no timeout.  That way the grub menu will never be displayed.  You should also look at wiki pages for quiet / silent boot.

---

"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman