-------- Original message --------Edited for size       From: fsmithred 
<fsmith...@gmail.com>
 To: dng@lists.dyne.org 
 Sent: Friday, May 11, 2018 6:52 AM
 Subject: Re: [DNG] Unable to "Load missing firmware from removable media"
   
On 05/10/2018 10:05 PM, dan pridgeon wrote:
> I'm trying to install ASCII on a Compaq presaria C700.According to the live 
> boot USB lspci, it has a Broadcom BCM4311 802.11 b/g WLAN [14e4"4311] rev 02 
> for the wireless adapter.  The install complains and ask for two files, the 
> names of which are duplicated for some reason: b43/ucode13.fw and 
> b43-open/ucode13.fw.  Using Gparted on this Refracta laptop, I recreated a 
> partition from scratch using all of the drive and formatting it to ext4 
> format. I then creatd the following structure in hopes of covering all the 
> bases:It contains:
> /ucode13.fw>/b43/ucode13.fw>/b43-open/ucode13.fw
> The installer message: "The missing files are:  b43/ucode13.fw and  
> b43-open/ucode13.fw"
> The permissions are set to 755 at all levels. 
> They are owned by root.


Dan,

Which iso are you using, 

The firmware is in the installer isos, in /firmware. If you choose expert
install (graphical or not) and use a mirror, you will be asked if you want
non-free firmware or not. With a regular install or without a mirror, the
firmware will be installed automatically.

In the live isos, the firmware is already installed, and there's a script
to remove it if you don't want it. (Look in /root or /usr/local/bin/)

fsmithred
_______________________________________________

I'm using the netinst.iso for ASCII. (downloaded about 2-3 weeks ago)  The 
lspci on tty2 allows me to see the hardware as noted above.  Due to licencing, 
the firmware file ( b43/ucode13.fw) cannot be freely distributed. The install 
software detects the correct hardware and presents the user with the correct 
filename(s?) which need to be placed on a removable media. A usb stick in my 
case.
 The 'tree' for the usb follows:
zenos@1stlinux:/media/mnt$ tree /media/mnt
/media/mnt
├── b43
│   └── ucode13.fw
├── b43-open
│   └── ucode13.fw
├── firmware
│   └── ucode13.fw
├── lib
│   ├── firmware
│   │   ├── b43
│   │   │   ├── a0g0bsinitvals5.fw
│   │   │   ├── a0g0bsinitvals9.fw
│   │   │   ├── a0g0initvals5.fw
│   │   │   ├── a0g0initvals9.fw
│   │   │   ├── a0g1bsinitvals13.fw
│   │   │   ├── a0g1bsinitvals5.fw
│   │   │   ├── a0g1bsinitvals9.fw
│   │   │   ├── a0g1initvals13.fw
│   │   │   ├── a0g1initvals5.fw
│   │   │   ├── a0g1initvals9.fw
<snip>
│   │   │   ├── sslpn3initvals21.fw
│   │   │   ├── sslpn4bsinitvals22.fw
│   │   │   ├── sslpn4initvals22.fw
│   │   │   ├── ucode11.fw
│   │   │   ├── ucode13.fw
│   │   │   ├── ucode14.fw
│   │   │   ├── ucode15.fw
│   │   │   ├── ucode16_lp.fw
│   │   │   ├── ucode16_mimo.fw
│   │   │   ├── ucode16_sslpn.fw
│   │   │   ├── ucode16_sslpn_nobt.fw
│   │   │   ├── ucode17_mimo.fw
│   │   │   ├── ucode19_sslpn.fw
│   │   │   ├── ucode19_sslpn_nobt.fw
│   │   │   ├── ucode20_sslpn.fw
│   │   │   ├── ucode20_sslpn_nobt.fw
│   │   │   ├── ucode21_sslpn.fw
│   │   │   ├── ucode21_sslpn_nobt.fw
│   │   │   ├── ucode22_mimo.fw
│   │   │   ├── ucode22_sslpn.fw
│   │   │   ├── ucode24_lcn.fw
│   │   │   ├── ucode24_mimo.fw
│   │   │   ├── ucode25_lcn.fw
│   │   │   ├── ucode25_mimo.fw
│   │   │   ├── ucode26_mimo.fw
│   │   │   ├── ucode27_sslpn.fw
│   │   │   ├── ucode29_mimo.fw
│   │   │   ├── ucode30_mimo.fw
│   │   │   ├── ucode32_mimo.fw
│   │   │   ├── ucode33_lcn40.fw
│   │   │   ├── ucode5.fw
│   │   │   └── ucode9.fw
│   │   ├── b43-open
│   │   │   └── ucode13.fw
│   │   └── ucode13.fw
│   └── ucode13.fw
├── lost+found [error opening dir]
└── ucode13.fw

It still can't find it.
The error message reads as follows:"Direct firmware load for b43/ucode13.fw 
failed with error -2"and"Direct firmware load for b43-open/ucode13.fw failed 
with error -2"It then states: "Broadcom 43xx driver loaded [Features: PNLS]"
What would be the next move?Thank you.
P.S. -  I bought a d-link usb wireless adapter as a possible workaround for a 
situation like this. When plugged, it's vendor data can be seen in the dmesg 
output at the point of install failure, but the lspci does not see it. (I 
suspect a device driver problem.(?)   It was advertised as being supported by 
most Linux distros. (I had hoped the dd would be in the kernel, or included in 
the install).  I can't find a bios option to disable the builtin Broadcom 
adapter, so I think the install does not look any further for a wireless 
adapter beyond the first one it finds.  The livecd boots just fine and the 
lspci allows me to see the Broadcom hardware ok. But not the d-link usb 
adapter.  When plugged, dmesg shows the d-link data ok.


    
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Reply via email to