Hi,
I don't think that would be necessary, I have this "bug" even with my old pc (which has a nvidia).
here the log of my Gentoo beginning of the month at boot :
an 6 08:04:05 localhost kernel: [ 49.892491] Modules linked in: snd_hda_codec_hdmi nouveau snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core ttm snd_pcm
Jan 6 08:04:05 localhost kernel: [ 49.892506] RIP: 0010:gf100_vmm_flush_+0x149/0x190 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892525] nvkm_vmm_iter.constprop.14+0x2ff/0x850 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892535] ? nvkm_vmm_map_choose+0xb0/0xb0 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892545] ? gp100_vmm_pgt_dma+0x220/0x220 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892554] nvkm_vmm_map+0x207/0x3e0 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892564] ? gp100_vmm_pgt_dma+0x220/0x220 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892576] nvkm_vram_map+0x51/0x70 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892587] nvkm_uvmm_mthd+0x742/0x880 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892593] nvkm_ioctl+0x105/0x240 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892599] nvif_object_mthd+0x103/0x130 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892604] ? nvif_object_mthd+0x113/0x130 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892610] nvif_vmm_map+0x115/0x130 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892621] nouveau_mem_map+0x83/0xf0 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892631] nouveau_vma_new+0x1bd/0x1e0 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892641] nouveau_gem_object_open+0x118/0x150 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892653] ? nouveau_gem_new+0x120/0x120 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892662] nouveau_gem_ioctl_new+0x84/0xd0 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892675] ? nouveau_gem_new+0x120/0x120 [nouveau]
Jan 6 08:04:05 localhost kernel: [ 49.892686] nouveau_drm_ioctl+0x5f/0xb0 [nouveau]
....
After rebuild of the kernel setting nouveau as hard build and not a module :
Jan 18 03:47:27 localhost kernel: [ 0.767736] nouveau 0000:01:00.0: NVIDIA GP107 (137000a1)
Jan 18 03:47:27 localhost kernel: [ 0.877512] nouveau 0000:01:00.0: bios: version 86.07.39.80.21
Jan 18 03:47:27 localhost kernel: [ 0.877921] nouveau 0000:01:00.0: Direct firmware load for nvidia/gp107/gr/sw_nonctx.bin failed with error -2
Jan 18 03:47:27 localhost kernel: [ 0.878362] nouveau 0000:01:00.0: gr: failed to load gr/sw_nonctx
Jan 18 03:47:27 localhost kernel: [ 0.878838] nouveau 0000:01:00.0: fb: 2048 MiB GDDR5
Jan 18 03:47:27 localhost kernel: [ 1.528593] nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
Jan 18 03:47:27 localhost kernel: [ 1.528888] nouveau 0000:01:00.0: DRM: GART: 536870912 MiB
Jan 18 03:47:27 localhost kernel: [ 1.529167] nouveau 0000:01:00.0: DRM: BIT table 'A' not found
Jan 18 03:47:27 localhost kernel: [ 1.529444] nouveau 0000:01:00.0: DRM: BIT table 'L' not found
Jan 18 03:47:27 localhost kernel: [ 1.529723] nouveau 0000:01:00.0: DRM: TMDS table version 2.0...
Except the failed firmware (I don't want blob into my kernel), the boot log is alright. This can't really be done on tails since the config shall be more generic to work on most of the device. Maybe seeking the help of the nouveau dev about this issue is the way to go
(Resend using reply all)
--
Securely sent with Tutanota. Get your own encrypted, ad-free mailbox:
https://tutanota.com
Jan 18, 2019, 11:33 AM by segfault@???:
> Hi,
>
> gengreen@??? <mailto:gengreen@tutanota.com>> :
>
>> Here my feedback regarding >> https://tails.boum.org/news/test_usb_images/index.en.html <https://tails.boum.org/news/test_usb_images/index.en.html>>> <>> https://tails.boum.org/news/test_usb_images/index.en.html <https://tails.boum.org/news/test_usb_images/index.en.html>>> >
>>
>> My config : >> https://paste.pound-python.org/show/6PtSaTJhB6wrHa8L3Eic <https://paste.pound-python.org/show/6PtSaTJhB6wrHa8L3Eic/>>> <>> https://paste.pound-python.org/show/6PtSaTJhB6wrHa8L3Eic <https://paste.pound-python.org/show/6PtSaTJhB6wrHa8L3Eic/>>> >
>>
>> Iso was burn into a 16go usb, not branded :
>>
>> [ 151.357958] sd 6:0:0:0: [sdc] 30412800 512-byte logical blocks: (15.6 GB/14.5 GiB)
>> [ 151.358775] sd 6:0:0:0: [sdc] Write Protect is off
>> [ 151.358780] sd 6:0:0:0: [sdc] Mode Sense: 43 00 00 00
>> [ 151.360041] sd 6:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
>> [ 151.375655] sdc: sdc1
>> [ 151.378044] sd 6:0:0:0: [sdc] Attached SCSI removable disk
>> [ 1676.544607] sdc: sdc1
>> dd if=/home/gentoo/tails.iso of=/dev/sdc bs=1M
>>
>> Boot was made in EFI and Legacy dos, in normal and troubleshot mode
>>
>> Error at the boot :
>>
>> https://paste.pound-python.org/show/h6GjEaYbriLKCrmPhcJZ <https://paste.pound-python.org/show/h6GjEaYbriLKCrmPhcJZ/>>> <>> https://paste.pound-python.org/show/h6GjEaYbriLKCrmPhcJZ <https://paste.pound-python.org/show/h6GjEaYbriLKCrmPhcJZ/>>> >
>>
>> But still reach the desktop, almost every applications I tried give this error :
>>
>> Gtk-WARNING **: Could not load a pixbuf from icon theme.
>> This may indicate that pixbuf loaders or the mime database could not be found.
>> **
>> Gtk:ERROR:/build/gtk+3.0-Y9KQNQ/gtk+3.0-3.22.11/./gtk/gtkiconhelper.c:493:ensure_surface_for_gicon: assertion failed: (destination)
>> Aborted
>>
>> After ~15 minutes, the desktop full crash.
>>
>> Tried 4 / 5 times, the same
>>
>
> Thanks for your report. Could you test if you have the same issue on the
> same hardware with Tails 3.11?
>
> Cheers
>
