Manjaro freezes on splash page

journalctl -p err -b 
2 Likes

thanks man.

Haha, gotcha.

Here’s the entire output of the command tbg mentioned

-- Logs begin at Fri 2018-06-22 20:25:08 NDT, end at Wed 2018-07-11 18:27:35 NDT. --
Jul 11 18:24:57 Kelly-linux kernel: ACPI Error: Needed [Integer/String/Buffer], found [Region] ffff93ed16152438 (20170728/exresop-424)
Jul 11 18:24:57 Kelly-linux kernel: ACPI Exception: AE_AML_OPERAND_TYPE, Could not execute arguments for [IOB2] (Region) (20170728/nsinit-426)
Jul 11 18:24:57 Kelly-linux kernel: sp5100_tco: I/O address 0x0cd6 already in use
Jul 11 18:24:57 Kelly-linux kernel: kvm: disabled by bios
Jul 11 18:24:57 Kelly-linux kernel: kvm: disabled by bios
Jul 11 18:27:34 Kelly-linux obexd[860]: stat(/home/noah/phonebook/): No such file or directory (2)
dmesg -w | grep  'error\|seg\|fail\|broke\|warn\|dump' 
2 Likes

output =

[    0.000000] tsc: Fast TSC calibration failed
[    0.000000] tsc: Fast TSC calibration failed
[    3.363867] random: 7 urandom warning(s) missed due to ratelimiting

@AgentS knows way more about your issue than me. I’d listen to any advice he gives you.

2 Likes

I think you might have the entropy bug.

Do this:

sudo pacman -S haveged
sudo systemctl enable haveged
sudo systemctl start haveged
2 Likes

This has some past reports for conflicts and kernel breakages. You can try blacklisting it.
Create a file like sp5100.conf in your /etc/modprobe.d/ (root rights needed).
Paste in this file this in one line

# For avoiding freezes on splash page (or whatever you like)
blacklist sp5100_tco

Save it and reboot to check if it solves the problem.

2 Likes

Ran through commands, I feel like something went wrong though, as it never asked me for the password to super user.
terminal text copied here:

$ sudo systemctl enable haveged
$ sudo systemctl start haveged

Good catch @AgentS. I searched the dmesg errors instead and turned up the entopy bug on that error.

2 Likes

They could be both as a combination :roll_eyes:

Without DDG and yakuake I would n’t be able to answer anything. Just cheating to get bonuses… :grin:

3 Likes

sudo systemctl status haveged

2 Likes

Followed instructions,
Screenshot attached so when things go wrong everyone can easily see what stupid mistake I made. Rebooting and testing now.

1 Like

output =

● haveged.service - Entropy Harvesting Daemon
   Loaded: loaded (/usr/lib/systemd/system/haveged.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2018-07-11 18:58:03 NDT; 1min 12s ago
     Docs: man:haveged(8)
 Main PID: 370 (haveged)
    Tasks: 1 (limit: 4915)
   Memory: 3.8M
   CGroup: /system.slice/haveged.service
           └─370 /usr/bin/haveged -F -w 1024 -v 1

Jul 11 18:58:03 Kelly-linux systemd[1]: Started Entropy Harvesting Daemon.
Jul 11 18:58:03 Kelly-linux haveged[370]: haveged: ver: 1.9.1; arch: x86; vend: ; build: (gcc 7.2.0 ITV); collect: 128K
Jul 11 18:58:03 Kelly-linux haveged[370]: haveged: cpu: (VC); data: 32K (V); inst: 64K (V); idx: 39/40; sz: 59688/59688
Jul 11 18:58:03 Kelly-linux haveged[370]: haveged: tot tests(BA8): A:1/1 B:1/1 continuous tests(B):  last entropy estimate 7.99936
Jul 11 18:58:03 Kelly-linux haveged[370]: haveged: fills: 0, generated: 0
1 Like

@AgentS
no dice, still freezes on the “preparing autostart” screen after login

Back to the drawing board, damn.

If haveged is not helping you can easily disable it.

sudo systemctl stop haveged

sudo systemctl disable haveged

Have you tried installing and testing any different kernels, that could possibly help.

I don’t 100% know what I’m doing, so I wanted to leave that as a last resort
If you dudes recommend it, I’ll try it out though

It’s super easy on Manjaro. Just open Manjaro Settings Manager —> Kernel

Just click the install button to the right of kernel 4.17

Wait till it finishes installing then reboot.

During the boot you will see a grub boot menu.

I believe its “advanced” you want to choose from the menu.

Next you simply select kernel 4.17 to boot from and continue booting.

See how that goes. You should always have at least 2 working kernels installed, so do not uninstall 4.14.

booted into 4.17. Still happens

I figured that was a low probability, but it’s a good thing to always have a second kernel installed anyways. I hope petsam can think of some more suggestions because I’m running low…

Forum kindly sponsored by Bytemark