FatDog 812 - problems with nouveau driver ???

[Misaligned]

application: ../nouveau/pushbuf.c:728: nouveau_pushbuf_data: Assertion `kref` failed.
/tmp/.mount_application/AppRun: line 41: 6764 Aborted ${MAIN} "$@"

This is the message I get when I run the "Appimage" from the Terminal. The application window comes up but closes
immediately after that. This is FatDog 812. I usually don't start the App from the terminal this was just to see what's
happening.

Under FatDog 810 everything is fine. Just wanted to mention that I have to run the App as spot.

Do I need an older nouveau driver? If yes, how can I swap it with the current one?

Thanks.

[jamesbond]

nouveau is a kernel driver.

If you want to use a different version of nouveau, you need to use a different kernel.
Follow the instructions here, or here.

Fatdog 810 uses 4.9.92 kernel.

Full list of all kernels ever built for 800 series are here.

[Misaligned]

Jamesbond, thanks for your reply.

I downloaded the FatDog810 kernel and matching modules.sfs.
Created a bootmenu entry to temporarily use this kernel, but after
booting, the screen resolution and aspect ratio is off. Not sure
if I am missing a step?

This happened without use of save file.

[jamesbond]

Most likely because the kernel-modules.sfs you specified, failed to load (or failed to be processed).
Please open terminal and run lsmod. If you see an no output, that confirms it.

If this is the case, can you please post your bootloader entry here.
Also post the output of this: load_sfs.sh --loaded (from terminal) and also losetup -a.

[Misaligned]

As you asumed, lsmod gave me no output.

Here is my boot entry, I also tried it with waitdev=5 after savefile=none, but no difference.

title FatDog64 812/810
rootnoverify (hd0,0)
kernel /boot/vmlinuz-4.19.92 rootfstype=ramfs pmedia=usbflash extrasfs=ramfd812:/boot∕kernel-modules.sfs-4.19.92 savefile=none
initrd /boot/initrd

... and here is the terminal output you asked for.

term-output.png (8.24 KiB) Viewed 1084 times

[jamesbond]

As you asumed, lsmod gave me no output.

Yes, so that confirms the problem.

Here is my boot entry, I also tried it with waitdev=5 after savefile=none, but no difference.

You definitely need that waitdev=5.

Code: Select all

title FatDog64 812/810
  rootnoverify (hd0,0)
  kernel /boot/vmlinuz-4.19.92  rootfstype=ramfs pmedia=usbflash extrasfs=ram:label:fd812:/boot∕kernel-modules.sfs-4.19.92 savefile=none
  initrd /boot/initrd

This looks correct, but for testing, can you use extrasfs=ram:local:/boot∕kernel-modules.sfs-4.19.92 instead of using "label". By the way, you can drop pmedia=usbflash, as Fatdog doesn't use it, but it's harmless otherwise.

If this still doesn't work, you will need to put that kernel-modules.sfs-4.19.92 into initrd, as outlined here.

[Misaligned]

Changing the boot parameter from label to local did not make a difference.

After modifying initrd, I was able to boot into X with a screen resolution as expected.
Unfortunately this did not help me with my initial problem to run the Appimage.
So I checked the terminal output again ... it looked like there is a permission problem
to write to a nouveau buffer (can't recall the exact wording of the message right
now).

Since I have to run the app as spot, maybe spot is too restricted. Maybe there are changes
in the permissions of spot since FD810.

Long story short, creating a new user solved the problem. I only tested the app for a short time,
but everything seems to be running just fine. Now this is still with the older kernel in place,
need to check if this also works with the original kernel in place.

Another thing I ran into though, is switching back and forth between an X session run by the
newly created user or root. Well, at some point the connection to the x server gets lost.
Maybe this would work better if I switch between X sessions that are both run by a regular user?

[Misaligned]

After replacing kernel and kernel modules with the original FD812 files and starting the AppImage as different
non-spot user (newly created user) does NOT work. Works only with FD810 kernel and modules.

Run-as-spot under FD812 and FD810 kernel and modules gives me following terminal output:

FreeCad-spot-nouveau-error.png (44.58 KiB) Viewed 1038 times

User Interface is visible at this point, but clicking on file new closes app and creates output below:

FreeCad-spot-nouveau-error2.png (164.09 KiB) Viewed 1038 times

Not sure what causes this.

Right now I got it working with FD810 kernel and user, still remains to see how stable, haven't done much yet.
Maybe I have to go back to FD810.

[jamesbond]

FreeCAD seems to be having problem with nouveau in general.

You need to use software opengl - which is slow, but at least, doesn't crash.
Some ideas here: https://askubuntu.com/questions/861246/ ... ms#1149351

Other alternative is that you'll have to use NVIDIA proprietary drivers which is suitable for your graphics card.

[Misaligned]

Thanks, Will check into using propriatary driver.