b43-dev.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Büsch" <mb@bues.ch>
To: "Zedequias Marin (DECO)" <dudecco@gmail.com>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: Re: BCM4312 EEPROM corruption recovery help - HP Mini 110 U98Z049.00
Date: Sun, 2 Nov 2025 19:07:15 +0100	[thread overview]
Message-ID: <20251102190715.317960fa@barney> (raw)
In-Reply-To: <CALaz+jkqX=JX5ODuSJTm0k_qokgYidQ5+Zu1vBuu-zmFZ6JWqQ@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1367 bytes --]

On Sun, 2 Nov 2025 10:27:10 -0300
"Zedequias Marin (DECO)" <dudecco@gmail.com> wrote:

> I found your 2011 thread about BCM4312 issues and need help recovering
> from EEPROM corruption.
> 
> My Device: HP Mini 110
> WiFi Card: Broadcom BCM4312 802.11b/g LP-PHY (14e4:4315)
> Subsystem: Hewlett-Packard Company U98Z049.00
> 
> Problem: I corrupted the EEPROM while trying to configure as WiFi
> repeater. The card is detected but no wireless interface is created.
> EEPROM shows repetitive FF/3F patterns.
> 
> Request: Could anyone provide a known good EEPROM dump for BCM4312
> (14e4:4315) specifically for HP Mini 110/U98Z049.00, or guidance on
> EEPROM recovery?
> 
> I have EEPROM backups and can provide diagnostic info.

Hi,

the PCI ID (14e4:4315) is stored in the wireless device's serial EEPROM.
If the EEPROM is corrupted, you need to find out which PCI ID it uses now.
You can do that with lspci -nn.
Once you found out which corrupted PCI ID your device uses, you can register this
new PCI ID to the b43 driver via sysfs to recognize (see PCI/sysfs documentation).

Then the driver will recognize your device again and you can flash the original
serial EEPROM to the device. See b43-tools/ssb_sprom documentation [1].

[1] https://github.com/mbuesch/b43-tools/tree/master/ssb_sprom

-- 
Michael Büsch
https://bues.ch/

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 149 bytes --]

_______________________________________________
b43-dev mailing list
b43-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/b43-dev

      reply	other threads:[~2025-11-02 18:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-02 13:27 BCM4312 EEPROM corruption recovery help - HP Mini 110 U98Z049.00 Zedequias Marin (DECO)
2025-11-02 18:07 ` Michael Büsch [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251102190715.317960fa@barney \
    --to=mb@bues.ch \
    --cc=b43-dev@lists.infradead.org \
    --cc=dudecco@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).