Package: linux-cpupower
Version: 6.10.11-1
Followup-For: Bug #894906
X-Debbugs-Cc: pitsior...@outlook.com
Can I add that this also works on my rpi3b running debian 11 arm64? The regular
debian distro, from the images of raspi.debian.net, not the fake "64bit on arm"
of raspbian.
-- System Informa
Package: linux-cpupower
Version: 6.9.10-1
Followup-For: Bug #894906
X-Debbugs-Cc: pitsior...@outlook.com, invernom...@paranoici.org
First and foremost, no need to worry about delayed replies. I do not check the
bug report every day too... and I may have done the cc wrong now.
Second, I can also v
Package: linux-cpupower
Version: 6.9.9-1
Followup-For: Bug #894906
X-Debbugs-Cc: pitsior...@outlook.com
Sunday report... on Monday afternoon because I forgot about it. Like with the
previous change, adding "After=remote-fs.target" did not change much. It still
fails like half the times, like it do
Package: linux-cpupower
Version: 6.9.9-1
Followup-For: Bug #894906
X-Debbugs-Cc: pitsior...@outlook.com
First failed start after adding "After=systemd-modules-load.service". If it
happens again today, I will not report it, but I will report how many times it
failed in total until tomorrow.
Jul 20
Package: linux-cpupower
Version: 6.9.9-1
Followup-For: Bug #894906
X-Debbugs-Cc: pitsior...@outlook.com
As you said, I used to manually run the command when the system had reached the
desktop. Here is a full output in case it helps.
$ sudo cpupower frequency-set -g powersave
Setting cpu: 0
Settin
Package: linux-cpupower
Version: 6.9.8-1
Followup-For: Bug #894906
X-Debbugs-Cc: pitsior...@outlook.com
Hello everyone and thank you for your great work. I am a former user of the
obsolete cpufrequtils and of the unmaintained (by debian) cpupower-gui. I was
using those tools until 2021 to set my g
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@outlook.com
And it just happened again, on the very first boot of the day, as if nothing
has changed since May. I was right for not upgrading past 5.10.28 all those
months.
-- System Information:
Debian Release: bookworm/sid
APT
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
One thing I noticed this weekend.
Time it took for 5.10.38/40 to reach testing from unstable: 7 days, despite
this awful bug here.
Time it took for 5.10.46 to reach testing from unstable: 20+ days and still
counting.
Pleas
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
There are 2 words that can completely justify my "appaling lack of respect for
debian developers": hardware failure. And it happened not once, but twice.
Plus, the support I received from here is non existant in every troub
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
I noticed that 5.10.46 reached unstable yesterday. If it was not for this
issue, I would have already upgraded, like I udually do when a kernel upgrade
comes out.
However, this time I had to check the config file for that -
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
Finally, a sane reply that does not blame nvidia's driver.
I have written above that something must have changed, at least regarding intel
hw, because I was missing the coretemp readings on my conky. However, from the
page
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
One more week passed with no issues. That's how things are when a kernel works
as it should and the gpu driver is flawless. Stability that matches the one of
a really stable distro or the one of windows 7.
As I expected, t
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
About the logs. Did anyone of you reply to my question "where can I find those
logs?" and I missed it? All I have found, again BY MYSELF, is this file here
that when I run cat on it, gibberish shows up in the terminal. I ca
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
To no surprise, the severity was lowered again. Without a single suggestion or
reason, again.
Imho, that is the usual incompetence most devs here show, so I am not
surprised. It's a real shame however for a distro this size
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
Finally a sane reply by someone!
First of all, I do not think that my issue is related to sleep at all. I
mentioned all that in the first post just in case. I know sleep is problematic
in linux, thus I never use it. I also
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
Control: severity -1 critical
Now that I have your attention, because raising the severity is the only way to
get an answer here, let me begin.
I noticed that this mess of a kernel reached testing today. As it seems, its
o
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
I came accross these 2 threads on r/debian and I am now thinking that my
problem too may not be related to debian packaging/patching/configuration but
to some upstream flaw(s) of 5.10.
The guy in the second thread has done
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
How would YOU feel if a system upgrade destroyed an (old yet) perfectly working
piece of important hardware? What if it destroyed another piece of similar
hardware a few days later?
How would you feel if all those days you
Control: severity -1 critical
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
I borrowed an old pc from a friend to test those 2 gpus. NONE of them reached
the post, which means they are damaged now. Moreover, when the ati was
connected, the system was beeping as if it had no vga on.
Thank you debian
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
One thing I forgot last time. The ati card was fucked up AFTER it ran on
5.10.40 for a couple of boots. I installed it because I wanted to check if it
works any better there (scrolling is laggy on all browsers).
Do you thin
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
And the same thing happened again today, with the ati card this time! I logged
in via ssh and, like with nvidia and nouveaum radeon was not found in lsmod. I
then checked lspci and the entire vga part was not there, as if a
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
I never thought I would say that, but radeon's capabilities are inferior even
to nvidia's legacy driver.
It has been a few hours now and I am still struggling to get vaapi working on
mpv and mplayer. 2d acceleration is bad,
Source: linux
Version: linux-image-5.10.0-7-amd64
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
Impending rant, because I think it is indeed a hardware failure that was caused
from the kernel upgrade.
I successfully downgraded linux-compiler-gcc-10-x86 and linux-kbuild-5.10 to
thei
Source: linux
Version: linux-image-5.10.0-7-amd64
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
Can I somehow determine that the button does run systemctl poweroff and not
sleep when I press it? All I can see in the shutdown messages, for that split
second they appear, is just the w
Source: linux
Followup-For: Bug #989010
X-Debbugs-Cc: pitsior...@gmail.com
First of all, I removed 5.10.38 because I want grub to directly boot to the
working kernel without me having to select it via grub's advanced menu.
Yes, nvidia (340 legacy) is the reason the tainted message pops up. To be
Package: src:linux
Version: 5.10.38-1
Severity: important
X-Debbugs-Cc: pitsior...@gmail.com
Preface.
I have disabled sleep, hibernate etc via systemd as you can see below.
$ systemctl status sleep.target suspend.target hibernate.target hybrid-
sleep.target
● sleep.target
Loaded: masked (Rea
Source: linux
Followup-For: Bug #953680
I just got the email that notified me that this bug report was closed because
kernel 5.5 (5.5.13 in fact) has reached unstable.
Kernel 5.6 was released yesterday from upstream, so isn't it a bit late now for
5.5?
Normally, I install it as soon as it hits th
Package: linux-image-5.5.0-rc5-amd64
Severity: normal
Kernel 5.5 was released more than a month ago, on January 26th 2020, and it has
not reached the repos yet. There is only its rc5 revision, which isn't the last
rc, and it is on experimental only. Why?
Meanwhile, 5.6, now on rc5, will be releas
Package: src:linux
Version: 4.19.28-1
Severity: normal
Dear Maintainer,
After today's upgrade to 4.19.28 (package linux-image-4.19.0-4-amd64), the
above mentioned is spammed dozens of times at boot.
Other than that, I see no other issue, not even a single delay of the boot
process.
Installing th
Package: src:linux
Version: 4.19.13-1
Severity: normal
I have been using wol on all my ethernet connected systems since 2012 that I
discovered it. Most of the times I use a wol app from my phone and wakeonlan or
etherwake from my linux systems.
According to lspci -k, this is my card and the r8169
Package: linux-image-4.10.0-rc6-amd64
Severity: normal
Dear Maintainer,
I was searching the repo earlier for some rc version of 4.20 and I came across
this package.
Kernel 4.10 was released 18+ months ago, it was not an lts, the package is not
a stable version of it and it also lacks the mandator
32 matches
Mail list logo
