Hello,

First, thanks a lot to all of you :)

I have installed with success bookworm on two machines (scratch
installation using the DI alpha 2):
- lenovo ideapad 120S
- macbook air 13" 2011 (MacBookAir 4,2 1.0) w/ brcm43xx

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?

Thanks and take care

raph


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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi raph,

raph <debian@marvie.eu> (2023-02-25):

First, thanks a lot to all of you :)

I have installed with success bookworm on two machines (scratch
installation using the DI alpha 2):
- lenovo ideapad 120S
- macbook air 13" 2011 (MacBookAir 4,2 1.0) w/ brcm43xx

Great news, thanks for sharing.

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


Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmP6jyEACgkQ/5FK8MKz VSARYBAAhlZzcm6WoE4A5TqSytfcaySv4geFWO8Wv9v9rGLHvlbF8v16AeNcKvFS NXklPQ2Vz+oeX6FGetwuzELXEIxm1RlN34ksS3O84ANAUjWJeA6On7PYFi49CvQM Vy9/SjxKvlMckx0Phndt1thAtIZOz9s1XEO5oM0nQxnq+2DaR5iICbeqFjgmyv/2 oA+1lDs4mQI2aEfjlT70w7ZWBjZiSV0KorUJDzDbDoHCDjsyQcsyjp4PNFZwHWQj 9ACn89/9uaMT2w8W5ylYWS66uN+0T+jpULd8yNocqcUcavQE09aFIYXkjfYqdGDX XgecdQydKD63O9Q2hHFAJW7R2t1tFT/S/4vf3MRSvX9oglkBUcOEwGCSwvu4QQKd mMn9rwZo941bGxjkzalSqZtkXOZ+UgYB4XVYZvdjn1/05XTZzUCitBnBFzVRZRJT p8ywtqgXXoPrjX+YWloewUZOnLZ58qwGP5mYe46l4vMaMg4M7WSse6Rw6uspHJmo NAVuvmsOpawsVGfY4abn4wTaJw3tO/EIHb5vlJAl1AxO4J+dAMhoid8k+0G1q8H7 hjob5fA6jDRxFCuJcRNwALGEW4k7nU2mc+qGxj/jxxhWTIo1OfyRyj43PUBGv/YK Y2WQ9Nl4nQ+hwW+pEwtY0JzrJ83ZMOULDLYUHDQXOLQ9qiYbB7I=
=h9lj
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
*

Cyril Brulebois writes:

Hi raph,

raph <debian@marvie.eu> (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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

raph <debian@marvie.eu> (2023-02-26):

In the attached gzipped archive you'll find: […]

Ping attachment. :)


Cheers,
--
Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmP7YrYACgkQ/5FK8MKz VSA3YQ//Z2pkusFdLniIpQpwMjHjgA6EQs68tlXeBud6He479i0J6yFWze81yDRV LgAO0AuVECF0Kq7aXFIS2jwTDpScmDxIW90pSsW7CJ5Ta8c8y2a4f2bxuTMXfDLf g/RDQT69bWXOSGRWEfq5DKdBptk/yRiXVjt4hiwZZ7q/dcbqfsCOUuGkATK1eL1p 35eKLqHuPjXm1jlwOXMlGFwy8XMTuNgiRKbkVj22lo9ULwxPoD30bLXSWAPP12Xo wfGdmShUQ+1e+tjB4ga+naM6KEOtmm4O/8f7UkBizbBlxvulwoMdDMS6Z54XeJ+1 fDFDw4nQ20hMHAzzbT5KcTtmRD9n6uHhNpbMxfx1jkcZsQ5moEiOn9pHq9DLgD3S NZWpCBbParV06SeBq+utZDVU9jW14/zhrzjx4vIH4nl2qkuqcQK36fWqvoGiJvC2 PW7irvRrjSCSEsZGDVmGUY4fJx59WOWZHhsKpagUN5QMjM+eArg3Tr8ycDiT1gUV hus2KXRV+IAKNaUz+GCkJ7CJ0IwaoshyjOpVOhNXyENVjl64Y1ynchk4+o3iJtrt u7aJnYXpXZaGD9LuE2LfMQc8icFwFMWXKUoOpvbn/VabRduxAkUwi1hMGh7eh90H 7SoyIIz7txopPE4gMM7sgueRU+9UqPCYG8T1xfQUfD5/VvXw+mo=
=R+EE
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
*

Hi,

raph <debian@marvie.eu> (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 (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmP7nXQACgkQ/5FK8MKz VSBtaA/8CtD/mVb7Pfk7NB0S96zcY5JCUIHPT0uVYNyTeXmaJ8+Y7j6pAbsvtQmC TtRzO/qg2At1i0FJh3PyXgn1UwfKmn/dMHT2EbNc0qak2bk+TLgN/kBsAO5aukTs KZg36hhD/uLsTBrTPH46W57qaYU769AvNUgDs3sSp88ytJ4z9IpTxPjyUWiE4Euv ahyffNK/j/70nU8qCoNF7Q2BEdrnIWwQxtzWaWZRZl9wUpKX1esAKt561egMgOXZ 2egfIjbg+UKiSLiA+gHDNo3PKvuuxcYaE4fvkWOYx1rL8RvO4A0jOJNktGS2LEch Bw8AUDH+Avn/qWmxDu1KO7aYF/Mz1/n+SI4DbG1vs1dqc618hgae9J5VFfSq8rwh lkywgY+1U/enwcYTsf9Jv3F5YVJ738m0h8ha2nDvTr0v+mWX5Y/Q9OWP/UFKRPgZ VZwaMcmD3eU5Wa/LeAVXOuTNtwgltrj2czxfGh6UNPnLeBqyyLCXVdIrIfIpp5ul i/XGW7h7R+K5xUHVKHD+c0WCHlflA8gFBPByIhnXvMJ83ZNeNqtow8/bk5NlF7pl fkt4wQeiMyeZ6JSldzQfT4Cm5ActAPnAfveKx0t1j2Sgdy0qEYz5YvbxCqTPtu2V 9bLTG82mUKBvi/BjqDQ9glFHXmeKVhCjCkVIfVB+xsYEyRwz1AM=
=26xe
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
*

Cyril Brulebois writes:

Hi,

raph <debian@marvie.eu> (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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

raph <debian@marvie.eu> (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 (kibi@debian.org) <https://debamax.com/>
D-I release manager -- Release team member -- Freelance Consultant

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmP77acACgkQ/5FK8MKz VSAisg/+OaUn12+QMStSIssKMvcDHTRS6TIIa2NUilbhshauTaCcf34pr2FwH7Mb CCAY+snjEQb6hFAyyajbVa7ZpMwbp0EGErvz4Dt+K/Ivlogr7wcc3mU79kJUqYZp BZ7cmRgOK3ArF76sC/KRY+qRWVUMsRds/gTPIF1r7DKEHY7B6tIlYJAZARWIxsNZ 1W/qDt0+RlB6zNhFK6zAzgxjNmDBo77g/tx8VctM+M7K6lDBqXYFFZdPW5IJAxYE 8+C8aTjLWD+ijGg/m9z5GG96iPSNgnpbqzku2wGw4vHkLxkmznidZ8LoyjSNjIL2 aXPzEoGqvbwsOrhUoKSxK7Df7dt0Q6oSWvntCL62yVB8d9wsxq2XOK1OftqoK5sr Uo4kxcakvlHGcRYY/YMqd24VJUtCekf0obIbgYbnD1GkwyuRlL3rim/WkFIw+EdJ 9UrmO9kVbKs4Z2tbY9BSCJX2ql3zXSEl8fIxo800YM9tftw1KpELoPGJw2Yz82sT 5yWsk07fMTGVR76x0JQ9oUaq+w6FHWLBjMqcs9DsS/1+tiFGrk89ioQlu7+TnwGc TlhNmrJybawNPoT3koFxwCxfKgw64HNd+lzdyhY34+5BiqQuUtjpyy1YMI7RK6UF Rvkf+AGnELGUXSR8p0b0RQVIvTWZvAoNv8YsRtlpzCa7uJv92fM=
=/llI
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
*