Closed vladkinoman closed 2 years ago
A possible solution to the x86/cpu: VMX (outside TXT) disabled by BIOS
problem: link. In short, go to your BIOS settings and enable the virtualization technology.
Acording to Reddit these are the benefits of virtualization:
You would need to be employing AMD's enterprise-level virtualization encryption to be concerned with potential door opening for Spectre. It really doesn't make sense for it to be disabled by default on desktop systems - it just makes people think that AMD can't do it considering every other AMD and Intel system has always left it enabled by default.
It has me wondering at this point if there were just early issues with virtualization on the AM4 platform and that caused everyone to disable it by default and they never bothered turning it back on.
Maybe, it's the type of thing people might be hesitant to change if they don't know the reasoning behind the original change.
Jan 09 16:13:26 pop-os kernel: kfd kfd: OLAND not supported in kfd
Hmm :thinking: This is a very difficult problem because it is unclear why it is being displayed in the log file. What is OLAND? OLAND is a chip variant of my GPU according to this. I don't know what is kfd, but I know that it has something to do with ROCm - Open Source Platform for HPC and Ultrascale GPU Computing.
ROCm is focused on using AMD GPUs to accelerate computational tasks such as machine learning, engineering workloads, and scientific computing. In order to focus development efforts on these domains of interest, ROCm supports a targeted set of hardware configurations which are detailed on that GitHub page.
ROCm is a collection of software ranging from drivers and runtimes to libraries and developer tools. Some of this software may work with more GPUs than the "officially supported" list mentioned above, though AMD does not make any official claims of support for these devices on the ROCm software platform.
Unfortunately ROCm does not support AMD GPUs that use OLAND chips.
By the way, ROCmSupport says that Pop!_OS is not officially supported with ROCm. There is also an interesting tip in the same discussion:
The device /dev/kfd need video or render group, using ls -l /dev/kfd to check the device group, and using groups to check the current login user group, if not matched, do sudo usermod -a -G video $LOGNAME
could this launch be failing because the owner of the file /dev/kfd is root and not the actual user on OS.
Using usermod I have added myself to the video group and even root. Didn't help.
My conclusion is that the video card just doesn't support the ROCm technology which is supported in the new kernel version (probably).
Jan 09 16:14:31 pop-os gdm-password][1328]: gkr-pam: unable to locate daemon control file
Looks like it hasn't been fixed. People are still complaining about the problem here. Nevertheless, they recommend adding
XDG_RUNTIME_DIR=/run/user/$UID
to /etc/profile
. However, it didn't help me.
Also, this post recommends setting XDG_BIN_HOME in .profile.
According to this thread (and information on the discussion of the issue):
There is no issue. Gdm-password checks whether a file is set via an environment variable that is under normal circumstances in a systemd context not available at the time it first does the check. It will note that, and retry later when the session is there and PAM/systemd has set up the environments for your user. It's an informal "error" most likely only relevant for systems that do not use systemd/logind, are embedded and single-user and start to actively fail when the file that is being checked for here is not present.
That's probably true:
vladkinoman@pop-os:~$ journalctl | grep 'gkr-pam'
...
Jan 09 23:07:05 pop-os gdm-password][1342]: gkr-pam: unable to locate daemon control file
Jan 09 23:07:05 pop-os gdm-password][1342]: gkr-pam: stashed password to try later in open session
Jan 09 23:07:06 pop-os gdm-password][1342]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
I think :thinking:
Jan 09 16:14:46 pop-os systemd[1333]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 416 and the job result is failed.
This is a very fresh issue. I haven't found a solution, but there are plenty of threads to keep track of: ArchLinux forum, AskUbuntu, Fedora - same question as AskUbuntu, Fedora - Failed to start Application launched by gnome-session-binary.
So, I've only fixed the virtualization issue:
vladkinoman@pop-os:~$ journalctl -xb -p err
-- Logs begin at Fri 2021-01-08 15:23:33 EET, end at Sat 2021-01-09 23:21:38 EET. --
Jan 09 23:06:05 pop-os kernel: kfd kfd: OLAND not supported in kfd
Jan 09 23:07:05 pop-os gdm-password][1342]: gkr-pam: unable to locate daemon control file
Jan 09 23:07:16 pop-os systemd[1348]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 312 and the job result is failed.
Jan 09 23:07:23 pop-os systemd[1348]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit UNIT has finished with a failure.
░░
░░ The job identifier is 419 and the job result is failed.
I'm getting strange new errors every 10 minutes or so:
Jan 10 19:34:04 pop-os kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
Jan 10 19:34:04 pop-os kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 10 19:34:04 pop-os kernel: Buffer I/O error on dev sr0, logical block 0, async page read
Jan 10 19:34:04 pop-os kernel: blk_update_request: I/O error, dev sr0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 10 19:34:04 pop-os kernel: Buffer I/O error on dev sr0, logical block 1, async page read
Jan 10 19:34:04 pop-os kernel: blk_update_request: I/O error, dev sr0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 10 19:34:04 pop-os kernel: Buffer I/O error on dev sr0, logical block 2, async page read
Jan 10 19:34:04 pop-os kernel: blk_update_request: I/O error, dev sr0, sector 3 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 10 19:34:04 pop-os kernel: Buffer I/O error on dev sr0, logical block 3, async page read
Jan 10 19:34:04 pop-os kernel: blk_update_request: I/O error, dev sr0, sector 4 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 10 19:34:04 pop-os kernel: Buffer I/O error on dev sr0, logical block 4, async page read
Jan 10 19:34:04 pop-os kernel: blk_update_request: I/O error, dev sr0, sector 5 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 10 19:34:04 pop-os kernel: Buffer I/O error on dev sr0, logical block 5, async page read
Jan 10 19:34:04 pop-os kernel: blk_update_request: I/O error, dev sr0, sector 6 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 10 19:34:04 pop-os kernel: Buffer I/O error on dev sr0, logical block 6, async page read
Jan 10 19:34:04 pop-os kernel: blk_update_request: I/O error, dev sr0, sector 7 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 10 19:34:04 pop-os kernel: Buffer I/O error on dev sr0, logical block 7, async page read
I work with Lutris at times like this.
Plus, I think there is an issue with the Wi-Fi driver. I lose connection every two hours. To fix such an error, you have to turn the Wi-Fi button off and on on the laptop. There was something similar on Linux Mint. However, it disappeared either when I switched to Cinnamon or after some update.
I figured out what the problem was. Solved it here.
Distrohopped to Fedora 35.
Output from
inxi
:What I solved already:
adm
group. Described in this discussion.New issues:
Plus, I think there is an issue with the Wi-Fi driver. I lose connection every two hours. To fix such an error, you have to turn the Wi-Fi button off and on on the laptop. There was something similar on Linux Mint. However, it disappeared either when I switched to Cinnamon or after some update.And when I launch one of the The West Wing episodes using MPV, I get the following error:
A possible solution to this problem could be found here. However, I think it is a problem with the files themselves.