** Changed in: linux
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1719795
Title:
Dell 7140 avarage power consumption in idle increased by 1.3-1.5
** Summary changed:
- Add support to NVIDIA GPU passthrough
+ Add support for NVIDIA GPU passthrough
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1800649
Title:
Add support for
Look at what this guy did:
https://forums.lenovo.com/t5/Lenovo-IdeaPad-1xx-3xx-5xx-7xx/Lenovo-Ideapad-330-15ARR-ryzen-5-bios-doesn-t-support-linux/m-p/4251437/highlight/true#M61640
to fix touchpad(not that easy if you havent compiled a kernel yet,not that
difficult either)
1)download any kernel
*** Bug 119614 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1699772
Title:
linux-image-4.13.0-12-generic,
You have been subscribed to a public bug:
[ 56.996976] [ cut here ]
[ 56.996978] Bad or missing usercopy whitelist? Kernel memory exposure
attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
[ 56.996985] WARNING: CPU: 3 PID: 2547 at
(In reply to simonmcquire from comment #432)
> But then realised I had not updated the amdgpu firmware...
Does that means that the issue was already resolved and it's just
distros being outdated? I haven't tried this solution yet but you're not
the only one who is saying that the problem can be
(In reply to Klaus Mueller from comment #427)
> (In reply to JerryD from comment #426)
> > I am on Ryzen 2500U Laptop, HP. I am using kernel 4.18.9-200.fc28.x86_64.
> >
> > The zenstates.py script fails when I try to disable C6. Oh well.
>
> Did you load msr kernel module before (modprobe msr)?
These settings directly go to firmware and this part of code is not touched
from a long time. Did you update BIOS recently?
Try to revert commits 6f92253024d9d947a4f454654840ce479e251376
and f1664eaacec31035450132c46ed2915fd2b2049a.
They should have been backported older kernels
I had this same bug in June 2018 and in the beginning of July 2018. It
seems to be solved for me by " Look in BIOS settings for "PSU Idle
Control" and set it to "Typical Current Idle" "
The bug was appearing about a few days (2-7) in low usage mode.
I was using openSUSE Leap 15.0 before this and
> "in_accel_sampling_frequency from 10 to 10", may be you mean
something.
Sorry, I mean 10 to 1.
> Then I think you will be fine.
Yes, events stopped, power consumption back to normal.
> Then enable 1 by 1 and see which device has issue.
magn_3d and accel_3d
> Then play with those parameters
Want to share this in case it helps anyone else. I stumbled across this
issue after putting together a new Ryzen 2200G HTPC with AsRock AB350
M-ITX mainboard a few weeks ago. Would encounter random freezes every
couple of hours.
After updating UEFI to latest version, updating kernel to latest
The root cause of the "freeze when idle" appears to be a fault in the
mechanism which wakes the CPU up once it has gone into the deepest of
deep sleeps.
Mr AMD has pointed the finger at PSUs which fail to maintain the correct
voltage when the current draw approaches 0A. Between the PSU and the
"in_accel_sampling_frequency from 10 to 10", may be you mean something.
You have two other devices also. First try this:
For all the devices
/sys/bus/iio/devices/iio:device*/buffer/enable = 1
make them 0.
echo 0 > /sys/bus/iio/devices/iio:device*/buffer/enable
Then I think you will be fine.
> These parameters should be set by user space based on the application
> requirement, kernel can't set.
Then why kernel version makes a difference? And how actually this bug
can be solved?
> I think geoclue is some service uses magnetometer.
I not sure how correct behaviour should look like,
These parameters should be set by user space based on the application
requirement, kernel can't set.
I think geoclue is some service uses magnetometer.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You are right, on Linux 4.9.0 where power consumption was low and there
was no interrupts coming from INT343A - monitor-sensor can't detect
orientation and can't get light sensor data.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
(In reply to Michael from comment #423)
> So, I'm running Ubuntu 18.04 stock kernel with
> - Typical Current Idle
> - disabling global c-states
> - idle=nomwait kernel parameter
>
> and have no freezes for 8 Days now - new record. So it looks like I can
> confirm what Nelson Castillo mentioned
@simonmcquire
Can you please clarify what this amdgpu firmware you are using is and what for?
Are you flashing the video card?
Are you flashing the motherboard?
Thanks in Advance
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
(In reply to JerryD from comment #426)
> I am on Ryzen 2500U Laptop, HP. I am using kernel 4.18.9-200.fc28.x86_64.
>
> The zenstates.py script fails when I try to disable C6. Oh well.
>
> I have kernel parameters: idle=nomwait processor.max_cstate=5
>
> I still get lockup. No BIOS settings
I am on Ryzen 2500U Laptop, HP. I am using kernel
4.18.9-200.fc28.x86_64.
The zenstates.py script fails when I try to disable C6. Oh well.
I have kernel parameters: idle=nomwait processor.max_cstate=5
I still get lockup. No BIOS settings available on this mavhine.
Feel pretty hopeless at the
Sure, I bought this one:
http://a.co/d/cZbYwot
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1269883
Title:
0b95:1790 [Asus N55SF] Bad performance of Asix Ethernet-to-USB device
on
Still an issue in 4.18.9... However, I have 2 different USB3 adapters
with the same chipset. One is the Plugable USB3-E1000 (which has the
problem within a second when running iperf). The other one is a cheap
Amazon Basics USB3 Gigabit Ethernet Adapter which runs perfectly fine.
Both use the same
*** This bug is a duplicate of bug 1366418 ***
https://bugs.launchpad.net/bugs/1366418
Many thanks !!
It works perfectly, smoothly and smoothly!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Matthieu, can you e-mail me a link to the Amazon branded adapter that
works? cin...@cinderblocks.biz I'd like to pick one up for testing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
(In reply to Zhang Rui from comment #265)
> Created attachment 278797 [details]
> revert patch on top of 4.19-rc4
>
> please confirm this revert patch works for you on top of 4.19-rc kernel.
> I will send it out after got your confirmation.
Hi Rui,
Any chance this will hit 4.19 rc before final
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201361.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Created attachment 278797
revert patch on top of 4.19-rc4
please confirm this revert patch works for you on top of 4.19-rc kernel.
I will send it out after got your confirmation.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=201359.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Interesting. I do have this device. The last I tested (on 4.17.17), it
reproduced the issue, albeit not immediately. I will have to give it
another try when I get back to my test machine with a newer kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which
(In reply to Zhang Rui from comment #265)
> please confirm this revert patch works for you on top of 4.19-rc kernel.
> I will send it out after got your confirmation.
It does! Also the CPU max frequency is now back to 2.4GHz after
unplug/replug cycle.
VANILLA 4.19-rc4
plugged:
bat ~ # cat
Created attachment 279003
iio devices list
Thank you for looking into this issue.
Names and status of sensor with enable iio sensor proxy is attached.
> Now measure power and see if you still have issue.
Issue is not reproducible with removed iio-sensor-proxy (for some reason
disabling
Ping? Is this still reproducible?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1733194
Title:
kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq
Status in Linux:
Expired
I don't think you need a patch. Enable iio-sensor-proxy again. You
probably want to change hysteresis. This will decide how much change in
sample data before data is sent to user. OR need to reduce sampling
frequency.
Most probably this is accel_3d, which in your case
please re-open if you have the data we asked for.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1733194
Title:
kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq
Status in
So, I'm running Ubuntu 18.04 stock kernel with
- Typical Current Idle
- disabling global c-states
- idle=nomwait kernel parameter
and have no freezes for 8 Days now - new record. So it looks like I can
confirm what Nelson Castillo mentioned in comment #419
This seems ok now. Now I need to
You can disable iio_sensor_proxy service and reboot. Then look at
value of /sys/bus/iio/devices/iio:device*/buffer/enable
They all should be 0. Also better to note the sensor name corresponding to each
iio:device*. There is an attribute called "name" under each iio:device*.
Now measure power
So what are the implications of using idle=nowait and why isn't it a
standard behaviour for all Ryzen CPU going forward?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085
Title:
(In reply to JerryD from comment #426)
> I am on Ryzen 2500U Laptop, HP. I am using kernel 4.18.9-200.fc28.x86_64.
>
> The zenstates.py script fails when I try to disable C6. Oh well.
Did you load msr kernel module before (modprobe msr)?
Do you have the possibility to slightly overclock? Isn't
I tried 0.10 in_accel_hysteresis, then tried 0.05 and 0.01.
I also tried to reduce in_accel_sampling_frequency from 10 to 10.
Unfortunately, all of this doesn't make noticeable difference.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Confirming the issue on Dell Vostro 5468 with Intel Bluetooth adapter
(8087:0a2a), OS Ubuntu 18.04.1, kernel version. 4.15.0-36-generic. Audio
output appears to clog and tear second after log line shows in dmesg.
This goes for 4-5 seconds, after which playback continues normally for
another ~10
Same here with rtl8723de 4.18.16 latest rtl_bt firmware.
Pairing fails with an Edifier r2000db speaker.
I'm not sure, but i think pairing with an android device worked.
On failure bluezctl says something like connect attempt failed.
--
You received this bug notification because you are a
This Bug seems to affect even basic HCI functionality:
"hcitool inq" is never returning in my case. dmesg gives me said error message.
I have tried two different USB-Bluetooth Dongles:
[ ] usb 2-2: New USB device found, idVendor=04b4, idProduct=f901, bcdDevice=
1.12
[ ] usb 2-2: New USB device
I am facing the same trouble.
I can't air with some devices.
My card is :
08:00.0 Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1]
(rev 73)
Subsystem: Intel Corporation Wireless-N 7260 [8086:4062]
Kernel driver in use: iwlwifi
--
You received this bug
dmesg
https://paste.pound-python.org/raw/Z0A2xHsgA3ePo8rmIL7L/
lspci -vvv
https://paste.pound-python.org/raw/9mPWBx1BJfar6yROQOVu/
lsmod
https://paste.pound-python.org/raw/TASuig0MdPwOmWiEUWeh/
sha256sum /lib/firmware/rtl_bt/rtl8723d_*
https://paste.pound-python.org/raw/XkFQ6c6f9HpqmUhCEJOn/
Same issue here with Fedora 28 and 29, using Gigabyte x470 Gaming 7
motherboard with an Intel Wifi and Bluetooth chipset.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1748565
Title:
sudo lsusb -vvv
https://paste.pound-python.org/raw/vfIi8iqFxDaI5Mofjruq/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1748565
Title:
Kernel regularly logs: Bluetooth: hci0: last event
(In reply to Y S Gupta from comment #8)
Same here. I used the commands from Szymon to find out what was going on and
got the Synaptics Touchpad, too.
The workaround by Y S Gupta works like a charm. Put it in a startup
script and everything is ok. THANK YOU!
--
You received this bug
Launchpad has imported 2 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=108554.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1800649
Title:
Add support to NVIDIA GPU passthrough
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1799718
Title:
Ubuntu 18.10 fr FAN always ON 5 400 rpm
Status in
ok, all's not wine and roses. When exiting X, it goes into the same
style lockup as used to happen on boot. Which includes crashing so hard
that often times (but not all the time) the BIOS can't find the boot
disk after the next power cycle.
At least the bug moving further back in the chain
(In reply to Alec Habig from comment #36)
> ok, all's not wine and roses. When exiting X, it goes into the same style
> lockup as used to happen on boot. Which includes crashing so hard that
> often times (but not all the time) the BIOS can't find the boot disk after
> the next power cycle.
>
>
So since last week, kernel-4.18.7-100.fc27.x86_64 came out on the Fedora
updates repo. Tried it just now in the process of looking at the next
batch of options differences... and it didn't crash! And all the other
drivers I need on this laptop are enabled (which wasn't the case with
your drm-tip
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
you (bountou), have you tried reset bios settings to defaults and/or
perform battery reset?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1776563
Title:
Acer Aspire A315
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
--- Comment From julian.wiedm...@de.ibm.com 2018-11-07 07:40 EDT---
Should be resolved by mainline commit e19e5be8b4ca ("s390/qeth: sanitize
strings in debug messages"). To cut down on the conflicts when applying against
18.04/master-next, I would suggest to also consider the following
I didn't use bluetooth on this machine before, so this may or may not be
relevant to update.
I also can't try a new kernel version.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802077
Verification successful on xenial-proposed.
Updated verification tags.
Steps
=
Setup 1) Enable xenial-proposed and install the iproute2 package:
---
$ echo 'deb http://archive.ubuntu.com/ubuntu xenial-proposed main restricted' |
sudo tee /etc/apt/sources.list.d/xenial-proposed.list
deb
@terryh-orcas,
if you are able to reproduce the problem relatively quickly and easily, then I
suggest testing different kernel versions, up to the latest upstream, to see if
and where it may be fixed with a newer i40e kernel driver. You can get
upstream kernel debs here:
I have attached the dsdt.dsl file.
** Attachment added: "dsdt.dsl"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802052/+attachment/5209975/+files/dsdt.dsl
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19
Spotted on Cosmic KVM as well.
** Summary changed:
- ubuntu_fan_smoke_test failed on 4.4/4.15 kvm & azure kernel
+ ubuntu_fan_smoke_test failed on 4.4/4.15/4.18 kvm & azure kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
So I think there is an issue regarding GDM and updated Nvidia
drivers...?
Well the issue with Nvidia settings is certainly releated to updated
Nvidia drivers
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in
A temporary workaround is to switch gdm to another display manager
Well there is another problem when you update the drivers on Intel you
can't open the nvidia settings, just save the old nvidia-settings and
libs from /use/lib
On Ubuntu 18.04 is present only if you update the drivers from the
** Description changed:
Backstory: The discrete touchpad enable/disable switch does not work on
Ubuntu but works perfectly on windows. This is probably an issue of the
msi_wmi drivers, so I tried to find a solution.
Followed the instructions here -
More infos. I installed the notebook from scratch with a 16.04.2 image
and update to latest 16.04 packages which installed 4.15.0-38 kernel.
The laptop has the correct behavior, without entering settings I can
switch/duplicate displays with the fn key.
So original problem seems not related to
This bug affects me too.
Ubuntu 18.10.
GeForce GTX 960M
Driver Version: 410.73
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1800465
Title:
Vulkan error when
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19
Skip "rtnetlink: fix rtnl_fdb_dump() for ndmsg header" because it was
already applied for bug #1796748.
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU
Also checked removing of tokens:
~# ip token set :: dev eth0
~# ip token list
token :: dev eth0
This works in Xenial and Stretch without any errors.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching
@Thomas: sorry, took me some days to find the time and check with
freshly installed versions:
16.04.5 LTS (Xenial Xerus):
~#ip token list
token :: dev eth0
~# ip token set ::12 dev eth0
~# ip token list
token ::12 dev eth0
~# ip token set ::ab dev eth0
~# ip token list
token ::ab dev eth0
The arches don't have HAVE_ARCH_SECCOMP_FILTER enabled as this has not
been implemented, so seccomp filtering does not exist. I'll fix stress-
ng to handle this corner case without an error.
** Changed in: stress-ng
Status: New => In Progress
** Changed in: stress-ng
Importance:
The result is a bit different on PowerPC and ARM64:
<<>>
tag=openat03 stime=1541585769
cmdline="openat03"
contacts=""
analysis=exit
<<>>
incrementing stop
openat031 TBROK : openat03.c:59: openat() failed: errno=EINVAL(22):
Invalid argument
openat032 TBROK : openat03.c:59: Remaining
I talked to the security team. There is no reason to check for
CONFIG_RETPOLINE != 'y' in Precise. CONFIG_RETPOLINE should always be
set to 'y', even if the toolchain doesn't support it. There are minimal
mitigations that we get even without toolchain support but for that we
need CONFIG_RETPOLINE
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Cosmic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Cosmic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
@Andrew: sorry, but your GPU is supported only by the 340 legacy driver,
and we do not support hybrid graphics with that driver.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
** Description changed:
No bluetooth device is found.
`rfkill list` shows a wifi device only, no bluetooth.
# rfkill list
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1802076
and then change the status of the bug to 'Confirmed'.
If, due to the
CONFIG_SECCOMP_FILTER does not appear to be configured for the ARM64
system, I presume this is the same for the Power8 box too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1801856
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802077
Title:
Bluetooth is not working on
Public bug reported:
No bluetooth device is found.
`rfkill list` shows a wifi device only, no bluetooth.
# rfkill list
0: ideapad_wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
ProblemType:
Public bug reported:
My Laptop is an ASUS TUF FX504 Series model. I installed ubuntu 18.04.1
on it but my trackpad is not detected. Attaching an external mouse works
fine.
Trackpad is easily identified by Windows 10.
`cat /proc/bus/input/devices | grep Name` shows the output:
```
N:
Here is the output of `dmesg > ~/dmesg`
** Attachment added: "`dmesg > ~/dmesg` output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802076/+attachment/5209937/+files/dmesg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
The failure in Trusty ARM64 is a bit different:
With 3.13.0-161-generic
request_key03.c:115: BROK: unexpected error adding key of type 'trusted': ENOMEM
With 3.13.0-162-generic
request_key03.c:70: BROK: failed to join new session keyring: EDQUOT
--
You received this bug notification because you
The mainline kernel indeed seems to fix the issue: Not a single failed
suspend/resume cycle since using 4.19.1.
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
It looks like there is a nbd related failure in the test report.
I will split the kernel_security one first to nail them down one by one:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802069
--
You received this bug notification because you are a member of Kernel
Packages, which is
Thank you Daniel,
I loaded Ubuntu again and now everything looks fine. Hopefully it will
stay this way.
With thanks to you
Spreebogendd
Am 07.11.18 um 02:47 schrieb Daniel van Vugt:
> Also, please run these commands and send the output:
>
>sudo apt install edid-decode
>for e in
201 - 289 of 289 matches
Mail list logo
