14
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 Dec 2023
14 points (93.8% liked)
linux4noobs
1356 readers
1 users here now
linux4noobs
Noob Friendly, Expert Enabling
Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.
Seeking Support?
- Mention your Linux distro and relevant system details.
- Describe what you've tried so far.
- Share your solution even if you found it yourself.
- Do not delete your post. This allows other people to see possible solutions if they have a similar problem.
- Properly format any scripts, code, logs, or error messages.
- Be mindful to omit any sensitive information such as usernames, passwords, IP addresses, etc.
Community Rules
- Keep discussions respectful and amiable. This community is a space where individuals may freely inquire, exchange thoughts, express viewpoints, and extend help without encountering belittlement. We were all a noob at one point. Differing opinions and ideas is a normal part of discourse, but it must remain civil. Offenders will be warned and/or removed.
- Posts must be Linux oriented
- Spam or affiliate links will not be tolerated.
founded 1 year ago
MODERATORS
Apologies for the late reply. I followed the instructions on the Debian page and now i keep seeing a popup with: conflicting nouveau kernel module loaded. It advices to reboot, but that doesn't work. Apparently, i had the dreaded nouveau already loaded on my window install. I' m waiting for help from someone who will visit tomorrow, because i seem to be suffering from a severe case of covid brain fog and am currently to stupid to mess with it...very annoying. Also, because i can't install programs now, also apparently because of this conflicting driver.
I don't have secure boot enabled and am using Wayland. It doesn't work in the sense that reboot doesn't solve the conflict. For instance, when trying to install software through cli, i get a: dpkg was interrupted, you must manually run sudo dpkg --configure -a to correct the problem. When i do that, the same popup about the conflict pops up. (And installing graphically trough Discover gives a 'cannot obtain lock' error. Thank you for the link, but that is the link i mentioned - and followed - in my post :-) Covid; yes, it was my first time and every bit as awful as i heard from people