I do have x11-drv-nouveau installed, but the kernel driver is blacklisted because I’m passing through my 1070 to a VM.
I’ve looked into that and couldn’t find anything about it except a bug report that was closed on the OBS bugtracker saying “fixed” with not much more info. That was back during F25.
For anyone using OpenSUSE with Wayland and yast isn’t launching, just enter xhost +SI:localuser:root in terminal, I tried putting it in a crontab to run at reboot, but that didn’t solve anything, I still have to enter it manually. Anyone have an idea as to how this could be automated?
Anyone have experience with the negativo17 Nvidia driver repo for Fedora? I’m thinking about reconfiguring my system and running proprietary drivers, but I don’t know if I should be using the official .run from nvidia or the ones that are bundled into these RPMs.
@SgtAwesomesauce : it’s has been a while since I switched to OpenSUSE, but from what I remember you have to be careful with Negativo repo. It was great last time I’ve used it, but it really didn’t mix well with some of the other repositories and I had to double check not to get packages mixed up.
I’d like to add a custom menu entry to the grub2 launcher - nothing fancy just a menu with IOMMU enabled. I figured out I need to modify /etc/grub.d/40_custom file:
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 391753fe-f39e-414b-92dc-505c512f73ae
else
search --no-floppy --fs-uuid --set=root 391753fe-f39e-414b-92dc-505c512f73ae
fi
echo 'Wczytywanie systemu Linux 4.4.104-39-default...'
linuxefi /vmlinuz-4.4.104-39-default root=UUID=3d697a71-17d6-4e7f-80df-2a202bc82583 ro resume=/dev/disk/by-uuid/0addf297-4cab-4973-8faa-d6338dc8b573 splash=silent quiet showopts intel_iommu=on
echo 'Wczytywanie początkowego dysku RAM...'
initrdefi /initrd-4.4.104-39-default
}
but how should I set it up so it would pick up new kernel when it gets updated?
If you want it to do this for all kernels in the future, you need to edit the /etc/default/grub file. The way that you did here is the sanctioned way but only for custom entries for a known kernel + configuration.
If you are building your kernel manually or know what you are doing, the proper way to set this up is to make symlinks (ln -s) to the vmlinuz and initrd files such that they point to the current kernel to boot. The symlinks would be named vmlinuz-linux and initrd-linux.
You would then do the same for the precious or recovery kernel and name the symlinks vmlinuz-linux.old and initrd-linux.old and point them to the fall back images. That way you can change the lines
Man, last week was a crappy week. I am happy to report that I didn’t go into rage mode, and go full Windows/OS X/FreeBSD. I stuck through my little issues and it looks like they’ve worked themselves out. The video showing the laptop issue hasn’t happened anymore, I’m using Ubuntu 18.04 with Gnome. It had happened a couple of times on Ubuntu, but Gnome/Linux/Intel must have released an update.
My desktop is working flawlessly, Debian Stretch and i3wm aka suckless tools lmao.
Things couldn’t be better. I am back to my old workflow and more productive than ever. Really glad I toughed it out and stuck with it, because Linux is life <3
