Re: Report on bookworm alpha 2 installer: wl wifi driver not found

[raph]

Cyril Brulebois writes:

> Hi raph,
>
> raph  (2023-02-25):

Hi Cyril,

>> On a macbook air 11" 2015 (MacBookAir 7,1 1.0), currently running buster
>> with the wl driver, the network step of configuration failed. And I dit
>> not found the wl driver in the provided list to pick a driver from.
>>
>> Is this an expected behavior (for example due to legal issues)?
>> Should this be a bug report?
>> Is there anything I can do to help?
>
> It'd be great to attach /var/log/syslog (possibly gzipped) from the
> installer environment, so that we have a chance of tracking this down.
>
> Are you sure that was about the driver (kernel module) rather than about
> firmware?

H,, look this is beyond my current knowledge to answer.

> Any chance you could let us know what your buster installation
> is reporting? (e.g. output of `lsmod` and `dpkg -l|grep firmware`).

In the attached gzipped archive you'll find:

debian-report $ ll
total 116K
-rw-r--r-- 1 raph raph  97K Feb 26 09:54 bookworm-syslog
-rw--- 1 raph raph 1.3K Feb 26 09:45 buster-dpkg-firmware.txt
-rw--- 1 raph raph 5.7K Feb 26 09:45 buster-lsmod.txt
-rw--- 1 raph raph  618 Feb 26 09:46 buster-sources.list

A few month ago, I tried to move this machine to testing. But like with
a previous debian install, when moving to testing the network stopped
working. I do not know if this is important / related or not.

Tell me I can do anything else to help.

This machine is ok with buster, but I can back it up and try a complete
install when/if needed to contribute.

Take care

Cheers,

raph

--
Reduce Reuse Repair Recycle Rethink
Réduire Réutiliser Réparer Recyler Repenser

Re: Report on bookworm alpha 2 installer: wl wifi driver not found

[Cyril Brulebois]

raph  (2023-02-26):
> In the attached gzipped archive you'll find: […]

Ping attachment. :)


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


signature.asc
Description: PGP signature

Re: Report on bookworm alpha 2 installer: wl wifi driver not found

[raph]

Cyril Brulebois writes:

> raph  (2023-02-26):
>> In the attached gzipped archive you'll find: […]
>
> Ping attachment. :)

Oops, Sorry.



debian-report.tgz
Description: archive of requested files

Cheers,

raph

--
Reduce Reuse Repair Recycle Rethink
Réduire Réutiliser Réparer Recyler Repenser

Bug#1032014: setupcon: do not copy security attribute

[Christian Göttsche]

Package: console-setup
Version: 1.217
User: selinux-de...@lists.alioth.debian.org
Usertags: selinux
Tags: patch

When copying files into the temporary working directory do not copy
the security context but use the default one for the target path.
Otherwise, e.g. when using SELinux, the context might not be allowed
on the destination filesystem and the process needs elevated access to
the original context.

diff --git a/setupcon b/setupcon
index 
50139a8e06c63fd14df4a6ec204e45a1aa563fe2..ac06c473cc0647183d7ca5d937595665cdb68efc
100755
--- a/setupcon
+++ b/setupcon
@@ -1213,7 +1213,7 @@ if [ "$setupdir" ]; then
 f="${f%.gz}"
 case "$arg" in
 *.gz) zcat "$arg"
>"$setupdir/etc/console-setup/$f" ;;
-*) cp -a "$arg"
"$setupdir/etc/console-setup/$f" ;;
+*) cp -aZ "$arg"
"$setupdir/etc/console-setup/$f" ;;
 esac
 printf "%s" "/etc/console-setup/$f" \
 | sed "s/'/\'\'\'/g"

Re: Report on bookworm alpha 2 installer: wl wifi driver not found

[Cyril Brulebois]

Hi,

raph  (2023-02-26):
> Cyril Brulebois writes:
> > Are you sure that was about the driver (kernel module) rather than
> > about firmware?
> 
> H,, look this is beyond my current knowledge to answer.

Thanks for the logs, that seems to be a *module* issue rather than a
firmware issue, and your subject (about wl) seems absolutely on point.

The relevant part of the installer's syslog is:

Feb 26 08:50:50 kernel: [   28.095391] b43-phy0: Broadcom 4360 WLAN found 
(core revision 42)
Feb 26 08:50:50 kernel: [   28.095805] b43-phy0 ERROR: FOUND UNSUPPORTED 
PHY (Analog 12, Type 11 (AC), Revision 1)
Feb 26 08:50:50 kernel: [   28.095810] b43: probe of bcma0:1 failed with 
error -95
Feb 26 08:50:50 kernel: [   28.095839] Broadcom 43xx driver loaded [ 
Features: PNLS ]

after a few lines about bcma-pci-bridge.

So your board is definitely detected, there's a module that tries to do
something with it, but fails…

> A few month ago, I tried to move this machine to testing. But like with
> a previous debian install, when moving to testing the network stopped
> working. I do not know if this is important / related or not.
> 
> Tell me I can do anything else to help.
> 
> This machine is ok with buster, but I can back it up and try a complete
> install when/if needed to contribute.

All files are super useful. The installer logs (meaning bookworm kernel)
are about bcma/b43. Those don't appear in your list of buster modules,
which contains “wl” instead. A quick search on bcma and wl suggests that
they might fight each other, at least in some kernel versions:
  
https://askubuntu.com/questions/592191/error-during-startup-b43-phy0-unsupported-phy

Checking the contents of current nic-wireless-modules udebs, we do ship
bcma.ko, but not wl.ko, so that's not about a competition between both
modules (at least in the installer context).

Now, looking at kernel sources, I'm not seeing any broadcom-wl driver in
mainline. Did you install a specific module on your buster system to get
wireless up and running?

I'm seeing a broadcom-sta source package that builds broadcom-sta-dkms
and broadcom-sta-source, I suppose that's what you might be using on
buster, after a successful wired install, maybe? At least your board
(4360) is listed in its description.


It's a binary-only driver so that's not something we include in the
installer, and if the above analysis is correct, I'm not sure we can do
anything about it. :(


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


signature.asc
Description: PGP signature

Bug#1028517: marked as done (tasksel: [INTL:tr] turkish translation update)

[Debian Bug Tracking System]

Your message dated Sun, 26 Feb 2023 18:21:18 +
with message-id 
and subject line Bug#1028517: fixed in tasksel 3.72
has caused the Debian Bug report #1028517,
regarding tasksel: [INTL:tr] turkish translation update
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Package: tasksel
Severity: wishlist
Tags: l10n patch

Hello,

Attached is the updated Turkish translation of the tasksel debconf template.
It has been submitted for review to the debian-l10n-turkish mailing list.
Please include it in your next upload.

Regards,
Atila KOÇ

--- YASAL UYARI ---
Bu iletinin gövdesi ve ekleri gizli bilgi içerebilir. Bu ileti yalnızca 
gönderilen kişilere özeldir. Eğer size yanlışlıkla ulaşmışsa, lütfen hemen 
siliniz ve göndereni bilgilendiriniz. Bu iletideki içerik gönderene ait olup 
Artı Endüstriyel Elektronik A.Ş. resmi görüşü olmak zorunda değildir. Bu 
iletinin gönderilmeden önce virüs ve diğer zararlı bileşenlere karşı 
denetimleri yapılmıştır. Buna karşın, e-posta iletiminin güvenli ve hatasız 
olduğu garanti edilemediğinden, iletiniz size ulaşana kadar değişmiş ve 
bozulmuş olabilir. Bu ileti nedeni ile göreceğiniz zararlardan Artı Endüstriyel 
Elektronik A.Ş. sorumlu tutulamaz.

# Turkish translation of tasksel.
# This file is distributed under the same license as the tasksel package.
# Recai Oktaş , 2004.
# Mert Dirik , 2014.
#
msgid ""
msgstr ""
"Project-Id-Version: tasksel\n"
"Report-Msgid-Bugs-To: task...@packages.debian.org\n"
"POT-Creation-Date: 2018-05-23 01:37+0200\n"
"PO-Revision-Date: 2022-12-29 21:25+0300\n"
"Last-Translator: Atila KOÇ \n"
"Language: tr\n"
"Language-Team: Debian L10N Turkish \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Poedit 2.4.2\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"

#. Type: multiselect
#. Description
#. Type: multiselect
#. Description
#: ../templates:1001 ../templates:2001
msgid "Choose software to install:"
msgstr "Kurulacak yazılımları seçin:"

#. Type: multiselect
#. Description
#: ../templates:1001
msgid ""
"At the moment, only the core of the system is installed. To tune the system "
"to your needs, you can choose to install one or more of the following "
"predefined collections of software."
msgstr ""
"Şu anda sisteminizin yalnızca temel kısmı kurulmuştur. Sistemizi amacınıza "
"daha uygun duruma getirmek için, aşağıda size önerilen yazılımlardan bir ya "
"da daha fazlasını seçip, kurabilirsiniz."

#. Type: multiselect
#. Description
#: ../templates:2001
msgid ""
"You can choose to install one or more of the following predefined "
"collections of software."
msgstr ""
"Aşağıda size önerilen yazılımlardan bir ya da daha fazlasını seçip, "
"kurabilirsiniz."

#. Type: multiselect
#. Description
#: ../templates:3001
msgid "This can be preseeded to override the default desktop."
msgstr ""
"Ön tanımlı masaüstünden farklı bir seçim için aşağıdakiler kullanılabilir."

#. Type: title
#. Description
#: ../templates:4001
msgid "Software selection"
msgstr "Yazılım seçimi"

#~ msgid "${ORIGCHOICES}"
#~ msgstr "${CHOICES}"
--- End Message ---
--- Begin Message ---
Source: tasksel
Source-Version: 3.72
Done: Cyril Brulebois 

We believe that the bug you reported is fixed in the latest version of
tasksel, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cyril Brulebois  (supplier of updated tasksel package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Feb 2023 19:03:20 +0100
Source: tasksel
Architecture: source
Version: 3.72
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 1028517
Changes:
 tasksel (3.72) unstable; urgency=medium
 .
   [ Atila KOÇ ]
   * Updated Turkish debconf translation. Closes: #1028517
 .
   [ Aurélien COUDERC ]
   * Cleanup task-kde-desktop:
 - Drop apper, hardly maintained upstream, superseded by Plasma Discover.
 - Dro

Processing of tasksel_3.72_source.changes

[Debian FTP Masters]

tasksel_3.72_source.changes uploaded successfully to localhost
along with the files:
  tasksel_3.72.dsc
  tasksel_3.72.tar.xz
  tasksel_3.72_source.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

tasksel_3.72_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Thank you for your contribution to Debian.



Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 26 Feb 2023 19:03:20 +0100
Source: tasksel
Architecture: source
Version: 3.72
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Cyril Brulebois 
Closes: 1028517
Changes:
 tasksel (3.72) unstable; urgency=medium
 .
   [ Atila KOÇ ]
   * Updated Turkish debconf translation. Closes: #1028517
 .
   [ Aurélien COUDERC ]
   * Cleanup task-kde-desktop:
 - Drop apper, hardly maintained upstream, superseded by Plasma Discover.
 - Drop dragonplayer, already pulled transitively by kde-standard.
 - Drop plasma-nm, already pulled transitively by plasma-desktop.
 - Drop k3b/k3b-i18n, not necessary on default installs anymore these days.
Checksums-Sha1:
 d84310c9610bf4ae25d47d0622628fb8b9040bd7 17490 tasksel_3.72.dsc
 b64df519e43be0afcfd9dee1a2f8262c6e8e0ce9 296832 tasksel_3.72.tar.xz
 6e53afb3478334b23c22c004df375138b4ffaecf 6406 tasksel_3.72_source.buildinfo
Checksums-Sha256:
 100d9a725d613e873af0582bdccc1fb9f76cdafeca6a125de56f998a56333f40 17490 
tasksel_3.72.dsc
 119de31f3c6f813994fd8920acec74902d2a735fbd34c1bb0a73f645a1262860 296832 
tasksel_3.72.tar.xz
 50a463f45b2636863b501d81fb049b3ea958a13331f28850adff94a867efbc3c 6406 
tasksel_3.72_source.buildinfo
Files:
 c0dca5660ac8c910b7c4fd3886ea0cd7 17490 tasks optional tasksel_3.72.dsc
 b6c1db122f217ec85485838b8487942b 296832 tasks optional tasksel_3.72.tar.xz
 8dce135a14bd9af70e6a42f54adefd53 6406 tasks optional 
tasksel_3.72_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmP7nzIQHGtpYmlAZGVi
aWFuLm9yZwAKCRD/kUrwwrNVIPkJEACeBMR7jMBrulrN1jPAtVjB8dtPPzfabPcb
JkDapUMvr/TNP4f0dz3V7JLgLWMCyfNoVKp3dDq0l1LtHBOMAn776XWxkNmgpnkB
C0OMibI/4pXI5tGt1MwA2vN/0MR7NPw70s01lORjFZaYM0jIuyLS8j73bzd2Hj35
6ZbXT16ilm4wIY7phudUHungnp8oXWCzPb6Ii6AQIuiIdfkp2NHjPjNWTPypuSP+
wlgNU1f4QiMVEKioJnkMCa8S0ENjmqYHjbTYvzDFK/OvN80mT79fV/LXTdIIThq5
6cUFTcYIhuQNB4dZPVU4wr8gkpC25PN8kk6LeqNxW1kpAMyy4+QRuV+8tpi1Tg63
BM+ZklUNMqczNl9NvVzsmW5YN7Yskf29Yv8Fo3dHfw32wOvgaZkiK58QhlNLN4Mn
DgcdowYimsMOewusbs9uzEQcFwMwFhKSvEamNk/QAoKhX9MJJyzefe8DJOtQW4e9
KPJLrudOKI6PzNm4IjKmtX84kAK8rebGks2iRCR6Fkv8rwiHBQZviRjDRrSrybrq
P3hRGdBiIYPSr7W/PfQeFfAMRtve90XWvge4HlwrKVVC2YPxHhhuvi232Easv6Z+
2/JJmagEim7F+1hYdLwQ00GSLVdOweDQPZf5X0NBg2nIZqwf817LNblGNK8OGbBI
C9lSCnRfMQ==
=Jj7g
-END PGP SIGNATURE-

Re: Report on bookworm alpha 2 installer: wl wifi driver not found

[raph]

Cyril Brulebois writes:

> Hi,
>
> raph  (2023-02-26):
>> Cyril Brulebois writes:
>> > Are you sure that was about the driver (kernel module) rather than
>> > about firmware?
>>
>> H,, look this is beyond my current knowledge to answer.
>
> Thanks for the logs, that seems to be a *module* issue rather than a
> firmware issue, and your subject (about wl) seems absolutely on point.
>
> The relevant part of the installer's syslog is:
>
> Feb 26 08:50:50 kernel: [   28.095391] b43-phy0: Broadcom 4360 WLAN found 
> (core revision 42)
> Feb 26 08:50:50 kernel: [   28.095805] b43-phy0 ERROR: FOUND UNSUPPORTED 
> PHY (Analog 12, Type 11 (AC), Revision 1)
> Feb 26 08:50:50 kernel: [   28.095810] b43: probe of bcma0:1 failed with 
> error -95
> Feb 26 08:50:50 kernel: [   28.095839] Broadcom 43xx driver loaded [ 
> Features: PNLS ]
>
> after a few lines about bcma-pci-bridge.
>
> So your board is definitely detected, there's a module that tries to do
> something with it, but fails…
>
>> A few month ago, I tried to move this machine to testing. But like with
>> a previous debian install, when moving to testing the network stopped
>> working. I do not know if this is important / related or not.
>>
>> Tell me I can do anything else to help.
>>
>> This machine is ok with buster, but I can back it up and try a complete
>> install when/if needed to contribute.
>
> All files are super useful. The installer logs (meaning bookworm kernel)
> are about bcma/b43. Those don't appear in your list of buster modules,
> which contains “wl” instead. A quick search on bcma and wl suggests that
> they might fight each other, at least in some kernel versions:
>   
> https://askubuntu.com/questions/592191/error-during-startup-b43-phy0-unsupported-phy
>
> Checking the contents of current nic-wireless-modules udebs, we do ship
> bcma.ko, but not wl.ko, so that's not about a competition between both
> modules (at least in the installer context).
>
> Now, looking at kernel sources, I'm not seeing any broadcom-wl driver in
> mainline. Did you install a specific module on your buster system to get
> wireless up and running?
>
> I'm seeing a broadcom-sta source package that builds broadcom-sta-dkms
> and broadcom-sta-source, I suppose that's what you might be using on
> buster, after a successful wired install, maybe? At least your board
> (4360) is listed in its description.
>
>
> It's a binary-only driver so that's not something we include in the
> installer, and if the above analysis is correct, I'm not sure we can do
> anything about it. :(
>
>
> Cheers,

Thank you for all these explanations :)

Since I got this second hand machine, I have always used a usb/ethernet
adaptor before installing wifi using non-free. I think the last
installation was performed using a debian buster gnome live iso.

One of my source of information at one point was :

https://wiki.debian.org/wl

If the information is interesting to you, I can re-install buster to see
how I get the driver. I can also try to install bookworm using ethernet
first, and then wifi, if it can provide you useful information.

Any way, my attempt at bookworm DI was mostly to test the installer with
the machines at home and provide feedback. So it is ok for me to stay on
buster on this machine.

Thanks again to you all and take care,

Cheers,


--
Reduce Reuse Repair Recycle Rethink
Réduire Réutiliser Réparer Recyler Repenser

Re: Report on bookworm alpha 2 installer: wl wifi driver not found

[Cyril Brulebois]

raph  (2023-02-26):
> Since I got this second hand machine, I have always used a usb/ethernet
> adaptor before installing wifi using non-free. I think the last
> installation was performed using a debian buster gnome live iso.

OK!

I was slightly afraid we might have regressed feature-wise (if using wl
was possible in an earlier version), but I didn't think it was probable.

> Any way, my attempt at bookworm DI was mostly to test the installer with
> the machines at home and provide feedback. So it is ok for me to stay on
> buster on this machine.

I think we're all good: great to read about the successes, slightly sad
about the failure, but if that's not something that's supported by the
in-kernel broadcom module, there's not much we can do.


Thanks for your reports!
 

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


signature.asc
Description: PGP signature

Non-free-firmware changes - initial cut released!

[Steve McIntyre]

Hey all!

Here's a status update on the non-free-firmware changes that we voted
for last year [1].

Cyril has done a huge amount of work [2], implementing the bulk of
what we need. We released d-i bookworm alpha 2 last weekend [3],
including those changes. Our own testing shows that things work well
on *our* test hardware, but we'd like some more assistance in testing!
If you would like to help and you have a machine that wants firmware,
please:

 1. Boot the installer and verify that it identifies the necessary
firmware correctly - go as far as configuring the network. If
there are still missing firmware blobs, d-i will complain. If you
stop before making any changes in the partitioner (partman), then
this should a safe thing to do on your existing machine and won't
make any permanent changes.

 2. (If you can) complete an installation and check that all the
hardware works as expected after normal bootup. We'd love people
to do this to verify the more awkward blobs: audio and GPU.

We're especially interested in wifi, NIC and GPU firmware here, as
they have been the things blocking people installing Debian in the
past.

Please file bugs against "installation-reports" with whatever you
find! Thanks in advance!

We're also planning more updates before the full bookworm release -
watch this space!

[1] https://www.debian.org/vote/2022/vote_003
[2] https://debamax.com/blog/2023/02/27/debian-versus-non-free-firmware/
[3] https://lists.debian.org/debian-devel-announce/2023/02/msg5.html

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Because heaters aren't purple!" -- Catherine Pitt