Manjaro crashes after installation

Hi guys,

yesterday I installed Manjaro on my Acer Aspire 717 - 72G, in dual boot with a Windows 10.
The installation finished perfectly, but after rebooting, the system crashes.
I either get stuck in the grub terminal and I’m asked to run fsck on my partition (which ends in random numbers running over my screen :frowning: )
If Manjaro starts, it runs for a while perfectly and “forgets” his filesystem sometime. I cant start any porgramm (e.g. the terminal). After rebooting I get stuck in the Grub terminal. :expressionless:

Anyone got a solution?

Thank you for your help :slight_smile:


This happens after I run fsck

Please boot the installer and post the output from running inxi -Fxxxz (as text).

here is the output:

System:    Host: manjaro Kernel: 4.14.65-1-MANJARO x86_64 bits: 64 compiler: gcc v: 8.2.0 
           Desktop: KDE Plasma 5.13.4 tk: Qt 5.11.1 wm: kwin_x11 dm: sddm Distro: Manjaro Linux 
Machine:   Type: Laptop System: Acer product: Aspire A717-72G v: V1.19 serial: <filter> 
           Mobo: CFL model: Charizard_CFS v: V1.19 serial: <filter> UEFI: Insyde v: 1.19 date: 07/13/2018 
Battery:   ID-1: BAT1 charge: 49.9 Wh condition: 49.9/48.9 Wh (102%) volts: 16.9/15.2 model: LG PABAS0241231 
           type: Li-ion serial: <filter> status: Full 
CPU:       Topology: 6-Core model: Intel Core i7-8750H bits: 64 type: MT MCP arch: Skylake rev: A 
           L2 cache: 9216 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 53004 
           Speed: 800 MHz min/max: 800/4100 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 
           7: 801 8: 800 9: 801 10: 800 11: 801 12: 800 
Graphics:  Card-1: Intel vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:3e9b 
           Card-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: Acer Incorporated ALI driver: nouveau 
           v: kernel bus ID: 01:00.0 chip ID: 10de:1c8d 
           Display: x11 server: X.Org 1.20.1 driver: intel,nouveau unloaded: modesetting 
           alternate: fbdev,nv,vesa compositor: kwin x11 resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2) v: 4.5 Mesa 18.1.6 
           compat-v: 3.0 direct render: Yes 
Audio:     Card-1: Intel Cannon Lake PCH cAVS vendor: Acer Incorporated ALI driver: snd_hda_intel v: kernel 
           bus ID: 00:1f.3 chip ID: 8086:a348 
           Sound Server: ALSA v: k4.14.65-1-MANJARO 
Network:   Card-1: Intel Wireless-AC 9560 [Jefferson Peak] driver: iwlwifi v: kernel bus ID: 00:14.3 
           chip ID: 8086:a370 
           IF: wlp0s20f3 state: down mac: <filter> 
           Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: 2.3LK-NAPI 
           port: 3000 bus ID: 07:00.1 chip ID: 10ec:8168 
           IF: enp7s0f1 state: down mac: <filter> 
Drives:    Local Storage: total: 1.16 TiB used: 2.01 GiB (0.2%) 
           ID-1: /dev/nvme0n1 vendor: Intel model: SSDPEKKW256G7 size: 238.47 GiB speed: 31.6 Gb/s lanes: 4 
           serial: <filter> rev: PSF109C scheme: GPT 
           ID-2: /dev/sda vendor: Western Digital model: WD10SPZX-21Z10T0 size: 931.51 GiB speed: 6.0 Gb/s 
           rotation: 5400 rpm serial: <filter> rev: 1A02 scheme: GPT 
           ID-3: /dev/sdb type: USB model: General USB Flash Disk size: 14.45 GiB serial: <filter> rev: 1.00 
           scheme: MBR 
Partition: ID-1: / size: 11.63 GiB used: 88.8 MiB (0.7%) fs: overlay dev: ERR-102 
Sensors:   System Temperatures: cpu: 46.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 259 Uptime: 1m Memory: 15.51 GiB used: 721.2 MiB (4.5%) Init: systemd v: 239 Compilers: 
           gcc: 8.2.0 Shell: bash v: 4.4.23 running in: konsole inxi: 3.0.20
1 Like

Have a read through this tutorial thread:

Are you sure you booted Live media in UEFI (and installed as well) ?

@jonathon
I tried those settings, but nothing really changed. My laptop freezes now directly after the login :confused:

@petsam I’m sure, I created a Bootstick in UEFI.
The Installation should be in UEFI, too.

But I need facts to be sure. Manjaro Live media are hybrid, both MSDOS and UEFI. Use this tutorial to check your boot mode

If you are on UEFI, boot to TTY and get this

inxi -puo

Read this as well

I see you are running a Intel i7-8750 :drooling_face: - with Intel 630 Graphics.

You should be able to get the Intel graphics running with no problems.

But it is a fairly new CPU/GPU combo so there could be something needing tweaking.

And you are on kernel 4.14 - You will no doubt get better result by downloading the beta version of KDE as it has kernel 4.19.

So,
I booted in UEFI mode. /Thanks for the Tutorial :smiley:

This is the output of inxi -puo

Partition:
 ID-1: / size: 11.63 GiB used: 90.3 MiB (0.8%) fs: overlay dev: ERR-102 
 uuid: N/A 
 ID-2: /run/miso/bootmnt size: 1.98 GiB used: 1.98 GiB (100.0%) 
 fs: iso9660 dev: /dev/sdb1 uuid: 2018-09-27-19-01-20-00 
Unmounted:
 ID-1: /dev/nvme0n1p1 size: 100.0 MiB fs: vfat label: ESP 
 uuid: 8696-71B7 
 ID-2: /dev/nvme0n1p2 size: 16.0 MiB fs: N/A label: N/A uuid: N/A 
 ID-3: /dev/nvme0n1p3 size: 129.94 GiB fs: ntfs label: Acer 
 uuid: 12D698F0D698D577 
 ID-4: /dev/nvme0n1p4 size: 108.42 GiB fs: ext4 label: N/A 
 uuid: d34b0cbd-a9e4-4faf-a4c4-7b9d8debff84 
 ID-5: /dev/sda1 size: 931.51 GiB fs: ntfs label: Data 
 uuid: DCDE9EB3DE9E8584 
 ID-6: /dev/sdb2 size: 4.0 MiB fs: vfat label: MISO_EFI uuid: 1DE8-4957 

I tried the beta, but after the login, the screen freezes.
After the first login + reboot, I get this error:

mount: /new_root: mount(2) system call failed l: structure needs cleaning
You are now being dropped into an emergancy shell. 
sh: can't access tty; job control turned off
[rootfs ] #

We need this from your installation. Use the 1st tutorial to boot to your installed Manjaro grub and the 2nd tutorial to boot to TTY of the installation (edit grub). Then get info, (inxi and/or as stated in 1st tutorial) and post via wgetpaste (2nd tutorial)

Oh oops sorry :expressionless:

Now here’s the right output:

Partition: ID-1: / size 106.22 GiB used: 6.32 GiB (6,0%) fs: ext4 dev: /dev/nvme0n1p1 uuid: 06104aaf-4221-47c1-bc19-5abc09676b0c
 ID-2: /boot/efi size: 69.0 MiB used: 64.9 MiB (67.6%) fs: vfat dev: /dev/nvme0n1p1 uuid: 8696-71B7
Unmounted: ID-1: /dev/nvme0n1p1 size: 16.0 MiB fs: <root required> label: N/A uuid: N/A
ID-2: /dev/nvme0n1p3 size: 129.94 GiB fs: ntfs label: Data uuid: 12D698F0D698D577
ID-3: /dev/sda1 size: 931.51 GiB fs: ntfs label: Data uuid: DCDE9EB3DE9E8584
ID-4: /dev/sdb1 size: 2.01 GiB fs: iso9660 label: MJR17112 uuid: 2018-08-15-15-33-20-00
ID-5: /dev/sdb2 size: 4.0 MiB fs: vfat label: MISO_EFI uuid: AA50-706E

I hope, this is the information you need :]

It looks fine (apart from a minor inxi bug @h2-1 might check mounted parririons names ).

@desman24 please try the fallback kernel at grub.
You may check your BIOS settings for AHCI or something else (I don’t really know) .
You could also try to startx from TTY and watch for errors.
Have you done a full update of your system? If not, do this first.

The SATA mode is AHCI, the other option is RST with Optane.

I tried the fallback kernel, but there is the same problem.
startx didn’t show any errors, after this I successfully switched to the desktop.

I will do a full update, but later this day. :-

-- Reboot --
Okt 02 07:05:40 Aspire-7 kernel: tpm tpm0: TPM self test failed
Okt 02 07:05:40 Aspire-7 kernel: genirq: Setting trigger mode 8 for irq 135 failed (intel_gpio_irq_type+0x0/0x110 [pinctrl_intel])
Okt 02 07:05:40 Aspire-7 kernel: genirq: Setting trigger mode 8 for irq 135 failed (intel_gpio_irq_type+0x0/0x110 [pinctrl_intel])
Okt 02 07:05:40 Aspire-7 kernel: iTCO_wdt iTCO_wdt: can't request region for resource [mem 0x00c5fffc-0x00c5ffff]
Okt 02 07:05:43 Aspire-7 kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 409800 [ TIMEOUT ]
Okt 02 07:05:45 Aspire-7 kernel: nouveau 0000:01:00.0: gr: init failed, -16
Okt 02 07:07:01 Aspire-7 kernel: [TTM] Buffer eviction failed
Okt 02 07:07:16 Aspire-7 kernel: nouveau 0000:01:00.0: DRM: failed to idle channel 0 [DRM]
Okt 02 07:07:16 Aspire-7 kernel: BUG: unable to handle kernel paging request at ffffa05e0dc15100
Okt 02 07:07:16 Aspire-7 kernel: IP: evo_wait+0x56/0x120 [nouveau]
Okt 02 07:07:16 Aspire-7 kernel: RIP: evo_wait+0x56/0x120 [nouveau] RSP: ffffbd4a81ca3c70
-- Reboot --
Okt 02 07:11:01 Aspire-7 kernel: tpm tpm0: TPM self test failed
Okt 02 07:11:01 Aspire-7 kernel: genirq: Setting trigger mode 8 for irq 135 failed (intel_gpio_irq_type+0x0/0x110 [pinctrl_intel])
Okt 02 07:11:01 Aspire-7 kernel: genirq: Setting trigger mode 8 for irq 135 failed (intel_gpio_irq_type+0x0/0x110 [pinctrl_intel])
Okt 02 07:11:02 Aspire-7 kernel: iTCO_wdt iTCO_wdt: can't request region for resource [mem 0x00c5fffc-0x00c5ffff]

Thats a part off the output from journalctl -p3
The first start, I switched to the desktop mode, in the second boot i stayed in tty.

I think I found a solution using the beta version v18. 0-beta7 and the tutorial for hybrid GPUs
( without doing step 2; this would break the installation)

$ systemctl status bumblebeed

returns

● bumblebeed.service - Bumblebee C Daemon
   Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2018-10-02 16:30:02 CEST; 3min 17s ago
 Main PID: 527 (bumblebeed)
    Tasks: 1 (limit: 4915)
   Memory: 1.3M
   CGroup: /system.slice/bumblebeed.service
           └─527 /usr/bin/bumblebeed --use-syslog

and

optirun -b none nvidia-settings -c :8

successfully starts nvidia-settings

I will watch out for problems, but now it works perfectly fine :blush:

For now I think, this topic is closed; thanks to you all helping me :smile:

What you actually did was change gpu drivers from free to non -free (bumblebee).
For the shake of the forum workflow, you should mark Jonathon 's post as solution, not yours. It points to the first advice that led to the solution.

1 Like

No bug I can see, maybe a problem with df -kTP output, can’t say without seeing user debugger data.

inxi doesn’t really makeup any of the dev locations, so it looks to me like maybe there’s a problem with the mounts, or something slightly odd or unusual, but I won’t guess at it without data.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.