Yes! Mouse much better now and boot faster this time. But as before I get a lot of "abrt-applet error boxes when Fedora window opens up.
The PixInsight app still isn’t working properly yet.
Also, should I do a dnf upade? I didn’t do that before I installed RPM Fusion drives.
Although mouse is operating fine.
Which one of these files I add “nvidia-drm.modeset=1”, so I don’t have to edit Grub every time I boot.
Or is it in the home directory?
Also when I opened the PixInsight app, eventually the black screen appears with “booting a command line list” and it hangs up. I have to turnoff the computer.
installing the drivers from rpmfusion pulls in the required versions of the depemdencies, but it is good practice to do a dnf upgrade whenever installing new software.
That line needs to be added to the proper line in /etc/default/grub.
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 initcall_blacklist=simpledrm_platform_driver_init rd.lvm.lv=fedora_laptop/root rhgb quiet"
Using sudo edit /etc/default/grub and add that option into the command line as shown above.
Once the file is saved then run sudo grub2-mkconfig -o /boot/grub2/grub.cfg.
Now when you reboot the option will already be in the kernel command line in grub.
Note that your command line should not exactly match mine since the installs are different. This is just an example of which line to add the option into.
That works, thanks again. FYI, the Linus I have doesn’t recognize the command edit, perhaps it’s an alias. I used vi to edit.
Now I have to troubleshoot PixInsight application.
Isn’t the recommend way to do this stuff to use grubby?
grubby --add-args=nvidia-drm.modeset=1 --update-kernel
At least that is what I’ve been doing to make sure that the kernel command line is consistent over updates etc.
@computersavvy Is nvidia-drm.modeset=1 documented somewhere as required for wayland?
It seems odd that a driver in 2023 is not always doing drm modeset.
I think this is going off topic, but from threads on this forum it seems the change in the way akmod-nvidia is installed recently has removed that option from what was previously automatically added into the command line in /etc/default/grub. I have noted that for some (my own systems included), and probably dependent upon hardware combinations, the option appears necessary. As such it is worth testing and if it works then making it permanent.
For others, it seems the option nomodeset may be required for the first boot after a new installation.
Here is the grub file.
If this needs to be change, please inform.
The PixInsight is not working well. When the updated packages are uploaded, I have to move my mouse (cursor) around. If I don’t, upload pauses. Hard to do for long packages. I sent this problem out to PixInsight Forum. If you know the fix, I would appreciate.
And of course, I appreciate you all in this post for introducing me to RPM Fusion and working through the boot problem.
As with PI forum, I’m going to send you the before and after “About this System”.
Before drivers update;
After driver update with RPM Fusion;
Fedora has a problem!!!
I was notified that I needed an update, from the lower right side of task bar. It appears it was the same update I did before.
As soon update was completed, I’m back to square one.
Slow to open Fedora and cursor erratic. I’ll do the same modeset all over again.
There is definitely an ongoing problem.
Grub file still intact. Something else going on with same symptoms as before. This what came up without me touching it.
Also a lot of “abt-applet” showing up, when Fedora opens up.
Again I uninstall PI and reboot. Fedora started slow (cursor), eventually ran normally. I restarted again and took Fedora an long time for login window to appear. The second restart, selected Fedora again in boot menu, the login window never appeared, screen blank. Thus I had to turn off the computer.
One more note. When I open PixInsight, I still get this warning.
No running X11 composite manger has been detected
I don’t use pixinsight, but that message seems to indicate one should be logged in using xorg for it to function properly.
Maybe you are having issues because of wayland and if you log out then log back in with xorg it may properly function
There are multiple posts on PixInsight forum about lack of Wayland support.
This is just a wild guess, but PixInsight appears to be Qt-based. You can try setting QT_QPA_PLATFORM=xcb to make Qt-based apps use X11.
Based on the forum, I think PixInsight is started like this:
/opt/PixInsight/bin/PixInsight.sh
So you would do this instead:
env QT_QPA_PLATFORM=xcb /opt/PixInsight/bin/PixInsight.sh
If it works you can edit the desktop file to make it permanent.
Otherwise, your best option is to use an X11 session (select it from the login screen).
I have boot problems.
The first one never reached login but left cursors marks all over the screen.
The second one I selected was able to login into Fedora, but a minute later the screen went blank. I had to unplug the computer.
The third on I selected is OK.
The 4th is new also, a rescue.
How do I clean up the Grub boot menu?
And how do I log back in xorg? I don’t see the option anywhere?
