You are not logged in.
Yes, knowing whether Trixie's installer supported b43 OOTB would be nice, but the same info about Bookworm would be interesting too. No need to proceed to install as long as the network setup attempt happens before the disk partitioning, which I think it does.
Either way, I'd be pleasantly surprised going on astonished if even the new regular d-i actually shipped b43 firmware. Having it on a 48MB mini.iso is not even something to dream of...
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
I can see this chunk regarding b43 getting spit off into its own topic.
I still haven't got round to trying with the old Belkin b43 PCMCIA card, however, I did experiment with a laptop using Broadcom Corporation BCM43142 before setting it up on Debian Stable for mother.
For that nothing ends up with working wifi post install, never mind being able to use it during the install, nor does the bluetooth get firmware. I tried the Bookworm (firmware) netinstall, an install of BL-Boron, & also the Trixie iso. Nor at any point do any of them ask about firmware, for the wifi or bluetooth (provided by same internal adapter).
Had to:
sudo apt-get install broadcom-sta-dkms
After some detective work (clue found here) which pulled in the usual depends for dkms, & got the wifi (but not the bluetooth) working.
For the bluetooth I had to go "off the reservation" to find firmware, Debian don't appear to have it, clue was here, and firmware here, anyhow after some grepping:
sudo dmesg | egrep -i 'blue|firm'
to confirm I was grabbing the right firmware:
wget https://github.com/winterheart/broadcom-bt-firmware/raw/master/brcm/BCM43142A0-105b-e065.hcd
sudo mv BCM43142A0-105b-e065.hcd /lib/firmware/brcm/
got the bluetooth working also.
I should perhaps have grabbed the .deb though, not in Debian, though a possibility to add for Bunsen?
Someone has that adapter (in my case in a Lenovo G500), I just don't see them easily installing using the wifi, no matter what. Though from the OP's remarks in the linked post on the Mint forum, it appears Mint manages to set the wifi (but not bluetooth) up.
Plain b43 I'll get to later, found hardware I should be able to try on in the junkpile, just not got to it yet.
Last edited by Bearded_Blunder (2024-06-19 15:09:27)
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
OK, I said I'd get to b43 proper...
Bookworm:
Asks for b43-open/ucode5.fw from removeable media, however, it refuses to load it, I'm sure it's nicely packed in a .deb under /cdrom/firmware, or a .deb that will fetch it during installation, assuming you have a connection so wget works (it wasn't in the .deb when I extracted it).
However, even that information is useless, while ucode5.fw can be obtained here even if you create & insert such media with the file in the root AND/OR in a folder called b43-open, it never loads it when you hit OK... One wonders quite what the point of asking is?
Trixie:
Exactly the same story. (Also still throwing that no script error mentioned elsewhere, still same workaround)
If you install using some other connection it's as simple as grabbing firmware-b43-installer from the install media then
sudo dpkg -i firmware-b43-installer
after the install (with the other connection available) firmware-b43-installer pulls stuff in using wget, & boms out if you don't have internet. Assuming you ran the installer with a connection, just reboot to enable it.
Boron:
In the live session the Belkin b43 PCMCIA monstrosity just works! Select SSID, supply pwd, connected.
Installer, however asks for firmware for the intel wifi (iwlwifi-5000-N.ucode N being 1 through 5) Which also works in the live session, & post-install, but can't be used during the install.
That intel adapter has been also present, detected, & useable without supplying firmware for all the others.
But the b43 adapter is found, no request for firmware (!!) Boron's installer manages to use the b43 monstrosity unaided?
Final test:
In the spirit of my sig, Boron no internet at all, let dhcp fail on the unplugged ethernet until it offers configure manually or don't configure... Pick the last one. Want to see what works or not after... Patience, usb2 speed, to mechanical laptop drive, & a slow one at that. After it can't use the mirror, pick continue without...
Result of silly test:
After the reboot & before running bl-welcome, the intel wifi works even though it wouldn't to install on, the b43 wifi works (but slower, it's ancient), & obviously wired also works if plugged in, congratulations on the magic.
Let's see if the firmware test in bl-welcome also fixes the bluetooth, & messed up sources.list..
Which indeed it did...
Now to reinstall again, I want a different disk configuration, sysvinit, & possibly lite or base on that machine. Not tonight though, off to bed early!
Anyone asks me how to do a netinstall using Broadcom wifi, my answer is don't try! Either plug the thing in wired, or buy a USB wifi dongle with a chipset from literally anyone else. There's plenty really cheap ones on the shopping sites that actually advertise Linux compatible.
It's quite sortable to make b43 stuff work after the install, if it doesn't get sorted during, but you're not easily going to make it work to install without the same black magic wrought upon the disk as the Bunsen Boron installer.
There was a guide where someone managed the remarkable feat of installing using a b43 adapter on the old and now offline Crunchbang forums, I haven't spent the time to go looking for it on the wayback machine though.
The Debian netinst isos are just fine with Intel wifi, which was previously problematic unless you got the unofficial "firmware" iso, Broadcom is & always was a nightmare though, why Boron has an issue with Intel & can do b43 I haven't a clue. I'd never have spotted it left to myself, I always plug in wired for installs, since wifi can be flaky.
Apologies for the double post.
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
b43 works on BL isos because the files are physically loaded on the iso.
Debian aren't allowed to host them because of some licensing issue, but they can provide the installer packed inside a .deb.
Anyone can run the installer to download the firmware. Of course that's not possible in the course of an online install because of Catch 22.
I don't know why intel would be a problem on Boron though, especially if the vanilla Debian Installer handles it OK. Maybe if we did a rebuild of the Boron iso it would pull in an improved Debian Installer with an intel fix.
Thanks for the stress-test on networkless install! It's very encouraging to hear that bl-welcome was able to fix up sources.list afterwards. A certain amount of thought went into that section of the script.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Debian aren't allowed to host them because of some licensing issue...
Yet they (Broadcom) provide the exact same firmware to Microsoft to be delivered via Windows Update, or included in their installer, nothing like a consistent approach about it...
I don't know why intel would be a problem on Boron though, especially if the vanilla Debian Installer handles it OK. Maybe if we did a rebuild of the Boron iso it would pull in an improved Debian Installer with an intel fix.
Me either, though i did notice you have firmware-whatever.deb files located elsewhere on the image it's all under /firmware on the Debian isos whereas /firmware is empty on the Bunsen one. Wonder if the version of D-I used is looking in /firmware ? I never did get to grips with unrolling an iso & rolling it back up with tweaks for D-I.
Thanks for the stress-test on networkless install! It's very encouraging to hear that bl-welcome was able to fix up sources.list afterwards. A certain amount of thought went into that section of the script.
You're quite welcome. It worked well.
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
johnraff wrote:I don't know why intel would be a problem on Boron though, especially if the vanilla Debian Installer handles it OK. Maybe if we did a rebuild of the Boron iso it would pull in an improved Debian Installer with an intel fix.
Me either, though i did notice you have firmware-whatever.deb files located elsewhere on the image it's all under /firmware on the Debian isos whereas /firmware is empty on the Bunsen one.
I just had a look at boron-1-240123-amd64.hybrid.iso and debian-12.0.0-amd64-netinst.iso
Debian have a collection of .deb packages under /firmware, while Boron under /firmware has a collection of symlinks pointing to packages in /pool/main/... Maybe the tool you used to unpick the isos didn't see symlinks?
The two lists are not identical though - in general the Debian Bookworm packages are slightly older than what live-build put in on 240123. Fair enough. After removing such date differences with sed I used comm (very handy utility, in coreutils) to compare, and found:
on Boron, not on Debian 12:
alsa-topology-conf_1.2.5.1-2_all.deb
indi-dsi_0.4+20221223123028-1_amd64.deb
ixo-usb-jtag_0.0.1-2_all.deb
libfishcamp1_1.2+20220607003151-1_amd64.deb
libsbig4_4.9.9-4_amd64.deb
nvidia-tesla-470-kernel-support_470.223.02-2~deb12u1_amd64.deb
wireless-regdb
On Debian, not Boron:
firmware-nvidia-gsp_525.105.17-1_amd64.deb
firmware-nvidia-tesla-gsp_525.105.17-1_amd64.deb
firmware-qcom-soc
firmware-samsung
firmware-ti-connectivity
raspi-firmware_1.20220830+ds-1_all.deb
So I don't see anything obviously intel-related that's not in Boron.
Last edited by johnraff (2024-06-24 03:27:56)
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Debian have a collection of .deb packages under /firmware, while Boron under /firmware has a collection of symlinks pointing to packages in /pool/main/... Maybe the tool you used to unpick the isos didn't see symlinks?
Probably because I was looking at the mounted USB, rather than the iso itself The USB being apparently formatted FAT32. FAT filesystems (12, 16, & 32) don't support symlinks. Meaning I've to quit being lazy & use the USB creation tool in dd mode, rather than it's default (recommended by the author) isohybrid mode. Which makes the stick a pain (extra steps) to re-use as a data drive sigh.
If you mount the Boron iso image under Linux you see symlinks, if you mount it under Windows you don't.
Blessed is he who expecteth nothing, for he shall not be disappointed...
If there's an obscure or silly way to break it, but you don't know what.. Just ask me
Offline
A nice surprise in my news feed this morning...
https://www.zdnet.com/article/this-linu … ng-system/
The Bunson Labs Linux!
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
^Nice to be appreciated anyway.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
The Bunson Labs Linux!
Wonderful!
Where's that Bunson from?
Debian 12 Beardog, SoxDog and still a Conky 1.9er
Offline
Where's that Bunson from?
That old variety TV thing, The Muppot Show. Dr. Bunson Honeydow and Beekor, duh! Swedish Chof, Miss Poggy, Kermot the Freg... remember?
No, he can't sleep on the floor. What do you think I'm yelling for?!!!
Offline
Sector11 wrote:Where's that Bunson from?
That old variety TV thing, The Muppot Show. Dr. Bunson Honeydow and Beekor, duh! Swedish Chof, Miss Poggy, Kermot the Freg... remember?
Ummmm - no.
But I do remember The Muppet Show and Dr. Bunsen Honeydew and OF COURSE: Statler and Waldorf
Debian 12 Beardog, SoxDog and still a Conky 1.9er
Offline
They've fixed the spelling in that Znet review:
https://www.zdnet.com/article/this-linu … ng-system/
And added BL to their latest list of 5 lightweight Linux distributions:
https://www.zdnet.com/article/5-lightwe … uirements/
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Having worked with BunsenLabs for a few weeks, I've put it to rigorous testing in my natural way of being difficult with it, and have found it to be quite resilient and literally bulletproof. It's like a "Weebles wobble but they don't fall down".
Thank you BunsenLabs Team for putting out a remarkable OS that improves access to config files for editing.
You bet. BooksPaulsen
Keep swimming. The ocean doesn't get smaller if you stop.
Offline