Issues running EndeavourOS

unix_lover · February 9, 2020, 3:33pm

https://mega.nz/#!iu4Q1A4Y!-c-7gF_6-vp-LL7eKMbhZx2P8f3nU50T4w6p0S9Qfp4

Hey man I uploaded my logs to the cloud and this is the sharable link. I was wondering if somebody could please take a look at it?

ricklinux · February 9, 2020, 3:50pm

https://endeavouros.com/docs/forum/how-to-include-systemlogs-in-your-post/

unix_lover · February 10, 2020, 12:13am

cat /tmp/journal | curl -F ‘f:1=<-’ ix.io

If I run this command, where will it go exactly and how would you know that this particular log is from me?

ricklinux · February 10, 2020, 12:30am

It’s all explained in the previous post.

unix_lover · February 10, 2020, 3:02am

Ok so I am doing exactly what the website asks me to do

Systemd Journal:

cat /tmp/journal | curl -F 'f:1=<-' ix.io
http://ix.io/2bgQ

cat /tmp/journal.last | curl -F 'f:1=<-' ix.io
http://ix.io/2bgR

cat /tmp/journal.2last | curl -F 'f:1=<-' ix.io
http://ix.io/2bgS

Xsession:

cat ~/.xsession-errors | curl -F 'f:1=<-' ix.io
http://ix.io/2bgT

cat ~/.xsession-errors.old | curl -F 'f:1=<-' ix.io
http://ix.io/2bgU

Xorg (X11):

cat /var/log/Xorg.0.log | curl -F 'f:1=<-' ix.io
http://ix.io/2bgV

cat /var/log/Xorg.0.log.old | curl -F 'f:1=<-' ix.io
http://ix.io/2bgW

Lightdm:

sudo cat /var/log/lightdm/lightdm.log | curl -F 'f:1=<-' ix.io
http://ix.io/2bgX

sudo cat /var/log/lightdm/x-0-greeter.log | curl -F 'f:1=<-' ix.io
File doesn’t exist.

Other log providers and options:

journalctl --since "10 minutes ago"
The output was:

-- Logs begin at Sat 2020-02-08 16:11:15 AEDT, end at Mon 2020-02-10 13:59:01 A>
Feb 10 13:50:26 somepc dbus-daemon[540]: [system] Activating via systemd: servi>
Feb 10 13:50:26 somepc dbus-daemon[540]: [system] Activation via systemd failed>
Feb 10 13:50:30 somepc gnome-keyring-daemon[659]: asked to register item /org/f>
Feb 10 13:50:41 somepc kernel: perf: interrupt took too long (2508 > 2500), low>
Feb 10 13:52:35 somepc kernel: perf: interrupt took too long (3143 > 3135), low>
Feb 10 13:56:45 somepc systemd[1]: Starting Cleanup of Temporary Directories...
Feb 10 13:56:45 somepc systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Feb 10 13:56:45 somepc systemd[1]: Started Cleanup of Temporary Directories.
Feb 10 13:56:45 somepc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=>
Feb 10 13:56:45 somepc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4>
Feb 10 13:56:45 somepc kernel: audit: type=1130 audit(1581303405.575:63): pid=1>
Feb 10 13:56:45 somepc kernel: audit: type=1131 audit(1581303405.575:64): pid=1>
Feb 10 13:58:03 somepc audit[2110]: USER_AUTH pid=2110 uid=1000 auid=1000 ses=2>
Feb 10 13:58:03 somepc audit[2110]: USER_ACCT pid=2110 uid=1000 auid=1000 ses=2>
Feb 10 13:58:03 somepc sudo[2110]:    user1 : TTY=pts/0 ; PWD=/home/user1 ; USE>
Feb 10 13:58:03 somepc audit[2110]: CRED_REFR pid=2110 uid=0 auid=1000 ses=2 ms>
Feb 10 13:58:03 somepc sudo[2110]: pam_unix(sudo:session): session opened for u>
Feb 10 13:58:03 somepc sudo[2110]: pam_unix(sudo:session): session opened for u>
-- Logs begin at Sat 2020-02-08 16:11:15 AEDT, end at Mon 2020-02-10 13:59:01 A>
-- Logs begin at Sat 2020-02-08 16:11:15 AEDT, end at Mon 2020-02-10 13:59:01 A>
Feb 10 13:50:26 somepc dbus-daemon[540]: [system] Activating via systemd: servi>
Feb 10 13:50:26 somepc dbus-daemon[540]: [system] Activation via systemd failed>
Feb 10 13:50:30 somepc gnome-keyring-daemon[659]: asked to register item /org/f>
Feb 10 13:50:41 somepc kernel: perf: interrupt took too long (2508 > 2500), low>
Feb 10 13:52:35 somepc kernel: perf: interrupt took too long (3143 > 3135), low>
Feb 10 13:56:45 somepc systemd[1]: Starting Cleanup of Temporary Directories...
Feb 10 13:56:45 somepc systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Feb 10 13:56:45 somepc systemd[1]: Started Cleanup of Temporary Directories.
Feb 10 13:56:45 somepc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=>
Feb 10 13:56:45 somepc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4>
Feb 10 13:56:45 somepc kernel: audit: type=1130 audit(1581303405.575:63): pid=1>
Feb 10 13:56:45 somepc kernel: audit: type=1131 audit(1581303405.575:64): pid=1>
Feb 10 13:58:03 somepc audit[2110]: USER_AUTH pid=2110 uid=1000 auid=1000 ses=2>
Feb 10 13:58:03 somepc audit[2110]: USER_ACCT pid=2110 uid=1000 auid=1000 ses=2>
Feb 10 13:58:03 somepc sudo[2110]:    user1 : TTY=pts/0 ; PWD=/home/user1 ; USE>
Feb 10 13:58:03 somepc audit[2110]: CRED_REFR pid=2110 uid=0 auid=1000 ses=2 ms>
Feb 10 13:58:03 somepc sudo[2110]: pam_unix(sudo:session): session opened for u>
Feb 10 13:58:03 somepc audit[2110]: USER_START pid=2110 uid=0 auid=1000 ses=2 m>
Feb 10 13:58:03 somepc kernel: audit: type=1100 audit(1581303483.788:65): pid=2>
Feb 10 13:58:03 somepc kernel: audit: type=1101 audit(1581303483.788:66): pid=2>
Feb 10 13:58:03 somepc kernel: audit: type=1110 audit(1581303483.788:67): pid=2>
Feb 10 13:58:03 somepc kernel: audit: type=1105 audit(1581303483.788:68): pid=2>
Feb 10 13:58:03 somepc sudo[2110]: pam_unix(sudo:session): session closed for u>
Feb 10 13:58:03 somepc audit[2110]: USER_END pid=2110 uid=0 auid=1000 ses=2 msg>
Feb 10 13:58:03 somepc audit[2110]: CRED_DISP pid=2110 uid=0 auid=1000 ses=2 ms>
Feb 10 13:58:03 somepc kernel: audit: type=1106 audit(1581303483.798:69): pid=2>
Feb 10 13:58:03 somepc kernel: audit: type=1104 audit(1581303483.798:70): pid=2>
Feb 10 13:59:01 somepc audit[2136]: USER_ACCT pid=2136 uid=1000 auid=1000 ses=2>
Feb 10 13:59:01 somepc sudo[2136]:    user1 : TTY=pts/0 ; PWD=/home/user1 ; USE>
Feb 10 13:59:01 somepc audit[2136]: CRED_REFR pid=2136 uid=0 auid=1000 ses=2 ms>
Feb 10 13:59:01 somepc kernel: audit: type=1101 audit(1581303541.011:71): pid=2>
Feb 10 13:59:01 somepc kernel: audit: type=1110 audit(1581303541.011:72): pid=2>
Feb 10 13:59:01 somepc audit[2136]: USER_START pid=2136 uid=0 auid=1000 ses=2 m>
Feb 10 13:59:01 somepc sudo[2136]: pam_unix(sudo:session): session opened for u>
Feb 10 13:59:01 somepc sudo[2136]: pam_unix(sudo:session): session closed for u>
Feb 10 13:59:01 somepc audit[2136]: USER_END pid=2136 uid=0 auid=1000 ses=2 msg>
Feb 10 13:59:01 somepc audit[2136]: CRED_DISP pid=2136 uid=0 auid=1000 ses=2 ms>
Feb 10 13:59:01 somepc kernel: audit: type=1105 audit(1581303541.021:73): pid=2>
Feb 10 13:59:01 somepc kernel: audit: type=1106 audit(1581303541.021:74): pid=2>
Feb 10 13:59:01 somepc kernel: audit: type=1104 audit(1581303541.021:75): pid=2>
...skipping...
Feb 10 13:58:03 somepc audit[2110]: USER_START pid=2110 uid=0 auid=1000 ses=2 m>
Feb 10 13:58:03 somepc kernel: audit: type=1100 audit(1581303483.788:65): pid=2>
Feb 10 13:58:03 somepc kernel: audit: type=1101 audit(1581303483.788:66): pid=2>
Feb 10 13:58:03 somepc kernel: audit: type=1110 audit(1581303483.788:67): pid=2>
Feb 10 13:58:03 somepc kernel: audit: type=1105 audit(1581303483.788:68): pid=2>
Feb 10 13:58:03 somepc sudo[2110]: pam_unix(sudo:session): session closed for u>
Feb 10 13:58:03 somepc audit[2110]: USER_END pid=2110 uid=0 auid=1000 ses=2 msg>
Feb 10 13:58:03 somepc audit[2110]: CRED_DISP pid=2110 uid=0 auid=1000 ses=2 ms>
Feb 10 13:58:03 somepc kernel: audit: type=1106 audit(1581303483.798:69): pid=2>
Feb 10 13:58:03 somepc kernel: audit: type=1104 audit(1581303483.798:70): pid=2>
Feb 10 13:59:01 somepc audit[2136]: USER_ACCT pid=2136 uid=1000 auid=1000 ses=2>
Feb 10 13:59:01 somepc sudo[2136]:    user1 : TTY=pts/0 ; PWD=/home/user1 ; USE>
Feb 10 13:59:01 somepc audit[2136]: CRED_REFR pid=2136 uid=0 auid=1000 ses=2 ms>
Feb 10 13:59:01 somepc kernel: audit: type=1101 audit(1581303541.011:71): pid=2>
Feb 10 13:59:01 somepc kernel: audit: type=1110 audit(1581303541.011:72): pid=2>
Feb 10 13:59:01 somepc audit[2136]: USER_START pid=2136 uid=0 auid=1000 ses=2 m>
Feb 10 13:59:01 somepc sudo[2136]: pam_unix(sudo:session): session opened for u>
Feb 10 13:59:01 somepc sudo[2136]: pam_unix(sudo:session): session closed for u>
Feb 10 13:59:01 somepc audit[2136]: USER_END pid=2136 uid=0 auid=1000 ses=2 msg>
Feb 10 13:59:01 somepc audit[2136]: CRED_DISP pid=2136 uid=0 auid=1000 ses=2 ms>
Feb 10 13:59:01 somepc kernel: audit: type=1105 audit(1581303541.021:73): pid=2>
Feb 10 13:59:01 somepc kernel: audit: type=1106 audit(1581303541.021:74): pid=2>
Feb 10 13:59:01 somepc kernel: audit: type=1104 audit(1581303541.021:75): pid=2>

cat ~/endeavour-install.log | curl -F 'f:1=<-' ix.io
The file doesn’t appear to exist.

lspci > log.txt && lsusb >> log.txt && journalctl -b -0 >> log.txt && cat log.txt | curl -F 'f:1=<-' ix.io
http://ix.io/2bgZ

Hardware Information Systems:

inxi -Fxxc0 | curl -F 'f:1=<-' ix.io
http://ix.io/2bh2

These actions were all done while booted into Linux-LTS fallback as this is the most workable version I can seem to boot into. All though sometimes when I boot into this, it will freeze up after logging in or if I opened an application or something so sometimes this works sometimes it fails to work.

Do you need anymore information?

unix_lover · February 10, 2020, 4:14am

@manuel Hey man I wanted to ask you did I post all my logs correctly in the previous post using the pastbins? And is it ok that I ran all those commands in Linux-LTS fallback mode?

manuel · February 10, 2020, 8:19am

Thanks for the logs.
They reveal some problems, but as you run in fallback, it does not show the actual errors.
Some clues though, seems that at least nouveau has problems to start, and wifi has issues too.

So, can you give some logs about the live system? Especially the Xorg log, and journalctl -b -0 logs?
They may give clue about why live works and real install has issues.

unix_lover · February 10, 2020, 8:50am

No worries.

Oh I see, I will boot into LTS then rather than LTS fallback and attempt to re-run this.

Yeah it is a bit laggy (surpirsingly less laggy than other distros though).

That is strange since I can access any website just fine and it seems ok the speed. I am using an external wifi adapter.

Sure let me try this out very soon I will resubmit all my logs under LTS (if I can somehow manage to log in without any issues) and I will run those extra commands.

unix_lover · February 10, 2020, 9:52am

Ok so this is this is under Linux-LTS mode.

Systemd Journal:

cat /tmp/journal | curl -F 'f:1=<-' ix.io
http://ix.io/2bhQ

cat /tmp/journal.last | curl -F 'f:1=<-' ix.io
http://ix.io/2bhR

cat /tmp/journal.2last | curl -F 'f:1=<-' ix.io
http://ix.io/2bhS

Xsession:

cat ~/.xsession-errors | curl -F 'f:1=<-' ix.io
http://ix.io/2bhT

cat ~/.xsession-errors.old | curl -F 'f:1=<-' ix.io
No content appears to exist inside this file.

Xorg (X11):

cat /var/log/Xorg.0.log | curl -F 'f:1=<-' ix.io
http://ix.io/2bhX

cat /var/log/Xorg.0.log.old | curl -F 'f:1=<-' ix.io
http://ix.io/2bhY

Lightdm:

sudo cat /var/log/lightdm/lightdm.log | curl -F 'f:1=<-' ix.io
http://ix.io/2bhZ

cat /var/log/lightdm/x-0-greeter.log | curl -F 'f:1=<-' ix.io
File doesn’t exist.

Other log providers and options:

journalctl --since "10 minutes ago"
The output for this was:

-- Logs begin at Sat 2020-02-08 16:11:15 AEDT, end at Mon 2020-02-10 20:27:12 A>
Feb 10 20:21:05 somepc kernel: perf: interrupt took too long (2503 > 2500), low>
Feb 10 20:25:52 somepc kernel: perf: interrupt took too long (3136 > 3128), low>
Feb 10 20:26:37 somepc systemd[1]: Starting Cleanup of Temporary Directories...
Feb 10 20:26:37 somepc systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Feb 10 20:26:37 somepc systemd[1]: Started Cleanup of Temporary Directories.
Feb 10 20:26:37 somepc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=>
Feb 10 20:26:37 somepc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4>
Feb 10 20:26:37 somepc kernel: audit: type=1130 audit(1581326797.797:61): pid=1>
Feb 10 20:26:37 somepc kernel: audit: type=1131 audit(1581326797.797:62): pid=1>
Feb 10 20:27:12 somepc audit[1723]: USER_AUTH pid=1723 uid=1000 auid=1000 ses=2>
Feb 10 20:27:12 somepc audit[1723]: USER_ACCT pid=1723 uid=1000 auid=1000 ses=2>
Feb 10 20:27:12 somepc sudo[1723]:    user1 : TTY=pts/0 ; PWD=/home/user1 ; USE>
Feb 10 20:27:12 somepc audit[1723]: CRED_REFR pid=1723 uid=0 auid=1000 ses=2 ms>
Feb 10 20:27:12 somepc sudo[1723]: pam_unix(sudo:session): session opened for u>
Feb 10 20:27:12 somepc audit[1723]: USER_START pid=1723 uid=0 auid=1000 ses=2 m>
Feb 10 20:27:12 somepc kernel: audit: type=1100 audit(1581326832.768:63): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1101 audit(1581326832.768:64): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1110 audit(1581326832.768:65): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1105 audit(1581326832.768:66): pid=1>
Feb 10 20:27:12 somepc sudo[1723]: pam_unix(sudo:session): session closed for u>
Feb 10 20:27:12 somepc audit[1723]: USER_END pid=1723 uid=0 auid=1000 ses=2 msg>
Feb 10 20:27:12 somepc audit[1723]: CRED_DISP pid=1723 uid=0 auid=1000 ses=2 ms>
Feb 10 20:27:12 somepc kernel: audit: type=1106 audit(1581326832.778:67): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1104 audit(1581326832.778:68): pid=1>
...skipping...
Feb 10 20:25:52 somepc kernel: perf: interrupt took too long (3136 > 3128), low>
Feb 10 20:26:37 somepc systemd[1]: Starting Cleanup of Temporary Directories...
Feb 10 20:26:37 somepc systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Feb 10 20:26:37 somepc systemd[1]: Started Cleanup of Temporary Directories.
Feb 10 20:26:37 somepc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=>
Feb 10 20:26:37 somepc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4>
Feb 10 20:26:37 somepc kernel: audit: type=1130 audit(1581326797.797:61): pid=1>
Feb 10 20:26:37 somepc kernel: audit: type=1131 audit(1581326797.797:62): pid=1>
Feb 10 20:27:12 somepc audit[1723]: USER_AUTH pid=1723 uid=1000 auid=1000 ses=2>
Feb 10 20:27:12 somepc audit[1723]: USER_ACCT pid=1723 uid=1000 auid=1000 ses=2>
Feb 10 20:27:12 somepc sudo[1723]:    user1 : TTY=pts/0 ; PWD=/home/user1 ; USE>
Feb 10 20:27:12 somepc audit[1723]: CRED_REFR pid=1723 uid=0 auid=1000 ses=2 ms>
Feb 10 20:27:12 somepc sudo[1723]: pam_unix(sudo:session): session opened for u>
Feb 10 20:27:12 somepc audit[1723]: USER_START pid=1723 uid=0 auid=1000 ses=2 m>
Feb 10 20:27:12 somepc kernel: audit: type=1100 audit(1581326832.768:63): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1101 audit(1581326832.768:64): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1110 audit(1581326832.768:65): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1105 audit(1581326832.768:66): pid=1>
Feb 10 20:27:12 somepc sudo[1723]: pam_unix(sudo:session): session closed for u>
Feb 10 20:27:12 somepc audit[1723]: USER_END pid=1723 uid=0 auid=1000 ses=2 msg>
Feb 10 20:27:12 somepc audit[1723]: CRED_DISP pid=1723 uid=0 auid=1000 ses=2 ms>
Feb 10 20:27:12 somepc kernel: audit: type=1106 audit(1581326832.778:67): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1104 audit(1581326832.778:68): pid=1>
...skipping...
Feb 10 20:25:52 somepc kernel: perf: interrupt took too long (3136 > 3128), low>
Feb 10 20:26:37 somepc systemd[1]: Starting Cleanup of Temporary Directories...
Feb 10 20:26:37 somepc systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Feb 10 20:26:37 somepc systemd[1]: Started Cleanup of Temporary Directories.
Feb 10 20:26:37 somepc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=>
Feb 10 20:26:37 somepc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4>
Feb 10 20:26:37 somepc kernel: audit: type=1130 audit(1581326797.797:61): pid=1>
Feb 10 20:26:37 somepc kernel: audit: type=1131 audit(1581326797.797:62): pid=1>
Feb 10 20:27:12 somepc audit[1723]: USER_AUTH pid=1723 uid=1000 auid=1000 ses=2>
Feb 10 20:27:12 somepc audit[1723]: USER_ACCT pid=1723 uid=1000 auid=1000 ses=2>
Feb 10 20:27:12 somepc sudo[1723]:    user1 : TTY=pts/0 ; PWD=/home/user1 ; USE>
Feb 10 20:27:12 somepc audit[1723]: CRED_REFR pid=1723 uid=0 auid=1000 ses=2 ms>
Feb 10 20:27:12 somepc sudo[1723]: pam_unix(sudo:session): session opened for u>
Feb 10 20:27:12 somepc audit[1723]: USER_START pid=1723 uid=0 auid=1000 ses=2 m>
Feb 10 20:27:12 somepc kernel: audit: type=1100 audit(1581326832.768:63): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1101 audit(1581326832.768:64): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1110 audit(1581326832.768:65): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1105 audit(1581326832.768:66): pid=1>
Feb 10 20:27:12 somepc sudo[1723]: pam_unix(sudo:session): session closed for u>
Feb 10 20:27:12 somepc audit[1723]: USER_END pid=1723 uid=0 auid=1000 ses=2 msg>
Feb 10 20:27:12 somepc audit[1723]: CRED_DISP pid=1723 uid=0 auid=1000 ses=2 ms>
Feb 10 20:27:12 somepc kernel: audit: type=1106 audit(1581326832.778:67): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1104 audit(1581326832.778:68): pid=1>
...skipping...
-- Logs begin at Sat 2020-02-08 16:11:15 AEDT, end at Mon 2020-02-10 20:27:12 A>
Feb 10 20:21:05 somepc kernel: perf: interrupt took too long (2503 > 2500), low>
Feb 10 20:25:52 somepc kernel: perf: interrupt took too long (3136 > 3128), low>
Feb 10 20:26:37 somepc systemd[1]: Starting Cleanup of Temporary Directories...
Feb 10 20:26:37 somepc systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Feb 10 20:26:37 somepc systemd[1]: Started Cleanup of Temporary Directories.
Feb 10 20:26:37 somepc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=>
Feb 10 20:26:37 somepc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4>
Feb 10 20:26:37 somepc kernel: audit: type=1130 audit(1581326797.797:61): pid=1>
Feb 10 20:26:37 somepc kernel: audit: type=1131 audit(1581326797.797:62): pid=1>
Feb 10 20:27:12 somepc audit[1723]: USER_AUTH pid=1723 uid=1000 auid=1000 ses=2>
Feb 10 20:27:12 somepc audit[1723]: USER_ACCT pid=1723 uid=1000 auid=1000 ses=2>
Feb 10 20:27:12 somepc sudo[1723]:    user1 : TTY=pts/0 ; PWD=/home/user1 ; USE>
Feb 10 20:27:12 somepc audit[1723]: CRED_REFR pid=1723 uid=0 auid=1000 ses=2 ms>
Feb 10 20:27:12 somepc sudo[1723]: pam_unix(sudo:session): session opened for u>
Feb 10 20:27:12 somepc audit[1723]: USER_START pid=1723 uid=0 auid=1000 ses=2 m>
Feb 10 20:27:12 somepc kernel: audit: type=1100 audit(1581326832.768:63): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1101 audit(1581326832.768:64): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1110 audit(1581326832.768:65): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1105 audit(1581326832.768:66): pid=1>
Feb 10 20:27:12 somepc sudo[1723]: pam_unix(sudo:session): session closed for u>
Feb 10 20:27:12 somepc audit[1723]: USER_END pid=1723 uid=0 auid=1000 ses=2 msg>
Feb 10 20:27:12 somepc audit[1723]: CRED_DISP pid=1723 uid=0 auid=1000 ses=2 ms>
...skipping...
-- Logs begin at Sat 2020-02-08 16:11:15 AEDT, end at Mon 2020-02-10 20:27:12 A>
Feb 10 20:21:05 somepc kernel: perf: interrupt took too long (2503 > 2500), low>
Feb 10 20:25:52 somepc kernel: perf: interrupt took too long (3136 > 3128), low>
Feb 10 20:26:37 somepc systemd[1]: Starting Cleanup of Temporary Directories...
Feb 10 20:26:37 somepc systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Feb 10 20:26:37 somepc systemd[1]: Started Cleanup of Temporary Directories.
Feb 10 20:26:37 somepc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=>
Feb 10 20:26:37 somepc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4>
Feb 10 20:26:37 somepc kernel: audit: type=1130 audit(1581326797.797:61): pid=1>
Feb 10 20:26:37 somepc kernel: audit: type=1131 audit(1581326797.797:62): pid=1>
Feb 10 20:27:12 somepc audit[1723]: USER_AUTH pid=1723 uid=1000 auid=1000 ses=2>
Feb 10 20:27:12 somepc audit[1723]: USER_ACCT pid=1723 uid=1000 auid=1000 ses=2>
Feb 10 20:27:12 somepc sudo[1723]:    user1 : TTY=pts/0 ; PWD=/home/user1 ; USE>
Feb 10 20:27:12 somepc audit[1723]: CRED_REFR pid=1723 uid=0 auid=1000 ses=2 ms>
Feb 10 20:27:12 somepc sudo[1723]: pam_unix(sudo:session): session opened for u>
Feb 10 20:27:12 somepc audit[1723]: USER_START pid=1723 uid=0 auid=1000 ses=2 m>
Feb 10 20:27:12 somepc kernel: audit: type=1100 audit(1581326832.768:63): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1101 audit(1581326832.768:64): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1110 audit(1581326832.768:65): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1105 audit(1581326832.768:66): pid=1>
Feb 10 20:27:12 somepc sudo[1723]: pam_unix(sudo:session): session closed for u>
Feb 10 20:27:12 somepc audit[1723]: USER_END pid=1723 uid=0 auid=1000 ses=2 msg>
Feb 10 20:27:12 somepc audit[1723]: CRED_DISP pid=1723 uid=0 auid=1000 ses=2 ms>
...skipping...
Feb 10 20:25:52 somepc kernel: perf: interrupt took too long (3136 > 3128), low>
Feb 10 20:26:37 somepc systemd[1]: Starting Cleanup of Temporary Directories...
Feb 10 20:26:37 somepc systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Feb 10 20:26:37 somepc systemd[1]: Started Cleanup of Temporary Directories.
Feb 10 20:26:37 somepc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=>
Feb 10 20:26:37 somepc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4>
Feb 10 20:26:37 somepc kernel: audit: type=1130 audit(1581326797.797:61): pid=1>
Feb 10 20:26:37 somepc kernel: audit: type=1131 audit(1581326797.797:62): pid=1>
Feb 10 20:27:12 somepc audit[1723]: USER_AUTH pid=1723 uid=1000 auid=1000 ses=2>
Feb 10 20:27:12 somepc audit[1723]: USER_ACCT pid=1723 uid=1000 auid=1000 ses=2>
Feb 10 20:27:12 somepc sudo[1723]:    user1 : TTY=pts/0 ; PWD=/home/user1 ; USE>
Feb 10 20:27:12 somepc audit[1723]: CRED_REFR pid=1723 uid=0 auid=1000 ses=2 ms>
Feb 10 20:27:12 somepc sudo[1723]: pam_unix(sudo:session): session opened for u>
Feb 10 20:27:12 somepc audit[1723]: USER_START pid=1723 uid=0 auid=1000 ses=2 m>
Feb 10 20:27:12 somepc kernel: audit: type=1100 audit(1581326832.768:63): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1101 audit(1581326832.768:64): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1110 audit(1581326832.768:65): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1105 audit(1581326832.768:66): pid=1>
Feb 10 20:27:12 somepc sudo[1723]: pam_unix(sudo:session): session closed for u>
Feb 10 20:27:12 somepc audit[1723]: USER_END pid=1723 uid=0 auid=1000 ses=2 msg>
Feb 10 20:27:12 somepc audit[1723]: CRED_DISP pid=1723 uid=0 auid=1000 ses=2 ms>
Feb 10 20:27:12 somepc kernel: audit: type=1106 audit(1581326832.778:67): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1104 audit(1581326832.778:68): pid=1>
...skipping...
Feb 10 20:25:52 somepc kernel: perf: interrupt took too long (3136 > 3128), low>
Feb 10 20:26:37 somepc systemd[1]: Starting Cleanup of Temporary Directories...
Feb 10 20:26:37 somepc systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Feb 10 20:26:37 somepc systemd[1]: Started Cleanup of Temporary Directories.
Feb 10 20:26:37 somepc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=>
Feb 10 20:26:37 somepc audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4>
Feb 10 20:26:37 somepc kernel: audit: type=1130 audit(1581326797.797:61): pid=1>
Feb 10 20:26:37 somepc kernel: audit: type=1131 audit(1581326797.797:62): pid=1>
Feb 10 20:27:12 somepc audit[1723]: USER_AUTH pid=1723 uid=1000 auid=1000 ses=2>
Feb 10 20:27:12 somepc audit[1723]: USER_ACCT pid=1723 uid=1000 auid=1000 ses=2>
Feb 10 20:27:12 somepc sudo[1723]:    user1 : TTY=pts/0 ; PWD=/home/user1 ; USE>
Feb 10 20:27:12 somepc audit[1723]: CRED_REFR pid=1723 uid=0 auid=1000 ses=2 ms>
Feb 10 20:27:12 somepc sudo[1723]: pam_unix(sudo:session): session opened for u>
Feb 10 20:27:12 somepc audit[1723]: USER_START pid=1723 uid=0 auid=1000 ses=2 m>
Feb 10 20:27:12 somepc kernel: audit: type=1100 audit(1581326832.768:63): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1101 audit(1581326832.768:64): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1110 audit(1581326832.768:65): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1105 audit(1581326832.768:66): pid=1>
Feb 10 20:27:12 somepc sudo[1723]: pam_unix(sudo:session): session closed for u>
Feb 10 20:27:12 somepc audit[1723]: USER_END pid=1723 uid=0 auid=1000 ses=2 msg>
Feb 10 20:27:12 somepc audit[1723]: CRED_DISP pid=1723 uid=0 auid=1000 ses=2 ms>
Feb 10 20:27:12 somepc kernel: audit: type=1106 audit(1581326832.778:67): pid=1>
Feb 10 20:27:12 somepc kernel: audit: type=1104 audit(1581326832.778:68): pid=1>

cat ~/endeavour-install.log | curl -F 'f:1=<-' ix.io

File doesn’t exist.

lspci > log.txt && lsusb >> log.txt && journalctl -b -0 >> log.txt && cat log.txt | curl -F 'f:1=<-' ix.io
http://ix.io/2bi0

Other systemd logs/analyze:

systemd-analyze blame
Strange I got this output.

Bootup is not yet finished (org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs

Pastebinit:

journalctl -b -0 > ~/journal.txt && pastebinit -i ~/journal.txt -b lpaste.net

I believe you are asking me to run this command, right?

Unknown website, please post a bugreport to request this pastebin to be added (lpaste.net)

So I chose another service

journalctl -b -0 > ~/journal.txt && pastebinit -i ~/journal.txt -b dpaste.com
http://dpaste.com//1SX20PH

lspci > log.txt && lsusb >> log.txt && journalctl -b -0 >> log.txt && pastebinit -i log.txt -b dpaste.com
http://dpaste.com//3Y5Z191

Hardware Information Systems:

inxi -Fxxc0 | curl -F 'f:1=<-' ix.io
http://ix.io/2bi7

I am going to now test this in live mode. Won’t be long

unix_lover · February 10, 2020, 11:17am

@manuel

So now this is the live version mode

Systemd Journal:

After I ran this command journalctl -b -1 > /tmp/journal.last and Specifying boot ID or boot offset has no effect, no persistent journal was found. I got this output.

Specifying boot ID or boot offset has no effect, no persistent journal was found.

cat /tmp/journal | curl -F 'f:1=<-' ix.io
http://ix.io/2biG

cat /tmp/journal.last | curl -F 'f:1=<-' ix.io
No output

cat /tmp/journal.2last | curl -F 'f:1=<-' ix.io
No output

Xsession:

cat ~/.xsession-errors | curl -F 'f:1=<-' ix.io
File doesn’t exist

cat ~/.xsession-errors.old | curl -F 'f:1=<-' ix.io
File doesn’t exist

Xorg (X11):

cat /var/log/Xorg.0.log | curl -F 'f:1=<-' ix.io
File doesn’t exist

cat /var/log/Xorg.0.log.old | curl -F 'f:1=<-' ix.io
File doesn’t exist

Lightdm:

cat /var/log/lightdm/lightdm.log | curl -F 'f:1=<-' ix.io
File doesn’t exist

cat /var/log/lightdm/x-0-greeter.log | curl -F 'f:1=<-' ix.io
File doesn’t exist

Other log providers and options:

journalctl --since "10 minutes ago"

-- Logs begin at Mon 2020-02-10 10:21:28 UTC, end at Mon 2020-02-10 10:58:47 UTC. --
Feb 10 10:55:09 archiso systemd[1]: systemd-hostnamed.service: Succeeded.
Feb 10 10:55:09 archiso audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostname>
Feb 10 10:55:09 archiso kernel: audit: type=1131 audit(1581332109.139:53): pid=1 uid=0 auid=4294967295 ses=429496729>
Feb 10 10:56:19 archiso su[2450]: pam_unix(su:auth): authentication failure; logname= uid=1000 euid=0 tty=pts/1 ruse>
Feb 10 10:56:19 archiso audit[2450]: USER_AUTH pid=2450 uid=1000 auid=1000 ses=1 msg='op=PAM:authentication grantors>
Feb 10 10:56:19 archiso kernel: audit: type=1100 audit(1581332179.119:54): pid=2450 uid=1000 auid=1000 ses=1 msg='op>
Feb 10 10:56:21 archiso su[2450]: FAILED SU (to root) liveuser on pts/1
Feb 10 10:56:24 archiso su[2451]: pam_unix(su:auth): authentication failure; logname= uid=1000 euid=0 tty=pts/1 ruse>
Feb 10 10:56:24 archiso kernel: audit: type=1100 audit(1581332184.615:55): pid=2451 uid=1000 auid=1000 ses=1 msg='op>
Feb 10 10:56:24 archiso audit[2451]: USER_AUTH pid=2451 uid=1000 auid=1000 ses=1 msg='op=PAM:authentication grantors>
Feb 10 10:56:26 archiso su[2451]: FAILED SU (to root) liveuser on pts/1
Feb 10 10:56:33 archiso su[2455]: pam_unix(su:auth): authentication failure; logname= uid=1000 euid=0 tty=pts/1 ruse>
Feb 10 10:56:33 archiso audit[2455]: USER_AUTH pid=2455 uid=1000 auid=1000 ses=1 msg='op=PAM:authentication grantors>
Feb 10 10:56:33 archiso kernel: audit: type=1100 audit(1581332193.832:56): pid=2455 uid=1000 auid=1000 ses=1 msg='op>
Feb 10 10:56:35 archiso su[2455]: FAILED SU (to root) liveuser on pts/1
Feb 10 10:56:50 archiso su[2457]: pam_unix(su:auth): authentication failure; logname= uid=1000 euid=0 tty=pts/1 ruse>
Feb 10 10:56:50 archiso audit[2457]: USER_AUTH pid=2457 uid=1000 auid=1000 ses=1 msg='op=PAM:authentication grantors>
Feb 10 10:56:50 archiso kernel: audit: type=1100 audit(1581332210.065:57): pid=2457 uid=1000 auid=1000 ses=1 msg='op>
Feb 10 10:56:51 archiso su[2457]: FAILED SU (to root) liveuser on pts/1
Feb 10 10:56:58 archiso audit[2458]: USER_ACCT pid=2458 uid=1000 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam>
Feb 10 10:56:58 archiso sudo[2458]: liveuser : TTY=pts/1 ; PWD=/home/liveuser ; USER=root ; COMMAND=/usr/bin/su
Feb 10 10:56:58 archiso audit[2458]: CRED_REFR pid=2458 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,>
Feb 10 10:56:58 archiso kernel: audit: type=1101 audit(1581332218.435:58): pid=2458 uid=1000 auid=1000 ses=1 msg='op>
Feb 10 10:56:58 archiso kernel: audit: type=1110 audit(1581332218.442:59): pid=2458 uid=0 auid=1000 ses=1 msg='op=PA>
Feb 10 10:56:58 archiso sudo[2458]: pam_unix(sudo:session): session opened for user root by (uid=0)
Feb 10 10:56:58 archiso audit[2458]: USER_START pid=2458 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam>
Feb 10 10:56:58 archiso kernel: audit: type=1105 audit(1581332218.445:60): pid=2458 uid=0 auid=1000 ses=1 msg='op=PA>
Feb 10 10:56:58 archiso audit[2459]: USER_AUTH pid=2459 uid=0 auid=1000 ses=1 msg='op=PAM:authentication grantors=pa>
Feb 10 10:56:58 archiso audit[2459]: USER_ACCT pid=2459 uid=0 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_un>
Feb 10 10:56:58 archiso su[2459]: (to root) liveuser on pts/1
Feb 10 10:56:58 archiso kernel: audit: type=1100 audit(1581332218.452:61): pid=2459 uid=0 auid=1000 ses=1 msg='op=PA>
Feb 10 10:56:58 archiso kernel: audit: type=1101 audit(1581332218.452:62): pid=2459 uid=0 auid=1000 ses=1 msg='op=PA>
Feb 10 10:56:58 archiso audit[2459]: CRED_ACQ pid=2459 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_rootok>
Feb 10 10:56:58 archiso su[2459]: pam_unix(su:session): session opened for user root by (uid=0)
Feb 10 10:56:58 archiso audit[2459]: USER_START pid=2459 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam>
Feb 10 10:56:58 archiso kernel: audit: type=1103 audit(1581332218.455:63): pid=2459 uid=0 auid=1000 ses=1 msg='op=PA>
Feb 10 10:56:58 archiso kernel: audit: type=1105 audit(1581332218.455:64): pid=2459 uid=0 auid=1000 ses=1 msg='op=PA>
Feb 10 10:58:47 archiso su[2459]: pam_unix(su:session): session closed for user root
Feb 10 10:58:47 archiso audit[2459]: USER_END pid=2459 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_>
Feb 10 10:58:47 archiso audit[2459]: CRED_DISP pid=2459 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_rooto>
Feb 10 10:58:47 archiso sudo[2458]: pam_unix(sudo:session): session closed for user root
Feb 10 10:58:47 archiso kernel: audit: type=1106 audit(1581332327.559:65): pid=2459 uid=0 auid=1000 ses=1 msg='op=PA>
Feb 10 10:58:47 archiso kernel: audit: type=1104 audit(1581332327.559:66): pid=2459 uid=0 auid=1000 ses=1 msg='op=PA>
Feb 10 10:58:47 archiso kernel: audit: type=1106 audit(1581332327.559:67): pid=2458 uid=0 auid=1000 ses=1 msg='op=PA>
Feb 10 10:58:47 archiso kernel: audit: type=1104 audit(1581332327.562:68): pid=2458 uid=0 auid=1000 ses=1 msg='op=PA>
Feb 10 10:58:47 archiso audit[2458]: USER_END pid=2458 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_>
Feb 10 10:58:47 archiso audit[2458]: CRED_DISP pid=2458 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,>

cat ~/endeavour-install.log | curl -F 'f:1=<-' ix.io
File does not exist.

lspci > log.txt && lsusb >> log.txt && journalctl -b -0 >> log.txt && cat log.txt | curl -F 'f:1=<-' ix.io
http://ix.io/2biJ

Other systemd logs/analyze:

systemd-analyze blame

30.272s dhcpcd@enp4s0.service
 9.730s ldconfig.service
 3.560s lvm2-monitor.service
 3.375s dev-sdb1.device
 1.700s systemd-logind.service
 1.516s dev-loop0.device
  960ms upower.service
  856ms polkit.service
  598ms systemd-udevd.service
  596ms systemd-journald.service
  443ms NetworkManager.service
  398ms udisks2.service
  264ms user@1000.service
  261ms systemd-udev-trigger.service
  162ms systemd-modules-load.service
  155ms wpa_supplicant.service
  104ms systemd-sysusers.service
   61ms systemd-sysctl.service
   55ms systemd-tmpfiles-setup.service
   50ms systemd-journal-catalog-update.service
   49ms dev-hugepages.mount
   48ms systemd-journal-flush.service
   47ms dev-mqueue.mount
   46ms systemd-tmpfiles-setup-dev.service
   46ms sys-kernel-debug.mount
   44ms tmp.mount
   42ms kmod-static-nodes.service
   39ms accounts-daemon.service
   30ms systemd-remount-fs.service
   23ms systemd-tmpfiles-clean.service
   22ms systemd-update-utmp.service
   20ms rtkit-daemon.service
   20ms systemd-rfkill.service
   20ms systemd-user-sessions.service
   16ms user-runtime-dir@1000.service
   16ms systemd-update-done.service
   10ms systemd-random-seed.service
    7ms sys-kernel-config.mount
    6ms sys-fs-fuse-connections.mount

Pastebinit:

journalctl -b -0 > ~/journal.txt && pastebinit -i ~/journal.txt -b dpaste.com
http://dpaste.com//0AFKXTG

lspci > log.txt && lsusb >> log.txt && journalctl -b -0 >> log.txt && pastebinit -i log.txt -b dpaste.com
http://dpaste.com//0E12RVT

Hardware Information Systems:

inxi -Fxxc0 | curl -F 'f:1=<-' ix.io
http://ix.io/2biK

I hope that is all The previous post was about Linux-LTS (no fallback) and in this post this is for the live mode.

manuel · February 10, 2020, 12:51pm

When comparing LTS Xorg logs, after line

[    27.526] (II) modeset(0): Disabling kernel dirty updates, not required.

one log shows total failure and the other not. Seems to fail randomly?

Anyway, the live journal shows nouveau is loading OK. And with LTS, nouveau has issues in the Xorg log.

I guess it is related to the nouveau graphics driver somehow.
As I’m no expert on those, hopefully someone here can help further.

unix_lover · February 10, 2020, 12:58pm

Which Xorg log shows faliure? Is it for the LTS or live mode?

There are times when i start my PC and boot into Endeavour it would crash after logging in, and/or it would crash after I click on an application or if I did something. All though the fallback mode seems a bit more stable than just LTS.

In live mode pretty much everything works except the online installer and I can’t mount the drives nor use gparted unless if I use the installer.

Strange. The LTS is noticebly a bit laggier than the live version. And in the Live version there is screentearing whereas on LTS there is no screen tearing.

If that is the case I could try and attempt to install Nvidia drivers and hope this fixes everything. But what doesn’t make sense is that if other GNU/Linux distros use Nouveau, why is only EndeavourOS unstable while it lags less than other distros?

Thanks man for all your help

ricklinux · February 10, 2020, 1:00pm

@manuel
Other than the graphics card i don’t see an issue with the hardware. It seems to load properly on the live ISO. Could it not be just a bad install?

manuel · February 10, 2020, 1:02pm

This one:
http://ix.io/2bhY

unix_lover · February 10, 2020, 1:03pm

Maybe I should try out Nvidia drivers instead and hope it works?

unix_lover · February 10, 2020, 1:03pm

Oh I see.

unix_lover · February 10, 2020, 1:06pm

Does the logs by any chance show any issues with the RAM? Cause what is strange is that Windows XP and Vista would not work correctly on this PC. And EndeavourOS seems quite unstable so I am curious to know if my RAM is faulty by any chance?

ricklinux · February 10, 2020, 1:18pm

I suppose you could try Nvidia. I’m just wondering if the install wasn’t quite right. It happens. You could always start again and do another install. It’s not a problem to just use replace partition so you select the existing installed partition and reinstall to the same partition that it is currently installed. I have dual boot Windows 10 and i do it all the time albeit i have EndeavourOS on a separate SSD drive. I used to have it on the same drive but i moved it over so i don’t need to worry about my Windows installation because i’m doing so much of it. It’s your decision what you do. I’m just throwing it out there. That is what i would do but that’s me. I don’t think it’s memory but you could always test it.

Edit: If you do another install i would just stick with the current kernel.

unix_lover · February 10, 2020, 1:27pm

Is there a way to validate this or something through some logs or something?

Yeah I could try that if the Nvidia option still fails.

Yes true. I just have a question though, see I have a seperate /home partition and / partition. So I would want to install the OS on / parition. But in the installer do I just select that home partition and select its mount point to be /home? And if so would my username and password be the same if the OS is installed? Or during the installation process would I be prompted to select a new username and password? I am not too sure how this stuff works.

Oh nice I wish I had a separate drive as dual booting does take up quite a bit of space.

Thanks for giving me the options

Do I do a memory test in the grub bootloader screen when I am presented with that option?

I would probably also have LTS just as a backup.

ricklinux · February 10, 2020, 1:48pm

If you decide to do another install just take your time. Boot on the live ISO. Make sure you have an internet connection if you’re on wifi before you start the installer if you are using the online install process.
When you go through the steps to install and it comes to the partitioning you can use replace partition and it will show the current one. You click on that and then it fills in the image below it to show what the new scheme will look like when it replaces it. It should be identical because you are replacing the current install. It’s not very difficult. With the issues you had originally trying to install i’m not sure if you did the offline install? The online install takes a while as it has to download all of the packages so you have to be patient. I don’t know how good your internet is so it takes about 30 minutes or less or more possibly. You can always install the lts kernel at any point. Keep in mind that installing nvidia may not help and you and need it for both the current kernel and lts. It’s an older Nvidia card which isn’t being supported anymore but you can still install the current drivers. You would have to follow the link i posted for that. If the mem test is available in the grub menu you could use that. Not sure whether it’s included anymore. But there are many ways to test the memory. You can do it from a Windows platform also. Good luck!