[SOLVED]nouveau kernel module black screen after login & battery

cernunnos · 2023-03-03 17:56:08

Hi all,

After my last pacman -Syu, when I did a reboot, after the first graphic login I got black screen.

Hardware:
Notebook Dell Precision 3560 (0A22)

X Server
Xorg

nouveau version
kmod version 30
+ZSTD +XZ +ZLIB +LIBCRYPTO -EXPERIMENTAL

Kernel version
6.2.1-arch1-1

root@cernunnos modprobe.d]# lshw -C display
  *-display                 
       description: VGA compatible controller
       product: TigerLake-LP GT2 [Iris Xe Graphics]
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       logical name: /dev/fb0
       version: 01
       width: 64 bits
       clock: 33MHz
       capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb
       configuration: depth=32 driver=i915 latency=0 mode=1920x1080 visual=truecolor xres=1920 yres=1080
       resources: iomemory:600-5ff iomemory:400-3ff irq:189 memory:6074000000-6074ffffff memory:4000000000-400fffffff ioport:4000(size=64) memory:c0000-dffff memory:4010000000-4016ffffff memory:4020000000-40ffffffff
  *-display UNCLAIMED [color=#FF0000]--> When I first did this command honestly I don't think it was UNCLAIMED[/color]
       description: 3D controller
       product: TU117GLM [Quadro T500 Mobile]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:01:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list
       configuration: latency=0
       resources: iomemory:600-5ff iomemory:600-5ff memory:a6000000-a6ffffff memory:6000000000-600fffffff memory:6010000000-6011ffffff ioport:3000(size=128)

  *-battery
       product: DELL 75X1619
       vendor: SMP
       physical id: 1
       version: 09/15/2021
       serial: 1043
       slot: Sys. Battery Bay
       capacity: 62280mWh
       configuration: voltage=15,2V

I saw the dmesg |grep nouveau logs and I got;

[   17.937420] nouveau: detected PR support, will not use DSM
[   17.938614] nouveau 0000:01:00.0: NVIDIA TU117 (167000a1)
[   18.066194] nouveau 0000:01:00.0: bios: version 90.17.66.00.25
[   18.091744] nouveau 0000:01:00.0: pmu: firmware unavailable
[   18.124530] nouveau 0000:01:00.0: fb: 2048 MiB GDDR6
[   18.139649] nouveau 0000:01:00.0: sec2: halted
[   18.139659] nouveau 0000:01:00.0: sec2: TRACEPC SCTL 00007021 TIDX 1b1f0000
[   18.139663] nouveau 0000:01:00.0: sec2: TRACEPC: 000023ac
[   18.139667] nouveau 0000:01:00.0: sec2: TRACEPC: 00002055
[   18.139670] nouveau 0000:01:00.0: sec2: TRACEPC: 00002305
[   18.139673] nouveau 0000:01:00.0: sec2: TRACEPC: 0000201c
[   18.139677] nouveau 0000:01:00.0: sec2: TRACEPC: 00002303
[   18.139680] nouveau 0000:01:00.0: sec2: TRACEPC: 00002051
[   18.139683] nouveau 0000:01:00.0: sec2: TRACEPC: 0000269e
[   18.139686] nouveau 0000:01:00.0: sec2: TRACEPC: 00002617
[   18.139689] nouveau 0000:01:00.0: sec2: TRACEPC: 000025e8
[   18.139692] nouveau 0000:01:00.0: sec2: TRACEPC: 000025b2
[   18.139695] nouveau 0000:01:00.0: sec2: TRACEPC: 000025b9
[   18.139699] nouveau 0000:01:00.0: sec2: TRACEPC: 000025aa
[   18.139702] nouveau 0000:01:00.0: sec2: TRACEPC: 000025b9
[   18.139705] nouveau 0000:01:00.0: sec2: TRACEPC: 000025aa
[   18.139707] nouveau 0000:01:00.0: sec2: TRACEPC: 000025b9
[   18.139710] nouveau 0000:01:00.0: sec2: TRACEPC: 000025aa
[   18.139715] nouveau 0000:01:00.0: sec2: TRACEPC: 000025b9
[   18.139718] nouveau 0000:01:00.0: sec2: TRACEPC: 000025aa
[   18.139720] nouveau 0000:01:00.0: sec2: TRACEPC: 000025b9
[   18.139722] nouveau 0000:01:00.0: sec2: TRACEPC: 000025aa
[   18.139725] nouveau 0000:01:00.0: sec2: TRACEPC: 000025b9
[   18.139727] nouveau 0000:01:00.0: sec2: TRACEPC: 000025aa
[   18.139730] nouveau 0000:01:00.0: sec2: TRACEPC: 000025b9
[   18.139732] nouveau 0000:01:00.0: sec2: TRACEPC: 000025aa
[   18.139734] nouveau 0000:01:00.0: sec2: TRACEPC: 000025b9
[   18.139737] nouveau 0000:01:00.0: sec2: TRACEPC: 000025aa
[   18.139739] nouveau 0000:01:00.0: sec2: TRACEPC: 000025b9
[   18.139744] nouveau 0000:01:00.0: sec2: TRACEPC: 00001822
[   18.139747] nouveau 0000:01:00.0: sec2: TRACEPC: 00001a97
[   18.139750] nouveau 0000:01:00.0: sec2: TRACEPC: 000026c8
[   18.139753] nouveau 0000:01:00.0: sec2: TRACEPC: 00002318
[   18.178390] nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
[   18.178394] nouveau 0000:01:00.0: DRM: GART: 536870912 MiB
[   18.178397] nouveau 0000:01:00.0: DRM: BIT table 'A' not found
[   18.178399] nouveau 0000:01:00.0: DRM: BIT table 'L' not found
[   18.178401] nouveau 0000:01:00.0: DRM: Pointer to TMDS table not found
[   18.178403] nouveau 0000:01:00.0: DRM: DCB version 4.1
[   18.179090] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
[   18.183503] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 1
[   21.722294] nouveau 0000:01:00.0: sec2:cmdq: timeout waiting for queue ready
[   21.722299] nouveau 0000:01:00.0: gr: init failed, -110
[   23.754794] nouveau 0000:01:00.0: timeout
[   23.754828] WARNING: CPU: 5 PID: 1597 at drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:840 gf100_gr_fecs_bind_pointer+0x124/0x140 [nouveau]
[   23.754995] Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables libcrc32c nfnetlink bridge 8021q garp mrp stp llc snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi soundwire_bus snd_hda_codec_hdmi snd_soc_core hid_sensor_custom snd_compress snd_ctl_led ac97_bus snd_pcm_dmaengine hid_sensor_hub snd_hda_codec_realtek snd_hda_codec_generic joydev snd_hda_intel dell_rbtn intel_ishtp_hid uvcvideo x86_pkg_temp_thermal intel_powerclamp nouveau snd_intel_dspcfg videobuf2_vmalloc snd_intel_sdw_acpi mei_pxp btusb coretemp mei_hdcp snd_hda_codec hid_multitouch videobuf2_memops dell_laptop iTCO_wdt btrtl intel_pmc_bxt btbcm iwlmvm kvm_intel
[   23.755103] RIP: 0010:gf100_gr_fecs_bind_pointer+0x124/0x140 [nouveau]
[   23.755217]  gf100_grctx_generate+0x2b9/0x720 [nouveau 3a096b63da5e9b4c67695f2bac175524b56b84d9]
[   23.755317]  ? nvkm_vram_map+0x5a/0x80 [nouveau 3a096b63da5e9b4c67695f2bac175524b56b84d9]
[   23.755398]  gf100_gr_chan_new+0x46b/0x490 [nouveau 3a096b63da5e9b4c67695f2bac175524b56b84d9]
[   23.755488]  nvkm_cgrp_ectx_get+0x145/0x1d0 [nouveau 3a096b63da5e9b4c67695f2bac175524b56b84d9]
[   23.755586]  nvkm_cgrp_vctx_get+0xda/0x240 [nouveau 3a096b63da5e9b4c67695f2bac175524b56b84d9]
[   23.755686]  nvkm_chan_cctx_get+0x111/0x210 [nouveau 3a096b63da5e9b4c67695f2bac175524b56b84d9]
[   23.755775]  nvkm_uchan_object_new+0xd9/0x1f0 [nouveau 3a096b63da5e9b4c67695f2bac175524b56b84d9]
[   23.755877]  nvkm_ioctl_new+0x153/0x220 [nouveau 3a096b63da5e9b4c67695f2bac175524b56b84d9]
[   23.755978]  ? __pfx_nvkm_uchan_object_new+0x10/0x10 [nouveau 3a096b63da5e9b4c67695f2bac175524b56b84d9]
[   23.756106]  ? __pfx_gf100_gr_object_new+0x10/0x10 [nouveau 3a096b63da5e9b4c67695f2bac175524b56b84d9]
[   23.756232]  nvkm_ioctl+0xd9/0x180 [nouveau 3a096b63da5e9b4c67695f2bac175524b56b84d9]
[   23.756327]  usif_ioctl+0x26e/0x3f0 [nouveau 3a096b63da5e9b4c67695f2bac175524b56b84d9]
[   23.756452]  nouveau_drm_ioctl+0xa5/0xb0 [nouveau 3a096b63da5e9b4c67695f2bac175524b56b84d9]
[   23.756677] nouveau 0000:01:00.0: gr: failed to construct context
[   23.756724] nouveau 0000:01:00.0: fifo:000000:0002:[Xorg[1597]] ectx 0[gr]: -110
[   23.756727] nouveau 0000:01:00.0: fifo:000000:0002:0002:[Xorg[1597]] vctx 0[gr]: -110

So my resolution was blacklisting that module by adding

blacklist-nouveau.conf

and

modprobe.conf

files in

/etc/modprobe.d/

After I did that, it worked, but I am still not sure if I really did the right thing, because now the battery of my laptop lasts less than two hours, and before it lasted up to 4 hours.. so I think it is caused because there isnt't the required module (which is still a graphical module).

If a do
root@cernunnos modprobe.d]# lsmod |grep -i nouveau
nouveau 3489792 0
mxm_wmi 16384 1 nouveau
drm_ttm_helper 16384 1 nouveau
ttm 102400 3 drm_ttm_helper,i915,nouveau
drm_display_helper 208896 2 i915,nouveau
video 73728 4 dell_wmi,dell_laptop,i915,nouveau
wmi 45056 8 dell_wmi_sysman,video,dell_wmi,wmi_bmof,dell_smbios,dell_wmi_descriptor,mxm_wmi,nouveau

And I see that it is required by other many modules... So this colud be another reason of the durability of the battery.
And after I have enabled it, it doesn't give me any problem with the graphics.. only on the boot
Maybe can I demand if there is an alternative to nouveau? It's just this module that gives me problems.

Hope somebody can help me,
If you need other further information please ask me. Thank y'all in advance!

Last edited by cernunnos (2023-03-09 14:43:41)

V1del · 2023-03-03 19:03:21

Install the nvidia drivers and set the ibt=off kernel parameter. Even if not actively using it the driver will enable proper power saving for the card, especially so if you properly set it up

cernunnos · 2023-03-06 07:55:51

V1del wrote:

Install the nvidia drivers and set the ibt=off kernel parameter. Even if not actively using it the driver will enable proper power saving for the card, especially so if you properly set it up

I think I have already installed all nvidia drivers (mesa & nouveau), because my problem it's just this, and also because I did not have to configure nothing regard the graphic drivers before (like under /etc/udev/rules.d/. which is to configure ad s it is said in the page you linked me, or /etc/modprobe.d/.).

[root@cernunnos modprobe.d]# lspci -k | grep -A 2 -E "(VGA|3D)"
0000:00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] (rev 01)
        Subsystem: Dell Device 0a22
        Kernel driver in use: i915
--
0000:01:00.0 3D controller: NVIDIA Corporation TU117GLM [Quadro T500 Mobile] (rev a1)
        Subsystem: Dell Device 0a22
        Kernel modules: nouveau

---> means for sure that I am only using Intel driver, and that's why my battery durability is short, and why my fans are always active.

And I don't understand why for the NVIDIA card it shows me only nouveau as kernel modules instead of also nvidia_drm, nvidia... Maybe because it lists only the installed modules? Could it be? I know for sure that I still have installed nouveau but I have blacklisted it, and if I

[root@cernunnos modprobe.d]# pacman -Qs nvidia
local/egl-wayland 2:1.1.11-3
    EGLStream-based Wayland external platform
local/libvdpau 1.5-1
    Nvidia VDPAU library
local/libxnvctrl 525.89.02-1
    NVIDIA NV-CONTROL X extension
local/nvidia-settings 525.89.02-1
    Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 525.89.02-2
    NVIDIA drivers utilities

I don't know If the packages are all correct..

seth · 2023-03-06 08:55:22

And I don't understand why for the NVIDIA card it shows me only nouveau as kernel modules

Because you have no kernel module installed, nvidia, nvidia-lts or nvidia-dkms (dependign on your kernel)

Status quo is that you blacklist nouveau w/ nvidia-utils and have no nvidia kernel module, so nothing is driving the GPU.

cernunnos · 2023-03-06 11:21:46

Ok so I don't have NVIDIA modules installed... only nouveau which i already blacklisted because of problems it gave me.

Following the docs https://wiki.archlinux.org/title/NVIDIA#Installation I can't neither find my product series here https://www.nvidia.com/Download/index.aspx (I have NVIDIA Quadro T500...) So consequently I can't find my corresponding codename.

So... by following the Arch documentation I will install the latest drivers.
But my doubt is, following the third step of installation, there is write "for the Maxwell (NV110/GMXXX), for the Turing (NV160/TUXXX) for the Kepler (NVE0/GKXXX), for even older cards"... but there is no explaination for the recent drivers... So I don't know how to proceed how to find the correct and latest drivers.

Can somebody suggest me how to proceed?

seth · 2023-03-06 13:57:41

TU117GLM is a Turing chip (you can also ask google about that) - you also already picked the regular nvidia-utils and which module package (nvidia, nvidia-lts or nvidia-dkms) you need depends, as pointed out, on your kernel.
Since you probably also don't know which that is:

uname -a

cernunnos · 2023-03-06 16:06:53

[root@cernunnos ~]# uname -a
Linux cernunnos 6.2.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 26 Feb 2023 03:39:23 +0000 x86_64 GNU/Linux

@seth you mean that the correct module and its dependencies to install are for Turing chip? Sorry in advance, I still learning about all this, and for now I can't understand how to individuate the product type/product series I have...

seth · 2023-03-06 16:54:49

I can't understand how to individuate the product type/product series I have...

seth wrote:

you can also ask google about that

Linux cernunnos 6.2.1-arch1-1

So install https://archlinux.org/packages/extra/x86_64/nvidia/

cernunnos · 2023-03-07 08:47:23

Well, I have a problem...
I installed that package, added the kernel parameter ibt=off as written in the docs (with grub-customizer, the graphical one), rebooted and now it doesn't even load me the grub...
It skips directly my arch boot and prompts me to the bios.
I tried a few times to reboot by setting arch linux as first boot option and then it disappeared from the boot options... and left me only my USB device with an ubuntu on it...
I'm trying to add the boot option with arch but every file .efi that i'm passing to him, during the boot it shows me for an instant the message at the top of the left of the screen "welcome to GRUB!" and then reboots again because it seems he doesn't want to start...

V1del · 2023-03-07 09:00:36

grub-customizer is broken with current versions of GRUB, you should remove it and configure GRUB manually: https://wiki.archlinux.org/title/GRUB#Configuration You might also have to rerun the grub-install command depending on when you last installed so that the payload is up to date. Which instructions did you follow to install Arch? Is this an archinstall setup?

Last edited by V1del (2023-03-07 09:02:52)

cernunnos · 2023-03-07 09:08:22

I've tried to add the boot option by passing him files
efi/grub/grubx64.efi
grub/x86_64/efi/core.efi (don't really know what means core,efi, but I tried)
grub/x86_64/efi/grub.efi
and none of these boots me correctly

cernunnos · 2023-03-07 09:13:26

@V1del I din't know it was broken... but how can it be so broken that it neither let me access anymore to my os?
How can I remove grub-customizer if it does't boot me to the system? Now I only can prompt to the system with a live usb OS, but I don't know how to continue...

I used archinstaller for my first installation.

Last edited by cernunnos (2023-03-07 09:15:19)

V1del · 2023-03-07 09:44:24

grub-customizer will generate a config that doesn't work anymore with the current versions of GRUB due to outdated assumptions in grub-customizer (it's a bit of a special situation since Arch currently ships prereleases of GRUB due to CVE mitigations, so grub-customizer isn't "strictly" to blame here). It doesn't matter which grub efi you boot they will all use the broken config. Boot into the live disk, mount your root partition to /mnt do a

arch-chroot /mnt
mount -a
pacman -Rns grub-customizer
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB #Double check the efi-directory, it will depend on where you've mounted your ESP, check fstab/findmnt in doubt on where you mount the ESP
#Check /etc/default/grub and make sure ibt=off is added to the GRUB_CMDLINE_LINUX_DEFAULT key
grub-mkconfig -o /boot/grub/grub.cfg

post the error messages/output if any appear: https://wiki.archlinux.org/title/List_o … n_services

cernunnos · 2023-03-07 10:59:38

Before I proceed with the grub installation, I have a doubt for the pacman command;

pacman -Rns grub-customizer

Will be worth if my live os is an Ubuntu (if I install pacman but I don't think there is a version for my current ubuntu) and will it recognize to use that command on the right disk?
An alternative is that I can do it from another usb with the arch iso live, but I would like to try before if this is the right method.

Also I want to say that before using the grub-customizer I created a backup file for /boot/grub/grub.cfg; it is stored in the same directory.
Could be helpful just renaming it to "grub.cfg"?
In the actual situation I can't know what is the name of the grub-customizer's generated config if I don't mount the disk... So I think that the grub-customizer just changed the options in /boot/grub/grub.cfg, which still has the same name.

seth · 2023-03-07 11:59:27

Will be worth if my live os is an Ubuntu (if I install pacman but I don't think there is a version for my current ubuntu)

V1del wrote:

arch-chroot /mnt

Sicne there won't be "arch-chroot" on a ubuntu live system, you could either just use the arch install iso or will have to chroot manually, https://wiki.archlinux.org/title/Chroot#Using_chroot

d.ALT · 2023-03-07 13:57:02

seth wrote:

Will be worth if my live os is an Ubuntu (if I install pacman but I don't think there is a version for my current ubuntu)
V1del wrote:
arch-chroot /mnt
Sicne there won't be "arch-chroot" on a ubuntu live system

Yup... But one could go with

$ sudo apt install arch-install-scripts

(Ubuntu's arch-install-scripts)

cernunnos · 2023-03-07 18:01:52

I'm still trying to solve... keep having patience
Now the situation is; I tried to install on another usb device archlinux but when I try to run

arch-chroot /mnttest /bin/bash

It prompts me

chroot:failed to run command '<weirdcharacter>bin/bash<weirdcharacter>': No such file or directory

Where I put <weirdcharacter> there is a square symbol that I guess it means that something is wrong with the installation... I will try to reinstall again.
Meanwhile I tried on the usb device with ubuntu by chrooting manually but when I try for example to

mount -t /proc proc/

it says me that

mount: proc/ can't find in /etc/fstab

Same output wih mounting other directories. I already mounted my test mountpoint with mount --bind /mnttest /mnttest -->https://man.archlinux.org/man/arch-chroot.8

Then I went back to usb with ubuntu and installed arch-install-scripts package (@d.ALT grazie mille!) and it provided me the scripts.
Also in this case it gives me that there is no such file or directory for /bin/bash (but without any special character)

Last edited by cernunnos (2023-03-07 18:05:29)

V1del · 2023-03-07 18:21:29

Are you mounting the root partition of your Arch install or what exactly are you mounting? You need to mount the root partition of your Arch install. Use the link above and post the output of

lsblk -f
ls -l /mnttest

cernunnos · 2023-03-08 09:58:00

Ok I was just skipping the most important part (first step by mounting the partition that doesn't start).
So now when I try to mount the partition of my disk on the usb live I get

root@ubuntu-DR:/# mount -o exec /dev/nvme0n1p2 /mnttest
mount: /mnttest: unknown filesystem type 'crypto_LUKS'.

And as we see in the following output, when I did my first installation on other disk I encrypted the partition for / ---> /dev/nvme0n1 is the hard disk of my computer to which I have to access;

root@ubuntu-DR:/# lsblk -f
NAME        FSTYPE      FSVER LABEL UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0       squashfs    4.0                                                    0   100% /snap/bare/5
loop1       squashfs    4.0                                                    0   100% /snap/core20/1822
loop2       squashfs    4.0                                                    0   100% /snap/core20/1828
loop3       squashfs    4.0                                                    0   100% /snap/firefox/2356
loop4       squashfs    4.0                                                    0   100% /snap/firefox/2391
loop5       squashfs    4.0                                                    0   100% /snap/gnome-3-38-2004/112
loop6       squashfs    4.0                                                    0   100% /snap/gnome-3-38-2004/119
loop7       squashfs    4.0                                                    0   100% /snap/gtk-common-themes/1535
loop8       squashfs    4.0                                                    0   100% /snap/snapd/17950
loop9       squashfs    4.0                                                    0   100% /snap/snapd/18357
sda                                                                                     
├─sda1                                                                                  
├─sda2      vfat        FAT32       BFD5-55BC                             506,7M     1% /boot/efi
└─sda3      ext4        1.0         4c1d8357-9ff6-4c9c-8f1f-d4f431dae5e1   15,6G    39% /var/snap/firefox/common/host-hunspell
                                                                                        /
nvme0n1                                                                                 
├─nvme0n1p1 vfat        FAT32       9483-893C                                           
├─nvme0n1p2 crypto_LUKS 2           0d1680db-7a57-49db-9e95-b22385d8be1b                
└─nvme0n1p3 crypto_LUKS 2           317f48f0-ffc6-4f17-a549-a0a0d2f2dcdf

So in that disk I have three partitions

Disk /dev/nvme0n1: 476,94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: PC711 NVMe SK hynix 512GB               
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 11583A86-A5B5-4ABD-8849-D3B395A40362

Device            Start        End   Sectors   Size Type
/dev/nvme0n1p1    10240    1001471    991232   484M EFI System
/dev/nvme0n1p2  1011712   39061503  38049792  18,1G Linux filesystem
/dev/nvme0n1p3 40038400 1000214527 960176128 457,8G Linux filesystem

The 484M one is for the boot, the 18,1G one is for the / filesystem (encrypted during the installation), and the other 457,8G is for /home. The configuration for the partitioning was also done with archinstaller choosing the suggested option, so it has to be the default.

Searching online I found here
Where an user explains that is necessary first decrypt the partition with

cryptsetup luksOpen /dev/sdb1 mydata

Where his "mydata" stands for the encrypted partition which he can see, but in my case I can't because I can't mount the fs.

I would like to open the enrcypted partition and mount it for chrooting without losing the data, like explained in the first answer here

luks - create a new block device encrypted over existing block device. Not filesystem - so you can't mount it directly after opening. But - all data are lost.

Last edited by cernunnos (2023-03-08 11:47:44)

seth · 2023-03-08 12:40:31

"mydata" is what the decrypted device will be available as in /dev/mapper/mydata

cernunnos · 2023-03-08 13:53:26

Ok, so would it be safe if I will unencrypt the partition of the disk which I have to access in, without losing my data? I'm now from the live USB.

I will do

cryptsetup luksOpen /dev/nvme0n1p2 unencrypteddata

And this will get me /dev/mapper/unencrypteddata

and then try to mount

mount -o exec /dev/mapper/unencrypteddata /mnttest

(same for /dev/nvme0n1p3)

Once terminated the chroot step and the system will boot again, is it sure that I will access to the other disk again without inserting password each time during the boot.
Would it be correct?

cryptsetup luksFormat /dev/mapper/unencrypteddata

seth · 2023-03-08 14:05:33

(same for /dev/nvme0n1p3)

You don't need to decrypt or mount your home partition, and that will help to protect your user data against errors.

EDIT: BUT DON'T FORGET TO MOUNT THE BOOT PARTITION

And nothign will be safe ever.
You're always exactly one dd-flub away from shredding your drive.

So try and pay attention what you do.

Last edited by seth (2023-03-08 14:12:39)

cernunnos · 2023-03-08 16:26:41

Yay finally I got it with chroot (I managed directly with chroot instead of arch-chroot so I could learn better its funcionality).
When I chrooted inside my system, the steps that I did are
- Removing that bad package.

pacman -Rns grub-customizer

- Entered in /boot and checked the differences between grub.cfg and grub.cfg_backup and there were a lot of differences...
Maybe it's because I don't know a lot about, but is it possible that the grub-customizer modified also the other files like grubenv, grubx64.efi and others?
I'm asking this because I only renamed the backup file to "grub.cfg"
- Umounted and rebooted in order to access to the other system, and successfully acceded to the archlinux grub, and entered the password for the unencryption for the partition as I always did, but after that, the kernel loads some log messages on the screen and then the system remains with black screen and a line on the top of the left, it doesn't even let me use tty2, tty3...

So I guess I maybe have to reinstall the grub entirely as @V1del suggested some messages before.
If needed I can post the logs of the kernel before it remains with black screen.

cernunnos · 2023-03-08 21:27:00

Update: I succeded to enter to my system back!
I restored the grub.cfg file to its original configuration from the backup file that I have created before the mess.
As I said in my last message after that modification I could access to the archlinux grub but It didn't load my graphical environment, giving me a kernel log "Failed to load modules".

At the end I fount out that the problem was the nvidia package that I have installed;

extra/nvidia 525.89.02-5

So that means that my Turnig chip doesn't like it.
So now I am at the initial step of the problem; my notebook now only works with intel vga controller.
I'll look better tomorrow for the nvidia drivers and will try them out.

seth · 2023-03-08 21:32:52

As I said in my last message after that modification I could access to the archlinux grub but It didn't load my graphical environment, giving me a kernel log "Failed to load modules".

What means you're most likely not booting the installed kernel.

So that means that my Turnig chip doesn't like it.

No, your turing chip likes that.

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Arch Linux

#1 2023-03-03 17:56:08

[SOLVED]nouveau kernel module black screen after login & battery

#2 2023-03-03 19:03:21

Re: [SOLVED]nouveau kernel module black screen after login & battery

#3 2023-03-06 07:55:51

Re: [SOLVED]nouveau kernel module black screen after login & battery

#4 2023-03-06 08:55:22

Re: [SOLVED]nouveau kernel module black screen after login & battery

#5 2023-03-06 11:21:46

Re: [SOLVED]nouveau kernel module black screen after login & battery

#6 2023-03-06 13:57:41

Re: [SOLVED]nouveau kernel module black screen after login & battery

#7 2023-03-06 16:06:53

Re: [SOLVED]nouveau kernel module black screen after login & battery

#8 2023-03-06 16:54:49

Re: [SOLVED]nouveau kernel module black screen after login & battery

#9 2023-03-07 08:47:23

Re: [SOLVED]nouveau kernel module black screen after login & battery

#10 2023-03-07 09:00:36

Re: [SOLVED]nouveau kernel module black screen after login & battery

#11 2023-03-07 09:08:22

Re: [SOLVED]nouveau kernel module black screen after login & battery

#12 2023-03-07 09:13:26

Re: [SOLVED]nouveau kernel module black screen after login & battery

#13 2023-03-07 09:44:24

Re: [SOLVED]nouveau kernel module black screen after login & battery

#14 2023-03-07 10:59:38

Re: [SOLVED]nouveau kernel module black screen after login & battery

#15 2023-03-07 11:59:27

Re: [SOLVED]nouveau kernel module black screen after login & battery

#16 2023-03-07 13:57:02

Re: [SOLVED]nouveau kernel module black screen after login & battery

#17 2023-03-07 18:01:52

Re: [SOLVED]nouveau kernel module black screen after login & battery

#18 2023-03-07 18:21:29

Re: [SOLVED]nouveau kernel module black screen after login & battery

#19 2023-03-08 09:58:00

Re: [SOLVED]nouveau kernel module black screen after login & battery

#20 2023-03-08 12:40:31

Re: [SOLVED]nouveau kernel module black screen after login & battery

#21 2023-03-08 13:53:26

Re: [SOLVED]nouveau kernel module black screen after login & battery

#22 2023-03-08 14:05:33

Re: [SOLVED]nouveau kernel module black screen after login & battery

#23 2023-03-08 16:26:41

Re: [SOLVED]nouveau kernel module black screen after login & battery

#24 2023-03-08 21:27:00

Re: [SOLVED]nouveau kernel module black screen after login & battery

#25 2023-03-08 21:32:52

Re: [SOLVED]nouveau kernel module black screen after login & battery

Board footer