Bug#1037087: chromium-l10n: The following packages have unmet dependencies: chromium-l10n : Depends: chromium (< 112.0.5615.138-1~deb11u1.1~) but 114.0.5735.90-2~deb11u1 is to be installed
Hi, I tried installing chromium-l10n again on a freshly updated Bullseye machine (with the bullseye-security and bullseye-updates repositories enabled, of course) and this time the operation succeeded with no conflicts. Unless there are new reports about this problem persisting, I think this bug can be closed. Best regards.
Bug#1022025: fixed in linux 5.10.149-2
On Thu, 27 Oct 2022 21:01:15 +0200 Salvatore Bonaccorso wrote: > Can you please fill a new bug for your issue, which would still > be > present in the 5.10.149-2 release? There are two users which > report > that they still have problems with the amdgpu driver still in > 5.10.149-2. I think bug 1022806 is a recent one referring to 5.10.149-2 specifically, which is about this same issue. I don't think there is a need to report yet another bug about it. Best regards. -- inasprecali
Bug#1022025: fixed in linux 5.10.149-2
On Thu, 27 Oct 2022 06:17:10 + Debian FTP Masters wrote: > Source: linux > Source-Version: 5.10.149-2 > Done: Salvatore Bonaccorso > > We believe that the bug you reported is fixed in the latest version of > linux, which is due to be installed in the Debian FTP archive. I'm sorry, but your belief seems to be mistaken, since we have multiple reports o 5.10.149-2 still not booting with the amdgpu driver. Best regards. -- inasprecali
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Diederik de Haas writes: > Then I'm inclined to think this *is* a separate issue, which is > due to the upgrade to -19, but that you happen to have an AMD > GPU is 'not' relevant. > > I realize it's not what you want, but may result in an useful > extra data point if you (for this test) switch those parameters > to enable radeon support and disable amdgpu support. Can you try > that? > > If that test does not make a difference, then I'm quite sure > it's a separate issue and it would be best to open a new bug > report for that. I tried booting 5.10.0-19 with an empty command line string and it worked, although it’s now using the "radeon" gpu driver while I’d like to use the "amdgpu" driver instead, mainly for better Vulkan support. Booting with command line options to disable "radeon" and enable "amdgpu" works for 5.10.0-18 and earlier. I don’t know if this an entirely separate issue, however. I can file a separate bug if you think it is appropriate. Best regards. -- inasprecali
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
Diederik de Haas writes: > Then I'm inclined to think this *is* a separate issue, which is > due to the upgrade to -19, but that you happen to have an AMD > GPU is 'not' relevant. > I realize it's not what you want, but may result in an useful > extra data point if you (for this test) switch those parameters > to enable radeon support and disable amdgpu support. Can you try > that? > > If that test does not make a difference, then I'm quite sure > it's a separate issue and it would be best to open a new bug > report for that.
Bug#1022042: kernel 5.10.149-2 does not help
On Sun, 23 Oct 2022 13:43:30 +0200 Diederik de Haas wrote: > Andreas and inasprecali, > > On zondag 23 oktober 2022 09:17:44 CEST Andreas Wirooks wrote: > > Kernel parameters are: > > radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 > > amdgpu.cik_support=1 amdgpu.gpu_recovery=1 > > You both have kernel parameters like these. Can you explain why? > I have an AMD GPU on a machine and I have never set parameters like these. In my case, it's because, without command line parameters, the kernel will select the "radeon" driver, while I want to use the "amdgpu" driver instead. The options "radeon.si_support=0 amdgpu.si_support=1" disable radeon support and enable amdgpu support respectively. 5.10.0-18 and earlier have always worked as expected. 5.10.0-19, even with the very latest stable update, fails to boot. Best regards. -- inasprecali
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
On Sun, 23 Oct 2022 13:40:26 +0200 Diederik de Haas wrote: > Does it really not boot? Or does the screen not work properly? > > The cases in this bug report all boot AFAIK, it's just that the screen does > not work properly, but people were able to SSH into the machine. > If your system actually does not boot, then I'm inclined to think that that is > a different problem. It does not boot at all, I'm unable to SSH into it. It's not merely that the display does not work. At the moment, I'm unable to provide additional information, but I'll try looking into it as soon as possible. Best regards -- inasprecali
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
After updating to the latest version (5.10.149-2), my system running an AMD GPU and CPU still does not boot. I am unable to retrieve any logs from the systemd journal. CPU: AMD FX-8350 GPU: AMD R9 270X (Southern Islands Family) Kernel command line parameters: GRUB_CMDLINE_LINUX="radeon.si_support=0 amdgpu.si_support=1" 5.10.0-19 fails to boot, while 5.10.0-18 does. Best regards. -- inasprecali
Bug#1022042: linux-image-amd64: linux-image-5.10.0-19-amd64 fails to boot on machines with AMD integrated graphics
I can confirm this same exact problem on a machine of mine. CPU: AMD FX-8350 GPU: AMD R9 270X (Southern Islands Family) 5.10.0-19 fails to boot, while 5.10.0-18 does. Best regards. -- inasprecali
