Processed: bug 1029116 is forwarded to https://patchwork.kernel.org/project/linux-wireless/patch/be3457d82f4e44bb71a22b2b5db27b644a37b1e1.1677107277.git.lore...@kernel.org/

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 1029116 
> https://patchwork.kernel.org/project/linux-wireless/patch/be3457d82f4e44bb71a22b2b5db27b644a37b1e1.1677107277.git.lore...@kernel.org/
Bug #1029116 [src:hw-detect] hw-detect: check-missing-firmware fails will 
attempting to reload kernel module on MT7922 WiFi card
Set Bug forwarded-to-address to 
'https://patchwork.kernel.org/project/linux-wireless/patch/be3457d82f4e44bb71a22b2b5db27b644a37b1e1.1677107277.git.lore...@kernel.org/'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1029116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: bookworm release date?

[Adam D. Barratt]

Hi,

Sorry for the delayed reply, apparently I'm further behind than I
realised. :-(

On Fri, 2023-02-17 at 21:56 +0100, Paul Gevers wrote:
[...]
> What do people think of the idea
> to start picking a release date already?
> 
[...]
> Adam, I think we'd also want to do a point release before that time, 
> e.g. to include a fix for bug #1029803. What do you think about it?
> 

Yes. We also really want to get a debian-archive-keyring update into
bullseye before the release, or we can't use the new keys to sign the
bookworm release files. But first we need to get it into unstable. I'm
aware that we're very late here, sorry. :-(

ftp-master have now published their bookworm keys, so we can get those
incorporated. For the SRM side, you probably saw that we've been
considering moving to an EC key. From the very limited responses to the
discussion I started on debian-release, I'm still not entirely sure if
that's feasible / a good idea.

It would also be good to finally get the shim updates into bullseye at
the same time, unless Steve tells me that's a bad plan. :-)

Regards,

Adam

Re: bookworm release date?

[Steve McIntyre]

On Thu, Mar 09, 2023 at 05:05:28PM +, Adam Barratt wrote:
>
>Sorry for the delayed reply, apparently I'm further behind than I
>realised. :-(

:-/ *hugs*

>On Fri, 2023-02-17 at 21:56 +0100, Paul Gevers wrote:
>[...]
>> What do people think of the idea
>> to start picking a release date already?
>> 
>[...]
>> Adam, I think we'd also want to do a point release before that time, 
>> e.g. to include a fix for bug #1029803. What do you think about it?
>> 
>
>Yes. We also really want to get a debian-archive-keyring update into
>bullseye before the release, or we can't use the new keys to sign the
>bookworm release files. But first we need to get it into unstable. I'm
>aware that we're very late here, sorry. :-(
>
>ftp-master have now published their bookworm keys, so we can get those
>incorporated. For the SRM side, you probably saw that we've been
>considering moving to an EC key. From the very limited responses to the
>discussion I started on debian-release, I'm still not entirely sure if
>that's feasible / a good idea.
>
>It would also be good to finally get the shim updates into bullseye at
>the same time, unless Steve tells me that's a bad plan. :-)

:-) I uploaded the latest signed shim last night expressly to have it
in the next bullseye point release. Do you want an unblock for that?

I'm also looking at some (small!) updates for grub too.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
“Why do people find DNS so difficult? It’s just cache invalidation and
 naming things.”
   -– Jeff Waugh (https://twitter.com/jdub)

Bug#1029116: hw-detect: check-missing-firmware fails will attempting to reload kernel module on MT7922 WiFi card

[Cyril Brulebois]

Control: reassign -1 src:linux 6.1.15-1

Cyril Brulebois  (2023-01-17):
> Stuart Hayhurst  (2023-01-17):
> > Source: hw-detect
> > Version: 1.152
> > Severity: important
> > X-Debbugs-Cc: stuart.a.hayhu...@gmail.com
> > 
> > Running "Detect network interfaces" hangs the installer, and with a
> > bit of troubleshooting, it's caused when check-missing-firmware
> > removes and loads the kernel module for my WiFi chip (mt7921e driver)
> 
> This wouldn't be the first issue about this modprobe dance, but I'm not
> sure why the kernel would go haywire… I'm definitely looking into
> firmware related issues these days, so maybe I'll be able to reproduce
> it somewhere, and/or find a different solution to account for the newly
> installed firmware (current plan would be to keep hw-detect ± as is
> while introducing support for non-free-firwmare).

Reassigning to the kernel, which definitely shouldn't panic…

More details in the MR:
  https://salsa.debian.org/kernel-team/linux/-/merge_requests/673


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: Re: Bug#1029116: hw-detect: check-missing-firmware fails will attempting to reload kernel module on MT7922 WiFi card

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 6.1.15-1
Bug #1029116 [src:hw-detect] hw-detect: check-missing-firmware fails will 
attempting to reload kernel module on MT7922 WiFi card
Bug reassigned from package 'src:hw-detect' to 'src:linux'.
No longer marked as found in versions hw-detect/1.152.
Ignoring request to alter fixed versions of bug #1029116 to the same values 
previously set
Bug #1029116 [src:linux] hw-detect: check-missing-firmware fails will 
attempting to reload kernel module on MT7922 WiFi card
Marked as found in versions linux/6.1.15-1.

-- 
1029116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Re: Bootaa64.efi and grubaa.efi are missing from the folder EFI/boot in EFI partition

[Steve McIntyre]

On Sun, Mar 05, 2023 at 04:02:04PM +0800, gugudu wrote:
>Hello, Developers.
>I installed Debian 12 BooksWorm on KunPeng（鲲鹏） / Phytium（飞腾）'s
>computer. These PCs are based on the ARM64 UEFI platform. After restarting,
>UEFI can't find Debian's EFI boot file, and GRUB can't boot. These UEFI
>firmware are made by Kunlun Tech（昆仑太科） or Byo software（百敖软件）. After
>Debian operating system is installed, I found that bootaa64.efi and grubaa.efi
>are missing from the folder EFI/boot in the EFI partition of the hard disk. If
>you try to repair the boot, you need to copy shimaa64.efi and grubaa.efi in EFI
>/debian to EFI/boot. Rename EFI/boot/shimaa64.efi to EFI/boot/bootaa64.efi.
># cp EFI/debian/shimaa64.efi EFI/boot/bootaa64.efi
># cp EFI/debian/grubaa64.efi EFI/boot/grubaa64.efi

It sounds like your firmware does not support setting of EFI boot
variables. Fully functional firmware should *not* need files in the
removable media path (EFI/boot like that). See

  
https://wiki.debian.org/UEFI#Force_grub-efi_installation_to_the_removable_media_path
 

for more information, and the correct way to work around this issue in
your firmware.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"...In the UNIX world, people tend to interpret `non-technical user'
 as meaning someone who's only ever written one device driver." -- Daniel Pead

Re: Error debian Acer nitro 5

[Steve McIntyre]

Hi Diego,

On Mon, Mar 06, 2023 at 07:33:50PM -0300, Diego Santos wrote:
>package: installation reports Boot method: DVD? usb pen? Network?> Image version: got> Data:  Machine: an515-52-7974 Processor: i7 Intel acer nitro 5 an515-52-7974 | i7-8750h Memory:
>16 Partitions:  External use
>hdc 1 2 with dual boot windows I tested it without it as main Output from lspci
>-knn (or lspci -nn): Basic system installation checklist: [O] = OK, [E] = Error
>(describe below), [ ] = did not try Initial boot: [ ]ok Detect network card: [
>]ok Configure network: [ ],,ok free kernel mode Detect installation medium: [ ]
>gave installation error Load installer modules: [ ] loads davfail Detect hard
>drives: [ ] ok Partition hard drives: [ ] ok Install base system: [ ] ok Clock/
>time zone setting: [ ]ok Set username/password: [ ]ok Installation tasks: [ ]
>ok Install the bootloader: [ ] ok Installation total: [ ] not installed Accepts
>Ubuntu 19.04 kernel firmware well

I'm struggling to understand wha you're trying to tell us here. Could
you give us a little more information please? What error did you get,
exactly? Which Debian installer image were you trying to use?

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
We don't need no education.
We don't need no thought control.

Bug#1032435: installation-reports: Fails to install GRUB bootloader

[John Talbut]

Thanks, Pascal, you gave me some more ideas where to look.

I have spent a lot of time on this without being able to discover 
exactly where the error lay in order to be able to correct it without 
going back to square 1.  In the end the only thing that has worked has 
been a complete reinstall including erasing all previous information in 
all partitions.


Consistently what was happening whatever I did was that when I tried to 
boot it would go straight to grub>: - The grub prompt on a blank screen. 
 When I checked the settings and files information on this screen, e.g. 
using ls and set commands, the information never corresponded to what 
was actually installed.


Clearly something was wrong that was used very early in the boot process 
but I was unable to find what.  None of the information that I could 
find online that I could make sense of stated exactly which files or 
settings the UEFI firmware first goes to.


One thing that seems to be the case but is not made clear is that grub 
needs two partitions for booting.  One is a plain EFI partition and the 
other is a normally formatted (e.g. ext4) partition mounted at /boot. 
Confusingly, although the EFI partition seems to get mounted as 
/boot/efi it has to be a separate partition in the installer 
partitioning scheme.