Please test with PulseAudio disabled ( pulseaudio -k ) and see if video still stutters.
Killing and later restarting PA results in temporary resolution to the stuttering issue.
( Using Bluetooth headset, iMac 2013 27", GT755M GPU, Ubuntu 19.10 and 20.04 )
EDIT: On ubuntu, try also remove the speech-dispatcher-audio-plugins package which has been indicated ...
To get the processor info you can use :
sudo dmidecode -t 4 |grep Version
lscpu |grep "Model name:"
The update can be done by installing firmwares and microcodes from buster-backports.
See Getting microcode updates sooner using Debian backports , how to check the microcode version and updates.
Intel: How to update/install microcode downloaded from ...
I believe the 'Host Bridge' that lspci is referring to is the PCI host bridge that connects the CPU to the PCI bus. I have a 3rd generation Core i5 and my host bridge description says:
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
I think what it means is that the host bridge is designed for use with ...
I had the same issue! I guess the problem is that Mint would save the display setting every time you turn off the computer. If there is just one time you turn off the computer with the second monitor connected and then boot without the second monitor, Mint would get confused and lose track of your display setting thereafter.
Have you tried to log out and ...
The main point is to save kernel RAM (which is not paged). Rather than building a kernel with everything in it, the kernel is built with some important drivers in it, and the rest available as modules. At boot time the kernel probes the various buses it finds, like pcie, and tries to find modules which claim to be drivers for the various things found. These ...
It is not possible to install a Windows XP device driver on linux.
You can start here (https://help.ubuntu.com/community/Webcam)
to find support for your webcam.
Or search for your webcam model here (https://askubuntu.com/search?q=webcam)
You have the kernel headers but the run file also needs the development header files and binaries. Install them and run the file again:
apt-get install libc-dev libc6-dev gcc g++
You may already have the last two which are the binaries but I'm including them in case you don't.
I was experiencing a lot of tearing with NVidia in Arch. I tried the suggestion in this answer to the question you linked. Completely eliminated it for me.
This is with the latest proprietary NVidia driver. I haven't seen any noticeable tearing since in both Mate (marco) and LXDE (openbox).
(if you want more details about my system/setup, let me know)
I found a solution to my problem somewhere on askfedora: after copying nvidia.conf from /usr/share/X11/xorg.conf.d to /etc/X11/xorg.conf.d (as per the RPM fusion howto) one should edit it to add Option "PrimaryGPU" "yes" in the "OutputClass" section.
As a result, /etc/X11/xorg.conf.d/nvidia.conf has:
I used crontab to schedule these commands at reboot.
To do this I opened file crontab as superuser in folder etc:
sudo gedit /etc/crontab
Then I inserted a line at the end, so that the commands are executed as root (applied to every user):
@reboot root modprobe -e psmouse && modprobe psmouse proto=imps
I hope it helps!
I found the answer.Using instruction here,I found that my pci uses "rt2800pci".I unloaded the module using the following command :
modprobe -r rt2800pci
It worked well and the usb wifi adapter started working,but this solution works only for one session once the computer reboots you will have to unload the module again, you can blacklist the module if you ...
I guess that ScanJet 2400c backend doesn't work with ScanJet 2400. luckily, I downloaded the driver mentioned in elcot.in before. you can download it from there:
by the way I thought adding the following link is better
A generic way to try to fix things is to increase the mac80211 kernel module parameters having to do with disconnections. From modinfo -p mac80211:
max_nullfunc_tries:Maximum nullfunc tx tries before disconnecting (reason 4). (int)
max_probe_tries:Maximum probe tries before disconnecting (reason 4). (int)
beacon_loss_count:Number of beacon intervals ...
Well... I've tried many things:
Running java with extra parameters to see if the application would run correctly
Tried to update the BIOS of the device (but it is too old and has no updates)
Looked for a way to disable the ohci driver of being taken, achieved it by using udev but the device won't be recognized or would use another driver. (There would be ...
What I specifically want know here is irrespective of the underlying hardwares it is on how Linux kernel manages to work on all different pcs
Before anything else, the kernel can run on any PC as long it's compiled for that specific architecture. With your general purpose computers, the architecture tends to be the same (x86_64/amd64) but this changes when ...
My UiD 121 error was not solved by any solution I found on the web. I assumed it was due to an update, but actually it turned out to just result from a full hard drive.
open a terminal as root
then remove all the files in trash
rm -r *
A simple reboot after this worked fine. May ...
Some clocks are based on others; for example in at91:
The Sama5d2 SoC has two audio PLLs (PMC and PAD) that shares the same parent
(FRAC). FRAC can output between 620 and 700MHz and only multiply the rate of
its own parent. PMC and PAD can then divide the FRAC rate to best match the
In such setups, knowing the topology is important, ...
First of all, the reason for this behaviour seems to be USB specific. Kernel.org (here) states the following:
When USB 1.1 devices plug into USB 2.0 hubs, they interact with the
EHCI controller through a “Transaction Translator” (TT) in the hub,
which turns low or full speed transactions into high speed “split
transactions” that don’t waste transfer ...
You can try to locate the relevant driver in the earliest kernel that supported it, and graft that on your museum piece. But I'd wagger it will be a huge undertaking, the Linux folks feel absolutely no compunction in redoing the kernel-internal interfaces. Current kernel is 5.5.4, 3.45 is ancient (and is not one of the long term support versions either, ...