Hello there Mark,
thanks for your email, and for the followup ping; weeks are well-filled with
$job, baby and other involvements.
Regarding firmware-nonfree updates, I have related my last-years' experience
on d-devel: https://lists.debian.org/msgid-search/2390124.3VsfAaAtOV@turnagra
I insist:
Control: tags -1 +patch -help
Control: clone -1 -2
Control: retitle -2 Thinkpad AMD: amd_pmc module is required for correct s0ix
(Windows mode) suspend
Control: severity -2 important
Hello there,
My understanding is that there are two distinct bugs here; hereby splitting
to make this clearer.
Control: tags -1 +patch
Le vendredi, 20 janvier 2023, 21.38:42 h CET Salvatore Bonaccorso a écrit :
> There is the patchset currently asked for inclusion at
> https://lore.kernel.org/stable/20230119235200.441386-1-harry.wentl...@amd.co
> m/T/#m3b5b3616eac750cfd7c9bd00ac1cf95006a6aeec which is for
Control: retitle -1 Thinkpad: amd_pmc module required for on 6.1 for correct
suspend
Le mardi, 17 janvier 2023, 22.53:54 h CET Didier 'OdyX' Raboud a écrit :
> Le mardi, 17 janvier 2023, 15.32:37 h CET Diederik de Haas a écrit :
> > On Monday, 16 January 2023 22:33:05 CET D
Control: found -1 6.1.6-1
Control: found -1 6.1.4-1
Control: severity -1 serious
Hello there,
Le mardi, 17 janvier 2023, 15.32:37 h CET Diederik de Haas a écrit :
> On Monday, 16 January 2023 22:33:05 CET Didier 'OdyX' Raboud wrote:
> > This is on 6.1.4-1a~test, patch
Hello Salvatore,
17 janvier 2023 07:14 "Salvatore Bonaccorso" a écrit:
> I will bite the bullet (taking full responsibility for it if
> necessary, don't blame the other kernel team members) and ask here now
> the release team: Can we let linux 6.1.4-1 despite the RC bug
> reported, migrate to tes
Package: linux-image-6.1.0-1-amd64
Version: 6.1.4-1
Severity: important
Hello there,
this is a regression from 6.0.0 too; after post-suspend wakeup, my
plasma wayland session stays frozen; the two DisplayPort screens light
up, backgrounds are shown, but the mouse doesn't move, nothing works.
I'm
Hello there,
I finally managed to test
https://github.com/archlinux/linux/commit/7c4fed4d2afd27d7acb8835f8e79f49c99c03cdf.patch
(which is a revert of 4d07b0bc403403438d9cf88450506240c5faf92f)
… on top of 6.1.4-1.
I can confirm (without looking into any code-related details), that the two
of my
~exp1, but I can't rewind
further.
Hope that helps!
OdyX
11 janvier 2023 10:04 "Diederik de Haas" a écrit:
> On Wednesday, 11 January 2023 08:33:29 CET Didier 'OdyX' Raboud wrote:
>
>> Package: src:linux
>> Version: 6.1.4-1
>> Severity: serio
Package: src:linux
Version: 6.1.4-1
Severity: serious
Hello there,
Since booting 6.1.0-1, the 2nd DisplayPort output from my Lenovo Docking
Station doesn't get any output. It is _seen_ as connected by the screen, but
apparently gets no video signal (or just blank). This is clearly a regression
fr
Hello there Ben!
I hope Nattie and you had safe travels back from Kosovo!
Having recently acquired a new laptop (X13 AMD gen2 from Lenovo); I tried the
daily testing non-free d-i without being able to use the WiFi (finished the
install over usb-to-android), which made me look at the needed firm
Package: src:linux
Followup-For: Bug #948593
Of course, just after filing this bug, I remembered I could at least try with
MODULES=most, which allowed me to boot. So the problem can be more accurately
described as "some modules gone missing from 5.4+ kernel's initramfs'es with
MODULES=dep for aes/
Package: src:linux
Version: 5.4.8-1
Severity: important
Hello there,
Since 5.4 kernels, my /dev/sda5 cannot be unlocked from initramfs anymore, so
I can't boot under a 5.4* kernel (at least I haven't managed yet).
Straight after typing my LUKS passphrase, I get "crypt: Error allocating
crypto tf
Control: found -1 4.8.11-1
Le vendredi, 9 décembre 2016, 13.03:44 h CET Ben Hutchings a écrit :
> fgetty uses dietlibc, and the stable version of dietlibc still uses the
> vsyscall feature which is now disabled by default. You can make it
> work again by adding 'vsyscall=emulate' to the kernel co
reassign -1 linux 3.16.7-ckt4-3
Le vendredi, 6 mars 2015, 07.35:44 William Melgaard a écrit :
> Dear Maintainer,
>
>* What led up to the situation?
> The default IOMMU setting in the BIOS for a GIGABYTE motherboard is
> off. Attempting to install a Debian system (Wheezy or Jessie AMD-64)
> wi
Hi Cyril,
Le jeudi, 30 janvier 2014, 02.51:48 Cyril Brulebois a écrit :
> as mentioned earlier this month, I had a little proof of concept for
> Paris Mini-DebConf 2014[1]. I've polished a few things, so here we go.
>
> 1. https://lists.debian.org/debian-boot/2014/01/msg00239.html
Thanks for th
Hi Jonathan,
Le jeudi, 25 octobre 2012 22.25:03, Jonathan Nieder a écrit :
> Didier Raboud wrote:
> > Tags: upstream
>
> What upstream version did you test?
Well we only tried packaged kernels, all wheezy, unstable and experimental
exhibit this behaviour. We started to compile an upstream kerne
Le Thursday 17 February 2011 11:30:40 jida...@jidanni.org, vous avez écrit :
> Why can't they simply ensure the lower layers in this particular
> dependency pyramid are sent out before or at the same time as the other
> parts?
Because it's not important in unstable (as it gets solved over time)!
Le Thursday 17 February 2011 02:04:27 jida...@jidanni.org, vous avez écrit :
> >>>>> "D'R" == Didier 'OdyX' Raboud writes:
> D'R> Such temporary glitches are perfectly normal (and transitional) in the
> unstable D'R> distribution.
reopen 607669
found 607669 2.6.37-1~experimental.1
retitle 607669 linux-image-2.6.37-trunk: Dell Latitude D630 backlight fails to
resume to "on"
thanks
Hi,
sorry, but despite what I thought, this has happened again using the 2.6.37-
trunk version. Hence re-opening.
Cheers, OdyX
--
Didier Rab
tags 602444 -patch
thanks
Hi Ben, and thanks for your answer,
Le jeudi 4 novembre 2010 23:37:48 Ben Hutchings, vous avez écrit :
> On Thu, 2010-11-04 at 22:52 +0100, Didier Raboud wrote:
> > Package: firmware-brcm80211
>
> What has this got to do with the firmware?
The observable facts I coul
Hrm,
I was probably shooting too fast: it didn't work - I believed it did as by
"not"
loading the module, it allowed to boot without panic, but no wireless.
More tomorrow, cheers,
OdyX
--
Didier Raboud, proud Debian Maintainer (DM).
CH-1020 Renens
did...@raboud.com
--
To UNSUBSCRIBE, em
Le dimanche 5 septembre 2010 17:56:44 Ben Hutchings, vous avez écrit :
> forwarded 595661 alsa-de...@alsa-project.org
> thanks
Hi Ben,
where has that bug been forwarded ? I can't find a trace of it in the alsa-
de...@a-p.org during September.
Cheers,
OdyX
--
Didier Raboud, proud Debian Main
reassign 595661 src:linux-2.6 2.6.35-1~experimental.2
found 595661 2.6.32-21
thanks
Hi,
I just tested with Sid/Squeeze's kernel: I can reproduce the behaviour, hence
marking "found" correctly (and marking as found on source as the binary
packages
names differ; please correct to match your wor
Le lundi 2 août 2010 00:27:10, vous avez écrit :
> On Fri, Feb 05, 2010 at 11:58:36AM -0500, Dave Witbrodt wrote:
> > Package: lm-sensors
> > Severity: normal
> >
> >
> > This looks like a consequence of a recent change in kernel policy
> > regarding resource conflicts. According to the 'kernel-
25 matches
Mail list logo
