[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1036565: marked as done (debian-installer-12-netboot-amd64: Installers needed b43 ucode16_mimo.fw, had to eth0 net install + manual firmware-b43-installer, MacBookPro5,5)

Your message dated Thu, 25 May 2023 19:09:49 +0200
with message-id <20230525170949.z4c4pso36gqbleto@mraw.org>
and subject line Re: Bug#1036565: debian-installer-12-netboot-amd64: Installers needed b43 ucode16_mimo.fw, had to eth0 net install + manual firmware-b43-installer, MacBookPro5,5
has caused the Debian Bug report #1036565,
regarding debian-installer-12-netboot-amd64: Installers needed b43 ucode16_mimo.fw,  had to eth0 net install + manual firmware-b43-installer,  MacBookPro5,5
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 owner@bugs.debian.org

1036565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036565
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer-12-netboot-amd64
Severity: normal
Tags: d-i
X-Debbugs-Cc: oregano+debian@disroot.org

Dear Maintainer,

   * What led up to the situation?

Tried to install with live installer on USB stick, plain installer on USB
stick, then net installer on USB stick

   * What exactly did you do (or not do) that was effective (or

Installers popped up error - wanted subject firmware to continue; putting
downloaded (standard) firmware on a second USB stick also failed. Finally
connected to ethernet over cable and installed with net installer on USB stick.

Then installed firmware-b43-installer manually.

   * What was the outcome of this action?

Successful install eventually. :)

   * What outcome did you expect instead?

Needed firmware included with installers so install using WiFi would just work.

-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

debian-installer-12-netboot-amd64 depends on no packages.

debian-installer-12-netboot-amd64 recommends no packages.

Versions of packages debian-installer-12-netboot-amd64 suggests:
pn  tftpd-hpa  <none>

--- End Message ---
--- Begin Message ---

Fan Naibed <oregano+debian@disroot.org> (2023-05-25):
> May 24, 2023 at 9:37 PM, "Cyril Brulebois" <kibi@debian.org> wrote:
> > Do you know which firmware files/packages were involved on those?
> The older macbook has
> 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43224 802.11a/b/g/n [14e4:4353] (rev 01)
> and uses firmware-brcm80211.

OK, so that's supported as the relevant firmware is available as a
Debian package.

> The macbook pro has
> 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4322 802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)
> > Presumably those are working this way because the license doesn't
> > allow for redistribution. Feel free to get that part resolved!
> Since I don't understand how automating the download and install is
> significantly different than including the firmware in the debian
> installer, from a license/legal standpoint, that is beyond me!

I'm not a lawyer, and the following is not legal advice: It's really not
the same thing.

Did you at least try to follow the link and read more about it?

    The Broadcom wireless chip needs proprietary software (called
    "firmware") that runs on the wireless chip itself to work properly. This
    firmware is copyrighted by Broadcom and must be extracted from
    Broadcom's proprietary drivers. To get such firmware on your system, you
    must download the driver from a legal distribution point, extract it,
    and install it. This is accomplished different ways by different Linux
    distributions, so please read the section for yours for the best
    results. You will need an alternate working internet connection (by
    Ethernet cable, for example) since the firmware cannot be included with
    the distro itself.
    Post details for missing distributions at b43-dev@lists.infradead.org .
    Note: the firmware from the binary drivers is copyrighted by Broadcom
    Corporation and cannot be redistributed.

Closing as there's nothing that can be done on the installer side.

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

Attachment: signature.asc
Description: PGP signature

--- End Message ---

Reply to: