VFS: Unable to mount root fs on unknown-block(0,0)
This is my first time installing Linux, any suggestions?
Second monitor freezing
Hey guys, I'm a new user and a pretty big Linux noob. I've been hanging out on Bazzite for a few days now and stuff mostly works fine, but whenever I play any video game on main monitor I can't interact with my second monitor anymore.
Like when I try to open a new tab on FireFox nothing visually happens, but after I close the game I do see new empty tabs. So it does register clicks but it doesn't visually do anything while a game is running.
I've looked through the posts here but couldn't really find anything....
Extremely slow boot times
New to Linux - please be patient with me!
Since installing Bazzite on my HP Omen 17 recently (dual-booting on the same drive as a Windows install, has a Nvidia GPU), the boot times have become extremely slow. From pressing the power button:
1. 25 seconds to get to Grub (this delay doesn't always happen)
2. +1:25 after Grub to get to the Omen logo...
Snaps on Bazzite
Hi! I'm trying to install a snap package (Processing) on Bazzite.
I tried installing it on a Debian Distrobox, but it shoots out this error:
error: cannot communicate with server: Post "http://localhost/v2/snaps/processing": dial unix /run/snapd.socket: connect: no such file or directory...
Help using a USB GPS device
Hi there, I've just purchased a VK-162 GPS device form Aliexpress. It's a USB GPS device that I want to use with GNOME maps.
I'm struggling to make it visible to the flatpak, unsure whether it's to expose the USB hardware, or systemd gpsd to the flatpak.
Or whether it's flatpak xdg in Flatseal/KDE flatpak permissions.
Help would be appreicated...
Slow boot times.
I’m using a Ryzen 9800X3D cpu with 32GB DDR5 6000 RAM, I have a Powercolor Hellhound 9070 XT gpu and I’m booting from a 2 TB WD BLACK SN850X M.2.
Booting from a full shutdown or restart takes 1:45 or longer.
Pressing esc during boot gives me this error and hangs for about 50 seconds before finally booting (with a few systemd errors). ...
Solution:
Try running
systemd-analyze blame which will show which services are taking long to start up. You can get much more details by running systemd-analyze plot > ~/boot-times.svg which will make an svg image in your home folder with a plot of the boot time with lots of details