Re: Vulkan with Radeon RX 5700 XT

[idiotei...@gmail.com]

Le 10/07/2021 à 17:41, The Wanderer a écrit :

On 2021-07-10 at 07:43, tv.deb...@googlemail.com wrote:


Le 09/07/2021 à 23:44, The Wanderer a écrit :


(Warning, this is fairly long, and the situation involved includes
a fair number of potentially-moving pieces.)


I've recently built a new computer, installed Debian, configured it
to largely match my previous setup, and migrated my data across.

Now, I'm trying to take advantage of one of the hardware
improvements over the system I migrated away from: a newer,
better-performing GPU. In particular, I want to run software which
makes use of the Vulkan API for improved graphics performance.


Hi, Debian unstable with bits of experimental here (because of the
freeze I pull some newer packages from experimental). Same graphic
card (5700XT), mesa drivers (21.1.4 at this precise moment, from
experimental). Here vulkan works afaik.


For comparison, I have mesa-vulkan-drivers 20.3.4-1, from testing.


vulkaninfo reports my card as:
"Group 1:
   Properties:
 physicalDevices: count = 1
 AMD RADV NAVI10 (ACO) (ID: 0)
 subsetAllocation = 0
   Present Capabilities:
 AMD RADV NAVI10 (ACO) (ID: 0):
 Can present images from the following devices: count = 1
 AMD RADV NAVI10 (ACO) (ID: 0)
"


That's excellent news; it means that, at least in principle, this can
work in (relatively-)clean Debian as currently constituted. (It also
confirms that RADV is the relevant thing here; my reading wasn't
conclusive as to whether or not that was specifically something for
older card models.)

Can you indicate exactly which Vulkan-related packages you're running
from experimental? For that matter, a list of Vulkan-related packages
and package versions from unstable too would probably be appropriate,
since I track testing and am *highly* hesitant to upgrade against sid
wholesale.
There you go, some packages are at the same version in Testing and 
Unstable, so you will see them in both.


"aptitude search '?narrow(?installed,?archive(experimental))' | egrep 
'(mesa|vulkan)'


i A libegl-mesa0 - free implementation of the EGL API -- Mesa vendor library
i  libegl-mesa0:i386 - free implementation of the EGL API -- Mesa vendor 
library

i  libegl1-mesa:i386 - transitional dummy package
i A libgl1-mesa-dri - free implementation of the OpenGL API -- DRI modules
i A libgl1-mesa-dri:i386 - free implementation of the OpenGL API -- DRI 
modules

i A libgl1-mesa-glx - transitional dummy package
i A libglapi-mesa - free implementation of the GL API -- shared library
i A libglapi-mesa:i386 - free implementation of the GL API -- shared library
i A libglx-mesa0 - free implementation of the OpenGL API -- GLX vendor 
library
i A libglx-mesa0:i386 - free implementation of the OpenGL API -- GLX 
vendor library

i A libosmesa6 - Mesa Off-screen rendering extension
i A libosmesa6:i386 - Mesa Off-screen rendering extension
i  mesa-opencl-icd - free implementation of the OpenCL API -- ICD runtime
i A mesa-va-drivers - Mesa VA-API video acceleration drivers
i A mesa-vdpau-drivers - Mesa VDPAU video acceleration drivers
i  mesa-vulkan-drivers - Mesa Vulkan graphics drivers
i  mesa-vulkan-drivers:i386 - Mesa Vulkan graphics drivers

aptitude search '?narrow(?installed,?archive(unstable))' | egrep 
'(mesa|vulkan)'

i A libglu1-mesa - Mesa OpenGL utility library (GLU)
i  libglu1-mesa:i386 - Mesa OpenGL utility library (GLU)
i A libglu1-mesa-dev - Mesa OpenGL utility library -- development files
i A libvulkan-dev - Vulkan loader library -- development files
i A libvulkan1 - Vulkan loader library
i A libvulkan1:i386 - Vulkan loader library
i A mesa-utils - Miscellaneous Mesa GL utilities
i  mesa-utils-extra - Miscellaneous Mesa utilies (opengles, egl)
i  vulkan-tools - Miscellaneous Vulkan utilities

aptitude search '?narrow(?installed,?archive(testing))' | egrep 
'(mesa|vulkan)'

i A libglu1-mesa - Mesa OpenGL utility library (GLU)
i  libglu1-mesa:i386 - Mesa OpenGL utility library (GLU)
i A libglu1-mesa-dev - Mesa OpenGL utility library -- development files
i A libvulkan-dev - Vulkan loader library -- development files
i A libvulkan1 - Vulkan loader library
i A libvulkan1:i386 - Vulkan loader library
i A mesa-utils - Miscellaneous Mesa GL utilities
i  mesa-utils-extra - Miscellaneous Mesa utilies (opengles, egl)
i  vulkan-tools - Miscellaneous Vulkan utilities

I also run llvm-12 from unstable, but really this gpu has been running 
fine almost from the start (more than two years ago), so I don't think 
testing packages are outdated, baring a massive regression or bug it 
should work.




(There was a time when I tracked sid. That computer wound up in an
inconsistent state, to the point that it wasn't worth fixing and would
have needed a full reinstall and possibly a few other things into the
bargain. I lived with it until I could build a replacement, then
migrated away to track testing and have never considered looking back.)
I have read such horror stories, 

Re: Wifi not working in Lenovo laptop/Ideapad/Atheros QCA9377

[idiotei...@gmail.com]

Putting thread back on list, this was sent to me directly. Answer is at 
bottom.


On 31/05/2019 19:07, senthil kosapeta wrote:


Hi,

These are the logs that i got, it says "firmware loading failed"



*May 31 12:58:48 debian kernel: [0.048770] Spectre V2 : Enabling
Restricted Speculation for firmware calls*
*May 31 12:58:48 debian kernel: [7.671866] i915 :00:02.0: Direct
firmware load for i915/kbl_dmc_ver1_01.bin failed with error -2May 31
12:58:48 debian kernel: [7.671873] i915 :00:02.0: Failed to load
DMC firmware [https://01.org/linuxgraphics/intel-linux-graphics-firmwares
], disabling
runtime power management.May 31 12:58:48 debian kernel: [7.677946]
[drm] GuC firmware load skippedMay 31 12:58:48 debian kernel: [
 8.226104] ath10k_pci :03:00.0: Direct firmware load for
ath10k/pre-cal-pci-:03:00.0.bin failed with error -2May 31 12:58:48
debian kernel: [8.226118] ath10k_pci :03:00.0: Direct firmware load
for ath10k/cal-pci-:03:00.0.bin failed with error -2May 31 12:58:48
debian kernel: [8.226129] ath10k_pci :03:00.0: Direct firmware load
for ath10k/QCA9377/hw1.0/firmware-5.bin failed with error -2May 31 12:58:48
debian kernel: [8.226143] ath10k_pci :03:00.0: Direct firmware load
for ath10k/QCA9377/hw1.0/firmware-4.bin failed with error -2May 31 12:58:48
debian kernel: [8.226156] ath10k_pci :03:00.0: Direct firmware load
for ath10k/QCA9377/hw1.0/firmware-3.bin failed with error -2May 31 12:58:48
debian kernel: [8.226168] ath10k_pci :03:00.0: Direct firmware load
for ath10k/QCA9377/hw1.0/firmware-2.bin failed with error -2May 31 12:58:50
debian NetworkManager[559]:   [1559287730.5479]
manager[0x5578b9b35040]: monitoring kernel firmware directory
'/lib/firmware'.May 31 12:58:50 debian kernel: [   16.179299] r8169
:02:00.0: Direct firmware load for rtl_nic/rtl8168g-3.fw failed with
error -2May 31 12:58:50 debian kernel: [   16.179307] r8169 :02:00.0
enp2s0: unable to load firmware patch rtl_nic/rtl8168g-3.fw (-2)May 31
14:37:49 debian kernel: [ 5323.527328] [drm] GuC firmware load skippedMay
31 18:44:53 debian kernel: [11230.812795] [drm] GuC firmware load skipped*

On Fri, May 31, 2019 at 4:46 PM tv.deb...@googlemail.com <
tv.deb...@googlemail.com> wrote:


On 31/05/2019 15:46, senthil kosapeta wrote:

Dear Debians,

I have purchased Lenovo laptop around 6 months back. (Lenovo ideapad)
I had installed ubuntu earlier and Wifi used to work fine.
Somehow it got crashed a month back.

I have decided to switch over to debian 9.9 and installed it.
Internet via Ethernet port is working. But wifi is not working and not
showing available wireless networks.
I searched/googled certain topic related to Debian wifi and tried
installing firmware-atheros earlier.
It did not work. When i tried restart, shutdown is stuck.
If i force shutdown and restart, It will be stuck again.
When i tried to do recover mode, msg displays that
"ath10k_pci ** failed recieve control reponse completion, polling "

Please let me know how to proceed.

  Thanks
Senthil



Hi, can you check for firmware loading information in your logs ?

"grep firmware /var/log/messages" or "journalctl -b" and look for info
related to the wifi chip.

Given the "shutdown stuck" issue I would try disabling interrupts and
see if it solves the problem, "modinfo" says ath10k_pci accepts three
irq options:

"parm:   irq_mode:0: auto, 1: legacy, 2: msi"

Maybe try "legacy" mode first, that may be what Ubuntu is doing as a
default. You will need elevated privileges to run the next commands
("sudo command" or "su -" and then type commands).

First two commands unload the driver module:


modprobe -r ath10k_pci
modprobe -r ath10k_core

Then reload it with proper option:

modprobe -v ath10k_core
modprobe -v ath10k_pci irq_mode=1

If it solves the problem you can make the change permanent.

Hope it helps.




The error message is very generic (ignore the message regarding the 
graphic chip, it's unrelated and mostly harmless).


First look into the firmware directory to make sure you do have the 
needed firmware binary:


ls -l /lib/firmware/ath10k/QCA9377/hw1.0/

You should see a "firmware-6.bin" file in the output.

Then try the commands I suggested before in a terminal window, you need 
to do this as root, either by using "sudo" in front of the commands or 
by doing "su -" and ater providing the root password type the actual 
commands one line at a time:


modprobe -r ath10k_pci
modprobe -r ath10k_core

modprobe -v ath10k_core
modprobe -v ath10k_pci irq_mode=1

and report back to the list the outcome.

Re: understanding kernel compilation and

[idiotei...@gmail.com]

On 23/10/2014 14:22, Muhammad Yousuf Khan wrote:

Actually the problem is i am trying to install KVM guest windows 7 64 bit.
during the installation everything went well. but when guest start for the
first time my KVM guest shows "booting from harddirve..." and struck.
my "/var/log/libvirt/qemu/(myguestfile) show  this


KVM: entry failed, hardware error 0x8021



If you're running a guest on an Intel machine without unrestricted mode



support, the failure can be most likely due to the guest entering an

invalid


state for Intel VT. For example, the guest maybe running in big real mode



which is not supported on less recent Intel processors.:



my kernel is 3.2.x which comes with Wheezy as default kernel.i found this
error in many places that this is a kernel bug and shall be fix if i patch
or update the kernel.


So my KVM host is not a production server so i thought it is a best time to
play with the kernal patching because i am working on linux for years but
never perform such task i always rely on default/stable debian repository
but this is a first time i am doing some thing out of the box for fixing
and learning purpose both


so that's the whole story. if you have any other suggestion please share.


Thanks,


I don't know about this specific error, but if you want to try a newer 
kernel for Wheezy may I suggest starting with the Debian backport [1] 
kernel ? It's a lot easier and less error prone, plus you won't have to 
recompile the kernel every time a new kernel comes out to get the fixes.


[1] http://backports.debian.org/

http://backports.debian.org/Instructions/


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Archive: https://lists.debian.org/5448ecaf.1060...@gmail.com

Re: VLC froze twice: so reboot

[idiotei...@gmail.com]

02/03/2012 14:37, Sian Mountbatten wrote:
> On 01/03/12 17:50, tv.deb...@googlemail.com wrote:
>> 01/03/2012 18:01, Sian Mountbatten wrote:
>>> Hello All!
>>>
>>> I started to watch a DVD last night with VLC when the screen froze.
>>> Nothing would work, neither the mouse nor the keyboard. I did a H/W
>>> reset and rebooted the OS and VLC. I set the film to close to where
>>> it froze and went on watching. A few minutes later, the computer froze
>>> again.
>>>
>>> This time, after I had done the H/W reset and rebooted the OS, I started
>>> using Kaffeine. No more problems. Then, this morning, I watched another
>>> DVD using Kaffeine and again no problems.
>>>
>>> The version of VLC was 2.0.0 with KDE 4.7.2 and kernel
>>> 3.2-7.towo.2-siduction-686 #1 SMP PREEMPT
>>> I am using the siduction distribution which is based on Debian unstable.
> 
>> Hi, what is the video driver in use (i.e. nvidia, fglrx, radeon,
>> nouveau, intel) ?
> Nvidia, AFAIK.
> 
>> Did you try to launch vlc from the command line with "-v" option:
>>
>> vlc -v /path/to/video
>>
>> to see if it prints any error ?
> No, I did not.
> 
>> I had a freeze yesterday while using vlc, but it turned out to be a more
>> general video driver bug.
> I shall try Kaffeine next time I want to watch a DVD.
> -- 
> Sian Mountbatten
> Algol 68 specialist
> 
> 


Latest Nvidia binary driver (295.20) isn't exactly a good brew, several
bug reports are appearing on different forums, NVidia site and Debian
bug tracker [1]. It seems to be good at locking/crashing X, or even
locking the system entirely. The most advanced investigation I read
mentioned crashes when some processes fork. Another reminder of the risk
associating with running closed-source drivers.

[1] #661253 (link to other reports in posts)


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f50e271.7070...@gmail.com